-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downgrading PSP 2000 using Chronoswitch v7 from 6.61 to 6.60 - error CAAFFFFFCF7 #1
Comments
Interesting issue:
|
Hey Davee, thanks for getting back to me. Here are my replies:
No, from PSX-Place, once a one of the Reddit users told me about the GitHub version, I checked and compared both, they were the same files (exact same size md5 etc), I did download the one from this GitHub after and the same error appears.
I tried this, it would just hang on the CFW, as in when it tries to go into the OFW firmware screen (where the error is), the black scree just before this comes in then restarts the PSP.
The current CFW I am using is temporary, Pro C2.
Yes, also tried this after the above from CFW failed, the error still attains everytime I try to use this, I have tried this with both OFW 6.60 and the 6.20 versions, but on both times it just keeps giving me the same error.
Yes, quite a few years back directly from Japan, its a day one sealed release final fantasy LE PSP 2000.
As I have no idea what this means, I can safely assume that I have not :), as all I have done is just had a non permanent CFW installed on the PSP, allows me to boot into CFW rather than the perma version.
Definitely no, again same answer as above would apply, I only had basic plugins and themes installed, with backups of my UMD's stored on the memory card, but nothing to do with the internals of the PSP itself.
Yes, as there is only one source I go to, its the Wiki PSP page listed with all the OFW and their direct Sony links, regarding the downgrader same would apply, there is only one chronoswitch file, and its from the PSX place, Wololo and your GitHub, all of them are the same files. On a side note, I removed pro c2 CFW, and applied LME (non perma), as someone suggested me to try a different CFW to see whether the downgrader would work possibly due to the CFW I was using, after 2 hours of doing the same steps as I did on the previous CFW, this sadly still did not work, I am just mind boggled as to what the problem could be, the PSP has been factory reset after removing all remnants of the CFW's using the installer methid to remove them safely, I have nothing installed on it, just the basic OFW, hopefully hoping that there is a fix for this, in which I can then downgrade the OFW successfully. Please let me know if there is anything you'd require, would be happy to oblige Davee. RippzEE |
I have same program. |
@BlueFang Can you answer the above questions and provide a screenshot of your motherboard info also. |
Some people have the same problem. |
I get same error with a my 3000 (FW6.61 Infinity v1, TA-095v2, 09g). My answer to each question is the same as @BlueFang. Even ofw6.61 can't downgrade with the v6~7, but qwikrazor87's Downgrader_661.zip can. |
Hey Davee, as an update, still not managed to downgrade, but I thought I might do some exploring with the flash files. I've uploaded 2 text files, one for updater log, and the other is the version file of the PSP. Please take a look at those, to see what it all means, maybe the updater log could possibly help in this? I'll upload the files here now:
Thanks RippzEE |
Hi, I have same problem. I would like to update Infinity to version 2.0.3, but I cannot because infinity 1 cannot be removed from my PSP due to the CAAFFFFFCF7 error. So I'm stuck at infinity 1. My board is TA-090 v2. The other questions have the same answers as the boys above me. Thanks UPDATE I found out that this fix was used long ago on these boards to succesfully downgrade. Unfortunately, the fix exists only for version 6.60. |
Hello guys. @rippzee @BlueFang @pettiagalla @phobbi I think the issue comes from IDStorage. I am reversing it (see https://playstationdev.wiki/pspdevwiki/index.php?title=IDStorage). I would need dumps from your PSP to check where the issue is. May you dump your PSP IDStorage using for example: IDStorage contains information about your PSP (PSID, MAC address), but nothing compromising (it does not embed infos about the owner (credentials, history, etc...) Please upload your dump and share the link here for analysis. Thanks |
@CelesteBlue-dev |
@pettiagalla Thank you. In the archive you send we can see it misses some leaves, especially leaf 0x51 which is needed for update/downgrade because it embeds the minimal FW version. |
Hey CB, Thanks for the reply and also looking into a probable fix for this, apologies for the late reply regarding this though, been very busy. I will upload my IDS later today for you, please bear with me :). I have also linked back to an updated Reddit thread, which will indicate to other users with PSP's to upload their IDS from PSP's that have this issue too. Thanks again CB :) LINK:
|
Interesting that people who have not done any idstorage modifications have idstorage modifications :) |
I see 2 different patients affected by this disease:
About PSP 09g, we have a lot of cases of issues even since Infinity 1.0, often caused by previous downgrading to FW 6.20. It seams that Indeed @pettiagalla had previously downgraded to FW 6.20. @BlueFang what about you ? @rippzee I'm still waiting for your PSP IDStorage please. |
Hello @CelesteBlue-dev Here's mine IDStorage. I apologize for the late reply. Thank you for your work on this issue. https://mega.nz/#!O1RWFYAY!qYOylwpRtw77QMV167goLA64INK36vC_FWaiOBvMJA8 |
@phobbi Thanks ! Similarly as @pettiagalla 's PSP, your PSP misses IDStorage leaf 0x51. Now the only thing I have to do to confirm this is the cause is to test on my own PSP. I have just bought two pandorable PSP for testing, and by "luck" one of them also doesn't have the 0x51 leaf. Let's see if Chronoswitch gives the same error as on your PSPs (CAAFFFFFCF7). |
@CelesteBlue-dev @DaveeFTW Hey guys, is there any update on this problem? I tried to find some information on how to regenerate 0x51 key but I didn't find anything. Thank you for your help. |
Experiencing the same issues as OP, here are my keys, board is PSP 2000 TA-085: |
I have the same issues |
Well i found this thread in 2020 Mine is PSP 3000 Btw i have the same issue, but it happen after i downgraded it from 6.61 Pro-C Infinity 2 to 6.60, then i downgraded it again to 6.20, intended to upgrade it to 6.39 and install Pro-C, but somehow i upgraded it back to 6.60, and i want to downgrade it again, and its not working. First im using 6.20 from 6.60, but it said corrupted file, i tried redownloading the file but no luck. when i search it online it said that for some PSP 3000 it can't work, so then i downloaded 6.39 I tried using 6.39 but it said an error code CAAFFFFFCF7, at this stage i almost gave up, i tried redownloading it and using version 6.30 even back to 6.61 Pro-C Infinity 2 to see if its just a corrupted data when downloading, but again no luck. i downgraded my PSP so i can use Iso Tool so i can install and game update, but this is unrelated to this. and here is my other problem, i cant use the IDStorage Manager for some reason, it says I dont know what i should do now, i cant go back to older version to try run IDStorage Manager, could it be because im using a MicroSD? If anyone knows and update, please let me know |
Oh well, its my fault why i cant run the IDStorage Manager ×_× I will update it tomorrow because i literally tried every single method, and now its already 9PM, I Will Update As Fast As I Can |
@CelesteBlue-dev Sorry im a little bit late |
I really don't want to bother but is there a fix planned for this issue? A short reply by the dev is greatly appreciated, if possible. Thanks much. |
It's still unclear what the root cause of this issue is. My hunch (and evidence above) suggests that corrupted idstorage may be related, but uncertain if this is too broad a scope to address in this tool. |
@CelesteBlue-dev did you diagnose this issue further? |
I had a similar issue to revert from 6.61 CFW to 6.61 OFW. I could revert without Chronoswitch by spoofing the current version as 6.60. I did the followings in CFW.
I'm actually not 100% sure if it did the trick inside, but at least the version now says it's OFW 6.61. |
Hello @megumilk First of all thank you for taking the time to respond with a possible solution, unfortunately, it did not help in my case. |
Well... This work for me, but after I enable Configuration > Use version.txt.... I needed to reset device and after that in PSP run the 6.61 updater. So if you have the same problem maybe this can help! |
Sorry if I'm resurrecting this again. I have the same error but I think its caused by something else. Everest reports TA-093v2, PSPident reports TA-093 with no version. PSPIdent 0.77.777 report Downgrading from anything to 6.20 results in 6.20 launcher to boot and show CAAFFFFFCF7. The only reference I found about a relation between TA-093v2 and 6.30 is this one. Probably is just that this table is a bit wrong and does not disambiguate between TA-093v1 (which I assume is a 4g PSP shipped with 5.70) and a TA-093v2 (my 4g which was shipped with 6.30, I think, and can't go any lower). |
I have all version fireware for psp3000/2000/1000 from 1.00 to 6.61, if you are look for 6.30, send me your email address. |
@BlueFang can you send me 6.30? |
I Resolved My Issue.. I had to use a Pandora Battery and revert back to OFW 5.0 |
Yes,and your email? |
revisiting this issue, and found the fix online. procedure is to replace it with Pro-C firmware, now i'm back to OFW 6.61, and can freely mod it again. good luck, |
As mentioned in the previous discussion the issue seems to be related to the 0x51 ID Storage key. The issue is actually in Chronoswitch's handling of minimum factory version. A lot of proceedures with Chronoswitch revolve around being as cautious as possible when faced with errors. This decision led to the implementation of a "minimum firmware" check, where Chronoswitch would refuse to allow an updater to run when the update version is lower than the "minimum firmware" version. Each PSP when manufactured is provided with a set of identification keys called ID Storage. These signed keys include various information regarding the region market, QA flags, and includes a factory shipped firmware. In an abundance of caution, the "minimum firmware" is derived from this value stored in the ID Storage 0x51 key. The last thing I want is somebody to accidentally run a firmware that their PSP claims it doesn't support, and end up with a brick. In this case, it seems as if @rippzee and @e1ysion have this issue on the 02g model because they are missing or have a corrupted 0x51 key. Others are experiencing this behaviour because their "minimum firmware" (i.e the firmware their PSP shipped with) is higher than the destination they are trying to downgrade to. This often manifests as 04g devices with min firmware 6.30 or 6.35 trying to downgrade to 6.20. The good news is, this is totally fixable. I've not decided yet on the approach that will replace this flawed "minimum version" design, but its likely going to be something that considers the generational model of the PSP instead. Alternatively, I may keep the existing system and introduce some consent based mechanism to inform the user that "hey, this might not work". I am almost certain it does work, but there is always a little bit of doubt regarding some weird firmware self-check that might decide "wait, this firmware I'm currently running is too old", and do something VERY dumb. Additionally, I'm going to improve the user experience so issues on Chronoswitch performing a last minute bail from the update is less silent. Lots of these checks could also be performed prior to running the updater so the user has some details beyond a cryptic error message from the updater. Expect a fix soon(tm). |
I found a fix, use this fork if you get this error: https://github.com/TheZett/Chronoswitch |
@megumilk U really saved my ass, thanks a lot. Someone who doesn't works, DON'T FORGET STEP 2, this method works like a charm. My case was: After downgrade, infinity 2 installation was successful. |
This also work. |
OMG DUDE! it worked i was forced to do this to install ark4 cfw and IT WORKED! tysm!! |
Hey Davee,
Apologies for disturbing you, but I've come across an issue with the Chrono downgrader, I'll C&P my original wording from Reddit:
"Hey all,
I am trying to downgrade my PSP 2000 from 6.61 OFW to 6.60 OFW (I also tried 6.20 OFW) as some of the plugins I want sadly do not work, I have a Pro C2 Semi firmware, which allows me to boot into CFW using darkspeed, but when using the latest version of Chronoswitch7 in order to downgrade, I keep getting the following error on the OFW update screen:
It then backs out to the XMB, thus not allowing me to downgrade at all. :(
I have all the correct files etc all placed in the correct directories and folders, I have been doing this PSP CFW stuff for a very long time (8 years now), but this is a first that I have encountered this error.
I am stumped as to what to do, as I have literally tried everything, I have sourced out version 4.1 and version 5 of the chronoswitch downgraders, but again they dont support my OFW, I used 6.1 of the chronoswitch again same error appears.
I have tried on google search but the search comes up very thin, as no one has encountered this, thus no faq or help topics/threads/posts are provided, other than the fact to use the previous downgraders, even though they dont support 6.61 OFW.
Any help would be greatly appreciated please. :)
Thanks
EDIT:
PSP 2000 V085 board, running 6.61 OFW - using Pro C2 to boot into CFW (I am not using a perma CFW, only the soft mod version), I want to downgrade so I can use the 6.60 plugins, most of the ones I love, just dont work, and cause me problems on my PSP, I have used Davees 6.61 to 6.60 plugin that allows me to run 6.60 on 6.61 plugins, but that does not work for me.
my PSP mobo data
EDIT 2:
I've opened a issue ticket on GitHub (Davee):
So if anyone else in this wonderful community has encountered this problem, either in the past or recently with no fix or no solutions, then please help out with the ticket or on this thread.
I don't want to disturb/nag Davee, but honestly I have no where to go from this problem, hopefully a solution or fix can be achieved."
Link to Reddit thread on PSP:
This error is really bugging me, just can not get the downgrader to work for me, I am unsure if its the downgrader or something to do with the PSP itself, but I have removed the CFW from my PSP, then installed it back again, I mentioned this in the comments and replies on the thread above.
Any help would be greatly appreciated.
Thanks
RippzEE
The text was updated successfully, but these errors were encountered: