LITEON DG-16D4S - SLIM 0401 vendor mode failure for slimkey

[unknown-9]

Hi,
since this is my first post, i'd like to say hi to everyone around - i am looking forward to interesting 360 related discussions. I follow this board long time as a passive reader, getting so much information out of it - thx for this!

Now back to topic.

I am trying to:

• dump key from 0401 using slimkey
• flash lt+1.92 to replacement pcb

I have:

• XBox Slim 4GB
• Dash 2.0.13599.0
• LiteOn 0401
• JungleFlasher 0.1.87 (277)
• DosFlash 2.0
• SATA: ICH7, ICH8R, VT8237, JMB363
• TX Unlocked PCB

What works:

• Getting the Key with DosFlash16 2.0 using NEW method [V3] Tarablinda. I do not need to 0x72 the drive. I follow the DosFlash readme to the dot and get dumped files. Did 2 reads to verify. Besides, DosFlash's built in key verification succeeded, too.
• Using JF and VT8237 i can get the PCB into 0x72, delete/clear the flash, write the flash, lock/unlock SPI

What does NOT work:

• key extraction with JF and slimkey
• using DosFlash dump with JF

Untried:

• Haven't tried Chipset JMB363 yet

I found out, that DosFlash uses different file structure for INQUIRY.BIN, SERIAL.BIN and the resulting DUMMY.BIN.

I also managed to extract the corresponding data from DosFlash files and (using a Hex-editor) convert them into a format JF can read.

However i am not confident with creating a DUMMY.BIN out of the converted files using JF. JF shows a warning telling there is information missing when building a DUMMY.BIN from single files (this warning is shown also for files dumped by JF itself).

I hope some of the experts here can shed some light into this whole matter - like if the drive key is sufficient to create an LT+ or if there are other parts actually needed from the OFW of my drive.

Thx in advance!

 

[cypher21]

drive key alone is NOT sufficient. You need the drive info as well

If slimkey fails, it's because you use an unsupported sata chipset

 

[unknown-9]

Hmm ... i heared already that chipsets are an issue for slim drives. I have successfully used the VIA chipset i mentioned above to flash several 74xxx (fat) liteons. What i get when trying to enter vendor mode is 0x51 and after flicking power i get 0x80 for 500ms or so and then it goes back to 0x51.

I have read some have hat success on JMicron chipsets. Maybe i will give the chipset i didnt try yet a chance before ordering an x360pro.

Although i think i have all the information needed extracted from the drive with DosFlash. If only the file formats were compatible... or maybe if JF implemented the Tarablinda method for data extraction. I suppose many chipset incompatibilities could be ruled out that way - I know a lot of people with alot more insight than i have are developing jf and have probably implemented best dump strategies already, but since dosflash 2.0 is pretty new, maybe JD could adopt this mechanism or make the data files compatible?

Addition: You speak of "unsupported" chipsets. I didn't find an "official" list of supported ones. Are there any officially recommended chipsets for slim drives? All i could find was this thread.

 

[cypher21]

that thread is the only place

we didn't make an official "supported" or "unsupported" list since there are too many different sata chipsets

only thing thats officially supported is the x360usb

Try different sata chipsets, if slimkey works, it works with the rest

Via definatly does NOT work well with locked slim drives

 

[lockpicker]

usbpro is the only way forward that u can be supported on here for

 

[unknown-9]

I succeeded reading the key using latest JF and ICH8. Now i am facing new troubles.... please check this out.