LITEON DG-16D4S - SLIM Trying to flash back to stock. Having issues...

[blazie151]

As the title says, I'm trying to flash my slim on the latest dash back to stock. Don't know why it's not working. I've flashed TONS of drives, and this one is the first giving me a problem. JF log below...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.92 Beta (304)
Session Started Sat Aug 04 11:23:13 2012
This is a Wow 64 process running on 2 x 64 bit CPUs 
X360USB PRO detected, Version 0.18
New CD/DVD detected.
Found drive C: - Hard Drive.
Found drive D: - CD/DVD.
Found drive E: - Removable.
No Hitachi drives were found!
portio64.sys Driver not Installed 
Found 7 I/O Ports.
Found 3 Com Ports.
Found 3 windows drives C: D: E:
Found 1 CD/DVD drives D:
Loading firmware file C:\Users\AVFL-TECH1\Desktop\Xbox Modding\Keys\005210612605\Lite-OFW.bin
MD5 hash:  98a93c3cbddee2fde156ab21182390bf
Drive key @ n/a 0A28F182C3AE1D20E2C622542D1CB8FD
Firmware Osig: [PLDS    DG-16D4S        0401]
Firmware is:  Stock                           
Loading firmware file C:\Users\AVFL-TECH1\Desktop\Xbox Modding\Keys\005210612605\Lite-OFW.bin
MD5 hash:  98a93c3cbddee2fde156ab21182390bf
Drive key @ n/a 0A28F182C3AE1D20E2C622542D1CB8FD
Firmware Osig: [PLDS    DG-16D4S        0401]
Firmware is:  Stock                           
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
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: 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: Dump Failed
Getting Status from port 0x0000
Invalid Status 0x80
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
Getting Status from port 0x0000
Serial flash found with Status 0x72
Reading Drive Key.
............
Stage 1 failed
Authorisation 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: 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: Dump Failed
Loading firmware file C:\Users\AVFL-TECH1\Desktop\Xbox Modding\Keys\005210612605\Lite-OFW.bin
MD5 hash:  98a93c3cbddee2fde156ab21182390bf
Drive key @ n/a 0A28F182C3AE1D20E2C622542D1CB8FD
Firmware Osig: [PLDS    DG-16D4S        0401]
Firmware is:  Stock                           
Auto-Loading firmware file C:\Users\AVFL-TECH1\Desktop\Xbox Modding\JungleFlasher v0.1.92 Beta (304)\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

Getting Status from port 0x0000
Invalid Status 0x80
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
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 3891mS
Write Verify Failed !

 

[guitarguy]

Are you using the X360USB Pro to connect the drive to your PC?

 

[sick360mods]

Sounds like it was drilled to far. Try writing to it with a qtip with alcohol in the hole.

Sent from my PC36100 using Tapatalk 2

 

[blazie151]

Are you using the X360USB Pro to connect the drive to your PC?

Yes. (It shows that in the beginning of the log, btw)

Sounds like it was drilled to far. Try writing to it with a qtip with alcohol in the hole.

Sent from my PC36100 using Tapatalk 2

I have written to it before (have been using it for months after the first unlock and FW write), and I used a hand drill, I don't think it went too far. To unlock the drive this time, I simply used a very fine wire and bridged from the 3.3v point to the hole in the chip (the alcohol trick didn't work, so I had to). I went ahead and tried locking the drive and outro'ing it, both worked without errors. I just don't want to test the drive for fear of a ban flag. I'd try the qtip method you mentioned, but the hole is WAY too small for a qtip. I drilled it with a very fine drill bit and a hand drill. I'll also mention that the capacitor was not used, as I read it wasn't needed with the newer versions of JF. Anything other than a qtip you suggest, something much thinner?

EDIT: I just went to try and flash again, and noticed that JF is no longer seeing the drive unless I intro it. Normally, it detects the drive and recognizes that the key is in the DB.

EDIT 2: I was able to unlock the drive and try again, errors out at the same place. What's weird is that it errors out at a different place when using CFW vs OFW (you can see that in the log above). Forgot to mention before, but the spindle starts up after the FW write and before the verification when writing CFW only. When writing OFW it does nothing.

 

[blazie151]

Just got it to write. To inform everyone of what I did....

I dried up the alcohol with a heat gun
plugged the drive back in to the computer
started a fresh JF session
intro'd the drive because it wasn't being seen by JF
opened the original dummy.bin instead of the Lite-OFW.bin file I was using before (opened in source)
picked the stock firmware image from the bundle pack download (opened in target)
spoofed the key over
clicked write

first time it did what it was doing before when writing CFW, wrote the banks, the drive spun up, it read the banks, and the verify failed

intro'd the drive again
click write again

this time it did the same as above, with the exception that it verified and everything went through as usual

intro'd the drive again
locked the drive
outro'd the drive
it's now being recognized as usual from JF, I'm going to test it in a few

I don't know what the problem was, but I think it might have had something to do with my original Lite-OFW.bin file.

EDIT: Tested it, it's working. I'm never flashing that drive again! lol.