The Firmware Page

The dumped firmware...

The new firmware I have downloaded here: http://files.rpc1.org/index.php?act=category&id=1823

I checked the core files from the dumped drive and the exe and there exactly the same, which is good news. the main dumps are very similar so they should work also.

I don't know if mac's have lights that can flash on there drive when running this too but if the do, does the light ever flash when my tool says it should be ?

No, there is no light while flashing. And I think there is no light anyway...

Any more ideas??

Since I worked really hard on this and had no idea what I was doing for 5 hours, here is how I did it:
How to do this on a Mac:
Use instructions of MCSE at: viewtopic.php?f=30&t=46767
to create a different drive file (.exe) file.

Download MCSE at viewtopic.php?f=2&t=41228

In the winebottler: http://winebottler.kronenberg.org/
Select (copy only) when you install.

Use your drive found in: http://files.rpc1.org/index.php
(make sure it is the apple drive if your on a Mac)

Inside MCSE:
Hit Load... and browse to the drive downloaded from http://files.rpc1.org/index.php

Then choose what you want... I chose to autoreset RPC2.

Then what you want to do is download the Flasher: http://sourceforge.net/projects/flasher/files/

Next what I did was create a folder in my Applications called App

I then put the .exe file created by MCSE in the folder App and the Flasher in the folder App

Next I opened an application called Terminal.

(Remember that the drive I used was GSA-S10N_AP12... It might be different for you. Substitute the name of your drive for this)

I typed in terminal: cd /Applications/App

Next I ripped the .exe into .bin format by typing: ./flasher -r GSA-S10N_AP12.exe
If it rips correctly you should get (cmd_ripexe: Finished firmware ripping process) (do not type this in)

I then typed in: ./flasher -d Drive ID: 1 -m main_firmware.bin
You should get: cmd_drive: Opening Drive: Drive.

So I am not sure if you need to do the next step.

and then i typed: ./flasher -d Drive ID: 1 -c core_firmware.bin
You should get: cmd_drive: Opening Drive: Drive.

I then dumped cache by typing: ./flasher -d 1 -m main_firmware.bin
You should get cmd_dumpmain: Dump process finished but it might take a little time for the process to complete so wait.

I'm not sure if you need to do the next step.

I then dumped a different cache by typing: ./flasher -d 1 -c core_firmware.bin
You should again get cmd_dumpmain: Dump process finished but it might take a little time for the process to complete so wait.

Now don't quit your application terminal, but check in the folder App which should be in the Applications and there should be two new files called main_firmware.bin and core_firmware.bin (this should still be with the flasher, GSA-S10N_AP12.exe, CORE_GSA-S10N_AP12.exe.bin, MAIN_GSA-S10N_AP12.exe.bin)

Next you want to flash the drive with the new .bin by typing: ./flasher -d 1 -f MAIN_GSA-S10N_AP12.exe.bin
Terminal will then have a space and 3 lines underneath it... you will know it has worked if it does not say error and it says (cmd_flashfirm: Flashing process finished)

Make sure you shut down the machine completely, restarting is most of the times not enough. LG drives need the power to be cut from the drive after flashing it in order to internally re-flash themselves with the new firmware. Once you turn your machine on again your drive should work normally. - cvs said

Please confirm this is right DevilsClaw and cvs...

Thank you dabmushi for the correction!

Added the CT30N and the GA3xN series (Panasonic chipset) to the unsupported list.

To me work perfect, but i don`t understant

I made all steps.

Extract from exe
Then dump both main and core

and then i put the new firmware. but there are two files core and main.

i only update the main (1.7MB)

what i have to do with core.. .bin? i flash like main? with ... -f core_...

You don't need to flash the core if your drive is working well.

thanks cvs updated main post

i know this is a VERY stupid question, but where do i find this programm called 'terminal'? is it called like that on all computers that run windows7 (regardless of the language - mine is german)?

terminal = command prompt, command line, command window, etc

Have a look here for step by step instructions on how to dump your firmware: http://club.myce.com/f91/update-firm-wa ... ost2575762

Hello,

I'm very new to all this, but I requested a firmware here:
viewtopic.php?f=12&t=47299

Its the new LG drive slim BD drive for my PopcornHour C-200.
DiskInfo:
DISCINFO VERSION : 1.7.0 BETA.12
VENDOR : HL-DT-ST
MODEL : BDDVDRW CA21N
REVISION : AS02
VENDOR SPECIFIC : 10/03/31 7U01
LOADING MECHANISM : Tray
SERIAL NUMBER :
NUMBER VOL. LEVELS : 255
BUFFER SIZE : 2048KB
INTERFACE : ATAPI
RPC2 SCHEME : YES
STATUS : Set
USER CHANGES : 4
VENDOR CHANGES : 4
CURRENT REGION : 1

There is no firmware on LG's homepage. The drive is very new, and I think only sold OEM, so I don't know if there will ever be one.
I was hoping that I could do the RPC2 auto reset myself by using devilsclaw's tool to dump the stock firmware. However I get the following:




This leaves me with the following questions:
1. Is this because it's not a Renesas drive or maybe because it's hooked up to a USB to SATA adapter?
2. If it's because it's not Renesas are there any other tool I can use to dump the current firmware?
3. If not how do I find out if I can cross flash the drive with some other firmware?

Any input will be much appreciated.

jblaabjerg I just replied to your other thread: viewtopic.php?f=12&t=47299

All 'evidence' so far points to the fact that CA2x drives use a Panasonic chipset, which is unfortunate if you want to dump the firmware from them, since there are no tools available to do so ...

Hi. flasher -d [Drive ID] -m main_firmware.bin and flasher -d [Drive ID] -c core_firmware.bin went just fine. Next you say you need to "Flashes drive with new firmware:". Would that be the firmware I have yet to extract in the next step ("Rips the firmware files out of the windows update executable:")?

Also when you extract you get a MAIN_..bin and a CORE_...bin. I guess you should do this twice then, one for each?

Anyway I did all that, but the verification step fails with a "failed to read from drive". At the same time the drive is now dead. It shows up in info tool you throw at it, but it will not accept any discs anymore.

Any way to restore the original firmware?

You don't need to flash the core. Flashing the main firmware is enough.

Make sure you shut down the machine completely, restarting is most of the times not enough. LG drives need the power to be cut from the drive after flashing it in order to internally re-flash themselves with the new firmware. Once you turn your machine on again your drive should work normally.

Today, I have try to flash my BH12NS30 EL00 to BH10NS30 1.09 for enhance the compatible problem with my CMC BD-R DL
I have backup my org. firmware before i cross flash to BH10. But after i cross flash to BH10. I can't be able to flash back to BH12 with my org. rom again.
I already try to extact a new core&main BIN on download version updater. But the flasher still display same error. Please help!!
Here come with my two BIN(Org=BH12NS30 & BH10NS30 1.09) : http://www.hkteam.org/files/rom.rar
*Flasher is the lastest version

Honestly, who told you to perform such a stupid crossflash just because you want to use some quirky discs?

I crossflash isn't for want to use some quirky discs. It's because 12NS30 E00 does not support this discs(Totally can't burn even 1x/2x).

Don't you think the LG engineers have their reason for this?

Have you asked them about support for these discs?

I'm surprised you managed to flash your BH12NS30 with a BH10NS30 firmware in the first place! This should not have worked, because the two drives have different cores.

Since the two models have different cores, probably the only way to go back to the original firmware is to create a special crossflash-ready firmware using the method described in here: viewtopic.php?f=2&t=46780

Make sure you understand exactly what you have to do and how, and if you don't fully understand it, then better don't do it at all rather than risk bricking your drive ...

How exactly did you make this crossflash ? Did you just flash the main firmware or did you also flash the core firmware ?

BH12NS30 and BH10NS30 cores are same. Also, after i flash to BH10NS30, i already burn arround 15's CMC BD-R DL Disc without any problem. Now, i already find the way to flash back to BH12NS30 firmware. Thanks

No they are not! The drives might well be similar in hardware terms, but they both have different cores (bootcodes) as you can see below:

Firmware: BD-RE BH10NS30 1.00-A9 083010
Bootcode: BH10NS30CORE

Firmware: BD-RE BH12NS30 EL00-01 122909
Bootcode: BH12NS30CORE

If the cores would have been the same, you would have been able to use the Renesas flasher to flash back and forth between the BH10NS30 and BH12NS30 firmwares without any problem. As you've seen it yourself when you've tried to do it, that was not the case ... and the different cores are to blame for that.

I tried to use HEX editor to change the firmware heading. It totally work. All burning (CD/DVD/BD/BD-DL)without any problem.

Hi all:

Stupid question, but I want to make sure I don't mess up my drive. I have a HL-DT-ST CT10L drive and I already dumped the main and core firmware that came with it (YC07). I have the YC09 firmware from someone that dumped it off his drive (CT10L_YC09_core_fw.bin and CT10L_YC09_main_fw.bin). To update my drive to YC09, do I just use the main one and issue the command "flasher -d 1 -f CT10L_YC09_main_fw.bin"? Is the core one needed for anything and, if I need to use it also, do I issue the same command. Sorry if it sounds dumb, new to this.

Thanks

yeah you only need the main firmware file