Topic: Flashed Lite-on Says Target Spoofed As: X6 , ?]: H .+i Sh & (Read 38 times)

jview · « **on:** January 06, 2009, 09:02:00 PM »

Target spoofed as: X6 , ?]: h .+i sh &p

i used the diy cable Yayoop did, (free to dump ur key here http://xbox-experts.com/e/tutorial.php?n=flashyourliteonf)

In junlge flasher everything went fine got key and other files, erased fine, and write was fine to the drive all was ok and verified.

So i thought id Read the fireware (with out comports in) and i got the details back in Firmware tool 32 tab and it says Target spoofed as: X6 , ?]: h .+i sh &p

but it wont play discs says unreadable disc

this is a brand new 360, Xmas

any help thanks could some one take a pic of the lito-on drive with the top off looking at the laser, i think some thing is missing looks like a cover should be over the lasers internals??

This post has been edited by jview: Jan 7 2009, 05:04 AM

cili0ne · « **Reply #1 on:** January 06, 2009, 09:32:00 PM »

I think you did something wrong when you created the firmware or when you flashed the drive.

Watch at THIS tutorial, shows step by step how you flash it (fast forward until page 11~ or something).

This post has been edited by cili0ne: Jan 7 2009, 05:34 AM

Exobex · « **Reply #2 on:** January 07, 2009, 04:16:00 AM »

Try recreating your hacked firmware using firmtool.exe and your dummy.bin file. If this also gives a scrambled version string then you had a bad read of the drive first time round, and if that's the only copy you've got, I'm afraid you've buggered it.

jview · « **Reply #3 on:** January 07, 2009, 06:02:00 AM »

I hope that aint the problem, as the read said good key etc etc, ive got another read off dvdkey32 aswell,

CiliOne, thats the guide i used, but via sata crashed after erase so i went back and i did it in dos in iprep, ill go with what Exobex said and use firmtool.exe 1.3

edit im goign to use firmware tools v1.3.1 as its got a serial bug fix,

This post has been edited by jview: Jan 7 2009, 02:07 PM

jview · « **Reply #4 on:** January 07, 2009, 06:30:00 AM »

reading from firmtool.exe 1.31

Drive Key: ME KEY censored

Original Firmware Version: Lite-On DG-16D2S 74850C

Hacked Firmware Version: Lite-On DG-16D2S 74850C
Hacked FW Type: iXtreme v1.5 12x

*** SUCCESS ***
Drive key copied.
Drive serial copied.

Your hacked firmware is now ready to be flashed!
hacked.bin created successfully! Press any key to exit...

---------------------------------------------------

ok atleast i now know i got a Good dump when reading the drive.. correct ?

but if thats right why didnt my jungle flash hacked fw not work ? because thats the one i used above to make this one now ummmm

and is it also right that you dont need the Com port RX TX diy cable ..any of it .. connected when erasing and flashing the lite-on ? as the firmware is updated by the sata cable ?

This post has been edited by jview: Jan 7 2009, 02:44 PM

jview · « **Reply #5 on:** January 07, 2009, 08:42:00 AM »

ok flashed it again in dosflash with above hacked firmware made from firmtool 1.3.1

same problem > unreadable disc even on original games seems like the disc isnt spining,

could this be the firmware ? or this drive it self has its own problems,??

ToBbErT · « **Reply #6 on:** January 07, 2009, 08:54:00 AM »

After you had the unreadable disc problems you erased your drive made a new dumb of serial (few times to check if the value doesnt change to make sure you got the right key) then made a new hacked fw and flashed?And still the same problems?If you can say yes to all and followed everything explained in the tutorial i would try a other pc if you got the opportunity but i think you just use a wrong key.

woody21_1 · « **Reply #7 on:** January 07, 2009, 08:56:00 AM »

must be a firmware problem, or possibly a bad/incomplete/corrupted write of the firmware.

you should not need the com port connected as i do them soldeless and use the com port to read the key, then erase and flash in dos without the probe touching r707 and not had an issue with any liton.

if the firmware had flashed then even with a wrong key it would still play dvds at least.

could you have shorted something in the drive perhaps causing the problem/ look on the pcb for any damage or burned track or components.

ToBbErT · « **Reply #8 on:** January 07, 2009, 09:08:00 AM »

And if he tries just playing a normal dvd?If it plays i would say the rom hasnt been damaged and hes using the wrong key.Or doesnt the drive read at all without correct key?

This post has been edited by ToBbErT: Jan 7 2009, 05:11 PM

jview · « **Reply #9 on:** January 07, 2009, 12:13:00 PM »

woody21_1 / ToBbErT,.. to be honest the 1st time around did 2 dumps one in Jungle flasher and the other in dvdkey32, both where good and i got all files, but ill look more closer in HEX based app at each file,

I did left R707 pads and used a probe to just make the link, other then that there is no damage to the drives pcb which i can see, and trust me i am looking, nothing blew or burnt,

heres the upsetting bit, i but in a original dvd movie and it wont play it, hopefully the drive isnt dead, but it would be cool if some one could confirm if the drive wont play anything if the key is wrong ? (im guessing thats what would happen tho)

QUOTE

ToBbErT

After you had the unreadable disc problems you erased your drive made a new dumb of serial (few times to check if the value doesnt change to make sure you got the right key)

i havnt done this yet but i will to see what it reads,

woody21_1 · « **Reply #10 on:** January 07, 2009, 12:35:00 PM »

i havent got a liteon here to play with but have just dumped the key from a benq via serial using jungleflasher...

now looking at the log only the key is read via serial as jungleflaher sends the command to com and sata for key and just sata for inquiry and identify bin files.(can anyone confirm this.

now having the correct key and screwed up identity and inquiry should produce the problems youre having from what i understand from reading. key can be wrong but drive need to be able to identify itself hence the reason we spoof firmware when we put a different model drive in a console.

now say if you put a samsung drive with wrong key in your liteon box it should play dvds because the console can identify the device connected as a dvdrom drive at least.

makes me think that for some reason your identify and inquiry.bin have corrupted while reading over sata as long as my interpetation is right about only the key being read via com port, seems the com port data is not getting corrupted but sata is.

the flash is done over sata so if your sata is playing up maybe an iffy flash but then it should be ok in dos unless your sata chipset is faulty or incompatible in some way which i cant see but possible.

does anyone know if the identify and identity are unique to each liton drive? i assume so as they are need to be dumped and injected into the ixreme1.5 firmware along with the key. could inquiry and identity be used from another drive? would it even work and if so would it be live safe.

jview · « **Reply #11 on:** January 07, 2009, 01:44:00 PM »

the above would be good info to know, we would have less ifs and buts to think about,

just checked the files and they all match, the keys are the same,

seems like other have had the problem, and fixed it like Th3_Burn3r, waiting for him to comment on it,

http://forums.xbox-scene.com/index.php?sho...p;#entry4411088

This post has been edited by jview: Jan 7 2009, 09:46 PM

woody21_1 · « **Reply #12 on:** January 07, 2009, 04:56:00 PM »

found this some guy used the identify and inquiry.bin from another drive and worked. not live safe imo
and someone who has already compared 3 different sets of identify and inquiry.bin says in all the only difference is the unique serial number.

http://www.xboxhacker.net/index.php?topic=10926.0

looks like fwtoolbox can generate a stock inquiry and identify and inject in into the firmware, you could look into that and then hex your serial into it.. but you might have to flash the firmware toolbox makes and then try and dump it again and possibly get issues again but you might be able to test the drive and if it works we know were youre problem is.

Maximus - FIRMWARE TOOLBOX V4.8
WHATS NEW ON V4.8:

- ADDED: Custom Spoofing Option on "Tools->Spoof Firmware" option
(it asks for your 96 bytes inquiry.bin), this could be
safer for spoofing drives to Liteon because appears
Liteon drives have per-drive specific inquiry response.

If you lost you inquiry.bin file and cannot redump it, then
go ahead with listed Liteon spoofing option (it will work
but you will not have the factory value).

This post has been edited by woody21_1: Jan 8 2009, 01:02 AM

jview · « **Reply #13 on:** April 05, 2009, 05:04:00 PM »

just a UPDATE

I read on here that some one said the Extra volts fry the laser, That didnt happened in my case as the guy i sold it to said he changed the laser, i think the 5v from the molex with power from the main 360 power supply frys the pcb so the drive is fukked,

do it with out the 5v from molex, see how that works for you, i used the cable method http://xbox-experts.com/e/tutorial.php?n=flashyourliteonf

this guy here http://forums.xbox-scene.com/index.php?sho...75812&st=60

isnt using anyother power apart from the 360 power supply,. with a USB cable, said to be working, over all i think its safer,..

This post has been edited by jview: Apr 6 2009, 12:09 AM

Author Topic: Flashed Lite-on Says Target Spoofed As: X6 , ?]: H .+i Sh & (Read 38 times)