Thoughts On Firmware

Quote:

Originally Posted by Abstract3000

a

Exploits: MPH's loader is a very good example of an exploit, take for example loading the GTA Game on a 1.5 system though it actually requires a 2.0 - in this effect what they have done is designed a loader that basically tells the Game or ISO not to look for the 2.0 files on the system but rather look in a directory on the memory stick for the files instead, these are also the most short lived being that exploits can simply be patched by the developer closing the "backdoor" used in making this exploit happen then its nothing but a rat race to find the next “backdoor” to open.

Editing The Firmware: This would be the second easiest way of doing it though this is not very easy at all in actuality (I assume this is the method your referring to)- one reason is the fact that in school when learning to develop in any language you are taught to leave (notes/memos) in your code giving an explanation of what each script and function mean better to assist you when it comes down to having to go back and edit the code or make fixes for that matter. A developer like sony sure as hell would not leave any of this in their code and if so very little really giving you no easy way of figuring it out after all this would be a big “bend me over and $$$$ me in the A$$” idea and this would have been done a long time ago. But instead in effort to find some type of flaw in the firmware or even make your own door you first have to figure out what every bit of it means and from there find where you want to add that door or give word of the exploit and in most cases flaws are slim to none and if there is one they find it and fix it in the next version. So essentially this would take 2 people one trained in engineering hardware and another being trained in development with some type of knowledge of the hardware.
This way you have the developer who gives the idea of where he wants the door to be and the engineer would make sure that it was possible and from there they could code and recompile the firmware but though that sounds easy – there can be NO flaws in this whatsoever otherwise it would leave you with a brick or cause many other problems down the road making it a very risky venture to pursue and most people just don’t have the time or patience to pursue this method.

ok i get what ur saying but im not taking about so over the top firmware edit
now like you said understanding what each line of code is for would be imposable without any notes in the program (just learn C++ and love to leave myself notes) but i just mean basicly your first methodbut with a little twist
instead of looking for a backdoor make on ie. patch in 1.5's lack of need for ansignature by sony(forgive the funny wording)or something simmalar

never mind just reread your post and making your own backdoor was something u said

but patching over the signature thing would be maby a little simpler mabey

what about assembleing a new one with the .prx files from 1.50 and replaceing just the ones needed to play umds and the new features simmilar to the way mph game loader works to play umds but make a new firmware out of it

i commend your ambition.....and i love final fantasy.... but i think to get anyone to work on this....your goona have too do 1 of 2 things

1: simply be patient....or...

2: set up a pay pal donation "spot" for coder insentive...on a popular site....such as this one....get ahold of wraggster or dark savior or kaiser ....any of the moderators here r gr8 peeps just contact them after you have everything orginized...

by the way gameshark made a custom firmeware 1.5 already you can get it at this site
http://www.psp-hacks.com/category/10