LG BH16NS55 Firmware 1.04 (and possibly other new drives)

Forum for discussions about UHD-capable dives
Billycar11
Posts: 1161
Joined: Sun Aug 24, 2014 5:49 am

Re: LG BH16NS55 Firmware 1.04 (and possibly other new drives)

Post by Billycar11 » Fri Jun 12, 2020 12:56 pm

k3nn2003 wrote:
Fri Jun 12, 2020 10:04 am
TeddyRaspin wrote:
Wed Apr 10, 2019 7:58 am
Some little steps forward :

- When you use the Asus ODD Flasher (modified) to downgrade unit, DOSFLASH still doesn't work, i.e. the MTK Vendor Intro Failed error is still present.
- In order to be able to dump the downgraded unit, you have to power off PC and boot again. In this way DOSFLASH works for me.

Another solution is :

- Downgrade your unit to an older firmware (in my case I have 2 BH16NS55 and I've flashed their original firmware 1.02).
- Reboot and boot from an USB Stick (FreeDos with Rufus).
- Use the latest Dosflash version 2.0 and type DOSFLASH. Even if it reports "MTK Vendor Intro failed", write down the SATA port (in my case 0xF0D0 and 0xF0B0).

Now write :

DOSFLASH /? and press 1 for flash commands. It will show the whole manual syntax you have to use in order to interrogate unit.

Commands are :

- W for writing, R for reading, E for erasing
- Port (F0D0 or F0B0 in my case)
- Port Type (1 For SATA)
- Master or Slave (A0 for Master, B0 for Slave)
- MTK Type (2 for 0x72)
- Flash Type (0 for normal handling or 1 is the same)
- Flash Size (20 as 20 in hex value is 32 in decimal, as MT1939/MT1959 eeprom has 32 banks)
- Flash OPCode (C7 if you're using the E command for erasing eeprom)
- Filename (required if you use the W or R command)
- Nforce fix (Put 0 for NO)

Thus, it is almost easy to write the proper manual syntax command and even if MTK Vendor Intro failed, if you downgrade unit you'll be able to do a valid dump.
This was the missing piece for me. Thanks very much. I have finally revived my Asus BW-16D1HT but with a different compatible firmware (LG BH16NS40 svc40). The info is strewn all over the net on how to low-level format your drive. I mistakenly upgraded my v1.01 to an incompatible v3.03 (despite the model being the same), it turns out that my drive was an older model not compatible with the 3.03 upgrade for newer same models. As I was in a hurry to upgrade, i didn't backup the original firmware. The firmware upgrade v3.03 was success, but the drive couldn't read any disc anymore after that.

So now, my ODD drive was useless, no thanks to asus for being stupid and naming different drives with the same model number sheesh.

These are the steps you need to take that worked for me in reviving that now useless drive.

Requirements:
- computer where bios settings for sata can be in IDE mode or AHCI mode.
- flash drive 4gb to store the dos OS (not windows) to boot from
- dosflash here --> download/file.php?id=1909
- firmware here --> https://drive.google.com/file/d/1zrqpeA ... Qtq3d/view
- rufus (i used 3.10) but i think any 2.0+ version will do

Steps:
1) make a flash bootable drive using rufus. Select Freedos as the boot OS.
2) copy dosflash into a new directory named "dosflash". copy also the firmware.bin
3) these are the commands needed to work with dosflash
a) DOSFLASH R F0D0 1 A0 2 0 20 "origFlash.bin" 0
- R is for reading the drive and saving the firmware to the specified ile "origFlash.bin"
b) DOSFLASH E F0D0 1 A0 2 0 20 C7 0
- E is for erasing the internal flash, if this is not done, error will show up saying status in not correct
c) DOSFLASH W F0D0 1 A0 2 0 20 "firmware.bin" 0
- W is for writing "firmware.bin" to the ODD drive
4) Make sure you connect the non-working drive to your motherboard's SATA ports or it will not work. to detect which HEX port your ODD drive to flash is, F0D0 is 2nd sata drive in my system. F0B0 is the 1st sata drive.
5) first reboot the machine and go into bios. set the sata mode to IDE. and set it to boot to USB drive as first option. save it and exit.
6) put in your newly made flash drive into the USB and reboot the machine. it should boot to a dos command prompt and not windows of any sort. the c:\ command prompt should show up now and go inside the subdirectory "dosflash" where dosflash.exe and firmware.bin is located.
7) at the command prompt, test if the drive port is correct by reading the ODD bios first using the R command
- c:\> DOSFLASH R F0D0 1 A0 2 0 20 "origFlash.bin" 0
8 ) it will error out if F0D0 is not the one your ODD drive is connected to. change it to F0B0 and run it again
- c:\> DOSFLASH R F0B0 1 A0 2 0 20 "origFlash.bin" 0
9) if it is successful, you can now proceed in Erasing and Writing to your "non-working" ODD drive
10) Erase command first using either F0D0 or F0B0 (whichever port was successful in your case)
- c:\> DOSFLASH E F0D0 1 A0 2 0 20 C7 0
11) Write command using either F0D0 or F0B0 (whichever port was successful in your case)
- c:\> DOSFLASH W F0D0 1 A0 2 0 20 "firmware.bin" 0
12) after successful flash, reboot the machine and go into bios again and set the SATA to use AHCI mode, then set the usb to a lower priority boot.

the firmware is BH16NS40 svc 40 1.03-A0 from a LG ODD drive. This is the one that revived my Asus BW-16D1HT drive. below link is to the original v1.01 of asus BW-16D1HT which may work for others

https://club.myce.com/uploads/short-url ... 2Pj2Yc.zip
Why would you do it that work around extra hard way you could use the gui dos flash with the how to video I made like 2 years ago

k3nn2003
Posts: 2
Joined: Fri Jun 12, 2020 7:41 am

Re: LG BH16NS55 Firmware 1.04 (and possibly other new drives)

Post by k3nn2003 » Fri Jun 12, 2020 3:59 pm

nothing worked for my old drive ;) all the gui flashers have errors like "can't read flash" or "checksum mismatch". the only one that worked for me was the low-level 16-bit dosflash in a dos OS. winpe-x86 boot flash drives would not let it run 16-bit dosflash.

can i get the link on your video? maybe i missed that. but all is well for me though :D

Billycar11
Posts: 1161
Joined: Sun Aug 24, 2014 5:49 am

Re: LG BH16NS55 Firmware 1.04 (and possibly other new drives)

Post by Billycar11 » Fri Jun 12, 2020 8:18 pm

k3nn2003 wrote:
Fri Jun 12, 2020 3:59 pm
nothing worked for my old drive ;) all the gui flashers have errors like "can't read flash" or "checksum mismatch". the only one that worked for me was the low-level 16-bit dosflash in a dos OS. winpe-x86 boot flash drives would not let it run 16-bit dosflash.

can i get the link on your video? maybe i missed that. but all is well for me though :D
https://youtu.be/eXgybNfHhcg

Post Reply