I just bought a BC-12D2HT drive that uses 3.11 fw.

[laughing]

Hi,
I just bought a BC-12D2HT drive that uses 3.11 fw.
Can you help me to downgrade the fw?
thanks a lot
can not find any tool to downgrade BC-12D2HT from 3.11 to 3.10 at this location. Might be removed.
Any other resource available?
I need a detailed tutorial. Thank you

[st4evr]

There is a very detailed instructional sticky post here:

https://www.makemkv.com/forum/viewtopic ... 16&t=19634

At the top of this forum that contains the information you are looking for. Including links to step-by-step videos on how to flash. But you have to do your part and read it. So READ that first.

If you are unable to follow those types of instructions, then you can find additional help here:

https://www.makemkv.com/forum/viewforum.php?f=20

And pay someone to do it for you.

[diffus1on]

I also just bought a BC-12D2HT with original 3.11 firmware, manufactured April 2019.

I am attempting to flash the drive with the following firmware which was recommended in the guides.

ASUS-BW-16D1HT-3.10-WM01601-211901041014.bin
Modified ‎Tuesday, ‎19 ‎March ‎2019, ‏‎11:57:59 p.m.
CRC-32: 3dd30242
MD4: 4942bfa77c680372a6838352da4c5b3e
MD5: fd8d913e6d3d788cce02d42cc88c5991
SHA-1: 303a00628bbf67ee8ba61757d61c370e45bd4451

I was not able to make a backup via dosflash as it gives me the MTK name error.


I tired the ASUS tool with the following details but it give me updating failure #5.
ASUS_ODD_FW_Changer_(Modified).exe
Modified ‎Saturday, ‎24 ‎August ‎2019, ‏‎12:13:11 a.m.
CRC-32: 45828ee9
MD4: 25806e4a8949b8e6e73104e064426979
MD5: 61a8bc642db0c5bca7a12282aad66f7d
SHA-1: 81712c1084000e43fb91097f129961a98b5e112e

I then tried with HL tool and it gave me the error checksum is mismatched drive will go to boot mode.
BH14NS40_N1.00-A4_patched.exe
Modified ‎Saturday, ‎3 ‎November ‎2018, ‏‎12:00:36 a.m.
CRC-32: e9604fe2
MD4: 32245b1a192ef6d7e810b842ea47a391
MD5: 8635650a95701e57157915a9dc1c46f1
SHA-1: 8482a1a5d63ede18a6e0e925a141cf0447551679


What further steps can I take from here?

[Billycar11]

What further steps can I take from here?

How is your drive hooked up?

[diffus1on]

What further steps can I take from here?

How is your drive hooked up?

Using a HP Compaq 6300 SFF 3570 in legacy IDE mode.
Windows 7 32bit

I tried a gigabyte b85m-d3h 4770 PC in IDE mode and dosflash could not see the drive.

[SamuriHL]

No dosflash. That's not how you downgrade these drives.

Sent from my SM-G975U using Tapatalk

[diffus1on]

No dosflash. That's not how you downgrade these drives.

Sent from my SM-G975U using Tapatalk

Just looking for a way to backup the original EEPROM data in case something goes wrong, I indented to use the recommended tolls after I had a backup of the EEPROM.
Has anyone be able to read the EEPROM data with DOSFlash on a drive that did not originally support DOSFlash after being flashed to an MK or similar firmware?

I forgot to mention that the drive is connected via SATA directly into the motherboard. The OS is installed on a spare hard drive - not the live USB boot PE version.

Kind regards.

[Billycar11]

Using a HP Compaq 6300 SFF 3570 in legacy IDE mode.
Windows 7 32bit

I tried a gigabyte b85m-d3h 4770 PC in IDE mode and dosflash could not see the drive.

dos flash does not work asus 3.10+ lg 1.4+ and bu40n 1.3+

watch my video and cross flash your drive to 3.10MK with the asus tool. here are some more instructions and the videos https://www.makemkv.com/forum/viewtopic ... 16&t=19634

[diffus1on]

Using a HP Compaq 6300 SFF 3570 in legacy IDE mode.
Windows 7 32bit

I tried a gigabyte b85m-d3h 4770 PC in IDE mode and dosflash could not see the drive.

dos flash does not work asus 3.10+ lg 1.4+ and bu40n 1.3+

watch my video and cross flash your drive to 3.10MK with the asus tool. here are some more instructions and the videos https://www.makemkv.com/forum/viewtopic ... 16&t=19634

I followed that guide prior to my original post #3. However the version of the ASUS tool I used is different.
I used the version of the tool dated ‎24 ‎August 2019 with CRC-32 45828ee9. The version of the tool in that post is dated ‎21 ‎March ‎2019 with CRC-32 350f91e1

I will use that older version of the tool you specified and will report back with my findings soon.


Additionally, MartyMcNuts patched the ASUS BW-16D1HT tool in page 1, post 10 of https://www.makemkv.com/forum/viewtopic ... 16&t=18873 which is not the correct version for my drive (BC-12D2HT), would it be worth trying that one as well?

[Billycar11]

I followed that guide prior to my original post #3. However the version of the ASUS tool I used is different.
I used the version of the tool dated ‎24 ‎August 2019 with CRC-32 45828ee9. The version of the tool in that post is dated ‎21 ‎March ‎2019 with CRC-32 350f91e1

I will use that older version of the tool you specified and will report back with my findings soon.


Additionally, MartyMcNuts patched the ASUS BW-16D1HT tool in page 1, post 10 of https://www.makemkv.com/forum/viewtopic ... 16&t=18873 which is not the correct version for my drive (BC-12D2HT), would it be worth trying that one as well?

No use the current Asus tool in Marty's thread and Mike's mk fw in libredrive section

This drive is connected with sata right?
Because some USB adapters don't support flashing

[SamuriHL]

I would also change the bios to ahcpi for that SATA port the drive is on. You mentioned setting it to ide which is only needed for dosflash.

Sent from my SM-G975U using Tapatalk

[diffus1on]

I'll take a look at these firmwares in 12 hours from the time of this post.

Kind regards


Edit, having problems with AHCI drivers. Switching to Windows 10


Edit2, Windows 10 1903 x64 in Legacy BIOS with AHCI using the following tools does not work.

ASUS-BW-16D1HT-3.10-WM01601-211901041014.bin
Modified ‎19 ‎March ‎2019
CRC-32: 3dd30242
MD4: 4942bfa77c680372a6838352da4c5b3e
MD5: fd8d913e6d3d788cce02d42cc88c5991
SHA-1: 303a00628bbf67ee8ba61757d61c370e45bd4451

ASUS_ODD_FW_Changer_(Modified).exe
Modified ‎24 ‎August ‎2019
CRC-32: 45828ee9
MD4: 25806e4a8949b8e6e73104e064426979
MD5: 61a8bc642db0c5bca7a12282aad66f7d
SHA-1: 81712c1084000e43fb91097f129961a98b5e112e

ASUS_ODD_FW_Changer_(Modified).exe
Modified 21 ‎March ‎2019
CRC-32: 350f91e1
MD4: b9e2e9cc3e812e2ff484c4f66ba81e93
MD5: e83e8c24545da818475ec765479ed696
SHA-1: b4dc1a7fb6d629b05419e055d133679ab7e005bc

Both tools using that firmware gives the same error #5.

[diffus1on]

Windows 10 1903 x32 in legacy BIOS with AHCI results in error #5 using the same tools as above.
The drive is connected via SATA into the motherboard

So far I have tried

Windows 7 32 IDE
MK ASUS-BW-16D1HT-3.10-WM01601-211901041014
ASUS_ODD_FW_Changer_(Modified).exe ‎24 ‎August ‎2019 (checksum above)
ASUS_ODD_FW_Changer_(Modified).exe ‎21 ‎March ‎2019 (checksum above)
HI-LG BH14NS40_N1.00-A4_patched.exe ‎3 ‎November ‎2018
CRC-32: e9604fe2
MD4: 32245b1a192ef6d7e810b842ea47a391
MD5: 8635650a95701e57157915a9dc1c46f1
SHA-1: 8482a1a5d63ede18a6e0e925a141cf0447551679

Windows 10 1903 AHCI (32&64bit)
MK ASUS-BW-16D1HT-3.10-WM01601-211901041014
ASUS_ODD_FW_Changer_(Modified).exe ‎24 ‎August ‎2019 (checksum above)
ASUS_ODD_FW_Changer_(Modified).exe ‎21 ‎March ‎2019 (checksum above)
HI-LG BH14NS40_N1.00-A4_patched.exe ‎3 ‎November ‎2018 (checksum above)

I am still suck on original 3.11

Will UHD blu rays work with AnyDVD HD + MakeMKV with this original FW?

[Billycar11]

I am still suck on original 3.11

Will UHD blu rays work with AnyDVD HD + MakeMKV with this original FW?

that's quite weird does the drive still work? i have only seen 1 guy with the same problem and his drive was defective and could not read any disks or he killed it idk
but im pretty sure 3.11 won't work with makemkv or anydvd

[diffus1on]

I am still suck on original 3.11

Will UHD blu rays work with AnyDVD HD + MakeMKV with this original FW?

that's quite weird does the drive still work? i have only seen 1 guy with the same problem and his drive was defective and could not read any disks or he killed it idk
but im pretty sure 3.11 won't work with makemkv or anydvd

Drive works perfectly, I can rip single and dual layer regular blu ray's just fine at 25MB/s 6.2x.

So I guess the next option would be taking the drive apart and trying to get data off the SPI bus, although judging by the security so far that is likely to be a dead end.