Testing done to verify this functions as intended

Ta-086

Corrupted idstorage with idchanger utility from the assorted downgrades ,

then fixed both with the onboard fix and with a keybackup.

Hard boot

ta-086

Corrupted idstorage with idchanger utility from the assorted downgrades ,

then fixed both with the onboard fix and with a keybackup.

Hard boot

Ta-079

Tested battery level check

Verified it wont allow any thing to be done to a psp that doesnt need it.

In case folks are wondering, I did all my testing on a TA-082 that originally had 2.60 on it. I've run IdStorageChanger so many times the last day it's not silly. :) After fixing my own keys, I then reran both the original idstoragechanger from the 2.71 DG, and the 2.80 NOOBZ DG. I also tested with USBHOSTFS-FIX, and my own idreset.

About the only thing I haven't been able to check is region info... hopefully we'll get more info on that as more people all over use it, then we'll make changes if any are needed for different region PSPs. The best way to handle that at the moment is to use keys from the same region as your own when fixing with key files on the memstick.

What exactly are "Keys" and as long as I use the ability to fix keys without reffering to the memory stick, is there any chance of brick? Under what circumstances could I brick my psp?

The keys are various settings stored in the flash. They are mostly low-level stuff that concerns the operation of things like the USB and WLAN. Screwing up the keys can result in the USB not working quite right, the WLAN hanging, brightness issues, or low battery issues.

Generally, you don't want to mess with the keys. TA-082/86 PSPs need one key to be modified in order to run the 1.5 kernel. Old downgraders messed with more than that one key, so KeyCleaner was made to help clean things up if you ran one of the old downgraders on a TA-082/86.

The new corruption-free downgraders alter the one key, leaving the others alone. You don't need to worry about KeyCleaner if you don't have a TA-082/86, or if you used one of the corruption-free downgraders on a TA-082/86.

The one case we KNOW WILL BRICK the PSP is if you have a TA-082/86 running 1.5 (or one of the custom firmwares) and you put an original copy of key 5 back in key 5. The PSP will then hang when the 1.5 fw IPL runs. KeyCleaner will never write a plain key 5 to key 5... it ALWAYS modifies key 5 so that it is patched so that 1.5 will work.

However, there may be other things no one knows about that could cause a brick if you wrote garbage to another key (say you wrote random garbage to key 4 or 6). Hence the warning.

I got "bad key 0x0043" after... That right?

yeah just means you need a .43 backup. The auto fix does not fix one of two keys 6 or 43

ok... So my name is Phillip.. I have a brand new PSP I JUST bougth yesterday from my local game store...now, I downgraded using the "corrupt-free" downgrader and when it finished I was on 1.5.. (not problems right?) any way, I went on from there to CF 3.03 OE-C right, and when I booted my Metal Gear Solid Portable OPS. off my memory stick, it crashed to black...all the other four games I backed up (by the way these are all legit back-up CSO's from games I bought legally) they loaded fine... its to my understanding that I i followed the "new" downgrader to the T instruction - wise I would not encounter this. If I run this fix.. will it fix all my keys necessary to run my back-ups? Im not experiencing brightness issues per-say.. my friend has 3.03 OE-c on a non TA-82 and his Metal Gear runs just fine.... I have everything working except Metal Gear, GTA VCS and LCS.... initially all I wanted was for these 3 to work.. I have like alomost everything you can think of on my new PSP (the one I had befor this 1 had the same trouble except I used the "old 2.71 TA-82 downgrader and was booting back-ups to a black screen as well, which is why I used my warranty and told the game store guy it was intermittently crashing to black and used my warranty to get a new 1 only to find out im back @ square 1 again! PLEASE PLEASE PLEASe shed some light on as to where to go from here and/or what to do ... should I return this 1 too and use the "new" downgrader and then use the "key fix" or should I just run it now on 3.03 OE-C? Please guys I am begging you for your advice here... I am VERY devoted to all this and what you guys do is amazing!!! I am so happy for all of us right now as to all these recent breakthroughs have slapped a big ol' smile on all us gamers faces ...I mean that and I thank you for ALL of your hard work and efforts. Just want some knowledgable advice as to where to go from here... please..

Luis~

kanjineck@hotmail.com OR lserrano@cavtel.com OR myspace.com/djluiluv

P.S.

I know this post is rather long but pleae do understand that I ve been tryting to get these three games to load since they came out and I've gone through like 4 PSP already trying to get my stuff to work right and YES I have tried loading a UMD in the tray and put my settings like I should - NO UMD enable and disable and still NADA.. region america and UMD region free and tried booting in kernel 1.5 and 3.03 and NADA.. please hrlp me some 1!!

I ran the fixer and I swear to GOD that it told me and I qoute" you keys are TOO messed up for me to screw with..exiting for my saniy and yours"...

please dude help...

Thanks for getting technical with me. (no sarcasm intended) So basically If i run the safe key cleaner that doesnt read from the memory stick I shouldn't have a chance to brick right?

8-)

There's no such message in KeyCleaner. If you used one of the Corruption-Free downgraders, the keys are fine.

Not being able to play certain ISOs is common on various custom firmwares and has NOTHING to do with the keys.

Please consult a thread on ISO compatibility... maybe others have run mods on the file to get it to work... maybe they use it with a UMD disc in the PSP (no-UMD doesn't work for all ISOs).

Correct. However, if you just use reasonable precautions in getting keys, you shouldn't have to worry about bricking either. The one sure-fired way to brick is prevented by KeyCleaner.

Hi, Chilly Willy...

I have a TA-082 psp 1001 wich downgraded from 2.6 --> 2.71 --> 1.5--> 3.03OE C

I have the battery issue. When i reach 12% or less (The Green led start flashing) and i turn my psp off, the only way i can turn it on, is by reconecting the psp to an AC adaptor. This however not happen when i just hibernate my psp...

I have run the Keycleaner program... but with no results on this issue.

Previously to run this i have run the following :

USBHostFIx

idreset-v7

Id repair (from codes02)

In fact when i ran the Keycleaner program, it recognize that i have ran the codes02, and told me to fix key05.

Any ideas on this issue? I still have this problem...

Thank you!

This message is from idrepair from codes02... not from Chilly Willy's Keycleaner....

Check out the source code (a safe practice whenever possible) before running any program on your psp...

The battery issue is normally fixed by restoring key 4. KeyCleaner doesn't checksum the keys at this time, so it might say okay when the key is not really okay. It currently does a minimal check to identify the key. It's possible your key 4 is whacked. Dump your keys and check key 4 against what is in HarleyG's doc...

http://harleyg.net/docs/idstorage.txt

If your key 4 is the same as there, I wouldn't have any idea what the problem is. There are still many unknowns in this area, and better folks than I are still looking into it.

Even though I got a no questions asked replacement warrenty on my PSP I'm very cautious on brickin it. My question is how high of a chance do I have to bricking my PSP using this?

Practically zero. As I said before, the one way KNOWN to brick is completely prevented by KeyCleaner. You'd probably have to spend all day messing with garbage in various other keys to find another way to brick. It's almost impossible to inadvertantly brick with KeyCleaner.

I spent a couple hours using various combinations of the 2.71 idstoragechanger, the 2.80 idstoragechanger, USBHOSTFS-FIX, idcopy, and idreset with three sets of different keys, and my TA-082 is still running fine. I do what I can to test my stuff on my own PSP, and had two other people beta test KeyCleaner after I was satisfied with my testing, so I'm satisfied with it's reliability.

The only part I couldn't test was alternate region PSPs where key 0x45 is different. KeyCleaner currently shows non-US key 0x45's as "unknown". An update later will take care of that, but it shouldn't affect the rest of KC's ability to cleanup the keys.

Thanks, I just ran it and it works great.

Great Info... Thanks...

I have one question though...

My keys 4 and 6 are exactly like Haleyg's. Key 5 however differs. And that's the key that KEycleaner repaired...

Could this key be the problem?

My actual key have the following values :

986B6C430100000001000000CAD9E39B

0A000000000000000000000000000000

Harleyg have the following :

67 68 6C 43 01 00 00 00-01 00 00 00 CA D9 E3 9B

0A 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00

Why is that difference?

Should i try to change ky 5 to Harleyg values without any risk of bricking?

HarleyG's dump there is the method codes02 used to patch key 5... changing 67 6B 6C 43 into 67 68 6C 43. The method I use to patch key 5 is to simply invert the first byte, so I change 67 6B 6C 43 into 98 6B 6C 43.

Either method is fine for making key 5 run 1.5 properly. KeyCleaner just converts the codes02 change into my change to try to keep it the same as all the "corruption-free" downgrader packages XsavioR and I put together.

Thanks for the info!

Ok sorry forgot to say this before many thanks Chilly, was a big fan of your cartoons too 8). You got your own website I could look at?

Is there a list of what these code do and or what is 43?

Lately... spanishnugz cut down on the caffine man... You will live longer and Mr Winky will thank you when you are 40.

No web site yet... you can find a bunch of info over in the Hacking forum at lan.sh. That's where most of the info used in KeyCleaner came from.

I ran this originaly because of this 12% AC issue. That is fixed and working great now Thanks. I do however now have a new problem. My psp only seems to charge while in the XMB. If the power is at anything but full and I run say psp radio as soon as the app runs the led light turns from orange to green. Sigifying its no longer changing. It will run all night ill wake up light is still green bat is at 38%. I then exit psp radio and back to xmb and the light will go back to orange and the bat charge meter will begin to blink. It does this evey time now since i ran key cleaner. So basicly what im trying to say is the psp no longer charges if its in use. (Other then idle in XMB)

Any ideas? comments suggestions :) Thanks

UPDATE: This only occurs when the wifi kicks on during a app. If its a regular app or game with no wifi it will charge fine and normal.

As soon as the wifi loads up and led turns green it forces the battery chage light to also turn green and stop charging.. pspradio and pspweather is what I used to make it fail.

Will also fail when using the webbrowser in the XMB

psp can't be charged, while wifi is on. it is hardware restriction. afaik, some mb revision CAN be charged, while wifi is on.

Well I used to be able to charge while pspradio was running, be4 I fixed the keys that it.

Wouldn't it be hilarious if there were a setting in the keys that Sony set to tell the PSP not to charge while the wifi is on... so by "breaking" the keys, people could bypass that restriction, and by "fixing" the keys, you're stuck with Sony's restrictions again. :-D

I guess that's something to experiment with... maybe we can find where that option is set and make an app to control it's value.

Tested v1.1 on my 86 w key 8

~recorrupted idstorage with 2.71 dg utilities

~fixed using square w/o files option

~fixed resulting missing 43 bin from backup

~hard boot

Success

Chilly Also tested on 82

2.71 idstoragechanger

2.71 idsc + idreset

2.71 idsc + USBHOSTFS-FIX

2.80 idsc

2.80 idsc + idcopy

We have no way to test the regional improvements. But as a consolation running it shouldnt leave you with any issues that cant be fixed if any issue did present it self.

thank you chilly willy

my psp is 1007(taiwan)

in the v1.1 ,key45 is only include 1000\1001\100?\1004\1006,would 1007 in the next version?

i have a questions:

when i run v1.0,the first screen said :codes02 soft-down psp , alternative region, after fix ,it said:chilly willy alternative region.but when i run v1.1 today ,it said unrecongized key.

i think 1007 is not include is the "unrecongized key" reason .

so i wonder if 1007 would add in the next version, and if there is 1007 in the new version , would i fix my key45 to the original(1007) key.i think my key45 had been patched to other region.

thank you again

looking forward to your new release!

I can only support what is known... so dump the keys on your 1007 and post the first four bytes (in hex) of key 0x045. If your key 0x45 had been patched to another region, KC 1.1 would have recognized it. If it says it's unknown, it's obviously something different from what I already know. :-D

key 45 cleared, sorry

http://img.photo.163.com/uMLnawVl0AP2yuu0KF6z8w==/121315714962466998.jpg

Hmm... too bad. Oh, well, maybe we'll get lucky and someone else with a stock 1007 will report their 0x45 value. I'll keep an eye out for the info. An update would be easy to make once the info is known.

Hi Chilly Willy, I have a question. Well I downgraded my TA-082/86 (dunno which exactly..) from version 2.71 and I have the battery issue, when it reaches 12% and turn off the unit, it wont turn on until i connect the AC adapter.

Also I've noticed something that I think shouldn't happen, it concerns wireless play, when I play, say, Initial D: Street Stage with my PSP and my brother's (his psp is not a TA082), we both notice that the rival car kind of 'stutters', as if it was lagging or something... very annoying :( It also happens with pretty much every game, such as Ridge Racers 2, GTA: VCS and LCS, etc... mostly 'fast paced' multiplayer games.

Do you think that KeyCleaner can fix this problem?

Also, is it possible to make a backup of my current keys to restore them if things get worse when I use the program?

Thanks and have a nice day :)

Fixing the keys fixes the battery problem for many people. I doubt the wireless problem is related to the keys, but you never know...

KeyCleaner allows you to dump the keys. It's recommended you do so before and after fixing the keys for safety's sake. When you run KeyCleaner, you'll notice on the main screen that it says to press the SQUARE button to dump the keys. When you do so, it asks you to press X to confirm, then makes a directory called "keys" in the KeyCleaner folder with all the keys in it. If the "keys" folder already exists, it renames it and then makes a new keys folder.

OMG OMG OMG OGM OGM OG MOGM GOGMO GM OGM OGM OGMO

Your program fixed COMPLETELY the stuttering from Initial D: Street Stage, it now looks as smooth as the 1P game!!!111 I'm so glad I found this app, the greatest, every TA082/86 user should use it.

I have yet to test it with other games, I'm gonna try Burnout Dominator now, but it should work :D

Oh yeah, I have also yet to test the 12% battery issue, I'll probably post the results

JESUS CHRIST I'm so happy!!!

I bow to you, my kind sir.

http://img213.imageshack.us/img213/4332/orzpw5.gif

I have TA-82 that is downgraded from the original idstorage patch.

Then I used idStorageFix 1.1 from code02 to fix the key.

Now I run KeyChanger 1.1 and it tells me "Unrecognized key state"

4 - original key - okay

5 - patched key - okay

6 - original key - okay

8 - no key (code 0x80000025)

41 - original key - okay

42 - copy of original key 6

43 - original key - okay

45 - original key - okay

42 - copy of original key 45

47 - original key - okay

Is my PSP ok?

It looks like codes02 fixer missed a couple keys... 42 and 46 should be cleared. I'm attaching an arc with keys 42 and 46... there can't possibly be any copyright issues with THESE keys as there is NOTHING in them. Unzip the folder into the KeyCleaner folder, press X to fix keys, press X to fix keys using memstick, press X to select the clear_keys folder (press O to skip any other folders in KeyCleaner until you get to clear_keys), then press X again to confirm fixing the keys. When it's done, the keys should all be fine.

The next update to KC, I'll add recognition of codes02 fixer to it, and bundle the clear keys so that people can fix it immediately.

Wow, I've seen some weird things, but that has to be in the top five. Thanks for reporting that. I wonder if some of the reports of stuttering I've seen in other games are due to the same thing...

OK, testing done, now I can turn on my PSP when the battery is below 12% !!

Simply awesome. Thanks a BUNCH again, sir.

Btw, I have a question, is it possible that further custom updates 'damage' my keys? Or is it just the downgrader that messes with them?

Thanks for clear keys. All the keys are "okay" now, except key 8.

What does "no key (code 0x80000025)" actually means?

Edit: Never mind about key 8. Your post at http://forums.maxconsole.net/showthread.php?t=56265 answered my question.

It was the idstorage changer that was part of the 1.5 downgrader that messed with the keys. No custom firmware upgraders mess with the keys, so after they are fixed, upgrading won't break them again. But that's why XsavioR and I put together "corruption-free" downgraders for 2.71, 2.80, and 3.03.

hi...i have psp 1001 (japan) 2.71 downgraded to 1.5 then to 3.03-OEC. Used the DA downgrader and I am having the 12% batt issue....

would it be okay to run the KeyCleaner fix first or run the IDfix first and then KeyCleaner the last?

please shed some light on this..

tnx

Hello Chilly Willy, my Englishman excuses since I am of spain, I have a psp metallic blue TA-086 psp 1000 japan, I made 3.03 the downgrader to 1.50 1.50 3.0.3OEA-c, I have problems of sheen(brightness) on having executed the homebrew, my results are these:

0x0004=original key-okay 0x0005=copy of original key 0x0004 0x0006=copy of original key 0x0005 0x0008=original key-okay 0x0041=original key-okay 0x0042=cleared key-okay 0x0043=original key-okay 0x0045=unknown status 0x0046=cleared key-ok 0x0047=original key-ok, key state:noobz soft-downed+idcopy.

The program advises me to fix from the memory stick, but I do not have a dump of the TA-086 already corrected. Serious so nice of me sending it.

If I you sending(parcel) the dump of the keys your serious so nice of arranging and to return them to send?

Thank you very much

First of all congratulation for this great app..

But I have some questions about this app and the IDStorage:

Which is the difference between fixing keys using files in the memstick and fixing the corrupted or bad keys whitout using this files (the SQUARE option)???

If we use the second way for fix the keys, why it won't clear all the bad/corrupted keys??? And which keys it won't clear???

In the other hand, if we use the first way (using the files) what dumps we should use?? If we have a TA-082 we must use a un-corrupted dumps of another TA-082?? Or we can use a dump of whatever PSP mobo??? Or it is different for each key??

- Sorry if the answer for some questions is in some reaply of this thread, my english is bad, and perhaps I haven't could find it.

Regards and thanks

@mellon

this utility can't fix keys which are destroyed during downgrade. this is why you need to copy these keys from memstick. square can only repair keys which are present in the idstorage, but placed in the incorrect locations.

ps. thank you for your great work, chilly willy!

If you run codes02's ID fixer, it'll leave you with two keys that need clearing. There's a arc of the two clear keys on the previous page that can be used with KeyCleaner to fix up after running idfixer.

Ok, thanks

But how can I know, which bad keys can I fix without the dump and which I must do with the dump??

Which is the message that appears next to the key for each case??

Regards

Hello first to be grateful for your help to you, I have spent(passed) the program with the keys TA-086 and continue having the problem of the sheen(brightness), this(this one) it is the result:

key 4 = ok

key 5 = patched key

key 6 = ok

key 8 = ok

key 41 = ok

key 42 = cleared

key 43 = ok

key 45 = ok

key 46 = cleared

key 47 = ok

The key 5 patched has now this value:

98 6b 6C 43 01 00 00 00-01 00 00 00 CA D9 E3 9B

0A 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00

When the correct thing serious:

67 68 6C 43 01 00 00 00-01 00 00 00 CA D9 E3 9B

0A 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00

I did the copya of the fix from the memory stick and now the program says to me that it is not a necessary patche.

Since I can change the values again into the key 05.?

Regards

I've used the original noobz downgrader to downgrade a White fw2.81 PSP-1006 (Singapore). I did the usual thing, update to 3.03, use GTA to enable HEN, run Update Flasher and went down to 1.5. Went up to 3.10 OE-A then A2 and after that, I used your v1.0 to fix the keys without using memstick. And then I saw your v1.1, then I checked the keys again with v1.1 and this shows:

4 - original key - okay

5 - patched key - okay

6 - copy of original key 0x0005

8 - original key - okay

41 - original key - okay

42 - cleared key - okay

43 - original key - okay

45 - original key - okay

46 - cleared key - okay

47 - original key - okay

I couldn't remember what it said when I was using v1.0 and I didn't dump the keys, but I remembered one was unknown, and it patched/fixed some keys and finally resulted in this. How can I fully fix the keys and did v1.0 caused any problems (regional)?

The original value of key 5 there is 67 6b 6c 43. codes02 changed it to 67 68 6c 43, while my patch simply inverts the first byte, making it 98 6b 6c 43. Either one will work fine. KeyCleaner changes codes02 patched key 5's into my format to bring then in line with the corruption-free downgraders XsavioR and I put together. Having one verses the other will make no difference in the operation of the PSP.

Brightness issues on new PSPs that have a key 8 are due to the display libraries, not the keys. The "fix" shown on lan.sh for that is to replace the display libs in the 1.5 firmware with the display libs from the newer firmware. This is not a fix for beginners.

You can make a key 6 using a hex editor and the idstorage text file from harleyg.

http://harleyg.net/docs/idstorage.txt

The key 6 in the text file there is the same as every dump I've seen from TA-082/86 PSPs from several regions.

Since you used the 3.03 downgrader, all the keys but 4, 5, and 6 were left alone, so they should all still be fine. KeyCleaner only copies 5 to 4, and 6 to 5 when you choose to fix without files and the PSP had been downgraded using the NOOBZ method. That's why it now says everything is fine except 6. 6 wasn't saved by the NOOBZ idstorage changer and therefore needs to be restored from a file.

Hi,

first of all, thank you very much for your work. I've been reading a lot about Idstorage since I downgraded my PSP, and I've paid attention to your work. I think this is the definitive Idstorage Fixer.

I've run the patch (version 1.1), it says that my key state was original soft-downed, I fixed without using memory stick, and it fixed every key but 0x0043. Now my state is:

--------------------------------------------------------------------------

0x0004 - original key - okay

0x0005 - patched key - okay

0x0006 - original key - okay

0x0008 - no key

0x0041 - original key - okay

0x0042 - cleared key - okay

0x0043 - cleared key - okay

0x0045 - original key - okay

0x0046 - cleared key - okay

0x0047 - original key - okay

Key state: Chilly Willy soft-downed TA-082/86 - bad key 0x0043

--------------------------------------------------------------------------

Please, can you tell me what should I do to fix all the keys on my PSP? It's a 1004, TA-082 PSP that came originally with 2.71 firmware. I think I have to fix keys from memory stick using a 0x0043 original key.

Thank you very much for your time.

Thanks for solving that key 6 problem on my white PSP as it didn't belonged to me. It was a friend's and I was asked to downgrade it for him. For my other TA-082 PSP, I've got the same issue as gonzo's after using KC v1.1 on it. It's a PSP-1000 Jap set (but made in china). It was downgraded to 1.5 from 2.71 using the first-gen TA-082 downgrader for 2.71 and it's like mentioned by gonzo. Key 43 is a cleared, but bad key.

Does this Key Cleaner perform IdStorage repair? Much noted in (I think) this thread?

http://forums.exophase.com/showthread.php?t=865

Because I'm looking for the utility that will repair my keys that I had to corrupt in order to downgrade to 1.5 for OE firmware.

Without any files, KeyCleaner will fix all but one key, either 0x43 if you had run the original 2.71 downgrader idstoragechanger, or 6 if you had run the NOOBZ idstoragechanger from the 2.80 or the 3.03 downgraders. Since the legality of bundling keys is questionable, those keys don't come with KeyCleaner.

You can get keys from someone with a clean or fixed PSP, or by making the key with a hexeditor from the idstorage.txt file from harleyg. Note that key 0x43 is identified as 0x040 right after the USBstor header... a goof in the text. It starts at line 267.

http://harleyg.net/docs/idstorage.txt

Thank you very much, now everything is correct. :biggrin:

How come when i run the program, it says that the game cannot be started. i placed the keycleaner in the game folder. I am runing a silver TA-82 psp with 1.5 firmware.

Hmm... on pure 1.5, it might need to be kxploited. It's designed around being run from HEN, or from the custom firmware at the moment. You kxploit it by doing "make kxploit" instead of "make".

I've attached a kxploited version of 1.1. Give it a try and see if it works.

Thanks for the Kxploit Cilly, the program starts now but the program gives me an eror after the white PSP icon. The program says "Error 0x00020146 loading/starting idstorage.prx" I ran KeyCleaner just like other homebrews by puting the two files in the attachment above into the game folder. Please help me. Thanks in advance.

Try this one...

Thanks for the quick reply, but now i get the same error in 0x000148. Sorry for the trouble.

Hi, Chilly Willy, thanks for your great work first! :smile:

I have a 2.71 TA-082(PSP1006) softdowned to 1.5 using Dark_Alex first downgrader. I have encountered the same problem as BaDaPpLe that I used to be able to charge while I'm using Wi-Fi, but after the keys are fixed, my PSP won't charge while using Wi-Fi. Any idea on how to fix it? Thanks for your help first!

the key status right now:

4 - original key - okay

5 - patched key - okay

6 - original key - okay

8 - no key (code 0x80000025)

41 - original key - okay

42 - cleared key - okay

43 - original key - okay

45 - original key - okay

46 - cleared key - okay

47 - original key - okay

I guess it'll have to wait until I get a chance to go back to plain 1.5... I can't test it otherwise, and I can't find anything about this sorta issue at ps2dev. They have a few threads on it, but the last arc should have handled that.

Uh, that's the NORMAL action of a PSP. Sony didn't want both the wifi and the charger heating the PSP at the same time. Something in the broken keys allows you to bypass that restriction, so you want to break the keys again. :biggrin:

I don't know what part of the keys controls that. If you want to experiment, dump your keys now that they are fixed as a nice backup. Then run the old idstoragechanger to break the keys. Then run KeyCleaner again with a copy of the backup keys you made, but with ONE of the keys (out of the list displayed by KeyCleaner) missing. Vary which one is missing until you find the one that "fixes" the wifi/battery issue. If you narrow it down that much, I may be able to make an app that switches the key to enable/disable that behavior.

Hey look pease chilly willy help me my problem is the ad hoc its not working im alomost sure that is one of my key that are corrupted anyway i have psp originally 2.6 upgraded 3.03 downgraded to 1.5 and upgraded to 3.03 oec now i have the ta082 version know that i have used the idcopy v1 that fixed my battery issue but not my ad hoc

can u please help me and suggest me what to do

thx very much

PS. when i try to send picture to my friend it works perfectly when i try to connect it just does not work put even both psp in channel 1 and automatic still nothing he has original 3.11 version i have 3.03oec i dont think that is the prob but anyway

and great job chilly willy on your key fixer

Run keycleaner , fix with out files ,

When your done , it should tellyou key 6 is corrupt.

When you get to this point post again and let me know ... from here it is easy to get you sorted,

Using my PSP1001 with TA-082 board I went from 2.60 -> 2.71 -> 1.5 (using a Dark_AleX easy downgrader with IDStorageChange) -> 3.40 OE-A. I have not run any other programs or made any changes. I havent run KeyCleaner yet. I wanna make sure it will work and that i know what i am doing first.

Which of my keys are changed by the path I took ? Is it possible to know for sure before i run KeyCleaner and know if will it work for me ?

I read the readme.txt and i want to know if KeyCleaner restore the original keys or does it basically make it good as new ? are there any problems it won't fix ? Finally where or how would I get a "dump on the memstick of the keys from a stock PSP". I do not have access to another PSP but I want to fully 100% fix any probs. If it is a legal issue can someone please give me the info via PM or something. I'm much obliged. Cheers for this great program.

run keycleaner , if it will , fix with oput files , post whats left (one key wont fix this way , then i can help ya)

OK ! Thanks ! I will do that ASAP when i am not rushed and post my infos.

Quik question in the meantime .... if you restore the keys from mem-stick do you have the original keys or what ? and what is the difference if any ?

Repair with out files... will fix any key (that the infos are stored in other keys). And will indefinately leave you with one key remaining corrupted... 6 or .43

Fixing with files, if you have the right files is kinda the same

only you gotta eb carefull to get them from an identical psp.

Just try it out and let me know when yer done ... then i can figure out what key you still need and instruct you on making/aquireing it.

Hi.

I have a 2.71 TA-082/86. I have encountered the problem of brightness. I already tried to fix with files on mem stick, and still have the problem, and now it says:

the key status right now:

4 - cleared key - okay

5 - unkonwn status

6 - copy of original key 0x0005

8 - no key (code 0x80000025)

41 - copy of original key 0x0006

42 - copy of original key 0x0041

43 - cleared key - okay

45 - copy of original key 0x0047

46 - copy of original key 0x0045

47 - no key (code 0x80000025)

PSP is a TA-082/86

Unrecognized key state

I think i've messed up... :(

Please help me... What's wrong???

I have no clue what to do... And what's the "SRC" Folder for? Do we copy it to the memory Stick? To Where?

ei guys need some help hir ive just use the keyscleaner to be able to fix my usb host but i cnt understand the tutorial on how to use it i dnt have the stock psp keys.. so i use the fix w/o using folder and it fix the keys when i restart the keyscleaner to check if its already ok a message appears

keystate: chilly willie soft-downed TA-082/86 - bad key 0x0043<----that the prob it didnt fix all my keys what the meaning of that??? will it damage my psp??? and where can i get an original dump keys of psp??? and if ever i have how can i run it on my psp to be able to flash it tnx.

i would really appreciate if you could help me tnx

you just need a 43 bin ...

sorry for bad english. i have a question. on key cleaner when restore from memory stick with same psp kind. do you end up with original keys? psp like new? or what is youre status? thanks.

If you make a dump of the keys from a good psp that is (basically) the same as yours, they can be used to fix the keys on your psp. If their psp was downgraded the same way as yours, its keys won't be any better than the ones you already have. :biggrin:

DONOT ASK FOR KEYS! IT IS ILLEGAL

Moderated 04/26

whoaw sori really new to this forum thing.. sori will not happen again...

thats what private messages are for .... look into it .

I have TA-82 that is downgraded from the original idstorage patch.

Now I run KeyChanger 1.1 and it tells me "Unrecognized key state"

4 - original key - okay

5 - patched key - okay

6 - original key - okay

8 - no key (code 0x80000025)

41 - original key - okay

42 - cleared key - okay

43 - original key - okay

45 - cleared key - okay

46 - cleared key - okay

47 - original key - okay

Is my PSP ok?

You key 0x45 isn't set right. The region data we've seen for key 0x45s go like this:

PSP1000 = 03 00 01 00 (Japan)

PSP1001 = 00 00 01 00 (USA)

PSP1002 = 00 00 01 00 (Australia)

PSP1003 = 02 00 01 00 (HK, I think)

PSP1004 = 02 00 01 00 (UK)

PSP1006 = 02 00 01 00 (Europe)

As you can see, all key 0x45s known about have an 01 at the third byte, with the first byte controlling some aspect of the region. There no known (valid) key 0x45s that are cleared, and that is why v1.1 says your key state is unknown. I think in v1.2, I'll report the state as soft-downed with bad key 0x45 for a state like yours.

On the other hand, no problems are known to be associated with 0x45 not being "correct". If you wish to make your keys perfect, you could dump them, edit 0x0045.bin with a hex editor to match one of the above values, then write it back.

Now I run KeyChanger 1.1 and it tells me "Chilly Willy soft-downed TA082-86"

4 - original key - okay

5 - patched key - okay

6 - original key - okay

8 - no key (code 0x80000025)

41 - original key - okay

42 - cleared key - okay

43 - original key - okay

45 - original key - okay

46 - cleared key - okay

47 - original key - okay

Is my PSP ok?

Thanks

Yes, now it's fine. You're as close to original as you can get without a dump from your PSP before you started messing with it. :biggrin:

NEW DESCOVERY ALERT

Hey chilly, i just found something important out, as i said before, this app fixed my Wi-Fi problem among other stuff..

The thing is, i noticed that when I try to load images via USB, for example with PSP Host, I no longer have to use the drivers for my TA-082, I just treat my PSP as if it was a ta-079, with the original drivers that come with USB applications... great :D

thanks, yet again

You're welcome.

Yes, the USBHOSTFS issue was the very first thing the old 2.71 DG was known to break, and lead to the first fixer apps. There was USBHOSTFS-Fix, then RUK, then my own idreset which became KeyCleaner. If you didn't wish to run one of those, there were specially hacked versions of the USBHOSTFS drivers for the PC that allowed USBHOSTFS to work with the "broken" keys.

Hello,

I've psp 2.71 (it's a TA 082) Downgraded whith DA Downgrader 2.71 => 1.5, and now i'm in 3.40 OE-A and my psp can't be reconized by my PS3 in USB (it says "There's no PSP system connected")

Does key cleaner repair this trouble and fix it ?

If it's possible can you explain me how to make it ?

(Sorry for my poor english i'm french :biggrin: )

Thnx Very Much

KeyCleaner should be able to fix that for you (someone reported that it did for them, I don't have a PS3 to check personally). Read the rest of the thread to start with, then ask any other questions that weren't answered by reading the thread. Here's a small outline of what you should probably do:

1 - Run keyCleaner

2 - Choose Dump the keys (just in case). That gives you a copy of all the current keys in a folder called "keys" inside the KeyCleaner folder.

3 - Choose Fix without files. This should fix all the keys but 0x43.

4 - Acquire a good key 0x43 file from the net, a good PSP, a friend, etc.

5 - Make another folder in the KeyCleaner folder, let's call it "good keys".

6 - Copy that good key 0x43 file to that folder. Make sure the name is "0x0043.bin" or it won't be recognized.

7 - Run KeyCleaner and choose Fix with files. Hit O on the PSP until you see the name of the folder at the top (remember we named the folder "good keys" ). Press X to select the "good keys" folder. This will fix key 0x43.

8 - Choose Dump the keys again. This will then rename the original dump to "keys0000" and make a new dump of your now good keys into the "keys" folder.

For the original key 0x0043.bin, i'have to dump an psp TA 082 or i can dump any psp mother board? and any jap or US versions ? Because mine is a PSP TA 082 EURO with custom firmware 3.40 OE-A DA Installed.

Thnx

Ok I made a mistake.... I thought 3.40 somehow messed up the usbhosft fix and it didnt. So I ran this app:

I tried to fix them and it did (supposedly) and now when I get into my USB I get an system error but I can go thru my files on my mem card somehow. And if I exit USB MODE, I still see the "USB" thing banner on top of my screen. cant get rid of it until I reboot the psp. SO something is way to wrong. If I try to get into USB MODE a 2nd time I get this error:

The odd thing is that even after getting the error Im able to 'browse' my files on mem stick, the only problem is that I need to reboot to get rid of the "USB CONNECTION"" banner on top..

I ran the app: and the Status of my Keys are:

HOW do I restore my keys??? I have never done this before.. any ideas?? I need to replace this faulty ones with new ones... How do I dump ORIGINALS? and how do I flash them???

Would someone provide me with their backup?? I have a US TA-082 PSP.

is it possible to fix it going back to 1.5 or reflashin 3.40 ?????

I wish people would put up the status of the keys from before they tried anything... I can't tell what was done from that status. It APPEARS that you tried "fix with files" while only using two valid keys. As such only two keys were fixed. That leaves the keys in a state that is unknown because who can predict someone trying to only fix two keys? :confused1:

I've seen people who dumped their keys, then chose "fix with files" using that dump... which is nothing but the keys as they already are... so nothing is fixed. :huh:

Ah well, I'll PM you and we'll see what we can do to get you straightened out.

By the way, upgrading or downgrading won't change the keys. So reinstalling 1.5 or 3.40 OE won't fix any keys.

@rico666: 0x43 is universal that I've seen, so you can take it from any PSP... except for one that has it bad like yours. :wink:

Hello!

First of all congrats 4 the great work!

I've a problem with my PSP and the battery when I have low battery like 10% and when I've hibernate the PSP I can't recovery the hibernation...

Could it be the keys? I've downgraded from 2.17 before the idstorage corruption free

Or could it be another issue?

Thanks alot

I'll assume you meant 2.71. :wink: Yes, the low-battery issue is related to the keys and most people report it fixed after using KeyCleaner. I'd suggest using KeyCleaner. Be sure to make a dump of your keys as they are now as a backup! Do NOT try to use that dump to fix the keys! The dump is of your broken keys, so using it to fix the keys won't work. You'd be surprised at the number of people who try to fix their keys with a dump of those same broken keys. :biggrin: Not saying YOU will, just making a warning in general...

The normal procedure is to fix WITHOUT files. That usually fixes all but one key: 6 or 0x43. Then you get a good 6 or 0x43 from a good PSP, a friend, the net, aliens, whatever, then use that one key to fix the last key. In your case, if you used the original 2.71 DG (as you seem to imply), the key it'll leave broken after fix without files is key 0x43. Key 0x43 is used by the PS3 to connect to the PSP, and such things as Remote Play. Key 0x43 is one of the few "universal" keys... all 0x43 keys I've have seen are the same, from the TA-079 to the TA-086, so you can use a key 0x43 from any good PSP.

Chilly Willy i would like to thank you because it worked !

SO => THANK YOU VERY MUCH ! :smile:

You're welcome. :smile:

ok um lets just go right out and say it!

Im dumb!!!

Now that that is out of the way....I never used this before and ofcourse i rushed into it and after reading this thread relized i made a huuuge mistake! so hopefully you can help me.

I dumped my keys and for some reason chose to restore the same keys! i know now that that was stupid so i am in "Unrecognized key state" PSP is a TA-082/86... keys may need fixing

recommended action: restore keys from memstick

I no longer have the option to restore the keys w/o files. I am assuming im screwed, but the psp still works fine but ive been having ps3 recognizing problems so i thought i would give this a whirl. So i guess now that we established that im a complete moron, whats the best way about fixing it. I'm assuming a good dump from another psp but have been having trouble tryin to aquire that. So if there is someone who can help or possibly point me in the right direction or something that would be awesome.

Thanks for everything

ok well i tried using keys from a different psp and that was a no go but we werent sure if it was downgraded correctly since it was bought downgraded so it could of been the same corruption.

im really appreciative to the people that have helped me so far.

So for now my psp sits as follows:

0x0004... cleared key - okay

0x0005... unknown status

0x0006... copy of original key 0x0005

0x0008... no key (code 0x80000025)

0x0041... original key - okay

0x0042... cleared key - okay

0x0043... original key - okay

0x0045... oringal key - okay

0x0046... cleared key - okay

0x0047... original key -okay

PSP is a TA-082/86

Unrecognized key state

Everything works fine except connecting to the ps3 and psplink.

Thanks,

Vince

If you still have the original dump of the keys, you can write them back as they are with IdStorage Manager (in this forum). Then rerun KeyCleaner. :biggrin:

The next version of KeyCleaner will specifically disallow trying to fix the keys with the same keys. Seriously, I never thought ANYONE would be crazy enough to do that, but I've seen maybe a dozen people do it so far. :laugh:

i ran idstorage and "fixed" and "verified" the keys and everything looks good and passes but key cleaner is still saying unrecognized state and i need to fix with memstick keys.

I really wish i would of freaking read this forum before i jumped into it!

Please help me Chilly Willy i will owe you my soul....

here is my key state, and i'm not sure what to do next

0x0004... original key - okay

0x0005... patched key - okay

0x0006... copy of original key 0x0005

0x0008... no key (code 0x80000025)

0x0041... original key - okay

0x0042... cleared key - okay

0x0043... original key - okay

0x0045... original key - okay

0x0046... cleared key - okay

0x0047... original key - okay

key state: chilly willy soft-downed TA-082/86 - bad key 0x0006

do i need to fix the key 0x0006, and how do i do that?

I really appreciate you created this program. It's really wonderful. Thanks

aquire a key 6 from an identical psp, fix with backups. thats all.

What is the region of your psp (the psp-1000 code on the sticker)

and what kinda mb do you have?

If you're handy with a hex editor, it's easy enough to make a key 6 using this text file documenting the keys:

http://harleyg.net/docs/idtable.txt

Hey Chilly Willy my friend suggested me to use ur app to fix my battery problem. 12% battery flashing turn it off and it wont turn it on till a charger is used.

i ran the app

the status is shown:

04....cleared key -okay

05....copy of original key 0x0004

06....copy of original key 0x0005

08....no key(code 0x80000025)

41....copy of original key 0x0006

42....copy of original key 0x0041

43....cleared key -okay

45....copy of original key 0x0047

46....copy of original key 0x0045

47....cleared key -okay

psp is a Ta-082/86

key state: original soft-downed Ta-082/86

i dumped the keys onto my ms

what should i do next, my keys look kinda messed up

do i click x for fix keys and then square to fix it without files?

help plz

You need to fix WITHOUT files first. In your case, that will fix all but key 0x43. Once you have all but 0x43 fixed, THEN do fix with files with just key 0x43. You can get that from any good PSP (0x43 is one of the few universal keys - all models have the same 0x43), make one yourself via the id text file I linked above your post, or from begging people with PMs. :biggrin:

plz can i get a 0x43 key from u :) plz i am begging u

my msn is kevinqixp@hotmail.com

what is the different between Ta-086 and ta-086??

One has a capital "T" and the other doesn't.

would it matter if i dont fix 0x0043?(battery problem)

I need to fix 0x0043, now two of my friends both have a PSP one is a TA and the other is not there both running FW 3.40OE. so all i need to do is get one of them to backup there keys and send me that one right?? does it matter if its not a TA psp and mine is?

I don't think 0x43 has any affect on the battery. That's mostly 4 and 6. From what I've had reports on, 0x43 is related to things like remote play.

lol yeah that was probably a typo

my psp is 1000 jap set

the key status right now:

4 - cleared key - okay

5 - unkonwn status

6 - copy of original key 0x0005

8 - no key (code 0x80000025)

41 - copy of original key 0x0006

42 - copy of original key 0x0041

43 - cleared key - okay

45 - copy of original key 0x0047

46 - copy of original key 0x0045

47 - no key (code 0x80000025)

PSP is a TA-082/86

Unrecognized key state

i need help!!

That's a hard-downed PSP. The next version of KC will handle that. I'm working on that this weekend.

good day. i just ran thekey cleaner...

first dump my keys, then run fix w/o files...

here's what i got... ta-082 3.40 oe-a

4 - original key - okay

5 - patched key - okay

6 - copy of original key 0x0005

8 - original key - okay

41 - original key - okay

42 - cleared key - okay

43 - original key - okay

45 - original key - okay

46 - cleared key - okay

47 - original key - okay

key state : Chilly Willy soft-downed TA-082/86 - bad key 0x0006

i have a ta-082 with a 2.71 FW (the original yet)...

is it possible to copy the 0x0006 here and use this as a fix...

thank you so much...

good day all...

went ahead and took keys from the 2.71FW sony...

use the copy of 0x0006 to use as a fix to 3.40 oe-a...

outcome...

4 - original key - okay

5 - patched key - okay

6 - original key - okay

8 - original key - okay

41 - original key - okay

42 - cleared key - okay

43 - original key - okay

45 - original key - okay

46 - cleared key - okay

47 - original key - okay

key state : Chilly Willy soft-downed TA-082/86

now hopefully it is fixed...

thanks sir chilly willy...

thanks xsavior...

Thank you so much Chilly Willy! Your software rock the casbash.

Here is my story.

I was trying to connect the psp to the ps3 to register and it wouldn't work. Jump online and found Chilly Willy. I figure I could do this easily, so I went to work. 1st thing I did was dump the existing key in case I screw up. thank god I did that. of course I backed up the existing keys with the key on memstick first. GRR, then I ended up with the dreaded unrecognized state. had to get the idstoragemanager to rebuild my key and back to square one. Then I redid keycleaner with the auto fix. Fix them all with the exception of 43. I was hoping the ps3 would recognize the psp but hell no. I figure the reason why is the 43. So I decided to get ballsy and did the hexedit of 43 with the notes from HarleyG txt doc. It work beatifully. Now I am able to sync with the ps3 and I am having a blast.

thank you so much Chilly Willy!

Glad you liked it. Glad you backed the keys up first. Glad you could work out the procedure without six posts on the forum. :wink:

It's not that we don't want to help people, it's just nice when people can help themselves and we get a little break. 8)

does 6 post really called for?

:crying:

i thought i was just trying to air my situation without hurting my psp...

well i thought i did only 2 post on this thread... regarding the keycleaner...

still agreat app though...

:biggrin:

Don't worry about it. I have a tendancy to not check forums sometimes, and often by the time I do, someone will have made a dozen posts asking for help, then working out the problem themselves before I've ever seen the first post. :wink:

I hope the 3.50 downgrader doesn't corrupt any more keys then it needs to. Time to get myself a silver psp :D, but updating it to 3.50 might be a problem, does it matter which region I upgrade it to (japanese or us?)

All PSP update reagons are the same exact update as of this time so no.

I checked the source with the 3.50 downgrader and it's fine. It's basically like my own and codes02's patches... changes one single byte in key 5.

It changes one byte but how is this change implemented? Is it reversible like yours Chilly Willy. You never know what may happen in the future. If not, can I use your existing IDSTORAGE changer in conjunction with the 3.5 Downgrader or should I wait for a completely reversible corruption free downgrader? In my opinion your patch set the standard for how to correctly corrupt idstorage key 5 for ta-082/086 downgrading. I'll hold off downgrading until I find out if the Noobz method of key 5 corruption is completely and easily reversible like yours.

Thanks to you, Noobz, Dark_Alex, Mathieulh, Codes02, Vadd, Squirrel, Stapol and everybody else who is working on PSP projects.

It's different from both mine and codes02's fixes, but similar as I said. It won't be any trouble to make reversible. I'll add recognizing it to the next rev of KC (working on that now).

Can you use the Keycleaner to change the idstoragekeys of a TA-082 PSP, so that the PSP can update past 3.30 Official FW again...? (I have a Japanese TA-082, so it might be tough for me)

No. KC is for making the keys as close to normal as possible, but still usable under OE. You can use the hidden feature of 1.5 Enabler to unpatch key 5 while in 2.71. That allows you to then go to 3.30+ official.

Hidden feature...? So you don't have to use KC at all, just the 1.5 enabler in the 2.71 downgrader? Would it still work if you downgraded from 3.50 to 1.50, then upgraded back to 2.71, then back to 1.5?

Is it that option where you press square and undo the option of changing key 5...?

The hidden feature in 1.5 Enabler only undoes the patching if it's in MY format. So KC is needed to make sure the keys are good and key 5 is patched MY way. Only then will pressing SQUARE in 1.5 Enabler unpatch key 5.

You should be able to do this in anything that runs my software. Note that KC doesn't work in 1.5 (no idea why) nor in 3.03 HEN or 3.50 HEN (no idea why). They're probably related. KC works in 3.xx OE and in 2.71 HEN and 2.80 HEN. 1.5 Enabler is probably the same. I would probably run it all from 2.71 HEN or 2.80 HEN if I were doing all this. Then go from there to official Sony 3.30+.

Ok thanks for the reponse, you have some awesome software for the PSP....you've helped me and my cousin out a lot! (My cousin was the one that needed to restore his PSP on OFW, unfortunately)

Hello, I sorry but if that has been asked before.. I want to know how I can revert back to original firmware once it has been downgraded using the noobz 3.50 downgrader.

I have checked out the readme for KeyCleaner and I am still confused with all these idstorage keys. Can someone list out the steps I would need to return to original firmware from a patched PSP (TA-86)? For example Original 3.50 (Noobz downgrade) ->1.5-> 3.40 OE -> 1.5 -> Original 3.50

Thanks

What does the current KC 1.1 say is the state of the keys for a 3.50 DG PSP? Without knowing that, the procedure would be more convoluted.

You have to have a backup of your idstorage keys if you want to go back to official fw. If you don't, you need to get them from a TA-86 untainted PSP. Also you have to restore them while in a HEN under 2.71 or 2.80 because restoring them under 1.50 will brick.

Hi Chilly,

Please tell me how to get back to official Sony firmware. If I can upgrade my PSP to Sony official firmware 3.50 then I can downgrade it to 1.50 again and upgrade it to 3.11 custom firmware according to NOOBZ. I did this for my nephew's PSP (official Sony firmware 3.50) and it worked beautifully.

I started with 2.60 official sony firmware, downgraded to 1.50 and somehow it updated itself to 2.71 when my son played some homebrews. I run HEND before running homebrew games.

The following are my keys after running Key Cleaner 1.1:

0x0004 original key okay

0x0005 original key okay

0x0006 original key okay

0x0008 no key (code 0x80000025)

0x0041 original key okay

0x0042 cleared key okay

0x0043 original key okay

0x0045 original key okay

0x0046 cleared key okay

0x0047 original key okay

PSP is a TA-082/86

Key state: unpatched PSP

Thanks a million for your time,

So you're firmware is on the official 2.71? HERE is a guide to downgrade. Remember to use the 1.5enabler TA-082 patch before downgrading.

Then you can upgrade to 3.52M33, HERE

Then update to 3.52M33-2, HERE.

If you have anymore question, feel free to PM or IM me on msn messenger(account is in my profile), because this place isn't where to posts question.

Good Luck!:biggrin:

EDIT: to downgrade to 1.5 from a custom firmware, follow the guide HERE, and be sure to check out the tutorial clip.

From the looks of it you don't have to run KeyCleaner. Since you're on 2.71 just run the downgrader available here. It's the corruption-free version.

Hi guys, I already posted here regarding my USA ta-082 PSP in which I used KC and it worked flawlessly, great app this is.

Anyways, I now have a japanese Champagne Gold PSP, downgraded from 3.50 and currently running 3.40OE-A. I ran KC and it patched key 0x0005, so now it says:

---------------------------------------

0x0004 original key - okay

0x0005 patched key - okay

0x0006 original key - okay

0x0008 original key - okay

0x0041 original key - okay

0x0042 cleared key - okay

0x0043 original key - okay

0x0045 original key - okay

0x0046 cleared key - okay

0x0047 original key - okay

PSP is a TA-082/86

Key State: Chilly Willy soft-downed TA-082/86

---------------------------------------

Is my key state OK?

Now I have the 12% battery problem :( However, I didn't check if i had that problem before I ran KC so I dont know... That seems to be the only problem I'm experimenting, what else should I test?

Also, how do I restore the keys I previously had before running KC? Btw I did make a dump of them and still have it.

Thanks.

The keys are fine, and only key 6 affects that battery problem you mention. It's more likely a settings issue. You should reset the settings to default, then discharge/recharge the battery.

okay thanks for your response, I'll try that.

By the way, I can just delete flash1 right? I mean, to completely reset all the settings.

I believe that's correct. If I remember correctly, it's the config.se file in flash1 that you specifically need to delete. Don't TOUCH flash0! That's how you brick. :crying: :biggrin:

Resetting the settings did the trick, thanks a lot, now I can turn the psp on even with less than 12% charge!

In the original post:

"...when the 1.5 fw IPL runs. "

I think I start understanding most of the lingo ;-), but what is "IPL"?

Initial Program Loader. It's the hardcoded part of the startup that can't be changed and loads the rest of the kernel init code from flash.

Additional: "Hardcoded" really hard? So, a part that transfers control TO the Flash0? Or the first entrypoint IN the Flash0 that first gets control? (so a bit less hard, but maybe never to be changed)

Because you implicitly call it "IPL Version 1.5".

Sorry if not relevant for end-user, but I try to get a grip on the normal workings of the PSP. Hard to find descriptions :-(

I'm not 100% sure on how the PSP handles the IPL, if it's in the flash or in ROM in the CPU like many modern consoles. It's not something I've had to deal with, so I haven't bothered looking into it. You'd be best to check the forum at lan.sh if you really want info that deep about the PSP. That's where I get most of my info on the PSP from.

http://lan.sh/forumdisplay.php?f=43

Hi Chilly

I've been reading the whole posts here but Im still unsure (or hard to swallow). :P

I got this msg on my Silver PSP-1000:

04 cleared key - ok

05 copy of original key 0x0004

06 copy of original key 0x0005

08 no key (code 0x80000025)

41 original key - ok

42 copy of original key 0x0041

43 original key - ok

45 copy of original key 0x0047

46 copy of original key 0x0045

47 no key (code 0x80000025)

PSP is TA-082/86

Unrecognized key state

I tried to fix without keys but it wont allow me & saying sumthin that i need keys.

Now to restore the keys, I need to put a original keys from fresh PSP right? Should I copy ALL keys to MS or just the keys shown above 04, 05, 06, 08, 41, 42, 43, 45, 46, 47?

And are there any particular CRCs of the keys I need to watch for?

I ask help from 2 different guy for their dumps. Couple keys arent the same. I believe both dump came from TA-082. The 1st one I cannot be sure (forgot) & 2nd is definetly from a TA-082/2.71fw.

(1st dump) - (2nd dump)

04.bin DFB50041 - same

05.bin B1009223 - same

06.bin EC25D704 - 45A4AC1A

08.bin not found

41.bin 2D278CA3 - same

42.bin B2AA7578 - same

43.bin 55E26FF6 - same

45.bin 4490D7AD - 54E20C85

46.bin B2AA7578 - same (this is also the same with 42)

47.bin 214E7710 - same

Btw, the USB is working on my PSP but not the brightness, which is reversed. Dunno abt the battery problem yet, or any other thing for that matter. Havent use much this new Silver PSP, I also got a Black non TA-082.

I can't tell anything from the CRCs you posted. Give me a KC status table for that other PSP. Your Silver PSP is a hard-downed PSP. It's the same as the 2.71 soft-downed, but also kills key 0x47. You can fix all the keys except for 0x47 by doing fix with files and a set of GOOD keys from a TA-082. I can't tell if that second PSP has good keys as you didn't post the KC status.

The reverse brightness is due to a change in the PSP LCD module for newer TA-082's and nearly all TA-086's. That was compensated for by adding some new display libs and an extra key (key 8 ). The 3.52 M33 custom firmware is supposed to have a fix for that in it. Older custom firmwares require you to write some display libs into the flash and alter some files. It's a pain, so most folks shouldn't bother.

Sorry I cant give you the KC status of 1st & 2nd dumps. They arent mine, I got it from some1 else on the net. The 1st dump actually from TA-079. So then technically I cant use this for safety reason right?

When you said 47 is killed is it really bad thing? You are scaring me. +_+;

I think I might go crazy (suicidal) mode. I may just copy the 2nd dump keys (from other guy's TA-082/2.71) onto MS & try fix from there. If it goes brick, can it be restored by simply doing the "recovery"? My Silver is on 3.03 OE-C.

Btw, is new KC gonna come out soon?

Thanks for ur s/w & help. :)

EDIT:

Done some changing. This is after applying 05, 06, 42, 45, 46.

04 cleared key - ok

05 patched key - ok

06 original key - ok

08 no key (code 0x80000025)

41 original key - ok

42 cleared key - ok

43 original key - ok

45 original key - ok

46 cleared key - ok

47 no key (code 0x80000025)

Unrecognized key state

Actually, in "fix with files", KC steps through each folder telling you the status of the keys inside it. You could have used that on the keys you got to find their statuses.

No, TA-079 keys in general can't be used on a TA-082/86. One or two are the same, but most aren't.

You seem to have missed the "copy of original key 4" that was in key 5 to fix key 4. Other than that, you seem to have cleared up the keys pretty well. You really need to fix key 4 - some of the oddball problems people have are related to a bad key 4. If you still have a dump of that key 5 (0x0005.bin), rename it to 0x0004.bin and try fix with files again.

I haven't quite finished v1.2 of KC yet... real life intruding recently and all. I'm still working on it, so don't be surprised if it pops up one of these days. :smile:

Aha.

Thanks again for ur help. I fixed 04 keys & now it says Key State: Chilly Willy soft-downed TA-082/86.

I feel much more safer now. ^____^

What abt 42 & 46 showing "cleared", are they ok to leave it like that?

Also what abt 05 too, it say patched. And 47 just leave it?

Looking foward from ur new update. :)

0x42 and 0x46 are supposed to be cleared, and if 5 says "patched" it means it a regular key 5 with my or codes02's patch applied (I'll add NOOBZ 3.50 patch to the next rev). Leave 0x47 until the next revision of KC comes out. It should be able to fix it for you. You don't need to worry about it much - I don't know of any problems linked to key 0x47.

Again, im greatful for ur super help! U r legend!

Thanks matey. :)

Indeed he is.:smile:

Hi Chilly Willy, big thanks for your KC, and I have one question about restoring 0x0006 too on a 3.03 Noobz dg-ed PSP.

Some info there:

04 - original - ok

05 - patched - ok

06 - copy of original 05

08 - no key

41 - original - ok

42 - cleared - ok

43 - original - ok

45 - original - ok

46 - cleared - ok

47 - original - ok

Key state: Chilly Willy soft-downed TA-082/86 - bad key 0x0006

So as I've read the thread I've seen an other member with the same problem, so I know I must hex-edit a 06 key by HarleyG's IDS guide. I just wanna know, if editing key 06 and putting it in a new dir, and giving KeyCleaner the dir will work, or I have to put in a full dump?

Thanks in advance.

Just 0x0006.bin in the folder is fine. No need for ALL the keys when 6 is the only one you're changing. 8)

Okay, thanks. :)

De nada. I anticipated that when I made KC, so I made it accept any number of files - all of them, just one, two, etc. It's more flexible that way. Flexibility is a key to useful tools, and that's what KC is - a tool.

hey guys all my keys say either original key - okay or cleared key - okay except for idstorage key 0x0005 and 0x0006 which say unknown status. Is this ok if I for some reason want to go back up to 3.52 official or something?

No, key 5 should say patched, and key 6 should say original ok.

Ok, key 0x0008 says no key (code 0x80000025)

key 0x0042 says cleared key (okay)

key 0x0046 is cleared as well (okay)

Everything else is original.

It says PSP is a TA-079-081 and the key state is unpatched psp.

Do I need to correct anything?

Well, as long as it really IS a TA-079 or 81, it should be fine. Key 8 is only on VERY new TA-082s, and most TA-086s. The other keys are fine. key 5 only needs to be "patched" for TA-082/86 PSPs.

I popped open the UMD Drive and there isn't any writing on the motherboard so it should be a TA-079 or 81. Thanks for the reply CW!

Make certain you're looking in the right place!! It can be hard to see if you don't know what you're looking for. Make note of the picture here: http://forums.exophase.com/showthread.php?t=858

When you have the back of the PSP facing you and the PSP is upright and you open the door, it's to the very top right of the opening, and is printed upside down. It took a while for me to spot it myself on my TA-082.

Nope nothing there.

Please help:

I was helping my friend modding his PSP and he ended up bricking it by when using 3.52 M33-3 firmware. I'm going to go and help him unbrick his PSP using the pandora's battery. However, i read in the readme file that the idstoage can not be fully restored. So here is my question:

1. Does this program working on PSP that are NOT TA-82?

2. Can i use your keycleaner v1.1 and do a key dump from my 3.52 M33-4 firmware and use those keys to restore my friend's idstorage??

Please let me know ASAP and thank you in advance for your help.

Yes, it works on any PSP motherboard.

You can use KeyCleaner to restore certain idstorage keys AFTER you've recovered. There is no way to completely recover the idstorage unless you have an old NAND dump of your friend's PSP.

While he does not have his own keys, he will have my keys right??? so if my keys are working fine then his should too is this correct???

I'm kinda new at this but what's the difference between his old NAND keys and my 3.52 M33-4 keys??? What's in the original keys that are not present in my set of keys?

Also, if i get a brand new PSP, dump that key on my memory stick and then put those key on my friend's PSP, wouldnt that store the idstorage of his PSP fully???

You can dump the keys on your PSP, then use them on his PSP through KeyCleaner.

I know that but what i'm asking is "will he end up having the same key as me?" and "how is this different from his original IDSTORAGE?" Is there something special in his IDSTORAGE that my keys can't restore?

Ok, KeyCleaner can replace just a few keys in the idstorage. Yes after restoring these keys will be the same as yours. KeyCleaner will also check if the keys need to be repaired when it boots up.

Some areas of the idstorage cannot be recovered as they are unique to a certain PSP. But there is no reason these areas would be deleted. That's what the Pandora readme is referring to. Also, KeyCleaner does not deal with these areas. No program does, so they wouldn't be deleted unless intentionally messed with.

i see. So if i were to recover using pandora's battery, do u know if my friend canstill update his PSP using customized firmwares/sony official firmware??? because i thought i read from somewhere that some people can't update after recover with pandora's battery , which is why i'm here because i'm trying to find out if i need to give him my Keys in order for him to update. Please clarify this for me

Thank you again for all of your help.

im sorry i couldnt find a topic on Daedalus r12 so ill just post my comment here

i have Daedalus r12 and a psp version 1.50 daedalus loads perfectly on my psp but it can never find my roms can someone please help me please

He can update to any custom firmware / official firmware after recovering with Pandora's Battery.

Daedalus R12: http://forums.exophase.com/showthread.php?t=2469

Asking for ROMs is not allowed here though.

x3sphere i have roms and there in my psp but when i open daedulus r12 it says it cant find any

im not asking for roms im asking why the piece of crap daudles r12 cant find my roms

I'll give you some advice. Next time create a new topic when you need help and not post in a existing thread that is totally unrelated to your question.

The Roms go in /Daedalus/Roms

and they must be a valid extension otherwise the emulator won't detect the files, like .v64, .z64, or .rom. If its a zip file then make sure the Rom inside the zip file has one of those extensions. If not then just rename it.

v1.2 is up! I was delayed trying to get it to work in 1.50 ofw. No go at this point, so HEN and custom firmware only.

Nice release! Good job :smile:

wicked! Can't wait to try it :D

Wow thanks Chilly Willy, testing now. :)

Update:

At first the screen showing me this.

04 ok

05 ok Chilly Willy patched key 5 found

06 ok

41 ok

42 ok

43 ok

45 ok

46 ok

47 failed! readykey returned code 0x80000025

Your PSP appear to have a bad key 47

Then I went fix it.

And now is OK. Except of course "Chilly Willy patched key 5 found" still showing.

So is mine fixed completely? O_o

The previous 1.1 says some of my keys are patched, but in 1.2 says OK. I hope no more prob rite? :)

Thanks very much for ur cool fixer. It even now show my Silver region is PSP-1000. WTF! :D

U r legend. :)

Edit2:

I just remembered abt my backlight. it still didnt fix. i saw sum link sumwhere before, cant find it anymore.

Hi mates, I just have a simple question that do I need to install Keycleaner 1.2 for my TA-082 with 3.52 M33-4 CFW?. Thanks in advance.

Umm, how is KeyCleaner different from IDStorage Manager v1.2 ?

Thanks.

@Nocuddle - the brightness bug is not due to the keys, its due to a difference in the LCD modules of new PSPs compared to the old display libs in the 1.50 firmware used for custom hardware. The M33 custom firmware supposedly has a fix in it for that, and you can manually apply a fix to older custom firmware, but it's not for the faint of heart.

@nhlan7 - KeyCleaner is for people who used one of the older downgraders on their TA-082/86 PSP, or who bought a PSP hard-downgraded to 1.50 by the dealer (common for colored Japanese models). You can run KC on your PSP to check your keys, but if you used one of my corruption-free downgraders, or used the 3.50 lumines downgrader, your keys are fine.

@TuncaCeleste - KeyCleaner is designed to be simple to use on fixing COMMON problems associated with old downgraders. A simple solution for simple problems. IdStorage Manager is designed to be a flexible method of examining and altering IdStorage in general. It is a developer tool, and possibly a way to deal with more complex issues. Do you wish you could just push a couple buttons and get your 2.71 downgraded PSP to connect to your PS3? You want KeyCleaner. Do you wonder what's inside key 6 or 0x44, or what would happen if you delete key 0x43? IdStorage Manager is for you.

I've learned new thing today, you're greatful and thanks.

This thing abit misleading then & worked half way:

http://lan.st/showthread.php?t=1374

When my Silver at 3.03 OE-C, I tried this tool. It fixed my XMB 1-2-3-4 but in Homebrew still stuck 3-2-1-off. If I change the level within homebrew, when back to XMB it screwed. Then I used IdStorage & delete my key 8. And then I decided to upgrade straight to 3.52 M33 then M33-4, but the brightness didnt fixed. Im confused. So did key 8 related to brightness but u said nothing to do with keys. +___+;

I think the fix in M33 requires the key 8 be there. Key 8 and the new display libs is what makes the LCD brightness work. If you're missing one (the display libs in 1.5) or the other (deleted key 8 ), no fix is going to work. You should probably create key 8, then run verify/fix keys with a dump of the original key 8 to set it back to normal. Then try M33 again.

You are right. I didnt tried running brightness fix when in M33. Now it is working! Too bad this aint permanent.

Thanks again for ur great guide. Dunno what to do without you. :)

New version of KC up! New color scheme that can be changed, more goodies, a few cosmetic changes...

Enjoy! 8)

I was expeirencing problems with my time on my PSP when it was 12:00 it would show 12:00 but when I go into a game and press home it would say it's 0:00 clock. I downgrading using the newest corruption free downgrader for 3.50 by Noobz. I ran keycleaner and I cleaned key5, now the time is fixed. Does it matter that I ran keycleaner even though I ran a corruption free downgrader?

If key 5 was the only thing you changed, it had nothing to do with your problem. The 3.50 DG only changes one byte of key 5 - just the same as my own patch. It's a different byte, but it wouldn't have any affect on the time. Actually, I've never heard of anyone with your particular problem before. I would have guessed it a problem of corrupt settings.

Does it matter that I used keycleaner, did it do anything bad to my PSP, because I downgraded from 3.50 Noobz Lumines downgrader?

The only thing it did (and only if you told it to) was to convert their key 5 patch into my key 5 patch.

Hi Chilly Willy

Just wondering, if Dpad functionality has sumthing to do with keys?

What happen is my friend got Metallic Blue PSP-1006 3.40 OE-C & had a prob with displaying Chinese font/language/region onto the system. So I uses KC 1.3 to fix lotsa stuffed keys. The damnest thing is I didnt make a list of whats on KC screen & didnt dump the original keys either. KC fixed all nicely & key 5 is patched. At this point I havent even try any homebrew games.

Later I upgraded to 3.52 M33-4. All went smoothly, fixed the Chinese system. Fixed the brightness problem too.

I try SleepNWake homebrew, all ok. Next I try CPS2PSP, didnt load. Then I try PCEngine, the dpad seems stuck. Thought the problem on key config but none. Then went into bomberman game & i notice the cursor gone crazy scrolling up continuously. Next i try to play the game, the char only going diagonal left-up. If I pressed right it will move but it wont go down at all when i press it. In PSP game is ok, same with XMB & Recovery. Nothing moving. Other non game homebrews such as your KC, didnt make any move on Dpad.

So the question is, if I did stuffed the keys or if the keys related to controller? Tho I still dun get it why only these particular emulator. I try also MVSPSP, CPS1PSP. Same thing. I will try more with other homebrews to test further.

EDIT:

Just now tried Mancala, same problem. This gonna drive me nutz tonight. +_+;

And oh yeah, I did try to flash0 Restore Default. Useless...

I might try downgrading with Pandora but i better wait ur opinion 1st.

EDIT2:

Ok im royally screwed. Now GAME like CrisisCore FF7 also stuffed up. The UP-LEFT got stickied. I can move other directions if i hold it.

I'm pretty sure the idstorage has nothing to do with key presses, this sounds like a hardware issue.

does the ta-082 patch key 5?

cause after i patched my key five with KC 1.2, now if i use the normal downgrade under the recovery menu all i get is a brick. (i have pandora so no worries)

i tried my friends memory stick with the files (we tried it on his to make sure it works, and yes he successfully downgraded back to 1.5)

and when i used it it just gives me a beautiful blue brick.

also after using the pandora i can't upgrade the official firmware (i wanna check out 3.71 so..).

does KC work on 1.5? maybe i could figure this out if KC works under 1.5

Thanks in Advance.

While the IdStorage has nothing to do with the D-Pad, some plugins can goof them up. Things like pikey, for example. Make sure all plugins are disabled when testing to be certain it's not just a compatibility issue with various plugins.

If you are using 1.50 or anything built on 1.50 (ALL custom firmwares), key 5 must be patched or you will brick. The only time it won't is on official 2.0+ firmware, or if you have the custom IPL installed.

The (safe) way to go back to official firmware is this:

Go back to official 2.71.

Run 2.71 HEN.

Run KeyCleaner v1.3 and cleanup keys, unpatch key 5.

Run updater for official 3.xx fimrware.

ahh okay thanks. Running 2.71HEN.... it was a nightmare. :D

Hmm okay. Im pretty sure too ID keys didnt stuffed up. I thought im the one stuffed it up... and this is not my PSP. My bad I dint check at beginning. +_+;

The owner did lent the PSP to sum guy for few hours before it get to my hand. I ask him if he encounter problem & he confirm in Virtual Tennis game, the player moving by itself. So it is hardware issue indeed. I will return it to the owner tomorrow & let him disassemble it. :D

v1.4 is up. Now fixes 0x45, and creates any missing keys before fixing them. It also identifies and analyzes the PSP Slim. If you get any "bad" keys on the Slim, don't try to fix them. It's probably not bad, just something I haven't seen yet. Report it instead.

Wow u r fast! Thanks.

I just got my Slim but still virgin. Waiting for better M33 upgrade as I heard it only patch sum files in it? Whatever it is, better wait then sorry. :)

Hi, Chilly. Thanks for this great little nifty app.

Real question: How is KeyCleaner different from IdStorage Manager? I don't get it:confused1:

KeyCleaner is meant for cleaning up after the old downgraders. It's simple and straightforward, and although it can also handle other minor issues, not very flexible.

IdStorage Manager is a dev tool. It can handle more complex problems, but if you aren't careful, it can totally hose the PSP. Dev tools are like that - lots of power, lots of danger.

You just ran the original 2.71 downgrader on your TA-082? Use KeyCleaner. You want to experiment with the region settings on your PSP? Use IdStorage Manager.

what up fam, one question. every time i try and load somthing i recieve a message that say's "The game could not be started (80020148)". what does this bullshit mean?

a few questions first

What firmware do you have?

If you have custom firmware:

-Did you put it ms0:/PSP/GAME150? or put it in ms0:/PSP/GAME and set the kernel to 1.5?

thanks Arcertheif..........

my f/w is 3.52

3.52 official fw? If it is official fw, it won't work at all.

ok... thanks Shadowthor........Anyone wanna buy a psp, lol

I joined just to say thanks to Chilly. Your key cleaner enabled me to be able to use my PS3 for remote play. Big props dude. Big props. Thanks a lot!

I did this, and here's to hoping it fixes all my problems. I ran key cleaner version 4, and I got the following failed keys:

4 - clear and shouldn't be

5 - copy of 4

6 - copy of 5

41 - copy of 6

42 - copy of 41

43 - clear and shouldn't be

45 - copy of 47

46 - copy of 45

47 - readkey returned code 0x80000025

PSP has been hard-downed.

Does anyone think this has anything to do with my PSP not turning on for days? (Only the green light comes on as if it's bricked). I was told it could be a flash problem or a hardware issue.

At this point, I'm still running 3.52 (downloaded here last week). Should I downgrade then re-upgrade? Just stay where I am? Create a pandora's battery? Any other suggestions?

Thanks a million, Chilly Willy!!!

The latest version of KeyCleaner is specifically designed to handle hard-downed PSPs, among other things. Hard-downed PSPs are commonly Japanese colored PSPs bought online as 1.50 ready. The dealer did a hard-down on the PSP, and the key status above is the result.

I know that you guys get this question all the time so im sorry and understand if you dont reply cause its a long story so i made the main details bold thanks, tom.

Well a friend wants me to hack his PSP1001k TA-79 so i think yay i get to help someone play homebrew easily. So I was at my technal school were i am taking computer repair but the computers all use Windows 2000 Pro, so i dont think much of it and go on through the flashing process with pandora using the standard 1.5 > wanted CFW well when im done he tells me he wants a custom interface so thats ok till i realize what should have known being in computer repair(software side) that Windows 2000 being first for Plug and Play Flash devices really sucks since it doesnt sync some data till its removed which really didnt give me any trouble till i was puting the back ground theme BMP file on the flash1 when i removed the connection from usb in recovery menu it said all files not written to flash device which corrupted the flash1 to the point that when i mounted it again it said insert disk in drive :crying: so i take it home cause the flash1 was not even there anymore(or so it seemed to my knowledge) i decided to try to go back to 1.5 with pandora since it wouldnt boot anymore when i did so it wouldnt write the registry file to flash1 at which point i smacked my self in the face for not figureing that one out sooner so i read all the danger about flashing a different psp NAND image to a different psp and after thinking it over decided to flash my PSP1001k TA-79 M33 3.52-4(default settings) Flash NAND Image(not sure if that was a good idea at the time but really was the only thing to do) using "the Joker"'s pandora menu and after doing so checked the IDstorage keys and All Keys were Okay and it booted up with out a single hitch! thought i was out of the woods right well i did the final touches to his psp cleaning, ms, interface, ect... then when i was puting the UMD back into the psp it poped up and said

"The Disk Could Not Be Read"

so i thought it was a simple missread till everytime so far i havnt gotten it to read any UMDs i know its not the hardware problem since my friend was playing a UMD game before he gave it to me. I have read others with this problem but usually along with other idstorage key problems so i was just wondering if there is anyway i can fix it through the Hex idstorage key program of if it is fixable or key related at all thanks sooo much for your key checker Chilly Willy you rock!!

If you overwrote the original ID storage with that from another PSP without making a backup, you're TOTALLY screwed. There is currently no way to restore the keys that are specific to a particular PSP. Sorry.

Crap i cant rember if i wrote it with or with out idstorage over write is there a way to fix it if i didnt over write the idstorage

If you have a NAND image with the original IdStorage, write that image back to the PSP and then use Pandora to install a good cfw. If you dumped the original IdStorage with KC or IDSM, you can use IDSM to overwrite the current keys with the backup. If you didn't do one of those, you're hosed.

Yo chillywilly, what exactly does this program do? deletes corrupted flash files or what?

when i first got my psp, i upgraded to 3.50, then used the 3.50--1.50 downgrader with lumines, then 1.50, then 3.40OE-A..

then it got bricked, fixed with pandora, now I'm on 3.52m33-4, do i still need to use this program? all my games, apps and everything run good

oh yeah.. and my psp is a TA-082 motherboard.

ok well... since no one is responding, i went ahead and and used the key cleaner, and i clicked analyze my ta-082 mobo.

all the files it said okay, but i think on key5 or something it said, this key is corrupt or something, and it said press O to leave as is, and press X to fix the key,

so i just pressed O to leave as is, and exited. do i have to change this or just leave it like that?

i'd sat patch key5 with chilly willy's patch. it's corrupted mostly because it's "another" patch from keeping you getting bricked.

On 3.52 M33 and below, key 5 must stay patched. If you ever decide to upgrade to 3.71 M33 the install process will automatically un-patch that key.

KC is just for fixing minor problems associated with using the old downgraders. That's all. IDSM can be helpful with bigger problems, but requires you to know what you're doing.

Thank you very much!!

Hi. I know, this may be against the rules, but I need help.

I used old KeyCleaner with few keys from internet.

Now KeyCleaner 1.4 says I have correct keys and 3.71 m33 works just fine, but I have few power "problems".

1 when my battery less than 20% (not 12) my psp goes to sleep mode I can turn it on for a while, but game resets.

2 it killed 3 batteries already I dont know how, but after a charge it just dont work. Once I got "autopoweroff" battery this way and twice - just dead batterrys. PSP dont power on from them and when I plug charger - there are no info about battery in "battery info" just like there is no battery inside.

So please, somebody send me full idstorage dump of 3.71 psp 1004 with ta82 motherboard.

hgage2003(a)gmail(d)com

Thanks in advance

Sounds more like a hardware problem to me. There are no known keys that can cause PSP batteries to fail. If it is a software problem, I'd more suspect 3.71 than the keys. Try going back to 3.52 M33-4, reset your settings to default, then try the batteries again.

Thanks for reply.

First batteries died when a was on earlier firmwares - 3.52 m332 and 3.52 m33.4

And still - psp goes to sleep when my batt at 20% or lower, although KeyKleaner claims my keys are correct (I used few keys from other console. I dont remember which one)

Some people find that formatting flash1 can fix issues like that, but you really don't want to do that in 3.71. Sony has a bug in the firmware that generally bricks the PSP instead of formatting the flash properly. If that doesn't work, it's almost certainly a hardware problem. The only remotely similar battery issue (PSP won't turn on if battery is less than 12%) is fixed by fixing key 6. If it says key 6 is fine, it's not a key problem. And as I said before, I don't know ANY key that will make the battery not work at all.

Thanks for help. At least I could try if somebody helped me.

I dont know if my battery bricked or not. Maybe my psp wont turn on just because battery level is higher than something (all my batts "bricked" after I charged my psp for a long time - a night f.e.)

I formatted my flash1 many times - nothing changes (and still psp wont boot if batt less than 20%).

My main problem is I can't try anything - all my friends have psps of another region and with ta79 motherboard. I hope somebody will send me this dump one day so I can confirm is there connection with idstorage or not.

You do NOT want to be writing someone else's idstorage to your PSP - it will prevent you from using most of the PSP features if you do so. Most of the keys are specific to a particular PSP, and replacing them with keys from another PSP means they won't decode on your PSP, and hence, the functionality they control is lost. You won't be able to use the UMD, the Wifi, the USB, and homebrew won't run from the XMB (you'll get a wrong region error message).

KeyCleaner v1.4 uses the Adler-32 checksum method to check the keys. If it says they are good, they're GOOD. The odds of the checksum coming up good when the key is really bad are astronomical. It's why I switched to using it a couple revs ago. Old copies of KC only checked a few key bytes in the key, not the whole thing. The current rev checks the entire key via checksumming.

Hi Chilly Willy,

Excerlent program, i have used it on several psp's.

On my personal psp which was running 3.52 m33 key cleaner worked fine but i have since updated it to m33 version 4 now when i ran key cleaner 1.4 i get

"Checking key... 0x0041 failed Readkey returned code 0xFFFFFFFF."

it correctly identified the motherboard as a jap 1000 and as a TA 082/86

can you help me with this or can i safely ignore it?

Thnx in advance.

RESPECT

key41 is for USB Connections,

so if you're not using usbhostfs, or USB Connection a lot (if usb connection is fine then it doesn't matter), then it would be okay.

My PSP is a Ta-86 and which is a PSP1006 Hong Kong Model, I guess.

My PSP's MAC was "-" and I use Chilly Willy's ID cleaner and ID storage to edit the 0x44 key to restore back my MAC address, it also fixed some of my keys. Thanks for the great software and the great man! Now, I could connected to my AP to browse Internet...

However, I find another big problem. It could not connect to other PSP to play networked game. I tried to search lot of web pages, it tells the key 0x45 is related to WLAN's region... I changed the key from "03 00 01" to "02 00 01" which is from other PSP... after that, it could not start WLAN-test from menu... I tried to change "00 00 01" which could connect to my AP but not network game...

Don't know if there is any other key could fix my problem? Could anyone help me?

I'd say flash your key45 back to the original one first,

Then use the WiFi MAC Address Fixer to create key44 again.

Now see if it works.

Key45 is unique for every PSP mobo, and very possibly unique for every individual PSP, I would recommend not to flash someone else key45 to your PSP.

Thank you for your reply.

I don't have the backup of my original key45, that's why I want to know the parameter of other PSP. In fact, I checked two other PSP, both of them are Japan model which Key45 value is "02 00 01", the rest are zero... and mine is "03 00 01" which is from other PSP's default value.

Other information... I used to play Monster Hunter, when I go to the room.. the message is English it tells "waiting for connect" and now, it becomes Japanese... so I guess the region had been changed.

I just compared the keys of a TA-79 version with my Ta-86 version PSP, both of them are running 3.71-M33.

The key are different in 05,06,10,11,13,45, 100-106, 120-126.

I make the key 06,10,11,13,45 are same as the TA-79. The WLAN still not work.

05- IPL

06- RAM Timing

10- MagicGate

11- MagicGate

13- MagicGate

45- WLAN Region

100- DNAS, VSH region, Internet browser region, ad-hoc region

101- OpenPSID

102-106 UMD

120-126 Backup of 100-106 key

What things I can tried?

The thing is, key45 is unique, so using other PSP will only damage more. If you don't have a backup, then possibly you're WLAN is useless forever.

change the magicgate keys back to the original, is different for each motherboard.

key5 is okay changing to other but i don't recommend so.

Key 0x45 is not unique to every PSP, just unique to the model and region it was intended for. It only contains a couple bytes, so you can fix it by hand using IDSM and a table of values (you'll find one over at lan.st).

Key 0x44 holds the MAC address. There is an app out that can "fix" key 0x44.

This is bad..

I have a TA-082/86 PSP-1006,

Which i had a 3.71 M33-4 firmware on it.

Recently, I tried to update to 3.80 M33 but it gave me an error, I think I corrupted my files, and I when I used this program, It says:"The motherboard cannot be determined from the idStorage

There may be a problem with the idStorage on this PSP", I tried dumping files and stuff, but to no avail.

What's more, My MAC Address is missing, I can connect to the internet but cannot connect to other PSP's. Tried Mac Fixer, it said :"Error writing updated address".

I think it all happened went I went to Malaysia,Johor for my modification, how stupid of me..

If you have a backup of you nand, write that back (or at least the idstorage part), then use pandora on it.

If you don't have a backup of the nand, you're in for a lot more trouble. You should be able to get back to where everything but the UMD works, but without the original idstorage, your UMD is dead.

Hi Chilly

I,m pretty much in the same boat everything works apart from umd & adhock I was interested to read your comment about restoring everything apart from umd .It would be great if i could get the adhock working again,care to elaborate on how i could try and fix this

cheers arman:smile:

Hi Chilly,

What version do i have to be on for the key cleaner to run? I'm on 2.81 and it says game could not be started? I used v1.1, v1.2, v1.3, and v1.4 and nothing works. What am i doing wrong? I have been seeing v2.60, is this version correct?

I was thinking this. If i need to go down to another version, i was going to use the Liberty Stories downgrade ( i'm bidding on 2.0 right now on ebay), then going up to whatever the version i need to so i can fix my keys.

I never knew this, but when I went from 3.50 using the Lumines to Downgrade to 1.50, I didn’t know I couldn’t go back up to sony's offical firmware, and thats what i want to do. I did manage to upgrade to 2.81, but I want to go to Sony's Offical 3.80.

@arman - I've just seen reports in threads at MC and lan.st. You'd be best to do a little more research as I don't remember exactly off hand. It's BASICALLY just using someone else's keys with certain keys deleted to force the PSP to use a default setting. That doesn't work with the UMD as the keys 120-126 are used to decode the UMD data, and those keys are specific to the particular PSP.

@DJSkeeter - You either need custom firmware, or official fimrware + HEN (Homebrew ENabler). HEN is available for 2.71, 2.80, 3.03, and 3.50. If you don't have one of those exact versions, you are stuck unless you can get the pandora battery and stick to go back down to 1.50 again.

Hey Chilly

Thanks for the responce sorry to be a P.I.T.A but i had a good look through the posts at lan.st. & mc but could,t find anything specific on what you said any chance of giving me a little more to go on or you could pm me if you like thanks again :smile:

I don't really know more, just what someone reported in one of the threads (forget where exactly). He wrote a set of someone else's keys, then started deleting certain keys (I think one was 8, but I'm not sure which he wound up deleting in all). After deleting a key, he'd check how things were going. If you do this yourself and figure out how to get the same result this other person reported, please let us know exactly what you did so others in the same position can try it as well.

Not key 8 afraid,deleted it and the first screen brightness turned the screen completly off :ohmy:

Like I said, I don't remember offhand exactly which ones he deleted. I'm not sure he even said more than just one, and I forget which that was. Just keep at it. Someone has to try them all, and it might as well be you. :D

Is it possible to run Key Cleaner from an elf menu?

You betch. I personally use it myself XD

Great, any way you can provide info how to convert into an elf? I have tried to google, not much info found...

Thanks for any help.

Never mind, found a tutorial on Lan.st

Thanks

Ok, I am having a big problem. I have created a KeyCleaner elf, however when I run keycleaner from the elf menu I get an error 0x00 stating my motherboard cannot be determined. If I analyze keys, all have errors, and keycleaner states problem with IDStorage.

I have only been able to recover writing a full NAND.

After I restore the NAND, I run keycleaner from the XMB and there are no errors and my motherboard is recognized as the correct TA-085. If I go back into the elf menu and run keycleaner, it trashes my IDStorage again...

I have tried 3-4 times, but get the same problem.

I am using Keycleaner 1.4 with the elf creation method explained from Jas0nk on Lan.st using the PBPUnpacker and extracting the data file.

PSP Slim 2000 TA-085

When the KC elf trashes your IDStorage again, dont restore the NAND yet. Boot up your PSP normally and try KC from the XMB. If the mobo is not determined even when KC is booted from the XMB, THEN restore your NAND.

I've look through the KC source code (lots of times), it only touches your keys either when you want to patch/unpatch key5 (for phat PSPs) or when it fixes small problems.

Booting up and the analyzing the keys literally don't touch anything.

I pretty much think that it's an error/bug when you boot up KC from the elf menu.

First I would like to say thank you for your patience and support. After I launch keycleaner from an elf, I can not boot into XMB. I can get into recovery and back into the elf menu, but no XMB.

I get an instant brick, cannot even recover with DCv4. It appears Flash1 is getting nailed with something... DCv4 locks on format of flash1.

Again this happens only after I launch KC from an elf menu.

I am lost...

Ah I see now.

Recover you NAND first.

What firmware do you have after you restored the NAND?

and after restoring, try to format flash1 from the Recovery Menu (Advanced -> Format flash1 and reset settings.

You can't run KC or IDSM from pandora on the SLIM because the keys are encrypted. You should use KC or IDSM on the Slim from the XMB only. The latest nandtool will access keys from pandora on the Slim.

Can I use the Keycleaner 1.4 to dump the NAND from my PSPs which are Phat, 3.80m33-5 and Slim 3.90m33?

Will the application work fine in these 2 PSPs?

I had used the KC1.4 and analyze my Key on my PSP1002, TA-82, 3.80m33-5

It shown up that some of my keys have to be bad key:

0x0042

0x0043

0x0045

0x0046

0x0047

The first time i got my PSP was 3.03oe-a. Then I continue upgrade 3.40oe > 3.52m33 >3.80m33 (whereby it said that some of my keys need to be fix, so I press X and fixed it) without bricking my PSP once.

Now the question is that Do I have to fix the keys or dump my keys first and fix it? Besides, I also have the original key 5 and my PSP2000, TA85, 3.90m33 all keys are okay.

Does it mean that my key42 and 43 cannot(if possible) be fixed by KC? I have to find those 2 keys from net? (or can you send me urs XD). But i dont remember i have used downgrader to downgrade my PSP, only upgrade.

Besides, how do I back up my keys and what is the exact size after back up? I've heard that backing up the NAND is also important for PSP, too.

(Why is my reply above Acerthief O.o?)

key42 and 43 and for USB. very possibly your PSP used an old downgrader. You'll need to find a clean pair to fix it

key45: WLAN Region. Fix it with KC

key46: Not Sure, I do remember KC fixes it.

key47: Default parental lock level. You Don't have to care too much on it.

It would be best to start looking for a clean set of keys around the net. and back up your keys first (even if some aren't correct) so if something messes up you can revert back.

So you should have 4 sets of keys best: Original keys from your psp (TA-082/TA-085) and

Clean set of keys found on the net (TA-082/TA-085)

KeyCleaner used to look for every combination of every type of downgrader and "cleanup" program out. The current one doesn't as it's pretty rare to see someone who has used both an old downgrader and an old cleaner. Sorry 'bout that. :)

You might try looking at how KC says the keys are bad - for example, if it says one key is a copy of a different key that's also bad, using IdStorage Manager to write the key over the other will restore that key. Every key you can handle that way is one less key you have to find/edit by hand with a hexeditor.

This is what I have when I use KeyCleaner 1.4 to analyze my keys on PSP Phat 3.80m33-5:

0x0004...okay!

0x0005...okay! Original unpatched key 5 found.

0x0006...okay!

0x0041...failed! This key is a copy of key 0x0006.

0x0042...failed! This key is a copy of key 0x0041.

0x0043...failed! This key is clear and shouldn't be.

0x0045...failed! This key is a copy of key 0x0047.

0x0046...failed! This key is a copy of key 0x0045.

0x0047...failed! This key is clear and shouldn't be.

There's a pic which i uploaded too.

But when I update from 3.40oe-a > 3.52m33-4 > 3.80m33-5, I didn't face any problem or brick during the whole progress. Only when update to 3.80m33, it said that my key 5 need to be fixed.

You needed to have fixed the keys before you did the update from 3.40 or 3.52. In the meantime, looking at the keys shows:

Run IDSM.

Dump the keys.

Rename 0x0042.bin to 0x0041.bin.

Rename 0x0045.bin to 0x0047.bin.

Rename 0x0046.bin to 0x0045.bin.

Run IDSM.

Verify/fix keys. That should allow you to fix those three keys.

Run KC.

Analyze keys. The rest that are bad KC should be able to handle.

But I already updated from 3.40 to 3.52 last time without the knowledge of the keys. Now I just heard from someone that some of the keys is unique for one PSP. Then I run the KC on my PSP3.80m33-5 and found those keys' problems. So now I just need to follow the steps to fix those keys?

Yes.

hi peeps, ive got psp 1006 with TA-082/86 and im having major probs updating cfw, ive bricked few times and no matter what i do i get the message saying idstorage is corrupt press x to fix or r to exit.. a mate told me about chilly willy keycleaner so i got it n ran it.. fixed key 5 and also all other keys it said needed fixing i fixed, but still cant update cfw.. im on 3.52 m33-4 and cant seem to get any higher.. ive read up a fair bit but how do i backup nand.. what is nand? knowing me i need new set off clean keys but how do i put them onto my psp.. its all confusing but i know il get there in the end.. cheers... apdd

xcuse me for being a numpty... ive sorted nand buisness... but could i get the idstorage off of my nieces psp, its an older one TA-079 and will they work on my TA-082.. also i purchased my pandora battery and magikstik off of person who sold his psp.. im not sure of the downgrader because i didnt do it.. is there anyway i can tell and would it be better for me to restore my psp too normal and wipe the magikstik and make another one with latest downgrader.. as i said my psp is 1006 and motheroard is ic1003/TA-082/86..

thanx in advance.. apdd

Do NOT use the idstorage from another PSP! Except for a few keys, the majority are specific to the particular PSP. Not to mention, even the "universal" keys are not all the same between the 79/81 and the 82/86.

What does KeyCleaner report of the keys? Then run IdStorage Manager and check if you have keys 7 and 8. Some folks are missing them for some reason, and an 86 cannot be updated to new firmware without them.

keycleaner says key 0x0005 okay! chilly willy patched key 5 found. key 0x0041 failed.. this is a copy of key 0x0006.

idstoragemgr says key 7 attempt to read key returned code 80000025 key apears to be non-existent, key 8 says the same, key 9 says the same also key 000a,b,c,d,e.. so i dont have keys 7 and 8.. how do i solve this problem...

thanx again.. apdd

9 and the others shouldn't exist, but 7 and 8 should. The way to handle 7/8/0x41 is to use IdStorage Manager.

Run IDSM.

Go to key 7, view/edit the key, create the key. It will be clear (all 0's).

Do same for key 8.

Dump the keys.

Exit IDSM and mount PSP on PC via USB.

Copy good key 7/8/0x41 files into the keys directory inside the IDSM directory.

Run IDSM again.

Verify/fix the keys. It should see that 7, 8, and 0x41 are different from the files you copied and ask if you wish to overwrite the key with the contents of the file. Press X to do so.

Run KC and verify the keys are good.

Hi Chilly,

I have a TA082/86 (PSP-1000). Did a run on KC V1.4 and fix most of the keys except the below result.

Result show:

- key 5 as okay! but Orginal unpatched key 5 found. and

- key 41 as failed! This key is a copy of key 6.

Can you enlighten me what or how to proceed so that i dont mess anything up.

Thank you for your reply and advice.

Cheers chilly mate, i got it sorted last night but all i did was dumped keys 1st then created 7 and 8 and they both said clear, i then verifyed keys and they were there so i tried the cfw update and it worked, i didnt touch any of the other keys and my psp works sound.. no issues as yet.. i take it it was ok too do it this way... and in future i will make sure i read stuff thoroughly as the answer was in the idstoragemgr readme.txt lol..

Manys thanks and keep up good work :smile:

Maybe chilly is busy and could someone here that have some knowledge in making a good 0x41 key or could link me to a guide to make that key.

Thanks! Appreciated it very much.

Ok so I get this error "The Game could not be started 80020001" everytime I try to use KeyCleaner V 1.4 (or any version I use) could anyone help me with this? I would like to be able to use the ligit firmware and not the custom stuff if possible... Oh and my firmware version is 1.50. Any help would be greatly appreciated!

This is for the 3.x kernel, update your PSP to 3.80 M33 or 3.90 M33.

If you have official firmware, you can also run it on Homebrew ENabler if you have a firmware of the proper version. HEN exists for 2.71, 2.80, 3.03, and 3.50.

Any you would recommend? I've tried to use a few and they don't seem to work... I usually get the game could not be started error..

2.71 always worked well for me, but some people report 2.80 as being better. Both of those used picture exploits: you viewed a special corrupted picture to trigger the exploit to allow HEN to work. 3.03 requires you to have an old copy of GTA:LCS that would trigger the exploit when you loaded a special save game. 3.50 is similar, but works with Lumines.

2.71 and 2.80 HEN also seem to work more reliably if you have a wallpaper set before viewing the picture.

It seems like everytime I try to install custom firmware I get an error "The game cannot be started."

You cannot just run the custom firmware installer on official firmware. You need either Homebrew ENabler, or the Pandora battery and magic stick. Look over the threads on installing custom firmware for details.

Hi Every1. I'm new to this forum and I think I may need lots of help. My knowledge on the PSP is very little. In other words, I may need a step by step, very detailed descriptions on your instructions. I have a FAT PSP with TA-082 motherboard (IC1003). My PSP was moded by my brother-in-law from 2.71 (type K) to CFW 3.40OE-A. I have no idea how he did it (something to do with DevHook). Last week at afterdawn's forum, I was able to dowload and upgrade to 3.52m33-4 CFW. No one responded to my cries for help at the beginning (which made me very disappointed). So I continued with the 3.52 upgrade on my own. Everything seems to work fine. I never noticed any backlight or battery at 12% issues (or any other issues) before and after the upgrade. Now I want to upgrade to the latest CFW 3.90m33-2. But after further reading, I found out about the keys that may need to be corrected before continuing with the upgrade to 3.90. (I had no clue about this prior to the 3.52 upgrade.) I downloaded and ran the KeyCleaner v1.4. It identified the motherboard as TA-082/86 as orignially suspected. This is what I get when I analyzed the keys...

--------------------------------------------------------------------

Checking Key 0x0004...failed This key is clear and chouldn't be.

Checking Key 0x0005...failed This key is a copy of 0x0004.

Checking Key 0x0006...failed This key is a copy of 0x0005.

Checking Key 0x0041...failed This key is a copy of 0x0006.

Checking Key 0x0042...failed This key is a copy of 0x0041.

Checking Key 0x0043...failed This key is clear and chouldn't be.

Checking Key 0x0045...failed This key is a copy of 0x0047.

Checking Key 0x0046...failed This key is a copy of 0x0045.

Checking Key 0x0047...failed This key is clear and chouldn't be.

The PSP appears to be original soft-downed. Press any key to fix.

--------------------------------------------------------------------

What should be my next steps? Please help.

What firmwares can i use KC from?

Do I just need HEN

Ok... well I'm not an expert with PSPs either but I would say to "Press any key to fix." It should be able to fix as most as possible. Also, I suggest downloading Chilly Willys Id Storage Manager, which has a fix key function too. Read the ReadMe's, they are there for a reason =).

@tl_tiger...

Ive left u pm on a/dawn and also replied to ur question... pm me if u need help

Thank You for the KC:biggrin:

Hi All,

I have a TA-082/86

I have used Keycleaner 1.4 and cleaned up the keys that need to be cleaned.

However, when I reanalyze I get a msg regarding Key 5 saying "Chilly Willy patched key 5 found"

Then finally it says:

"Do you wish to unpatch key 0x0005? Please note that an unpatched key 0x0005 will brick a TA-082/86 with 1.50 or custom firmware unless you have installed a custom IPL to prevent this."

Should I unpatch this key. My current firmware is 3.52 M33-4. I am trying to upgrade to higher versions but I'm getting a msg when i try to do so that my idstorage keys have not the correct values, probably due to a downgrader.

Any help will be much appreciated.

Thanks!!

Don't unpatch key 5 while on 3.52 M33-4. All of the newer M33 installers will safely unpatch that key when upgrading.

Now that you've cleaned the other keys does the M33 installer work?

No, the update still doesn't work

I still getting an error that my "idstorage keys have not the correct values, probably due to a downgrader."

I don't know what to do ><...

As x3sphere says leave key 5 as is.. i have upgraded my ta 082/86 and u prob havnt got keys 7 and 8.. run idstoragemgr and create keys 7 and 8... it will prob say keys non-existent and u want it too say key clear with loads of 0000's above in rows.... then try the upgrade process... if any probs pm me ... i just also sorted a chap out on a/dawn.com so go have a look.. he had same prob...

@RC_dude.. u need to open idstoragemgr on psp and press triangle to view/edit keys.. scroll through and does it say under key=0007 and key=0008 key appears to be non-existent? if it does then you need to press x to edit then triangle to create key.. once you have created these keys it will say key appears to be clear with all the 000's above.. once you have done this you will be fine to run the updates.... let me know how it goes.. also it will want too correct keys like it usually says.. press x to correct them cos u will now have key 7 and 8

Thanks, I'll try this tonight when I get home from work.

EDIT:

So I tried everything, I used the IDSM and created keys 7 and 8, verified all Ok... Ran KC, other than key 5 everything looks ok. Tried to update, still can't update, still getting the same idstorage error. I don't know what to do anymore.

Any more suggestions?

If you get the same idstorage error and u know you have created keys 7 and 8 then when u run the update and u get to the message just let it fix the keys.... press x....

Some people are missing keys 7 and 8 for some odd reason. KC doesn't check them either since they aren't normally messed with by the old downgraders. Those keys not only need to be created, but also have to have the correct data in them. Fortunately, those two are not "unique" so you can use keys 7 and 8 from a good PSP to put on a PSP missing them.

Thanks for the replies apdd and Chilly Willy.

So in the end should I try to let my psp fix the keys when it does the update??

Or should I try to get keys from a good PSP and copy them onto mine before I do anything??

Yeah, I'm a bit of a newb, so I really appreciate all your help.

Thanks in advance.

Let youre psp fix ur keys when u update..

@chilly willy

when u create the keys 7 and 8 and they are clear in idstoragemgr u can run the cfw update.. it will say idstorage does not apear to have correct values like normal but when u press x to fix them the update runs no probs... (ive noticed it also in the TA-082/86 that they are missing) and once u have run the update if you run idstoragemgr again the keys that was created have the data in them.. no need to get the keys from another psp... i have just sorted tl_tiger the same way and he is too running cfw 3.90 m33-2 with no issues... Do you think it would be a good idea for me to do a guide regarding this issue as its obvious more people are having this probs with this mobo and the keys 7 and 8... my way is tryed n testedand i could rack a guide up instead off all this posting... cheers... Andy

Did that, everything worked out fine after that. I now am updated to 3.90 M33-2

Thanks all for the advice.

Cheers!

@RC-dude

Nice one.. glad too help mate.. will deff do a guide now regarding these keys on this mobo lol

Ok, heres how I mess up somehow.

I have 2 fat psp's (TA-82/86). 1 for my son & 1 for my daughter.

They both have M33 3.90-3 and ran fine.

My son's psp wouldnt remote with the PS3, something was wrong with the Keys. My daughters psp connects to PS3 fine so I dumped her keys which read:

Checking Key 4 ok

Checking Key 5 Original unpatch key 5 found

Checking Key 6 ok

Checking Key 41 ok

Checking Key 42 ok

Checking Key 43 ok

Checking Key 45 ok

Checking Key 46 ok

Checking Key 47 ok

so... I transfered all the keys dumped into the memstick and ran the fix on my sons psp and all works but umd will not load anymore. The exact error is "The disk could not be read".

What are my options? The last resort would be for me to take it to bestbuy and swap it for another $30. Can chilly willy help?

Ah... Dear father,

do you have your a back up of your sons keys? Because if you overwrited every single key on your sons keys, you've also overwrited unique keys that are different for each PSP.

(Keys 0x100~0x106, 0x120~0x126 to be certain, they are different on each PSP, and they contain the decryption code for the UMD, Also key44 as well, your son's PSP will lose the feature to use wifi or ad-hoc.)

So, if you don't have a back up, then I'm sorry, there is no way to recover this.

(Send it back to Sony? Maybe they'll fix it, but you'll lose your warrently as well, and some didn't even get their PSP back...)

Yes, I replaced every key but everything works but the umd. Well if its not fixable I'll have to swap it for another at Bestbuy.

The UMD uses those unique keys. They cannot be fixed. If you don't have a backup of the NAND or keys, then it's totally borked. Folks are looking into this, but there's currently nothing to be done if you don't have a backup.

hi chilly willy,

i just got a psp fat from my cousin with CFW version 2.71 se-b.

i just want to know if i can use pandora on my psp fat with CFW version 2.71 se-b, to update it to 3.90 m33-3? is it dangerus to do this? is this will effect the keys of my psp?

and if its ok to do this method.. should i use your wonderful apps(keycleaner) to clean my keys? or the pandora already do that?

If he's using 2.71 se-b, none of the keys should be altered. It should be fine to go straight to 3.90M33 with Pandora. If that Phat is TOO old, it may be missing keys 7 and 8. If that is the case, you'll need to go to 3.52M33, run IdStorage Manager to make a good key 7 and 8, then go to 3.90 or later M33.

thanks men! your the man...

ohh! you said about "If that Phat is TOO old, it may be missing keys 7 and 8", what do you mean with this?

thank again men. i will update you if i encounter any problem...

ohhh! again!by the way... sir chilly willy

i got another question.... you said that none of the keys should be altered. right?

my question is, can i update my psp phat directly from 2.71 se-b to 3.90 m33-3, using the updater of DAX? instead of using pandora with DC5?

In order in update your PSP to 3.90m33-3, you will need the minimum requirement of 3.52m33-3. So if you want to update straightly from 2.71 se-b to 3.90m33-3, pandora is the only way. Else, you will have to update to 3.52m33-3 and then 3.90m33-3. :smile:

hmm nice thanks men.. but what do chilly willy mean about this? If that Phat is TOO old, it may be missing keys 7 and 8?

i used the keycleaner and it recognized that it is noobs softdown downgrade something liked that and the corrupted key is 4, 5, 6 "that's what i remember". then it ask me if i want to fix it, then i fix it. and when i analyzed again the it say that my key 5 is patch with chilly willy patch...

is this ok? well when i fix my keys using this. theres nothing happen to my phat psp..

If your key 5 is Chilly Willy patch, you will need to unpatch and become original key 5 in order to update from 3.52m33-3 to 3.90m33.

This is just a map of upgrading:

Chilly Willy Patch << ---------- >> Original Patch Key 5

3.52m33 or below << ---------- >> 3.71m33 or above

Which means that you are now using 2.71se-b with Chilly Willy Patch Key 5. So when you update from your current version to 3.52m33, you will not need to unpatch key 5, just use Chilly Willy Patch key 5.

Key 5 is the ONE KEY that the 3.71 or better M33 updaters will fix themselves. What gets most people are missing key 7 and 8. They aren't "bad", just not there. I've helped more people who needed a key 7 and 8 than had a problem with key 5. :)

owhh!!! thanks! i get it now... but how can i know if my key 7 and 8 are missing? what if i use pandoraDC5 and upgrade it directly to 3.90 m33-3, and i do not unpatch chilly willy key5 patch and key 7 and 8 are missing? what will happen?

If you run IdStorage Manager and view the keys and look at 7 and 8, you will get an error code instead of data if they are missing. If you try to install 3.90 M33 and they're missing, you get an error code and it doesn't install.

You can run 3.xx with a patched key 5, it just doesn't need to be patched. 3.71 or better won't install with a patched key 5, but that's not because it won't run, it was just Sony trying to prevent people with custom firmware from updating.

so it means that there is no choice, but to upgrade to 3.52m33. and then upgrade to 3.90m33? is that right?

ohhh! sir! also i want to add to my question. what is the difference of kxploitpatcher and kxploitpatcher%, that is needed to for installing 3.52m33 to your pacther and to your keycleaner? and do i have to use kxploitpatcher, even if i patch my key to your way?

To the previous post, yes, some folks have to upgrade in steps. Not everyone can go straight to the latest. It depends on how new your PSP is and how much the old downgraders screwed it up. :smile:

The folder/folder% is how 1.50 is exploited to run homebrew. You put a specially corrupted EBOOT in folder% that triggers the exploit that allows the EBOOT in folder to run under 1.50. It's only needed in pure 1.50 firmware for running homebrew.

nice thanks!

is it ok for my psp phat to downgrade back to 1.5 CFW, with your key5 patch? and updgrade it to 3.52 CFW by following the step of DAX and team m33?

If your Phat is a TA-082 or TA-086, you need key 5 patched to run 1.50 or 1.50-based custom firmware (like 3.52 M33 or older). If the Phat is a TA-079 or older, it doesn't need key 5 patched. Once you have 3.52 M33 running and have all the keys cleaned (except maybe key 5), then running the 3.71 M33 (or newer) update should work. While on 3.52 M33, you'll be able to run KeyCleaner and IdStorage Manager if you need to change some other keys (like make 7 or 8).

yeah! my phat is TA-82. so can i downgrade my psp using pandora back to 1.5?

i want do backup my nand, co'z when i back read your thread this is important. is pandora

support the dumping of NAND? or i have to use the universal unbricker DC3,4 or 5?

sir sorry for asking to many question... i am so noobs in this field. but i understand a little. and understand more because of you sir.. thanks!

Yes, but key 5 must stay patched while using 1.50 or 1.50-based cfw. The TA-082 is one of those that needs key 5 patched.

DCx uses Pandora. It's just newer software for the magic stick. Anywho, they all support dumping the NAND, and I suggest people do that the first moment they can. Personally, I use elfmenu + nandTool 0.3b1 with Pandora. nandTool is a slightly more sophisticate and powerful nand dumping/restoring tool than the dumper in DC, but you don't really need to go that far. Any dumper will work for making a backup.

No problem. Better to ask NOW than to not understand something and really screw something up. When I first downgraded my TA-082 (from 2.71 to 1.50), I read every single thread on MaxConsole that mentioned "TA-082", "NAND", "devhook", and "downgrade". Back then, the downgrader messed with quite a few more keys than just key 5. It wasn't understood at that time that only key 5 needed to be changed. That was how I got into PSP programming - I needed something to help fix my own keys.

wow! i wish im smart like you!!

anyway sir i would also like to try the "elfmenu +nandTool 0.3b1 with Pandora".^_^

i heard about this UPT/UPMS, according to it, its a ultimate psp tools made for noobs like me..:D

anyway, i just use DCx for now, for dumping my NAND... i wish i understand too how to make an "elfmenu +nandTool 0.3b1 with Pandora". lol

phew! thanks sir for all the help.. i can fix now my phat psp...lol

thank you again sir see yah! later! ^_^

Elfmenu is relatively simple... make a magic stick like normal, then make a directory in the root of the memstick named "elf". Move the file "ms0:/kd/resurrection.elf" into that elf directoy. Then copy the resurrection.elf file from the elfmenu archive into that kd directory. That is replacing the main magic stick executable with elfmenu, while putting the original executable into the directory elfmenu launches apps from so that you can run it if you want. Then copy the nandtool_03_beta1_nousb.elf file from the nandtool archive into the elf directory.

At that point, booting the magic stick with a Pandora battery goes right into elf menu, which will show a list of the files in the elf directory (should be the original resurrection and the nandtool elf files). Use the d-pad to select nandtool and press X to run it. You'll then get the nandtool menu. Read the nandtool readme for more info about what you can do with nandtool. Quiting nandtool will go back into elf menu. Select resurrection.elf and press X to run the original magic stick program.

Note: I've attached the latest versions of nandtool and elfmenu so you don't have to hunt them down.

hehehe sir chilly...

i successfully fix my phat psp, and updated it to 4.01m33-2. thanks to your help. and also try the elf menu. wow its so very cool. lol

thanks sir... i think i will try the time machine this time.

Good to hear. Hearing about success is much better than hearing about failure. :biggrin:

So i got a psp slim 2004 but i screw it up and put another nand... but i manage to fix it to play iso/cso, but no umd, whith help of nandtools, pandora and homemister keys... there is no solucion for the umd yet :( but anyway i come where beacouse i run keycleaner and it said that i was on a ta-79 1003 is ther a way to change it to a 1004?? beacouse that's my region!

One of the "region" settings is in key 0x45. You can use IdStorage Manager to change that one. There are tables floating around about what values go to what regions. That only affects the WiFi. The main region value is in one of those unique keys, so you're out of luck on that.

ok, having a little problem, i am at 2.60 firmware and i have the KeyCleaner 1.4. i put it in my GAME folder and everything like it said, and when i go over to the game menu i go to memory stick and the name, pics, and the sound all work but when i start it the first thing to come up is:

The game could not be started. ( 80020148 ) PLEASE HELP!!!!!:confused1::confused1::confused1:

You have to use custom firmware to run any kind of homebrew, or Homebrew Enabler. I believe Homebrew Enabler is available for 2.71 and 2.80... you'd best search on that to be sure first.

Sry to bring this up again :P (got asked b4) Zoom for better vision :)

look at my keys XD but still... I don't find anything wrong with my PSP and still can update smoothly without error.

But can Chilly explain my keys problem? I mean each of the error keys indicate which part in the PSP. Thanks XD

EDITED: This is my PSP1002 as mentioned in my Sig there :P

That PSP was originally soft-downgraded. Then someone must have "fixed" only keys 4, 5, and 6. That left the other keys in the original soft-downed state.

You should probably use the latest DC to rebuild your keys. If you want to do it by hand, I can help, but it'll be more of a pain. Basically, to repair by hand you need to dump the key with IdStorage Manager, rename some of the files, make 0x43 by hand (or use someone else's copy as it's universal), and then use IDSM to write them back.

Sorry for the late reply for week :blushing: been bz...

Anyway, I don't face any problem using this PSP1002 from the time I bought it till now. I can still upgrade it without any error. It just seems like normal PSP.

Can you help me list down the error that will bring out from faulty key? If possible :P Thanks.

Key 0x41 is bad. This key controls the USB and it won't work properly until it's fixed. At best, you get generic storage usage, and that's it. When fixed, you can use things like USBHOSTFS.

Key 0x42 should be clear.

Key 0x43 is bad, and if I remember correctly, it's used for PS3 connectivity.

Key 0x45 is bad, and it contains some region info used by the WIFI.

Key 0x46 should be clear.

Key 0x47 is bad, and may cause problems with PS3 connectivity as well.

None of those are REALLY serious, as you've seen, but you can clear them up to eliminate any problems.

Notice that most of the "bad" keys aren't gone, just in the wrong place. If you dump the keys and then rename them, then write the keys back, you should be able to clear it all up.

Notice that 0x41 holds the original key 6. That's not really needed anymore since you've gotten that one fixed. 0x42 currently holds the original 0x41; you would rename 0x0042.bin to 0x0041.bin to write back the original value to 0x41. Notice that 0x45 has the original 0x47, and 0x46 has the original 0x45. The only key you're missing completely is 0x43. If you fix the others, KeyCleaner will restore 0x43 for you.

Dump the keys with IdStorage Manager.

Rename the keys that hold the original values to the proper names. See above.

Verify/fix the keys with IDSM.

Run KeyCleaner and fix 0x43.

Be sure to backup your NAND and keys as they are now just in case something goes wrong.

i used it and i think it caused a brick... i ran it and after that tried to play bleach 5 and it hanged. i tried to restart my psp but it juz could not start. There was only a black screen and the green light. Can u tell me wat happened? BTW i have a PSP-1000 3.52 M33-4

Sounds like you may have unpatched key 5... and TA-082/86s won't run without key 5 being patched unless you're using a patched IPL or 3.70 M33 or better. Use a Pandora battery and the latest DC to fix your problem.

oh ok cool... well actually i m quite a noob at this... could u like gimme some instructions on how to fix this problem? Very much appreciated.

You need to go read through the thread on using the Pandora battery and associated software.

Go look through the sticky threads in the FAQ and Guides forum. The Pandora Deluxe is generally one place to start.

Hey, i have used the keycleaner 1.4 on my psp 2000 v3, i know it was a big mistake but i did it for some reason, i have taken the ta-085 choice to mess with my key.

But now, my WIFI doesnt work anymore, when i scan for router, i get this error

"An internal error has occurred. (80410A0B)"

And my wifi light doesnt blink anymore.

Is it possible to fix that?

Thank you.

THat code is displayed when the wi fi is causing trouble.

Your details are a bit vague, you have a TA-088v3 board but choose the TA-085 option?

Few things it could be, The key for the wi fi is dead/deleted/corrupt, The wi fi board is loose.

I have to say though, that app is very safe if used correctly within the guidance supplied & i very much doubt the app is at fault, more your application of it.

First of all, i never dropped my psp so it cant be that, i am pretty sure that the key are corupted or deleted, so i was wondering if i could fix it without buying another psp, since the light doesnt even blink anymore. Also because keycleaner is certainly not used for psp 3000 or ta-088 v3.

Hi. I would like to apologize first hand if this has already been posted, but 33 pages is A LOT to read through.

A friend of mine wants to go back to official firmware. He knows nothing about CFW and homebrew and actually tried to upgrade from 5.00 m33-6 to official 6.20. I lol'd. Calls me up as soon as he finds that it doesn't work. So, I downgrade it using pandora's battery and begin to upgrade to the OFW. I get an error message and find that key 5 is damaged. Is it possible to return to OFW, or must his PSP live out the rest of it's life in CFW? It's a PSP 1000. TA-82/86...not sure which. Any help would be appreciated.

Either use KeyCleaner to fix key 5 or use DDC7 or 8 to regenerate a new IDS.

Update should work then.

Well, I used KeyCleaner and patched it, but it still does not let me update. I'm pretty familiar when it comes to the CFW and plugins. I don't know anything involving the keys. But, I'll look up DDC and figure out how to work it.

Thanks for the help!

::EDIT::

Excellent! I used DDC8 to create a new IDS and was able to update to 6.20 OFW.

Thanks again!