Hacking does anyone know why 3.65enso will disable after restore system

[paulzheng]

does anyone know why 3.65enso will disable after restore system

enso can be made your vita permanently hacked is as known to everyone. my vita is 3.65henkaku enso as well, even if i format it or switch another psn account. the enso is activation as before.
but some guy said that his vita is 3.65henkaku enso. but it will disable after restore system.

his vita's hacking procedure is as follows
1: resign h-encore with his psn account. then upload it into memorycard via qcma.
2: open h-encore hacking . after that download enso.vpk from theofficialflow's and installation as usual.
the problem is vita's opening logo display enso symbol but the system information is 3.65 henkaku without "O"
actually this vita needn't to run h-encore after reboot. all games and apps can working well. it means henkaku is taking effect.

it's so weird that if this vita restore system. the henkaku is disable working. it become 3.65 OFW . luckily. this guy backup h-encore in another official memorycard and delete id.dat as well. so replace this MC could hacking rapidly without login PSN and via qcma.

i was curious about it and had compared with 2 different vita's root files between 3.65henkaku enso and 3.68henkaku.
it's amazing that there is a "tai" folder include hacking files under vs0's partition device in 3.65henkaku enso. but that guy's 3.65henkaku enso not be found. it's the same as 3.68henkaku
so i assume that is the reason why his vita's 3.65enso couldn't be working after restore system but mine is good .

does anyone can explain or solve this problem?
i am not sure whether i could copy this folder to another vita's vs0 will not make it be brick.

 

[Deleted member 424658]

it's amazing that there is a "tai" folder include hacking files under vs0's partition device in 3.65henkaku enso. but that guy's 3.65henkaku enso not be found. it's the same as 3.68henkaku
so i assume that is the reason why his vita's 3.65enso couldn't be working after restore system but mine is good

You have update365 Enso (puts henkaku files in vs0) while the other guy has normal Enso for 3.65 (puts henkaku files in ur0)

 

[paulzheng]

You have update365 Enso (puts henkaku files in vs0) while the other guy has normal Enso for 3.65 (puts henkaku files in ur0)

exactly. that's ture but i want to know how to put henkaku files in vs0 with normal enso for 3.65 ? is it be possible or not
i couldn't find out what's different between them online

 

[Deleted member 424658]

exactly. that's ture but i want to know how to put henkaku files in vs0 with normal enso for 3.65 ? is it be possible or not
i couldn't find out what's different between them online

update365 Enso is coded specifically to read from vs0, normal Enso will only read files from ur0. You can always just use the installer to get update365 installed (I did this last week) but it's not recommended.

 

[paulzheng]

update365 Enso is coded specifically to read from vs0, normal Enso will only read files from ur0. You can always just use the installer to get update365 installed (I did this last week) but it's not recommended.

wow. install updater365 in 3.65henkaku. you have tried it last week is successful. it not recommended it means could be brick possilble right?

vs0's file will not be wiped after factory reset. but it must be used special license support. i will not try it for brick risk except tech guys guide us.