Martin C
VIP Member
SlimKey + Orig Dump are 2 different keys
- Thread starter skatermike21988
- Start date
- Status
See that's just It, I don't really know. Because when I load the OFW into the target it shows this key:
E638AE392AA2EE1E8D*********
I tried it with LT+ and no go. Now with the stock fw flashed to the drive and I do a slimkey I get the other key:
7512C709005E8C99E9*********
Which also does not work with LT+
Other things I have tried are taking a stock firmware that's included in the FW pack and spoofing the key to it I tried both 0225.bin and 0225u.bin stock fw. I tried both keys and that also didn't work. The only thing that seems to work is the Lite-OFW.bin
Edit: I hope you can see why I'm so confused. I did another 0225 drive before and didn't have anything like this. Just had to figure out 0225.bin or 0225u.bin and then I was up and going.
Last edited:
Martin C
VIP Member
But Lite-OFW works only with auth failed, yes?
Load the dummy.bin into your source and flash LT+ based on that. Post the log.
Load the dummy.bin into your source and flash LT+ based on that. Post the log.
Right everytime I flash Lite-OFW.bin I get the authorisation failed. The only time I didn't was when I was flashing the ones I created using the FW pack.
Here's the log you asked for:
Going to go pop the drive in the console real quick to see if anything might have changed....
Martin C
VIP Member
Well I'm glad it does because it just started working. Any Idea as to why I would be getting 2 different keys from slimkey and the OFW?
Edit: Also wanted to say thanks for your help. This is my first Kamikazee hack. Whille doing the hack wasn't that hard I had thought I had messed up the drive. Apparently I didn't it was just a Issue with getting the keys figured out. Thanks alot for help. I've done plenty of phat consoles but only 2 slims including this one and the first one I just replaced the pcb.
Last edited:
Martin C
VIP Member
Yeah - you basically had a bad read of the OFW. Either to do with the Kamikaze or just one of those things. Your OFW was corrupt, which is why it failed auth and the data was throwing out the key.
Try this now - re-dump an OFW based on this working drive and try again with the NEW OFW.
Try this now - re-dump an OFW based on this working drive and try again with the NEW OFW.
Ok so here's what I just did:
I did a read of the drive in it's current state which had LT+ 2.0 on it and working. I then manually loaded Orig-0225.bin from the FW pack and clicked spoof to target. I then flashed this new Orig.bin to the drive, but it doesn't work.
Here's a log:
Martin C
VIP Member
ok - one more to try:
load your good dummy.bin, then manually load the stock 0225 as above and spoof source to target.
Write to the drive and test. Let me know what happens.
load your good dummy.bin, then manually load the stock 0225 as above and spoof source to target.
Write to the drive and test. Let me know what happens.
Martin C
VIP Member
ok - was expecting that to work.
Just confirm that dummy.bin as source and autoload LT still works!
Just confirm that dummy.bin as source and autoload LT still works!
If it doesn't I did save a full read of the working LT on my PC so hopefully either one will work. Going to check now.
---------- Post added at 06:35 ---------- Previous post was at 06:26 ----------
OMG what is it with this drive that's making it such a pain.
Just tried to auto load LT+ from dummy and it didn't work again. Gonna try the dump i took of it when it was working and hopefully it's good again.
Martin C
VIP Member
It could be the work you did to unlock it. You're getting bad writes to the drive.
Keep using dummy.bin as the source as it's the data you took before cutting into the chip.
Failing that, replace the chip or PCB.
Keep using dummy.bin as the source as it's the data you took before cutting into the chip.
Failing that, replace the chip or PCB.
Ok so I just tried the "working" LT+ dump I took and it's not working now either. I don't get it.
---------- Post added at 06:43 ---------- Previous post was at 06:40 ----------
---------- Post added at 06:43 ---------- Previous post was at 06:40 ----------
Alright, I'm just gonna wait on 3.0 and then mess with it to get it working again. Still doesn't make sense though, because every time I flash the Lite-Orig.bin it works with the exception of the failed authorisation. If I was getting the occasional bad writes, wouldn't it affect that as well.
Martin C
VIP Member
As I said, load dummy.bin - let JF load the firmware.
(we know this works)
Write to your drive and test. If it doesn't, leave everything as is in JF and intro/write again.
Keep doing it until it works.
Once it works, leave it as is.
EDIT: I still reckon this is down to you cutting something in the chip. A replacement PCB/Drive would prove it.
(we know this works)
Write to your drive and test. If it doesn't, leave everything as is in JF and intro/write again.
Keep doing it until it works.
Once it works, leave it as is.
EDIT: I still reckon this is down to you cutting something in the chip. A replacement PCB/Drive would prove it.
I have a 0225 drive with a replacement pcb in it. I will try later today to flash it with the dummy as source and pop it into the other console and see how it goes.
Ok I just tried with my drive that has a replacement pcb. I also had mixed results using dummy.bin as source. It worked one minute and then I tried to make a new orig.bin and then it didn't work again. I'm just going to wait on 3.0 and get it working and leave it.
Martin C
VIP Member
ok - no worries. I'll close this thread as resolved then. Use the dummy.bin as source for now.
- Status