LITEON DG-16D4S - SLIM Xbox 360 won't read games after xecuter 1.1 install

[Viper12004]

Hi, I installed a xecuter 1.1 pcb into two slim I have and after the install they both give me an unrecognized disk error 03-57-00. I tried two new lasers in both of them and I even tried replacing the worm motors. The one drive is a 9504 and I tried flashing with both the original 0272 and 3.0 firmware. The other is a 0225 drive and I tried both the original and 3.0 firmware with the same results. When I flashed them I also locked the spi on both drives and set the switch to lock. Both xbox worked fine before the install.

Thank you for any help.

USBPRO
CK3
Windows 7

 

[TilVl]

Well, you posted no pics or logs. Also you made two topics for some odd reason so obviously you have a hard time reading rules which would make me believe you didn't read the guide and missed a step. Please post as much information as possible. As JungleFlasher guides, hard ware and pics. Thank you.

 

[talby71]

maybe if you posted your Jungleflasher logs someone might be able to see what you have done

 

[Viper12004]

Well, you posted no pics or logs. Also you made two topics for some odd reason so obviously you have a hard time reading rules which would make me believe you didn't read the guide and missed a step. Please post as much information as possible. As JungleFlasher guides, hard ware and pics. Thank you.

Sorry, I was posting using my ipad and every time I would post it would just sit the spinning and do nothing in tapatalk. I retyped that thing 5 times.


I attached a log file from my last attempt.

Computer:
Dell XPS 400
Pentium D
4GB Ram
Windows 7 64bit
2 160GB HDD Raid 0

 

[copycatuk]

Are you trying your original games or your backed up games?

Also does your drive play dvd's fine ?

 

[Viper12004]

Are you trying your original games or your backed up games?

Also does your drive play dvd's fine ?

I tired about 30 original games and 5 backups. The only game that made a different error was an original black ops game me a 03-80-00 every time. Even DVD movies give me the same errors. Both of these consoles were on very old dashboards. There were never really played just sat on a shelf for over a year.

 

[copycatuk]

Tried putting the original pcb's back in there ?
Which dashboard is it ?
Dont know if this is any help
AFTER DASHBOARD UPDATE (13146) ALL SLIM 9504 LITEONS ARE NOW STOCK 0272 FW

Not flashed an xbox for a long long time so ignore me if i dribble

 

[printf(howdy)]

Doesn't appear you outro'd the drives?

EDIT - NM - I see it now. Looks like you only did it once. Maybe try it 3 or 4 times.

 

[Viper12004]

I did not try the stock pcb, the pcb for the 9504 is messed up and I didn't try they 0225 yet.


Sent from my iPad using Tapatalk HD

 

[Viper12004]

Hi, I just tried reinstalling my original pcb and now it gives the unrecognized disk 03-57-00. Any idea what would haven caused this issue?


Sent from my iPad using Tapatalk HD

 

[yoohoomat]

Did you make sure you used your DVD key with the board and do the correct steps it could cause the errors with not reading disk. I may be wrong but more info and picks would help narrow the problem down. I know I used the wrong key one time on jungleflasher it caused a similar issue with a pcb.

 

[Viper12004]

I only have one good original pcb so I cannot mix them up. I am just going to order a brand new drive and hope it works.


Sent from my iPad using Tapatalk HD

 

[stefff]

a log from jugleflasher would help alot..

both from what i can see you said that you have read the dummy.bin out of the drive, then cut out the original pcb from the dvd drive and put in a new replacement v1.1 pcb from tx, are you sure that all the wires are conneted the right way? did you intro to see the drive? did you remember to spoof the drive key and use the right cfw? did you remember to lock the drive and dobbel outro it when finished?

or just following the jungleflasher tut - http://jungleflasher.net/downloads.html "jungleflasher tut" it tells all what you need to know and what to do

 

[Viper12004]

a log from jugleflasher would help alot..

both from what i can see you said that you have read the dummy.bin out of the drive, then cut out the original pcb from the dvd drive and put in a new replacement v1.1 pcb from tx, are you sure that all the wires are conneted the right way? did you intro to see the drive? did you remember to spoof the drive key and use the right cfw? did you remember to lock the drive and dobbel outro it when finished?

or just following the jungleflasher tut - http://jungleflasher.net/downloads.html "jungleflasher tut" it tells all what you need to know and what to do

There is a log attached to my second post. It's the 4th post from the top. Yes I introed the drive, I also locked the drive with jungle flasher and outroed twice. I have done several other drives with the ****** unlock board. Probably about 20. Theses are the only two drives I have ever used the xecuter 1.1 on and happen to be my own. I tried all 3 firmware on them as a last resort and still had no success. I am waiting on a brand new replacement drive to see if that helps as I have no other slims here right now.


Sent from my iPad using Tapatalk HD

 

[Goldensavage]

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

JungleFlasher 0.1.92 Beta (304)

Session Started Wed Dec 26 20:25:51 2012



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

X360USB PRO detected, Version 0.18



Found 1 I/O Ports.

Found 0 Com Ports.

Found 5 windows drives C: D: E: F: G:

Found 2 CD/DVD drives D: E:



Drive is Slim Lite-On..



Key found in KeyDB at record (113 - My slim)

Key is: F7AAB402AEB9C009D0C47ADAF64884FA

Key has been tested and verified, thanks C4eva !

Sending Vendor Intro to port 0x0000



Serial flash found with Status 0x72



Sending Device ID request to port 0x0000

Spi Status: 0x8C

Manufacturer ID: 0xC2

Device ID: 0x11

Flash Name: MXIC(MX25L2005)

Flash Size: 262144 bytes

Loading firmware file G:\BACKUPS\My slim\Dummy.bin

MD5 hash: 25e4c217098f70a9ead47e13ec431707

Inquiry string found

Identify string found

Parse Failed !



Loading firmware file C:\Users\Rob\Desktop\JungleFlasher.0.1.92.Beta(304)\JungleFlasher v0.1.92 Beta (304)\firmware\Orig-0272.bin

MD5 hash: 371cb1cdf0c953534cbca83c6930abb9

Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

Firmware Osig: [PLDS DG-16D4S 0272]

Firmware is: Stock

Loading firmware file G:\BACKUPS\My slim\Dummy.bin

MD5 hash: 25e4c217098f70a9ead47e13ec431707

Inquiry string found

Identify string found

Drive key @ 0xA030 F7AAB402AEB9C009D0C47ADAF64884FA

Firmware Osig: [PLDS DG-16D4S 0272]

Firmware is: SlimKey Extract

Spoofing Target

DVD Key copied to target

Key Sector copied from Source to Target

Target is LT - ID strings not copied to Target





Sending Spi UnLock request to Port 0x0000

.

Spi Status: 0x00



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 Spi Lock request to Port 0x0000

Spi Status: 0x8C

Sending Vendor Outro to port 0x0000

Sending Vendor Outro to port 0x0000

Drive is Slim Lite-On..



Key found in KeyDB at record (113 - My slim)

Key is: F7AAB402AEB9C009D0C47ADAF64884FA

Key has been tested and verified, thanks C4eva !

Sending Vendor Intro to port 0x0000

Status 0x80

Re-sending Vendor Intro:

..

Serial flash found with Status 0x72



Sending Device ID request to port 0x0000

Spi Status: 0x00

Manufacturer ID: 0xC2

Device ID: 0x11

Flash Name: MXIC(MX25L2005)

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 Spi Lock request to Port 0x0000

Spi Status: 0x8C

Sending Vendor Outro to port 0x0000

Drive is Slim Lite-On..



Key found in KeyDB at record (113 - My slim)

Key is: F7AAB402AEB9C009D0C47ADAF64884FA

Key has been tested and verified, thanks C4eva !

Drive is Slim Lite-On..



Key found in KeyDB at record (106 - New folder)

Key is: 1EC1018B6536AA72C54924FDB3B9FD21

Key has been tested and verified, thanks C4eva !





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 34 53 - 20 20 20 20 20 20 20 20 DG-16D4S

0020: 30 32 32 35 00 00 00 00 - 00 00 00 00 00 00 00 00 0225............

0030: 00 00 00 00 41 30 41 30 - 00 00 00 00 00 00 00 00 ....A0A0........

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 ................

0060: 44 37 31 34 43 47 30 34 - 30 39 31 30 30 30 30 48 D714CG040910000H

0070: 54 20 20 20 T



Sending Vendor Intro to port 0x0000



Serial flash found with Status 0x72



Sending Device ID request to port 0x0000

Manufacturer ID: 0xEF

Device ID: 0x11

Flash Name: Winbond/NEX(W25P20/NX25P20)

Flash Size: 262144 bytes

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

Key: 1EC1018B6536AA72C54924FDB3B9FD21 is verified, Thanks C4eva



Grabbing Key sector: ................

Key Sector verified.

Grabbing Serial info: ........



Drive is Slim Lite-On..



Key found in KeyDB at record (106 - New folder)

Key is: 1EC1018B6536AA72C54924FDB3B9FD21

Key has been tested and verified, thanks C4eva !

Key data saved to G:\BACKUPS\0718417\04308\New folder (2)\Key.bin



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 34 53 - 20 20 20 20 20 20 20 20 DG-16D4S

0020: 30 32 32 35 00 00 00 00 - 00 00 00 00 00 00 00 00 0225............

0030: 00 00 00 00 41 30 41 30 - 00 00 00 00 00 00 00 00 ....A0A0........

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 ................

0060: 44 37 31 34 43 47 30 34 - 30 39 31 30 30 30 30 48 D714CG040910000H

0070: 54 20 20 20 T



Inquiry String saved to G:\BACKUPS\0718417\04308\New folder (2)\Inquiry.bin



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

0010: 00 00 00 00 37 44 34 31 - 47 43 34 30 39 30 30 31 ....7D41GC409001

0020: 30 30 48 30 20 54 20 20 - 00 00 00 00 00 00 32 30 00H0 T ......20

0030: 35 32 20 20 20 20 4C 50 - 53 44 20 20 20 20 47 44 52 LPSD GD

0040: 31 2D 44 36 53 34 20 20 - 20 20 20 20 20 20 00 00 1-D6S4 ..

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

0060: 00 00 00 0F 00 40 00 04 - 00 02 06 00 00 00 00 00 [email protected]

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

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

0090: 00 00 F8 00 10 02 00 00 - 02 02 00 00 60 00 40 00 ............`[email protected]

00A0: F8 00 10 02 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

00B0: 3F 20 00 00 ? ..



Identify String saved to G:\BACKUPS\0718417\04308\New folder (2)\Identify.bin



0000: 44 37 31 34 43 47 30 34 - 30 39 31 30 30 30 30 48 D714CG040910000H

0010: 54 20 20 20 FF FF FF FF - 30 48 32 37 30 33 34 35 T ....0H270345

0020: 31 36 36 38 31 35 58 58 - 41 30 FF FF 53 34 50 30 166815XXA0..S4P0

0030: 39 32 34 30 30 30 30 30 - 30 38 37 36 30 32 00 00 92400000087602..

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



Serial String saved to G:\BACKUPS\0718417\04308\New folder (2)\Serial.bin



Hashing Drive: ................



Dummy.bin file saved to Dummy.bin

Loading firmware from buffer

Inquiry string found

Identify string found

Drive key @ 0xA030 1EC1018B6536AA72C54924FDB3B9FD21

Firmware Osig: [PLDS DG-16D4S 0225]

Firmware is: SlimKey Extract

Key database updated



Auto-Loading firmware file C:\Users\Rob\Desktop\JungleFlasher.0.1.92.Beta(304)\JungleFlasher v0.1.92 Beta (304)\firmware\LTPlus-0225-v3.0.bin

MD5 hash: 1a38d3a2a6519339599fa1866642c513

Genuine LT plus v3.0

Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

Firmware Osig: [PLDS DG-16D4S 0225]

Firmware is: LT-Plus 3.0

Spoofing Target

DVD Key copied to target

Key Sector copied from Source to Target

Target is LT - ID strings not copied to Target





Getting Status from port 0x0000

Invalid Status 0x0

Sending Vendor Intro to port 0x0000

Status 0x51

Re-sending Vendor Intro:

.

Serial flash found with Status 0x72



Sending Device ID request to port 0x0000

Spi Status: 0x8C

Manufacturer ID: 0xC2

Device ID: 0x11

Flash Name: MXIC(MX25L2005)

Flash Size: 262144 bytes



Sending Spi UnLock request to Port 0x0000

.

Spi Status: 0x00



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 Spi Lock request to Port 0x0000

Spi Status: 0x8C

Sending Vendor Outro to port 0x0000

Sending Vendor Outro to port 0x0000

Drive is Slim Lite-On..



Key found in KeyDB at record (106 - New folder (2))

Key is: 1EC1018B6536AA72C54924FDB3B9FD21

Key has been tested and verified, thanks C4eva !


I have highlighted why the reason might be, for some reason it changes keys half way through after you flash the drive originally, whether down to a wrong click or something else. But i think you may have the wrong key on it.

Flash again with the original read .bin

 

[Viper12004]

There is two keys because I tried it on two different xbox slims. I tired the original dump and had no success.


Sent from my iPad using Tapatalk HD

 

[Goldensavage]

Well its one key for each 360. Make sure you have the correct key for that 360.

 

[Viper12004]

I fixed both consoles. It was bad worm motors. I swapped them with fat lite on/benq motors and now they work great. I know t is one key per Xbox I have flashed over 5,000 consoles.


Sent from my iPad using Tapatalk HD

 

[Goldensavage]

I fixed both consoles. It was bad worm motors. I swapped them with fat lite on/benq motors and now they work great. I know t is one key per Xbox I have flashed over 5,000 consoles.


Sent from my iPad using Tapatalk HD

Sorry for stating the obvious, but not everybody does, which is why i said it.

It is good to know you got them working...