Jump to content


Photo

Dump Fail And Write Verification Fail


  • Please log in to reply
3 replies to this topic

#1 Argentum

Argentum

    X-S Enthusiast

  • Members
  • 3 posts

Posted 24 January 2012 - 12:34 AM

I have 2 Liteon 0225 winbond pcb unlocked using kamikaze and I am facing the following issues with.

The 1st one after unlocking it gave me 0x00 then failed to read and changed spi status to 0xBc (not 0x08c). after several tries I managed making it 0x8c and then 0x00 using alcohol. However at the end it fail's to Dump when I try to write

here is a log:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.90 Beta (293)
Session Started Tue Jan 24 00:01:17 2012

This is a 32 bit process running on 2 x 32 bit CPUs
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 3 I/O Ports.
Found 1 Com Ports.
Found 7 windows drives C: D: E: F: G: H: I:
Found 5 CD/DVD drives D: E: F: G: H:

XECUTER X360USB PRO attached.

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: 0xBC
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Spi Status: 0x8C
Sending Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000
Spi Status: 0xBC
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Spi Status: 0x8C
Spi Status: 0x8C
Sending Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000
Spi Status: 0xBC
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Sending Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0x0
Device ID: 0x0
Flash Name: Unknown type
Flash Size: n/a
Sending Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000
Spi Status: 0xBC
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Spi Status: 0x8C
Sending Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000
Spi Status: 0xBC
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes

Sending Spi Lock request to Port 0x0000
Spi Status: 0x8C

Sending Spi UnLock request to Port 0x0000
.......
Spi Status: 0x00
Loading firmware file C:\Users\Amgad El Khodiry\Xbox\Jungle Flasher\log\AEK0059cn.bin
MD5 hash: 05021ef500286e5929a545fa8dd801bf
Inquiry string found
Identify string found
Drive key @ 0xA030 51A44C1435876D78AD8CD9A1ED59D6FA
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: SlimKey Extract
Loading firmware file C:\Users\Amgad El Khodiry\Xbox\Jungle Flasher\log\Dummy.bin
MD5 hash: f737bcbddd3053a3983fdcea93656ae5
Inquiry string found
Identify string found
Drive key @ 0xA030 639D9E4DDE64C3123D2E9A9F0CB88875
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: SlimKey Extract
Auto-Loading firmware file C:\Users\Amgad El Khodiry\Xbox\Jungle Flasher\JungleFlasher v0.1.90 Beta (293)\firmware\LTPlus-0225-v2.0.bin
MD5 hash: 1012021472620cad9adf1f838497668e
Genuine LT plus v2.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: LT-Plus 2.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
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

The second one:
After unlocking it's spi status register is 0x03 in flash properties, although in the log it's 0x00 it writes but the write verification fails

And here is the log for 2nd:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.90 Beta (293)
Session Started Tue Jan 24 01:01:11 2012

This is a 32 bit process running on 2 x 32 bit CPUs
X360USB PRO detected, Version 0.18

Found 1 I/O Ports.
Found 1 Com Ports.
Found 6 windows drives C: D: E: F: G: H:
Found 5 CD/DVD drives D: E: F: G: H:

Drive is Slim Lite-On..

Key found in KeyDB at record (40 - N/A)
Key is: D2CD63F4C5ADD58ECCB1097C69538669
Key has been tested and verified, thanks C4eva !
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: 0x2C
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Spi Status: 0x8C
Spi Status: 0x8C.. Already locked !
Sending Vendor Intro to port 0x0000

Serial flash found with Status 0x72

Sending Device ID request to port 0x0000
Spi Status: 0x8C
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes

Sending Spi UnLock request to Port 0x0000
........
Spi Status: 0x00

Getting Status from port 0x0000
Loading firmware file C:\Users\Amgad El Khodiry\Xbox\Jungle Flasher\log\Dummy.bin
MD5 hash: f737bcbddd3053a3983fdcea93656ae5
Inquiry string found
Identify string found
Drive key @ 0xA030 639D9E4DDE64C3123D2E9A9F0CB88875
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: SlimKey Extract
Auto-Loading firmware file C:\Users\Amgad El Khodiry\Xbox\Jungle Flasher\JungleFlasher v0.1.90 Beta (293)\firmware\LTPlus-0225-v2.0.bin
MD5 hash: 1012021472620cad9adf1f838497668e
Genuine LT plus v2.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: LT-Plus 2.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
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: ................
Dumped in 4709mS

Write Verify Failed !

#2 krizalid

krizalid

    X-S Expert

  • Dev/Contributor
  • PipPipPip
  • 612 posts
  • Location:Mexico
  • Xbox Version:none
  • 360 version:v5.0 (360S - trinity)

Posted 24 January 2012 - 12:40 AM

When ever you're at this point


Writing target buffer to flash
Writing Bank 0: ................
Writing Bank 1: ................
Writing Bank 2: ................
Writing Bank 3: ................
....

Power off CK or whatever you use to power up your drive, wait 1 second and power back on, it will do the rest just fine.


This has been talked about quite a while and it should only happen on SATA chipsets, if you are using USBPro o Lizzard than this shouldn't happen.

Good luck!

#3 Argentum

Argentum

    X-S Enthusiast

  • Members
  • 3 posts

Posted 24 January 2012 - 01:18 AM

QUOTE(krizalid @ Jan 24 2012, 02:40 AM) View Post

This has been talked about quite a while and it should only happen on SATA chipsets, if you are using USBPro o Lizzard than this shouldn't happen.

Good luck!


Actually I am using X360 USB pro

#4 BoNg420

BoNg420

    X-S Messiah

  • Head Moderators
  • PipPipPipPipPipPipPip
  • 3,809 posts
  • Gender:Male
  • Location:USA
  • Xbox Version:none
  • 360 version:v5.0 (360S - trinity)

Posted 24 January 2012 - 02:30 PM

Sounds like a bad kamikaze.

Did you read and save the firmware before doing the kamikaze?

Does your drive still function at all? Eject?

When you are writing to the drive, does it move really slow, then when it goes on to the write verification it fails, if it does this most likely bad kamikaze.

Think the first one is a bad kamikaze, the one that doesnt even start the write verify. If it doesn't function after you write to it, assume its a bad kamikaze because it doesn't even take the write and the write dots move really slow, then its bad kamikaze for sure.

If the 2nd one works after writing and plays games, then you probably are ok, but for some reason it doesn't want to verify...

Edited by BoNg420, 24 January 2012 - 02:32 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users