|
Portal Board index » .:: Firmware Flashing ::. » DVD-RW/+RW/RAM Firmware
All times are UTC [ DST ]
|
| Author |
Message |
|
|
 Posted: Wed Jun 16, 2010 7:40 pm |
|
Joined: Wed Jun 16, 2010 7:31 pm
Posts: 2
|
|
Hello Devilsclaw,
How do I compile your Renesas Util fw flasher and dumper programs to use in Windows XP, please? I have downloaded the Borland C++ Compiler 5.5, if that is any help. If not, do you have some pre-compiled versions, please? I am not sure if it is two programs or just the one.
Thanks so much for any help.
Best regards,
Lee
|
|
| Top |
|
 |
|
|
Posted: Wed Jun 16, 2010 7:50 pm |
|
Joined: Wed Jun 16, 2010 7:06 pm
Posts: 6
|
|
Would the firmware file for this drive tell us anything useful?
|
|
| Top |
|
|
|
|
Posted: Wed Jun 16, 2010 8:00 pm |
|
Joined: Wed Jun 16, 2010 7:31 pm
Posts: 2
|
|
Hello Codename_Falcon,
I do not believe the fw in my drive will tell you guys anything useful. I have the Buffalo BR-X816U2-EU blu-ray drive, bought in the UK, which is an internal LG BH10NS30, with fw EL00-06 inside at present (older than the current revision EL00-07). I wanted to have a Windows version of the Renesas Util to backup my fw inside my new blu-ray drive (the one mentioned above).
Thanks for any help.
Best regards,
Lee
|
|
| Top |
|
|
|
|
Posted: Thu Jun 17, 2010 8:20 am |
|
Joined: Fri Feb 01, 2008 1:25 pm
Posts: 1
|
|
| Top |
|
|
|
|
Posted: Wed Jun 23, 2010 3:00 pm |
|
Joined: Wed Jun 23, 2010 2:42 pm
Posts: 3
|
Hello devilsclaw and thanks from me, too, for your excellent tool. I only registered here to post my findings and problem, hopefully to assist some debugging... I did follow your exact steps: using WinXP SP3 and command/console prompt. I have bought the OEM drive GT20N ( external USB drive) from a local distributor/maker, it comes with firmware CQ01. The firmware for this GT20N drive that I found, officially, is the CW3 version so I wanted to cross-flash it. Here is the console output with the error "Failed to write at 0x00070000" but also the next attempt to re-flash the drive with its own firmware, patched with MCSE 1.2.0.7 for auto RPC-2 reset (a new .bin created): Code: D:\Devilclaw's Flasher>flasher -D
Devilsclaw's LG Renesas Drive Utility
drives_available: Cannot open device n.
drives_available: Cannot open device w.
drives_available: Cannot open device z.
AVAILABLE DRIVES AND IDs:
Drive ID: 1 Name: DVDRAM GT20N
D:\Devilclaw's Flasher>flasher -d 1 -c core_firmware.bin
Devilsclaw's LG Renesas Drive Utility
cmd_drive: Opening Drive: 1.
cmd_dumpcore: Starting dumping process
cmd_dumpcore: Dump process finished
D:\Devilclaw's Flasher>flasher -d 1 -m main_firmware.bin
Devilsclaw's LG Renesas Drive Utility
cmd_drive: Opening Drive: 1.
cmd_dumpmain: Starting dumping process
cmd_dumpmain: Dump process finished
D:\Devilclaw's Flasher>flasher -r GT20N_CW03.exe
Devilsclaw's LG Renesas Drive Utility
cmd_ripexe: Starting firmware ripping process
Firm location 0x0001B000
cmd_ripexe: Finished firmware ripping process
D:\Devilclaw's Flasher>flasher -d 1 -f MAIN_GT20N_CW03.exe.bin
Devilsclaw's LG Renesas Drive Utility
cmd_drive: Opening Drive: 1.
cmd_flashfirm: Flashing process started
firm_flasher: Drive should be flashing its light.
firm_flasher: This indicates its flashing its self.
firm_flasher: This can take a while, Please be patiant.
firm_flasher: Failed to write at 0x00070000
firm_flasher: your drive should still be fine.
cmd_flashfirm: Flashing process failed
D:\Devilclaw's Flasher>flasher -d 1 -V MAIN_GT20N_CW03.exe.bin
Devilsclaw's LG Renesas Drive Utility
cmd_drive: Opening Drive: 1.
cmd_verifyfirm: Verification process started
firm_verify: Verifying firmware
firm_verify: Verification failed
cmd_verifyfirm: Verification process failed
D:\Devilclaw's Flasher>flasher -d 1 -V main_firmware.bin
Devilsclaw's LG Renesas Drive Utility
cmd_drive: Opening Drive: 1.
cmd_verifyfirm: Verification process started
firm_verify: Verifying firmware
cmd_verifyfirm: Verification process passed
D:\Devilclaw's Flasher>flasher -d 1 -f main_firmware_speedpatched.bin
Devilsclaw's LG Renesas Drive Utility
cmd_drive: Opening Drive: 1.
cmd_flashfirm: Flashing process started
firm_flasher: Drive should be flashing its light.
firm_flasher: This indicates its flashing its self.
firm_flasher: This can take a while, Please be patiant.
cmd_flashfirm: Flashing process finished
D:\Devilclaw's Flasher>flasher -d 1 -V main_firmware_speedpatched.bin
Devilsclaw's LG Renesas Drive Utility
cmd_drive: Opening Drive: 1.
cmd_verifyfirm: Verification process started
firm_verify: Verifying firmware
firm_verify: Verification failed
cmd_verifyfirm: Verification process failed
D:\Devilclaw's Flasher>flasher -d 1 -V main_firmware.bin
Devilsclaw's LG Renesas Drive Utility
cmd_drive: Opening Drive: 1.
cmd_verifyfirm: Verification process started
firm_verify: Verifying firmware
cmd_verifyfirm: Verification process passed Sorry for this long output... I thought this forum could use the [codebox] tag to allow scroll bars... In the meantime, I did unplug/eject the drive a couple of times... Crazy, isn't it? It had an error flashing CW03, but still verified OK with original dump. Then, it says that patched original firmware was successfully flashed, then it fails verification as it seems the original firmware is still there! I apologise in advance... Care to comment, please? Is this due to the fact it's an external USB device rather than an ATAPI/SATA device on the controller? Many thanks!
|
|
| Top |
|
|
|
|
Posted: Wed Jun 23, 2010 5:47 pm |
|
| devilsclaw |
| Moderator |
 |
 |
Joined: Sat Jan 12, 2002 6:08 am
Posts: 331
|
|
You are using the tool correctly.
Did you rename the .exe.hex to .exe.bin, if so that is fine I just didn't see it in the log.
Btw each attempt of flashing the drive might require it to be turned off and back on before attempting again, this is not always true but I have seen it required by some drives.
Verify might need to be ran after you turn off and back on your drive.
|
|
| Top |
|
|
|
|
Posted: Thu Jun 24, 2010 9:11 am |
|
Joined: Wed Jun 23, 2010 2:42 pm
Posts: 3
|
Good morning devilsclaw, thanks for taking the time to reply. Indeed, I renamed the .hex file to .bin and kept the .exe. thingie just for the log above. I did remove the USB drive (eject) and plugged it in, tried a couple of times, especially to verify. No result. I still strongly believe that this drive uses the Renesas chipset, but I can't flash it! I can't even flash it with its own firmware, patched... The problem is that I bought it brand new, yesterday, at a sale (40 Euros) and never tested its performance, only after I did all that fiddling around. Could these efforts to cross-re-flash have affected its performance? Read speed maxes out at X2 whilst write speed reached X7 (via ImgBurn tool)... I might as well give up 
|
|
| Top |
|
|
|
|
Posted: Thu Jun 24, 2010 9:23 am |
|
Joined: Wed Jun 23, 2010 2:42 pm
Posts: 3
|
Well, _chef_, I did indeed had a DVD Video handy in the office and tried with DVDInfoPro to be honest. But that DVD was a studio proof disc, on a DVD-R or DVD+R without CSS. I also tried a factory DVD Video, same results. Will see if with a data DVD it will do the same... Nevertheless, thanks for the tip 
|
|
| Top |
|
|
|
|
Posted: Mon Aug 16, 2010 5:13 am |
|
Joined: Wed Aug 11, 2010 5:21 am
Posts: 12
|
Hi all, hi devilsclaw, a quick question before I take the jump. I have a LG GS23N SB03, and I am trying to install a patched firmware with autoreset patch. I downloaded the firmware here, http://files.rpc1.org/index.php?act=category&id=1823 and I patched on a Win machine with MCSE. On my mac, I ripped the firmware BINs from the patched firmware. >> ./flasher -r GS23N_SB03-00_speedpatched.exe Devilsclaw's LG Renesas Drive Utility cmd_ripexe: Starting firmware ripping process Firm location 0x0001C000 cmd_ripexe: Finished firmware ripping process I am left with CORE_GS23N_SB03-00_speedpatched.exe.hex MAIN_GS23N_SB03-00_speedpatched.exe.hex Now, do I have to flash both onto my DVD? How can I tell flasher which is MAIN and which is CORE (with a command line flag)? As far as I can tell, I should do flasher -d 1 -f CORE_GS23N_SB03-00_speedpatched.exe.hex flasher -d 1 -f MAIN_GS23N_SB03-00_speedpatched.exe.hex But how can flasher tell MAIN from CORE? Is it in the file format? And, again, are both needed? Thank you for your help! John
|
|
| Top |
|
|
|
|
Posted: Mon Aug 16, 2010 10:12 am |
|
| devilsclaw |
| Moderator |
|
|
Joined: Sat Jan 12, 2002 6:08 am
Posts: 331
|
|
The flashing process just sends the data to the drive in a special location the drive its self flashes.
each file has info in side telling the drive where and how to flash.
I would suggest flashing the main firmware then turn of system fully so that the power is off.
then flash the core if you must. then power it off the same way.
|
|
| Top |
|
|
|
|
Posted: Mon Aug 16, 2010 3:21 pm |
|
Joined: Wed Aug 11, 2010 5:21 am
Posts: 12
|
|
Thank you very much. As far as I know, the only way to tell if flashing the MAIN was enough is to see if autoreset is working. If it doesn't work, I would end up using my 5 allowed changes. Right? Is there another way to test autoreset, and see if I need the CORE as well, without burning up the 5 allowed change? DVD Info can't tell, I think.
|
|
| Top |
|
|
|
|
Posted: Mon Aug 16, 2010 3:28 pm |
|
| Puma |
| Administrator |
 |
Joined: Tue May 11, 2004 3:02 pm
Posts: 10124
Location: UK
|
john_hc09 wrote: Thank you very much. As far as I know, the only way to tell if flashing the MAIN was enough is to see if autoreset is working. If it doesn't work, I would end up using my 5 allowed changes. Right? Is there another way to test autoreset, and see if I need the CORE as well, without burning up the 5 allowed change? DVD Info can't tell, I think. what's wrong with changing once and powering down. then restart and see if the drive has reset to what is was
_________________
Read The FAQ Firmware Request Rules
MCSE Thread Utilities
|
|
| Top |
|
|
|
|
Posted: Mon Aug 16, 2010 6:47 pm |
|
| devilsclaw |
| Moderator |
|
|
Joined: Sat Jan 12, 2002 6:08 am
Posts: 331
|
|
the core wont have the patched data the main will.. the core is really used for recovery if the drive flash goes bad.
|
|
| Top |
|
|
|
|
Posted: Fri Aug 20, 2010 1:29 am |
|
Joined: Wed Aug 11, 2010 5:21 am
Posts: 12
|
Puma wrote: what's wrong with changing once and powering down. then restart and see if the drive has reset to what is was If the autoreset patch doesn't work, this would use up one of my 5 changes just for the test. Thank you guys for all the help, I think I have all the info I need. I will flash with the autoreset patch the first time I need to change, and will see if then a restart will give me a reset state. I will post the results here. Thanks again.
|
|
| Top |
|
|
|
|
Posted: Sun Aug 22, 2010 2:23 pm |
|
Joined: Sun Aug 22, 2010 2:15 pm
Posts: 5
|
Did this through Terminal yesterday and it worked perfectly after a restart. devilsclaw wrote: Here is the usage instructions for Mac OS X: Code: returns the drives name and id
./flasher -D
dumps drives firmwares
./flasher -d 1 -m main_firmware.bin
./flasher -d 1 -c core_firmware.bin
Rips the firmware files out of the windows update executable
./flasher -r GS23N_SB03-00.exe
But today my drive is region locked again, and redoing it hasn't worked.  Surely it should stay region free? Have I done something wrong/missed something?
|
|
| Top |
|
|
|
|
Posted: Sun Aug 22, 2010 6:17 pm |
|
| devilsclaw |
| Moderator |
|
|
Joined: Sat Jan 12, 2002 6:08 am
Posts: 331
|
|
none of the flashes the driver. so none of that would unlock your drive.
|
|
| Top |
|
|
|
|
Posted: Sun Aug 22, 2010 8:11 pm |
|
Joined: Sun Aug 22, 2010 2:15 pm
Posts: 5
|
devilsclaw wrote: none of the flashes the driver. so none of that would unlock your drive. Oh, ok. Which commands am I missing?
|
|
| Top |
|
|
|
|
Posted: Sun Aug 22, 2010 8:13 pm |
|
| devilsclaw |
| Moderator |
|
|
Joined: Sat Jan 12, 2002 6:08 am
Posts: 331
|
|
flasher -d [drive id] -f main_firmware.bin
|
|
| Top |
|
|
|
|
Posted: Sun Aug 22, 2010 8:18 pm |
|
Joined: Sun Aug 22, 2010 2:15 pm
Posts: 5
|
devilsclaw wrote: flasher -d [drive id] -f main_firmware.bin After the others? Is that it? If so I'll give it another go. Just done this Quote: Code: ./flasher -D
./flasher -d 1 -m main_firmware.bin
./flasher -d 1 -c core_firmware.bin
./flasher -r GS23N_SB03-00.exe
./flasher -d 1 -f main_firmware.bin
But it's still not working, I'm probably missing something really obvious, but if someone could point that out I'd be grateful.
|
|
| Top |
|
|
|
|
Posted: Sun Aug 22, 2010 8:45 pm |
|
| devilsclaw |
| Moderator |
|
|
Joined: Sat Jan 12, 2002 6:08 am
Posts: 331
|
|
i think you need to read a bit more. your flashing the firmware you dumped and not the only you patched. if you actually patched it.
|
|
| Top |
|
|
|
|
Posted: Sun Aug 22, 2010 9:12 pm |
|
Joined: Sun Aug 22, 2010 2:15 pm
Posts: 5
|
devilsclaw wrote: i think you need to read a bit more. your flashing the firmware you dumped and not the only you patched. if you actually patched it. Oh. I was just following the code in your first post. *looks for info on patching* Ok, I've downloaded the MSCE thing, and added the original file via the load button. Stuck now.
|
|
| Top |
|
|
|
|
Posted: Mon Aug 23, 2010 9:23 am |
|
Joined: Sun Aug 22, 2010 2:15 pm
Posts: 5
|
[_chef_] wrote: You should start reading the info given carefully, then following them. I've read this whole thread, it's just not that clear.
|
|
| Top |
|
|
|
