Hi, I have search everywhere but there don't seem to be any support for sharing F drive as a Samba drive. This feature would be nice to have.
Samba mount to F
- Thread starter flashx
- Start date
dosflash no atapi devices present
So I believe I've bricked my LiteOn Drive. I know this has been posted everywhere but none of the forums or videos I've found have worked. A lot of sites point me here: http://robinhoodsplayground.com/forum/viewtopic.php?f=110&t=3226
Which didn't work.
I've also tried the steps here: http://www.se7ensins.com/forums/firmware-hack-tutorials/127410-unlocking-locked-up-lite-drive.html
Both sites give me the same results. When i run the command l-o-eras.exe i get a status code of ff7f. I've tried power cycling the drive with or without the pc on. I've reseated the sata cable at multiple points throughout the process with no success. I was successfully able to get my Lite_CFW.bin file and keys before this happened. The first link contained a video with almost the exact steps taken to replicate the issue. The only difference is he is using the kit for power where i'm using the 360. Also I am not using a via card. Jungleflasher no longer finds the drive. Same status code and error "Device not found". Ive even tried manually putting the tray at half open and tried all the steps with no luck.
And yes i know this is posted everywhere under the sun but none of the sites i've found worked. Does anyone have any ideas?
So I believe I've bricked my LiteOn Drive. I know this has been posted everywhere but none of the forums or videos I've found have worked. A lot of sites point me here: http://robinhoodsplayground.com/forum/viewtopic.php?f=110&t=3226
Which didn't work.
I've also tried the steps here: http://www.se7ensins.com/forums/firmware-hack-tutorials/127410-unlocking-locked-up-lite-drive.html
Both sites give me the same results. When i run the command l-o-eras.exe i get a status code of ff7f. I've tried power cycling the drive with or without the pc on. I've reseated the sata cable at multiple points throughout the process with no success. I was successfully able to get my Lite_CFW.bin file and keys before this happened. The first link contained a video with almost the exact steps taken to replicate the issue. The only difference is he is using the kit for power where i'm using the 360. Also I am not using a via card. Jungleflasher no longer finds the drive. Same status code and error "Device not found". Ive even tried manually putting the tray at half open and tried all the steps with no luck.
And yes i know this is posted everywhere under the sun but none of the sites i've found worked. Does anyone have any ideas?
Re: dosflash no atapi devices present
Try this it worked for me:
To Go into Vendor Mode
1 Start up your PC with Lite-On Drive connected
2 Power on the Lite-On drive
3 Start Jungle Flasher (Wont pick up Lite-On its fine)==Make sure you know what I/O port the drive is on
4 Go to MTK Flash 32 Tab
5 Click on the Intro/Device ID Button to power Cycle the drive
6 Click Lite-On Erase Button (Dont forget to do the QUICK POWER-ON POWER-OFF METHOD) Once done, you should get the 0x72, Now its ready to be flashed
7 Go to firmware Tool 32 tab and Load up your dummy.bin to source (it will then ask you if you want to auto load the Target Firmware) click save to file
8 Go back to MTK Flash 32 Tab and click write (your drive should now be receiving firmware)
9 Power off the Lite-On drive when flash is complete then power back on and eject then close the Lite-on drive a few times
10 Power off the Lite-On drive replace in your BOX
Hope this is helpful if you want to try, good Luck
Try this it worked for me:
To Go into Vendor Mode
1 Start up your PC with Lite-On Drive connected
2 Power on the Lite-On drive
3 Start Jungle Flasher (Wont pick up Lite-On its fine)==Make sure you know what I/O port the drive is on
4 Go to MTK Flash 32 Tab
5 Click on the Intro/Device ID Button to power Cycle the drive
6 Click Lite-On Erase Button (Dont forget to do the QUICK POWER-ON POWER-OFF METHOD) Once done, you should get the 0x72, Now its ready to be flashed
7 Go to firmware Tool 32 tab and Load up your dummy.bin to source (it will then ask you if you want to auto load the Target Firmware) click save to file
8 Go back to MTK Flash 32 Tab and click write (your drive should now be receiving firmware)
9 Power off the Lite-On drive when flash is complete then power back on and eject then close the Lite-on drive a few times
10 Power off the Lite-On drive replace in your BOX
Hope this is helpful if you want to try, good Luck
CJAndT
Junior Member
Re: dosflash no atapi devices present
it is really hard to brick a lite on because it is an erase command! next to imposable!!!!
you are doing somthing wrong!
use dosflash32
Os1r1s
it is really hard to brick a lite on because it is an erase command! next to imposable!!!!
you are doing somthing wrong!
use dosflash32
Os1r1s
CJAndT
Junior Member
CJAndT
Junior Member
Re: dosflash no atapi devices present
try the old hot swap... i did it with a bricked hitachi worked great....
1st have both drive handy
2nd load with good drive into windows wait for detection if nothing that fine too ........
3rd unlock drive and proceed to flash ... but do not flash!
4th swap out drive for fucturd one!
then proceed to flash! erase cmd!
hope this helps ...
forgot to ask what rev. is itÉ
try the old hot swap... i did it with a bricked hitachi worked great....
1st have both drive handy
2nd load with good drive into windows wait for detection if nothing that fine too ........
3rd unlock drive and proceed to flash ... but do not flash!
4th swap out drive for fucturd one!
then proceed to flash! erase cmd!
hope this helps ...
forgot to ask what rev. is itÉ
Re: dosflash no atapi devices present
Its the a0a2/83580c v1. I don't want to hot swap mainly because I don't have a spare drive and I'm not willing to get another drive. Im not ready to give up on this issue yet.
As for recognizing the device in the bios, no. But then again my bios is locked down by the oem. I never really cared to unlock it because I only use this pc for flashing 360 drives. (I have 7 pc's and none have a sata connection I can use for 360 drives except this one)
Its the a0a2/83580c v1. I don't want to hot swap mainly because I don't have a spare drive and I'm not willing to get another drive. Im not ready to give up on this issue yet.
As for recognizing the device in the bios, no. But then again my bios is locked down by the oem. I never really cared to unlock it because I only use this pc for flashing 360 drives. (I have 7 pc's and none have a sata connection I can use for 360 drives except this one)
CJAndT
Junior Member
Re: dosflash no atapi devices present
well i doubt you bricked the drive ... seems that it is erased .. and now you will have to write it .... if all fails spoof the data to another drive ...
but i doubt it is bricked .. it is just erased is all ....... jf dont read it becasue there is no inq
it is a blank drive ...
and you probed r707 to get drive key dummy.bin ??
well i doubt you bricked the drive ... seems that it is erased .. and now you will have to write it .... if all fails spoof the data to another drive ...
but i doubt it is bricked .. it is just erased is all ....... jf dont read it becasue there is no inq
it is a blank drive ...
and you probed r707 to get drive key dummy.bin ??
Re: dosflash no atapi devices present
so i read on some forum (can't find the link anymore) that dosflash 1.8 may solve my problem. I've been using 1.7 for 16 bit and 1.8 for 32 so i tried 1.8 for 16 bit back in dos and no go. still status ff7f. i'm open to more ideas? anyone?
I believe my drive to be bricked so i'm willing to try anything outside of soldering the device or getting a new one
so i read on some forum (can't find the link anymore) that dosflash 1.8 may solve my problem. I've been using 1.7 for 16 bit and 1.8 for 32 so i tried 1.8 for 16 bit back in dos and no go. still status ff7f. i'm open to more ideas? anyone?
I believe my drive to be bricked so i'm willing to try anything outside of soldering the device or getting a new one
CJAndT
Junior Member
Re: dosflash no atapi devices present
http://forums.xbox-scene.com/lofiversion/index.php/t671543.html
this post might help greatly!!
good luck!!!
http://forums.xbox-scene.com/lofiversion/index.php/t671543.html
this post might help greatly!!
good luck!!!
Re: dosflash no atapi devices present
yeah ive done the steps on that forum and it didn't work. the main difference is he is using a via card where i'm not. there are no via drivers to get in the way. plus most of the work ive been doing is in the iprep dos bootable usb. at this point im going to have to try hot swapping. the difficult part is finding another liteon to use. but while i search im still open for ideas.
yeah ive done the steps on that forum and it didn't work. the main difference is he is using a via card where i'm not. there are no via drivers to get in the way. plus most of the work ive been doing is in the iprep dos bootable usb. at this point im going to have to try hot swapping. the difficult part is finding another liteon to use. but while i search im still open for ideas.
hotdogstuff
Full Member
- Dec 10, 2003
- 90
- 0
Re: dosflash no atapi devices present
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.
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.
Re: dosflash no atapi devices present
yeah ive done the steps on that forum and it didn't work. the main difference is he is using a via card where i'm not. there are no via drivers to get in the way. plus most of the work ive been doing is in the iprep dos bootable usb. at this point im going to have to try hot swapping. the difficult part is finding another liteon to use. but while i search im still open for ideas.
yeah ive done the steps on that forum and it didn't work. the main difference is he is using a via card where i'm not. there are no via drivers to get in the way. plus most of the work ive been doing is in the iprep dos bootable usb. at this point im going to have to try hot swapping. the difficult part is finding another liteon to use. but while i search im still open for ideas.