NO-KXploit Patcher for 1.50
NO-KXploit Patcher for 1.50
This program will patch the firmware 1.50 (in RAM) to allow it to run normal pbp's.
The patch will remain resident in the firmware until one of these conditions happen:
1) A program crashes the psp, forcing you to do 2.
2) You restart your psp holding the power button or remove the battery.
You can run/exit games/homebrews, put the psp in sleep mode... none of those things will delete the patch from RAM.
I don't know if someone will find this useful since most current homebrews are kxploited, but it's a solution to having 2 folders, hiding icons... and all those annoying things.
It's also an example of a program that remains resident surviving sceKernelLoadExec, sceKernelExitGame, maybe someone finds that useful (there is a part of the code that it's executed with no firmware in RAM :), some cool things could be done with that)
http://rapidshare.de/files/17641675/NOKXPLOIT.zip.html
The patch will remain resident in the firmware until one of these conditions happen:
1) A program crashes the psp, forcing you to do 2.
2) You restart your psp holding the power button or remove the battery.
You can run/exit games/homebrews, put the psp in sleep mode... none of those things will delete the patch from RAM.
I don't know if someone will find this useful since most current homebrews are kxploited, but it's a solution to having 2 folders, hiding icons... and all those annoying things.
It's also an example of a program that remains resident surviving sceKernelLoadExec, sceKernelExitGame, maybe someone finds that useful (there is a part of the code that it's executed with no firmware in RAM :), some cool things could be done with that)
http://rapidshare.de/files/17641675/NOKXPLOIT.zip.html
Last edited by moonlight on Mon Apr 10, 2006 9:59 pm, edited 1 time in total.
Moonlight, i've got a question regarding your hack.
I have a PSP fw 1.0 and for now am very happy with it because it launches homebrews very fast (fw 1.0 in 3,5 seconds, fw 1.50 in almost 9 seconds!).
Also I like using 1.0 PBPs (easier to manage) and no corrupted icon (i know these can be hidden on 1.50 so that' a rather moot argument ^^)
But I am tempted to upgrade to 1.50 because I would like to try the Firwmare Emulator from MPH..
Do you notice if with your hack the 1.50 launches homebrew faster than without it?
Can you stopwatch if it's not a problem?
(from pressing the "execute" (circle or square if jap or us) button on the PBP list to the first screen of the homebrew).
It would help me decide i think ;)
Thanks,
Alcahest
I have a PSP fw 1.0 and for now am very happy with it because it launches homebrews very fast (fw 1.0 in 3,5 seconds, fw 1.50 in almost 9 seconds!).
Also I like using 1.0 PBPs (easier to manage) and no corrupted icon (i know these can be hidden on 1.50 so that' a rather moot argument ^^)
But I am tempted to upgrade to 1.50 because I would like to try the Firwmare Emulator from MPH..
Do you notice if with your hack the 1.50 launches homebrew faster than without it?
Can you stopwatch if it's not a problem?
(from pressing the "execute" (circle or square if jap or us) button on the PBP list to the first screen of the homebrew).
It would help me decide i think ;)
Thanks,
Alcahest
The loading of unpatched eboots on 1.50 using moonlight patch is slower than the kxploit patched eboots, and way slower than 1.00, beside 1.00 is so rare that I would never advise to update itAlcahest wrote:Moonlight, i've got a question regarding your hack.
I have a PSP fw 1.0 and for now am very happy with it because it launches homebrews very fast (fw 1.0 in 3,5 seconds, fw 1.50 in almost 9 seconds!).
Also I like using 1.0 PBPs (easier to manage) and no corrupted icon (i know these can be hidden on 1.50 so that' a rather moot argument ^^)
But I am tempted to upgrade to 1.50 because I would like to try the Firwmare Emulator from MPH..
Do you notice if with your hack the 1.50 launches homebrew faster than without it?
Can you stopwatch if it's not a problem?
(from pressing the "execute" (circle or square if jap or us) button on the PBP list to the first screen of the homebrew).
It would help me decide i think ;)
Thanks,
Alcahest
Mathieulh is right. Right now it's more slow, because it extracts the elf from the pbp to another file.
I'll take a look at the (undocumented) functions sceKernelLoadExecBufferPlain, sceKernelLoadExecBufferPlain0 and sceKernelLoadExecBufferVSHPlain to document them and avoid having to extract the file to another one.
I'll take a look at the (undocumented) functions sceKernelLoadExecBufferPlain, sceKernelLoadExecBufferPlain0 and sceKernelLoadExecBufferVSHPlain to document them and avoid having to extract the file to another one.
Hum, yep extracting the ELF from the archive may be slow...
Why not writing our own process ? The PBP archive can contains only a tiny loader which loadExec something called EBOOT.ELF or whatever located in the same directory ?
EBOOT.ELF should be, obviously, the homebrew stuff to run.
Those EBOOT.PBP are so usless :D viva PSPLink :D
as simple as that...
tiny loader
Why not writing our own process ? The PBP archive can contains only a tiny loader which loadExec something called EBOOT.ELF or whatever located in the same directory ?
EBOOT.ELF should be, obviously, the homebrew stuff to run.
Those EBOOT.PBP are so usless :D viva PSPLink :D
as simple as that...
tiny loader
Code: Select all
#include <pspkernel.h>
#include <pspdebug.h>
#include <pspdisplay.h>
#include <pspsdk.h>
#include <psploadexec.h>
#include <psptypes.h>
#include <stdio.h>
#include <string.h>
#include <sys/unistd.h>
#define ELF_FILENAME "EBOOT.ELF"
PSP_MODULE_INFO("TINY_LOADER", 0x1000, 1, 1);
PSP_MAIN_THREAD_ATTR(0);
int main(void)
{
char initialPath[MAXPATHLEN];
struct SceKernelLoadExecParam execParam;
if(getcwd(initialPath, MAXPATHLEN))
{
char pathFA[MAXPATHLEN];
sprintf(pathFA, "%s/%s", initialPath, ELF_FILENAME );
execParam.size = sizeof(execParam);
execParam.argp = path;
execParam.args = strlen(path);
execParam.key = NULL;
int res;
res = sceKernelLoadExec(path, &execParam);
}
//never goes here...
sceKernelExitGame();
return 0;
}
- TiTAN Art Division -
http://www.titandemo.org
http://www.titandemo.org
They are not replaceable. You might try selling it on eBay,But I am tempted to upgrade to 1.50 because I would like to try the Firwmare Emulator from MPH..
and might find you end up with enough cash for a new unit.
At least over here, there are good firmware units still available.
Sorry for the off topic... but here we are trying to make 1.5's behave like 1.0s!
Oh mind you, I worship my 1.0 and would never sell it. It's just sad that most homebrews released nowadays do not work on it.Art wrote:They are not replaceable. You might try selling it on eBay,But I am tempted to upgrade to 1.50 because I would like to try the Firwmare Emulator from MPH..
and might find you end up with enough cash for a new unit.
At least over here, there are good firmware units still available.
Sorry for the off topic... but here we are trying to make 1.5's behave like 1.0s!
Later,
Alcahest
You can't do this unless you manage to bypass the IPL prx checksum (as unfortunately, loadexec.prx is one of the few modules checked by the IPL at startup (as most of the modules in the flash0:/kd/ folder are)), and this can't be done without overwriting the IPL in the first place.Duo wrote:Are there plans for releasing a version that patches the firmware so this doesn't have to be loaded every time? Great job though. This is a great idea. Saves some memory stick memory too.