Hacking Enso 3.65 accidentally updated to official 3.72

[Rich8606]

So, just turned on my Vita today and suddenly my firmware is updated to 3.72. Weirdly Enso is still installed, the logo at the Vita startup is the Enso logo.

So what do I have to do to downgrade it to Enso 3.65 again?

I used a tutorial on how to downgrade from 3.73 to 3.60 and then install Enso 3.65. Can I use that tutorial again? Will Enso still installed be a problem?

Assuming it's okay, right now I'm updating to 3.73 first.

 

[godreborn]

enso may not be installed technically. I've heard that the screen with the enso logo can still be in memory (maybe it's not updated with a firmware update), but that screen is a product of the vita camera (vitadevwiki).

--------------------- MERGED ---------------------------

here's info on the boot logo: https://wiki.henkaku.xyz/vita/SceDisplay

 

[Rich8606]

So it's okay to just update to 3.73 and redo all those steps to install Enso 3.65?

So what I'm about to do:
1. Vita is now 3.72 (No Enso Chinese characters next to it, but Enso logo at startup)
2. Update to 3.73
3. Downgrade to 3.60 with Modoru
4. Install Enso 3.65

Or, should I uninstall Enso first? So:
1. Vita is now 3.72 (No Enso Chinese characters next to it, but Enso logo at startup)
2. Uninstall Enso
3. Update to 3.73
4. Downgrade to 3.60 with Modoru
5. Install Enso 3.65

 

[godreborn]

tbh, I don't recall actually uninstalling enso when I downgraded from 3.65 to 3.60. I undid the plugins (errors if you don't). it's probably fine as is.

 

[0x3000027E]

So it's okay to just update to 3.73 and redo all those steps to install Enso 3.65?

So what I'm about to do:
1. Vita is now 3.72 (No Enso Chinese characters next to it, but Enso logo at startup)
2. Update to 3.73
3. Downgrade to 3.60 with Modoru
4. Install Enso 3.65

Or, should I uninstall Enso first? So:
1. Vita is now 3.72 (No Enso Chinese characters next to it, but Enso logo at startup)
2. Uninstall Enso
3. Update to 3.73
4. Downgrade to 3.60 with Modoru
5. Install Enso 3.65

Uninstall Enso is not necessary, since the MBR will be reset with update.

 

[Rich8606]

Uninstall Enso is not necessary, since the MBR will be reset with update.

Has it? Even though the Enso logo is still at the startup? So what should I do, update to 3.73 is fine? And then redo the downgrade and install with Modoru and all?

 

[0x3000027E]

Has it? Even though the Enso logo is still at the startup? So what should I do, update to 3.73 is fine? And then redo the downgrade and install with Modoru and all?

I missed that. Yes, update does reset MBR, so the fact that you are seeing Enso logo on 3.72 means this is probably the 'Henkaku bug'. Also, Vita does not spontaneously update without your permission.
Henkaku bug is when the taiHEN config becomes corrupt. The system version becomes your spoofed version, and Henkaku settings disappears. The fix is relatively easy.
What version were you running when this happened?
EDIT: okay, 3.65. You should still have h-ecnore application?

 

[Rich8606]

Hang on, I never set spoofing. Every time I play Helldivers online it sometimes asks me to update my firmware. Also from time to time, Vita actually auto download system updates which I always cancelled. Could a Vita auto download and auto install a firmware? And I think this is Helldivers' doing, since it only updates to 3.72. If it's the system doing it it would have updated to the latest 3.73.

--------------------- MERGED ---------------------------

I missed that. Yes, update does reset MBR, so the fact that you are seeing Enso logo on 3.72 means this is probably the 'Henkaku bug'. Also, Vita does not spontaneously update without your permission.
Henkaku bug is when the taiHEN config becomes corrupt. The system version becomes your spoofed version, and Henkaku settings disappears. The fix is relatively easy.
What version were you running when this happened?
EDIT: okay, 3.65. You should still have h-ecnore application?

Wait, that's a thing? Come to think of it, even if my Vita auto downloaded 3.72, it should have asked me permission to install it, it wouldn't just install it itself.

Is spoofing on by default? And is it set 3.72? If yes and what you said is actually what happens to my Vita, how do I fix it?

 

[0x3000027E]

Hang on, I never set spoofing. Every time I play Helldivers online it sometimes asks me to update my firmware. Also from time to time, Vita actually auto download system updates which I always cancelled. Could a Vita auto download and auto install a firmware? And I think this is Helldivers' doing, since it only updates to 3.72. If it's the system doing it it would have updated to the latest 3.73.

Odd. In any case, you will be fine to update to 3.73 without uninstalling Enso. I would just go that route.

 

[godreborn]

from what I remember, spoofing is not on my default, since the current latest firmware may be different. I think it's tied to the id.dat, because if the id.dat's firmware is higher, the system will try to get you to update when you boot up.

 

[Rich8606]

EDIT: okay, 3.65. You should still have h-ecnore application?

Yep, h-encore, VitaShell, Adrenaline, everything is still installed.

 

[0x3000027E]

Yep, h-encore, VitaShell, Adrenaline, everything is still installed.

Run hencore, (open hencore bootstrap menu) see if you can 'Install Henkaku' then 'reset taiHEN config'.

 

[Rich8606]

Welp, problem solved. I opened Autoplugin and uninstalled all my plug-ins, but then had a change of heart and reinstalled them. Exit out Autoplugin and restarted my Vita twice right? Behold, Enso 3.65, Henkaku settings, everything is back:

And spoofing is on by default, and somehow is set to 3.72, not 3.73?

What exactly happened? Could it be the Henkaku bug like you said?

 

[0x3000027E]

Welp, problem solved. I opened Autoplugin and uninstalled all my plug-ins, but then had a change of heart and reinstalled them. Exit out Autoplugin and restarted my Vita twice right? Behold, Enso 3.65, Henkaku settings, everything is back:View attachment 241420And spoofing is on by default, and somehow is set to 3.72, not 3.73?

What exactly happened? Could it be the Henkaku bug like you said?

Yes, it was Henkaku bug from corrupt taiHEN config. Those operations with Autoplugin must have reset taiHEN config or solved the corruption issue,

 

[Rich8606]

Weird, I didn't uninstall Henkaku though, Autoplugin wouldn't let me. So somehow uninstalling and reinstalling NoNpDrm, PSVShell, VitaGrafix and ioplus fixed my problem? Very weird.

Well, thanks for your help, today I learnt of this Henkaku bug and what do to. Damn, I almost updated to 3.73, started downloading and everything 

 

[godreborn]

you have to update the spoof each time a new update is released. it doesn't move forward automatically. also, I wouldn't use autoplugin. way too many problems others have had with it. just input the plugins manually. it's real easy.

 

[ccfman2004]

Spoofed version has to be updated every time a new firmware is launched.

 

[Rich8606]

you have to update the spoof each time a new update is released. it doesn't move forward automatically. also, I wouldn't use autoplugin. way too many problems others have had with it. just input the plugins manually. it's real easy.

Spoofed version has to be updated every time a new firmware is launched.

But official 3.73 came out in Oct 2019, my Vita was firmware 3.73 long before I installed Enso back in Nov 2020. Why did Henkaku set 3.72 by default and not 3.73? Is my version of Henkaku released before 3.73 or something?

 

[godreborn]

the spoof has nothing to do with what the console was on originally. whatever it's set to by default is probably based on which enso you installed.

 

[Rich8606]

Ah, I see... So Enso 3.65 probably came out during the FW 3.72 time. Say, I read on Reddit, people just set their spoof to 9.99 and it works. Overkill? 3.73 is enough? Sony has declared Vita a legacy console and it's highly unlikely that there will be another FW update.