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

Converting UHD Friendly drive into UHD Real and viceversa

Status
Not open for further replies.
This was helpful to me in converting an LG BE16NU50 from firmware from Version 1.02 to Version 1.01

My largest problem was finding a motherboard that would put the SATA controllers into IDE mode.
 
Please send me a valid dump of BU40N/BU50N/BP60NB10 devices if you have one of them. It will be needed for further testing purposes.
Thanks !!!

Are you still looking for a dump from a BU50N? If so, I have one I can pass along. Also, is it possible to convert my BU50N into a "UHD-friendly" drive? This thread suggests it is, but reading through the thread with instructions seems to imply it doesn't work. Apart from anything else, I can't seem to find an appropriate firmware to cross-flash to. Any pointers would be appreciated!

Thanks!
 
@TeddyRaspin

Hi,

here I have a dump from my LG BU40N with firmware v1.02.
I would appreciate it if you could work your magic on it. :)
 

Attachments

  • BU40N.7z
    1.1 MB · Views: 24
Hi
Forgive me if I'm being stupid.
I have a couple of desktop UHD friendly drives (one of which I needed to downgrade with your instructions and it worked fine, thanks!)
I would like one in my laptop. I've never been able to fine a BU30N but can get a BU40N which is on the list in the first post.
I'm fine following the instructions - but, after dumping, what firmware file am I copying the bytes INTO in order to create a UHD friendly firmware for the BU40N that I can flash back??
Cheers
Andy
 
@andyp

I suggest you a 1.00 fw for BU40N, or if you need you can attach your original dump and I'll do the job.
 
@andyp

I suggest you a 1.00 fw for BU40N, or if you need you can attach your original dump and I'll do the job.

Thank you. I hadn't realised the 1.00 BU40N was UHD friendly. I'll have a look around for it, all I can see currently is 1.02.
 
Hi
I must say I can't find 1.00 anywhere. Grateful if you could do the necessary modifications to this dump of 1.02.
Thanks
Andy
 

Attachments

  • lg102.zip
    1.3 MB · Views: 9
It will be useless. Just tried before and BU40N is only UHD real drive. :(
 
It will be useless. Just tried before and BU40N is only UHD real drive. :(
Oh, that's frustrating. Thanks for looking.
Might be worth updating the first post as that implies BU40N and BU50N can be switched.
Can the BU50N??
Cheers
A
 
BU40N and BU50N could be switched to BU30N (which is UHD friendly), but I never found a BU30N firmware dump.

Anyway, I have to do a deeper scan. Stay tuned.
 
Hi guys,

I've found a way to properly convert a UHD Friendly drive, into a UHD real one and viceversa.
In order to do it, a proper firmware dump of your unit is needed and to do that, you can follow
my guide linked HERE!!
{...}
Required Steps :

  • A UHD Real/Friendly drive.
  • A valid dump (made with DOSFlash or devilsclaw's if supported by the tool).
  • DOSFlash modified version (which can be taken from my guide linked above) in order to erase and flash eeprom.
  • For external devices, you will have to unmount the chassis and connect drive to a sata cable and have a compatible motherboard.
  • Open the dump file and the firmware file you want to write on your drive, into the HEX Editor (I've used WinHEX).
  • Select hex range from 0x1E0000 to 0x1E84FF and copy it from the dumped firmware to the new firmware file.
  • Select now the hex range from 0x1E9000 to 0x1EBFFF from the dumped firmware to the new firmware file.
  • Select, at last, the range from 0x1F0000 to the end from the dumped firmware to the new firmware file.
  • Save all and now you will be ready to flash the new firmware on your device, using the DOSFlash modified version (DOS).

@teddy. There is a small mistake in the first hex range in this guide: 0x1E0000 to 0x1E84FF. an "F" in behind 0x1E84FF is missing: It should be "1E84FFF"
 
The hex range is right. On WinHEX that is the exact DV value range. 0x001E84FF (but first 00 are not calculated in the hex range).
 
Ah sry. You're correct. Was a careless mistake :).
-------------------

"Select hex range from 0x1E0000 to 0x1E84FF and copy it from the dumped firmware to the new firmware file."
"Select now the hex range from 0x1E9000 to 0x1EBFFF from the dumped firmware to the new firmware file."
"Select, at last, the range from 0x1F0000 to the end from the dumped firmware to the new firmware file."

Help Guide for Teddy's guide, hexediting with "dd"-command in Linux for official UHD drive to UHD-friendly-drive-conversion


(EEPROM Data Mover method is probably not an option here.
first Hex-range differs from other guide "Dumping & Downgrading firmware on UHD Friendly Devices" for normal downgrade -where the Data Mover method is related to)


Backup your original unit's firmware on multiple places!!

Things needed:
official UHD drive convertible to UHD-friendly: eg. LG WH16NS60
Clean firmware: flash_ASUS_BW-16D1HT_3.01.bin
2nd copy from your WH16NS60 original dump
Knoppix; Debian or Ubuntu: "dd" command program installed
DVD-blank disk (DVD+RW/DVD-RW/DVD+R/DVD-R)
(empty) USB flash drive (optional)

http://www.knopper.net/knoppix-mirrors/
Choose your download mirror:
(eg. v8.2 DVD ISO=>newer)
Burn the DVD-ISO to DVD eg. with ImgBurn (Burn image to disc). Then boot Knoppix from DVD.

Once in Knoppix, prepare Knoppix bootable USB flash drive (empty!!) with flash Knoppix to USB on Knoppix-Desktop (shortcut-symbol), which will make Knoppix boot much faster
.
"RUFUS" should have an option to make a bootable USB flash drive from a bootable Knoppix ISO-image.

"Prepare an {...} bootable stick, using Rufus (which can be downloaded here)".
http://rufus.akeo.ie/?locale
--
In Knoppix open Console/bash/shell/terminal
type in:
su

To find partition with your firmware files,
type in:
cat /proc/partitions:

As safety precaution mount partition/storage device, containing the "flash_ASUS_BW-16D1HT_3.01.bin" and your original unit's firmware, as read-only!!
mount -o ro /media/sdXy

(sdXy is your corresponding partition from behind /dev/"" in /cat/proc/partitions -table
containing the necessary files.)

Navigate to directory with the files,
type in ("sdb1" example location)
cd /media/sdb1/Users/Your-Username/Download

Copy "flash_ASUS_BW-16D1HT_3.01.bin" and WH16NS60_Original-Dumped-Dosflash.bin to other location,
type in (in two seperate commands:
cp -a flash_ASUS_BW-16D1HT_3.01.bin /home/knoppix
cp -a WH16NS60_Original-Dumped-Dosflash.bin /home knoppix

"/home/knoppix" = RAM-Disc (files saved there, will be lost after rebooting!!)

When finished, type in:
sync

Navigate to /home/knoppix:
cd /home/knoppix

Code:
dd  if=WH16NS60_Original-Dumped-Dosflash.bin  bs=1  skip=1966080  count=34048  of=flash_ASUS_BW-16D1HT_3.01.bin  seek=1966080  conv=notrunc

flash_ASUS_BW-16D1HT_3.01.bin =Clean firmware
---
Code:
dd  if=WH16NS60_Original-Dumped-Dosflash.bin  bs=1  skip=2002944  count=12288  of=flash_ASUS_BW-16D1HT_3.01.bin  seek=2002944  conv=notrunc
---
Code:
dd  if=WH16NS60_Original-Dumped-Dosflash.bin  bs=1  skip=2031616  of=flash_ASUS_BW-16D1HT_3.01.bin  seek=2031616  conv=notrunc
(each alone confirmed with pressing return)

Rename "flash_ASUS_BW-16D1HT_3.01.bin" to "NS60-Cv.bin", type in:
mv flash_ASUS_BW-16D1HT_3.01.bin NS60-Cv.bin

Plug in further USB pen drive with Teddy's Dosflash: (Please DO NOT unplug Knoppix-USB-drive as currently running!!)

type in:
cat /proc/partitions:

Mount your USB flash drive with Teddy's Dosflash:
mount /dev/sdRz /media/sdRz

Copy NS60-Cv.bin to the Dosflash USB flash drive, type in:
cp -a /home/knoppix/NS60-Cv.bin /media/sdRz

Then, type in:
sync

Then make sure that all potential console-windows/tabs are navigated away from the currently opened directories from mounted storage device/partition with the firmwares
type in:
cd /

Unmount the filesystems with the firmwares (NO REBOOT!!)(Exampl.):
unmount /media/sdb1
unmount /media/sdRz

-------------------------------------------------------
Explanation for values for dd-command (seek=,skip=,count=)

First Hex range: 0x1E0000 to 0x1E84FF
=>all bytes between Byte offset 0x1E84FF and Byte offset 0x1E0000
=>Byte count: difference between 0x1E84FF (including) and 0x1E0000 (including),
plus adding up one to difference (from start of 0x1E0000 till start of 0x1E84FF + last one Byte (0x1E84FF)

Convert 0x1E0000 (hexa-dec.) =>(dec.):
0x1E0000
=1 *16^5 + E *16^4 + 0 *16^3 + 0 *16^2 + 0 *16^1 + 0 *16^0
=1*16^5 + 14 *16^4 + 0 + 0 + 0 + 0
=1*(2^4)^5 +14 *(2^4)^4
=1*(2^20) + 14 *(2^16)
=1*(2^10)*2^(10) + 14 * (2^10*2^6)
=1024*1024 + 14 * (1024 *64)
=1048576 + 14 *(65536)
=1048576 + 917504
=1966080
=>0x1E0000 (hex-dec.) => 1966080 (dec.)


Convert 0x1E84FF (hexa-dec.) =>(dec.)
0x1E84FF
=1 *16^5 + E *16^4 + 8 *16^3 + 4 *16^2 + F *16^1 + F *16^0
=1 *16^5 + 14 *16^4 + 8 *16^3 + 4 *16^2 + 15 *16^1 + 15 *16^0
=16^5 + 7 *2^1 *(2^4)^4 + 2^3 *(2^4)^3 + 2^2*(2^4)^2 + 15* 16 + 15 *1
=1048576 + 7*2^17 + 2^15 + 2^10 +240 + 15
=1048576 + 7 *131072 + 32768 + 1024 + 255
=1048576 + 917504 + 32768 + 1279
=2000127(dec.)
=>0x1E84FF (hex-dec.) => 2000127(dec.)

(Byte) 2000127(dec.) - (Byte) 1966080 (dec.) = 34047 Bytes (dec.)

plus adding up one to difference (from start of 0x1E0000 till start of 0x1E84FF + last one Byte (0x1E84FF)
34047 (dec.) Bytes + 1 Byte =34048 Bytes
=>First Byte Range from hexrange (dec.) =34048 Bytes (dec.)


Code:
dd  if=WH16NS60_Original-Dumped-Dosflash.bin  bs=1  skip=1966080  count=34048  of=flash_ASUS_BW-16D1HT_3.01.bin  seek=1966080  conv=notrunc

----------------------------------------------------------

Second Hex range: 0x1E9000 to 0x1EBFFF
=>all bytes between Byte offset 0x1EBFFF and offset 0x1E9000
=>Byte count: difference between 0x1EBFFF (including) and 0x1E9000 (including),
plus adding up one to difference (from start of 0x1E9000 till start of 0x1EBFFF + last one Byte (0x1EBFFF)

Convert 0x1EBFFF (hexa-dec.) =>(dec.)
0x1EBFFF
=1 *16^5 + E *16^4 + B *16^3 + F *16^2 + F *16^1 + F *16^0
=1 *16^5 + 14 *16^4 + 11 *16^3 + 15 *16^2 + 15 *16^1 + 15 *16^0
=16^5 + 14 *((2^4)^4) + 11 *((2^4)^3) + 15*((2^4)^2) + 15 *16 + 15*1
=1048576 + 14 * 2^16 + 11 *2^12 + 15 *2^8 + 240 + 15
=1048576 + 14 *65536 + 11 *4096 + 15 *256 + 255
=1048576 + 917504 + 45056 + 3840 + 255
=2015231 (dec.)
=0x1BFFF (hexa-dec.) => 2015231 (dec.)


Convert 0x1E9000 (hexa-dec.) =>(dec.)
0x1E9000
=1 *16^5 + E *16^4 + 9 *16^3 + 0 *16^2 + 0 *16^1 + 0 *16^0
=1 *16^5 + 14 *16^4 + 9 *16^3 + 0 *16^2+ 0 *16^1 + 0 *16^0
=16^5 + 14 *((2^4)^4) + 9 *(2^4)^3 + 0 + 0 + 0
=1048576 + 14 *2^16 + 9 *2^12
=1048576 + 14 *65536 + 9 *4096
=1048576 + 917504 + 36864
=2002944 (dec.)
=0x1E9000 (hex) => 2002944 (dec.)

(Byte) 2015231 (dec.) - (Byte) 2002944 (dec.) = 12287 Bytes (dec.)

plus adding up one to difference (from start of 0x1E9000 till start of 0x1EBFFF + last one Byte (0x1EBFFF)
12287 Bytes (dec.) + 1 Byte = 12288 Bytes (dec)
=>Second Byte Range from Hex Range=12288 Bytes (dec.)


Code:
dd  if=WH16NS60_Original-Dumped-Dosflash.bin  bs=1  skip=2002944  count=12288  of=flash_ASUS_BW-16D1HT_3.01.bin  seek=2002944  conv=notrunc

-------------------------------------------------------------

Third Hex range: 0x1F0000 to End of file
=>all bytes between Byte offset 0x1F0000 to including the last byte (end of file).
=>No range necessary to calculate. Just from 0x1F0000 (including) to end (including)

Convert 0x1F0000 (hexa-dec.) =>(dec.)
0x1F0000
=1 *16^5 + F *16^4 + 0 *16^3 + 0 *16^2 + 0 *16^1 + 0 *16^0
=1 *16^5 + 15 *16^4 + 0 + 0 + 0 + 0
=(2^4)^5 + 15 *((2^4)^4)
=2^10 *2^10 + 15 *2^16
=1048576 + 15 * 65536
=1048576 + 983040
=2031616 (dec.)
=0x1F0000 (hex) => 2031616 (dec.)

No Byte range necessary to calculate. Just from 0x1F0000 (including) to end (including)

Code:
dd  if=WH16NS60_Original-Dumped-Dosflash.bin  bs=1  skip=2031616  of=flash_ASUS_BW-16D1HT_3.01.bin  seek=2031616  conv=notrunc
 
Last edited:
Hello,
i need a little bit of help.
I tried the method with dosflash (windows) an winhex an the Clean BU40N 1.00 from here.
DataMover doesent works, it says incorrect firmware if i try to open the dump.
After flashing, the drive works but not with DVDFAB or DeUHD. Everytime appear : Cannot work with your UHDrive / Your drive ist not supportet.

What do i wrong?
Is a LG BU40N from February 2018 ROM Ver:1.02

Greetings!
 

Attachments

  • MyFiles.zip
    2.5 MB · Views: 9
Last edited:
Hello,
i need a little bit of help.
I tried the method with dosflash (windows) an winhex an the Clean BU40N 1.00 from here.
DataMover doesent works, it says incorrect firmware if i try to open the dump.
After flashing, the drive works but not with DVDFAB or DeUHD. Everytime appear : Cannot work with your UHDrive / Your drive ist not supportet.

What do i wrong?
Is a LG BU40N from February 2018 ROM Ver:1.02

Greetings!

The upper posts posts on this page might be worth reading:

Hi

I would like one in my laptop. I've never been able to fine a BU30N but can get a BU40N which is on the list in the first post.
{...}
Andy

@andyp

I suggest you a 1.00 fw for BU40N, or if you need you can attach your original dump and I'll do the job.

Hi
I must say I can't find 1.00 anywhere.{...}
Andy

It will be useless. Just tried before and BU40N is only UHD real drive. :(
---

@Red_User
So maybe you need a BU30N firmware, difficult to find.

In any case make sure you DON'T flash any Clean firmware into the unit, the Clean firmwares don't contain any drv drive signature.
The clean firmware must be modded, some data of the original unit's dump needs to be imported into the Clean firmware, before flashing into the unit's EEPROM with Dosflash.
The drv value is uinque (principially) to each sample unit for UHD support.

Make sure to make several backups of your original BU40N dump on multiple places!!

EEPROM data mover is probably not compatible to BU40N firmwares, but anyway no issue when you use hexeditor (when using correct offsets and ranges).


Did you use the hexrange from this guide here?
=>https://forum.redfox.bz/threads/converting-uhd-friendly-drive-into-uhd-real-and-viceversa.74544/
(The first hex range differs, the difference is marked in fat letters)
Select hex range from 0x1E0000 to 0x1E84FF and copy it from the dumped firmware to the new firmware file.
Select now the hex range from 0x1E9000 to 0x1EBFFF from the dumped firmware to the new firmware file.
Select, at last, the range from 0x1F0000 to the end from the dumped firmware to the new firmware file.

----
Or did you use this hex range from other guide?
https://forum.redfox.bz/threads/dumping-downgrading-firmware-on-uhd-friendly-devices.74479/
(The first hex range differs, the difference is marked in fat letters)
Steps for importing data from backup firmwares : (Hex Editing)
On the backup firmware (the dumped one) select hex range starting from 0x1E8000 offset to 0x1E84FF and copy it in the same range of the new firmware. (**)
Do the same as point 3. but starting now from 0x1E9000 to 0x1EBFFF
At last, copy range from 0x1F0000 to the end. (***)


Afaik the EEPROM data mover (always) uses the hexrange 0x1E8000 offset to 0x1E84FF from the latter guide. (But I didn't check this entirely, see own tests further below)
I tested with EEPROM data mover on a WH16NS60 (UHD real drive). It even accepts firmware 1.01 dump from a WH16NS60 UHD-official-drive.
(first EEPROM mover dialog is for the original firmware dump, the 2nd dialog to choose the Clean firmware to where to import into.)
--

Anyway the EEPROM data mover seems to be doing something different things with UHD real drive firmwares.

Tested both Teddys guides on just (experimeting) "mods" with EEPROM data mover from a WH16NS60 original firmware into a Asus BW-16D1HT firmware, and from WH16NS60 original dump into BH16NS55 clean firmware seperately

(of course I recopied the unmodified Clean firmware when trying both guides one by one)

The resulting file NEITHER matched to the comparison file using "dd" and hexeding range from to the first guide: https://forum.redfox.bz/threads/converting-uhd-friendly-drive-into-uhd-real-and-viceversa.74544/
NOR to "dd" using the hexrange from this guide: one https://forum.redfox.bz/threads/dumping-downgrading-firmware-on-uhd-friendly-devices.74479/
??

So I had expect the EEPROM data mover should at least (just) match to the dd-result using the hexrange from this guide:
https://forum.redfox.bz/threads/dum...ading-firmware-on-uhd-friendly-devices.74479/

just as an expriment if EEPROM data mover behaves unusual:
Result a (completely) different behavior, but can't say what it exactly is.

I double controlled, and I used the same seek=, skip= and count= parameters from a few month before stored in a text file seperately, which got same result with EEPROM data mover on a (normal BH16NS55 UHD-friendly drive) from 1.03 to 1.02 (or 1.01) downgrade.
So a bit odd??:confused:

And I rechecked everything in calculator, redone clean firmware unzipping, both guides steps etc, always with test-copies of all elements needed, or course. :)
 
Last edited:
I have an HP OEM BU40N and EEPROM data mover worked fine with my dosflash dump and the clean 1.00.
Works fine with DeUHD, but not with DVDFab.
In their UHD drive list they also mention NEC OEM Firmware version CA03 - which doesn't work as well.
Looks like they only check their server logs which drives/firmwares where used without knowing whether they are working or not.
 
I have an HP OEM BU40N and EEPROM data mover worked fine with my dosflash dump and the clean 1.00.
Works fine with DeUHD, but not with DVDFab.
{...}

And works fine with AnyDVD/CloneBD, too?
 
Status
Not open for further replies.
Back
Top