My First LiteOn Mod (7xxxx)

This site is best viewed in a modern browser with JavaScript enabled.

My First LiteOn Mod (7xxxx)

edsfunsite

So, after a little problem getting USB Probe drivers, I've started trying to mod this LiteOn.
My first real problem, which is where I'm at now, is that the eject button on the kit doesn't actually eject the drive. I read another forum post about switching to the retail x360 dvd power cord to fix this. I have swapped them, and it still won't eject.
Since I've already got the drive open, I figured I'd manually eject it, so that it was half open, and see what came up in JungleFlasher (v0.1.72 Beta). The USB probe comes up in JF, but after that, it says 'checking...' and then 'unavailable' for status. The name that comes up in JF is Prolific USB-to-Serial Comm Port. Its also on COM17, which seemed kinda weird to me, but whatever.
So currently, I'm stuck here. Anyone have any ideas?

edsfunsite

So, its quite possible that I was being dumb when trying to get the probe to work in JungleFlasher. Its working now, kinda weird.
I successfully dumped the key from the LiteOn. Saved the dummy.bin file.
Now, when I go to erase the firmware, I'm getting stuck here:

Sending Lite-On-Erase request to port 0x0970
..............
Drive returned Status 0x72
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name:  Unknown type
Flash Size:  n/a

I've power cycled the drive 15-20 times already, and it still gives me the same thing. I'm pretty sure it needs to get one step farther, and give me a proper Manufacturer ID, Device ID, Flash Name, and Flash Size.
It doesn't seem like these forums are too busy, so I'm not holding out for an answer. This is more just a log for someone else to hopefully get some info from.
*EDIT*
In the interest of having all the information possible, I'm doing this with a chipset other than a VIA one. I've got a Compaq mobo here that flashes the other drives perfectly every time. But, seeing as I've gotten this far, I don't think (hope that its not) the chipset is going to stop this from working.

Tutoromix

Follow the info in gray and green.
http://www.tiaowiki.com/forums/xbox-360-hardware-talk/how-to-spoof-and-flash-to-a-new-liteonbenq/

edsfunsite

So, I got a dummy.bin file dumped, and after reading some other forums and whatnot, decided to try DosFlash32. That program seemed to have little problem interacting with the drive. I opened the ixtreme firmware in JungleFlasher, safed the new spoofed firmware to disk, loaded it with DosFlash32, wrote it to the drive, and now the drive doesn't spin up or anything when I put a disk in it, when its in the Xbox.
Does this mean that I toasted the drive, and that the dummy.bin file that I saved has an incorrect key? I'm really hoping I didn't brick the 360.
I'm going to try and write the firmware again later, and hopefully it wrote wrong or something.

edsfunsite

So, I got my hands on a second 360, that unfortunately has the exact same drive. I've got to get something working here, so I'm back at it.
I've ran DVDKEY32 3 times, and compared the keys it received each time. They were all the same, and status for the key is "Good".
I've downloaded the latest LiteOn LT 1.1 firmware for the drive, so when (if?) this does work, I'll be good to go. Also of note is that I have the latest JungleFlasher as well, so that its compatible with the new firmware. JF Ver 0.1.73 Beta.
I also downloaded WinMerge and did a comparison to make sure that each of the dummy.bin files I saved were identical. They were.
---
Same as last time now, I'm getting caught up at trying to erase the LiteOn. Keeps giving me the same shit as the last drive:

Sending Lite-On-Erase request to port 0x0960
..............
Drive returned Status 0x72
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name:  Unknown type
Flash Size:  n/a

I'm following the tutorial as it says, but still, I get this shit. Huge fucking thumbs down.

edsfunsite

So, it would appear that the drive I was trying to mod was shit or something. The first time getting the key with DVDKEY32 in JF, luckily I did get the correct key, and flashed a different LiteOn drive with DosFlash32, with the first drives key, and it worked perfectly. So, long story short, I think my case was very specific and isolated, and probably won't happen to anyone like it happened to me.

TheTwo

edsfunsite wrote: So, it would appear that the drive I was trying to mod was shit or something. The first time getting the key with DVDKEY32 in JF, luckily I did get the correct key, and flashed a different LiteOn drive with DosFlash32, with the first drives key, and it worked perfectly. So, long story short, I think my case was very specific and isolated, and probably won't happen to anyone like it happened to me.

Hmm, I doubt your driver is isolated... your sure it is 7xxxx?
thanks

edsfunsite

Will wrote: Hmm, I doubt your driver is isolated... your sure it is 7xxxx?
thanks

I broke the seals myself on the drives.