3.03 (ta-082 and ta-086) Downgrader {Release} Corruption free ~

3.03 (ta-082 and ta-086) Downgrader {Release} Corruption free ~
This tutorial is only for Ta-082 or Ta-086 3.03 downgrading to firmware 1.5.
Use this at your own risk. Its always possible to break your psp.
Special thanks to Chilly Willy for taking the time to code this


To verify you have a Ta-082 or Ta-086 see the picture below.



PLEASE NOTE: YOU MUST HAVE YOUR PSP CHARGER IN AT ALL TIMES!

Donot power off During downgrade!

Donot use fake memory cards to downgrade or upgrade see link below to identify fakes.
http://forums.exophase.com/showthread.php?t=651

Note: If at some point your screen goes black for more then a few seconds Hit the brightness key gently a few times. Be careful not to bump the power or other buttons. In some cases the brightness goes to off.

Requirements

* Original GTA LCS (any region), which should have the 2.00 update on the disc.

1. Before you start, format your memory stick and reset your default settings.
A. Format MS by going to System , Format Memory Stick. press X
B. Push down to restore Factory Settings

2.Create a USB connection between your PSP and computer.

3. A. Download the official Sony 1.50 eboot and rename it to UPDATE.PBP

B. And put it in the MSroot/PSP/GAME/UPDATE folder of this download with the name of UPDATE.PBP DO NOT OVERWRITE PSP/GAME/UPDATE/EBOOT.PBP! Doing so will brick.
official Sony 1.5 eboot ** http://www.psp-hacks.com/category/43

4.Copy the contents of the MS_root folder to your memory stick root, click yes to overwrite. Do not put the readme on the psp.

5. Load GTA LCS

6. It should get to loading savegame, then the screen will clear to black and fill with a light blue color, then the PSP will reset itself.

7. Check that HEN is running by going to system settings, then to "System Information" and it should show up as system version 303 HEN.
If it is showing up as 303HEN then go to the memory stick and run the The update.

8. If you have an unpatched TA-082 or higher motherboard, you will be prompted to allow the downgrader to patch your motherboard so it can Be safely downgraded. The downgrader will not let you proceed without patching, if your motherboard requires it.

9. Before the downgrader does anything to your PSP it will ask for you to agree to what it is doing, if you no longer want to continue press the Right Shoulder Button (R-TRIGGER).

10. Once you have agreed to start the downgrade do not unplug the PSP, or try and restart it.

11. Once finished the PSP will ask you to press X, and reset itself.

12. If it comes up saying that the settings are corrupt, press X to continue, this will mean you will need to re-enter the settings for network connections into your PSP.

All done now If everything went well you should now have a brand new 1.50!

FORMAT YOUR MEMORY STICK AND RESTORE DEFAULT SETTINGS BEFORE DOING ANY THING ELSE>>>>>>>>>>>>


Credits:
TA-082 downgrader by Dark_AleX/Mathieulh/Harleyg
1.5enabler Concept and modifications by Chilly Willy
Original driver modification by codes02
Original readme's adapted by XsavioR
photo thanks to Calo edited for content
Original tutorial by X3phase
proof of concept: Stapol, Vad

Attachment 13823

_______________________________________
2.71 downgrader http://forums.maxconsole.net/showthr...480#post448480
2.80 downgrader http://forums.maxconsole.net/showthread.php?t=53933
3.03 downgrader http://forums.maxconsole.net/showthread.php?t=53936

Cool, thakyou for this downgrader

it was my understanding that noobz 303 downgrader was already corruption free. i used it and i have never had any brightness problems or anything else associated with ta-082 corrupy keys

You don't need to use the 1.5 enabler for the 3.03 downgrader.You only need to use the modded ta082 driver by codes02.

Originally Posted by suzukis4ever

You don't need to use the 1.5 enabler for the 3.03 downgrader.You only need to use the modded ta082 driver by codes02.

Yeah that was a typo , i fixed it , We actually worked together with codes02 to prouduce this. We spoke after the confusion. Noobz downgrader is pretty good. This however only swaps 2 bytes of key 5, which is whats needed to run 1.5 ipl.

Codes driver over writes the byte.
This modification to codes driver (with permission from codes02) swaps two bytes.

Same out come , it was agreed that the 1.5enabler *method* was cleaner , and hence this standard was used in all 3 DG.

Originally Posted by vodkkaa

it was my understanding that noobz 303 downgrader was already corruption free. i used it and i have never had any brightness problems or anything else associated with ta-082 corrupy keys

The 303 DG was LESS corrupting, but still corrupted 3 keys (4, 5, and 6). The "new" method only changes one byte of key 5, and does so in a reversible manner.

The main issue from altering key 4 is a change in how (most) PSPs operate at low battery levels. I don't know of any issues related to altering key 6, but better safe than sorry.

I compared the codes02's ta082_driver.prx ,that I was previously using with 3.03 downgrader, with the one inside the above package and it is different.

Original codes02's ta082_driver.prx :
CRC32 1B1BA372
MD5 5F1BE45A59F1D455AA24040123F864ED

The new ta082_driver.prx inside the package:
CRC32 425468A5
MD5 2962921D1E40EA0848F480817F85C51C

So, the codes02's ta082_driver.prx was modified ?

Yes Codes02 driver originally wrote a new value to one Byte....

It now , takes two bytes and flips them,, Its no big deal if you ran codes02 first version. Me and codes02 spoke this morning about standardizing the method used. And decided on Chilly's method of 1.5Enabling.

The key benifit is NO keys or values are purely over written. You can recover 100 % with this version , by fliping the two values back... for example

if its originally 12345
codes original 19345
Now it does 13245

It was cosmetic, both methods work. Ones just "less" corrupt and easier to revert.

Originally Posted by Bon Scott

I compared the codes02's ta082_driver.prx ,that I was previously using with 3.03 downgrader, with the one inside the above package and it is different.

Original codes02's ta082_driver.prx :
CRC32 1B1BA372
MD5 5F1BE45A59F1D455AA24040123F864ED

The new ta082_driver.prx inside the package:
CRC32 425468A5
MD5 2962921D1E40EA0848F480817F85C51C

So, the codes02's ta082_driver.prx was modified ?

codes02's driver was fine for downgrading... it altered one byte of key 5. I modified it just a smidge to be exactly the same as the 1.50 Enabler we released a little earlier. The idea was to make all the downgraders work on the PSP key 5 in the same manner.

The source for both are out there for anyone who wishes to see what they do. But that is why we give credit to codes02 in the new releases - because I just modified his replacement ta082_driver.prx and tested it to be certain it was doing what it was supposed to.

Originally Posted by Chilly Willy

The 303 DG was LESS corrupting, but still corrupted 3 keys (4, 5, and 6). The "new" method only changes one byte of key 5, and does so in a reversible manner.

The main issue from altering key 4 is a change in how (most) PSPs operate at low battery levels. I don't know of any issues related to altering key 6, but better safe than sorry.

i currently am running 3.03 OE-C. if i downgrade to 1.50 then up to 3.03 agian, is it still possible to run your corruption free dg or will i end up bricking due to my currently changed keys. it would be nice to have a clean install of 1.50 on my ta-082 and know i will never have any problems with it.

Originally Posted by idstoragefix

Yes Codes02 driver originally wrote a new value to one Byte....

It now , takes two bytes and flips them,, Its no big deal if you ran codes02 first version. Me and codes02 spoke this morning about standardizing the method used. And decided on Chilly's method of 1.5Enabling.

The key benifit is NO keys or values are purely over written. You can recover 100 % with this version , by fliping the two values back... for example

if its originally 12345
codes original 19345
Now it does 13245

It was cosmetic, both methods work. Ones just "less" corrupt and easier to revert.

Well, not exactly... I invert the first byte in binary format. The exact code is

            buffer[0] = (char)(~((int)buffer[0] & 0xff));

~ is the binary NOT function in C. Using it twice results in the original value. The above code replaces first first byte with NOT(first byte). That first byte is 0x67, so it is replaced with 0x98. Running the enabler again will invert that byte again, giving 0x67 once more. Very simple (for a programmer ), and only modifies one byte.

Originally Posted by vodkkaa

i currently am running 3.03 OE-C. if i downgrade to 1.50 then up to 3.03 agian, is it still possible to run your corruption free dg or will i end up bricking due to my currently changed keys. it would be nice to have a clean install of 1.50 on my ta-082 and know i will never have any problems with it.

How did you originally downgrade? What IdChanger program did you use (if any)?

Originally Posted by Chilly Willy

How did you originally downgrade? What IdChanger program did you use (if any)?

i used the noobz 303 downgrader. i havnt changed any of the keys except for what the downgrader has done

Originally Posted by Chilly Willy

That first byte is 0x67, so it is replaced with 0x98. Running the enabler again will invert that byte again, giving 0x67 once more. Very simple (for a programmer ), and only modifies one byte.

And this folks , is why Chilly Willy codes apps.... and why I'm happy to beta test them. And write documents so he can spend more time coding

will 32mb sony memstick work?