BlackSheep
Active Member
if someone makes a umd update that contains cfw will it be possible??
if it is give me some crezzz
if it is give me some crezzz
-
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.
cfw on psp 3000 possible???
- Thread starter BlackSheep
- Start date
BlackSheep
Active Member
why
CFW can be ran on the TA oh-eighty-eight and oh-nighty mother boards but the hacker community haven't yet figured out what they need to know about the newer mobos what they found out with the old ones.
The only reason we can run HEN on the newer ones is that slim.tiff basically tricks the psp OFW into thinking that the h.bin is on the flash0 and not the ms0 which causes the psp to reload Davee's system software into the memory.
The only reason we can run HEN on the newer ones is that slim.tiff basically tricks the psp OFW into thinking that the h.bin is on the flash0 and not the ms0 which causes the psp to reload Davee's system software into the memory.
Hellcat
Contributor
Huh? Sorry if I sound rude, but that's total BS 
The TIF doesn't trick the PSP to think the h.bin is anywhere.
It uses a flaw in the firmware to execute the code contained in it (no matter where the PSP thinks it is). And that code actively patches parts of the system software (in RAM) to enable launching of unsigned code.
As for why no CFW on 3k:
CFW *must* have a custom IPL to be able to run, that again is unofficial, unsigned code.
On the older MoBos there's another flaw in the way how the PSP checks the signature, that flaw had been fixed on newer MoBos.
The TIF doesn't trick the PSP to think the h.bin is anywhere.
It uses a flaw in the firmware to execute the code contained in it (no matter where the PSP thinks it is). And that code actively patches parts of the system software (in RAM) to enable launching of unsigned code.
As for why no CFW on 3k:
CFW *must* have a custom IPL to be able to run, that again is unofficial, unsigned code.
On the older MoBos there's another flaw in the way how the PSP checks the signature, that flaw had been fixed on newer MoBos.
BlackSheep
Active Member
Huh? Sorry if I sound rude, but that's total BS
The TIF doesn't trick the PSP to think the h.bin is anywhere.
It uses a flaw in the firmware to execute the code contained in it (no matter where the PSP thinks it is). And that code actively patches parts of the system software (in RAM) to enable launching of unsigned code.
As for why no CFW on 3k:
CFW *must* have a custom IPL to be able to run, that again is unofficial, unsigned code.
On the older MoBos there's another flaw in the way how the PSP checks the signature, that flaw had been fixed on newer MoBos.
on topic guys and the topic is if u can run cfw if u put a update into the umd
Huh? Sorry if I sound rude, but that's total BS
The TIF doesn't trick the PSP to think the h.bin is anywhere.
It uses a flaw in the firmware to execute the code contained in it (no matter where the PSP thinks it is). And that code actively patches parts of the system software (in RAM) to enable launching of unsigned code.
As for why no CFW on 3k:
CFW *must* have a custom IPL to be able to run, that again is unofficial, unsigned code.
On the older MoBos there's another flaw in the way how the PSP checks the signature, that flaw had been fixed on newer MoBos.
Ok sorry im just guessing I thought it was similar to somthing else:blushing:
Hellcat
Contributor
It WAS on topic.
My original answer answered the q' to 100%.
Short A: no.
Long: no, it will not work.
What you flag as OT was the explanation of WHY - as has been asked in this thread.
Now, go and take your help-moding somewhere else, thank you.
BlackSheep
Active Member
thx u but u were geting out of it
Hellcat, that is not quite the right answer. As of right now the current custom fw will never work on the PSP 3k, however it is still possible to find another hole in the boot process that will allow a custom firmware. However, only time will tell, maybe the IPL will get cracked, we just do not know yet.
#1. To answer the question that was asked. We cannot write to UMD's so, it's not possible to put a CFW on a UMD to be able to run even if CFW was possible on the TA-088v3 and the PSP 3k.
#2. To have a true CFW like M33 is, technically, we need a custom IPL. To get a custom IPL we need to crack the Pre-IPL to find an exploit in it. If there is no way to exploit the Pre-IPL once it's been dumped then the only way to get a CFW would be to exploit the boot process somewhere. This can be in the IPL or in one of the prx's that loads the PSP it's self. You can possibly do it in the reboot.bin I assume, since it's a file that gets used in the boot process, as long as there is an exploit in it.
#3. Correct me if I'm wrong but, didn't 2.71 OE - 3.40 OE not use a custom IPL but, hijack the boot process somewhere? And it wasn't until Pandora came out that he started using his own custom IPL? Thinking about it. I think he loaded 1.50 OFW or at least a certain portion of it, just enough of it to allow for running of homebrew, then at that point he launched the normal firmware e.g. 2.71 - 3.40 ect.
Basically since 1.50 cannot be run on the Ta-088v3 and 3K, and there is no way to run homebrew on boot, unless there is a kernal exploit in the boot process found then no CFW for the PSP3k/TA-088v3.
---------- Post added at 11:27 PM EST ---------- Previous post was at 11:25 PM EST ----------
What do you mean cracked?
It's been reversed since the PSP 3k came out...
You mean a new custom IPL is 75% done?
#2. To have a true CFW like M33 is, technically, we need a custom IPL. To get a custom IPL we need to crack the Pre-IPL to find an exploit in it. If there is no way to exploit the Pre-IPL once it's been dumped then the only way to get a CFW would be to exploit the boot process somewhere. This can be in the IPL or in one of the prx's that loads the PSP it's self. You can possibly do it in the reboot.bin I assume, since it's a file that gets used in the boot process, as long as there is an exploit in it.
#3. Correct me if I'm wrong but, didn't 2.71 OE - 3.40 OE not use a custom IPL but, hijack the boot process somewhere? And it wasn't until Pandora came out that he started using his own custom IPL? Thinking about it. I think he loaded 1.50 OFW or at least a certain portion of it, just enough of it to allow for running of homebrew, then at that point he launched the normal firmware e.g. 2.71 - 3.40 ect.
Basically since 1.50 cannot be run on the Ta-088v3 and 3K, and there is no way to run homebrew on boot, unless there is a kernal exploit in the boot process found then no CFW for the PSP3k/TA-088v3.
---------- Post added at 11:27 PM EST ---------- Previous post was at 11:25 PM EST ----------
Well the IPL apparently is almost completely cracked 75% I read on this forum
What do you mean cracked?
It's been reversed since the PSP 3k came out...
You mean a new custom IPL is 75% done?
Man I would love to fly a plane to japan, walk to a Sony manufacturing plant, Grab a UMD burning tool, a ton of blank UMDs, and load the drivers for the device onto my memory stick then just walk out saying that theres new equipment coming in ten minutes.
unlockingsky
New Member
wasn't there a earlier news said DA crack the IPL?
BlackSheep
Active Member
my uncle works at sega!!! i can get blank umds and he can burn them somehow but!!! he moved to ny and i life in cali!
abchopra2010
New Member
Burning CFW to a umd wont help.
Cuz when u install it , the firmware wont have the sony's signature and the psp will brick.
Cuz when u install it , the firmware wont have the sony's signature and the psp will brick.
slasher2661996
New Member
Doesn't matter, the CFW will disable the check for the Sig, and if it was possible (which it's not) then we could even dump the pre-ipl.
BUT IT'S NOT
BUT IT'S NOT
Only person with access to UMD's are SONY not Sega... Sorry he can't get them.