Wierd Situation With Lite-ON Drive

[aN4rK1]

Ok So something weird happend to me today while I was flashing a brand new lite-on drive.
I got it out of the box, took off the cover and hooked it up to my pc via the a port on my motherboard. I ejected the tray, turned it off, closed the tray half way, and turned it back on. I went into JungleFlahsher. I found the drive on the right port and used my CK3 and probe to get the key, which went fine.

Now this is where the weird thing happend. I clicked on the Lite-On erase button, hit ok to the two prompts and then power-cycled the drive really quick. Everything was normal and then BAM!!! Right after it went into 0x73 status, it IMMEDIATELY sent an Outro Vendor for some reason. At that point the drive seemed like it was bricked. It would not eject, would not close, nothing.

This had never happened before. All the lite-ons ive done in the past been fine. So i tried to unbrick the drive using cofree's video, but I came across another post which told me to just connect the drive to the pc, and send another Intro vendor, and I should be able to flash it. The first time i tried it, it didnt work, but the 2nd time I tried it, it did work. I was able to flash it ok and it came back just fine.

I found this REALLY weird and I have no idea why this happend. My PC has an ASUS P5QL Pro Mother board and I just gave it a reformat yesturday. I have flashed a Sammy, and a Benq after this reformat and BEFORE this lite-on and everything was as normal. The only other thing I can think of is that I dont have a video card driver installed but I dont see how that would affect the flashing. My pc also has the VIA Sata PCI card installed, with the driver taken out and portIO installed.

I thought id just share this and maybe see if anyone has any insight into this?

[aN4rK1]

Also,
forgot to mention that I dont know if this will happen again or not. I will find out saturday since I have another lite-on coming then. Anyone with any help to fix this would be greatly appriciated.

[commando_lee]

EDIT

Wrong post

[louisM92]

commando_lee if you read what he says he doesn't need to do that, its was a different problem jungle flasher gave him, not the lite on erase problem lol. But the recovery might of worked as well so maybe your right too lol. aN4rK1 thats great you got it going again, ill try that if that ever happens to me, good job

[Shootsteel]

What happened to you is not really that uncommon...JF is notorious for that kind of thing....I am glad that all is well with that drive but if you continue flashing lite-on's with JF, expect that to happen from time to time.

[aN4rK1]

Ok I have an update.
I had two more lite-ons to mod so I went to try the same process again, and the same thing happend on the first one. It sends out a verndor outro as SOON as it hits the 0x73 status. So i did the same process as before and got it modded.

For the 2nd one, I accidently hit IntroID instead of the Liteon Unlock, i turned the drive on and off, and it went to 0x73 status with no problems.....explain that one!

[grandview]

i thought that its suppose to get a 0x72 status not a 0x73 status...but thats weird...

[aN4rK1]

My mistake. It is 0x72, I read the jungleflasher tut wrong to being with

[grandview]

did you figure it out?

[aN4rK1]

I got nothing. I need to download JF again and see or else its got to be the pc?