• 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.

Eboot Mod Mercury 6.20 crashing the system PSPGo

K

knyz

New Member
Hello everybody...

I recently added on youtube a video of my eboot mod Mercury 6.20(Mercury patched on the PSN Store), you can crash the system with this version of Mercury

http://www.youtube.com/watch?v=n7XtEPLPWjE.

Let me know your think

Anyway, you can launch the games mercury patched available on the PSN Store.

Just edit the part of line on eboot.PBP (offset 0170) with the number of your firmware, you can launch the games after that.
 
knyz said:
Hello everybody...

I recently added on youtube a video of my eboot mod Mercury 6.20(Mercury patched on the PSN Store), you can crash the system with this version of Mercury (i put the link soon).

Let me know your think

Anyway, you can launch the games mercury patched available on the PSN Store.

Just edit the part of line on eboot.PBP (offset 0170) with the number of your firmware, you can launch the games after that.
Click to expand...

Crashing the PSP != useful.

What happens is that the PSP detects that something is wrong and completely resets so the RAM is cleared. It's nearly completely useless.
 
It crashes because you broke an encrypted file, that doesn't mean anything at all, in order to stop further speculation I'm going to go ahead and close this thread.

Edit after a PM 1: I stand corrected, although there's more checks than that, one of them being that the DATA.PSP in the PSP also has a copy of the version number, but this file is encrypted. It's why it crashes, it doesn't pass that check.

Edit after a PM 2: As a result of a number of PM's I decided to reopen the thread, although from my personal point of view I am almost certainth it will not lead to anything good.
 
well what if we compared the patched and unpatched eboots, and see exactly what was patched using a hex editor. it may just be an offset or just extra coding.

This may lead nowhere due to encrytion but, it will kill some peoples curiosity of what was done and how sony does it.
 
This will highly likely lead nowhere, yes.

Not every crash is an exploit oportunity, just keep that in mind.

Besides, due to the encryptions and signatures on EBOOTs, there little to no chance to ever get enything going that way.
Unless there's a HUGE flaw (again *lol*) in the system.
 
Too bad my eboot doesn't run on my 6.10 either. And each time we mention an idea that worked in the past (like swap trick) we get the response that we shouldn't dig up past things.
But still... any odds that buying a M2 card would help with hacking the Go?
 
Lets just close the thread like every other one on MFM
 
You must log in or register to reply here.
Back
Top