LG BH16NS55 Firmware 1.04 (and possibly other new drives)

[TeddyRaspin]

I've tried on my BH16NS55 crossflashed to ASUS BW-16D1HT 3.10 firmware and I confirm I'm unable to dump fw
using DOSFLASH (any version). I'm trying to figure out how circumvent the "MTK Vendor Intro Failed" error but
I am at a dead point.

[SamuriHL]

Well...a new fun puzzle to play with?

Sent from my Pixel XL using Tapatalk

[TeddyRaspin]

I've found that even downgrading 3.10 to older fw, DOSFLASH always reports MTK Vendor Intro Failed error.

Can anyone confirm this please ?

[SamuriHL]

Yea that appears to be correct even with my BW-16D1HT. Once it's been kissed by 3.10 (and to be clear, mine was only ever touched by the MK 3.10 NOT the official version), dosflash is toast.

[Billycar11]

I've found that even downgrading 3.10 to older fw, DOSFLASH always reports MTK Vendor Intro Failed error.

Can anyone confirm this please ?

Yea that appears to be correct even with my BW-16D1HT. Once it's been kissed by 3.10 (and to be clear, mine was only ever touched by the MK 3.10 NOT the official version), dosflash is toast.

i can also confirm this no more dosflash and weirdly dosflash disables drive in device manager on my pc and does not re enable it thought it was bricked for a second nothing was seeing it even after a reboot but reenabled and all back to normal. also just some info about lg drives im getting in usa they are build 1/9/19 and still have 1.03 and dosflash works

[MartyMcNuts]

I believe 1.04 started in Feb. My 2 drives were dated Feb 13th 2019.

[SamuriHL]

I'd like to find a way to get dosflash support back on my Asus drive. Not super critical but I like having the option of restoring my original firmware dump which I can no longer do. Hopefully Mike or Teddy have an idea on this one.

Sent from my Pixel XL using Tapatalk

[MartyMcNuts]

I'd like to find a way to get dosflash support back on my Asus drive. Not super critical but I like having the option of restoring my original firmware dump which I can no longer do. Hopefully Mike or Teddy have an idea on this one.

Sent from my Pixel XL using Tapatalk

Can you flash it back to 3.02 then use dosflash?

[Billycar11]

I'd like to find a way to get dosflash support back on my Asus drive. Not super critical but I like having the option of restoring my original firmware dump which I can no longer do. Hopefully Mike or Teddy have an idea on this one.

Sent from my Pixel XL using Tapatalk

Can you flash it back to 3.02 then use dosflash?

nope you can go back to any fw with unlocked flashers but dosflash no work i tried today also tried on ns60 1.00 dos flash is disabled once upgraded and still disabled even when downgraded again crosflashed everything
2 ideas both probably wrong
q fuse blown like phone bootloader permanently disable flash reading
slightly changed method of dosflash reading flash

oh 1 more idea
we know certain parts of flash are untouched by official flashers maybe there is a vendor access in one of those untouched areas that this firmware writes over but others dont. im going to look at it a bit but i dont think im going to notice anything

[TeddyRaspin]

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.

[Billycar11]

- 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.

quick question on my dosflash it always said yes for nforce fix as i have nforce pc for flashing so i should put it to yes or is no correct and needed for this to work?

[TeddyRaspin]

quick question on my dosflash it always said yes for nforce fix as i have nforce pc for flashing so i should put it to yes or is no correct and needed for this to work?

You have to try it.

[SamuriHL]

Teddy, I see you said this could allow you to dump the firmware using the new dosflash. However, is it possible to erase the firmware and restore a previous dump? I'm curious if the drive could be completely restored to its factory state (I had 3.02 as the highest official flash on it) and whether that would fully restore dosflash functionality without the errors. Thoughts?

[TeddyRaspin]

@SamuriHL

Yes you can and after flashing and powering off PC, drive will be properly detected by DOSFLASH MTK Vendor Intro command.

[SamuriHL]

That's interesting then. I might give that a go and put mine back on 3.02 factory. Maybe.