new 2.6 Donwgrader?

Ya i agree with you but where there is a will there is a way. I think that someday you'll be susprised about how good the devs's and hackers are when it comes to getting what they want homebrew for psp. Well anyways i'm never upgrading i'll probaly buy another psp in the future for updates and UMD's and PS3 compatibility. But anyways Gp2x is a great console almost bought one. But there wont be a N64 emu for it will there. Recently it seems that the psp is still better for homebrew because sony is making a PS1 emu,There are N64 emu's coming aloung nicely, Even NJ creator of Neo geo cd emu for psp is making a Neo Geo AES emu and found a way to fix the ram problem, Plus all other emulators with the exception of GBA(which will get better in time once someone finishes it) They all run perfect or near it. And when everythings done i think the PSP will prove to be the ultimate portable homebrew console even greator than Gp2x. (that was ment for homebrew)

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...

At this point almost everything has been tried. and 99% of exploit possibilities have been exhausted. If you think you have an original idea then google it and see that it has been tried and has failed. Also, like i wrote earlier the new consoles have hardware which is incompatible with older firmware so any downgrades will have to be encrypted and also custom. Lastly i got the 1.5 update to boot on my 2.6 psp and it bricked it even though the update ran as it should. which further supports my what i said. the only available option is to recreate the dnas or encryption to make exploit free homebrew. I think that the newer firmware even on a psp-1001 or original psp will still brick after a downgrade attempt because of some crap sony put into the new firmware. I recently preordered the psp modchip and am looking forward to that instead of a band-aid or downgrader.

Quote:

---

Originally Posted by metalspector

Even though I don't know about downgrading my friend who upgraded to 2.7 like 4 days ago started working on a exploit he found on the RSS , 2 days ago he showed me that he with his 2.7 psp went to the RSS thing ( his house has wi-fi ) and loaded from there an e-loader , he doesn't want to give me the files or post them on the internet cause he says that he worked gard for it and don't want anybody else to have it. Anyways it sucks if you have to be on a wi-fi hotspot to play it.

---

Dude, I've heard this same scenario on like 5 other PSP forums it's like a CHAIN LETTER or something.

Closed