Mobile/PDA About Us Advertise here
User User name Password  
  Not registered yet? Register here.
Lost your password? Click here. 		 
  Home   News   Guides   Downloads   Glossary   Hardware   Profiles   Forums   v4  
 Advertise at AfterDawn.com     Link to us!     Private messages     Compose a private message     List of all updated threads     Threads without replies     Search messages
Wednesday 20.5.2026 / 17:28
Search AfterDawn Forums:        In English   Suomeksi   På svenska
afterdawn.com > forums > consoles > xbox 360 - modding & hacking > have lite-on files but think something went wrong
Show topics
 
Forums
Forums
Have Lite-on files but think something went wrong
  Jump to:
 
Posted Message
knarf444
Newbie
_ 		25. January 2009 @ 12:08 _ Link to this message    Send private message to this user   
I think I did something wrong. I was able to extract these bin files
Inquiry which says 1 kb
Key which says 1 kb
Identify which says 256 kb but it should say 1 kb
Dummy which says 256 kb
Lite-CFW2 which says 256 kb

Drive is now dead no eject functions. As long as if I have the key will I be able to revive this drive and do I need the Identify bin. THANKS FOR ANY HELP
[ + quote]
Advertisement
_ 		__
larrylje
AfterDawn Addict
_ 		25. January 2009 @ 12:56 _ Link to this message    Send private message to this user   
The size of all my files are...

Key.bin 16kb
Inquiry.bin 96kb
Identify.bin 512kb

I have done 4 of them and they all have the same size.

Did you extract them with the drive tray half open?
[ + quote]

This message has been edited since posting. Last time this message was edited on 25. January 2009 @ 13:24
knarf444
Newbie
_ 		25. January 2009 @ 14:36 _ Link to this message    Send private message to this user   
Yes it was half open and if I ck the bins by the property thay are
Inquiry:96 bytes
Key:16 bytes
Identify:256 kb

The Identify is the problem. Do I need this?
[ + quote]
aj123
Member
_ 		25. January 2009 @ 14:45 _ Link to this message    Send private message to this user   
try using ur dummy if u can.
[ + quote]
larrylje
AfterDawn Addict
_ 		25. January 2009 @ 15:25 _ Link to this message    Send private message to this user   
I don't know if the identify.bin will be an issue or not.

Did you erase and write the firmware to the drive or did it freeze during that step?

Friday I had an issue with a drive during the Write part of it. It froze and after that the PC would freeze during boot up. It also didn't detect the drive and it would not eject. So try turning off the drive and boot your PC.

So what I did was start JungleFlasher then went to FirmwareTool 32 TAB. Then I selected "load from dump files" for source and loaded the key/inquiry/identify files. Then for the Target I loaded the lite-on hacked firmware. Now spoof source to target and make sure the DVD key# is the same. After you do that and verify the DVD Key numbers are same for source and target choose "save to file" name it something like lite.bin and keep it handy for the next step.

Now go HERE and read the green section part of this tutorial. All your doing is creating a floppy boot disc and then transferring L-O-Eras.exe/dosflash16/lite.bin to the boot disc.

Then follow the linked guide on how to erase/write the firmware using DOS.

I had issues using the L-O-Eras.exe part of the linked tutorial. So I used JungleFlasher to erase the drive then just used the dosflash in DOS to write the firmware. If you have issues and want to try it this way then boot the PC (without drive on). Select the MTK Flash 32 TAB. Make sure the I/O port is the same port that you used previously to read the files off the drive (The drive properties probably will not show or will not show properly because the firmware has been erased or botched). Now turn on the drive. Then choose Lite-On-Erase and try to erase the firmware from the drive. This should work and you should get all the proper information filed in the flashchip properties dialog box. After you do this turn off your PC and boot up with the bootable floppy and then follow the steps the above linked tutorial gives for writing the firmware to the drive.

Hope this helps out. But I have no idea if your real issue is the Identify.bin file. It could be and this might not work for you.
[ + quote]
knarf444
Newbie
_ 		25. January 2009 @ 21:24 _ Link to this message    Send private message to this user   
Thanks for your help but I tried the first part and start JungleFlasher then went to FirmwareTool 32 TAB. Then I selected "load from dump files" for source and loaded the key/inquiry/identify files. When selecting the identify it says (Identify file should be 512 byyes) and mine is 256 kbs. My question is how important is the Identify. can I use one from my first xbox and if not is there a way to retreve it. Yes my problem started when I hit the lite-on erase. The key bin and inquiry bin looks good.
[ + quote]
Donaldo
Senior Member
_ 		25. January 2009 @ 23:25 _ Link to this message    Send private message to this user   
the file is very important... it has information unique to that very drive...

load your identify.bin into a HEX editor ... does it contain any information or is the file entirely 00's or FF's
[ + quote]
knarf444
Newbie
_ 		27. January 2009 @ 19:24 _ Link to this message    Send private message to this user   
I loaded my identify.bin into a HEX editor and file contains 00's. So now that I now this info. Is there any way to recover the identify.bin. It seem as if all the info that you read they are always focusing on the key so I did not pay any attention to the identify bin. Please advice. Thanks
[ + quote]
Donaldo
Senior Member
_ 		27. January 2009 @ 20:10 _ Link to this message    Send private message to this user   
Originally posted by knarf444:
 It seem as if all the info that you read they are always focusing on the key so I did not pay any attention to the identify bin.
yes that is true... it is sort-of one of those unspoken things that people just know ... when they refer to the "key" they mean the series of 3 files key.bin, inquiry.bin and identify.bin

as to your situation... encountering a file of all 00's and an erased liteon drive ... i don't think you can recover from that. the file contains drive specific information...

maybe somebody else has an idea cause the way i see it you're up the creek...
[ + quote]
Advertisement
_ 		__
 
_
knarf444
Newbie
_ 		27. January 2009 @ 22:19 _ Link to this message    Send private message to this user   
I look further with the hex editor and did find something similar to the first consol that was done and it looks as if it is intact. It seem to have a little more info in it then the first consol I have done. Not knowing hex I made a copy of the bad bin and edited it so that it would look like the first consol but using the info from the bad bin. The difference in the two bins is that the good one starts on line 00000000 and ends at line 000001f0 and the bad one has all 0?s down and starts the info on line 00002c00 and goes to line 00002cb0 and then from there all 0?s to line 00002e00 starts more info to line 00002e30. at one point it has dvdkey32 extract. Does this make any since to you. Please if you could help to sort this out Donaldo it sure would be a lot of help. Thanks for the help so far. To clarify the edited bin I did not use all the info because I?m not sure that you have to. If you need to take a look at it I could email it to you. Thanks
[ + quote]
afterdawn.com > forums > consoles > xbox 360 - modding & hacking > have lite-on files but think something went wrong
 

Digital video: AfterDawn.com | AfterDawn Forums
Music: MP3Lizard.com
Gaming: Blasteroids.com | Blasteroids Forums | Compare game prices
Software: Software downloads
Blogs: User profile pages
RSS feeds: AfterDawn.com News | Software updates | AfterDawn Forums
International: AfterDawn in Finnish | AfterDawn in Swedish | AfterDawn in Norwegian | download.fi
Navigate: Search | Site map
About us: About AfterDawn Ltd | Advertise on our sites | Rules, Restrictions, Legal disclaimer & Privacy policy
Contact us: Send feedback | Contact our media sales team
 
  © 1999-2026 by AfterDawn Ltd.

  IDG TechNetwork