Topic: Bricked Lite-On? Read Here First Before Posting (Read 523 times)

Takashi · « **Reply #30 on:** March 10, 2009, 09:13:00 AM »

or an msdos boot thumb with dosflash, L-O-Eras, and firmtool on it.

This post has been edited by Takashi: Mar 10 2009, 04:14 PM

mOrZ · « **Reply #31 on:** March 11, 2009, 01:42:00 PM »

What if I always get code FF80 with l-o-eras and Dosflash says no acpi detected

flash360 · « **Reply #32 on:** March 13, 2009, 04:24:00 PM »

QUOTE(mOrZ @ Mar 11 2009, 08:18 PM)

What if I always get code FF80 with l-o-eras and Dosflash says no acpi detected

You probably got the wrong port in l-o-eras. If you got a spare drive there run dosflash (just type dosflash in dos) with that drive attached to find the right port number.

jmuralles · « **Reply #33 on:** March 14, 2009, 01:45:00 AM »

i HAVE THE PROBLEM THAT MY COMPUTER FREEZES WHEN I TRY TO POWER ON THE CK3PRO AND I WASN'T ABLE TO EXTRACT THE KEY, I TRIED TU USE THE L-O-ERAS BUT MY DRIVE GOT BRICKED WHAT CAN I DO?

SAMOSA · « **Reply #34 on:** March 15, 2009, 05:28:00 AM »

i bricked mine too, everytime i went into windows my pc hung when i turn chip on, so i used l-o-eras and dosflash.

i had the firmware update in less than 3 minutes from this point.

see my post here http://forums.xbox-scene.com/index.php?showtopic=679665

mOrZ · « **Reply #35 on:** March 16, 2009, 04:15:00 PM »

QUOTE(flash360 @ Mar 13 2009, 04:00 PM)

You probably got the wrong port in l-o-eras. If you got a spare drive there run dosflash (just type dosflash in dos) with that drive attached to find the right port number.

100% sure it's the right port... I think it's dead.

chewy · « **Reply #36 on:** March 30, 2009, 04:32:00 PM »

I had the same problem with pc locking up.
I also got the ff80 response on my port.
I then found a youtube tutorial showing the same and all he did was type l-o-eras.exe command a 2nd time. He then got a ff72 and flashed as normal. The same happened to mine.

hope this helps

bcfc · « **Reply #37 on:** April 08, 2009, 02:33:00 PM »

i have fried my dvd drive in xbox i know it can't be fixed but when i boot up my xbox i comes with the e65 is there anyway to skip the red ring so i can see the menu. I just want to watch movies off my xbox 360 not play games.

hardie · « **Reply #38 on:** April 13, 2009, 08:05:00 PM »

E65: DVD Drive Error.... DVD Timeout, Wrong firmware, dvd is without f/w chip, etc. This can also be caused by the tray not being fully closed on boot.

I had this 1 red light in the fourth quadrant come up with error 65 and fixed it
the persons box that i flashed was a samsung which was spoofed as a liteon of course he didnt tell me this so i flashed as a samsung thats when i got this error
all fixed though and easy to do
so all im saying is check your firmware isnt spoofed as another drive and then try to reflash with the correct firmware

xboxdawg · « **Reply #39 on:** April 16, 2009, 04:28:00 PM »

I found a pretty good video on using the l-o-eras . It really helped me.

http://video.google....391525807200902

Jungleflasher froze on me during the writing of my firmware. Then it wouldn't recognize the drive.

I wrote down the steps from the video. I didn't know you had to turn the drive off after each step. I couldn't figure out why I wasn't getting the same thing as I had found in another post about dosflash16 and l-o-eras.

I still couldn't get it to work. So I took out the via sata card and used my onboard NForce3 sata. I still had to power cycle (cut the drive off and on) the drive a few times before I finally got l-o-eras to give me a FF72 status. Once I got it to do that it was a piece of cake. You don't have to do the erase step cause when you do the write it will erase it for you (if you're using the latest dosflash, I think it's 1.7).

I was doing a friends liteon and was worried to death that I had bricked it but this worked!

If it still won't work, try turning off your PC, the liteon drive and remove the Sata cable from the drive. Then reattach the cable, reboot the PC to dos, then turn on the liteon and try l-o-eras . the first time you'll get like ff80, the next time you should get ff72. If not turn power to the drive off, then back on and try it 2 more times.

If that doesn't work try it on another PC. PC's can really be flakey. What works on one may not work on another.

By the way the guy in the video said to copy all this stuff to your USB drive. All you really need is it formatted to boot in DOS, DOSFLASH16 and associated files from that directory, L-O-ERAS.exe and your hacked firmware LITE_CFW.bin or whatever you named it.

Hope this info will help someone.

XBD

Spartiku5 · « **Reply #40 on:** April 23, 2009, 04:30:00 PM »

Bong you are a god !! i nearly cried when i thought i killed my new 2 day old arcade when the drive wouldn't respond.
Cheers again

Spartiku5 · « **Reply #41 on:** April 23, 2009, 05:08:00 PM »

sorry to post again but is it ok to use dosflash32 instead of 16, i used 32 and it seemed to work ok.

d0pe · « **Reply #42 on:** May 17, 2009, 06:39:00 AM »

Got status x072 in Jungleflasher 1.60, after Lite On Erase press but after writing verification failed.

Booted with 360 Modification Disc v1.6, kept L-O-Erase.exe and dumped dummy.bin on local harddisk.

Had to run L-O-Erase twice, power cycle in between, used firmtool, dosflash write, et voila, running 1.6 ixtreme.

/me bows down to the specialist, c4eva, the Jungle team, xbox-scene and everyone else involved.

Thank you, thank you, thank you.. I love you guys!

BlackBurN · « **Reply #43 on:** May 17, 2009, 09:20:00 AM »

guys, my lite on is now spinning too fast any discs i put in......

he cant read any disc, just start spinning them toooooo fast

someone have seen some like this ?

loki232323 · « **Reply #44 on:** May 19, 2009, 08:59:00 PM »

I flashed a stock lite-on drive using jungleflasher. Everything seemed to have worked fine. When I put in games, all I get is reading on the dashboard?

I've got all my files and as far as I can tell there is nothing missing. Where do I even start?

Author Topic: Bricked Lite-On? Read Here First Before Posting (Read 523 times)