LITEON DG-16D4S - SLIM JF returns "Write Verify Failed" when attempting to write to LTU2 PCB

iomega311

Full Member
Dec 9, 2011
92
8
Arizona, USA
I have searched for a solution before posting... I can't find anything that is helping me fix this.

I have a 0225 Trinity that I bought without a DVD drive in it. The previous owner messed up the drive while trying to do the Kamakazi on it as well as RGH it. I was able to RGH it and get the CPU key and DVD key off of it.
I was able to extract the C-R.bin and key.bin out of the NAND as well.
It is currently on a really old dash. Is on 13599.
I wanted to get this back to stock with a DVD drive. I have a spare drive for it and just got my LTU2 board today.

I am using the most recent version of JF. Is v0.1.96 Beta (323).
I am doing this on my laptop via a Windows 7 virtual machine. (Windows 8 is the host OS)

I am using a USB Pro V1 and CK3 mini for power. Am powering via molex from my desktop PC.

Now that all of that info is out of the way...
I am able to get the LTU2 board into vendor mode with ease. I am able to build the FW image with ease. But when I attempt to write it, it writes to all 4 banks and then returns "Write Verify Failed".
I still have been sending the Outro command as well as locking via SPI and with the physical switch on my PCB.

The console boots without the drive just fine... other than the middle light flashes green because there is no drive detected.
But when I attach the disk drive, it will not boot up to the dash. Screen stays black and then the center light starts flashing.

This tells me that the FW is not writing correctly (at least, I think that's the case).

Here are my JF logs:

**********************************









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


JungleFlasher 0.1.96 Beta (323)


Session Started Fri Dec 27 20:58:50 2013






This is a Wow 64 process running on a 64 bit CPU


X360USB PRO detected, Version 0.18






New CD/DVD detected.


Found drive A: - Removable.


Found drive C: - Hard Drive.


Found drive D: - CD/DVD.


Found drive E: - Removable.


Found drive F: - Removable.


No Hitachi drives were found!


portio64.sys Driver not Installed


Found 1 I/O Ports.


Found 2 Com Ports.


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


Found 1 CD/DVD drives D:






Loading firmware file C:\Users\Me\Desktop\Xbox\JungleFlasher v0.1.96 Beta (323)\firmware\LTU2-0225-v1.0.bin


MD5 hash: d6ab7ccd7bbc1301762e6eff602afac3


Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF


Firmware Osig: [PLDS DG-16D4S 0225]


Firmware is: LTU2 v1.0






re-parseing file


Loading firmware from buffer


Drive key @ n/a XXXXXXXXXXXXXXXXXXXXXXXXXXX


Firmware Osig: [PLDS DG-16D4S 0225]


Firmware is: LTU2 v1.0






Stage 1 failed


Key Verification Failed !!


Additional extracts not completed.






Target f/w saved as: Restore2Stock.bin


XECUTER X360USB PRO removed.






XECUTER X360USB PRO attached.






Drive is Slim Lite-On..


Sending Vendor Intro to port 0x0000


Status 0x90


Re-sending Vendor Intro:


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


Serial flash found with Status 0x72






Sending Device ID request to port 0x0000


Spi Status: 0x00


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: ..Write Verify Failed !


Sending Vendor Outro to port 0x0000


Drive is Slim Lite-On..

*****************************************

Any and all help is much appreciated!
Thanks!
 

iomega311

Full Member
Dec 9, 2011
92
8
Arizona, USA
**UPDATE**
I tried the EXACT same steps on my other PC that is running Windows 7 as the host OS.
It wrote correctly this time.

However, when I plug it in to my xbox... It is still not booting to the dash and the green light flashes. This is only while my drive is plugged in, but still, when I unplug the drive the console boots to the stock dash.


Here are my JF logs for the successful write:

********************************************





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


JungleFlasher 0.1.96 Beta (323)


Session Started Fri Dec 27 21:21:24 2013






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


X360USB PRO detected, Version 0.18






Found 1 I/O Ports.


Found 0 Com Ports.


Found 14 windows drives C: D: E: F: G: H: I: J: K: L: M: N: Y: Z:


Found 3 CD/DVD drives E: H: M:






Sending Vendor Intro to port


Status 0x80


Re-sending Vendor Intro:


........


Serial flash found with Status 0x72






Sending Device ID request to port


Spi Status: 0x00


Manufacturer ID: 0xEF


Device ID: 0x11


Flash Name: Winbond/NEX(W25P20/NX25P20)


Flash Size: 262144 bytes


Loading firmware file C:\Users\me\Desktop\Restore2Stock.bin


MD5 hash: a1f316e9b9bcd9e2241602bafaf5a283


Drive key @ n/a xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


Firmware Osig: [PLDS DG-16D4S 0225]


Firmware is: LTU2 v1.0






Getting Status from port


SPi flash found with Status 0x72






Sending Chip Erase to Port


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


Spi Status: 0x8C
 
Last edited:

iomega311

Full Member
Dec 9, 2011
92
8
Arizona, USA
Sorry, I guess I thought it was up to date. I downloaded what appears to be the most recent update and flashed it.
Went through the process again and it is still doing the same thing... won't boot up.

I am using a Lite on 16d4s drive that originally had a 9504 FW PCB in it. And then am flashing 0225 FW for this console.
Would that cause any issues?

Here are my new logs:

****************************








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


JungleFlasher 0.1.96 Beta (323)


Session Started Fri Dec 27 23:11:09 2013






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


X360USB PRO detected, Version 0.20






Found 1 I/O Ports.


Found 0 Com Ports.


Found 13 windows drives C: D: E: F: G: H: I: J: K: L: M: Y: Z:


Found 3 CD/DVD drives E: H: M:






XECUTER X360USB PRO removed.






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: 0x00


Manufacturer ID: 0xEF


Device ID: 0x11


Flash Name: Winbond/NEX(W25P20/NX25P20)


Flash Size: 262144 bytes


Loading firmware file C:\Users\me\Desktop\LTU2-0225-v1.0.bin


MD5 hash: d6ab7ccd7bbc1301762e6eff602afac3


Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF


Firmware Osig: [PLDS DG-16D4S 0225]


Firmware is: LTU2 v1.0






re-parseing file


Loading firmware from buffer


Drive key @ n/a XXXXXXXXXXXXXXXXXXXXXXXXXXXX


Firmware Osig: [PLDS DG-16D4S 0225]


Firmware is: LTU2 v1.0






Stage 1 failed


Key Verification Failed !!


Additional extracts not completed.






Target f/w saved as: afterupdate.bin






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 Slim Lite-On..


XECUTER X360USB PRO removed.

******************************************


So it APPEARED to write correctly (doing this on my desktop PC running Win 7 as host OS) but is still not working as of yet. :frown:
 

manuforti

Junior Member
Nov 30, 2011
13
0
Are you locking the drive using the switch and the software before issuing the drive outro?
 

manuforti

Junior Member
Nov 30, 2011
13
0
Does JF tell you it has been successfull in locking the drive.

Your log shows the outro only after the verification.