Enso 3.60 Issue - Can I change to Enso 3.65

[trash116]

Hi,
Hope somebody can give me some help please.

I have an OLED vita running on Enso 3.60 with a 128GB micro-SD & SD2Vita - everything was working perfectly.

I then followed a TechJames video on how to stream to PC - I've got totally lost and think I've somehow messed up the vita.

When I try to power it up, the Enso logo appears, then the warning message - but then the vita won't boot up it turns off.

The vita will boot up in safe mode with the mods deactivated.

I'm really stuck - could anybody help.

Somebody has told me the solution would be to move to Enso 3.65 - but i have no idea if that is the best solution, if there are any risks, or basically how to do it ?

Could somebody help me...

Thank you so much

 

[pinky]

you could try it, but I doubt it's going to make a difference. that sounds like a hardware problem. if not, remove the sd2vita, then do a system restore. it will delete your account, but it will also rebuild the boot_plugin.txt, which might be the problem.

 

[Berion]

Boot Vita into Enso recovery mode where it ignoring plugins index. Then run VitaShell or something by which You can edit "ur0:/tai/config.txt" and remove everything from all categories, leaving only "ur0:tai/henkaku.suprx" under *MAIN and two system applications.

This is the default config.txt (do NOT mislead it with boot_config.txt... if You do, You will got PERM brick):

*KERNEL

*main
ur0:tai/henkaku.suprx

*NPXS10015
ur0:tai/henkaku.suprx

*NPXS10016
ur0:tai/henkaku.suprx

*all

Upgrading to newer Enso will not help You in anything if config stay the same...

Anyway, 3.60 is the best firmware.

 

[pinky]

you can put a config in ux0/tai. it will override ur0/tai. it's meant to fix errors if ur0/tai has a problem. I suggested on temp he try booting up with the L button held. this will disable plugins.

 

[pinky]

btw, corrupting the boot_plugins.txt won't perm brick the system. it's only a soft brick. in the file itself, it says to fix it is to restore factory defaults. since there is no separate option for that, you have to do system restore. it might format the sd2vita, so don't leave that plugged in. it's a fairly seamless fix.

edit: that was my suggestion to someone who somehow had his boot_plugin.txt corrupted when installing yamt, which makes changes to the file. here's what it says in the boot_plugins.txt:

"# WARNING: DO NOT EDIT THIS FILE. IF YOU JUST WANT TO RUN A PLUGIN ON BOOT,
# EDIT ux0:tai/config.txt INSTEAD. IF YOU BREAK THIS FILE, YOUR VITA WILL NO
# LONGER BOOT. IF THAT HAPPENS, YOU CAN ENTER SAFE MODE AND RESET ALL SETTINGS
# TO RESET THIS FILE. THIS FILE IS UNIQUE TO EACH VITA MODEL. DO NOT BLINDLY
# USE SOMEONE ELSE'S CONFIG."