|
bricked liteon drive. l-o-eras status code ff7f
|
|
|
raim1312
Newbie
|
8. February 2010 @ 12:19 |
Link to this message
|
So I found this forum here: http://forums.afterdawn.com/thread_view.cfm/762847
Since I'm a new user I can't post there because I'm a new user but I'm having a very similar issue but the resolution on that forum did not work for me.
After dumping my key and such in jungleflasher and creating my customer firmware I tried using the liteon erase. Which shortly there after my pc froze and the process failed. Jungleflasher will no longer show my drive. Also when I connect the drive the pc freezes but after waiting awhile it becomes usable again but I still cannot find the drive in jungleflasher or dosflash32.
I created a dos disk with iprep and tried using l-o-eras or dosflash on the port. l-o-eras fails with error code ff7f and dosflash states no atapi devices present. I tried forcing dosflash to flash to that port but it just hangs at status 0x7f or ff7f.
I've rebooted the drive with no luck. I've also tried using the steps from the video listed on robinhood forums which is linked in the forum I linked to with same results. I believe the drive is bricked but I'm looking for a second opinion or ideas to help flash the drive.
|
|
Advertisement
|
 |
|
|
|
4g63evo
Suspended due to non-functional email address
|
8. February 2010 @ 16:33 |
Link to this message
|
dont forget to disable your via driver
if you have the key then you are fine
to get your drive(dvd rom) to detec ...put it in vendor mode.
this happened to me before and what i did was
half try method and then click " lite on erase " in Fj
good luck to you man
Bruce lee invented Vtec. Chuck Noris uses Ivtec
|
|
raim1312
Newbie
|
8. February 2010 @ 17:00 |
Link to this message
|
I have no via drivers at all. I'm not using a via card and its a fresh install of XP. I also triple checked device manager just to be sure. I can't put the drive back into vendor mode because JF doesn't find it. If I could get it back in vendor mode then I could use l-o-erase and dosflash to get the custom firm i made onto it. Thats where my problem lies. The pc froze during the liteon erase which means there is no fw on it but I believe its not in vendor mode anymore. If thats even possible
|
|
coorva
Suspended due to non-functional email address
|
9. February 2010 @ 01:24 |
Link to this message
|
ok pc is on,,your xbox is on,,drive is plugged into your pc board or your via card,,start jungleflasher,,go to mtk flash,yes your drive does not show,,dont worry its there,,click vendor intro,,click yes again,,then do the one second power cycle on the drive,,do this twice and your drive should show up in vendor mode,,
|
Member
|
9. February 2010 @ 01:57 |
Link to this message
|
|
I know I had trouble getting a few lite-ons to properly erase. I did finally use l-o-eras and ran the erase command at least a dozen times (randomly turning the drive on and off) and finally the erase went through successfully and I was able to write the new key to the drive. There is something quirky about the lite-ons and getting erase properly, if they don't erase right just keep trying with l-o-erase and it should work!
|
|
raim1312
Newbie
|
9. February 2010 @ 07:46 |
Link to this message
|
|
adambar: I've tried using l-o-eras over a dozen times with multiple power cycles at different stages with no luck.
coorva: Some recommended the drive into with JF but to not power cycle during it. I'm at work now so I can't try what you recommended but I'll give it a go when I get home and let you know the results.
|
Member
|
9. February 2010 @ 19:40 |
Link to this message
|
That's strange because regardless of what firmware may or may not be on the drive it should still give you a successful erase eventually. I'm stumped.
|
|
raim1312
Newbie
|
9. February 2010 @ 19:46 |
Link to this message
|
|
thats what i've been told but i've tried multiple methods for liteon erase that all failed with the same status code. at this point its safe to say that method will not work with my drive. i've heard about a hot swap method which i'm curious to try now. a fellow modder i know has a liteon in the same state as mine and a virgin liteon. i'm going to give the hot swap a try once i can get together with him (hopefully by the weekend weather pending). i'll update here if the hotswap method works.
i just tried the power cycle drive intro method that was posted by coorva with the same error. the drive intro just hangs and eventually fails with a generic "drive intro failed" error message.
|
Senior Member
|
9. February 2010 @ 19:53 |
Link to this message
|
try dosflash,
when i did my 1st lite on i my pc did the same,i reconnected the drive back,remembered which port the sata was connected to and i reloaded my dummy bin and firmware then went to lite on erase follow the commands and liteon was brought back from the dead
|
|
raim1312
Newbie
|
9. February 2010 @ 19:55 |
Link to this message
|
|
ive tried dosflash. multiple versions in multiple architectures with the same error. the drive isn't initializing the port so dosflash doesn't see anything connected. i've even tried forcing dosflash to write to the drive and it still fails with status code 0x7f
|
Senior Member
|
9. February 2010 @ 20:09 |
Link to this message
|
|
ok go back to jungleflasher]
reconnect the drive,and press the lite on erase follow the directions that should bring up the status
|
|
raim1312
Newbie
|
9. February 2010 @ 20:19 |
Link to this message
|
jungleflasher does not detect the drive anymore so liteon erase won't even start. when i run liteon erase from the iprep dos stick i made it throws status code ff7f.
I just tried running liteon erase in jungleflasher. It gave me several warnings about firmware missing and no drive detected. i told it to do it anyway. i threw a status of 0x7f then went to drive intro. drive intro failed shortly after with a generic error message.
|
Senior Member
|
9. February 2010 @ 20:23 |
Link to this message
|
ok you almost got it,
load your dummy bin
and the firmware you want
go back to lite on erase press yes
2nd window will tell you yes to turn off the drive and power back on,see if that status will go,thats the way i keep doing it to work
|
|
raim1312
Newbie
|
9. February 2010 @ 20:31 |
Link to this message
|
|
i loaded the dummy.bin and my custom fw and tried it again. same status code and drive intro. tried it about 5 more times with same error. its giving me the same error that dosflash and liteon erase in dos gave. status code 0x7f or ff7f. ive previously tried this for hours without any status code change.
|
Member
|
9. February 2010 @ 20:37 |
Link to this message
|
are you on the correct port in jungle flasher?
are you using a connectivity kit or powering with the xbox?
the same thing happened to me just keep trying it you will get it.
no need to hot swap there is nothing wrong with your drive.
in jungleflasher try clicking on read let it go through the motions then afterwards click on device intro id it should ask you to power the drive after that you should get vendor mode up.
if you are using the ck3 kit the blue mode light should be on not red.
thats all i can think of.
your drive is not bricked so just keep trying you will get it.
This message has been edited since posting. Last time this message was edited on 9. February 2010 @ 20:42
|
|
raim1312
Newbie
|
9. February 2010 @ 20:43 |
Link to this message
|
|
yes i'm on the right port. for my pc its 20c8. same port i used to dump the keys and such. I'm using the 360 to power it but my friend who will be dropping by tomorrow has a connectivity kit and a via card so i'm going to try using those two to see if there will be any difference.
|
Member
|
9. February 2010 @ 20:49 |
Link to this message
|
you dont need the via card if your pc´s motherboard has the correct sata ports which it does seeing as youve allready got the keys from your drive.
try clicking read wait for it to read (doesnt matter if it gives you an error)
then click the device id button and power the drive.(it has to be within one second the quicker the better)
i hope this helped
it realy pissed me off when it happened to me so i know what your going through just stick with it bud.
|
Senior Member
|
9. February 2010 @ 21:24 |
Link to this message
|
thats your problem,u need a connectivity kit,i wouldnt use a xbox to power it on thats why u get that status,
|
|
raim1312
Newbie
|
10. February 2010 @ 19:18 |
Link to this message
|
okay so i found a resolution. first steps i tried that failed:
I got my hands on a via card and the ck3 kit. hooked it all up and same thing. i only tried this in the iprep drive with dosflash.
So I also got my hands on a virgin liteon and another bricked liteon in the same state as mine. The virgin was firmware 93450c and the bricked was 74850c while mine is 83850c v1. I Hooked the virgin up to the via and getting power via the 360 while my bricked drive was getting power via the kit and not hooked up via sata. With both drives powered on I powered the pc up and reached the dos prompt.
1. I ran dosflash then hit ctrl+c to not only check the port for the via card but to make sure the virgin drive was inquiring the port.
2. I unplugged the sata from the virgin into the brick making sure they both remained powered on.
3. I ran l-o-eras 1190 (my new port was 1190 yours could be different) and it returned a status of ffd1.
4. I ran l-o-eras again and voila there was the ff72.
5. Ran dosflash with the e command the powercycled my drive
6. ran dosflash with the w command and pointed to my custom firmware. done.
So for everyone who has a liteon in the same state as mine. there is a resolution. I did the same steps with the bricked 74850c and got the exact same results.
remember: having the via card or the kit didn't make a difference. the swap is what resolved it
|
|
5W34R
Newbie
|
18. February 2010 @ 18:01 |
Link to this message
|
I had all the same problems with my 9xxxx liteon non responsive, code ff80 status 0x80 ff7f 0xd2 could not get it into vendor mode with dos or jf. so i had a non responsive drive brickd as far a i was concernd because i could not get it to erase, or respond.
here is what i did i used a homade probe i made. held the probe in proper holes ran jf hit intro device id , turn ck3 on off vola instant 0x72 status.
loaded my cfw and proceded to flash, write verify ok!
hooked back up all happy fired up 360 now jus flashing green light
it was my trace repair so i went back resolderd traces, now it has lt fw and works flawless.
this was all from the new 9xxxx series liteon.
I never got it to erase but now i can get an instant 0x72 with out a problem.
it took me 6 hrs to finally figure it all out ,on a last hope ov faith and it workd!
Xx_5W3412_xX
|
|
qwert99
Senior Member
|
18. February 2010 @ 18:15 |
Link to this message
|
|
In the switch, or 'vampire' non-solder design like shown above, how many volts are you putting in to that connection on the 360?
$38 on new discs -- Check
$15 on burn after burn that showed as a DVD -- Check
$11 on new laser -- Check
$28 on new multimeter -- Check
___________________________________
Knowledge from Leerage? -- Priceless
|
|
Advertisement
|
|
|
|
5W34R
Newbie
|
19. February 2010 @ 13:33 |
Link to this message
|
here is the voltages 
and holes 
Originally posted by qwert99:
In the switch, or 'vampire' non-solder design like shown above, how many volts are you putting in to that connection on the 360?
Xx_5W3412_xX
|
