The Firmware Page

Weird.....
That PCB is 1 year older than the "sticker" and almost anything else from the drive?!?

A fast search brought up:
http://www.cdrlabs.com/db/tag/chipset/R ... criteria=1

YL01-06 sounds like GGW-H20.
http://files.rpc1.org/index.php?act=category&id=587
http://club.myce.com/f142/lg-ggw-h20l-s ... re-234488/

Yes, like Chef said, that's definitely a GGW-H20L drive.... Besides the chipset and the GGW-H20L firmware reference on the PCB label, the date on the same PCB label is also a dead give away ... the BH08xS20 drives were first publicly announced in December 2008, so a 2007 PCB is out of question.

If my records are correct (I tend to write these things down when I come across them ) the chipset used by the BH08xS20 family should be the Renesas R8BJ32710RFPV.

Correct, and the BH08 board looks different.

Ok thanks guys, now we got the reason why my flash failed. Its really strange that the case is different...
There is no chance to revive the drive without special tools, isnt it?
ala42 do you want this drive? I am from Germany so I can send you this drive in a parcel for constructing purpose, you just have to pay for delivery service (I think Hermes with 3,80€ should be the cheapest).

Thanks anyway for your help

I have a GGC-H20 here, so that wouldnt be much of help I think.
It's really sad (from my view) just because of the HD-DVD read ability with the GGW-H20.

Of course your main view is on a working drive, preferably as BD burner.

Regarding my WH10LS30 ,

After extracting firmware from the BH10LS30 1.00-09 executable with Flasher, I ran that .bin file through MCSE to remove the riplock - as well as RPC1 patch. Finally, I crossflashed the resulting speed hacked .bin with Flasher - reported as successful.

Upon rebooting Windows still sees the drive (now as a CD drive), but I can't eject it through the Windows explorer drive context menu, nor does the eject button on the front of the drive pop out the tray. Flasher still sees the drive and I tried flashing again using only drive speed hack (no RPC1), but after rebooting I still have the same result. The stock 1.00-09 executable still detects the drive (as COR4) and offers me the option to upgrade to stock 1.00..

I tried again by speedhacking and RPC hacking the WH10LS30 firmware (I've read that WH10LS30/BH10LS30 firmwares are the same sans a few bytes in the header for drive name - can anyone confirm?) and flashing, but I got the same result - Windows shows a CD drive.

FINALLY, I ran the official WH10LS30 flasher executable, reflashed to 1.0, rebooted. Drive works again - but doesn't this mean I'm back on stock without RPC1 hacks or speedhacks? ODDLY, Windows shows me using a BH10LS30 - despite the last flash I did being from the WH10LS30 executable. Odd or what? The heck am I missing here..?

Nope, not windows but the explorer shows that info... that little bug is known.
Go into Device Manager and you should see the true info about your drive.

Or just use a tool like Discinfo or DVDinfopro to list the capabilities of your drive.

I am going to start being a pain in butt about this since I put it in the main post of this topic recently and you just happen to the be first person that has not read it since the documenting it.

First off READ the main post again and see at the bottom that it EXPLICITLY says in some cases REBOOTING ONLY DOES NOT ALWAYS WORK. and that you need to POWER THE WHOLE SYSTEM DOWN for it to work. BTW its in RED so people CAN'T miss it.

It does not say the reason why because people don't need to understand why since all they have to do is follow the instructions since in most cased people just want thing to work and don't care why it works.

The reason why is because a while back I had to remove a specific part of the flashing process from the program so that it could program all the drives. That part would freeze the program since not all drives supported it, and that part was there so that the drive would not need powered down to finish the programming process.

So now part of the process of flashing since I don't know which drive supports that feature is to POWER DOWN the ENTIRE system and if its a external drive all you need to do is POWER DOWN the external drive.

Pardon my ignorance, I read it several times over and don't know how I missed power down the computer - late night confusion, I suppose.

Eureka, though, your suggestion worked! Thank you both for the swift replies, this community is fantastic. Thank you, devilsclaw, for making such a useful tool so simple to a noobish end user - I've never had a drive this fast, my mind is absolutely blown at the capability of this thing now. Couldn't even believe my eyes when I saw my rip speed.

Thanks again, sorry for overlooking and not being thorough!

Edit: What factors determine read/rip speed? On some discs I get 8MB/s, some 13MB/s, some I get a whopping 25MB/s. It's not possible for riplock disabled/speeds thrown back to stock upon reboot, is it (by CORE firmware, or other underlying things in volatile memory)?

Hey first time writing on these forrums,
I am region 2 but i had changd it a twice and then it usually warns me if i try to do it again that its my last time. I had reinstalled my os a few times so when i put in a region 1 dvd n it asked if i wanted to change it, it dint warn me that it was my last chance so i thought reinstalling the os reset it. It hadnt n now my region is set at 1 and every dvd i have is region 2.
I have never done the reset region n dont think i'm doing it right! ive searched it for days and tried to follow all the instructions but it still hasnt worked!
This is my drive info

HL-DT-ST DVDRW GSA-S10N:

Firmware Revision: BP10
Interconnect: ATAPI
Burn Support: Yes (Apple Shipping Drive)
Cache: 2048 KB
Reads DVD: Yes
CD-Write: -R, -RW
DVD-Write: -R, -R DL, -RW, +R, +R DL, +RW
Write Strategies: CD-TAO, CD-SAO, CD-Raw, DVD-DAO
Media: To show the available burn speeds, insert a disc and choose View > Refresh

i dowloaded MCSE with the GSA-S10N_BP10 patch thing and saved it as GSA-S10N_BP10-1_speedpatched (using wine as i have a mac) and i run the speedpatch file and nothing happens.
I also run the flasher program flasher_MacOSX_10252010_1126PM and it just shows this

Last login: Mon Feb 27 10:36:40 on ttys000
/Volumes/flasher/flasher ; exit;
gethin-joness-macbook:~ gethinjones$ /Volumes/flasher/flasher ; exit;
logout

[Process completed]

but still nothing has happened!!!!
Please can someone help me! i need clear instruction step by step for something that works!!!!

does it flash the drive at all, pretty vague nothing happens, have you fully powered down the system after the flash. If its correct then the counter should be reset, as ala did introduced a patch for this.

Never does, never will.

Ok i did exactly what this guy did and it worked!
viewtopic.php?f=30&t=46871#p229198
by Dud3z » Mon Dec 20, 2010 6:13 pm.

It didn't make it region free but it reset the counter for me to go back to Region 2 with 4 switches left!
Cheers guys!

Just read it carefully, he posted "Then choose what you want... I chose to autoreset RPC2. "

I've got a new LG WH12ls39 and I'm having a problem flashing. I can dump my firmware and do the other utilities, but a no go as far as flashing. This is the error that I get if I use the main firmware just as is, or if I modify with mediacodespeededit.

cmd_flashfirm: flashing process started.Then immediately I get this message: falloc: could not open main_firmware.bin.

Thank You Bob H.

Where is your "main_firmware.bin" ??

When using flasher you must specify the correct location.

I have a folder called flasher on my D drive, in the folder is flasher and my main_ firmware file which has been patched with mediacodespeededit.
At the D prompt I type in flasher\flasher -d 1 -f main_firmware.bin.

Thank you for the reply. Bob H.

I have the flasher folder on my D drive and inside is the flasher program along with main_firmware that is patched with speedpatched.Then renamed main_firmware

I then type in flasher\flasher -d 1 -f main_firmare.bin that is when I get the error messages that are in my first post.
I even tried to flash the dumped firmware with out patching and I get the same set of errors. I have no clue why it won't flash, when I can dump the core and main firmwares. It seems I can do all of the other tasks except flash.

Where's my 2 posts that I submitted.

You have not 10 posts yet, they have to be confirmed first because of spamming.

How should the flasher find the firmware when you use that commandline??

Got it. Moved the program flasher and the file back to the root C: drive. Typed in :
flasher -d 1 -f main_firmware_ speedpatched.bin
It started flashing the drive

Thank you for your time.
Bob H.

I have got this error yesterday when tried to upgrade my GGW-H20L from 1.05 to 1.07 with .bin firmware file.
Tried flasher's 64-bit version of 26 oct 2010.

Process closes after 4-6 seconds from start without any consequences. During this light won't flashes.
Other options like making dump firmware files or ripping .bin files from firmware work fine.


Upgrading from .exe file also works normally. Don't know what to do
If it is needed to, i can upload .bin file.

I have been running the flasher on my 64bit os, maybe I am only using the 32bit version I will have to look when I get home.

Not sure what has happened, but finally i successfully flashed drive. I presume it was problem with firmware not flasher.

Very useful tool, thanks for it.

I am writing to ask if there's anyway to add support for the LG GH22NS70 drive? I would be flashing it on Linux (Linux Mint 13 64-bit Cinnamon), my only system. There's a current RPC1 firmware available which is why I bought it but haven't found a way to flash it yet.