0401 MXIC Locking Up

J

Johnny8675309

VIP Member
Feb 9, 2011
232
0
Palm Springs CA
I'm trying to flash my first slim an on occasion I manage to get the "write" portion to work although it takes a minute. Here is my JF log with notes about that portion of the log between asterisks

HTML: 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.92 Beta (304)
Session Started Thu Mar 29 21:13:24 2012

This is a 32 bit process running on a 32 bit CPU 
X360USB PRO detected, Version 0.18

Found 1 I/O Ports.
Found 1 Com Ports.
Found 4 windows drives A: C: D: F:
Found 1 CD/DVD drives D:

Loading firmware file F:\360\Dumps\DVD Key\GoW Dump\Dummy.bin
MD5 hash:  40dc6f2871cb0fc5d73726aff1ba5b9f
Inquiry string found
Identify string found
Drive key @ 0xA030 CED3B38F493E5E0BFECE1C5960D5FE84
Firmware Osig: [PLDS    DG-16D4S        0401]
Firmware is:  SlimKey Extract                 
Loading firmware file F:\360\Dumps\DVD Key\GoW Dump\Dummy.bin
MD5 hash:  40dc6f2871cb0fc5d73726aff1ba5b9f
Inquiry string found
Identify string found
Parse Failed !

Loading firmware file C:\Documents and Settings\User\My Documents\Latest_iXtreme_and_Stock_Firmware_Pack\Firmware\LTPlus-0401-v3.0.bin
MD5 hash:  87fba52607d01d3c73722f9f818588c9
Genuine LT plus v3.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS    DG-16D4S        0401]
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

Sending Vendor Intro to port 0x0000 **No Drive Detected**
Status 0x80
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 Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000 **Probe DIP switch default**
Spi Status: 0x8C
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name:  MXIC(MX25L2005)
Flash Size:  262144 bytes
Sending Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000 **Probe DIP switch 1 "On"**
Spi Status: 0x8C 
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name:  MXIC(MX25L2005)
Flash Size:  262144 bytes
Sending Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000 **Probe DIP switch 2 "On"
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: . **Frozen**

So then I restart JF and continue the process after unplugging the X360USB Pro and another intro to detect the drive

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.92 Beta (304)
Session Started Thu Mar 29 21:35:37 2012

This is a 32 bit process running on a 32 bit CPU 
X360USB PRO detected, Version 0.18

Found 1 I/O Ports.
Found 1 Com Ports.
Found 4 windows drives A: C: D: F:
Found 1 CD/DVD drives D:

Loading firmware file F:\360\Dumps\DVD Key\GoW Dump\Dummy.bin
MD5 hash:  40dc6f2871cb0fc5d73726aff1ba5b9f
Inquiry string found
Identify string found
Drive key @ 0xA030 CED3B38F493E5E0BFECE1C5960D5FE84
Firmware Osig: [PLDS    DG-16D4S        0401]
Firmware is:  SlimKey Extract                 
Loading firmware file C:\Documents and Settings\User\My Documents\Latest_iXtreme_and_Stock_Firmware_Pack\Firmware\LTPlus-0401-v3.0.bin
MD5 hash:  87fba52607d01d3c73722f9f818588c9
Genuine LT plus v3.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS    DG-16D4S        0401]
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

Sending Vendor Intro to port 0x0000 **Initial Intro**
Status 0x80
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 Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000 **DIP Switch 3 "On" - Probe removed after I saw Spi Status**
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
Spi is locked, Aborting!

Getting Status from port 0x0000 **Replaced Probe and held it there during write**
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: Dump Failed
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: 0x8C
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name:  MXIC(MX25L2005)
Flash Size:  262144 bytes
Sending Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000 **DIP Switch 4 "On" 
Spi Status: 0x88
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name:  MXIC(MX25L2005)
Flash Size:  262144 bytes
I'm not entirely sure where I'm going wrong here it seems like I've tried everything if anyone could help me out I would really appreciate it since I've tried each switch position and also checked for continuity.:confused:
 
Last edited by a moderator:
D

doe1200

VIP Member
Feb 21, 2011
460
48
northern ireland
post pics of pcb are you using the sputnik add on with the sputnik probe,are have you just cut the trace and probeing the hole,are you also pushing down on the probe
 
Last edited:
A

Argentum

VIP Member
Dec 13, 2011
388
0
Khobar, Saudi Arabia
Post pics of the board
 
J

Johnny8675309

VIP Member
Feb 9, 2011
232
0
Palm Springs CA
Slim is checked during both Intro and Write processes. Only using the probe if I'm not mistaken the switch was designed for the end user where as the probe itself was for modders for efficiency. I bought it a while back just haven't had anyone bring me a slim. Yes the trace cut is all the way through each pass I made was tested with a multimeter to check for continuity. I slipped with the knife twice but nothing was damaged the enamel was just scratched which will be fixed after the flash is complete. This thing is driving me up the wall.
 
D

doe1200

VIP Member
Feb 21, 2011
460
48
northern ireland
set the probe to 10 intro put the drive in vendor mode press spi button press yes hold in button probe point release button on probe when you get 0x00 status remove probe,have your frimware loaded in frimware tool 32 then reintro again to see if the status stays at 0x00,if it does try and write the frimware
 
Last edited:
  • Like
Reactions: Johnny8675309
A

Argentum

VIP Member
Dec 13, 2011
388
0
Khobar, Saudi Arabia
Wait you said you held the probe during write ?! you should not

just select the right resistance usually 10 into the drive, make sure you get 0x72 and good flash properties then press 0x8c button

and probe once unlocked 0x00 remove probe then read write with probe removed
 
  • Like
Reactions: Johnny8675309
J

Johnny8675309

VIP Member
Feb 9, 2011
232
0
Palm Springs CA
Alright finally got it to work first try this time. I don't know what I was thinking yesterday holding it there:crazy: However I did attempt to take it off after the intro just forgot to hit the SPI button as it already said 0x00. Thank you very much for all your help. :redface:
 
A

Argentum

VIP Member
Dec 13, 2011
388
0
Khobar, Saudi Arabia
Johnny8675309 said:
Alright finally got it to work first try this time. I don't know what I was thinking yesterday holding it there:crazy: However I did attempt to take it off after the intro just forgot to hit the SPI button as it already said 0x00. Thank you very much for all your help. :redface:
Click to expand...
I am glad you got yourself sorted out

don't forget to press thanks for the people who helped you
 
You must log in or register to reply here.