How to recover your Lite-on dg-16d2s drive after bad erase
Posted on May 17, 2009 by Marty
So you’ve successfully extracted the 3 .bin files from your Lite-On drive and created your hacked firmware (Lite_CFW.bin)
Assuming you have done that and have now erased your Lite-On using Jungle Flasher and the drive is no longer recognized in Windows and the drive wont eject.
Oh No Don’t Panic! Never fear this guide is written to help you through this.
1) Make a note of your SATA port you used to read your drive keys (In this example I will use A900)
2) Create a clean bootable USB drive using http://www.abgx.net/tools/Makeboot.rar
3) Copy the DOS folder from the ixtreme_1.5 package onto the USB drive
4) Copy your Lite_CFW.bin into the DOS folder
5) Turn the power of the Lite-On drive off
6) Boot your USB drive to DOS
7) Turn the power to the Lite-On drive on
8) Type CD DOS
9) Type l-o-eras EC00 (replace EC00 with your SATA port address). You should see status FF80
10) TYpe l-o-eras EC00 (again replace EC00 with your SATA port address).
11) You should see status FF72. If not, repeat the command a few times.12) Type DOSFLASH If you are prompted to resend MTK to Vendor, press No
13) Select the number that represents your SATA port (It should have a item under it called “No Identify Possible”)
14) Press W. You may see a message saying “Unknown flash chip”, Don’t worry this is normal
15) Type DOSFLASH If you are prompted to resent MTK to Vendor, press No
16) Select the number that represents your SATA port (It should have a item under it called “No Identify Possible”)
17) Press W. You should be prompted to enter a filename
18) Type Lite_CFW.bin and press Enter
19) The drive should say “Erasing…..” followed by “Writing Bank 0….1….2….”
So there you have it, you cannot brick a Lite-On drive (as long as you have your 3 .bin files safe)
Comments (5)
Hi, I’m at step #3. I can’t find any DOS folder in either the 1.6 or 1.51. There is however one packaged with the Makeboot.rar that you linked to. Is that what you’re talking about?
I just want to thank you for this. I stumbled upon this the last time I was having this problem with a Lite-on, and it resolved it exactly as you described. I now use this process to flash Lite-ons whenever I run across one. You don’t need to use the original firmware by the way, as long as you’ve built the modified firmware with the 3 extracted files, you can flash with that, and it works great.
hi, i have the 3 files and have done everything you explained in an attempt to boot to dos and salvage my bad erase but i cant even get my pc to boot into dos. i have tried to repair from cmd within windows and all i get is status ffff then a whole heap of freezing up.
Hi, just wana say “Thanks” for the help. Much appreciated.
For anybody who has problems, you might try, in addition to the above, the following:
A) Use the “half open tray” method before you start your PC. (Im using the xbox to power the drive)
B) Use ..\Dosflash16\DosFlash.exe version 1.8 Build 20090808 instead of the the older version
C) Use l-o-eras first. In my case, I got an error, then rebooted, still with the tray half-open, then ran dosflash.exe, got an error, then manually closed the tray and pressed the “eject” button. Tray stays closed. Then ran Dosflash with “R” and it successfuly read, with errors! I ignored the errors. Ran again, used “E”, worked. Then ran with “W” and it wrote all 4 banks with “OK” message for all banks.
Prior to this, my firmware was Liteon 1.5. Thus, backup of HAWX and Batman Arkham Asylum didnt work. After the update, both games worked fine, confirming that the firmware is updated. :-)
NOTE!!! You “MUST” use jungleflasher 0.1.70, in conjunction with the jungleflasher.pdf (v0.1.3.3b) to create your custom firmware LITE_CFW.BIN file. I had to manually create serial data, as described in the pdf.
Some additional info: PC has nForce 3 chipset (no VIA). Liteon drive is 74850C. Also, XP kept freezing up during boot, during jungleflasher, but eventully I was able to create the LITE_CFW.BIN. So, keep on trying.
Hope the above helps anyone coming across this.
Thanks buddy. First method worked fine on 64-bit Windows 7 with Intel SATA controller (Gigabyte board) just using the power from the console, no CK stuff.