Psp 3.52 updater

And remember that savedata of 3. Some of the files of this update are protected by encryption schemes to protect ourselves from that page that annoys homebrew developers. The keys for the decryption: the own update file. So if the file is changed, the decrypted data is not the original one, and this causes the wrong data to be written.

There is no way you can call this malicious code as there is no explicit code to brick nothing, it is the corruption of the update what actually causes the bad decrypted data to be written.

Anyways in this update we check if decrypted data is wrong and in that case we write a recovery warning the user what happened. It will activate usb, and it will allow you to execute a recovery eboot. If you visited ps3news and bricked in last release, then blame his administrator. He is the one that modified the files and had them in the server for lots of hours knowing the consequences.

Sit and enjoy while Sony code installs 3. DO IT. Do not skip this step shutting down the psp by yourself, or you'll end with a brick. PBP, PBP and PBP names. PBP will be used for unbricker, so don't delete it. If you have 1. Otherwise, use corly tool. Battery and ms will work on all psp and slims to this date. Unbricking: - Press X to install 3. When done, psp will auto shutdown. If you are working with a dump that isn't yours, you will get either a brick or a corrupt idstorage, depending on the firmware.

If while you are restoring your psp have got any damaged block more than when you dumped it, you might also get a brick, depending on what block is it. Last edited: Feb 21, ONE question Will I need it for anything?

Thank you very much for this easy instruction. AKqZ , Oct 4, PBP, but it came up Corrupted Data.