(TA-082/86) Safe to use recovery mode to go back 1.50 from 3.40 OE-A?

[sameapple]

Hi I am first time here. I bought a psp today, it is a TA-082/86 with official firmware 3.11 installed. I updated to FW3.50 and used the

downgrade package that I got from here to get my psp to 1.50. Then further updated it with CF 3.40 OE-A. Until now, I've encounterd

a serveral blank screen issue upon reboot and entering the recovery mode which I fixed by pressing the brightness adjustment button.

However, I was informed by the "v3.50 Downgrader FAQ" that the blank screen issue doesn't happen on this downgrader. If so, why it

happens to me and some ppl else too?

I research for hours reading other forums and an article from wikipedia and I discovered that all these battery/brightness/wireless

issues had to do with the corruption of one's psp IDstorage key as a result of patching them which is nessessary in order for a TA-082

psp to accept FW1.5. I resort to psp-hacks forum for solution to this brightness issue and the detail post is here:

http://www.psp-hacks.com/....php?pid=1037938#p1037938


I was adviced to use Chilly Willy's KeyCleaner v1.0 to patch my IDstorage that would fix the brightness issue however it didn't. The

KeyCleaner patched the "0x0005" of my psp IDstorage because this line was detected with "unknown status".

Now I am so worry that I messed up my psp's IDstorage with that strange program that patched my psp's IDstorage key because I

know in order for my psp (any TA-082/86 system) to accept FW1.50, the psp's IDstorage key must be correctly patched. So my main

question here is that will my psp brick if I downgrade it back from 3.40 OE-A to sony's official FW 1.50 through the custom firmware

recovery mode?

Thank you for your time and please I really need help!

[wakaru]

No it won´t.

If your TA-082/086 can run 3.40 OE, it will handle 1.50 as well. (3.40 OE-A is using the 1.50 bootstrap or whatever it´s called)

You should have made a backup of your IDStorage keys with Chilly Willy´s Key Cleaner though. You never know when you´ll need them.

[sameapple]

Thanks for the help and Yes, luckily I've dumped my IDstorage key before patching the "0x0005". I read from the maxconsole forum that

the dumped keys can be restored using a certain program. Any idea on how to do this?

[wakaru]

I think KeyCleaner can do that.... though I am not sure.
If not, try IDStorage Cleaner 1.1, from same coder (Chilly Willy), which according to this thread http://forums.noobz.eu/ge...us-fw-on-ta082plus-psp/0/
cannot be run in 3.50 HEN, so run it on 2.71 HEN and you will be back to the original settings afterwards. (Meaning you could then upgrade again to 3.50, of over although I would not do, bypassing that Sony security measure in place after 3.11 firmware).

[sameapple]

k I am gonna try the v1.1

Pordan me though I am not computer language literated so I could only guess how this is troubling TA-082/86 through decent logics. Please check this tell me if it's right/wrong:

1.) Unpatched IDstorage key "0x0005" is modified -> FW1.5 supported + creates blank screen issue.

2.) Then, IDstorage key "0x0005" is reversly modified the second time such that the blank screen issue is dissoved -> thus, FW1.5 becomes unsupported.

From here it is observed that the key "0x0005" controls at least the psp's compatibility of firmwares and screen brightness levels. A relationship is also seen here that the modification of 1 of these 2 factors causes the other to change correspondingly. Do they exist only in the 2 combos above?
(Which are: "1. FW1.5 supported + blank screen issue" "2. FW1.5 unsupported + no blank screen issue") ?

[wakaru]

(...)
From here it is observed that the key "0x0005" controls at least the psp's compatibility of firmwares and screen brightness levels. A relationship is also seen here that the modification of 1 of these 2 factors causes the other to change correspondingly. Do they exist only in the 2 combos above?
(...)

Don´t quote me on this, but I think that the blank screen issue was because the first TA-082, TA-086 downgraders released changed several idstorage keys, when only the "0x0005" key was responsible for the 1.50 compatibility (but this was not found until much later). Therefore KeyCleaner fixes the keys that should not have been changed, in order to fix the screen, USBHost and wifi problems experienced by some (if not most) TA-082/86 downgraded  PSP users.

Nowadays the latest downgraders (i.e. the 3.50) only patch the "0x0005" key, hence there should not be any screen issues.

Bottom line is that the key "0x0005"  must be patched to run 1.50 or Custom firmwares or otherwise the PSP will brick.

The problem is that now Sony has included a security measure in their latest firmwares where if any TA-082/086 with the patched "0x0005" key try to upgrade to a newer official firmware (I think this is just for 3.11 Firmware or over) it will simply not work.

The Noobz team seem to be working on it though  

[barbs]

The problem is that now Sony has included a security measure in their latest firmwares where if any TA-082/086 with the patched "0x0005" key try to upgrade to a newer official firmware (I think this is just for 3.11 Firmware or over) it will simply not work.

The Noobz team seem to be working on it though  

Hey guys - First of all thanks Team Noobz for the excellent downgrader.  I have not used it but I have a copy of Lumines as well as several backups of my current PSP games and I am hesitating to use the downgrader before I get some news about this rumor i've been reading - Are you guys working on this project for a program that will fix the 0x0005 key so that we can update to the new official sony firmwares on ta 082?

I have one of these motherboards and I have not yet downgraded, although I have all the files and Lumines for it, because I am afraid that God of War or Castlevania will be released as requiring a version over 3.51, of which no custom OE is available.  I would not mind - if I could simply upgrade to sony's official firmware and resort to using my UMDs again.  I'm torn on what to do - part of me just wants to throw in the towel, downgrade anyway, and see what happens.

Anyway I just wanted to respark interest in this - Hows it coming along?

Thanks for your excellent community work.

[wakaru]

(...)
I have one of these motherboards and I have not yet downgraded, although I have all the files and Lumines for it, because I am afraid that God of War or Castlevania will be released as requiring a version over 3.51, of which no custom OE is available.  I would not mind - if I could simply upgrade to sony's official firmware and resort to using my UMDs again.  I'm torn on what to do - part of me just wants to throw in the towel, downgrade anyway, and see what happens.
(...)

There is a new Custom Firmware from Team M33, called 3.51 M33. That CFW should allow you to play any game up to press so far.
http://forums.noobz.eu/ge...-pikey-v0-3-compatible/0/

(...)
Anyway I just wanted to respark interest in this - Hows it coming along?
(...)

It´ll be done when it´s done. Don´t worry and be patient.

However, and until the Noobz Team release that utility, there is a way to go back to the highest official firmware on a downgraded TA-082+ PSP. Just check this thread, where it´s all explained:
http://forums.noobz.eu/ge...us-fw-on-ta082plus-psp/0/

[barbs]

Thanks for the information man.  I'm just a huge noob with the PSP scene that I'm afraid I dont even understand these steps

1.) Do i need to backup my 0x0005 key prior to downgrading at all using lumines?

I cannot understand that part of the step.  I am not sure when i should be downloading my IDkeys.  Thanks

[wakaru]

Backing up your IDStorage keys is only optional, but recommended.

During the downgrade with the 3.50 downgrader, ONLY your 0x0005 key will be patched so your PSP can run 1.50 Firmware.

IDStorageManager v1.1 of a present version has the bug, and the 'verify/fix' mode doesn't work on HEN-D/3.03HEN, therefore you cannot back up or your IDStorage keys while in 3.50 HEN. Nevertheless, it should work in 2.71 HEN, 1.50 or CFW. Therefore whenever you try to back the IdStorage keys up, 0x0005 will be already patched.

Whenever you want to upgrade again to the latest Official Firmware, just upgrade to 2.71 Official Firmware first, run HEN-D (Tiff Exploit), then IDStorageManager 1.1 (In order to fix key 0x0005 to it's original value and then you would be able to upgrade to the latest official firmware without problems).

Do NOT try to fix the 0x0005 key in any firmware lower than 2.71 or otherwise you will get a brick. (Actually I think that in 2.50 or 2.60 firmware you wouldn't but at this moment I do not think it could be possible to run IDStorageManager on such firmwares)

I could not confirm you all of this though , because I have never done it. You could ask Sandler in this thread (http://forums.noobz.eu/ge...us-fw-on-ta082plus-psp/0/) if you have any problems.

[sameapple]

Whoa then I can forsee that this is gonna be dangerous should Noobz decide to release a fix for IDstorage key so one can go back to official firmware...

Because this whole patched IDstoragekey issue and details is discrete and can possibly brick your psp if not patched properly. As I've heard many different stories from ths psp community.

Like you and the readme in the downgrader package said because only the "0x0005" is patched, there shouldn't be any blank screen issue however, the blank screen issue happened to me and others, this I am 100% sure and I can confirm that. Then it is possible Noobz have been misinformed that editing/patching key 0x0005 does not cause any issue other than allowing the psp to be downgradable.

If this didn't happened to you or someone, then the problem is inconsistence and uncertain which is quite risky if further work is to be release base upon this uncertainty...

Hopefully thing will be more clear later.

[Fanjita]

Yeah, I think we might have been wrong/misinformed about the blank screen issue, which is a shame.

But it's not on the level of something that might cause bricking, which is something that we're always much more careful to test and be sure about.

[sameapple]

Hi there again.

The recent Custom Firmware 3.51 patch M33-7 said to have fixed the brightness problem for the TA-082 psps. I've tried it and it worked.

Any idea if this fix touched the IDstorage key "0x0005"? If yes is it still safe to restore the psp back to 1.5 from CF3.51 m33-7?

Thanks

[wakaru]

[Speculation Mode ON]  

I believe that patch (#7) for CFW 3.51 M33 which corrects the brightness issue has got nothing to do at all with the IDStorage (or at least with the key 0x0005) since you should be able to revert you PSP back to 1.5 with no problems from the Recovery Mode.

Perhaps the brightness issue for the TA-082+ had nothing (or very little to do) with the IDStorage key 0x0005 ONLY and these wise russian coders have found exactly where that problem was coming from, and found the way to sort it out.

[Speculation Mode OFF]

This should be easy to find out just by dumping the IDStorage keys twice in a TA-082+, first before applying the patch #7, and then again afterwards.... You would just have to compare them to find any differences.

My money is on that you will not find any though.

I wouln't mind trying that myself, but my PSP is a TA-081, so the brightness issue is not applicable to me.

[sameapple]

lol nice speculations.

First of all I think that the Russian hackers are truly amazing. From the look and quality of their early works in the psp field, they really stand out as highly experienced compared to others (probably because much of the foundation key works have been done by others and shaped the coding custom which lead to an easier coding in the future). Perhaps they've been waiting for moment like when Dark_Alex steps out before intruding and showing off their skill, still undeniably, I'd say they're really good hackers (of course, the downgrader developers too!).

True though dumping the IDstorage key again and compare them might work but honestly I really don't know how.

But if the Russians hacker permenantly fixed the brightness issue then it would mean that even if re-installing the custom firmware, the blank screen will no longer shows up and I am going to try it right now.

If the blank screen persists... then the brightness fix was only corrected solely on the psp's OS/firmware code.
If the blank screen no longer persists... then the brightness fix was corrected permenantly at the psp motherboard flash or IDstorage (But indeed, it doesn't mess with the 1.50 bootstrap).
Posted on: July 23, 2007, 01:12:09 PMAh ha, wanna hear the results? They're as follow:

I used the recovery and got my psp back to firmware 1.5. And Yes! the first thing showed up upon restart was a blank screen.
I immediately rushed to upgrade it to custom firmware 3.51 m33 (unpatched) first because I feel uneasy without the recovery mode.
Upon restart I entered the recovery mode, the blank screen appeared just like before patch #7.. ehhh everything was like before.
Lastly got it back to patch 7.

Conclusion:
Base on your speculation and my understand + this testing, it seems obvious to me that the brightness issue comes from IDstorage key wether it's 0x0005 or not, it's directly influenced by the IDstorage key configuration.

Secondly this brightness fix of m33-7 is not permanent. Generally speaking, it was only corrected and recognized by the psp's operation system / firmware (software), not a fix on the hardware. As this explanation fits the results.