Post by: BoNg420 on January 14, 2009, 10:15:00 AM
First off, if you plugged in your power cable in, well upside down? Smell smoke? Drive don't work anymore? Then you need to buy a new xbox and be more careful! Learn from your mistakes.
------------------------------------------------------------
Problem: JungleFlasher can't open bin files (key.bin, inquiry.bin, identify.bin, hacked.bin, dummy.bin)
Solution:
Put JungleFlasher.exe in the same directory where your bin files are, then start it again. (key, inquiry, identify, hacked.bin, dummy.bin)
==
Problem: No Com port in DVDkey32 in JungleFlasher OMGWTF? (IMG:style_emoticons/default/uhh.gif)
Solution: Just type in your com port in the box. So if you are using com port 1, you would type COM1 in the box where the drop down menu is. IMPORTANT=> you must put COM before the Port number!!!
or this might be resolved in the latest version of jungle flasher, i know my com port now shows in the latest beta.
------------------------------------------------------------
PC freezing issue:
If you were in windows and using Jungle Flasher and you have successfully got your key and created your firmware from your dummy.bin or even have got as far as getting your key, inquiry, and identify.bin files, then you should be ok, just make a dummy.bin and then make your liteon firmware!
So your pc froze? You were erasing your liteon and then when you did the power cycle, your PC froze? Well you are in luck. As long as your key, inquiry, and identify.bin files were correct, then you can save your drive. What will happen at this point is your drive will no longer eject, so you think oh no bricked drive. This can be fixed. Make sure you can boot to DOS by floppy or USB drive and have the proper files on it.
You will need L-O-Eras.exe, latest dosflash16, and your hacked firmware file. Well what you do, restart your PC with your liteon connected, but not powered on, boot to DOS. Once you get to DOS restore power to your liteon drive. Go to where your files are.
Type L-O-Eras SATAPORT <-- put in your sata port that your drive is connected too. If you don't know your sata port, you can do dosflash really fast and figure out which port has the liteon drive on it. So after you do L-O-Eras SATAPORT you should return status FF72 I believe. I haven't had to do this way for awhile so if I made a mistake on the status please PM me so I can fix this. After you do this, go type DOSFLASH, then enter the proper # for the port that has the liteon drive on it. Then type W for write. Then enter your hacked firmware file, usually lite_cfw.bin then it will erase and write the firmware to your drive. After it is done, turn the power off on your drive, then turn it back on and press eject and if it does, problem solved!
Now you have flashed your firmware to your Liteon drive, put your system back together and test a backup.
------------------------------------------------------------
Note:
Also for those who are having problems with PC freezing. Make sure your Windows is up to date. Make sure you have the latest drivers for your chipset. For example I was having problems with my onboard nforce 650i sli. I went to nvidia.com and downloaded the latest drives for the 650i sli, installed them, then installed portio32.exe and restarted. Now my PC doesnt freeze anymore when erasing a liteon and power cycling in windows. If you don't have nforce, you will have to figure out where to get your drivers from.
If I missed anything please PM me or post what I was wrong with here.
This post has been edited by BoNg420: Jan 26 2009, 02:34 PM
Post by: woody21_1 on January 14, 2009, 10:21:00 AM
'First off, if you plugged in your power cable in, well upside down? Smell smoke? Drive don't work anymore? Then you need to buy a new xbox and be more careful! Learn from your mistakes.'
that made me laugh...
anyone new to flashing should either wait till more updated and stable tools become availiable or get someone to do it for you, a small fee to get it done is better than the fee of buying a new xbox and still not being able to play backups... THINK - AM I CAPABLE OF THIS BEFORE YOU OPEN THE CONSOLE.
This post has been edited by woody21_1: Jan 14 2009, 06:24 PM
Post by: that360guy on January 14, 2009, 04:03:00 PM
Post by: ruph on January 17, 2009, 06:06:00 AM
It worked for a while but now i just cant seem to open the application at all without freezing my system.
Post by: kingpickle on January 17, 2009, 09:01:00 PM
I had a problem with JF saying my com port status was not available (instead of ready). I was stuck for a few hours trying different things. The fix for me was changing the com port number in device manager to something other than 1. Worked like a charm.
The cause of the problem turned out to be microsoft's activesync (which I use for my cell phone) hijacked the port and always kept it open.
Post by: scorpionking77 on January 17, 2009, 10:59:00 PM
Post by: ruph on January 18, 2009, 12:12:00 AM
QUOTE(scorpionking77 @ Jan 18 2009, 07:35 AM) 
For anybody out there who are having problems with pc freezing I found out that when i install the ck3 drivers after i install jungleflasher was the reason it cause my pc to lock up. Once i uninstalled the ck3 drivers my pc stop freezing on me. IF this helps anybody as well.
tried that and my pc still locks up the moment i open JF in Vista. What did was install XP on a seperate partition without installing my nforce drivers. I installed all CK3 Drivers, PIO32, VIA Drivers and now it's no longer freezing. Then just for the hell of it, I installed the latest nforce and boom, it froze. I haven't tried reading/writing with it yet so i'm not exactly sure if it's working 100%. I'll give it a shot tomorrow on my friends Lite-On
Post by: flash360 on January 18, 2009, 02:24:00 PM
Podger posted a while ago about this but for some reason it dosnt seem to have cought on
I installed the VIA_RAID_V530C which can be found here http://www.versiontr...einfo/win/70826 and the problem was sorted
No boot disk or dos or rebooting pc required, you can do the whole thing in 1 go 
Thank's again podger
Post by: Millerboy3 on January 18, 2009, 02:43:00 PM
Post by: antz1970 on January 18, 2009, 05:26:00 PM
QUOTE(flash360 @ Jan 19 2009, 12:00 AM) 
I had the freezing problems when trying to erase in jf using via 6421 and maximus extractor through usb
Podger posted a while ago about this but for some reason it dosnt seem to have cought on
I installed the VIA_RAID_V530C which can be found here http://www.versiontr...einfo/win/70826 and the problem was sorted
No boot disk or dos or rebooting pc required, you can do the whole thing in 1 go Thank's again podger
i couldnt get your link to work so heres an alternative for anyone having the same problem
http://drivers.viaar..._raid_v530c.zip
Post by: BoNg420 on January 21, 2009, 06:33:00 AM
QUOTE(Millerboy3 @ Jan 18 2009, 05:19 PM)
awesome post. should be stickied for tutorial purposes i think....
It is stickied
Post by: headonism on January 24, 2009, 07:42:00 PM
i put it back together again the tried to read my back up i have and i got the message
PLEASE INSERT AND XBOX GAME INTO THIS CONSOLE
so i put the original game in same as the backup HALO 3
and got the same message.....
is there anything that i can do with this drive now
Post by: deilzfcjk on January 25, 2009, 09:00:00 PM
Post by: headonism on January 26, 2009, 03:49:00 PM
QUOTE(deilzfcjk @ Jan 26 2009, 04:36 AM)
yeah you're up shitcreek without a paddle. Better luck next time.
didnt need a paddle just my wit and inginueity < (i think it is spelt like that)
problem solved after many hours of hard graft and help from many other people on this forum
!!!!THANKS GUYS N GALS YOU KNOW WHO U ARE!!!!
Post by: Zan3 on January 27, 2009, 03:11:00 AM
QUOTE(flash360 @ Jan 18 2009, 11:00 PM)
I had the freezing problems when trying to erase in jf using via 6421 and maximus extractor through usb
Podger posted a while ago about this but for some reason it dosnt seem to have cought on
I installed the VIA_RAID_V530C which can be found here http://www.versiontr...einfo/win/70826 and the problem was sorted
No boot disk or dos or rebooting pc required, you can do the whole thing in 1 go Thank's again podger
Nice! is this working for somone with CK3 to? annyone?
Post by: deilzfcjk on January 28, 2009, 04:26:00 AM
QUOTE(headonism @ Jan 26 2009, 03:25 PM)
didnt need a paddle just my wit and inginueity < (i think it is spelt like that)
problem solved after many hours of hard graft and help from many other people on this forum
!!!!THANKS GUYS N GALS YOU KNOW WHO U ARE!!!!
What did you do to rectify?
Post by: headonism on January 28, 2009, 06:06:00 PM
thamks to all that helped me with this problem
Post by: FilthySeabass on February 02, 2009, 10:19:00 PM
Post by: brandogg on February 05, 2009, 12:20:00 AM
Post by: dalton4life on February 07, 2009, 09:35:00 PM
Post by: sw45 on February 14, 2009, 04:45:00 PM
I've tried making a dummy.bin but it doesn't work. After writing the image to the drive and putting it back in the xbox it won't read any discs. It opens and closes but won't read. I think my problem is creating the dummy.bin.
If this drive is junk is it possible to spoof another drive (ms28) since I have the key?
Thanks
Post by: sw45 on February 14, 2009, 10:11:00 PM
I read a ton more today and it seems I don't need the serial for the drive to work and my lite-on not reading discs is a key issue. I tried spoofing the lite-on to a ms28 and the ms28 works fine so it appears my key.bin is correct. What else should I try to get the lite-on to work?
Post by: flash360 on February 15, 2009, 05:47:00 PM
It is not a fourth file you need to dump
Post by: sw45 on February 18, 2009, 09:53:00 PM
Since the ms28 is working doesn't that mean the key is correct thus the lite-on flashed with the key and ixtreme should work? I'll just leave ms28 in until I have a reason to change it then worry about it but it is too bad I can't use original.
Post by: renski26 on February 20, 2009, 06:38:00 AM
Post by: DoomSayerSantos on February 24, 2009, 07:44:00 AM
QUOTE(renski26 @ Feb 20 2009, 03:14 PM)
Does the drive show in bios for anyone else? I'm having the same trouble, except my pc wasn't freezing when booting with the lite-on drive. The drive isn't recognised at all for me
I can relate bro.
I tried every guide on this and other forums.
My lite-on is still bricked.
l-o-eras , dosflash , dosflash32 , jungleflasher etc.
Nothing picks up my lite-on anymore.
If anyone got a fresh idea please give me a shout.
Post by: FuzzyTattooedBear on February 24, 2009, 04:23:00 PM
U
F
V
C
K
I
N
G
R > U L E >
Post by: fozzieb on February 25, 2009, 08:06:00 AM
i done this late at nght so i may of made mistake
I used jungle flasher and extracted the key, it created the 4 files and saved them to my pc.
i used the dummy.bin to patch the ixtreme 1.5 firmware, looked ok
I then tried to erase the drive but it crashed half way through (intel sata chipset)
I then booted to dos, tried l-o-erase but no mater what i can not get it to return correct code to say it is erased.
I tried dosflash, it sees the drive, used liteon erase, looked good
I then used tosflsh to write the liteon_cfw.bin to drive, looked ok
put drive back in xbox, turn it on and i get an E66 error, contact customer support.
Any ideas or thought on how to fix?
Cheers very much,
Steven
Post by: Racing.Ray on March 06, 2009, 08:57:00 PM
Thanks!
Post by: BoNg420 on March 10, 2009, 08:36:00 AM
QUOTE(Racing.Ray @ Mar 7 2009, 12:33 AM)
I have the VIA 6421 card that I used under DOS to successfully flash Samsung and BenQ drives. But now with a Lite-On, I have to use Windows, but I only have Vistax64 installed. How can I still get my key (without PortIO32) and hack/flash my drive?
Thanks!
You don't.
You need 32 bit windows.
Post by: Takashi on March 10, 2009, 09:13:00 AM
This post has been edited by Takashi: Mar 10 2009, 04:14 PM
Post by: mOrZ on March 11, 2009, 01:42:00 PM
Post by: flash360 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.
Post by: jmuralles on March 14, 2009, 01:45:00 AM
Post by: SAMOSA on March 15, 2009, 05:28:00 AM
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
Post by: mOrZ 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.
Post by: chewy on March 30, 2009, 04:32:00 PM
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
Post by: bcfc on April 08, 2009, 02:33:00 PM
Post by: hardie on April 13, 2009, 08:05:00 PM
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
Post by: xboxdawg on April 16, 2009, 04:28:00 PM
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
Post by: Spartiku5 on April 23, 2009, 04:30:00 PM
Cheers again
Post by: Spartiku5 on April 23, 2009, 05:08:00 PM
Post by: d0pe on May 17, 2009, 06:39:00 AM
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!
Post by: BlackBurN on May 17, 2009, 09:20:00 AM
he cant read any disc, just start spinning them toooooo fast
someone have seen some like this ?
Post by: loki232323 on May 19, 2009, 08:59:00 PM
I've got all my files and as far as I can tell there is nothing missing. Where do I even start?
Post by: Studulike on May 19, 2009, 11:27:00 PM
QUOTE(loki232323 @ May 20 2009, 02:51 AM)
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?
Ok had the same problem tonight also and worked out what it was.
You probably booted to Dos with a USB flashdisk and a common problem with them is data gets corrupt when transfering accross files. What has happened here is the "lite_cfw.bin" file has become slightly corrupt during transfer to stick and although will write to drive it does not function correctly.
Just re-copy back accross files and try flash again, I am sure all will be fine second or maybe even third time round.
One other problem people seem to be having is getting the l-o-eras.exe (port) command to return the correct code 072. You keep getting 080 because the drive bay is not quite in the correct possition (Half Way). This is of coarse based on the fact you are sure you have corred drive port entered.
Hope the above helps
Post by: loki232323 on May 20, 2009, 07:36:00 AM
I'm thinking that maybe I just got a bad flash and need to re-do it using dos instead of jungleflasher?
I also didn't have any issues with freezing or anything strange.
This post has been edited by loki232323: May 20 2009, 02:51 PM
Post by: dobosininja on May 21, 2009, 07:04:00 AM
Post by: shamus666 on May 22, 2009, 09:11:00 AM
Followed what you said and everything turned out fine.
Post by: razalom on May 23, 2009, 10:21:00 PM
Thanks heaps!
Post by: tequiller on June 02, 2009, 06:23:00 AM
Windows still detects the drive, but I always get ***BAD SERIAL DATA***
This is with a liteon in jungle flasher btw.
After successfully doing a few liteons, it seems as if the ***BAD SERIAL DATA*** is mostly due to the tray not being correctly positioned.
After using the conductor paint, all of the sudden the drive closed, and could not get it to eject again.
So I yoinked it out.
Hopefully I'm getting the ***BAD SERIAL DATA*** because I can't find the correct positioning of the drive.
Is there any way anyone can think of to get this key?
I don't care if I have to blowtorch the drive, I have plenty I can spoof it to.
Post by: Ossos on June 05, 2009, 06:29:00 PM
____________________\\________________________________________\\_________________________
Sending Lite-On-Erase request to port 0xB000
..............
Drive returned Status 0xD0
....................
Device Intro failed!
Lite-On-Erase NOT sent
____________________\\________________________________________\\_________________________
....After the "Drive returned Status 0xD0" and during the dots (like indicated in the JF tutorial) i quickly unplugged and plugged the power jack from the dvd drive. After that the "Device Intro failed!" appeared. I sure as hell didn´t plug it upside down though. Now JF won´t recognize the drive...and it seems dead. Have i really bricked it for good? Should i try it and flash it from DOS now?...thanks.
Post by: davebordon on June 08, 2009, 04:39:00 PM
I seem to have bricked a lite-on drive. I'm just hoping that someone here can help me out a bit.
I've tried everything listed in this post so far with no positive results.
Here is a breakdown of what I did. Please note that I have successfully flashed a few lite-ons before this one. This wasn't my fault either!
1. Connected up the drive to the PC with the connectivity kit.
2. Used Jungle Flasher and a probe to grab the keys from the drive
3. Built the hacked firmware in JF
4. Hit the Lite-on erase button and erased the drive
5. Flash the hacked firmware to the drive (and stopped there).
The problem is that when JF was 1/2 way through flashing bank 3 (the final bank), the PC completely crapped itself and locked up. This has not happened on Lite-ons before and now the drive basically has no soul!
I've tried all kinds of L-O-ERAS and DOSFLASH tricks to get this drive to even be recognised.
My PC has a VIA mainboard with a 3149 Sata chipset that has never failed before.
I have tried on both sata ports and the drive won't respond.
L-O-ERAS and DOSFLASH tell me that there is no drive connected to the PC. However, if the drive is connected and powered when I reset the PC, it locks up trying to detect the drive, so there is still life left in it.
When I run DOSFLASH it just says that port FC00 (the port I always use) has no drive attached.
A few notes that should also help the fairly obvious questions that are sure to follow:
Q. Did you plug the power in upside down?
A. No it's the right way around. In fact I didn't un-plug it (only powered off) until I was certain something was horribly wong. At which point I changed drive (explained in next question)
Q. Have you tried another drive?
A. Yes I have successfully spoofed a spare BENQ and it works fine, but the guy at work is so picky that he won't settle for another drive. He HAS to have his drive.
Q. Have you tried another PC?
A. Yes. I tried on a friends PC with a different SATA set and still no go. Not too sure what SATA chipset he has though
Q. Did you have the drive 1/2 way open?
A. I have tried it with the drive closed, opened fully, and every 1/4 inch increment in between. I have seen further up in this post that people have found that the tray position is very important, and I feel confident that I have tried all the necessary positions.
Q. What version of (insert software title here) are you using?
A. Jungle Flasher - 1.55 Beta
DOSFLASH - 1.7 (latest version)
L-O-ERAS - (don't know)
Q. Have you read through the posts to find solutions?
I have read through several posts regarding bad flashes on Lite-On drives, but the solutions others have tried have failed for me.
Q. Do you have the Key.bin, Inquiry.bin, Identify.bin and dummy.bin?
A. Yes I have these, so I have all the keys and stuff for patching a firmware. All I need is a working drive to flash it to.
Q. Are you using the VIA driver or PortIO32?
A. I am using PortIO32, as stated earlier, I have done a few Lite-Ons before with no problems.
Q. Does the drive Eject?
A. No it doesn't. Not in the Xbox 360, not with the connectivity kit.
Q. What did you have for breakfast?
A. 2 bacon and egg sandwiches. Very delicious.
Sorry about the length of this post, but I figured this way you can get all the info you need without crappy vague descriptions and 100 follow up questions. Plus, this way, anyone reading this at their work will look busy!
Any ideas are welcome, no matter how crazy or far fetched! (But preferrably cheap)
Thanks,
Dave.
Post by: Takashi on June 08, 2009, 07:15:00 PM
v1.62 is out.
Post by: davebordon on June 09, 2009, 01:07:00 AM
I'll upgrade my Jungle Flasher.
Do you reckon that will help with recovering the dead Lite-On?
Dave
Post by: deilzfcjk on June 10, 2009, 03:10:00 PM
QUOTE(davebordon @ Jun 9 2009, 12:07 AM)
Thanks,
I'll upgrade my Jungle Flasher.
Do you reckon that will help with recovering the dead Lite-On?
Dave
It probably won't help. But I do know that you are not doing something fundamentally right. Sounds like a situation I was in. Did you try Liteon Erase using dosflash? Do not use the one with the L-o-erase.exe It in my opinion was useless. When you have the latest dosflash....make sure you have the lastest dosflash. I know some people assume they have it but always double check. The older dosflashes did not have liteon [erase] [write] [read] on the menu. Trust me. Make sure you have the right port too. Do not want to mistakenly erase an IDE or other SATA drive.
Post by: davebordon on June 11, 2009, 06:24:00 AM
I've got the latest dosflash, but the drive won't appear any more.
When I run dosflash, it tells me that nothing is connected to the sata port.
I've tried power cycling the drive before, during and after starting dosflash, but it won't be seen.
Before flashing, and with other drives, port FC00 (Which I always use) works fine.
Since the drive suffered brain damage, it won't appear on that port or my other sata port.
However, other drives can be flashed no problem, so it's not the sata port for dosflash that's the problem, just the drive itself.
I'm just looking for ideas on how to get the drive visible and flashable. Even if I get it back to stock firmware, I can work with it from there.
Cheers,
Dave.
Post by: HaloSlayer on June 26, 2009, 03:37:00 PM
I've done over 15 systems now with my pc and only this one Lite-On drive has given me issues.
Originally I was able to read the firmware, erase the drive and attempt to write all using jf 1.55 (before 1.62 was out)
The issue was while writing the last bank of the firmware, it just stopped. I gave it several mins, no luck.
After that I couldn't get windows to stay working while the drive was powered on. (3secs after power on windows would just freeze, 5secs after power off it would unfreeze)
So now I turned to Dos (l-o-eras & dosflash) which I have used fine before on this same pc.
Everytime I tried "l-o-eras ****" it would return status FF80.
And Dosflash saw unknown drive chip and wouldn't flash to it.
"Dosflash liteon e ****" said it worked, but would work even with no drive there. ?!?!?
I tried every combination I could think of to get this to change to FF72!
I've read all the posts, all the methods and tried them all
Power on, try, try power off/on, try try,..., no luck.
Drive tray at all positions, ..., no luck.
Different ports, ..., no luck.
Different drives worked fine using this setup.
Always FF80 for this specific liteon drive.
Then today I had nothing to do and decided to mess with it some more.
Still FF80 in Dos using "l-o-eras ****" after 50 trys.
So without rebooting or powering my pc down I unplugged the drive and plugged in a possibly dead Hitachi Drive I had laying around just to see what I get from that.
It came back with FFF2, then FF01 all the time.
(Again without rebooting or powering down my pc)
I hooked up the Liteon again and tried a few times.
Came back with FF81, noticed drive was off, turned power on, got FFF2, then FF72, and again FF72!!
Wow!! That actually helped change the status!
I then went through the normal process using DosFlash with a 1.6 cfw and it was able to write to the drive!!
Thought I would give my experience to possibly help those still stuck with status FF80 on their lite-on's.
Hope this helps someone,
Later
Post by: bouf111 on June 28, 2009, 01:10:00 AM
I seem to have bricked my drive also using JF
pc now freezes and wont eject
I can get the drive in dosflash to show FF72 but when I try to erasenothing happens it just shows erasing ... and doesn't progress
Can anyone give me any help on this?
Thanks
Post by: mrblobby501 on July 08, 2009, 04:14:00 AM
I have been modding drives for family and friend since day1 so I have seen some strange things, but I now have a drive that baffles me.
Its a Lite-on DG-16D2s, HW ver A0A2 FW ver 74850C produced march 2009.
I extracted the keys and erased the drive for flashing. During flashing, jungelflasher froze and left me with a dead drive.
I have tried re-flashing with junge flasher and with dosflash (latest versions) everything goes well untill it starts flashing. The programs just freeze.
This is a screenshot of JF in frozen state:
I am lost, I tried a different PC, but on that one, dosflash would hang during the port scan.
I am using a PCI VIA card for flashing and that has flashed around 10 lite-ons before with no problems!
Post by: Wateva on July 11, 2009, 10:36:00 PM
What about us that have a full brick?? ---> http://forums.xbox-s...howtopic=686444 (Drive doesn't even show up on dosflash)..
About your issue mrblobby501, just prep an USB boot or floppy and use dosflash/l-o-eras combo to write the new firmware.. trust me. it works (I had the same issue with 3 lite-on here)..
Post by: Juise on July 11, 2009, 11:09:00 PM
I make the bootable USB stick with iprep. Did the l-o-eras d600 twice first returns ff80 second returns ff72. power off the drive run dosflash it ask if I want to resend, I say yes, power up the drive and it cycles between 0xf2, and 0x72 constantly (just looks like the 7 constantly changes from 7 to f). Only way out of it is to ctrl c it.
So close but so far!
Any ideas?
Post by: Juise on July 12, 2009, 12:01:00 PM
QUOTE(Juise @ Jul 12 2009, 06:09 AM)
OK my lite-on bricked when I tried to update from 1.5 to 1.6.
I make the bootable USB stick with iprep. Did the l-o-eras d600 twice first returns ff80 second returns ff72. power off the drive run dosflash it ask if I want to resend, I say yes, power up the drive and it cycles between 0xf2, and 0x72 constantly (just looks like the 7 constantly changes from 7 to f). Only way out of it is to ctrl c it.
So close but so far!
Any ideas?
So I figured out I was using an older version of dosflash. I can now flash the drive but newer backups come up as DVD's while older backups work normally.
Post by: mrblobby501 on July 17, 2009, 11:32:00 PM
QUOTE(Wateva @ Jul 12 2009, 06:36 AM)
Most of the users here have a "semi brick" lite on...
About your issue mrblobby501, just prep an USB boot or floppy and use dosflash/l-o-eras combo to write the new firmware.. trust me. it works (I had the same issue with 3 lite-on here)..
Thanks for the advice, but I already tried that. I can get it erased and then go into dosflash, but the flashing routine always hangs during flashing of the first bank. I just flashed another Lite-on with no problem in Jungleflasher (HW ver A0A1). My "problem" drive is HW ver A0A2.
Post by: ricky54326 on August 15, 2009, 07:07:00 PM
The status code I got, was FF78, which wasn't FF80 like the post said, but i still unbricked it.
Thank you so much @ the poster.
Post by: darkstar8907 on August 21, 2009, 08:50:00 PM
Post by: chiribomb on August 22, 2009, 10:43:00 AM
just use iprep to format and make the thumb drive bootable.
Add dosflash and the hacked firmware.
I tried to boot into dos but it froze at the bios because even the unpowered connected xbox will cause this.
So I disconnected the sata and booted into dos.
Ran dosflash to see my ports but it only shows ide ports.
So this time I left my HD connected and booted into dos and ran dosflash and then it showed my sata ports with my HD connected.
Without powering down the pc, I removed the sata cable and plugged into the xbox and powered it up.
Ran dosflash and it did not freeze and it showed sata ports with a device hooked to one of them.
Ran dosflash and it erased and wrote to the drive.
Done and Done
Post by: GRIFFIN1 on August 29, 2009, 04:33:00 PM
QUOTE(Juise @ Jul 12 2009, 07:01 PM)
So I figured out I was using an older version of dosflash. I can now flash the drive but newer backups come up as DVD's while older backups work normally.
I also wasted a lot of time trying to use dosflash 1.4. I was tying to use it because it's the version that's found in the pc tools section of this web site. I didn't realize it was it wasn't the latest version.
Maybe dosflash 1.4 works form some people, but it didn't work for me. I spent 3 hours messing around with 1.4, and I was finished flashing 3 minutes after I downloaded dosflash 1.8.
A note should be added to the original post to try dosflash1.8 if the 1.4 version doesn't work.
Post by: nhoj_yelbom on September 18, 2009, 09:53:00 AM
Post by: geniusjc on September 29, 2009, 10:51:00 PM
Too late for the fried lasers I have though.
I have a spare Benq How do I use JF to spoof the Lite-On key, inq, ident, dummy? to the Benq ???
Post by: UMDJ on October 03, 2009, 12:19:00 PM
QUOTE(geniusjc @ Sep 30 2009, 12:51 AM)
I have flashed many drives over the last 3 yrs successfully and now i've fried the laser on 3 Lite-on drives when using JF 1.55 i think. I am now thinking that it was the probe that screwed them up and they are prob 83850 lite0n drives. The newest version JF 1.66 has LO83 in it now so you can successfully flash them without a probe.
Too late for the fried lasers I have though.
I have a spare Benq How do I use JF to spoof the Lite-On key, inq, ident, dummy? to the Benq ???
just load the lite on dummy key into jungle flash, and spoof to ben q 1.6 fw, then follow regular procedures for ben q flashing...
but to my problem though. i erased my lite on, then i flashed it to 1.6, and now it wont read back ups or originals. and its a brand new xbox 360. i erased and reflashed to 1.5, and it didnt work. any idea why? the laser still lights up properly. and the disc spins(only for a sec), its not a bad key because i spoofed the the lite on to a sammy. i even did a pot tweak with no change in results
Post by: barelynotlegal on October 04, 2009, 04:53:00 PM
QUOTE(flash360 @ Jan 18 2009, 02:24 PM)
I had the freezing problems when trying to erase in jf using via 6421 and maximus extractor through usb
Podger posted a while ago about this but for some reason it dosnt seem to have cought on
I installed the VIA_RAID_V530C which can be found here http://www.versiontr...einfo/win/70826 and the problem was sorted
No boot disk or dos or rebooting pc required, you can do the whole thing in 1 go Thank's again podger
so what u are saying is if i update to the V50C package, i wont freeze up on me??
I had the freezing problems when trying to erase in jf using via 6421 and maximus extractor through usb sad.gif
Podger posted a while ago about this but for some reason it dosnt seem to have cought on huh.gif
I installed the VIA_RAID_V530C which can be found here http://www.versiontr...einfo/win/70826 and the problem was sorted biggrin.gif No boot disk or dos or rebooting pc required, you can do the whole thing in 1 go rolleyes.gif
Thank's again podger wink.gif
so what u are saying is if i update to the V50C package, i wont freeze up on me??
Post by: barelynotlegal on October 04, 2009, 05:34:00 PM
QUOTE(Zan3 @ Jan 27 2009, 03:11 AM)
Nice! is this working for somone with CK3 to? annyone?
anyone??? please help.
Post by: janaro78 on October 05, 2009, 04:38:00 PM
QUOTE(geniusjc @ Sep 30 2009, 05:51 AM)
I have flashed many drives over the last 3 yrs successfully and now i've fried the laser on 3 Lite-on drives when using JF 1.55 i think. I am now thinking that it was the probe that screwed them up and they are prob 83850 lite0n drives. The newest version JF 1.66 has LO83 in it now so you can successfully flash them without a probe.
Too late for the fried lasers I have though.
I have a spare Benq How do I use JF to spoof the Lite-On key, inq, ident, dummy? to the Benq ???
I've got a similar situation....I've got the DG-16D28-S-09C (AOA2/83850C) I got the dummy twice, flashed it and now I'm unable to ready any dvds. Flashed back the original firmware and the drive goes as if I had erased it. Then I have real trouble getting it back to the hacked firmware, but that doesn't help much because as stated before, it's unable to read any dvds...
Any ideas?
Post by: daman22 on October 14, 2009, 08:31:00 PM
Post by: chomnom on October 16, 2009, 01:50:00 PM
QUOTE(mrblobby501 @ Jul 17 2009, 10:32 PM)
Thanks for the advice, but I already tried that. I can get it erased and then go into dosflash, but the flashing routine always hangs during flashing of the first bank. I just flashed another Lite-on with no problem in Jungleflasher (HW ver A0A1). My "problem" drive is HW ver A0A2.
did you ever fix this? my drive hangs at writing bank 0 in dosflash too. been frustratin me for weeks.
Post by: bb90 on October 22, 2009, 04:12:00 PM
Anyways it worked great and my drive is properly flashed now.
Thanks again!
This post has been edited by bb90: Oct 22 2009, 11:13 PM
Post by: ltrover on October 31, 2009, 03:30:00 PM
QUOTE(UMDJ @ Oct 3 2009, 08:19 PM)
just load the lite on dummy key into jungle flash, and spoof to ben q 1.6 fw, then follow regular procedures for ben q flashing...
but to my problem though. i erased my lite on, then i flashed it to 1.6, and now it wont read back ups or originals. and its a brand new xbox 360. i erased and reflashed to 1.5, and it didnt work. any idea why? the laser still lights up properly. and the disc spins(only for a sec), its not a bad key because i spoofed the the lite on to a sammy. i even did a pot tweak with no change in results
I've got exactly th esame problem. Anyone know a solution for this?
I originaly tried flashing my new liteon 830850c drive ( I have successfully flashed lots of other types of drives with no problem) using JF, after erase during write my pc froze locking drive in vendor mode. I tried everythng I have read in this forum to get the firmware wrote to the drive, but no luck at all! I then sent my drive to a reputable flasher/repairer of 360s of another forum. They said they had successfully flashed the drive with IX1.6, but when I put it in the 360 it wont read any disks. No error lights, or error codes. The drive spins, it says reading on the screen, then nothing.
Anybody help?
Post by: Soulja85 on November 05, 2009, 07:51:00 AM
Post by: donhu on November 05, 2009, 07:48:00 PM
thanx
Post by: amp2006 on November 25, 2009, 01:35:00 AM
QUOTE(donhu @ Nov 6 2009, 06:48 AM)
hey guys i really need some help.... so... i tried to flash a 83850c drive and didnt check the dummy.bin that i created to see if it was "good" before i went ahead with the rest of the process and so i ended up erasing the drive and not having a "good" dummy.bin to finish the process. so now im stuck with a dead drive and no dummy.bin to work from (becuz the drive is erased) what can i do to get my drive back up and running (i.e. flashed)?
thanx
i had the same problem but i had the valid keys (dummy.bin)
since i also erased coudnot write it due to my Via sata raid .issues
i ended up to use Iprep to write the keys to flash the drive but mine was 74850c
here is what i did :
i have used JF latest one + after i got a valid keys with 360 xtraxtor Pro
open source firmware (dummy.bin)
open target firmware (ix1.6-liteon)
and then Save to File Lite_CFW
and then i used Iprep to make a bootable USB Drive
and deleted the L74CFW in CFW folder created by iprep and put the Lite_CFW and renamed to L74CFW
and also created a folder inside BACKUPS named 1234567 and a folder named 12345 and put it the L74CFW inside 12345
BACKUPS >>1234567 >>12345
and then i used iprep 10.7 to write the flash .
c:\>l74 1234567 12345 w
and it flashed and done ..
hope you have a good valid keys
but from question no keys no work .i think
Post by: pwedkc on December 18, 2009, 08:15:00 AM
Post by: jdog7765 on December 27, 2009, 08:59:00 PM
Thanks
Post by: amp2006 on December 29, 2009, 12:33:00 PM
QUOTE(jdog7765 @ Dec 28 2009, 06:59 AM)
I know this Sticky is old, but I'm having trouble with my Liteon. I was able to dump all the files compile the firmware. Did the Liteon erase, but wasn't quick to reset the drive and drive did not go into vendor mode. So i followed all the tutorials I could find and did the L-O-Eras and got FF72 but when I use dosflash I don't see the drive listed under option 5 0xC800, it says no ATAPI device found. If I don't use the loeras and just go straight to dosflash it asks if I want to send drive intro. I say yes, reset drive but that doesn't work. Has anyone else had this issue. I cant figure it out.
Thanks
here if you have a 74850c
open Jungleflasher go to Firmware Tool 32 and then :
open source firmware (dummy.bin)
open target firmware (lite-on 1.6)
and then Save to File Lite_CFW
then use Iprep ( latest one) to make a bootable USB Drive
and delete the L74CFW in CFW folder created by iprep and put the Lite_CFW and rename it to L74CFW
and also create a folder inside BACKUPS name it 1234567 and a folder name it 12345 and put it the L74CFW inside 12345
BACKUPS >>1234567 >>12345>>L74CFW
after all done restart the PC and then boot from a usb drive and then just type this after you clicked on YES button for a risky message :
l74 1234567 12345 w
it will ears the drive now and after that it will ask you to turn off the drive power and back it again .and it will ask you to press any key and after you pressed the key the writing will be done
Post by: jdog7765 on December 29, 2009, 10:10:00 PM
Post by: nhoj_yelbom on January 04, 2010, 02:45:00 AM
Post by: jackblock on January 05, 2010, 10:31:00 AM
I have correctly extracted the key and created the custom FW. The first time that I tried and flash the new FW the verify failed so I tried to just erase and flash again, but comp restarted. Since then I have not been able to get it back in vendor mode.
I have been reading many posts on remedies to get back in vendor but I cant get it. Everything I have read says that the drive isnt bricked so I am set on getting it working.
I have tried over and over in JF to get it in vendor, constantly get 0x80, 0x51, 0x50, and 0xD0 statuses.
I have also created a boot floppy with l-o-eras.exe dosflash and my custom FW. Have been trying to erase the drive from dos and constantly get FF80 status, I know that I am using the right sata port.
My only questions are what to try next; I am using the ck3 pro with usb. While I am trying to get it into vendor do I need to have the usb wire connected also?
Any help would be appreciated
This post has been edited by jackblock: Jan 5 2010, 06:32 PM
Post by: PhoneyVirus on January 09, 2010, 05:33:00 PM
No and you might need that USB Driver installed I used the Serial knowing that USB needs a driver installed where Serial is always installed if you got one. Also with Liteon drives the Original firmware can't be Restored so theres no going back when you flash your Liteon drive.
This post has been edited by PhoneyVirus: Jan 10 2010, 01:36 AM
Post by: jackblock on January 13, 2010, 01:47:00 PM
Post by: njmbb8 on February 02, 2010, 12:27:00 PM
heres the log file:
CODE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~
JungleFlasher 0.1.70 Beta
Session Started Tue Feb 02 13:54:00 2010
This is a 32 bit process running on 8 x 32 bit CPUs
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 6 I/O Ports.
Found 0 Com Ports.
Found 3 windows drives C: D: E:
Found 2 CD/DVD drives D: E:
Loading firmware file C:\Users\Nate\Documents\Dummy.bin
MD5 hash: af24a825c6341ab3e05a71f7516b3f8c
Inquiry string found
Identify string found
Drive key @ 0xA030 5BE19EBE0995E2340B1F7A9B2B2DE155
Firmware Osig: [PLDS DG-16D2S 8385]
Firmware is: iXtreme v1.60-12x-
Auto-Loading firmware file C:\Users\Nate\Documents\JungleFlasher v0.1.70 Beta (86)\firmware\ix-lt-838.bin
MD5 hash: 187ee5780d863922d49ec1d2ed0d9f48
Genuine iXtreme Lite-Touch
Drive key @ n/a 77777777777777777777777777777777
Firmware Osig: [PLDS DG-16D2S 8385]
Firmware is: iXtreme LT
Spoofing Target
DVD Key copied to target
Inquiry string copied to Target
Identify string copied to Target
Serial data copied from Source to Target
No Calibration data in source
Spoofing Target
DVD Key already matches
ID strings already match
Serial data already matches
No Calibration data in source
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0xD0
....................
Device Intro failed!
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0xD0
....................
Device Intro failed!
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x72
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name: Unknown type
Flash Size: n/a
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x72
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name: Unknown type
Flash Size: n/a
Unknown flash type Write aborted !
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x80
....................
Device Intro failed!
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x80
....................
Device Intro failed!
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x80
....................
Device Intro failed!
No Drive Detected! DVDkey files extraction aborted!
~~~~~~~~~~
JungleFlasher 0.1.70 Beta
Session Started Tue Feb 02 13:54:00 2010
This is a 32 bit process running on 8 x 32 bit CPUs
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 6 I/O Ports.
Found 0 Com Ports.
Found 3 windows drives C: D: E:
Found 2 CD/DVD drives D: E:
Loading firmware file C:\Users\Nate\Documents\Dummy.bin
MD5 hash: af24a825c6341ab3e05a71f7516b3f8c
Inquiry string found
Identify string found
Drive key @ 0xA030 5BE19EBE0995E2340B1F7A9B2B2DE155
Firmware Osig: [PLDS DG-16D2S 8385]
Firmware is: iXtreme v1.60-12x-
Auto-Loading firmware file C:\Users\Nate\Documents\JungleFlasher v0.1.70 Beta (86)\firmware\ix-lt-838.bin
MD5 hash: 187ee5780d863922d49ec1d2ed0d9f48
Genuine iXtreme Lite-Touch
Drive key @ n/a 77777777777777777777777777777777
Firmware Osig: [PLDS DG-16D2S 8385]
Firmware is: iXtreme LT
Spoofing Target
DVD Key copied to target
Inquiry string copied to Target
Identify string copied to Target
Serial data copied from Source to Target
No Calibration data in source
Spoofing Target
DVD Key already matches
ID strings already match
Serial data already matches
No Calibration data in source
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0xD0
....................
Device Intro failed!
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0xD0
....................
Device Intro failed!
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x72
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name: Unknown type
Flash Size: n/a
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x72
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name: Unknown type
Flash Size: n/a
Unknown flash type Write aborted !
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x80
....................
Device Intro failed!
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x80
....................
Device Intro failed!
Sending Lite-On-Erase request to port 0x7880
..............
Drive returned Status 0x80
....................
Device Intro failed!
No Drive Detected! DVDkey files extraction aborted!
Post by: njmbb8 on February 02, 2010, 05:02:00 PM
Post by: bubble_gum on February 08, 2010, 11:11:00 PM
Post by: bubble_gum on February 09, 2010, 11:48:00 PM
Post by: gazasexpot on February 21, 2010, 01:37:00 PM
QUOTE(bubble_gum @ Feb 10 2010, 08:48 AM)
My friend says that becouse i spoof firmware LT with jungle 1.6 not 1.7, so that kill my drive.Are you agree?
nope .do u have the latest ver of dosflash an liton erase tool also run liton erase once then turn of the power to the drive then back on then run it again then again make shure u get ff72 then run dosflash to see if it picks up the chip if it dus the your drives ok all u nead is to create the corect firmware and flash again using dosflash works a treat
Post by: neildmd on March 23, 2010, 12:22:00 AM
Solution: I have discovered a way to get these pesky Lite-on driver to recognize properly in JungleFlasher and allow the firmware to be written while still in the Windows operating environment. I have only ever had this problem with the 74850C model drives but it may happen to other drives as well and this should solve the problem in most cases. I'm pretty sure this issue only happens with nForce 3 and VIA IDE drivers. If you have either I advise you to remove the drivers and use the windows generic ones. I realize this can usually be fixed with DOSFlash or iPrep using a bootable DOS floppy or USB flash drive but not everyone has that option.
You should already have your dummy.bin file at this point or at the very least your key.bin serial.bin inquiry.bin and identity.bin. (DummyGen button under the DVDKey32 tab will allow you to generate the dummy.bin)
First you will need to download DOSFlash 1.8 from the usual places.
1. Open jungleflasher (if your bin files are already in the backups folder enter that folder name in the first dialog box) and on the FirmwareTool32 tab, click on Open Source Firmware, browse to the backup folder under JungleFlashwer, where the dummy.bin for this drive is located, and open it.
2. JF will automatically load iXtreme LT v1.1 and patch all the necessary info. Once you verify everything looks ok, click on Save to File and save your hacked firmware (Lite_CFW.bin) in the default folder.
3. Hook up the power and sata cables to the drive and power it on. At this point, it will not matter if the tray is half open, since the chip is already erased. It is just not being detected properly by JF.
4. Go to the MTK Flash 32 tab and click on Lite-On-Erase (if it goes to status 0x72 then click on Write cuz you just got lucky!)
5. Close JungleFlasher and open up either DOSFlash32 or DOSFlash64 depending if you have a 32-bit or 64-bit operating system. Choose LiteOn Erase next to Flashing Task and then click on the LiteOn Erase button at the bottom just to be sure it was fully erased. (If the next step didn't work the first time skip to the alternate steps at the end now)
6. Choose Write next to Flashing Task and click on Write Flash at the bottom. Browse to where you saved Lite_CFW.bin and open it.
7. Once the flash has been written and verified you can close DOSFlash and click on Yes.
8. Your drive should now be working! Go test it out.
If it still refuses to flash, go back to step 5 and get it into status 0x72 again, but instead of going to step 6:
1. Open task manager by pressing Ctrl+Alt+Delete, click on the Processes tab, find DOSFlash32.exe or DOSFlash64.exe in the list and right-click on it and press End Task. Confirm that you want to end the process. (This allows the portio drive to stay loaded in memory and leaves the drive in status 0x72)
2. Open JungleFlasher and type in the folder name you used earlier. Click on Open Source Firmware and open your dummy.bin or you can click on Open Target Firmware and open the Lite_CFW.bin file you created earlier. Either will achieve the same result.
3. Click on the MTK Flash 32 tab, do not try to detect the drive or click any other button!!
4. Click on Write and your hacked firmware will be written to the drive. Congrats and enjoy your newly resurrected Lite-On!
Maybe this could be added into the main post. Hopefully Team Jungle will come by this and figure out whats causing this issue by breaking down whats happening here on a software level. (I'm sure many of you will point them to this post) It obviously has something to do with the way JF polls the drive for the flash chips status. DOSFlash must do this differently. Also worth mentioning is the fact that you could probably avoid this issue all together by just using DOSFlash instead, but I really like what Team Jungle have put together with JF. Thanks to all those involved for making this scene and this workaround possible, especially Xbox-Scene.com!
Yes I know this is my first post. I always seem to figure things out on my own or find the answer I'm looking for right here at X-S. (IMG:style_emoticons/default/tongue.gif)
Edit: I just noticed that gazasexpot pretty much summed this up right above. Oh well, I'm sure many will still find this useful...
This post has been edited by neildmd: Mar 23 2010, 07:24 AM
Post by: St0ked56 on April 13, 2010, 05:06:00 PM
Thanks,
St0ked56
Post by: abracs on May 22, 2010, 06:27:00 AM
Post by: winterknights on May 29, 2010, 06:12:00 AM
Here is an easier way of understanding
surely if ur at this stage u know how to installed the via card drivers and portio32
1. get these programs latest versions should be fine
- Iprep
- Dosflash
- Lite On Erase
- Lite on's latest firmware
i found that i didnt even need liteon erase, but you may need it so get it anyway
they can all be found in auto xbins 2008
2. using iprep make a boot usb drive.
do this by opening iprep then adding a samsung firmware any one doesnt matter as this isnt used
then make sure mtk flash box is ticked and then prepare destination (ur usb)
once thats done put all the programs u downloaded onto the drive not in folders makes it easier
the firmware you put on here HAS to have your drives key in it.. u should have saved the dummy, u can add your key to the new firmware through jungleflasher
do this by opening jungleflasher then in the first tab that shows up open source firmware and pick your dummy. then open target firmware and pick your new latest cracked firmware and spoof your key to it. make sure its not multiples of 7's or f's
once its spoofed save the firmware to the drive with an easy to remember name.
okay now that your this far you need to restart your pc make suren ur lite on drive isnt powered yet and boot into the usb device by pressing f8 just after bootup.
once u agree to y (for iprep) power up lite on and type dosflash
this should list your drives
once listed type in the number that corrispondes with your drive
then type LITEON E to erase.
once thats done type dosflash again and get back to the swcreen where u flashed and press w to write instead.
once done that type in the name of your file "LOFIRM.bin" was what mine was called and this should erase again and write it to the drive. this is now done. power off the drive for a few seconds then re power and press eject and if it ejects it should be fixxed and ready for you to test..
i know its messy but its easy for dumbarses like myself.
cheers
Post by: dascope on December 21, 2010, 08:25:00 AM
QUOTE(brandogg @ Feb 5 2009, 08:20 AM)
I just want to say thanks for these awesome tips. For some reason iprep refused to see my friend's LiteOn CFW, so I used l-o-eras.exe and dosflash, and had it working with seconds. Awesome thread!
Do I need to put the wires/resistor/switch (what position) and cut the traces on the drive when i want to recover it with l-o-erase/dosflas? it froze at the erasing part with jungle flasher... i have the original saved firmware with key before it stopped responding... thanks for the help!
Post by: WEB11 on March 08, 2011, 11:37:00 PM
.
Post by: jamiebarrington on June 17, 2011, 02:00:00 AM
you saved me, and also i now prefer to flash in dos as it saves messing around with the VIA driversThanks again.
Post by: peeer on September 08, 2011, 12:55:00 AM
tory burch sale
Cheap Tory Burch Handbags
Green Weight Loss Tea
p57 hoodia
Post by: oden1st on November 11, 2011, 07:46:00 PM
I've modded about 20 Xbox's, but 3 days ago I was flashing a liteon 78450C and didn't cycle fast enough(obviously) and bricked the drive. I'm using a PCMCIA sata 6421 card on an old HP nc6000 laptop. My question is...I've been trying for days with diff things to unbrick the drive...I have the key, inquiry, dummy, lite-cfw.bin,etc...tried 360 mod disk but since laptop is PCMCIA...doesn't boot up...made bootable flash drive with iprep but lappie won't boot from USB..no option in bios...tried dosflash32, but can't install portio32.sys, used dosflash16....with partial luck...L-O-eras gave me a FFFF code...I was able to erase drive with dosflash but not able to write 0x80 code in dosflash as well as jungle flasher...1 out of 3 tries with JF I will get good flash chip ID with 0x72 code...but when I try to erase............0x80......I really need someone's help...I have a Sammy I spoofed but can't play XGD3 games....ie SKYRIM, Batman Arkham City, & LOTR War in the North, or COD MW3....which are my fav 4....obviously....I'm sure with the vast knowledge of all of you...someone knows a solution with my current hardware....(Laptop, CK3 Lite, CK3 probe 3, PCMCIA to sata card reporting as VIA 3249, I have all .bin files as well). PLEASE HELP....it's the weekend and u want to play my fav 4 games without buying a new drive right now or a 6421 for my desktop.....HELP.....
Post by: ashbylaker on December 08, 2011, 10:04:00 PM
QUOTE(St0ked56 @ Apr 13 2010, 06:06 PM)
I have onboard via chipset. I am trying to use l-o-eras and dosflash to recover my drive and I am not having much luck. First I do the l-o-eras PORT # to get the port in FFx72. Once this is done I type in DOSflash and select the corresponding number and type W for write. Once I do this I get back "Unknown flash chip!"
Hi,
I have the same issue as stoked "unknown flash chip", when using the same method as he explained:
l-o-eras PORT, then dosflash. I have tried it with all manner of power-cycles, number of times I use l-o-eras, etc. (I can get ff72 on the second eras cmd)
Other methods:
In JF (1.84 for my phat) I can get the device info from the power cycle with Liteon Erase button, but when I write it freezes on the first period of the first bank - consistently.
When I use just dosflash, without putting it into ff72, if of course freezes on erase (when writes). however LiteON E works to just erase, which I've also tried before write cmd, in many combos etc.
Anyone have any new ideas on how to get past the "unknown flash chip"?
Thanks!