LITEON 0225 Unlocked PCB Replacement Issues upgrading to Lt 3.0

phamilee

Junior Member
Aug 9, 2011
16
0
Hey guys,

I've been having some issues I can't seem to solve from read the forums. I recently upgraded my fw from LT 2.0 to LT 3.0. It has a replacement unlocked pcb installed with a winbound chip. I can't seem to get it to read the drive properties after flashing the upgrade. Also, I can't seem to get the xbox 360 to get passed the startup screen, it just goes to the E64 error message. I've tried reverting to stock fw but I still get the e64 error message. I tried reconnecting the wires and ribbons to make sure there's proper contact on the pcb. I haven't tried soldering the red/black/yellow/white/green wires directly from the board to the drive yet as I have no experience soldering anything, but I did make sure the connections were good 4-5 times. Please let me know if you have any suggestions for me. Is this a hardware issue or a firmware issue?

Attached is the JF log.


Thanks a bunch guys.
 

nosherfj

VIP Member
Nov 1, 2010
1,094
0
Manchester UK
not 100% but think you outro 1st then send lock command.can you still get drive into vender?
 
Does the drive eject?

---------- Post added at 09:07 ---------- Previous post was at 09:07 ----------

not 100% but think you outro 1st then send lock command.can you still get drive into vender?
Nope you have to be in vendor mode to lock.
 

phamilee

Junior Member
Aug 9, 2011
16
0
not 100% but think you outro 1st then send lock command.can you still get drive into vender?
Yes, I can get it into vendor just fine. I just can't ever see the drive properties, but when I press read, it verifies the firmware version and proper key was written.


Does the drive eject?
I can't get the drive to eject when plugged into the xbox. I forgot to mention that i'm using a ck3 and usbpro. I can't get it to eject from the ck3 either.
 

phamilee

Junior Member
Aug 9, 2011
16
0
In that case it hasnt written the firmware correctly.

Change the position of the WP switch then re-write the firmware
I've tried rewriting the firmware probably close to 10 times. When I press read after unlocking the SPI it verifies that i'm running lt 3.0. I tried reinstalling the firmware again anyways per your request but to no avail. Here's the JF log.

PHP:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.92 Beta (304)
Session Started Tue May 29 01:28:52 2012

This is a Wow 64 process running on 4 x 64 bit CPUs 
X360USB PRO detected, Version 0.18

portio64.sys Driver not Installed 
Found 3 I/O Ports.
Found 1 Com Ports.
Found 5 windows drives C: D: E: F: I:
Found 2 CD/DVD drives F: I:

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: 0xEF
Device ID: 0x11
Flash Name:  Winbond/NEX(W25P20/NX25P20)
Flash Size:  262144 bytes

Sending Spi UnLock request to Port 0x0000
.
Spi Status: 0x00
Loading firmware file C:\Users\Lee\Documents\Michelle Xbox\Dummy.bin
MD5 hash:  3313651b1dac3bcaba6e8725af9e2744
Inquiry string found
Identify string found
Drive key @ 0xA030 BE6C1982C6BB9A552BEF651D1EE1F249
Firmware Osig: [PLDS    DG-16D4S        0225]
Firmware is:  SlimKey Extract                 
Loading firmware file C:\Users\Lee\Desktop\ixtreme 3.0\Firmware\LTPlus-0225-v3.0.bin
MD5 hash:  1a38d3a2a6519339599fa1866642c513
Genuine LT plus v3.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS    DG-16D4S        0225]
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
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 Spi Lock request to Port 0x0000
Spi Status: 0x8C
Sending Vendor Outro to port 0x0000
Sending Vendor Outro to port 0x0000
Sending Vendor Outro to port 0x0000
Sending Vendor Outro to port 0x0000
 

sp4rkst4rt3r

VIP Member
Oct 9, 2010
2,126
0
North-West (UK)
After sending vendor outro the key should be verified like this:-

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 Outro to port 0x0000

Drive is Slim Lite-On..



Key found in KeyDB at record (20 - N/A)

Key is: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Key has been tested and verified, thanks C4eva !


Can you confirm that the key is verified after outro?
 

phamilee

Junior Member
Aug 9, 2011
16
0
I also tried reverting to stock, but all the issues remain the same. Thanks for your fast responses. I appreciate the help!

---------- Post added at 01:42 ---------- Previous post was at 01:40 ----------

Can you confirm that the key is verified after outro?
No. It does not show that it is verified after outro. I'm not sure if the outro is even working. Here's what happens from firmware flash to outro:

Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Write verified OK !


Sending Spi Lock request to Port 0x0000
Spi Status: 0x8C
Sending Vendor Outro to port 0x0000
Sending Vendor Outro to port 0x0000
Sending Vendor Outro to port 0x0000
Sending Vendor Outro to port 0x0000



Thanks again.
 
Last edited:

sp4rkst4rt3r

VIP Member
Oct 9, 2010
2,126
0
North-West (UK)
Not had this problem myself but I use a crappy old LapTop with Win XP.....

Have you tried a different operating system, I see you are using Win7 x64.....

Shouldn't make a difference but when I have issues with anything in Win7 I revert to XP and no more problems :p


EDIT:- Noticed that the portio.sys drivers are not loading, not completely sure if that could be the problem because it reads/writes but not verify!!!!

JungleFlasher 0.1.92 Beta (304)
Session Started Tue May 29 01:28:52 2012

This is a Wow 64 process running on 4 x 64 bit CPUs
X360USB PRO detected, Version 0.18

portio64.sys Driver not Installed
Found 3 I/O Ports.
Found 1 Com Ports.
Found 5 windows drives C: D: E: F: I:
Found 2 CD/DVD drives F: I:

Sending Vendor Intro to port 0x0000
Status 0x80
Re-sending Vendor Intro:
 
Last edited:

phamilee

Junior Member
Aug 9, 2011
16
0
Not had this problem myself but I use a crappy old LapTop with Win XP.....

Have you tried a different operating system, I see you are using Win7 x64.....

Shouldn't make a difference but when I have issues with anything in Win7 I revert to XP and no more problems :p
I only have one computer with me at the moment. I can give it a shot though tomorrow. I'm willing to try anything. It's so weird because before I decided to any firmware upgrading it was working fine. On a side note, I tried doing the lite-on erase to install from scratch, but i'm not sure that's working properly. Am I supposed to be in vendor mode with the spi unlocked to do that?


Thanks
 

phamilee

Junior Member
Aug 9, 2011
16
0
port io drivers arent needed with x360.

---------- Post added at 10:16 ---------- Previous post was at 10:15 ----------

Try two erases before you write to it....

Erase power off....
Erase then write.
Are you talking about the "Lite-On Erase" or simply the regular firmware erase button? What's the procedure when you have a replacement pcb installed? It doesn't seem to work. I tried performing in Vendor mode with spi unlocked, it can't get into vendor mode unless I Intro. Once I intro it doesn't seem to have erased anything. I can still read the firmware that's installed.
 

phamilee

Junior Member
Aug 9, 2011
16
0
You have drive type set to phat
Click intro dev id and make sure the spi is unlocked.
Click liteon erase
power off the drive
power on the drive
Click liteon erase again
now try writing.
Yeah the liteon erase function doesn't seem to work. That was exactly how I tried doing it. After I press liteon erase I can't get into vendor mode without pressing intro again. Either way, it doesn't erase the firmware.