about to use 2.71 downgrader

[AvengedSevenfold Fan]

tomarrow im downgrading my friends psp from 2.71. is there anything special about it that i should know? and what do i run it with? and how does it work and what did they exploit?

[Video_freak]

Don't Brick!!!
The exploit runs throught the picture viewer...

[K.L.]

check for ta-82 motherboard!

[razorak]

make sure u have all the files needed and after a successful downgrade, update to 2.0 and downgrade with mph back to 1.5 to remove bugs and then perhaps install custom firmware ^^

[VampDude]

check for ta-82 motherboard!

yup, check for TA-082 motherboard...

...and watch this vid!

WATCH THIS VIDEO

[mavsman4457]

It makes me angry to see someone throw a perfectly good brick like that. Give it to me, I'll get it modded, then it will be a perfectly good PSP.

[AvengedSevenfold Fan]

i just saw that the other day on youtube

[ryutoki]

The 2.71 downgrader leaves you with a slightly corrupted version of the 1.50 Firmware. If you use this corrupted Firmware, there is a much higher risk that you could brick your PSP easily. But don't worry, this problem is easy to fix. All you have to do is this: after you have downgraded from 2.71 to 1.50, before you do ANYTHING else at all, you should upgrade to 2.00, and then downgrade back to 1.50 again. The 2.00 to 1.50 downgrader leaves you with a perfectly clean version of the 1.50 Firmware.

[cartmandude14]

The 2.71 downgrader leaves you with a slightly corrupted version of the 1.50 Firmware. If you use this corrupted Firmware, there is a much higher risk that you could brick your PSP easily. But don't worry, this problem is easy to fix. All you have to do is this: after you have downgraded from 2.71 to 1.50, before you do ANYTHING else at all, you should upgrade to 2.00, and then downgrade back to 1.50 again. The 2.00 to 1.50 downgrader leaves you with a perfectly clean version of the 1.50 Firmware.

This doesnt occur with the 2.6 downgrader? cause mine has been working fine but i dont want it to suddenly brick.

[pibs]

thats exactly what i did with the 2.6 just to make sure.
downgrade from 2.6 >1.5 then upgrade 2.0 and downgrade to 1.5...... probably didnt need to do this but just incase.