Soft bricked 1st gen WH14NS40

Forum for discussions about UHD-capable dives
Post Reply
grayboardtiles
Posts: 2
Joined: Tue Jun 11, 2019 3:48 pm

Soft bricked 1st gen WH14NS40

Post by grayboardtiles » Wed Jun 12, 2019 6:14 pm

Hey everyone, I accidentally flashed a 2nd gen LG WH14NS40 SVC50 firmware with the self update tool and forgot to check if my drive was compatible, and DVDs and Blurays are no longer detected by the drive. Tried flashing an old official firmware with the same tool and got the checksum error. I found a couple threads that mentioned the only way to fix this is with the dosflash tool, Windows PE, the data mover tool, and the old official firmware WH14NS40_140326_1.03-A0_NOBJ_DE.bin. Link from the first topic link:

download/file.php?id=1817

I made a 32-bit Windows PE bootable 4 gb usb with the Aomei tool and tried booting it just to see if it worked, but only my installed Windows 10 started. I haven't tried booting it with my SATA ports set to IDE, would that be why?

Also, does it matter what incorrect firmware my drive is currently using? Is the vital calibration data always encoded in the current firmware if it was flashed with the self update tool?

Links for anyone else looking for them:

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

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

https://www.youtube.com/watch?v=eXgybNfHhcg

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

https://club.myce.com/t/dosflash-v2-0-p ... ves/399911

https://drive.google.com/file/d/1w8I-pH ... 0Pf0O/view

https://www.aomeitech.com/pe-builder.html

Instructions by SamuriHL from the first topic link for anyone else who needs them:

o) Create a WinPE boot usb stick with dosflash and WH14NS40_140326_1.03-A0_NOBJ_DE.bin and the data mover tool
o) Put the SATA port to IDE mode in the bios
o) Boot from the WinPE USB stick

The rest of this is INCREDIBLY important to not screw up so read this twice:

o) Using dosflash, extract (read) the current firmware
o) Run the data mover and move the data from the extracted firmware to the WH14NS40_140326_1.03-A0_NOBJ_DE.bin file and write out a new bin file
o) Flash the new bin file with dosflash

d00zah
Posts: 506
Joined: Mon Jun 06, 2016 8:23 pm

Re: Soft bricked 1st gen WH14NS40

Post by d00zah » Wed Jun 12, 2019 7:55 pm

grayboardtiles wrote:
Wed Jun 12, 2019 6:14 pm
I made a 32-bit Windows PE bootable 4 gb usb with the Aomei tool and tried booting it just to see if it worked, but only my installed Windows 10 started. I haven't tried booting it with my SATA ports set to IDE, would that be why?
You need to set the order of boot devices in the BIOS such that it tries USB before HDD.

Mine is typically set to try USB, then ODD (install DVD/BD), then HDD (installed OS). This covers MOST circumstances.

SamuriHL
Posts: 937
Joined: Mon Jun 14, 2010 5:32 pm

Re: Soft bricked 1st gen WH14NS40

Post by SamuriHL » Wed Jun 12, 2019 10:25 pm

And if you flashed it with the wrong firmware using a Windows flasher, then the calibration and encryption data should be in tact.

grayboardtiles
Posts: 2
Joined: Tue Jun 11, 2019 3:48 pm

Re: Soft bricked 1st gen WH14NS40

Post by grayboardtiles » Fri Jun 14, 2019 8:18 pm

It worked, my drive can now read blurays and dvds again! Turns out my Gigabyte motherboard had Legacy USB support turned off which was preventing the BIOS mode 32-bit windows PE USB drive from starting up. I enabled it in the BIOS by holding down the delete key during system startup, going to classic setup from the home menu, going to the peripherals menu, and then enabling Legacy USB support.

I also made sure boot mode selection was configured to UEFI and Legacy under windows 8 features in the BIOS features section. I also noticed that windows didn't boot by default unless I booted it directly by holding down F12 during boot. It turns out that the BIOS was trying to boot to a nonexistent USB drive even when the drive was unplugged. Replugging the USB drive and putting windows boot manager and the ssd back together as the first and second boot options in the boot order fixed that. Thank you both for your help!

Post Reply