LITEON DG-16D2S System restarts when any disc (backup or retail) is inserted.

E

exseptember

Junior Member
Aug 6, 2011
13
0
Michigan, USA
Okay, I know this stuff is years old, which is probably why I'm having problems. I recently acquired an old phat and decided to flash it for the heck of it. I flashed my slim a few years back when LT+ first hit it, and decided against all the experimental stuff when M$ enabled write protection. Now I'm back in the scene, and have immediately hit an obstacle.

After plenty of research (this old stuff is hard to find sometimes!), some tech support from my brother (made me a probe--the slim didn't need these things!) some finagling (my new rig with Win 8 didn't like my x360USB pro, and refused to update the firmware or communicate in Jflasher--had to find an old Win 7 laptop to update and flash on), I finally got a clean flash onto my drive. As far as I can tell, at least. Log looked exactly the same as any other flash I've done, and exactly the same as the tutorial.

Popped it back into the Xbox, and now it just restarts to dashboard every time any disc is inserted. My thoughts:

1. Maybe I screwed something up with the probing, even though the flashing went smoothly.
2. Maybe our homemade probe shorted something? Should we pull our hardware back out of the power cable?
3. Maybe I ought to just flash back to stock and see if that fixes it? Try again from scratch? If so, what is the proper stock now for the DG-16D2S? The drive label says the FW is 74850C, but somewhere along the way I read that M$ flashed new FW onto these in some dash update. Could use some clarity in that department, definitely--maybe I just flashed the wrong FW onto it in my confusion (Although I just let JFlasher auto-choose my LT+ version).

I know I probably sound dumb asking this stuff, but I've been out of the loop for a bit, and I never flashed a phat. At least I didn't end up with a Hitachi 0_0. If it does turn out I screwed up the whole thing, no big loss. It's just a pet project.

Thanks in advance for any assistance, I can post any information you need (I would have if I knew what mattered :p).

EDIT: JF Log!









~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


JungleFlasher 0.1.96 Beta (323)


Session Started Thu Nov 07 18:04:15 2013






This is a Wow 64 process running on 2 x 64 bit CPUs


portio64.sys Driver not Installed


Found 0 I/O Ports.


Found 0 Com Ports.


Found 3 windows drives C: D: E:


Found 0 CD/DVD drives






XECUTER X360USB PRO attached.






XECUTER X360USB PRO removed.






XECUTER X360USB PRO attached.






Drive is Lite-On..


Drive is Lite-On..


Sending Vendor Intro to port 0x0000


Status 0x51


Re-sending Vendor Intro:


.........


Serial flash found with Status 0x52






Extracted drive key passed Verification !






key returned: FA2BE6DAEF72343539CA9BB56A9EE460


0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS


0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S


0020: 30 32 35 31 30 43 41 30 - 41 30 44 36 30 38 43 47 02510CA0A0D608CG


0030: 37 33 38 38 30 38 30 30 - 33 34 38 20 20 20 00 00 73880800348 ..


0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................


0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................






0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS


0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S


0020: 30 32 35 31 30 43 20 20 - 00 00 00 00 00 00 00 00 02510C ........


0030: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................


0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................


0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................






0000: C0 85 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................


0010: 00 00 00 00 44 36 30 38 - 43 47 37 33 38 38 30 38 ....D608CG738808


0020: 30 30 33 34 38 20 20 20 - 00 00 00 00 00 00 32 30 00348 ......20


0030: 31 35 43 30 20 20 4C 50 - 53 44 20 20 20 20 47 44 15C0 LPSD GD


0040: 31 2D 44 36 53 32 20 20 - 20 20 20 20 20 20 20 20 1-D6S2


0050: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 00 00 ..


0060: 00 00 00 0B 00 00 00 04 - 00 02 06 00 00 00 00 00 ................


0070: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................


0080: 03 00 78 00 78 00 E3 00 - 78 00 00 00 00 00 00 00 ..x.x...x.......


0090: 00 00 00 00 00 00 00 00 - 02 02 00 00 68 00 00 00 ............h...


00A0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................


00B0: 20 20 00 00 ..






0000: 44 36 30 38 43 47 37 33 - 38 38 30 38 30 30 33 34 D608CG7388080034


0010: 38 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 8 ............


0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......


0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................


0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 30 FF FF ............A0..






Loading firmware from buffer


Inquiry string found


Identify string found


Drive key @ 0xA030 FA2BE6DAEF72343539CA9BB56A9EE460


Firmware Osig: [PLDS DG-16D2S 0251]


Firmware is: PhatKey Extract


Key added to database






Auto-Loading firmware file C:\Users\User\Desktop\JungleFlasher v0.1.96 Beta (323)\firmware\LTPlus-0251-v3.0.bin


MD5 hash: d14fe82b96741b7a18e5c1e7adbf0a98


Genuine LT plus v3.0


Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF


Firmware Osig: [PLDS DG-16D2S 0251]


Firmware is: LT-Plus 3.0


Spoofing Target


DVD Key copied to target


Target is LT - ID strings not copied to Target


Serial data already matches






Target rev is LT 02510C, serial info not copied






Sending Lite-On-Erase request to port 0x0000


..............


Drive returned Status 0x0


...


Serial flash found with Status 0x72


Manufacturer ID: 0xEF


Device ID: 0x11


Flash Name: Winbond/NEX(W25P20/NX25P20)


Flash Size: 262144 bytes






Getting Status from port 0x0000


SPi flash found with Status 0x72






Sending Chip Erase to Port 0x0000


Erasing:


Writing target buffer to flash


Writing Bank 0: ................


Writing Bank 1: ................


Writing Bank 2: ................


Writing Bank 3: ................






Flash Verification Test !


Reading Bank 0: ................


Reading Bank 1: ................


Reading Bank 2: ................


Reading Bank 3: ................


Write verified OK !






Sending Vendor Outro to port 0x0000


Drive is Lite-On..






Key found in KeyDB at record (1 - N/A)


Key is: FA2BE6DAEF72343539CA9BB56A9EE460


Key has been tested and verified, thanks C4eva !


XECUTER X360USB PRO removed.
 
Last edited:
gazcoigne

gazcoigne

BANNED
Jan 31, 2005
1,106
0
Belfast, UK
What kernel version is on the console?

Sounds exactly like a fw mismatch.

Flash a stock 74850 fw with your key to the drive and update to the latest fw then flash lt3.0 to the drive
 
Taijigamer2

Taijigamer2

VIP Member
Jun 8, 2013
1,292
0
England
Have u read the jungleflasher PDF and the in depth guide on this site? If your dashboard is post 13149 (I think) your 16d2s firmware will be 02510. Lt+ 3.0. Read the tuts. Then flash back to stock, if games boot then retrace steps through jungleflasher armed with fresh info. Good luck.

Edit: ok the guys have completely beat me to it. Lols. :p
 
Last edited:
E

exseptember

Junior Member
Aug 6, 2011
13
0
Michigan, USA
Taijigamer2 said:
Have u read the jungleflasher PDF and the in depth guide on this site? If your dashboard is post 13149 (I think) your 16d2s firmware will be 02510. Lt+ 3.0. Read the tuts. Then flash back to stock, if games boot then retrace steps through jungleflasher armed with fresh info. Good luck.
Click to expand...
I read as much as possible before attempting flashing; the possibility of something going horribly wrong with the probe seemed too great for me to go in uneducated. I will try a fresh flash soon--just wanted to hear what the experts had to say first! :)
 
E

exseptember

Junior Member
Aug 6, 2011
13
0
Michigan, USA
Well, now I can't get it back into vendor mode. As soon as I hit Intro, the message comes up to resend the command and then it doesn't register my probe. Will keep trying :/

Edit: Got it, forgot you don't have to get it in vendor mode to erase. Will test retails now.
 
Last edited:
E

exseptember

Junior Member
Aug 6, 2011
13
0
Michigan, USA
Outro command doesn't verify anything after I receive "write verified OK!", and all drive properties have disappeared. I tried flashing twice. Is this normal for stock?

Edit: Yeah, I can't achieve a "complete" flash unless I use LT+, and I am still experiencing the same error on every LT+ flash. I'm using "orig-02510C-1c000.bin" found in "Stock" for my target, that is the correct one, yes?
 
Last edited:
Taijigamer2

Taijigamer2

VIP Member
Jun 8, 2013
1,292
0
England
Hmm. I had this with a 16d2s. Would write and verify but not show after outro. Tried reflashing numerous times. I concluded I must have damaged the ic somehow. This may not be the case with your drive though.
 
WildCard007

WildCard007

VIP Member
Feb 27, 2013
285
0
USA
I would try loading your dummy in the source. Once the DVD key becomes visible, select it with the mouse and copy it to notepad or something. Click Open Source Firmware, when the Source Firmware Box appears click cancel. That will clear out the source section. Then load up the stock firmware in the target slot, click manual spoofing, paste your DVD Key then click Check then click OK. After that try to flash it.
 
  • Like
Reactions: exseptember
You must log in or register to reply here.