LITEON DG-16D2S Flashing Back to Stock, Can't Hit Vendor

[dickwad]

Hi guys,

Here's my situation:

• Lite-on DG-16D2S, currently on LT+ 1.6 (I think). Flashed it about 9 months ago for the first time, from stock, and never looked back. Never updated the dash. LIVE is meaningless for me, though the console remains unbanned.

• Now, I want to update to LT+ 2 finally, so I can read xgd3 discs. I still have my ripped firmware files from before I first flashed it to 1.6. Should be easy.

• I'm running a PCI VIA 6421 card and using Jungleflasher 0.1.89 Beta 284. Drivers are uninstalled, portio64.sys driver installed and started. Drive is detected in MTK Flash 32, "Drive is Lite-On.."


And here's where I'm falling down:

When I choose Erase, it says Drive returned Invalid Status! The invalid status is 0x50. Okay, so I choose Intro / Device ID. Then it says Status 0x51, and asks if I want to resend the command. If I click yes and power cycle, it just sits there forever resending the vendor intro. I've tried it with the drive sitting normally, I've tried with the tray half open, I've stood on my head and spat out five dollar bills, but I can't get the damned thing into vendor mode.

Is it because of LT+ 1.6? Should I just do the dash update (with USB flash drive updater, because I know I shouldn't be connecting to LIVE for any reason right now!!) over top of LT+ 1.6? It'll reflash to a new stock, right? Will that make it hit vendor properly, so I can then flash LT+ 2? Or is that risky?

I didn't have any trouble hitting vendor mode back when I first flashed it... :-\

Any ideas, guys??

 

[vegaslightsss]

Power cycle the drive after you resend the intro. You should download the update and put it on a flash drive anyways for newer games. Also after you update your liteon 7000 it turns into a 0251c. You will have to spoof your keys to the lt2.0 firmware because your bin file is for a liteon 7000 and it is now a 0251c.

 

[tennisdude516]

I was in your exact same position. Make sure you're power cycling the drive correctly, as that was my problem. Once you probe the MPX01 point on the PCB, make sure you've saved the DVD key, then click MTK Flash, then Lite-On Erase, then OK, then flip the power switch on the CK3i / CK3 Pro (or whatever you're using), then it should put it into Vendor Mode. I personally was being an idiot and pushing a button instead of flipping the switch, which I learned ultimately did nothing but prove I was a complete moron :facepalm:.

After that, you should be able to select the Original Firmware for the Lite-on Drive, and write it. Then install latest dashboard update, and reflash it back to LT+ v2.0.

Good Luck!

 

[dickwad]

I have the Blaster 360, but I don't even have it connected because I thought it was only needed when dumping the key, which I thought I didn't have to do.

BUT...

After it flashes (assuming I get it to work!) to the new stock FW after the dash update, will I need to redump my key to spoof to LT+ 2.0? Like, would the dummy.bin change?

To cycle power, I was just pulling the power cable out and then back in, same as I did first time I flashed many months ago. I will try powering it through the Blaster 360, and use the power switch on there.

---------- Post added at 06:37 ---------- Previous post was at 06:34 ----------

Power cycle the drive after you resend the intro. You should download the update and put it on a flash drive anyways for newer games. Also after you update your liteon 7000 it turns into a 0251c. You will have to spoof your keys to the lt2.0 firmware because your bin file is for a liteon 7000 and it is now a 0251c.

Just to clarify, if I get past the point of this invalid status, and am finally able to write the new FW, do I need to redump my dummy.bin/DVD key after it is 0251c, or can I just spoof onto LT+ 2.0 the dummy.bin I dumped back when it was 74850c?

 

[dickwad]

Okay... so it's not a Blaster 360 that I have, it is the old Blaster CK3. I don't think this has the ability to power cycle the drive, does it?? There is a little switch labeled power, however flipping it seems only to turn the blaster itself on and off... the drive still seems to have power.

When I first flashed the drive, I power cycled by pulling the cord out and then plugging it back in. How would I power cycle the drive using the Blaster CK3?

 

[dickwad]

SOLVED

Problem was, I was hitting "Erase" under the mtk32 flash tab where it also says "Write" and "Intro/Vendor", etc.

Instead, I should have been hitting "Lite-on Erase" up near the top (with other drive-specific functions for Benq, Hitachi, etc.)

D'oh!!

Once I used Lite-on Erase, I hit 0x72 easily and was able to roll back, update via USB, and then flash to LT+ 2.0. I just used my dummy.bin from my 74850c dump, and when spoofed to LT+ 2.0, it worked fine. Was able to play burned xdg3.