Attempting to flash in macOS

Discussion of LibreDrive mode, compatible drives and firmwares
MartyMcNuts
Posts: 3092
Joined: Wed Nov 22, 2017 11:45 pm

Re: Attempting to flash in macOS

Post by MartyMcNuts »

eMouse wrote:
Wed Mar 06, 2024 10:42 pm
I'll run the latest OS update and see if it changes anything.

I had to re-download MakeMKV, so it is the latest version of that.

The drive is plugged into a USB hub, which is then plugged into the Mac. It's a Mac mini, and the drive requires two USB ports, so plugging it directly into the Mac isn't really an option.

If necessary, I can connect the drive to a windows machine, but this Mac is what I use 90% of the time.
If using a USB hub, make sure it is a powered one, not one that gets power from a USB port.

It would be quicker and easier to connect it to a Windows PC for flashing purposes as it only takes a minute.
Cheers :D
----------------------------------------------------------------------------------------------------------------------------
For UHD enabled drives (AU/NZ/SG + Others) & DIY Single Drive Flasher (WW): https://uhdenableddrives.com
eMouse
Posts: 4
Joined: Wed Mar 06, 2024 7:05 pm

Re: Attempting to flash in macOS

Post by eMouse »

I updated to the latest version of Sonoma. Still have the same issue where it doesn't show a usable identifier for the drive. I'm going to guess that Sonoma changed something about how that identifier is obtained and MakeMKV hasn't updated to handle that change yet.

Ended up flashing it with the visual flasher on Windows.
absent2999
Posts: 4
Joined: Fri Dec 20, 2024 6:15 pm

Re: Attempting to flash in macOS

Post by absent2999 »

Hi there, been trying on a Mac for awhile and having no luck. Keep getting the same error, no matter what firmware I try. And I feel like I've tried them all. Here's what I see in terminal:

Reading input file /tmp/HL-DT-ST-BD-RE_WH16NS40-NS50-1.05-NM00900-212005061440.bin
Flashing flags = 0x0 : 0 0 0 0 : ---- ---- ---- ----
Sending image in encrypted format
Current Drive ID: HL-DT-ST_BD-RE__WH16NS40_1.05_212005061440_M00MAEC4935
Ready to write drive flash memory.
Type "yes" to continue, "no" to abort
yes
Operation started: Sending flash image to drive
6% ...
Write DRAM NG 04/08/03
Command produced error code 0x82040803


I get that same Write Dram and error code every time, regardless of firmware. Is there an obvious step I'm missing?
dcoke22
Posts: 3322
Joined: Wed Jul 22, 2020 11:25 pm

Re: Attempting to flash in macOS

Post by dcoke22 »

absent2999 wrote:
Fri Dec 20, 2024 6:33 pm
Hi there, been trying on a Mac for awhile and having no luck. Keep getting the same error, no matter what firmware I try. And I feel like I've tried them all. Here's what I see in terminal:

Reading input file /tmp/HL-DT-ST-BD-RE_WH16NS40-NS50-1.05-NM00900-212005061440.bin
Flashing flags = 0x0 : 0 0 0 0 : ---- ---- ---- ----
Sending image in encrypted format
Current Drive ID: HL-DT-ST_BD-RE__WH16NS40_1.05_212005061440_M00MAEC4935
Ready to write drive flash memory.
Type "yes" to continue, "no" to abort
yes
Operation started: Sending flash image to drive
6% ...
Write DRAM NG 04/08/03
Command produced error code 0x82040803


I get that same Write Dram and error code every time, regardless of firmware. Is there an obvious step I'm missing?
What command are you using in terminal?
Billycar11
Posts: 4509
Joined: Sun Aug 24, 2014 5:49 am

Re: Attempting to flash in macOS

Post by Billycar11 »

absent2999 wrote:
Fri Dec 20, 2024 6:33 pm
Hi there, been trying on a Mac for awhile and having no luck. Keep getting the same error, no matter what firmware I try. And I feel like I've tried them all. Here's what I see in terminal:

Reading input file /tmp/HL-DT-ST-BD-RE_WH16NS40-NS50-1.05-NM00900-212005061440.bin
Flashing flags = 0x0 : 0 0 0 0 : ---- ---- ---- ----
Sending image in encrypted format
Current Drive ID: HL-DT-ST_BD-RE__WH16NS40_1.05_212005061440_M00MAEC4935
Ready to write drive flash memory.
Type "yes" to continue, "no" to abort
yes
Operation started: Sending flash image to drive
6% ...
Write DRAM NG 04/08/03
Command produced error code 0x82040803


I get that same Write Dram and error code every time, regardless of firmware. Is there an obvious step I'm missing?
what your doing should work so issue is probably the usb to sata adapter
what adapter do you have?
Buy a UHD drive from the guide and how to video maker: https://www.makemkv.com/forum/viewtopic ... 20&t=17831
UHD Drives Guide: https://www.makemkv.com/forum/viewtopic ... 16&t=19634
Auto flash kit $25 Email me for one Billycar5924@gmail.com
absent2999
Posts: 4
Joined: Fri Dec 20, 2024 6:15 pm

Re: Attempting to flash in macOS

Post by absent2999 »

Billycar11 wrote:
Sat Dec 21, 2024 5:26 am

what your doing should work so issue is probably the usb to sata adapter
what adapter do you have?

I'm not sure what you mean by what adapter... I just have the usb cable from my enclosure to my Mac?

But I just tried this on a different drive, the BP50NB40, which just has a usb from the drive to the Mac, and I get the same error. Is there a different cable I should be using?

I never have trouble ripping blu rays with either of these drives, just trying to get started ripping 4k discs.
Billycar11
Posts: 4509
Joined: Sun Aug 24, 2014 5:49 am

Re: Attempting to flash in macOS

Post by Billycar11 »

absent2999 wrote:
Wed Jan 01, 2025 7:07 pm
Billycar11 wrote:
Sat Dec 21, 2024 5:26 am

what your doing should work so issue is probably the usb to sata adapter
what adapter do you have?

I'm not sure what you mean by what adapter... I just have the usb cable from my enclosure to my Mac?

But I just tried this on a different drive, the BP50NB40, which just has a usb from the drive to the Mac, and I get the same error. Is there a different cable I should be using?

I never have trouble ripping blu rays with either of these drives, just trying to get started ripping 4k discs.
What case do you have I'm asking
The bp50 should definitely be able to be flashed what fw did you try on that? Well unless it's nb72
Buy a UHD drive from the guide and how to video maker: https://www.makemkv.com/forum/viewtopic ... 20&t=17831
UHD Drives Guide: https://www.makemkv.com/forum/viewtopic ... 16&t=19634
Auto flash kit $25 Email me for one Billycar5924@gmail.com
absent2999
Posts: 4
Joined: Fri Dec 20, 2024 6:15 pm

Re: Attempting to flash in macOS

Post by absent2999 »

Billycar11 wrote:
Wed Jan 01, 2025 9:37 pm
absent2999 wrote:
Wed Jan 01, 2025 7:07 pm
Billycar11 wrote:
Sat Dec 21, 2024 5:26 am

what your doing should work so issue is probably the usb to sata adapter
what adapter do you have?

I'm not sure what you mean by what adapter... I just have the usb cable from my enclosure to my Mac?

But I just tried this on a different drive, the BP50NB40, which just has a usb from the drive to the Mac, and I get the same error. Is there a different cable I should be using?

I never have trouble ripping blu rays with either of these drives, just trying to get started ripping 4k discs.
What case do you have I'm asking
The bp50 should definitely be able to be flashed what fw did you try on that? Well unless it's nb72
Thank you for your help!

For the WH case, I don't know what case actually. It's an old generic case I got from a used computer store, so maybe that's the problem.

But for the BP50, it's NB52. This is what it says when I open MakeMKV

Drive Information
Manufacturer: HL-DT-ST
Product: BD-RE BP50NB40
Revision: 1.03
Serial number: ...
Firmware date: 2121-07-08 16:03
Bus encryption flags: 17
Highest AACS version: 81

LibreDrive Information
Status: Possible (with patched firmware)
Drive platform: MT1959
Harware support: Yes
Firmware support: No
Firmware type: Original (patched version available)
Firmware version: 1.03
DVD all regions: Possible (with patched firmware)
BD raw data read: Possible (with patched firmware)
BD raw metadata read: Possible (with patched firmware)
Unrestricted read speed: Possible (with patched firmware)



And this is the error I get in Mac terminal:


Reading input file /tmp/DE_LG_BP60NB10_1.00_MK_HBD.bin
Flashing flags = 0x0 : 0 0 0 0 : ---- ---- ---- ----
Current Drive ID: HL-DT-ST_BD-RE_BP50NB40_1.03_212107081603_SIM2222MK0421
Using USB chipset workaround for Desktop drive handshake
Ready to write drive flash memory.
Type "yes" to continue, "no" to abort
yes
Operation started: Sending flash image to drive
98% .................................................
Write DRAM NG 05/24/00

Command produced error code 0x82052400
absent2999
Posts: 4
Joined: Fri Dec 20, 2024 6:15 pm

Re: Attempting to flash in macOS

Post by absent2999 »

Okay well actually I think I was able to get it to work on my BP50, I must have been using the wrong firmware in my last go round.


In Terminal, this is what happened:
Reading input file /tmp/DE_LG_BP60NB10_1.00_MK_HBD.bin
Flashing flags = 0x0 : 0 0 0 0 : ---- ---- ---- ----
Current Drive ID: HL-DT-ST_BD-RE_BP50NB40_1.03_212005070917_SIM2222MK0421
Using USB chipset workaround for Desktop drive handshake
Ready to write drive flash memory.
Type "yes" to continue, "no" to abort
yes
Operation started: Sending flash image to drive
100% Operation finished
Operation started: Programming flash
100% Operation finished
Done successfully


MakeMKV now shows this:

Drive Information
Manufacturer: HL-DT-ST
Product: BD-RE BP50NB40
Revision: 1.03
Serial number: ...
Firmware date: 2120-05-07 09:17
Bus encryption flags: 17
Highest AACS version: 81

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 1.03
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Currently ripping a disc now!
Coopervid
Posts: 2306
Joined: Tue Feb 19, 2019 10:32 pm

Re: Attempting to flash in macOS

Post by Coopervid »

Your enclosure for the full size drive doesn't support flashing. Connect it to SATA with a desktop PC. And the slim drive has been flashed before as ist doesn't report to be what you tried to flash.
ThatGuyName
Posts: 6
Joined: Tue Aug 08, 2023 5:45 pm

Re: Attempting to flash in macOS

Post by ThatGuyName »

I'm still having a problem with actually flashing it. everything goes swell until the last step when it gives me the error:
"Input file not found -- /HL-DT-ST-BD-RE_BP60NB10-1.02-NM00800-212005070935
Internal error 0x83000001"
It also wont let me make a tmp folder for some reason?
"zsh: permission denied: /tmp"
dcoke22
Posts: 3322
Joined: Wed Jul 22, 2020 11:25 pm

Re: Attempting to flash in macOS

Post by dcoke22 »

ThatGuyName wrote:
Wed Jan 22, 2025 5:03 pm
I'm still having a problem with actually flashing it. everything goes swell until the last step when it gives me the error:
"Input file not found -- /HL-DT-ST-BD-RE_BP60NB10-1.02-NM00800-212005070935
Internal error 0x83000001"
It also wont let me make a tmp folder for some reason?
"zsh: permission denied: /tmp"
Where did you put the firmware file you're trying to flash into your drive? Is it in a folder on your Desktop? Or perhaps in your Downloads folder?

Wherever it is, when you're typing the command in Terminal to perform the flash (aka Step 7 in the Mac/linux commands to flash in the Guide) when you get to the spot where you're supposed to type the firmware filename… don't type it, find the file in Finder and drag it into Terminal. Terminal will put the fully qualified pathname to the file wherever the cursor is in Terminal.

You can do the same thing for sdf.bin.

When the instructions in the Guide say, in step 4, to copy sdf.bin and the firmware file into /tmp, what it means is "put those two files into a temporary folder of your choosing." Later, when the commands reference '/tmp/sdf.bin' for example, what it means is "put the fully qualified path to the file here." On a Mac, the easiest way to do this is to drag & drop the relevant file from Finder into Terminal and it'll do the right thing.

The /tmp shorthand comes to us from Ye Olden Days™, before the internet existed and before the Mac was invented. Back then there really was a folder named 'tmp' at the root of the filesystem and you really could copy things there temporarily. As operating systems got more complicated and security got better, /tmp more or less disappeared or became hard to use but the shorthand of /tmp survives because 4 characters is way easier to type than the two paragraphs I've got here. :)
ThatGuyName
Posts: 6
Joined: Tue Aug 08, 2023 5:45 pm

Re: Attempting to flash in macOS

Post by ThatGuyName »

dcoke22 wrote:
Thu Jan 23, 2025 4:36 pm
ThatGuyName wrote:
Wed Jan 22, 2025 5:03 pm
I'm still having a problem with actually flashing it. everything goes swell until the last step when it gives me the error:
"Input file not found -- /HL-DT-ST-BD-RE_BP60NB10-1.02-NM00800-212005070935
Internal error 0x83000001"
It also wont let me make a tmp folder for some reason?
"zsh: permission denied: /tmp"
Where did you put the firmware file you're trying to flash into your drive? Is it in a folder on your Desktop? Or perhaps in your Downloads folder?

Wherever it is, when you're typing the command in Terminal to perform the flash (aka Step 7 in the Mac/linux commands to flash in the Guide) when you get to the spot where you're supposed to type the firmware filename… don't type it, find the file in Finder and drag it into Terminal. Terminal will put the fully qualified pathname to the file wherever the cursor is in Terminal.

You can do the same thing for sdf.bin.

When the instructions in the Guide say, in step 4, to copy sdf.bin and the firmware file into /tmp, what it means is "put those two files into a temporary folder of your choosing." Later, when the commands reference '/tmp/sdf.bin' for example, what it means is "put the fully qualified path to the file here." On a Mac, the easiest way to do this is to drag & drop the relevant file from Finder into Terminal and it'll do the right thing.

The /tmp shorthand comes to us from Ye Olden Days™, before the internet existed and before the Mac was invented. Back then there really was a folder named 'tmp' at the root of the filesystem and you really could copy things there temporarily. As operating systems got more complicated and security got better, /tmp more or less disappeared or became hard to use but the shorthand of /tmp survives because 4 characters is way easier to type than the two paragraphs I've got here. :)
So in the command where it says "/tmp" do I also replace that with the name of my chosen folder?
Or do I drag the folder whenever it says "tmp"? I've tried both ways and it's still not working. Do I have to put the two files into a folder or no? and If I choose not two what do I replace /tmp with? Desktop?

If my folder is named "rio" and it's in desktop, then is this correct:
./makemkvcon f -d '/IOBDServices/D5D25996' -f /Users/NAME/Desktop/rio/sdf.bin rawflash enc -i/Users/NAME/Desktop/rio/Users/NAME/Desktop/rio/HL-DT-ST-BD-RE_BP60NB10-1.02-NM00800-212005070935.bin ?
dcoke22
Posts: 3322
Joined: Wed Jul 22, 2020 11:25 pm

Re: Attempting to flash in macOS

Post by dcoke22 »

ThatGuyName wrote:
Fri Jan 24, 2025 12:10 am
So in the command where it says "/tmp" do I also replace that with the name of my chosen folder?
Or do I drag the folder whenever it says "tmp"? I've tried both ways and it's still not working. Do I have to put the two files into a folder or no? and If I choose not two what do I replace /tmp with? Desktop?

If my folder is named "rio" and it's in desktop, then is this correct:
./makemkvcon f -d '/IOBDServices/D5D25996' -f /Users/NAME/Desktop/rio/sdf.bin rawflash enc -i/Users/NAME/Desktop/rio/Users/NAME/Desktop/rio/HL-DT-ST-BD-RE_BP60NB10-1.02-NM00800-212005070935.bin ?
Where is says '/tmp/sdf.bin' in the command, drag the sdf.bin file into Terminal. And then for the part where the firmware goes, drag the firmware file into Terminal.

Code: Select all

./makemkvcon f -d '/IOBDServices/D5D25996' -f /Users/NAME/Desktop/rio/sdf.bin rawflash enc -i /Users/NAME/Desktop/rio/HL-DT-ST-BD-RE_BP60NB10-1.02-NM00800-212005070935.bin
As a sidenote, you have to do step 6 and substitute your actual drive identifier into the correct spot in command used in step 7. The one in your command is the same as the example, which is very unlikely. :)
ThatGuyName
Posts: 6
Joined: Tue Aug 08, 2023 5:45 pm

Re: Attempting to flash in macOS

Post by ThatGuyName »

dcoke22 wrote:
Fri Jan 24, 2025 7:37 am
ThatGuyName wrote:
Fri Jan 24, 2025 12:10 am
So in the command where it says "/tmp" do I also replace that with the name of my chosen folder?
Or do I drag the folder whenever it says "tmp"? I've tried both ways and it's still not working. Do I have to put the two files into a folder or no? and If I choose not two what do I replace /tmp with? Desktop?

If my folder is named "rio" and it's in desktop, then is this correct:
./makemkvcon f -d '/IOBDServices/D5D25996' -f /Users/NAME/Desktop/rio/sdf.bin rawflash enc -i/Users/NAME/Desktop/rio/Users/NAME/Desktop/rio/HL-DT-ST-BD-RE_BP60NB10-1.02-NM00800-212005070935.bin ?
Where is says '/tmp/sdf.bin' in the command, drag the sdf.bin file into Terminal. And then for the part where the firmware goes, drag the firmware file into Terminal.

Code: Select all

./makemkvcon f -d '/IOBDServices/D5D25996' -f /Users/NAME/Desktop/rio/sdf.bin rawflash enc -i /Users/NAME/Desktop/rio/HL-DT-ST-BD-RE_BP60NB10-1.02-NM00800-212005070935.bin
As a sidenote, you have to do step 6 and substitute your actual drive identifier into the correct spot in command used in step 7. The one in your command is the same as the example, which is very unlikely. :)
ah, I see. sorry about that. I'll try again.

EDIT: IT WORKS!!!!! thanks so much. Sorry about all that. I'm not really good with terminal I'm more of an editing guy.
Post Reply