Ok, let me try and explain...
I've been having some problems with my psp lately. Small glitches mainly, icons not showing up correctly, buttons doing things they shouldn't, and games not loading so this morning I decided to reflash my psp. I put the 1.50 official update into e:/psp/game/recovery/eboot.pbp (all in caps) and then turned on the psp holding R to enter recovery (I'm on 3,40 oea by the way), and chose "run program at [path].pbp". The screen went black and the memstick light started blinking. after a few seconds it stopped. after a few more seconds the psp turned itself off. I turned it on again and it loaded up normally then BOOM! BSOD! "registry is corrupt press O to fix and restore default settings...". I pressed O and the screen went black and the psp turned off. Turned it back on again and I get the same thing. I must have tried about 15 times now and no luck.
Fine, I've got a backup of flash0 and flash1 on my computer anyway. Turn off, turn on holding R, Choose advanced, choose toggle flash 1 usb, copy over my flash 1 backup including registry files, disconnect psp reboot, still getting BSOD! ok, Tried copying over the files again and found that the psp had deleted everything in flash1!!!!!!O_O :@eek! if it's doing that to flash 1 then what's it doing to flash0!! Tried again anyway, rebooted, BSOD again! Checked flash 1 again on the computer found it had erased everything again!
I desperately need help as I'm going on holiday in a few days and I can't live without my psp! I'll be away from my computer which will make it difficult to fix if I can't get help withing the next few days.
Please help me!!!!!!
(p.s. sorry about the essay!)
i think you are kinda screwed
i agree - it specifically states NOT to run the official updates from custom firmwares. you must use the recovery program provided to either reinstall the same custom firmware (if its provided) or reinstall an older one.
im not sure actually how you can return to an official update. i THINK it might be possible if you use the 1.0 firmware flasher released a long time ago and then going from there to 1.5 HOWEVER i will NOT be responsible if it doesn't work - and especially if it bricks your psp because theres a very high chance of that.
also this definitely won't work for ta-082 and ta-086 people because those psp's can't run on 1.5 anyway.
your best bet - if you still have it - is to reflash the same dxar (or if on m33, the eboot file) via recovery - then at least your psp will still be fine. i don't know if its possible to run the m33 firmware creator under recovery however in theory it should be possible to run the flasher part. your in uncharted territory here - good luck.
Like z7shaft said, you can't just run the 1.5 update from the recovery menu, it will screw things up. The proper way to downgrade to 1.5 is using the OERecovery program, it was originally in the 3.02 OE-A download, but was left out of subsequent updates. I wouldn't recommend doing that now though because I don't know if it will fix your flash1, and if it doesn't then you won't have a recovery menu anymore. I'd suggest trying to reflash OE using the recovery menu, that's probably the best way to try and fix what you did. I can't guarantee that it will work though.
@Anger: If the PSP is on a custom firmware then it can go to 1.5 no matter what motherboard it has, because the idstorage will already be patched.
I had the same problem, but I was going from 3.40 OE to 3.51 - Using M33's 3.51 I either get a continuous, repeated "corrupt press O blah blah" screen, or just a blank background with the wave, clock, battery, nothing else. I'd try to delete everything on flash1, and it would all reappear when rebooting, or it would all delete except the registry foler (and Windows would say it couldn't delete it, repeatedly) - I actually just flashed 3.40OE back onto it using Recovery (since that's all I could get to) and all was well again. I'm gonna try some experimental (AKA - dangerous) mods, like hex-wiping flash1, etc, and let you know how it goes. *(I'm not a moron. This PSP has a dead UMD drive, a screen with distortion from a water spill, and a few other flaws, all from its previous owner - I got it free, so it is my test device. I'm not worried about 'corrupting' flash1 permanently, because I'll simply pick up a mod for it and start messing around with that.)
For your information, I can find no reason to go back to official 1.50 between flashes; I've never had to do this in the past. I've always gone straight from stock 1.50 to the OE, then if I needed an update I went to the newest OE from the older OE.
Peacefully Disturbed Wrote:@Anger: If the PSP is on a custom firmware then it can go to 1.5 no matter what motherboard it has, because the idstorage will already be patched.
i didnt realise they fixed that problem. but does that mean people can use the official updater to get to 1.5 on a ta82 or 86 mobo after its been patched? and does the patch stay forever?
z7shaft Wrote:for DaninFuchs: have you trying using any special flash1 formatter? there is one... search it :)
Aww, that's too easy. I'd rather be able to say "Yes sir, I fixed my flash1 problem with a hex editor." but I suppose that'll do if it must..hehe.
EDIT - Yeah okay, flash1 format DID NOT change the problem whatsoever, so I'm gonna have some fun now.
Anger Wrote:i didnt realise they fixed that problem. but does that mean people can use the official updater to get to 1.5 on a ta82 or 86 mobo after its been patched? and does the patch stay forever?
I'm not sure what you mean by use the official updater, obviously they can only directly update to 1.5 if they are on 1.0, which they can do. If they are downgrading from official or custom firmware then they would of course still use the official 1.5 update.
The patch changes one key (key5) in the idstorage, the key can be reverted back to it's original state if they use an app like Key Cleaner or Key Manager. The only reason to change the key back though is if they are upgrading to official firmware 3.30 or higher, because Sony implemented checks in those updaters to not allow motherboards with a patched idstorage to update.
Plus how did you think TA-082 and TA-086 PSP's got onto custom firmware? They have to downgrade 1.5 first.
maybe i don't explain clearly (as usual :P)
it was my understanding that ta-082 and ta-086 could not use any firmware below the version they came with (and it was usually 2.0+ if memory serves), so that meant installing 1.5 was not possible, either by downgrader, or by the 1.0 flasher route (installing the 1.0 then using the official update to get to 1.5). now i know that downgraders were created for the ta mobos (to allow them to get to 1.5) but from what i read they couldnt then use any official update except custom firmware or a firmware higher than what was factory installed. was i wrong in my understanding of this?
also sorry for getting way off topic here - as stated your best bet is to either reinstall what you have (if possible) or try the riskier routes mentioned before - official updates are a no-no. it sounds like some of the files are gone - if you could find out exactly which ones you might be able to restore the xmb enough to reinstall the custom firmware from scratch but if you don't have a source for the files then you may not have a hope that way. you could ask if someone has a full flash dump of the firmware your using and just copy over what doesn't exist (or is significantly different). this i think is your safest bet (untill you start messing with the kd/kn and nodule/module folders). i suspect the problem is not in the kd folder or the module folder. so if you decide to check it check everythig but those 2 folders because without those your psp wouldnt have recovery at all. you are soooo lucky because it means you have a chance of fixing this if you do the right thing.
so get a dump and copy over firstly only missing files then reboot the psp and reset the settings (you should get a bsod or rsod the first time) if it still doesn't work then your looking at corrupt files so you MUST be carefull if your overwriting files you think are corrupt because if you overwrite any of those used for recovery then your half brick will be a full brick. take it one step at a time.
Anger Wrote:maybe i don't explain clearly (as usual :P)
it was my understanding that ta-082 and ta-086 could not use any firmware below the version they came with (and it was usually 2.0+ if memory serves), so that meant installing 1.5 was not possible, either by downgrader, or by the 1.0 flasher route (installing the 1.0 then using the official update to get to 1.5). now i know that downgraders were created for the ta mobos (to allow them to get to 1.5) but from what i read they couldnt then use any official update except custom firmware or a firmware higher than what was factory installed. was i wrong in my understanding of this?
You were a little off. TA-082's and TA-086's were designed to not allow any firmware under a specific version. The first downgraders for them corrupted a few idstorage keys to let them get to 1.5, then it was discovered that only key5 needs to be changed. Once the idstorage is patched TA-082 and TA-086 motherboards can run almost any firmware version (official or custom). The only firmwares it can't run when patched are official firmwares 3.30 and up, that's because Sony put checks in the updaters for those to stop patched motherboards from upgrading.
A patched TA-082 or TA-086 can run official firmwares 3.30 and up if key 5 is restored though, to do that they have to downgrade to 1.5, upgrade to 2.71 and restore the idstorage to it's original state using Key Cleaner or Key Manager, then upgrade to whatever official firmware the user wants. That is all pretty pointless though unless that person has more than one PSP.