Topic: Dummy.bin File For Lite-on Drive (Read 20 times)

Elite_Mods · « **on:** January 19, 2009, 05:43:00 AM »

why dont you just make the dummy and hacked fw through jungle flasher witg the dumped files. much easier as you need to make the hacked FW anyhow

gnahtor · « **Reply #1 on:** January 19, 2009, 05:57:00 AM »

The dummy.bin created by jungleflasher/dosflash/dvdkey32 contains the serial number of your liteon drive. If you create the dummy.bin only with the three files (inqiry, identify, key) the drive serial is NOT copied.
Ergo dont use the outdated dos dvdkey!

wildwild · « **Reply #2 on:** January 19, 2009, 08:33:00 PM »

QUOTE(gnahtor @ Jan 19 2009, 02:33 PM)

The dummy.bin created by jungleflasher/dosflash/dvdkey32 contains the serial number of your liteon drive. If you create the dummy.bin only with the three files (inqiry, identify, key) the drive serial is NOT copied.
Ergo dont use the outdated dos dvdkey!

I gathered that I will have to manually insert the key into the Dummy.bin using 360FW-Toolbox. Will it give me a VALID bin file for flashing?

gnahtor · « **Reply #3 on:** January 20, 2009, 06:36:00 AM »

You can join your dummy.bin and the liteon fw with firmtool.
But i think you are mixing things up. Im talking about the drives's serial number not about the key!

woody21_1 · « **Reply #4 on:** January 20, 2009, 11:45:00 AM »

QUOTE(wildwild @ Jan 20 2009, 04:09 AM)

I gathered that I will have to manually insert the key into the Dummy.bin using 360FW-Toolbox. Will it give me a VALID bin file for flashing?

firmware toolbox does not work with ixtreme 1.5 firmware, it can generate a dummy.bin file but i dont know if i would trust it until its updated.

use jungleflasher in windows to create your firmware as it will create it properly and tranfer the drive serial information correctly.

jt1 · « **Reply #5 on:** January 21, 2009, 06:15:00 AM »

Its too late if you have allready flashed. You should have used a program that generates all 4 files by itself. If you use 3 to create the 4th file it will be missing serial information. Your drive requires a key to play backups. Without your serial it could possibly lead to detection.

But its too late now. Just keep your fingers crossed.

woody21_1 · « **Reply #6 on:** January 21, 2009, 06:57:00 AM »

QUOTE(Kurt Hectic @ Jan 21 2009, 12:05 AM)

I don't understand.

I just used DVDKEY under DOS and get 3 files (inq,key,ident).
Started Windows and JungleFlasher.

There, by a few clicks of a mouse - I prepared final firmware. Flashed. Works good.
So you say... I don't have a serial inside the Lite-On drive now ? Even though it reads discs as it should?

Please explain. Maybe I should reflash immediately to avoid ban or something?

if you prepared the firmware using jungleflasher its fine, your drives serial will have been transferred as long as all 3 files were dumped, doesnt matter what you use to flash as long as the firmware is created in jungleflasher.

Kurt Hectic · « **Reply #7 on:** January 21, 2009, 01:34:00 PM »

QUOTE(woody21_1 @ Jan 21 2009, 03:33 PM)

if you prepared the firmware using jungleflasher its fine, your drives serial will have been transferred as long as all 3 files were dumped, doesnt matter what you use to flash as long as the firmware is created in jungleflasher.

I',m just more confused.
A similiar thread, next to this was created recently. And there...

http://forums.xbox-s...&...t&p=4420258
quote:
"It has been writing a thousand times that only dummy.bins created by jungleflasher/dvdkey32/dosflash are valid. The drive serial (not the key) is stored in the dummy.bin, but not in on one of the 3 bins (inquiry, key, identify).
Your drive serial is now lost forever. But your drive should still work, if your key was dumped correctly."

So I really don't know who is right and who is not. :|

I've used dvdkey under DOS, so not dvdkey32 to dump a key.
Then jugleflasher in Windows seemed to CREATE a dummy.bin from indentify.bin, key.bin and inquiry.bin

So either someone got it wrong or I've got a perfectly working flashed Lite-On, reading anything it should but without a serial. If so - what are the disandantages of this?
I'm asking just to be 100% sure, but I just don't really believe it could work and read everything without a needed piece (serial).

caster420 · « **Reply #8 on:** January 21, 2009, 03:10:00 PM »

QUOTE(Kurt Hectic @ Jan 21 2009, 05:10 PM)

I'm asking just to be 100% sure, but I just don't really believe it could work and read everything without a needed piece (serial).

Yes, the drive will function perfectly fine without a serial in the firmware. It is not like your drive key which is used to boot 360 media. When certain CDB's are issued to the drive, the response is from your serial. So, to make your iXtreme look as much as your original firmware as possible, the certain CDB's (drive serial) are issued to the drive and the responses used to form your serial in dummy.bin. Without them, if M$ issued these CDB's to your drive, it would respond with an invalid return, making it stick out.

Caster.

chiperman · « **Reply #9 on:** January 21, 2009, 03:27:00 PM »

Is it possible to restore the drive serial in any way?
Saved the log file from JungleFlash with the driveserial inside.

The serial is inside the logfile but not in the dumpfiles, is it possible to restore this data into dummy.bin?

pogi1100 · « **Reply #10 on:** January 21, 2009, 11:25:00 PM »

QUOTE(gnahtor @ Jan 20 2009, 06:12 AM)

You can join your dummy.bin and the liteon fw with firmtool.
But i think you are mixing things up. Im talking about the drives's serial number not about the key!

QUOTE(jt1 @ Jan 21 2009, 05:51 AM)

Its too late if you have allready flashed. You should have used a program that generates all 4 files by itself. If you use 3 to create the 4th file it will be missing serial information. Your drive requires a key to play backups. Without your serial it could possibly lead to detection.

But its too late now. Just keep your fingers crossed.

There is no drive serial (THE DRIVE SERIAL IS THE KEY)... You're talking about the key. You need the key of course, that is in key.bin.
You only need identify.bin, inquiry.bin, and key.bin to make the dummy.bin and creating the hacked FW.

See the bottom part of this tutorial for details: http://team-xecuter....eon_windows.htm

caster420 · « **Reply #11 on:** January 22, 2009, 05:55:00 AM »

QUOTE(pogi1100 @ Jan 22 2009, 03:01 AM)

There is no drive serial (THE DRIVE SERIAL IS THE KEY)... You're talking about the key. You need the key of course, that is in key.bin.

Better go do some reading, specifically my post above...

Caster.

calloused labia · « **Reply #12 on:** January 22, 2009, 06:47:00 AM »

QUOTE(caster420 @ Jan 22 2009, 08:31 AM)

Better go do some reading, specifically my post above...

Caster.

Exactly.
Dump your stock Lite-on using JF and let it create the dummy.bin. Dump your Lite-on using say...xtractor and then use JF to create the dummy.bin. "dif" (compare) the key.bin inquiry.bin and indentify.bin dumped by JF to those dumped by Xtractor (you will see they are identical). Now dif the dummy.bin(s) you will see the difference. You will see the serial.

Author Topic: Dummy.bin File For Lite-on Drive (Read 20 times)