after kamikaze - wont verify write

dkopsieker

Junior Member
Dec 5, 2011
15
0
I just kamikazee'd my slim, and everything seemed to go smoothly. I can lock and unlock my drive fine. Reading works good. But, when i try to write the lt+ 3.0 firmware, it doesnt verify. I tried 3 times, all the same result. The drive works fine in the console, and plays backups fine. Should i be concerned about getting banned because of this?

THanks!
 

dkopsieker

Junior Member
Dec 5, 2011
15
0
Also forgot to mention, since it stops at the "Write Verification Failed" part, it never goes to the "Restoring Sector" part..... but like i said, it seems to work fine. And no eject issues.
 

paul.86

VIP Member
Sep 4, 2011
242
0
ROTHERHAM
every time i have seen Write Verification Failed it never worked you must be a lucky one if its locked i cannot see a ban coming your way but dont quote me
 

dkopsieker

Junior Member
Dec 5, 2011
15
0
yes, its locked and can be unlocked with alcohol... works every time. Only other weird thing, sometimes when i click the intro button to put it in vendor mode, and it asks me to cut power to drive for a cesond and turn it back on, sometimes it goes straight into vendor mode after i click yes. I dont need to turn power off. But the screen still comes up saying i have to cut power.
 

kwazziee

Full Member
Jan 10, 2012
59
0
yes, its locked and can be unlocked with alcohol... works every time. Only other weird thing, sometimes when i click the intro button to put it in vendor mode, and it asks me to cut power to drive for a cesond and turn it back on, sometimes it goes straight into vendor mode after i click yes. I dont need to turn power off. But the screen still comes up saying i have to cut power.
This is true for me also. As the tutorial stated "most time it will kick in automatically".

@OP I did not us the Kamakazi method but instead TX PCB and had the same issue as you did. It played burned game without a problem however I got the writing process to complete. I was not able to outra and lock it(0x80). I was using a older version of JF. To all having this problem please make sure you are using the most UTD JF.