awesome, ill have 3 psp's today that work, but i need cash....hmmm. gamestop here we come!! haha
awesome, ill have 3 psp's today that work, but i need cash....hmmm. gamestop here we come!! haha
hmm, i got thinking, now i'm not bricked [nor have i before, lol] buuut, we use the official 1.50 update, what if we used a 3.52M33 update instead of the 1.50, the 3.52M33 update isn't kxploited, for it's just a common 1.00 eboot as the $ony updates are. so any ideas? i mean they do have to use a homebrew capable PSP, so making the update isn't really an issue
so if it's someone stuck on 3.52 they can use a friends PSP and go straight to 3.52M33 if this is even plausable
ya, but i meen the actual update, not the update creator.....cause it's a separate single eboot
u can only downgrade to 1.50 then from there u can update to any custom firmware
BRILLIANT WORK!!!! Thank you!
For everyone needing help, use this tutorial: http://f6y.ath.cx/pspdev/PandoraGuide.html
dang, people... I thought I answered all the questions that have been posted again on pg25 and after.
you can always fix a memory stick if it messes up, just not with a psp. Use a memory card reader and format it with your PC. Your psp will recognise it after that.
FOL... are you using an A/C adapter to get into service mode or are you using a USB thing with a power plug on it. The USB thing won't work. What I did, is use another battery to boot into the XMB, then swapped it with my pandora's battery (while the PSP is still powered on and plugged in) and reflashed the pandora's battery. Then, I did a complete power down, swapped batteries again and turned it on. After that I could swap out again (now using the former pandora) and it works perfectly normal.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks