Are you not able to execute the updater on your memory card? If not, try updating via a UMD to 2.XX (like 2.00 or other) and then move on up to 2.82.
First of all, i'm a noob, so try to use the most simple language possible.
I downgraded to 1.5 from 2.71 using dark alex's downdater, just to play with some homebrew and whatnot. But i've decided i want to update to the standard official psp firmware 2.82, mostly because i'm getting GTA VCS.
I thought i would be able to simply run the EBOOT like a normal update. When i do this, it does the normal thing where it goes to the PSP screen, and then i see a screen where the letters are supposed to be, saying "You are updating your psp... etc", but the letters arent there, it is a blank screen with the X and O at the bottom. So cant update the normal way, and i dont know what to do.
Please help!! it would be much appreciated!!
Are you not able to execute the updater on your memory card? If not, try updating via a UMD to 2.XX (like 2.00 or other) and then move on up to 2.82.
Why do you want to go to 2.82 anyway vice city stories will need 2.81 and a new devhook will be released
PSN ID: splodger15
get the gta disc, insert it, it will have the update on there-below the game icon
i've tried loading it from a UMD such as GTA LCS which has 2.00 on it, but it does the same thing. It executes, but i cant do anything from the installation screen.
Try restoring default settings then start it again
PSN ID: splodger15
GTA:VCS only requires 2.71. You would be a fool to upgrade.
Just use devhook to run it, and all will be fine
Cloudy
We'll... in the past, when I did decide to go insane and updrade to 2.70 or 2.71 (not further than that), if I had faked the firmware version number (like showing 1.45, 2.92 or 3.40 instead of 1.50) previously using X-flash and restored to 1.50, the updater would say it's corrupted. In fact it's due to the modification of 2 filea on the PSPs flash memory called index.dat and version.txt. If that was the case, I'd downgrade to 1.00 and start an update from there (in my case it was to get a clean installation of 1.50).
Maybe you could try downgrading to 1.00 and then start the 2.82 updater from there, or use device hook instead if you get it to work. Remember, it's a suggestion and it's up to you on how you're going to go about it.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks