General IdStorage Repair and 1.50 ipl enabler Released

[mnuhaily22]

Yes!!!!!my Usbhosts Is Fixed!!!!

[kingreuben]

I ran the program, and, unfortunately, it didn't fix the brightness issue.

[Xeniczone]

For those who don't know I think it is ment to fix the problems with downgrading a psp with a motherboard TA-82 or TA-86.

The Problems are:

-Adhoc
-Brightness (after downgrading the psp has a blank screen until you repeatedly push the display button)
-Battery (if you turn your psp off after downgrading with 12% or less on it it will not turn back on)
-USB issues

[burrito]

The 2.71, 2.80 and 3.03 downgraders change more than 1 key.
It was recently found out that only 1 key needs to be changed. This program unpatches all keys that were patched while downgrading except for the 1 key that actually needs to be patched.
In some cases, this will fix brightness problems.

I found this post on lan.sh saying how to fix the brightness problem: http://lan.sh/showthread.php?t=730&page=6

Yes, it is. I have done so, but it is a VERY delicate change. My brightness works correctly in everything but the recovery screen now. This is very dangerous if you mess up any of these steps you will have a brick. In fact, I recommend nobody trying this. This has however fixed my brightness in homebrew for the TA-082 3,2,1,off brightness problem and been tested in 1 other non-TA-082 PSP.

1) Get a copy of the 2.70 update eboot
2) Extract the data.psar file from it via PBP Unpacker
3) Use a psardumper program to extract 2.70 DECRYPTED (option square i think)
4) Take out 3 files: display.prx, impose.prx, and lcdc.prx and rename them to display270.prx, impose270.prx, and lcdc270.prx
5) Go to the recovery screen and go to the advanced option and turn on the USB to access flash0
6) Add the display270.prx, impose270.prx, lcdc270.prx files to flash0:/kd/ (DO NOT ALTER THE EXISTING DISPLAY.PRX, IMPOSE.PRX, or LCDC.PRX OR YOU WILL BRICK)
7) After this you need to modify this file "flash0:/kd/pspbtcnf_game.txt" and ONLY this file. This is the ONLY file that will be modified in the whole process.

Change the following lines:

/kd/lcdc.prx TO /kd/lcdc270.prx
/kd/ge.prx #/kd/display.prx TO /kd/display270.prx #/kd/display.prx
/kd/impose.prx TO /kd/impose270.prx

8) Safely eject the USB on the PC
9) Toggle off flash0 USB

This modification uses about 100kb of your flash0 and uses unencrypted versions of 3 files from 2.70 instead of the 3 files from 1.50. The normal space left from 3.10 OE-A' is about 400kb. This change should be undone before doing anything firmware related such as custom firmware updates by deleting the three 270 files and reverting "pspbtcnf_game.txt".

Sorry to repeat myself, but this change has only been tested on 2 PSPs with success (although it had no effect on the non TA-082 one) and 0 bricks (the brick by squirrel was from a seperate test after this one was successful). I have turned my PSP off for hours and it still runs after the change. IF you want to try this do so at your own risk.

DO NOT MODIFY OR REPLACE ANYTHING BUT pspbtcnf_game.txt

[Buddy4point0]

great ofr TA-82
lucky me i dont have a TA-82

[burrito]

The brightness problem only happens on TA-086, not on TA-082 or below.

[sedkiller]

If im not sure i have the TA-082 problems, can i use it anyway and not brick ? caus im not really sure i have the problem...

[shedeus]

The brightness problem only happens on TA-086, not on TA-082 or below.

not so. i have ta-082. it has the brightness issue.

[comicgeek]

These issues are found in recent PSPs only some 2.71 TA-082 and most TA-086. I had the brightness issue and after I used the hack posted at lan.sh only the recovery menu remains having the inverted brightness problem. Now when playing homebrew it shows the correct brightness settings as it was in the XMB.

[burrito]

not so. i have ta-082. it has the brightness issue.

Are you sure it's TA-082? Look at this picture of a TA-086. At the bottom you see IC1003, which means it's 082 or 086. To the left of it is a black thing. On a TA-082, it is silver. You can see it by opening your UMD drive.