I'm not sure if the PSID I got is right but I'm using both and still not connecting. I have been unbanned with previous versions of this app but not this version. And with previous versions it only worked sometimes. I'm guessing this is one of those times that it just wont work no matter what ID you use.
specifically try v2.1. and make both console id.txt file and psid.txt file. spoof them both through the version and try and see if you can connect. (if you haven't already)
I only have a DEX.bin which is the CEX to DEX conversion file which actually killed the console and NAND FLASH dumps. I don't think they have the PSID in them.
As the console is dead I don't think I can get the PSID from that console. Unless you know where to find it in those NAND dumps?
BTW, I'm getting the *224 error when I use this Console ID. Its from the dump so it should be a good ID. The console was working online before it died. Could it be I got a slim and the ID is from a phat 60gb?
Last edited by StanSmith; 02-03-2013 at 10:19 PMReason: Automerged Doublepost
You can get your IDPS/Console ID from a DEX NAND dump you'll just need to change the 6th byte back to your original Target ID 84 for USA and 85 for Europe.
THANKS. I knew this ID was a good one. Its now working.
I don't have that LV-2 Memory dump so I cant get the PSID from that console. If its written on the motherboard then I can get it but anything software wise is gone as its dead. The CEX to DEX conversion bricked it then the Progskeet installer killed it as he couldn't install the Progskeet without killing one of the chips.
Reply With Quote
