I think i just messed up big time..I flashed my 9504 with the LTPlus 0225 1.9 firmware! when i think i was suppose to use the LTPlus 0272....now my drive is locked... Anyway to unlock since i already have it dumped? Or i'm i just Screwed? My Dashboard verison is 2.0.13146.0 so i haven't updated to new dash yet. can somebody help me out?
LITEON 9504 Slim Ltplus flash gone wrong!
- Thread starter eric4179
- Start date
your drive isn't locked 0225 firmware and 0272 are pretty much the same it might have been a mistake but certainly not a bad one just reflash the drive with 0272 lt+ and your done why would it be locked if you haven't updated? 0225 firmware does not just lock your drive only if you updated or you locked it somehow it would be locked.
Opps!
As long as you still got the key or can get the key.bin off the drive you are set!
You will have to either buy the expensive unlock PCB...
Or!! The new russian method, involving cut and solder:
http://team-xecuter.com/forums/showthread.php?t=67810
But then thinking it shouldn't of locked... Try reflashing it with 0272 LT+ firmware
As long as you still got the key or can get the key.bin off the drive you are set!
You will have to either buy the expensive unlock PCB...
Or!! The new russian method, involving cut and solder:
http://team-xecuter.com/forums/showthread.php?t=67810
But then thinking it shouldn't of locked... Try reflashing it with 0272 LT+ firmware
This what happens when i try unlock slim button.....
Drive properties
vendor: PLDS
F/W Rev: 0225
Reserved: A0a0
So i hit slim Unlock:
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 31 43 47 30 31 - 36 38 30 31 30 30 39 50 D711CG016801009P
0070: 4A 20 20 20 J
Sending Password to Drive on port 0xEF00
Slim-Un-lock command returned an error
unlock failed!
----------------------------------------
intro/ devise ID is also a no go!
Here is a copy of the jf.log as u can see at the end Authorisation Failed!
and Restore Verify Failed! i think thats why it's messed up!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.85 Beta (257)
Session Started Wed Jul 20 17:01:46 2011
This is a 32 bit process running on 2 x 32 bit CPUs
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 8 I/O Ports.
Found 0 Com Ports.
Found 4 windows drives C: D: E: F:
Found 1 CD/DVD drives D:
Loading firmware file C:\Users\User\Desktop\Xbox 360 Software\Xbox360 firmware Bin\My slim 9504\Lite-OFW.bin
MD5 hash: e79a562420f97010b86c3ffee6460651
Drive key @ n/a F0F166AD030AC097C25786E88C680839
Firmware Osig: [PLDS DG-16D4S 9504]
Firmware is: Stock
Loading firmware file C:\Users\User\Desktop\Xbox 360 Software\JungleFlasher v0.1.85 Beta (257)\firmware\LTPlus-0225-v1.9.bin
MD5 hash: 693cfff56a632029f008295b06ce1021
Genuine LT plus v1.9
Drive key @ n/a D53B9CA4511C9BCFA5C31123166A5829
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: LT-Plus 1.9
Spoofing Target
DVD Key copied to target
Key Sector copied from Source to Target
Target is LT - ID strings not copied to Target
Drive is Slim Lite-On..
Key found in KeyDB at record (12 - Desktop)
Key is: F0F166AD030AC097C25786E88C680839
Key has been tested and verified, thanks C4eva !
Drive is Slim Lite-On..
Key found in KeyDB at record (12 - Desktop)
Key is: F0F166AD030AC097C25786E88C680839
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: 39 35 30 34 00 00 00 00 - 00 00 00 00 00 00 00 00 9504............
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 31 43 47 30 31 - 36 38 30 31 30 30 39 50 D711CG016801009P
0070: 4A 00 00 00 J...
Sending Password to Drive on port 0xEF00
Done!
Sending Vendor Intro to port 0xEF00
Serial flash found with Status 0x72
Sending Device ID request to port 0xEF00
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Getting Status from port 0xEF00
SPi flash found with Status 0x72
Sending Chip Erase to Port 0xEF00
Erasing:
Done !
Getting Status from port 0xEF00
SPi flash found with Status 0x72
Sending Chip Erase to Port 0xEF00
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: ................
Dumped in 1935mS
Write verified OK !
Restoring sector 0x3E000.
Sending Sector Erase to Port 0xEF00
Erasing: 0x3E000
Writing: 0x3E000
............
Authorisation Failed!
Restore Verify Failed !
Sending Vendor Intro to port 0xEF00
Status 0x51
Re-sending Vendor Intro:
..........................
Drive properties
vendor: PLDS
F/W Rev: 0225
Reserved: A0a0
So i hit slim Unlock:
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 31 43 47 30 31 - 36 38 30 31 30 30 39 50 D711CG016801009P
0070: 4A 20 20 20 J
Sending Password to Drive on port 0xEF00
Slim-Un-lock command returned an error
unlock failed!
----------------------------------------
intro/ devise ID is also a no go!
Here is a copy of the jf.log as u can see at the end Authorisation Failed!
and Restore Verify Failed! i think thats why it's messed up!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.85 Beta (257)
Session Started Wed Jul 20 17:01:46 2011
This is a 32 bit process running on 2 x 32 bit CPUs
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 8 I/O Ports.
Found 0 Com Ports.
Found 4 windows drives C: D: E: F:
Found 1 CD/DVD drives D:
Loading firmware file C:\Users\User\Desktop\Xbox 360 Software\Xbox360 firmware Bin\My slim 9504\Lite-OFW.bin
MD5 hash: e79a562420f97010b86c3ffee6460651
Drive key @ n/a F0F166AD030AC097C25786E88C680839
Firmware Osig: [PLDS DG-16D4S 9504]
Firmware is: Stock
Loading firmware file C:\Users\User\Desktop\Xbox 360 Software\JungleFlasher v0.1.85 Beta (257)\firmware\LTPlus-0225-v1.9.bin
MD5 hash: 693cfff56a632029f008295b06ce1021
Genuine LT plus v1.9
Drive key @ n/a D53B9CA4511C9BCFA5C31123166A5829
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: LT-Plus 1.9
Spoofing Target
DVD Key copied to target
Key Sector copied from Source to Target
Target is LT - ID strings not copied to Target
Drive is Slim Lite-On..
Key found in KeyDB at record (12 - Desktop)
Key is: F0F166AD030AC097C25786E88C680839
Key has been tested and verified, thanks C4eva !
Drive is Slim Lite-On..
Key found in KeyDB at record (12 - Desktop)
Key is: F0F166AD030AC097C25786E88C680839
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: 39 35 30 34 00 00 00 00 - 00 00 00 00 00 00 00 00 9504............
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 31 43 47 30 31 - 36 38 30 31 30 30 39 50 D711CG016801009P
0070: 4A 00 00 00 J...
Sending Password to Drive on port 0xEF00
Done!
Sending Vendor Intro to port 0xEF00
Serial flash found with Status 0x72
Sending Device ID request to port 0xEF00
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Getting Status from port 0xEF00
SPi flash found with Status 0x72
Sending Chip Erase to Port 0xEF00
Erasing:
Done !
Getting Status from port 0xEF00
SPi flash found with Status 0x72
Sending Chip Erase to Port 0xEF00
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: ................
Dumped in 1935mS
Write verified OK !
Restoring sector 0x3E000.
Sending Sector Erase to Port 0xEF00
Erasing: 0x3E000
Writing: 0x3E000
............
Authorisation Failed!
Restore Verify Failed !
Sending Vendor Intro to port 0xEF00
Status 0x51
Re-sending Vendor Intro:
..........................
It looks locked to me, i haven't worked with many locked ones and am only just recently been fiddling with the russian method, if your confident enough it might be your best shot
Getting Status from port 0xEF00
SPi flash found with Status 0x72
Sending Chip Erase to Port 0xEF00
Erasing:
Done !
Getting Status from port 0xEF00
SPi flash found with Status 0x72
Sending Chip Erase to Port 0xEF00
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: ................
Dumped in 1935mS
Write verified OK !
How could it even get that far with drive locked and even say the write is OK! have you tried any games in it and what not it even says SPi found with status 0x72 so it looks unlocked to me with a locked drive i have never seen it go that far in the process seems odd to me
If you really have not updated to get the drive locked there is no way it can be locked
SPi flash found with Status 0x72
Sending Chip Erase to Port 0xEF00
Erasing:
Done !
Getting Status from port 0xEF00
SPi flash found with Status 0x72
Sending Chip Erase to Port 0xEF00
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: ................
Dumped in 1935mS
Write verified OK !
How could it even get that far with drive locked and even say the write is OK! have you tried any games in it and what not it even says SPi found with status 0x72 so it looks unlocked to me with a locked drive i have never seen it go that far in the process seems odd to me
If you really have not updated to get the drive locked there is no way it can be locked
Last edited:
whataretheyfeedingyou
VIP Member
whataretheyfeedingyou
VIP Member
I fixed it guys and most of u all were right! here is what i did:
1. power off the drive
2. click intro ... make sure that in the same group box that .... Phat ( ) (*) Slim is selected
3. Click yes, to resend vendor intro
4. Now probe the MPX01 point with a probe attached to ground, T-X Probe 3 does exactly this.
5. power on the drive and remove the probe after 1 or 2 seconds
6. Drive should no be in vendor mode.
Hope this help other....
1. power off the drive
2. click intro ... make sure that in the same group box that .... Phat ( ) (*) Slim is selected
3. Click yes, to resend vendor intro
4. Now probe the MPX01 point with a probe attached to ground, T-X Probe 3 does exactly this.
5. power on the drive and remove the probe after 1 or 2 seconds
6. Drive should no be in vendor mode.
Hope this help other....
I fixed it guys and most of u all were right! here is what i did:
1. power off the drive
2. click intro ... make sure that in the same group box that .... Phat ( ) (*) Slim is selected
3. Click yes, to resend vendor intro
4. Now probe the MPX01 point with a probe attached to ground, T-X Probe 3 does exactly this.
5. power on the drive and remove the probe after 1 or 2 seconds
6. Drive should no be in vendor mode.
Hope this help other....
I get that far but i only get flash name unknown
and flash size n/a spi status 0xff device ID 0xff please help