Custom Firmware - The proof of concept

Zitat:

---

Zitat von Networkgamer

basically if the config file isnt found,then its as if you had never done anything with your psp.i beleive it finds it,loads it,and when something that needs security hacks,it loads the normal unhacked version of vshmain,which is really the only thing modded,but still there kinda.also basically recovery mode is you connect your psp to comp,load up the 1.0 index.dat and flash that so you psp says its a 1.0,then load,while in recovery mode,the 1.5 update to reflash the psp.its all very simple to me.

---

yeh i get the idea where if config file is not found on boot , it would load vshmain_real.prx... but i'm talking about when the config file was found on boot, and it loads the modified, and then you delete the config file... what it it THEN do?

Dark_Alex.O have 2 ideas/questions.first,wouldnt it be postble to make a mod to devhook so that this is loaded along with 2.71 to have like an epsilon bios-like firmware,or cant that be done.
Second,couldnt you have a backup on the memory stick of all of the resources that would be considered vital prx's so that if its a brick you can load those as default for recovery mode so that you could fix a really bad brick?or possibly have a dump of your exact firmware and just restore it through that or cant you do that either?

Zitat:

---

Zitat von RaZoRbe

ok, few questions

- What happens if you Format the memory stick when you are running this hack..
the config file would be deleted, and would it freeze or reboot or what?

- Did anyone try the recovery mode with the index.dat flashing? (i know it works with updating to 2.6)
how does it work?
* you first flash your index.dat, then it goes back to the menu and you run 1.5 eboot? or
* do you flash index.dat , reboot,run 1.5 eboot?

---

The Flash only uses the config.txt file when first rebooting the PSP...if you format the memory stick, this does nothing at all to the booted XMB......when you then power your PSP completely off & reboot, there is no config.txt file & the XMB reboots as if it were the original (no hidden icons, full boot video , no custom .prx loaded etc).
You would then need to re-instigate the config.txt in the SYSTEM folder & any .prx modules needed to load if you wanted to go to your own custom XMB...

just a thought here.....you could have 2 cards available...1 to boot a standard 1.5 XMB & one with the files needed for your modified XMB...boot from either to get the XMB of your choice.......a bit icky I guess but the best option for now.....

Keep em coming everyone....we are on a roll!

Zitat:

---

Zitat von Networkgamer

Dark_Alex.O have 2 ideas/questions.first,wouldnt it be postble to make a mod to devhook so that this is loaded along with 2.71 to have like an epsilon bios-like firmware,or cant that be done.
Second,couldnt you have a backup on the memory stick of all of the resources that would be considered vital prx's so that if its a brick you can load those as default for recovery mode so that you could fix a really bad brick?or possibly have a dump of your exact firmware and just restore it through that or cant you do that either?

---

From what I've read in this thread, that wouldn't work. In order for the recovery mode to launch, it needs those prx's. If they are corrupted, it can't load. Since the recovery mode can't load, there is no way it can restore the corrupted prx's.

Zitat:

---

Zitat von Networkgamer

Dark_Alex.O have 2 ideas/questions.first,wouldnt it be postble to make a mod to devhook so that this is loaded along with 2.71 to have like an epsilon bios-like firmware,or cant that be done.
Second,couldnt you have a backup on the memory stick of all of the resources that would be considered vital prx's so that if its a brick you can load those as default for recovery mode so that you could fix a really bad brick?or possibly have a dump of your exact firmware and just restore it through that or cant you do that either?

---

I think if you messed with a critical .prx, your PSP wouldent recognize your pressing "R" , maybe?

RaZoRbe, I think it only checks for the config file on boot-up and when you try to do something that requires those changes (left the PSP alone for 10 minutes, and I don't see the PSP's light flashing, meaning it's not reading anything.) But who knows....

Networkgamer, if I've understood correctly, the reason why it can't fix the serious prx issues that cause bricking, is because those prx's are needed to boot up Restore mode.
If Dark_Alex, or another dev, finds a way to enter Restore mode without the need of those prx's, then it would be possible to recover from any form of bricking.

EDIT: 3 answers in a row :ROFL:

I think that the only reason we cant unbrick PSPs that were bricked due to bad PRXs, is due to the reason that the recovery mode relies on the PRXs and so do the sony updates.

If Dark_Alex made this process standalone we could unbrick any PSP.

what i mean is backup the critical prx's and instead of loading the corrupt ones in flash have recovery method load backedup good ones that work.if you can redirect the prx's at startup to ms0/and then upon starting an app or something re direct them back to flash0/1,wouldnt that work?

I just rememebred somthing.

Wasnt TEX (Team Emergency eXit) working along time ago on "PSP DUEL BOOT" toggling the loading of a custom eboot on the MS on psp startup by default when the Wi-fi is on.

Maybe DA could use this idea (Would be steal if PSP Duel boot Actualy happened but never did) to toggle the custom Eboot loading, so you dont have to hold a button down to activate it.

Another nifty feature would be to hold down another button (such as L maybe) to load up a GUI on boot to toggle the settings insted of having to use external aplications to modify a txt file.

hey I dotn knwo what to do with all teh files under the "src" folder can anyone hlep the brotha out?

Zitat:

---

Zitat von Nutterbutter

I think that the only reason we cant unbrick PSPs that were bricked due to bad PRXs, is due to the reason that the recovery mode relies on the PRXs and so do the sony updates.

If Dark_Alex made this process standalone we could unbrick any PSP.

---

Hopefully that is possible...

Hmm, that depends....If you need said critical prx's to redirect the reading of the flash at startup, then no, for the same reason that you couldn't use Restore mode.

If you didn't....then it would be a damn good ideia.

Zitat:

---

Zitat von Bam-0

hey I dotn knwo what to do with all teh files under the "src" folder can anyone hlep the brotha out?

---

those are only for devs wanting to improve on this.it has no meaning if you want to use it.

thats the scource for dev's you dont need that folder.

read the readme next time :P

Zitat:

---

Zitat von cooldocy795

Why in the hell would we want that? Custom firmware could make it so we could run 2.6+ WITH homebrew.

---

Well, a custom firmware wouldn't be too handy if we couldn't downgrade to 1.5 (or 2.5/2.6) to flash it to our PSPs...

Please be open minded and considerate to others...

Thanks!

Peace!

Zitat:

---

Zitat von Smiffers

If I were to guess, FreePlay was just trying to see if he could. He does a lot of stuff for no reason :P.

---

Truer words have seldom been said.

Zitat:

---

Zitat von DarkDragon-X

Hmm, that depends....If you need said critical prx's to redirect the reading of the flash at startup, then no, for the same reason that you couldn't use Restore mode.

---

It depends on the prxs then?

Someone should test what PRX's are required to still be able to boot into recovery mode. using devhook :P

I supose....If to re-direct access from the flash to the memory stick you don't need the critical prx's, then you should be able to access the PSP (same as emulating firmware with Devhook)and re-flash it, fixing whatever prx could be corrupt, and un-bricking a PSP from...well anything.

Zitat:

---

Zitat von PS2MAN

I just rememebred somthing.

Wasnt TEX (Team Emergency eXit) working along time ago on "PSP DUEL BOOT" toggling the loading of a custom eboot on the MS on psp startup by default when the Wi-fi is on.

Maybe DA could use this idea (Would be steal if PSP Duel boot Actualy happened but never did) to toggle the custom Eboot loading, so you dont have to hold a button down to activate it.

Another nifty feature would be to hold down another button (such as L maybe) to load up a GUI on boot to toggle the settings insted of having to use external aplications to modify a txt file.

---

good idea ps2man, holding down R would be better for a boot menu (like f8 for comps) so that u can choose between recovery mode, boot XMB, and change the settings (which saves them onto the memory stick) i would have never thought of this! well i would have but i prolly wudnta posted it cuz im too lazy

Zitat:

---

Zitat von DarkDragon-X

Hmm, that depends....If you need said critical prx's to redirect the reading of the flash at startup, then no, for the same reason that you couldn't use Restore mode.

If you didn't....then it would be a damn good ideia.

---

no i mean have a backup on the memory stick,boot the psp,and it boots recovery mode from those prx's.the app then reflashes the psp with your original firmware dump that you had dumped previously.and then you boot the xmb with the backup prx's and re-direct them or flash the psp with the dump,then restart and you have a new 1.5.

Zitat:

---

Zitat von Networkgamer

those are only for devs wanting to improve on this.it has no meaning if you want to use it.

---

got cha sorry bro

Would be very good, though if it is bricked, I'm not sure how would the program start as you can't see what it is doing.

Zitat:

---

Zitat von DeMoN X

Someone should test what PRX's are required to still be able to boot into recovery mode. using devhook :P

---

You cant make the custom firmware program target the devhook version of 1.5. It always targets the flash, which means if you emulator 1.5 and tried to install it, it would install to your flash.

Zitat:

---

Zitat von XSAQZW

You cant make the custom firmware program target the devhook version of 1.5. It always targets the flash, which means if you emulator 1.5 and tried to install it, it would install to your flash.

---

Replace vshmain.prx with the one in the 150 folder (flash0/vsh/module) and add the recovery.elf to it as well, Actually what part is recovery.elf located in the flash by the way? Is it in vsh/module as well?

i tryed all that but it wouldnt boot.I copyed everything where it as supossed to go but the memory stick light kept blinking endlessly in the same pattern

Zitat:

---

Zitat von Networkgamer

i tryed all that but it wouldnt boot.I copyed everything where it as supossed to go but the memory stick light kept blinking endlessly in the same pattern

---

Odd, Devhook should emulate it? Do you need vshmain_real.prx as well perhaps?
Actually, I think its because devhook only emulates decrypted modules?

Zitat:

---

Zitat von Networkgamer

no i mean have a backup on the memory stick,boot the psp,and it boots recovery mode from those prx's.the app then reflashes the psp with your original firmware dump that you had dumped previously.and then you boot the xmb with the backup prx's and re-direct them or flash the psp with the dump,then restart and you have a new 1.5.

---

Well if you could boot recovery mode from dumped prx's in the memory stick, that would be the ****, since with recovery mode you can fix the PSP by just updating it. If the devs can find a way to use Recovery mode, despite the prx's in the flash (which I believe they will), well can you say "Unbrickable PSP's" ?

Double Post Merge

Zitat:

---

Zitat von DeMoN X

Odd, Devhook should emulate it? Do you need vshmain_real.prx as well perhaps?
Actually, I think its because devhook only emulates decrypted modules?

---

Yes, as it still uses vshmain_real.prx to boot up the PSP.

Maybe that's the cause of the crash?

Zitat:

---

Zitat von DarkDragon-X

Yes, as it still uses vshmain_real.prx to boot up the PSP.
Maybe that's the cause of the crash?

---

No idea, I've not checked it out fully yet but if you want to give it a go then go ahead :p , Just make a copy of your vshmain_real.prx using File Assistant or you could copy your org vshmain.prx and rename it to vshmain_real.prx (that should work, but I recommend using file assistant instead)

rename vshmain.prx from ms0:\dh\150\flash0\vsh\mo dule\ to vshmain_real.prx
copy vshmain.prx to ms0:\dh\150\flash0\vsh\mo dule\
copy recovery.elf to ms0:\dh\150\flash0\kd\

Zitat:

---

Zitat von ColombianCartel

rename vshmain.prx from ms0:\dh\150\flash0\vsh\mo dule\ to vshmain.prx
copy vshmain.prx to ms0:\dh\150\flash0\vsh\mo dule\
copy recovery.elf to ms0:\dh\150\flash0\kd\

---

That should be :

rename *ORIG* vshmain.prx from ms0:\dh\150\flash0\vsh\mo dule\ to vshmain_real.prx
copy *CUSTOM* vshmain.prx to ms0:\dh\150\flash0\vsh\mo dule\
copy recovery.elf to ms0:\dh\150\flash0\kd\

Lol freeplay was wrong the 3rd time :ROFL: :ROFL: :ROFL:

Zitat:

---

Zitat von Ralan

Lol freeplay was wrong the 3rd time :ROFL: :ROFL: :ROFL:

---

I won't be taking his word again, EVER! :p

Actually he wasn't, if you call this a custom firmware then you'd have to be an idiot.

Zitat:

---

Zitat von FreePlay

Yeah, I'm wrong. But here's one thing to consider: every time someone proves me wrong, it's a good thing for the community :p I'm your classic anti-hero! YAY!

First a 2.5/2.6 downgrader, then a 1.50 downgrader, then custom firmware. Keep proving me wrong and we eventually might have a TA-082 downgrader XD

---

Didn't I told you that it was possible ? lol

About TA-082 I am more sceptical, I have done some researches (thanks to Groepaz for the hint ), it seems that unlike what I and everyone tough the IPLs are not blacklisted, the problem seems to lie in the nand chip ID itself which is not recognised by older IPLs because the nand chip model changed in TA-082 is no in the id list until 2.50 IPL.

So we wont even be able to use IPLs such as the one in Ridge Racers afaik.

I feel very sorry for TA-082 owners.

but it IS custom firmware - it is an edited version of the 1.50 firmware on the flash drive therefore making it custom

Zitat:

---

Zitat von Fluff

Actually he wasn't, if you call this a custom firmware then you'd have to be an idiot.

---

What would you call it then?

Very nice work Dark_AleX.

i have to agree with everyone, it is indeed custom. Its a 1.0 firmware with customable features

Well got it working with DevHook....

Instead of trying out inumerous mumbo-jumbo's, I just dumped my Firmware, and copied into DevHook's 1.5 folder, presto and working.