I'm sure this has been said before, but.. the original 2.00 downgrader, which used a "tiff" exploit worked by accessing the cpu and running a program to read the flash, and re-writing it to tell it to run the 1.5 update EBOOT, the tiff exploit accualy worked because of a loophole in the tiff picture viewing code, the only reason it worked was because the psp would try to load a tiff picture, and read the code built into the file instead..
there is no longer a loophole in the code, it was accualy quite simple and easy for sony to fix it, just to add a few lines of code...
that is why the GTA exploit wont work for any tiff anything....
the only way that a downgrader could work would be if someone could access the flash files, and to re-write them how they wanted (to tell the psp to run the 1.5 eboot)...
and since the later firmwares wouldnt allow any debug code access, the system couldnt change the way it runs unsigned code...
I however havent yet figured out why someone cant change the 1.5 eboot to run.. it seems like if the 1.5 code within the eboot could be run, then the system would be able to compleetly re-write the flash with the 1.5 code...
now, let me ask, has anyone ever thought about taking code from a 2.7 eboot and using it within a 1.5 eboot to tell the system that it was signed code... why is it possible for everyone to program games and emulators.. but nobody has been able to edit the firmware updaters to be run as signed... if someone could just figure that out, any homebrew could be run on 2.01 all the way to 2.71...
Bookmarks