• Steam recently changed the default privacy settings for all users. This may impact tracking. Ensure your profile has the correct settings by following the guide on our forums.

PSNabler FINAL by Smokin and RedHate

shikamaru

Senior Member ~ Trolololo
This is a plugin to allow PSN access on PSP games like resistence retribution while on 5.50 GEN-D. There are reports of it also working on M33 but I haven't tried. This is a quote from the website i found it on. This is made by Smokin and Redhate, I take no Credit. There are not any reports about it working on GEN-C for 3k but there have been queries.

hey guys, just a heads up. RedHate and Smokin just released their final version of the PSNabler plugin. check it out here.
a few tips for successful use:
umd driver set to m33
uninstall all previous versions
have a PSN account registered to ur psp
dont use WPA internet security encryption on ur wifi
LBP and motorstorm prolly wont work.

other than that, hopefully this works well for u guys. all credit and props go to RedHate and Smokin from aiolab! enjoy!

P.S.
here's the official statement from smokin

Quote:
This will be the final version, it is a modular design so all the game patches will be added to the psnabler folder. So no more updates on the plugin itself. Games will continue to be added when requested. When games are added they will be added to the repo too. To add new games simply download the file for the game ie., UCUS-12345.bin and put it in the psnabler folder in seplugins.

***UNINSTALL previous versions of psnabler before installing this one***

The games in the repo now are already in the final version so no need to download them they are there for future reference.

If you still have problems with it here are a few things to try:

1. As mentioned in the readme WPA security is not allowing users to logon to some games. This is an issue with sony, alot of people are having problems with it even ps3 users. This is the problem with some users trying to play Resistance, this is NOT a problem with this plugin.

2. Make sure you are using the m33 driver.

3. Some gen users get an error when clicking sign up in the psn tab from the xmb, again this is a firmware issue NOT a problem with psnabler. My suggestion is to update and if you can't then i'm sorry but its not gonna work.

4. Little Big Planet and Motorstorm will not work with this because of their own problems. LBP requires a game patch which has nothing to do with the psnabler and Motorstorm has network problems, after signing into psn a popup appears saying "fatal network error" this is happening to everyone even people without custom firmware.

5. READ THE README !!!!! it may just answer some of your questions.

To get the latest psnabler and future patches go to the PSNabler Repository

Download : Here

Even though this is FINAL, smokin is still making patches for games so that they are supported which can also be found on the download link above. For instructions on how to install these patches, see quote above.
 
Considering it allows applications like CWCheat to be used, I don't really support it. It'd be nice if he added something to block cheating applications.
 
Considering it allows applications like CWCheat to be used, I don't really support it. It'd be nice if he added something to block cheating applications.

NitePR's the most common cheating device (At least online), and there's a billion FOSS deviants flying around.

He and I did attempt to anti NitePR and CWCheat once. However that's unreliable because people just rename the module or threads, and since it's not like we can have a whitelist of good modules (again, someone can just rename it to something that would match the whitelist) it'd just be pointless, and he knows it.
 
1. As mentioned in the readme WPA security is not allowing users to logon to some games. This is an issue with sony, alot of people are having problems with it even ps3 users. This is the problem with some users trying to play Resistance, this is NOT a problem with this plugin.
I don't see how Sony is to blame for those using WPA when it works just fine when connecting online in official firmware, but it doesn't connect using this plugin.
WPA works just fine on PS3 also.

2. Make sure you are using the m33 driver.
The plugin works fine with Sony NP9660 on GEN-D3.

3. Some gen users get an error when clicking sign up in the psn tab from the xmb, again this is a firmware issue NOT a problem with psnabler. My suggestion is to update and if you can't then i'm sorry but its not gonna work.
Make an account from a PC if you don't have a PS3, choose to use an existing account on the PSP, and add. You don't need to update if you're using an existing account anyway.
Updating the firmware and adding in your info will be useless since once you downgrade back (if you can that is), that info is lost.

4. Little Big Planet and Motorstorm will not work with this because of their own problems. LBP requires a game patch which has nothing to do with the psnabler and Motorstorm has network problems, after signing into psn a popup appears saying "fatal network error" this is happening to everyone even people without custom firmware.
I have Motorstorm Arctic Edge, it works with no problems on official firmware, but it doesn't with this plugin. That "Fatal Error" message is coming from the plugin.
I also have LittleBigPlanet and the needed update only works on 6.20 since it's a PBOOT.PBP. Any firmware lower than that will display the patch as corrupted in the XMB and won't apply to the game when playing it.
 
Thanks for extra info Infiniti. The plugin is final but patches are still being made by Smokin for other games hopefully for FF Dissidia ;)
 
Thanks for extra info Infiniti. The plugin is final but patches are still being made by Smokin for other games hopefully for FF Dissidia ;)

wtf? What would you need patches for Dissidia? The game doesn't even have online and afaik ad-hoc party doesn't care about your FW version.
 
I don't see how Sony is to blame for those using WPA when it works just fine when connecting online in official firmware, but it doesn't connect using this plugin.
WPA works just fine on PS3 also.


The plugin works fine with Sony NP9660 on GEN-D3.


Make an account from a PC if you don't have a PS3, choose to use an existing account on the PSP, and add. You don't need to update if you're using an existing account anyway.
Updating the firmware and adding in your info will be useless since once you downgrade back (if you can that is), that info is lost.


I have Motorstorm Arctic Edge, it works with no problems on official firmware, but it doesn't with this plugin. That "Fatal Error" message is coming from the plugin.
I also have LittleBigPlanet and the needed update only works on 6.20 since it's a PBOOT.PBP. Any firmware lower than that will display the patch as corrupted in the XMB and won't apply to the game when playing it.

Lemme esplain what I think the problems are.

I think the patches are static, whereas with different system options (ie WPA) it shifts the memory due to different or more modules being loaded, and as such, does not work.
 
Also, this plugin does everything it should but the essential. Give PS Store access.
 
Also, this plugin does everything it should but the essential. Give PS Store access.

True, and I also worked on that a bit with RedHate too. The problem that NoEffex mentioned on the previous page, also applies to why this hasn't been done. There are a few things in memory we want to "patch" to enable the store to load, but that stuff isn't static, so it shifts around in mem a lot, so it's hard to hit the exact spot you want to change each time.

Don't get me wrong, I'm sure it's possible, it would just require a bit of work, and I didn't have that much time to look at it with him :neutral: Last I spoke with him he was still trying to make it work...

I agree, that would be the best feature ;)


n00b81
 
That would be quite awesome, to have PSN store access on lower (C)FW, yeah.

But I see another problem arising here: compatibility.

It's not rare that new options and such are build into the store and if you manage to launch an older store and the FW does not support things being thrown at it from the internet side....
 
True, and I also worked on that a bit with RedHate too. The problem that NoEffex mentioned on the previous page, also applies to why this hasn't been done. There are a few things in memory we want to "patch" to enable the store to load, but that stuff isn't static, so it shifts around in mem a lot, so it's hard to hit the exact spot you want to change each time.

Don't get me wrong, I'm sure it's possible, it would just require a bit of work, and I didn't have that much time to look at it with him :neutral: Last I spoke with him he was still trying to make it work...

I agree, that would be the best feature ;)


n00b81

You know, you could always search for things around it that never change (ie the same 0x30 bytes, no matter the location) then have boundaries for it to find it in, then from there apply an offset.
 
Wow, you fail (badly) if you use completely static addresses for patching stuff. Relative addresses is the way to go. Also, if you're just overwriting stuff in a buffer, why not hook the buffer allocation and access stuff (if needed) so you'd know where to change stuff? :-P

---------- Post added at 07:49 AM ---------- Previous post was at 12:51 AM ----------

I wanted to know how this plugin applies patches (and where), so I sat down, reversed it, and noticed some suprising things. So here:

How the patches are loaded (and "decrypted"):
Code:
void LoadAndDecryptPatch(char* gamecode)
{
	char buf[64];
	// this is (for some reason) copied to another buffer but I skipped that :-P
	char* xorkey = "redhatesyounoobiesdontbesnoopingididyouafavornowyouwannafuckmeee";
	
	sprintf(buf, "ms0:/seplugins/psnabler/%s.bin", gamecode);
	
	SceUID fd = sceIoOpen(buf, PSP_O_RDONLY, 511);
	if(fd < 0) return 0;
	
	sceIoRead(fd, &patch_buf, 64);
	sceIoClose(fd);
	
	int i, x;
	for(i = 0; i < 64; i++)
		buf[i] ^= xorkey[i];
	
	for(i = 0; i < 8; i++)
		patch_buf[i] = strtoi(buf[i*8], &x);

	return 1;
}
Why the patches are garbled with a simple xor algo is beyond me, but I felt that people should be able to make their own patches and now they have the needed information. So basically a lot of effort went to umm... what exactly?

Patches are applied like this:
Code:
void sub_00000394(u32 a0, u32 a1)
{
	if(*(u32*)(0x08800000 + a0) == (0x08800000 + a1))
	{
		*(u32*)(0x08800000 + a0 + 260) = *(u32*)version_string;
	}
}

...

	sub_0000394(patch_buf[0], patch_buf[1]);
	sub_0000394(patch_buf[2], patch_buf[3]);
	sub_0000394(patch_buf[4], patch_buf[5]);
	sub_0000394(patch_buf[6], patch_buf[7]);

redhatesusnoobieswebesnoopinghedidusafavornowwewannafuckhiiim :-P
 
lool at encryption
 
i use the pointer's to validate if its accessing the stack where the info is stored for a breif amount of time, when the pointer is active the info in the stack is also active.

honestly if i wanted to keep people out i wouldnt count 64 bites dead strait in a row shifting using a blatently obvious key. it was a 6:30 - 7:30 am re-write to stop the stupid updating.

now something better might come of it, perhaps people who create their own patches will help in supplying the rest of the community with them, or perhaps they will hoard them to themself. or maybe one of you will end up getting the psn store and completing the missing piece of the puzzle because I cant get that store, im not hiding anything or trying to hold anything back from ppl if i could get into the store everyone would have it too :(

i can see psn / psp getting an update again, soon they will force updates on use as they do with ps3 (just change their validation method for each fw)

the only thing that erks me just a bit about this thread is the fact dude just said he did it because he wanted to know, but then he POSTED it (saying and doing are different things). wick wicka wack.
 
Back
Top