Post: [RELEASE] PSIDPatch 1.6
02-28-2011, 08:48 PM #1
(adsbygoogle = window.adsbygoogle || []).push({}); This is a minor update but potentially could be very important.

You must login or register to view this content.


Today stoker25 has updated his security app to PSIDPatch version 1.6, it patches 2 extra places in Lv-2 where your ConsoleID is stored.

Download:
You must login or register to view this content.

From the ReadMe file:
Originally posted by another user
Updated PSIDPatch 1.6, seems there were 2 extra places in Lv-2 where your ConsoleID is stored that I didn't notice, now PSIDPatch changes them too.

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.


Features:

  • Patches two other locations where your psid is located
  • 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)

Usage:

  1. Install package
  2. Run PSIDPatch
  3. Press Cross to patch PSID with a random number, or Square to patch ConsoleID.
  4. Or.. if you want to use your own:
  5. Create a text file called psid.txt/consoleid.txt on root of your USB
  6. Put 32 hex characters inside (e.g. 1234567890ABCDEFFEDCBA0987654321) or 64 for ConsoleID
  7. Open PSIDPatch, choose your USB using Up/Down arrows and press R1 to patch.


Technical Stuff:
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.

AFAIK console id spoofing doesn't work, Sony might operate on a whitelist basis... If somebody can message me their console id, I'd be happy to try it out on mine to see if it could be something else.

Thanks:
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...


There is no source :(
(adsbygoogle = window.adsbygoogle || []).push({});

The following 6 users say thank you to MCPADDINGTON for this useful post:

club-bomb-shizl, emersons35, hofpint, Superchunk, tsuma, w8t4it
02-28-2011, 08:52 PM #2
nice, thanks for posting it m8 :y: I just dont get it why there are so many unbann tools releasing if nearly nobody has been banned yet...
02-28-2011, 08:56 PM #3
Originally posted by soc18 View Post
nice, thanks for posting it m8 :y: I just dont get it why there are so many unbann tools releasing if nearly nobody has been banned yet...


Well there have been no permabans yet only 30 day ones and your better safe than sorry. Outie

The following user thanked MCPADDINGTON for this useful post:

Mankins
02-28-2011, 08:57 PM #4
Superchunk
Are you high?
LULZ SONY FAILS but don't outsmart them =D
02-28-2011, 10:42 PM #5
mateo124
Bounty hunter
I'm pretty sure that Sony is suing because they can't do anything about this. They know nothing on the PS3 is permanent and hackers can change pretty much every little thing about the PS3 up until 3.56 where problems arise. So if you are banned I'm pretty sure there will be some permanent way to unban yourself in the future.. and ban anyone else out there
02-28-2011, 11:27 PM #6
Has anyone actually tried changing thier psid/consoleid and actually got it to sign in?

I tried it with v1.15 and 1.16 but i still get the error.

I am using a legit console and ps id unless a phat ps3s info wont work on a slims?
03-01-2011, 09:39 PM #7
Originally posted by MCPADDINGTON View Post
Well there have been no permabans yet only 30 day ones and your better safe than sorry. Outie


is this for the Black Ops bans or is this like for a PSN ban jw?
03-01-2011, 10:01 PM #8
Originally posted by KiiNGZiiLLA View Post
is this for the Black Ops bans or is this like for a PSN ban jw?


PSN but it's more than likely they had nothing to do with cfw.

---------- Post added at 10:01 PM ---------- Previous post was at 10:00 PM ----------

Originally posted by coffeehead View Post
Has anyone actually tried changing thier psid/consoleid and actually got it to sign in?

I tried it with v1.15 and 1.16 but i still get the error.

I am using a legit console and ps id unless a phat ps3s info wont work on a slims?


You have to be doing something wrong. I'm able to sign in fine.
03-01-2011, 11:08 PM #9
any chance it would help in any way for the black ops bans ? if not know any thing that would i'm tryin to help a buddy out
03-01-2011, 11:17 PM #10
Swade
The Brain Named Its Self
very nice post

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo