Post by: LiarInGlass on March 07, 2009, 10:30:00 PM
Now it displays No Drive Detected, and when I press Eject on my CK3, nothing happens.
I have my Key, Inquiry, Dummy, and Identify files.
I have all my files that I need but I do not know what to do now.
It seems like it will not detect the drive in JungleFlasher and I'm not sure what to do now.
No matter what I do, it displays "No Drive Detected!"
And I don't know what to do now.
I have my files that I need but I'm not sure of how to get it to be detected now. It was detected fine until I tried to erase it.
Any help would be appreciated as I've done this before and thought I had it under control.
Post by: LiarInGlass on March 07, 2009, 10:41:00 PM
Post by: jp35 on March 07, 2009, 10:57:00 PM
Post by: LiarInGlass on March 07, 2009, 11:02:00 PM
Is the drive supposed to show up in my BIOS?
It doesn't.
JungleFlasher never freezes, but even as soon as it's open and I choose the correct I/O port, it doesn't even display the drive information.
I also tried CK3 Tool and it will not show my drive.
Post by: jp35 on March 07, 2009, 11:05:00 PM
Post by: LiarInGlass on March 07, 2009, 11:08:00 PM
Is dosflash the only way to fix this?
And if so, why did this happen?
Is it because I tried to erase the firmware and it failed, so now Windows will not detect it since there is no Firmware?
I'm happy to use Dosflash to try it, but I am just wanting to make sure I did not ruin my drive.
If I have my key and inquiry files and everything else, then I should be safe right?
Post by: LiarInGlass on March 07, 2009, 11:41:00 PM
Is there any way I can get this done or direct me to an actual tutorial for dosflash?
I do not understand why my drive will not eject.
Post by: jp35 on March 07, 2009, 11:48:00 PM
Post by: LiarInGlass on March 08, 2009, 12:13:00 AM
I tried using NTFS4DOS, and it just sits on initializing my drive.
I tried making a bootable USB drive for DosFlash but it will not boot.
I do not understand why I need to use Dos if I have done this before.
Why is my drive not being detected now at all?
Post by: jp35 on March 08, 2009, 12:31:00 AM
http://forums.xbox-scene.com/index.php?showtopic=673927
Post by: LiarInGlass on March 08, 2009, 01:10:00 AM
I then used DosFlash32 to properly read the drive, and in came back correct.
I then used the Lite-CFW that I made with JungleFlasher earlier and it properly flashed.
I then tried ejecting it with my CK3 and it opened!
I tested out RE5 and it seems to be reading backups.
Haven't tested anything else, but I'm hoping it was just a mistake in connection.
Thanks for the help.
Post by: jp35 on March 08, 2009, 01:50:00 AM
Post by: LiarInGlass on March 08, 2009, 03:28:00 AM
QUOTE(jp35 @ Mar 8 2009, 04:26 AM) 
congrats as long as you have your key you can't mess up a Liteon (IMG:style_emoticons/default/beerchug.gif)
Yeah. I have two drives, both with my backup files (key inquiry dummy identify) all those on both drives, as well as a USB key with the files on it.
Just to be safe.
I really don't know what happened though.
I unplugged my dvd drive then just had my two drives and my 360 drive connected, opened DosFlash, and one of them came up with drive information, so I erased it, then wrote the new firmware. Opened up JF and it shows the Lite-On drive name and I pressed eject and it opened.
Hopefully I did it correctly.
Does it matter if when I originally made the custom firmware it asked about serial information but I never fixed it? I read that it was a issue with older flashes with older jungleflasher which is what I used prior to this flash.
Just wondering if I'm still safe even though I didn't fix that serial information error.
Post by: jp35 on March 08, 2009, 03:38:00 AM
QUOTE(LiarInGlass @ Mar 8 2009, 03:04 AM)
Yeah. I have two drives, both with my backup files (key inquiry dummy identify) all those on both drives, as well as a USB key with the files on it.
Just to be safe.
I really don't know what happened though.
I unplugged my dvd drive then just had my two drives and my 360 drive connected, opened DosFlash, and one of them came up with drive information, so I erased it, then wrote the new firmware. Opened up JF and it shows the Lite-On drive name and I pressed eject and it opened.
Hopefully I did it correctly.
Does it matter if when I originally made the custom firmware it asked about serial information but I never fixed it? I read that it was a issue with older flashes with older jungleflasher which is what I used prior to this flash.
Just wondering if I'm still safe even though I didn't fix that serial information error.
if you don't go on Live i wouldn't worry about it - someone made a program to verify the drive serial info matches floating around somewhere. Haven't heard of anyone getting banned because of this but its always good to be safe
Post by: LiarInGlass on March 08, 2009, 04:06:00 AM
It seems when I used old JF for 1.5, and now new JF for 1.51 it says some info missing, but I do not really know if that's a problem in the long run or not.
I am thinking when 1.6 is out I will use the probe and do it all over again just to be safe and the serial info should be fine then.