www.makemkv.com

dennis__ wrote: Mon Mar 11, 2024 2:14 am

V1.05 is encrypted. You need to add 'enc' to the command line.

I have tried adding enc after the rawflash parameter like I read in a post above -

Code: Select all

sudo makemkvcon f -f sdf_00000065.bin -d /dev/sr0 rawflash enc -i HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin 
[sudo] password for dennis: 

Parameter 'enc' not recognized

Command produced error code 0x8f1e0005

Then I tried it in a few other spots with a similar error or "Unknown command".

I hate to ask for you to spell it out for me but could you tell me exactly how to inform makekvon that the existing fw is encrypted?

why dont we use the guide endorsed by the developer thats pinned that has the linux stuff right and up to date....

dennis__ wrote: Mon Mar 11, 2024 2:14 am

V1.05 is encrypted. You need to add 'enc' to the command line.

I have tried adding enc after the rawflash parameter like I read in a post above -

Code: Select all

sudo makemkvcon f -f sdf_00000065.bin -d /dev/sr0 rawflash enc -i HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin 
[sudo] password for dennis: 

Parameter 'enc' not recognized

Command produced error code 0x8f1e0005

Then I tried it in a few other spots with a similar error or "Unknown command".

I hate to ask for you to spell it out for me but could you tell me exactly how to inform makekvon that the existing fw is encrypted?

Lifted from the guide, using your info, try...

./makemkvcon f -d '/dev_21:2' -f sdf_00000065.bin rawflash enc -i HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin

Billycar11 wrote: Mon Mar 11, 2024 2:27 am why dont we use the guide endorsed by the developer thats pinned that has the linux stuff right and up to date....

Sounds good. Where is it? This? Because I downloaded it and its an exe.
Otherwise I looked around the board under LibreDrive Drives and MakeMKV for Linux. Sorry if I missed it but I do not see it.

d00zah wrote: Mon Mar 11, 2024 2:30 am
Lifted from the guide, using your info, try...

./makemkvcon f -d '/dev_21:2' -f sdf_00000065.bin rawflash enc -i HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin

Thanks but I am still having issues. Could you update your post to link to the guide? It is currently linking this thread.

dennis__ wrote: Mon Mar 11, 2024 3:15 am

d00zah wrote: Mon Mar 11, 2024 2:30 am
Lifted from the guide, using your info, try...

./makemkvcon f -d '/dev_21:2' -f sdf_00000065.bin rawflash enc -i HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin

Thanks but I am still having issues. Could you update your post to link to the guide? It is currently linking this thread.

done. sorry.

Got it downgraded / changed. Thanks!

Well hello everyone! I'm hijacking this thread as the OP seems to be done with it and I am in a similar enough situation that I think making a new one only would make things harder to find.

I am here sitting at a Linux computer (Rocky Linux and I have been using MakeMKV to rip my Blurays with a decent enough successrate for a few years now. Up until this year I was on the windows platform, but my computer was too old for the coming win11, so I did the switch to Linux.

That's my backstory. I have extensive experience with computers, but I am a fumbling n00b in the Linux space.

Now... I was thinking I should try my hand at UHD-ripping. I looked around, Seems drives are getting discontinued so I pulled the trigger and got myself a BW-16D1HT. And as I now installed it along with my existing bluray drive that I have been using for HD blurays all this time. I look in MakeMKV and I see... that it's the same darned model number. Only difference being in firmware. Old one running at v1.03. New one is at v3.11. As the big thread about flashing says, there's probably other things different, as the box does say it can do 128GB writing and the old one only did DVD-writing.

Anywhooo. Preamble aside.

I have read through this here thread. And read a bit of the thread with the big guides. I am getting a bit stumped (like I usually do with linux research, lots and lots of conflicting information and very little consensus and even more irrellevant and outdated things abound).

As I understand things... I should use MakeMKV's GUI to determine platform and stuff. the new drive is using MT1959. LibreDrive is "Possible, not yet enabled"



As I have also gathered, Newer firmwares are tricky, as the modded firmware is 3.10 I need to downgrade the firmware and 3.11 doesn't like that.

I have tried following the big guide. I am assuming that the steps outlined for Mac/Linux are the same for both OS's. So I try to find the "makemkvconf". And I did that... here:

/home/flatpak/app/com.makemkv.MakeMKV/current/4b1d0cea3dd4a8b9c7bba3aedadd92fe1edc96c3876c97bf6b9a7357a625f3b8/files/bin

Now, I can hear dear reader screaming. But... yes. I installed makemkv via the software app. So it's using the flatpak version. It's been working fine for the older drive (it's ripping season 3 disc 5 of Twilight Zone 1959 as I type this).

When I navigate to that folder, and I try using the command to list the drive identifier "./makemkvcon f -l", I get this result:
Again, I hear you screaming. It's probably because I am using the flatpak version. The Makemkvconf file I found is probably not useable like some other install would give me. But I claim ignorance there. I do not know of another way to install makemkv on this linux computer.

So. I know the disclaimers and warnings. Flashing a firmware is not to be taken lightly. If I mess up. I have only myself to blame, no matter what someone here types out. But... since I do have the older drive working for HD discs. I feel like I can do some mucking around with the new drive. Best case, I get it to work with UHD-ripping. Worst case, I brick it.

TLDR:

On Linux. With an ASUS BW-16D1HT drive currently running firmware v3.11. If I only have the flatpak installed. How do I do the flashing? Because the big guide does not detail it as far as I have read (there's 200+ of pages of all sorts of discussions irrelevant to my drive in that thread so I can't be sure), is it possible to get the makemkvcon file working from some other source?

The 1st post of the guide is the only part that is maintained & relevant. The rest is largely 'noise'. It contains links to FW & tools, instructional videos, recommended FW for supported drives & specifically, an example of the linux command line needed to flash your drive. Focus on the 1st post.

Hi @jmalmsten,

you cannot execute the binaries from a flatpak directly; you always have to use flatpak run to execute them.

Using what you try as an example you need to execute this:

gabiel wrote: Thu Sep 04, 2025 3:19 pm Hi @jmalmsten,

you cannot execute the binaries from a flatpak directly; you always have to use flatpak run to execute them.

Using what you try as an example you need to execute this:

Code: Select all

flatpak run --command=makemkvcon com.makemkv.MakeMKV f -l

ok, first of all, Thanks for helping, it is very appreicated.

I did try that now. I got this result:
ok so I gather that the syntax then is:

flatpak run --command=makemkvcon com.makemkv.MakeMKV and then the arguments.

so in the guide it's

7. to perform the flash, type "./makemkvcon f -d '/IOBDServices/D5D25996' -f /tmp/sdf.bin rawflash main -i /tmp/your firmware filename here
or ./makemkvcon f -d '/IOBDServices/D5D25996' -f /tmp/sdf.bin rawflash enc -i /tmp/your firmware filename here
if your firmware is on the encrypted list

which, if I understand things corrently should make my modified command (bolded bits where I add my specific drive and firmware):

flatpak run --command=makemkvcon com.makemkv.MakeMKV f -d '/dev_21:2' -f /tmp/sdf.bin rawflash enc -i /tmp/ASUS-BW-16D1HT-3.10-WM01601-211901041014.bin

I have put the firmware bin and the sdf.bin file in my /tmp folder. But when I run that command I get this result:
Now. I have the suspicion that the flatpak may not be able to see the tmp folder because of how flatpaks work (I think).

I have another thread going, trying to find out how to install makeMKV on Rocky Linux without flatpak. But if you know of how to point the flatpak to the /tmp folder. That may suffice?

Yes, you are correct, the Flatpaks are sandboxed and depending on the given permissions they can/cannot access some parts of the file system.

For com.makemkv.MakeMKV, by default it can only access your "videos" and ~/.MakeMKV directories.

You can check the permissions using Or you can use flatseal for a graphical interface.

If you plan to compile the Linux version keep in mind that it seems that there are issues with versions above 1.17.7; you can grab older versions from here: https://www.makemkv.com/download/old/