• AnyStream is having some DRM issues currently, Netflix is not available in HD for the time being.
    Situations like this will always happen with AnyStream: streaming providers are continuously improving their countermeasures while we try to catch up, it's an ongoing cat-and-mouse game. Please be patient and don't flood our support or forum with requests, we are working on it 24/7 to get it resolved. Thank you.

Dumping & Downgrading firmware on UHD Friendly Devices. (OUTDATED)

Is there a way to downgrade firmware if one doesn't have a motherboard that has an option to set the SATA controller as IDE?
 
@TeddyRaspin

Thanks Teddy for all the effort you put in this thread!!!!!!
I just followed up your guide to downgrade my LG BD-RE_BH16NS55 to FW 1.02.(Windows-Version). It works great!

@ all othes who wants to have an adapted Firmware

It is not that hard to use a Hex-Editor and to do the change autonomously. I've never done that before too but the description of Teddy is idiotproof. I used the Tiny Hexer because I was not allowed to save with WINHEX. Download Tiny Hexer here: https://www.portablefreeware.com/?id=2504
After some trials I found out that it is much easyer to open both firmwares (source and destination) and to syncronize the windows. Now you mark the lines with the numbers mentioned in Teddys guide in the source firmware (dumped firmware from your drive) and copie it to the clipboard. If the windows of both firmwares are propper syncronized, the lines in the windows of the destination firmware (a copy of the according firmware taken from clean firmware) are automatically marked as well.
put the cursor to the first position of the first marked line in the window of the destination firmware and hit the Paste-Button. Now the content is transfered.
After done this with all lines mentioned in Teddys guide save the copy e.g. as test.bin. It must have the same size as as the dumped firmware, othewise it will not work to write it back to the drive.
Use this test.bin to transfer it to your drive with DosFlash32_BH16NS40.exe (in the Windows Version)
Good luck!
 
@TeddyRaspin
I just wanted to let you know that the cross flash to the Asus BW-16D1HT_302 took and is recognized by all programs. Thank you so much for your help! I'm pretty psyched to have a functional and now faster UHD drive,
 
@TeddyRaspin

Thanks Teddy for all the effort you put in this thread!!!!!!
I just followed up your guide to downgrade my LG BD-RE_BH16NS55 to FW 1.02.(Windows-Version). It works great!

@ all othes who wants to have an adapted Firmware

It is not that hard to use a Hex-Editor and to do the change autonomously. I've never done that before too but the description of Teddy is idiotproof. I used the Tiny Hexer because I was not allowed to save with WINHEX. Download Tiny Hexer here: https://www.portablefreeware.com/?id=2504
After some trials I found out that it is much easyer to open both firmwares (source and destination) and to syncronize the windows. Now you mark the lines with the numbers mentioned in Teddys guide in the source firmware (dumped firmware from your drive) and copie it to the clipboard. If the windows of both firmwares are propper syncronized, the lines in the windows of the destination firmware (a copy of the according firmware taken from clean firmware) are automatically marked as well.
put the cursor to the first position of the first marked line in the window of the destination firmware and hit the Paste-Button. Now the content is transfered.
After done this with all lines mentioned in Teddys guide save the copy e.g. as test.bin. It must have the same size as as the dumped firmware, othewise it will not work to write it back to the drive.
Use this test.bin to transfer it to your drive with DosFlash32_BH16NS40.exe (in the Windows Version)
Good luck!

Agreed - Great guide by Teddy. Never done this kind of thing before but this guide was really helpful. Thank you Teddy!!!
 
Hi Teddy,
Can you mod my LG firmware with the Asus one, thanks
 

Attachments

  • LG firmware from bass4040.zip
    1.3 MB · Views: 8
No, see post 396.

Sent from my Nexus 6P with Tapatalk
 
I downgraded my BH16NS40 with the clean firmware and ended up losing the calibration data. How do I restore this data to recover the drive, as it does not read disk and only opens the tray?
I would like to send a firmware any BH16NS40 rev. NS50 I bought in 2014 with the data calibrated for me to revert the unit.
 
The only way I can think of is someone exporting their calibration data from the EXACT same model and you then import it and reflash the drive no guarantee that will work.

There's a reason the guide says to BACKUP the existing firmware first.

Sent from my Nexus 6P with Tapatalk
 
Does anyone have a firmware of the 2014 model BH16NS40 or earlier with the calibration data? Because I lost the calibration data. This can be any version of the firmware.
 
Does anyone have a firmware of the 2014 model BH16NS40 or earlier with the calibration data? Because I lost the calibration data. This can be any version of the firmware.
I just know that member "tourist" has collected some firmwares, and he reported he could reanimate an LG drive with a dump from another unit (incl. UHD support, but with much luck!!)

Post #359 from tourist, maybe he can help you (probably low chance): https://forum.redfox.bz/threads/dumping-downgrading-firmware-on-uhd-friendly-devices.74479/page-18

@Guilherme Bravo

You're absolutely wrong mate. If you ever read the Important Note on my own guide, you would know that if you flash a dump taken from ANY other device like yours,
it will break the Drive Signature (DV value), as that signature is unique for each device.

In other words, if you are unable to recover YOUR original dump, you can throw your drive into the WC. :(

@teddy
I have to disagree - kind of.
Although chances are usually low it happens that you can make a drive functional again - even fully functional (especially if Data Sum matches, granted, i've only seen that once).
Anyhow, here in the german forum section there was one drive made functional again (except 50GB blanks recognition), and i shared another dump which made a drive fully funtional again.
So why not trying when you have nothing at all to lose ;)
 
Prinicpially only one of all the sections is the most important: At first (really at first order) dumping your original unit's firmware.

Principially at first, you can blind out (ignore) all that text sections +its sub-steps (further down), which are NOT related to dumping firmware.
In Teddys guide: first you principially have to concentrate only on one paragraph section, related to making the original unit's firmware dump:
1) "Steps for dumping firmware : (Windows Method)"
"Download the Windows 7 Live (Portable Edition) ISO from here."
"Use Rufus and select the ISO image previously downloaded and prepare the USB stick"
{...} <=Addional rest sub-steps
----
or
2) "Steps for dumping firmware : (DOS Method)"
1. Prepare an USB FreeDOS bootable stick, using Rufus (which can be downloaded here)."
{...} <=Addional rest sub-steps 2. - 10.

-
Both two dumping methods share in common:
=>1) and 2) both use Dosflash (in different versions)
a) "Prepare an USB FreeDOS bootable stick, using Rufus"
b)"Be sure to connect your ASUS/LG drive alone, as SATA Primary Master (USE SATA1 or b)SATA2 controller ports)"
c)"Enable CMS in BIOS option in order to boot from the USB stick (NOT UEFI !!!!)...
d) ...and configure SATA controller as IDE !!"
---

So I see no advantage in "Steps for dumping firmware : (Windows Method)" over "Steps for dumping firmware : (DOS Method)"

You can decide on which paragraph 1) or 2) you want to focuse. I personally found that one the easiest:
2)"Steps for dumping firmware : (DOS Method)"

There's also 3rd Dump method Devilsclaw's, but you can ignore it: "Steps for dumping firmware : (Devilsclaw's Method only for old firmwares)"
"It is important that the dumped firmware must be the DOSFLASH dump and not the Devilsclaw's one !!
"I've written "for old firmwares" because, it seems that the latest ASUS/LG firmwares, which fixes the AACS 1.0 loophole (for UHD reading), inhibit the devilsclaw's flasher and you could not be able to have a valid dump."
---
Please make a copy of the original dump on several places, HDDs or USB-sticks, because if Windows reformatted/reinstalled, or if the storage device gets broken.
---

You can regard the other text/sections in behind later, after having original dump. :)
Items may be taken down for various reasons, including by decision of the uploader or due to a violation of our Terms of Use.
got this up for the W7 download.
 
You think wrong. The flasher will detect the wrong model and simply refuse to flash. If the NS40 was the same as an NS50 it would be labelled NS50 from the start. Besides pretty sure the flasher doesn't contain calibration data. Your existing drive firmware does
 
You think wrong. The flasher will detect the wrong model and simply refuse to flash. If the NS40 was the same as an NS50 it would be labelled NS50 from the start. Besides pretty sure the flasher doesn't contain calibration data. Your existing drive firmware does

I have WH16NS40 firmware from my OG drive with calibration data that I’ve flashed to two WH14NS40 drives. I ordered the wrong drives hence the WH 14 instead of 16, but they work perfectly. Would this help @Leandro Siqueira ?
 
I'd guess: Those WH16NS40 (SVC 40) and BH16NS40 (SVC 40) are principially the same.
The "B..." could mean: plastic front in black color,
"W..."= plastic front in white color.

I'd have an BH16NS40 (SVC CODE: NS40), from August 2014. Maybe there's a way to dump its firmware with certain Dosflash version (don't know exactly which).
Will Dosflash work? If yes which one? I could try out to dump firmare with Teddy's Dosflash 1.7 and with Dosflash version 2.0.
Anyone an idea which program tool to choose if Dosflash version out there won't help ?
What about "LG unlocked flasher", patched flasher? What about Devilsclaw's flasher in this case?
As a last resort I could open the drive and try to find the EEPROM, and try to read it out with external EEPROM programmer/reader.

Would there be issues with Bus encryption on standard Blu-rays (BD-ROM,BD-R/BD-RE -SL/DL) if he flashed the firmware of my unit (or ruggercb's) on his?
Are those problems with not original DRV value just related to UHD drives? Does playing/ripping software care/make use of the drv value just with UHD-drives (at least with UHD discs) ?
 
Last edited:
Back
Top