Help the PSP 3D community grow!
Vote for us below:
| | Getting Started/Help/Tutorials - Just bought your PSP and need some basic help using it or loading homebrew? |
Welcome to PSP3D.com - Sony PlayStation Portable News, Homebrew, Hacks, Reviews, Videos, Mods, Forums!
You are currently viewing our website as a guest, which gives you limited access to reply and interact to discussions and other members. By joining our free community, you will be able to post topics in the forums, communicate privately with other members, vote in polls, and access many other special features.
Registration is fast, simple, and absolutely free so join our community today!
|
03-12-2007, 04:25 PM
|  | Camouflage Condoms: They won't see you coming
My Mood:  | | Join Date: Nov 2005 Location: Surrey, UK Age: 23
Posts: 1,310
Points: 215.28 Donate | | | Could be. Have you done everything on the list? |
03-12-2007, 04:28 PM
|  | Senior Member
My Mood:  | | Join Date: Nov 2005 Location: encrypted beyond the update eboot
Posts: 301
Points: 11.69 Donate | | | have you tried upgrading to 3.03 the offical firmware? or you could probably delete all files in flash1 and flash0 then get some1 to send u there files and put them where there post to be that should work |
03-12-2007, 04:35 PM
|  | Moderator / Pastafarian
My Mood:  | | Join Date: Jan 2006 Location: sda1:/sys/kernel
Posts: 2,422
Points: 356.24 Donate | | Let's take a look... Quote:
Originally Posted by pj1115  After each step, reboot and try to go to the XMB:
[Remove UMD]
1. Check for TA-082/086.
2. Delete all files in Flash1
3. Then run a CHKDSK on Flash1 through recovery with write access (chkdsk X: /F).
4. Restore 3.10 OE-A again.
5. Leave your battery out for 15 minutes. You get a temporary brick if you use Devhook on OE.
6. Format your memory stick, and try without one inserted.
7. Run a CHKDSK on Flash0 through recovery (without write priviledges; ie, like so:
'chkdsk X:'). If any errors are found, it's up to you if you want to run one that will correct it: (chkdsk X: /F).
Not sure what to do after that... | - Yep.
- Uh huh.
- Yeah.
- Three times.
- Actually, I haven't. I'll try that, but I haven't used Devhook on this PSP...
- I haven't formatted it, but I have tried without one.
- No errors found.
So I'll try 5 and 6, but I'm not sure if they'll work...  Quote:
Originally Posted by dc psp have you tried upgrading to 3.03 the offical firmware? or you could probably delete all files in flash1 and flash0 then get some1 to send u there files and put them where there post to be that should work | I don't want to upgrade to the official 3.03, and I can't anyway as I can't get to the XMB. And I've already tried restoring both flashes. |
03-12-2007, 04:46 PM
| | | Camouflage Condoms: They won't see you coming
My Mood: | | Join Date: Nov 2005 Location: Surrey, UK Age: 23
Posts: 1,310
Points: 215.28 Donate | | | Five is actually both the most sensible and safest thing to try. Devhook temporarily stops the PSP from booting because it is remembered for a short period in the memory. This is known to happen occasionally on OE firmwares, even without DH.
If that doesn't work, it's internal hardware damage, no question. Unless, of course, it's your iDstorage; in which case, you need a backup from your PSP or you're screwed.
Last edited by pj1115 : 03-12-2007 at 04:49 PM.
|
03-12-2007, 04:55 PM
| | | Moderator / Pastafarian
My Mood: | | Join Date: Jan 2006 Location: sda1:/sys/kernel
Posts: 2,422
Points: 356.24 Donate | | | But how would the idstorage be affected in any way by restoring default settings? (Or at least trying to...)
EDIT: And, TBH, I don't really fully understand what the idstorage is. I know it helps to boot the firmware, and that it's really important - what else? And what are the chances of it being damaged?
Last edited by dorkdork777 : 03-12-2007 at 04:58 PM.
|
03-12-2007, 05:08 PM
| | | Senior Member
My Mood: | | Join Date: Nov 2005 Location: encrypted beyond the update eboot
Posts: 301
Points: 11.69 Donate | | | but if u were to upgrade to offical 3.03 you could downgrade to 1.5 then to 3.03 oe-c agian try through recovery mode |
03-12-2007, 05:19 PM
| | | Camouflage Condoms: They won't see you coming
My Mood: | | Join Date: Nov 2005 Location: Surrey, UK Age: 23
Posts: 1,310
Points: 215.28 Donate | | iDstorage is where alot of the systems unique data is stored. Things like the serial number, MAC address (not the actual one, just the one visible thorugh the XMB), and region are here. It also stores alot of data that the IPL uses; for instance, on a TA-082 a certain key that the IPL loads from is not one that 1.50 will understand, hence the boot sequence fails. It's corrupted and some stuff is switched around in order to downgrade. Click here to learn more about why 1.50 will not boot.
More information about iDstorage here. Don't mess with it if you don't know what you're doing.
I doubt the IdStorage is the problem. The only things to modify it are re-writers, TA-082 downgraders, and customizers. |
03-12-2007, 06:14 PM
| | | Moderator / Pastafarian
My Mood: | | Join Date: Jan 2006 Location: sda1:/sys/kernel
Posts: 2,422
Points: 356.24 Donate | | Quote:
Originally Posted by pj1115 I doubt the IdStorage is the problem. The only things to modify it are re-writers, TA-082 downgraders, and customizers. | Well, that's one thing off the list. I seriously doubt it was a hardware issue too, as I think the problem was caused by my failed attempt to restore system settings. Quote:
Originally Posted by dc psp but if u were to upgrade to offical 3.03 you could downgrade to 1.5 then to 3.03 oe-c agian try through recovery mode | Wouldn't it be a better idea to upgrade to 2.71, so I can downgrade through the TIFF exploit? But I don't want to do that TBH, because if my error somehow disallows the XMB to boot but allows the recovery mode, I'll have no chance of restoring, as 2.71 has no recovery mode. |
03-12-2007, 06:36 PM
| | | Camouflage Condoms: They won't see you coming
My Mood: | | Join Date: Nov 2005 Location: Surrey, UK Age: 23
Posts: 1,310
Points: 215.28 Donate | | Ehm, this is a tricky situation. If it's not Flash1, it's not your firmware, it's not IdStorage, and it's not your memory stick, I'm not sure.
Did you try formatting flash1 with this tool? There must be something you've done wrong. |
03-13-2007, 01:31 PM
| | | Moderator / Pastafarian
My Mood: | | Join Date: Jan 2006 Location: sda1:/sys/kernel
Posts: 2,422
Points: 356.24 Donate | | | I'll try that now. BTW, I've decided on how many points the person who helps me will get. But I'm such a prick that I'm putting it into binary.
01001001 00100000 01110111 01101001 01101100 01101100 00100000 01100111 01101001 01110110 01100101 00100000 01100101 01111000 01100001 01100011 01110100 01101100 01111001 00100000 01101111 01101110 01100101 00100000 01110100 01101000 01101111 01110101 01110011 01100001 01101110 01100100 00100000 01110000 01101111 01101001 01101110 01110100 01110011 00101110
HINT FOR DECODING: Snarkles. | |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | | | | Thread Tools | | | | Display Modes |  Linear Mode | 
Posting Rules
| You may not post new threads You may not post replies You may not post attachments You may not edit your posts
HTML code is Off
Points Per Thread View: 0.00 Points Per Thread: 15.00 Points Per Reply: 0.50 | | | | |
credit goes to onyx7 i just made the name 
