Currently PSIDPatch is for 3.55 only. It'll run on other versions, but the ConsoleID shown will be wrong and the patching functions will patch the wrong places.
From the ReadMe file: Updated PSIDPatch 1.5, now it can also change the Console ID sent to PSN, although if the ID isn't valid you'll get a nice 8002A224 error. Included a sample consoleid.txt file too.
Updated PSIDPatch 1.2 for 3.55 consoles. SELF is signed and the package is "signed". 1.2 also lets you generate a random PSID now, no need for txt files. Also, removed the confirmation screens.
PSID is your playstation's unique identifier to Sony, this program will patch the loaded PSID in memory to one of your choice. This won't permanently patch your PSID, but *MIGHT* let you fool PSN. Best way to test this is for somebody with a banned PS3 to try changing it and going online.
Please note that I'm not sure if PSID is what is actually used for bans! Apparently the ID used for banning is generated using the PSID, but I think that the result of this generation *MIGHT* be stored somewhere in memory. If it is, this tool is worthless for PSN until that result is found.
Made and tested on a 3.41 PS3 for 1.0, 3.55 PS3 for 1.2... Although not tested online by me! If your using a different version and patching doesn't work properly please contact me and we'll work out a fix
+ Shows you current PSID
+ Shows you current Console ID
+ Patch PSID from dev_usb/psid.txt
+ Patch PSID to random number
+ Patch Console ID from dev_usb/consoleid.txt
+ Patch ConsoleID (line 2) to random number
+ Choose USB to load from
This uses the peek and poke syscalls in order to patch your PSID. Please make sure your using a payload which uses them or a CFW that has them (kmeaw 3.55 does)
Press Cross to patch PSID with a random number, or Square to patch ConsoleID.
Or.. if you want to use your own:
Create a text file called psid.txt/consoleid.txt on root of your USB
Put 32 hex characters inside (e.g. 1234567890ABCDEFFEDCBA0987654321) or 64 for ConsoleID
Open PSIDPatch, choose your USB using Up/Down arrows and press R1 to patch.
PSID starts at 0x800000000044A18C in 3.41, 0x800000000045218C in 3.55. It is 16 bytes long. Two identicle Console ID's exist in memory: one which is 32 bytes at 0x80000000003C2EF0 and another which is 16 bytes at 0x8000000000452174. PSN seems to use the second one, but PSIDPatch patches both.
Mathieulh/RichDevX - bragging about PSID stuff on twitter, if it was a private convo I never would of started this
user - Fixing CFWLoad code so no SCE confidential stuff is included, thanks man
djekl - Random PSID idea, can't believe I didn't think of that...
Update: PSIDPatch 4.21 CEX&DEX (DEXPSIDPatch / CEXPSIDPatch) by arj1231 is now available (linked above) as well and is edited to work on DEX MODE!
To quote: Just edited the source to use correct offsets. Both fully working on 4.21. Change PSID and CONID. Please Dont abuse (Stay away from COD games).
Thanks to Stoker25 for making source avail. To everyone please use a legit Console Id saved to USB.
Update #2: PSIDPatch for 4.40 CFW (linked above) by solidspike is now available, who states: PSIDPATCH 4.40 for most 4.40 CFW like rogero, miralatijera etc
The last 2 offsets for console id seem to keep changing in lv2 every time the system is restarted so we can’t patch these unless someone creates a new program that patches dynamically instead of using fixed offsets.
However this works and patches the PSID and the 2 fixed locations where the console id is for 4.40 CFW
Finally, from kokotonix comes a PSIDpatch fix for 4.46 by KW (linked above) who states:
I've been using psidpatch 4.40 to patch the consoleid of my bricked (non-working) console into my banned (but working) system.
Since I've updated to Rogero 4.46 CFW, psidpatch 4.40 stopped working with my system.
Ive tried a psidpatch 4.46 but it freezes my system.
As I've seen I was not the only one having this problem, I share a small test with the forum that I've came across: a "patched" PSIDpatch for 4.46 CFW made by KW
And thank you to stoker25 for this simple and very efficient tool. I have only test this with Rogero 4.46 1.00. It will be great to receive some reports with Rogero 1.01 or HABIB.
Tested on habib 4.46 1.13, tested in rebug 4.46.1 REX and LTE versions. From the number of tests I risk to say it is full 4.46 CFW compatible.
About PSID Patcher 4.46 CEX fixed by kokotonix (via ps3-solution-pour-tous.doomby.com/blog/ps3-homebrew/psid-patcher-4-46-cex-fixed-by-kokotonix.html) to quote, roughly translated:
A Dev named kokotonix released a few hours already secured version of homebrew PSIDpatcher coded Stoker25 behind. This version is now compatible for CFW 4.46 CEX.
NOTE: As usual, we were treated to a redesign of the work of this Dev by SGK, fast team, but starting input by three bricks BSOD (seen in the comments of U.S. sites that relate to inaccurate news) so beware of the version you want to install!
As a reminder, this homebrew allows de-ban or to protect the ban on condition where one has a valid PSID and consoleID!
This change is not permanent, the console resumes consoleID / Psid original every time you reboot. It will therefore boost PSIDpatcher every time before you connect to the SEN.
Install the package via install_package_file
Put on a USB stick formatted in FAT32 text files named like this:
psid.txt (you put into your file psid nothing else)
consoleid.txt (you put into your file consoleID followed by 32 times the number 0 and nothing else)
NOTE: The . txt is the file extension of course
Connect to the USB port on your leftmost console
Start PSIDpatcher then press L1 and also on R1
Do next TRIANGLE to exit the application
Connect to the PSN / SEN
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
They won't be able to ban consoles as you own them, they can just ban from psn only.. a guide from facanferff is below:
This method was tested by myself with my banned console (error 8002A227, could not log in to PSN or create new accounts, so permanent ban). If you have any problem in executing this method, please tell me.
IMPORTANT: You can find some problems in some games while trying to play online, but generally you can play online.
1. I hope that you put the new CA24.cer in dev_flash/data/cert
1. Download PS3DNS-GUI
2. Run "PS3DNS-GUI.exe" and choose your ip and region
3. Go to Tools -> Rewrite -> PS3DNS - eth0 -> Rules -> Add
4. Put every field like in the image, where in the image it says "your console id" you have to write your original (banned) console id with no spaces:
5. Click ok -> ok (of course)
6. Go to your PS3, in DNS set in primary your pc's ip, activate proxy, in host enter again your pc's ip and in port enter 8888. Then you can test to confirm that you have network.
7. Try to log in to PSN (it can take some time, about 1 minute)
I agree with you its not fair i don't use my modded ps3 online so i shouldn't get banned. My point is its wrong to do this sort of thing if you get banned thats because you violated the TOS/terms you deserve it its not fair to go using someone else's console ID just to get back online and for it to get banned again i mean lets say you do it you spoof/clone a console ID you get online for how long ? 30 mins 10 mins 1 hour then what ?
you have to find another console ID just to play again for a bit not worth it for all the work you have to do then the person who`s console ID you have used will be banned and for all you know they might buy lots of stuff from PSN i know i do then what is sony detect 2 console with the same ID online what then ?
ITS JUST NOT WORTH IT if you wanna go online buy another console if you dont then put up with offline games.
What's stopping Sony from sending a command to your PS3 to revel its MAC address to them? Don't forget, Sony has all the backdoor keys to your system and they can have it broadcast any information they want. The PS3 is essentially a giant rootkit in the shape of a gaming console.