DAMAGED SLIM 1070 PCB, REPLACED ANOTHER ORIGINAL UNLOCKED PCB AND NOW OPEN TRAY!

D1TazMan

Junior Member
Dec 7, 2010
12
0
I have been doing kamikaze for a while, this is my first time I messed up... I got my Dummy.bin and other files... when I went to unlock it seemed this time my usb pro and laptop got a glitch... a delay.. then when I heard the beep it showed unlocked, when I went to read after it asked me to power cycle to due the rest it stopped for a while it seemed it intro it again.. but stayed... so I started all over and then this time when I went to intro it the lock button didn't show and the spi status was 0x3c however I was able to lock with the ctrl+shift+f11 then I outro then intro, now it shows the lock butto 0x8c then I did the unlock this time with a qtip then it unlocked and the button showed 0x00 great!! So I tried read again and the same thing all over... ok... so I know I messed it up I probably went to far... well lucky I have to original unlocked pcb boards so then I tried writing the firmware to those and everything went ok, once locked and then put it on the xbox it says reading but now it says OPEN TRAY... can some one help me with the right procedures for this... I looked everywhere and I think I did this right... can someone help me with this... I appreciate it...
 

D1TazMan

Junior Member
Dec 7, 2010
12
0
I have 2 other drives new with the original unlocked pcbs as well I loaded the firm and still open tray!! I also have new laser do you think I should try replacing it!!
 

D1TazMan

Junior Member
Dec 7, 2010
12
0
HERE IS THE LOG!!.

JungleFlasher 0.1.96 Beta (323)
Session Started Mon Sep 23 00:58:19 2013

This is a 32 bit process running on 4 x 32 bit CPUs
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
XECUTER X360USB PRO attached.

Found 0 I/O Ports.
Found 2 Com Ports.
Found 1 windows drives C:
Found 0 CD/DVD drives

XECUTER X360USB PRO removed.

XECUTER X360USB PRO attached.

Drive is Slim Lite-On..

Key found in KeyDB at record (116 - TEST)
Key is: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Key has been tested and verified, thanks C4eva !
Loading firmware file C:\Users\BadBoy\Desktop\JungleFlasher v0.1.95 Beta (321)\firmware\KIDDI VW SLIM 1071 18603006YQ-46513205\Dummy.bin
MD5 hash: 59e5366803e041d672901b9aef6f8fd3
Inquiry string found
Identify string found
Drive key @ 0xA030 XXXXXXXXXXXXXXXXXXXXXXXXXX
Firmware Osig: [PLDS DG-16D4S 1071]
Firmware is: SlimKey Extract
Auto-Loading firmware file C:\Users\BadBoy\Desktop\JungleFlasher v0.1.96 Beta (323)\firmware\LTPlus-1071-v3.0.bin
MD5 hash: 3d1243454d9c6c1cd2760b8ea5f5c648
Genuine LT plus v3.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS DG-16D4S 1071]
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
Status 0x51
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 5288mS

Write verified OK !

Restoring sector 0x3E000.

Sending Sector Erase to Port 0x0000
Erasing: 0x3E000
Writing: 0x3E000
............
Authorised !
................
Restore verified OK !
Drive is Slim Lite-On..

Key found in KeyDB at record (116 - TEST)
Key is: XXXXXXXXXXXXXXXXXXXXX
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: 0x00
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 Vendor Outro to port 0x0000
Drive is Slim Lite-On..

Key found in KeyDB at record (116 - TEST)
Key is: XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Key has been tested and verified, thanks C4eva !
 

D1TazMan

Junior Member
Dec 7, 2010
12
0
This is the replacement board I installed in the same drive, as I removed the old one. and I still get open tray.. Should I replace the laser, which it did work previously with the old pcb board before I damaged the chip..
 

xzanox

VIP Member
Nov 1, 2011
905
48
Netherlands, 1336
This is the replacement board I installed in the same drive, as I removed the old one. and I still get open tray.. Should I replace the laser, which it did work previously with the old pcb board before I damaged the chip..
Of course you should try it since it most likely is caused by a faulty/damaged/weak laser.

If you've tried the new laser and still receiving the open tray error (which I doubt) then report back here. It's not the first time I hear a similar problem you describing with unlocking etc.
 
  • Like
Reactions: D1TazMan

xbox2712

Full Member
Jun 3, 2013
64
0
Sounds like your failed kamikaze fried your laser as well.
It seems like this is the issue to me, I've never heard of a kamikaze making this happen, its usually disc motor or eject motor been effected, but who knows, I mean drilling into a microchip while its powered on is kinda not a great idea, but its what required to unlock these drives, much damage could occur because of such an attempt, its your risk to take, there is a reason its called the "kamikaze hack".
 
  • Like
Reactions: D1TazMan

D1TazMan

Junior Member
Dec 7, 2010
12
0
I opened the drive and just put the spindle part on it to see what it was doing, the laser seems to work now is the motor that don't spin. I am going to try to replace it and see.
 

D1TazMan

Junior Member
Dec 7, 2010
12
0
It was the pcb it worked great unlock and lock, but like you guys said it was the motor control part of the chip, so I guess I went to far... So I got another drive and did the kamikaze and this time it was going to far and my usb pro wasn't detecting it... so as soon as I thought I was going to far I stopped checked the drive and it still worked so I was happy I didn't mess up, so instead of drilling further I just decided to use the qtip with alcohol and BINGO!! Can I ask a question what ohm resistor is the correct count to go through the 3.3 ?