Robin Hoods Playground

Like so many others out there, my Lite-On drive locked up during the erase process in JungleFlasher. This happened to me before as well, on another Lite-On drive, and using CoFree's recovery tutorial ( http://www.robinhoodsplayground.com/for ... 195&t=3226" onclick="window.open(this.href);return false; ) I was able to restore it.

However, this drive does not seem to want to cooperate as well as the previous one did. If I have the drive connected to my VIA PCI card, everything seems to go fine until I run dosflash for the first time. See the picture below.
It knows the drive is on the port (B000 being the main port on my card) and asks me to send the MTK. I do so, turn on my drive, and as you can see, it returns the desired status of 0x72. However, my computer now seems to lock up and no longer accepts any input from the keyboard, so I am unable to simply type "6" to continue on with the process. (I say "seems to lock up" because the little underscore at the bottom of the screen continues to blink, but no keypress from the keyboard is recognized and I am forced to reset my computer.

When attaching the drive to either one of my onboard SATA ports, the following happens:
Here once again the l-o-eras.exe process works fine and returns the correct status, so I turn off my drive using my CK3, but when I run dosflash it does not recognize the drive any more. You can see that it is at port D400 with l-o-eras, but dosflash detects nothing at that port. If I turn the drive back on before running dosflash, the drive is detected at that port, but I am not prompted to send the MTK, and when I type in the number that corrosponds to that port to continue, the computer hangs once again and I have to restart.

I also tried using the following method with iprep:

CoFree wrote:try just making a iprep boot drive
in the backup folder
make a folder named 1234567
then in that one make a 2nd named 12345
in that 2nd folder put a copy of the hacked firmware you want to flash in
make sure its named litcfw.bin
you can make that with jungle flasher open your dummy.bin
open target firmware would be your lit v1.6

then boot on the flash and just go to the flash command
flit 1234567 12345
it will try to erase it
keep your fingers crossed
if it works then just let it flash it

and got as far as the following screen:
The initial erase works fine, I then power cycle the drive, and once again the computer locks up. No inputs from the keyboard are being recognized. The same thing happens no matter which SATA port (two onboard, two on my VIA card) I use.

So, anybody out there have any ideas? I'll take anything you can think of. I've been searching around for the last few hours and trying every method I can find with no luck...

Thanks.

Try doing it with iprep or jungleflash, don't try and move the mountain if you don't have to try and go around. You have to improvise, when i do lite-ons i read with jf and make the cfw and then just write with dosflash.

Well I've still got my custom firmware from before Jungle Flasher failed during the erase, I'm just having trouble reviving my drive and getting that firmware on it...

Yes, have you tried the latest jungle flash, for me anyway it did the same thing that you are saying but with the newer version it works for me.

Yeah I would make an iPrep setup much like what you've got now and just load the cfw for the lite-on that you've got. Then just run the flit 1234567 12345 like normal. See if iPrep will do what it's programmed to do without having mess with l-o-eras.exe since you're drive has sucessfully been erased.

DrPoo wrote:So I just ran the drive through Jungle Flasher again, starting at the steps after erase, using the same process I tried many times yesterday, using one of the ports on my VIA card I tried many times yesterday, and the damn thing decided that it was finally tired of messing with me and flashed perfectly.

I was a bit worried at first because when I put the drive back in my 360 I was greeted with a lovely E65 screen, but after turning the 360 off and on again, everything is working perfectly.

So, problem mysteriously solved! Thanks for the help and suggestions, guys!

Nevermind! Now everytime I turn my 360 on I am presented with an E64 screen! Any ideas why it would work for awhile (I was able to boot up a wave 3 game and play it for a few minutes until I was satisfied that everything was working properly...) and then no longer function? Should I try reflashing it with a different version of ixtreme? (I used 1.6 for this flash)

No I would try reflashin with iXtreme 1.6, and then if that doesn't work try 1.51. But before you reflash at all you should make sure that you have the latest 1.6 version by downloading it again from Xbins. An E64 error is "No DVD drive or Faulty DVD drive".

Alright, my problem was finally solved. For real this time.

I went back and reflashed the drive with ixtreme 1.6 two more times, and each time I had the same result: when I turned on my 360 I would either be given the E64 screen, or it would boot to the dashboard but refuse to load any games. As a last resort I decided to try and flash it back with ixtreme 1.51 and now the drive is working beautifully.

Thanks again for the help.

And, just for curiosity's sake, anyone have any clue as to why 1.6 would not run properly on my drive? I was using the repack downloaded fresh from xbins so I know that's not the case...

Unless maybe something was messed up during the download, but other than that I don't know. Files get corrupted all of the time so there's no telling.

Wow... Once again I seem to have celebrated too soon... My 360 was working fine for all of last night after I flashed it with 1.51, but when I went to start it up this morning the same old situation occurred: either an e64 screen or a boot to the dashboard without being able to play anything. Could these be the symptoms of having extracted a bad key back when I first started working on the drive? I used Jungle Flasher to extract the key, which does it six times, and even ran the extract three times with Jungle Flasher giving me a total of 18 extracts of the key, and all of them were the same, so that would be pretty lame if it still managed to extract a false key... If that is the case, there is no possible way around this, right?

Since you said it was working and then just out of the blue started giving e64 again, it's not the key. Check the sata connections on the DVD drive and the motherboard and also check the cable. Also check the power cable and the power cable connector on the DVD drive and motherboard. Sounds like something is interrupting the communication between the 360 and the DVD drive.

Yeah, I agree you definately have some hardware issues you need to address, it's most definately not in your flash.