Usually, there is a pre-amble here. A section to roughly explains what the article you’re reading is about to be about. It’s something more than a headline, something less than a paragraph. Well today, we’re going to breeze over this part because the headline is enough and I’m sure you’re chomping at the bit to find out how to downgrade your up to date Vita. Let’s do it!
Quick History Lesson:
Just this last week TheFloW announced that he had a method of having a CFW running on everyone’s 3.71 Vitas. This meant that you could start up your Vita and put it into a modified state to run homebrews, Vita improvements, Vita backups, PSP backups, etc. This wasn’t a permanent jailbreak as only Vitas up to 3.65 could have that option due to their firmware having keyholes to insert specific exploits. Everyone was very happy about this if they had been too far updated to run Enso on 3.65. We also knew that the last time someone released a CFW to work, Sony didn’t patch it for at least 6 months, so it gave everyone a chance to get the 3.71 CFW exploit installed. However, the very next day, Sony dropped 3.72. This was, at first, believed to have blacklisted the exploit altogether. Later on that night, TheFloW stated in a tweet that someone had told him wrong and that the exploit wasn’t patched. It was then updated to work on 3.72 firmware as well! The only problem is that if you want a permanent CFW instead of the one you have to start every time that you restart your device, a downgrade would be required.
Enter developer SKGleba. He’s the one who has made this newer downgrade possible. Here is what he had to say about the release of his downgrade:
‘Hey guys, I’ve been recently working on a custom lv0 framework. Sony’s update 3.71 broke modoru by adding checks in lv0. So I spent the last few days on get code exec on 3.71-3.72 and porting decsecldr – a loader for decrypted lv0 modules.
One of the advantages it gives is ability to load older/custom lv0 modules, which, you guessed it right, I used to load 3.65 updatesm effectively reverting the changes made in 3.71. The injector is not really stable (may take a few tries), but the loader itself is.’
What You Need:
- Download the tool needed.
- Download 3.72 OFW file (if you’re on 3.72 currently), rename it to PSP2UPDAT.PUP if it isn’t already.
- Download 3.71 OFW file (if you’re on 3.71 currently), rename it to PSP2UPDAT.PUP if it isn’t already.
- Download full 3.65 OFW file, rename it to PSP2UPDAT.PUP if it isn’t already.
- Download decrpyted 3.65 OFW file.
- Download current Modoru CFW.
Instructions (This assumes you know how to use Modoru on 3.71/3.72 already):
- Install the VPK files from your download using Vita Shell.
- Copy full 3.65 download to ux0:app/MODORU000/PSP2UPDAT.PUP
- Now, copy 3.72 PUP (or 3.71 PUP if that is the firmware you’re currently running) to ux0:data/PSP2/UPDATE/PSP2UPDAT.PUP
- Copy the update_sm.bin (decrypted 3.65 OFW you downloaded) to ux0:data/update_sm.bin.
- Power off your device, then turn it back on.
- Next, you’ll go ahead and enable homebrew with h-encore2.
- Start up decsecldr[LITE] then wait patiently. Once it says “module loaded” you can press Start to leave the app. (NOTE:It could crash or hang for longer than 15 seconds. If it does, just hold down the power button until the console turns off. It could happen more than once, just be diligent, it will eventually work. If you have to power cycle the system like this, simply pick back up from step 7.)
- Now once the app has successfully loaded the module and you have exited out to the main screen, you just need to start up the Modoru app.
- Next, follow all of the on-screen prompts for Modoru and once it’s done, you’re golden! That’s all there is to it!
- Then, once downgraded to 3.65, simply follow our guide for installing Enso on it!