PDA

View Full Version : about to use 2.71 downgrader


AvengedSevenfold Fan
September 5th, 2006, 01:12
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
September 5th, 2006, 01:17
Don't Brick!!! :)
The exploit runs throught the picture viewer...
K.L.
September 5th, 2006, 11:58
check for ta-82 motherboard!
razorak
September 5th, 2006, 12:12
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
September 7th, 2006, 01:36
check for ta-82 motherboard!

yup, check for TA-082 motherboard...

...and watch this vid!

WATCH THIS VIDEO (http://video.google.co.uk/videoplay?docid=1849498063912966574&q=PSP)
mavsman4457
September 7th, 2006, 02:08
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
September 7th, 2006, 02:42
i just saw that the other day on youtube
ryutoki
September 7th, 2006, 04:21
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
September 7th, 2006, 04:35
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
September 7th, 2006, 07:05
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.
Zion
September 7th, 2006, 13:35
By the way, the cleanest way to downgrade from 2.71 isnt to upgrade to 2.0 then down to 1.5.

the best and cleanest way is this...
Downgrade from 2.71 to 1.50. Then Downgrade from 1.5 to 1.0. Then upgrade to 1.5.

That way you have a 100% clean and bug-free 1.5 :D
VampDude
September 7th, 2006, 15:22
By the way, the cleanest way to downgrade from 2.71 isnt to upgrade to 2.0 then down to 1.5.

the best and cleanest way is this...
Downgrade from 2.71 to 1.50. Then Downgrade from 1.5 to 1.0. Then upgrade to 1.5.

That way you have a 100% clean and bug-free 1.5 :D

or 2.71 >> 1.50 >> 2.60 >> good 1.50
dejkirkby
September 7th, 2006, 15:40
or 2.71 >> 1.50 >> 2.60 >> good 1.50
No, this is still a "buggy" version of the 1.5 firmware.
MikeDX
September 7th, 2006, 15:45
How buggy are we talking? I've never had issues with it.
dejkirkby
September 7th, 2006, 15:57
I found that it freezes randomly sometimes and switches itself off, I did the whole 1.5>2.0>1.5 thing and it's been fine ever since.
ryutoki
September 8th, 2006, 05:14
This doesnt occur with the 2.6 downgrader? cause mine has been working fine but i dont want it to suddenly brick.

It also occurs with the 2.60 downgrader, but just not as bad. You should still upgrade to 2.00 and downgrader back to 1.50 just to be safe.