The original 2.71 downgrader comes with an app called idstoragechanger. The purpose of that app was to make TA-082/86 PSPs capable of running 1.50 firmware. A stock TA-082 or TA-086 won't run 1.5 as it hangs when it goes to check key 5 of the IdStorage. The problem was that the 2.71 DG idstoragechanger modified a LOT more keys than were needed - 9 keys instead of 1. Among the problems are:

- USB is only a generic USB 1.1 storage device
- USBHOSTFS doesn't work
- Stuttering while playing some ISOs
- Some people have brightness problems
- PSP won't come out of hibernation when battery is less than 12%

When NOOBZ came out with their 2.80 downgrader, they modified the idstorager changer to modify 3 keys, and hence had fewer problems. However, it still changes more keys than needed, and still caused a few problems - just not nearly as many as the 2.71 DG. Among its problems are:

- Some people have brightness problems
- PSP won't come out of hibernation when battery is less than 12%

The 3.03 downgrader used the same method of altering the IdStorage as the 2.80 DG, so it has the same trouble.

Eventually, it was learned that changing one byte of key 5 was all that was needed. Unfortunately, none of the original downgraders were changed to reflect the new knowledge, and to this very day people are still corrupting their keys with those downgraders (unknowingly). So me and a friend put together a new app to alter IdStorage key 5, and made new packages for all three downgraders. I also made an app to help people fix their keys if they ran one of the older downgraders on their TA-082/86.

Remember, this only applies to TA-082 and TA-086 PSPs!

EDIT: The sendspace links for all the apps that were here originally have expired, but rather than repost them, I'll just point you to my google group. Just download the app you want from the appropriate app page. You don't have to join to download, only to post messages. I'd prefer if people didn't join just for the sake of posting. You can do that here where more people will see the questions and answers which may help answer their questions as well.

http://groups.google.com/group/chilly-willys-ice-flow/?hl=en

Interesting, I had been reading something simillar to the effect of folks who were trying to upgrade from their custom FWs to 3.30 (not quite sure why you'd give up hombrew ISO and PSX games up for security and shiny RSS icons) but I remember the culprit being currupted ID storage due to t3h downgraders ID storage. Now just out of curiosity will t3h keys cleaner work on a custom FW or is this something you could only use on a newly downgraded 1.5? I already know my PSP is a TA-082, and I mean I don't really care about brightness bugs (which I have yet to have) and my battery is never below 30% or maybe 25% xD. But I guess I was just rather curious and this had caught my eye.

KeyCleaner can run via HEN on stock PSPs, or straight on 1.5 or custom firmware PSPs. The idea is that you run KeyCleaner via HEN before you downgrade your stock PSP and dump the keys as a backup. Then downgrade. If you use one of the corruption-free downgraders linked above, KeyCleaner will tell you that the keys are fine, and key 5 is patched for 1.5 / custom firmware usage. If you used one of the original downgraders, you can use KeyCleaner and the backup dump you made to clean up the keys.

If you didn't make a backup dump of the keys, KeyCleaner can fix all but one of the keys without a backup dump. If you used the original 2.71 DG, the one remaining "bad" key will be 0x0043, and if you used NOOBZ 2.80 DG or the 3.03 DG, the remaining "bad" key will be 0x0006. You can get those keys from someone with a good 82/86 PSP, or from folks with good or fixed PSPs via private message.

Now will this also allow me to update my FW beyond 3.30 if ever desired because I remember neverused making a post saying users who decided to go from CFW to offical couldn't go beyond 3.30 because of something to this effect

i have a ta082 white psp and it doesnt come out of hibernation or turn on below 12% battery. will the key cleaner fix this? is there a chance of bricking with the key cleaner? i also dont have the original key dump. and the link to the key cleaner does not work anymore.

i found the keycleaner on maxconsole and use square to fix my keys after being softdowned. still says bad key 0x0006 and idstorage key 0x0006... coyp of original key 0x0005. reading through the original to see if a fix key cleaner thread now to see if a fix was posted. thanks chilly you are awesome.


Edit: apparently i need a new key6 does anyone have a clean key dump for a ta082 they can upload?

The link to keycleaner on sendspace is broken!! Oh no, what can I do??

PS Does key cleaner have a risk of bricking????

here i uploaded the keycleaner i got. just download and check the readme.pdf

http://rapidshare.com/files/28807012/KeyCl...1_1_.1.zip.html

there is always a slight chance of bricking doing anything but it seems very slim from what i saw while running it. you can just use the keycleaner to check what bad keys you have without any worry. there seems to only be a chance of bricking when repairing the keys.

i read something about an image dump, do i need one of those? does dat file have?

you either need a dump of the cleaned keys or the original keys. otherwise you can try to fix without the dump. but if you fix without the dump folder you will end up with one bad key still like me. i still have a bad key 6. other people will end up with a bad key 43 after the fix. the key 6 has to be off a ta-82/86 psp.

does anyone have a clean key dump off their ta-82 that can give me key 6?

for me:

0x0008 no key (code 0x80000025)

can someone give me a dump? do i need all da keys fixed? wat if i leave this one?

So wait t3h read me says this can run on HEN will that only work with stock or can I run on a previously downgraded 3.03 HEN?

its normal for some of the ta-82 boards to have no key for key 8. if thats the only thing it says is wrong you should be fine.

so that means you have a good key 6? can you post a key dump?



according to the readme it should be able to be run like any homebrew.

It says my key 8 has no key. It says my 43 is cleared key, okay, but below it says my bad key is 43...

I dont think many people know what this all is. key cleaner finally working thanx bud.

its ok to have no key 8. according to chilly willy some ta-82s have a key 8 some dont so its normal. and your bad key 43 says ok because it reads ok. but it says its the bad key because its still not reading what it is supposed to. so to fix it you need a key 43. can you dump your keys and post them or just key 6 if you can?

In the list it says key 43 is okay, but down there it says key43 is bad, that's contradicting! And if it normal to have no key 8 how come it doesnt say ok?

chilly said key 8 is missing in most ta-082 and most ta-086 have it. it doesnt tell the difference between the boards so it just lets you know you dont have one. and he said the testers wanted it to read that way. put ok if the key reads ok but thats why he put its a bad key to let you know its not the right one.

so can you upload a key 6 from your dump?

Here's a new upload of KeyCleaner v1.1 to sendspace. I would have uploaded to here, but it's too big.

http://www.sendspace.com/file/nm9yuq

It's a pain that SendSpace files only last a few weeks, but I like it better than most other services as it doesn't make you jump through hoops to download the damn file.

Keys go in a folder of any name inside the KeyCleaner folder (where the EBOOT is). When you choose "fix with files", KeyCleaner steps through all folders inside the KeyCleaner folder showing you what it thinks of the keys in that folder and giving you the option to either skip that folder or select it to use to fix the keys.

The preferred action is to first try fixing without files. That usually leaves you with one bad key - either 6 or 0x43. You can then fix that one key with a single file. You can make key 6 or key 0x43 yourself with a hex editor and this text file about the various keys: http://harleyg.net/docs/idtable.txt

You could also PM someone.

There's a big thread over at MaxConsole as that's where most of the work on this occured, but I didn't want to point people over there as most boards don't like folks posting links to other boards.

If anyone has questions, be sure to ask. Better to ask if you're not sure than to goof things up. KeyCleaner is designed to be pretty idiot-proof, but the universe is getting better at making idiots.

As to one question I saw above: KeyCleaner has only a VERY small chance of bricking... the two methods of bricking that we know of are covered. 1) Running out of battery power while writing the flash - KeyCleaner checks for a 75% battery charge before it runs. 2) Key 5 having a certain value will brick TA-082/86 PSPs - KeyCleaner will ALWAYS patch key 5 when it writes it to avoid this brick.

So while it's theoretically possible to brick, no one has yet reported bricking using it... and if someone had, they'd be screaming bloody murder. I've had two people that somehow managed to REALLY goof up their keys badly, but I was able to set them both straight with one or two replies.

Okay well I only asked because Chilly said stock but I mis-read because that's if you wish to dump yer keys then which I didn't.

yeah there is a huge 14 page thread over on max console i read through the whole thread thats where i got the cleaner i uploaded and most of the answers i was posting.

You have to be a little careful about keys... key 6 from a TA-079 is the same as the one from a TA-081, but different from a TA-082 or TA-086. The key 6 from a TA-082 and 86 are the same. All PSPs have the same key 0x43, so a dump of 0x43 from any (good clean) PSP is fine.

As for key 8 - key 8 comes on PSPs that have a different LCD module than the original LCD. This "new" key 8 along with new display libs in the 2.71 and up kernel (if I remember correctly) take care of the differences between the new LCD and old LCD. A scant few TA-082's have this, while most TA-086s have it. Missing key 8 only means you have the old LCD module. Having key 8 means you not only have a new LCD, but will also have the brightness bug when you downgrade. The bug is due to the old display libs in the 1.5 firmware installed for the custom firmware, not the keys! There's a thread at MaxConsole and lan.sh that shows how to write the newer display libs into the flash to eliminate this brightness bug, but it's not for the faint at heart.

Questions like that one are the kind I like... rather than ones like "when it says 'press O to exit', does that mean it will exit when I press the circle button?"

wierd i never had the brightness bug and i have a key 8

Many folks don't notice it because it's only active when in 1.5 mode... like in the recovery menu or in 1.5 apps. However, once some people do notice the bug, they obsess over it, even though it really isn't much of a bug to begin with.

Hey Chilly RU from Max Console I think I seen u there, in my one thread when I asked about 082 the person said to look @ Chilly Willy's thing and I thought I would have to goto Max Console, but I guess U R here now!

i tried to get the brightness bug to show up my brightness button works fine in recovery and 1.5 kernel. maybe the bug is something different than i thought.

yes chilly is from max console i got most of my answers to peoples questions here from his answers to peoples questions there.

realg can you send me a dump copy of your key 6 since yours seems to be good

Chilly Sent me a file w/ 6 and 43 keys, do u want that? Am I allowed to post a link on the forums??

Anyways, judging my that picture, what key[s] do I need just 43??

awesome thanks for the files chilly and realg. key cleaner says everything is good now. all i needed was a good key6

edit: wierd now that i have key 6 fixed the brightness bug shows up. is there a way to put it back the way it was... hahaha

Ah... that's interesting to hear. Maybe we can find a way around the brightness trouble without libs. This will take some looking into key 6.

You can "break" your keys again with the idstoragechanger app from the 2.80 downgrade from Dark_AleX's web site. That will break 4, 5, and 6. Then run KeyCleaner and fix without files to fix 4 and 5, leaving 6 broken.

We learn a bit more about what's in the keys this way.

It's not a contradiction, it's the way my beta testers felt was best to keep from scaring users. KeyCleaner checks each key individually to begin with. The okay means that no error occured while checking the key. KeyCleaner also makes note of a general status of that one key... is it an original key, is it a copy of a key, is it cleared?

Then KeyCleaner takes all the keys into consideration - are they what they're SUPPOSED to be? It puts an overall state description below the individual key statuses. So an indiviudal key might read okay and have a clear status, so it reads "clear - okay", but if it's SUPPOSED to have something else in it, the overall state of the keys will be different than if it had the correct contents.

well i ran the id storage changer from dark alex ta-082 downgrade. and when i fixed it using the key cleaner it fixed all but key 43 this time... when the original time it fixed all but key 6. but this time the bug was still there even after the ta-082 id storage patch was run. so thats wierd. so i just cleaned the keys again so they are all ok.

You ran the idstorage changer from 2.71, not 2.80. Use the 2.80 DG idstorage changer app.

So OK for 43 means it checked the key okay and there is no key, below it says its the bad key cuz there is supposed to be no key.

And for 8 it says no key but there isn't suppsoed to be a key.
When i fixed key 43 it just put it back the the original, did it need a MS to tell it to do that?

no go still the same problem using both downgraders now... wierd stuff. anyways i now have clean keys and the brightness "bug" . so whats the big deal with this bug if all it does is add an "off" brightness? or is there something worse that i dont know about.

What is the brightness bug, I dont think I had that just cut out after 20% and when I did USBHosts Windows said that the driver didnt have any info on the device!

I noticed the brightness went differently for me but I probably was just trippin'..

from what i noticed the brightness bug just cuts out the screen during homebrew. when pushing the brightness button during homebrew or in 1.5 the screen will blank out so it has like a 4th brightness of off. i think thats the bug because mine didnt do that before. and since you dont have a key 8 that means you have the old screen which means you shouldnt have the brightness bug as they said it mainly affects new screens.

does the bug do something worse than add a 4th brightness of off? if not i dont see why people were making such a big deal out of it.

There is a key 0x43, but it's content is nothing but 0's. That's what cleared means. Cleared doesn't mean no key, it means a key that is clear. It would be like a text file that was nothing but spaces and no letters.

If you get the code 0x80000025 for key 8, that's fine. It just means your PSP doesn't have a key 8, which is fine.

Both 6 and 0x43 are fixed from files on the memstick. I'd bundle those with KeyCleaner, but can't do that in the US due to stupid IP laws. It's debatable whether Sony can actually claim a copyright on those files due to the limited content, but that doesn't mean they wouldn't try to sue anyway. So KeyCleaner fixes what it can without files, and leaves it to the user to find files on their own for the rest.

As to the brightness bug... from what I understand (as I have an old 82 that doesn't have it), it consists of two things: one level of black, and the brightness changes backwards, going bright, dimmer, even dimmer, black. Normal PSPs go dim, brighter, even brighter, brightest.

The download link for 3.03 doesn't work for me..

i still dont see what the big deal is if thats all there is to the bug. before all this my psp only had 3 levels of brightness and it still has 3 levels. and never went black. but i didnt notice it going backwards now that i think about it. i just checked again, while typing this, and i no longer have a black level. just the 3 i started with and it still goes backwards in homebrew but no longer goes black in homebrew, or in recovery mode. like it magically fixed itself. all my keys are clean.

Mine never went dim if U used iR Shell to get max bright and then push button it would goback to where I was then bright, max bright..

Yeah, the "bug" doesn't seem worth all the fuss to me. The one quirk you noticed may have been a setting that the PSP corrected. Generally, you should "Restore Default Settings" when you mess with your PSP, like update to a new custom firmware. Half the issues many people report (especially about the browser) are cured by doing that.

brightness glitch is back out of nowhere. seems like it comes and goes when it feels like.

My battery is messed up, might be partly cuzza this, since my PSP cut out at 20% it has never been bwloe 20% for months, so maybe when it was that's why???

My understanding of it is key 6 controls that. Setting key 6 back to it's original state usually fixes that issue for most folks. Check your key 6 against the one in the text here: http://harleyg.net/docs/idtable.txt

i dont get what dat file means, how do i reset key 6 to fix da battery thing?

also i notice dat before when my psp was stock it wouldnt charge while wlan was on, after downgrade it did, now it doesnt!

also if da key was cleared to 0s, why would i need a file? how come da one key needs da file? y dont da other ones?

so you ran the key cleaner and you still have the problem?

The downgraders move some of the keys around, and toss out others. So depending on the downgrader you used, most of the keys can be restored, but some cannot and have to be replaced from a file that holds the original contents of the key.

If you used the original 2.71 downgrader, fix without keys fixes all the keys but 0x43. If you used the original 2.80 or 3.03 downgrader, fix without files fixed all the keys but 6. I'd include those two keys with KeyCleaner, but there's some dispute over whether distributing keys violates copyright laws. Some keys clearly cannot be copyrighted as they don't meet the criteria (for example, cleared keys are nothing but 0's, so they cannot possibly be copyrighted).

Key 6 controls aspects of the power related to the battery. A good key 6 allows you to run the PSP with less than 12% charge, but DOESN'T allow the battery to charge while the wifi is on (unless you have the custom firmware set to clock the CPU at 333MHz). A broken key 6 allows the battery to charge while using wifi at any speed, but doesn't let the PSP run at low battery levels.

You don't NEED to fix key 6... the keys recommended to fix are 4 and 0x41. So if you fix without files and key 6 is still broken, you can either leave it, or get a copy of a good key 6 file and fix it... it really doesn't matter other than the behavior described above.

Key 6 appears to be working. Is there a reason why it dont charge when WiFi is on??

I just am confused why my batter F@#$ed up..

interesting. but when i fixed my keys without the mem stick key 6 was still bad and i was still able to run at low battery levels and i was not able to before the fix. it was the first thing i checked because it bugged me the most.

on a side note i think i know why i never noticed the brightness glitch before. i only get 4 levels of brightness when my psp is plugged in. and in homebrew the 4th level is "off". so it only shows up when my psp is plugged in and not on battery.

That's standard Sony behavior. They didn't wish the have the wifi and battery charger both running at the same time to keep the PSP cooler.