Bricked Lite-On? Read Here First Before Posting, JungleFlasher can't open .bin files? No COM Ports in JungleFlasher Options

[BoNg420]

I am posting this to hope that people quit making the same post, BRICKED LITEON OMG PLEASE HELP!! People don't think first before they post to look and see if someone else had the same issue, they post the same questions several times a day it seems... So please make sure you read the tutorials over several times before you try to flash your liteon, hopefully you read this post before doing so, so you know what you might run into. If you are unsure of what to do still, pay someone to do it instead of having to pay another $200 for a new Xbox 360!!

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?

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

[neildmd]

Symptoms: After clicking Lite-On Erase in JungleFlasher and cycling the power the drive will only ever get a status of 0x80 and/or 0xF2.

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.

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