Editing Updating From Old Custom Firmware

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 5: Line 5:
Another common issue is that some CFWs blocked installing official updates on purpose either with an error, usually "DADADADA", or by spoofing the version to a crazy high number (5.50 GEN spoofed the version to 9.90). This was to prevent accidental updates to official firmware back when it was much harder to install custom firmware. That block was a good thing back then, but now that we WANT to be on the newest OFW in order to use modern day CFW, it just makes things harder.
Another common issue is that some CFWs blocked installing official updates on purpose either with an error, usually "DADADADA", or by spoofing the version to a crazy high number (5.50 GEN spoofed the version to 9.90). This was to prevent accidental updates to official firmware back when it was much harder to install custom firmware. That block was a good thing back then, but now that we WANT to be on the newest OFW in order to use modern day CFW, it just makes things harder.


This page is here to help you get your PSP 1000 or 2000 with old CFW (pre-6.xx) up to date and ready for modern CFW (6.6x). If you're not on CFW or 1.50 OFW already, this guide won't work for you and you'll need to look into setting up a version of Despertar del Cementerio with a jigkick battery in order to get on a CFW first.
This page is here to help you get your PSP 1000 or 2000 with old CFW (pre-6.xx) up to date and ready for modern CFW (6.61). If you're not on CFW already, this guide won't work for you and you'll need to look into setting up a version of Despertar del Cementerio with a jigkick battery in order to get on a CFW first.


== Preparation ==
== Step One: Knowing Your Motherboard ==


The following downloads will have everything you'll need for this guide, download the one that applies to you and copy everything inside the .zip file to your PSPs memory stick.
You need to know what motherboard is inside your PSP before continuing, as it's important for a step you may need to take. Since you're already on CFW, this part should be easy.  


Old CFW Update Kit: [https://drive.google.com/file/d/17t73cvQIlkMzW1rmtSDl0-9K5j4UoV-D/view?usp=sharing Google Drive] | [https://mega.nz/file/eM1XEIwb#e4QxpcXAcgdUn2s_Pfo84sHxhtOkHHj3MVIklrriUDw Mega]
The following download will have everything you'll need for this guide, download it and copy everything inside the .zip file to your PSPs memory stick.


1.50 OFW Update Kit: [https://drive.google.com/file/d/1hiA4BtfEWxN2pdnulLRLAquJ9EUWAeCp/view?usp=drive_link Google Drive] | [https://mega.nz/file/GIFFXZYT#QZaoP70NqbaERRDTnAH8gUsdnNhLFeF9zffZReUyiGc Mega]
Old CFW Update Kit: [https://drive.google.com/file/d/1hlR1prYLPeWQ63-79hCmcCMhmxcwfCgP/view?usp=sharing Google Drive] | [https://mega.nz/file/LIF3xQoB#fgo3e5N7lup1VVKKObPN3VjKE3YdQtVmiCAO3vCNthU Mega]


Note: The Update Kits include the 6.61 OFW update by default. If you would rather have 6.60 instead, replace the EBOOT.PBP in PSP/GAME/UPDATE/ with the one from [https://archive.org/details/OFW660 here]
Run "pspIdent v2.0 by Yoti" on your PSP. In the blue section near the bottom, you'll see the model (PSP-x00x) followed by the motherboard (TA-0xx). Take note of the TA part, this is what you need to know for a future section.


== Step One: Updating/Downgrading to 5.00 m33 ==
[[File:PspIdent For Old CFW Update.png|frameless|alt=pspIdent]]
 
== Step Two: Updating/Downgrading to 5.00 m33 ==


Updating to 5.00 m33 from an older CFW will bypass the DADADADA error. If you're on 5.50 GEN, downgrading to 5.00 m33 will remove the 9.90 version patching. If you're on 1.50 OFW, installing 5.00 m33 will allow you to run the other tools necessary to fix your IDStorage issue. If you're already on 5.00 m33, you can skip to Step Two.
Updating to 5.00 m33 from an older CFW will bypass the DADADADA error. If you're on 5.50 GEN, downgrading to 5.00 m33 will remove the 9.90 version patching.


[[File:DADADADA Error.png|frameless]]
[[File:DADADADA Error.png|frameless]]
Line 27: Line 29:
[[File:Recovery Flasher For Old CFW.jpg|frameless]]
[[File:Recovery Flasher For Old CFW.jpg|frameless]]


Once it's done and you're on 5.00 m33, you will be able to run the official 6.6x (either 6.60 or 6.61) update, you should do that now. If you see a DRNFFFFFxx error after launching the 6.6x update, continue with Step Two below. If you see the option to start the update, you're done and can skip to Step Four.
Once it's done and you're on 5.00 m33, you will be able to run the official 6.61 update, you should do that now. If you see a DRNFFFFFxx error after launching the 6.61 update, follow the section below. If you see the option to start the update, you're done and can move on to Step Three.
 
== Step Two: Knowing Your Motherboard ==
 
You need to know what motherboard is inside your PSP before continuing, as it's important for the next step. Since you're already on CFW, this part should be easy.
 
Run "pspIdent v1.5 by Yoti" on your PSP. In the blue section near the bottom, you'll see the model (PSP-x00x) followed by the motherboard (TA-0xx). Take note of the TA part, this is what you need to know for Step Three.
 
[[File:PspIdent For Old CFW Update.png|frameless|alt=pspIdent]]


== Step Three: Fixing the DRNFFFFFxx Error ==
=== Fixing the DRNFFFFFxx Error ===


This error code appears if your IDStorage is corrupted or patched and prevents you from applying the update. In order to proceed, you'll need to fix your IDStorage.
This error code appears if your IDStorage is corrupted or patched and prevents you from applying the update. In order to proceed, you'll need to fix your IDStorage.
Line 43: Line 37:
[[File:Updater IDStorage Error Screen.jpg|frameless]]
[[File:Updater IDStorage Error Screen.jpg|frameless]]


Run Key Cleaner on your PSP. It will attempt to determine your motherboard and region based on the current IDStorage, but there's a small chance your IDStorage is corrupted enough for these to be wrong, so use the info you got from pspIdent in step two instead.
Run Key Cleaner on your PSP. It will attempt to determine your motherboard and region based on the current IDStorage, but there's a small chance your IDStorage is corrupted enough for these to be wrong, so use the info you got from pspIdent in step one instead.


Press X to analyze keys, then press the button that corresponds to your motherboard's group. Key Cleaner will scan your IDStorage keys and determine if any need to be fixed. If you're prompted to fix any keys, you should do so.
Press X to analyze keys, then press the button that corresponds to your motherboard's group. Key Cleaner will scan your IDStorage keys and determine if any need to be fixed. If you're prompted to fix any keys, you should do so.
Line 51: Line 45:
[[File:Key Cleaner For Old CFW.jpg|frameless]]
[[File:Key Cleaner For Old CFW.jpg|frameless]]


== Step Four: Update To 6.6x ==
== Step Three: Update To 6.61 ==


You should now be able to launch the official 6.60 or 6.61 update and complete it without issues! After that, you can install your 6.6x CFW of choice and enjoy the modern PSP era.
You should now be able to launch the official 6.61 update and complete it without issues! After that, you can install your 6.61 CFW of choice and enjoy the modern PSP era.
Please note that all contributions to PSP Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PSP Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)