www.makemkv.com

It's possible your BU40N was actually originally a different slim drive that has since been recased and a fake label applied; a photo would clear this up.

When a drive like that is crossflashed to a firmware with a different boot code, attempting to reflash with the original boot code tends to ...

There are a lot of counterfeit drives from China at the moment that are probably pieced together with spare parts. Tells are:

Incorrect or inconsistent fonts on the labels.
For desktop drives, biggest tell is if the circular sticker at the top has an large indent directly around it (fake for ...

There are a lot of counterfeit drives from China at the moment that are probably pieced together with spare parts. Tells are:

Incorrect or inconsistent fonts on the labels.
For desktop drives, biggest tell is if the circular sticker at the top has an large indent directly around it (fake for ...

The v3 validation script does not blindly patch every BL-looking word, because data tables can contain values that look like Thumb instructions.


Believe it or not the drive does exactly this. Here is some pseudocode as generated by IDA:
i = 0;
if ( DecompressedDataSize >= 4 )
{
do ...

If anyone has a RAM dump of this region after the drive has decompressed it, comparing that against this output would probably show exactly what is still missing.


RAM dump here: https://workupload.com/file/daUYdQasjXj

Please check DMs, I'm interesting in working with you on this; but these ...

Questions:
Has anyone identified the compression/packing method used for this MT1959 firmware block?
Does the decompressor reside inside the firmware itself, or in MT1959 boot ROM / mask ROM?
Does this region contain executable ARM code, servo/DSP microcode, or some other firmware component ...

The latest BU40N Revision 4 hardware incorporates refinements to the internal PCB layout, power regulation and drive control sections. These updates improve mechanical tolerance control and rotational stability, helping to reduce the likelihood of circular surface marking on certain disc types ...

But it's not made in 2023 it's re stickered they stopped making those in 2015


The pre-2016 JB7s use the same casing as the JB8 drives, this new casing that is seen on these 2023-dated JB7 drives suggests they are new, and I doubt the effort would be taken to resticker a whole bunch of drives ...

These "a" drives as well as other drives from China seem to often (but not always) be the JB7-board (MT1939) even if the date on the sticker is >=2016. Here is an example of a BW-16D1HT from China that was manufactured December 2023 and yet is JB7/MT1939:
https://i.postimg.cc/653PC3wS/image.png ...

In terms of cases for the slimline drives I have a ECD819-SU3 which seems to work very well on my BU40N and passes through all commands just fine. They seem to be available under a whole bunch of cheap brands.

Ordered a Pioneer drive and it arrived quickly and working great!

I am confused though, the date on the drive sticker is June 2023; did they ship drives with old firmware or is there some sort of secret flashing method...

Late reply, but you can enable force-downgrading on the official flashing tool by changing the byte at 0x9F89 in the EXE from 0x00 to 0x01. This allowed me to flash from 1.02 firmware back to 1.01. No idea if this works with "patched" firmwares from December 2022 onwards, my guess is that it ...

Late reply, but you can enable force-downgrading on the official flashing tool by changing the byte at 0x9F89 in the EXE from 0x00 to 0x01. This allowed me to flash from 1.02 firmware back to 1.01. No idea if this works with "patched" firmwares from December 2022 onwards, my guess is that it doesn't ...

No one officially ever promised anyone that there would be some “release date” of that to the public from the MakeMKV side. If someone told you this or promised it to you then they have flat out lied to you or are trolling you.

MakeMKV and all source code related to that software is owned by and ...

kurayamino wrote: Mon Sep 21, 2020 5:27 am I don't see different AUN start/end values when I specify different layers in the CDB at offset 6. Super hacky POC code attached -- have I done something wrong?

Hmm, I'm getting the same results. Doesn't match the documentation I found for sure.