Hacking Screwed up installing Enso EX

kotoar · May 23, 2019

kaymynd said:
Yes just install henkaku in 2nd vita or if you have a alim vita or pstv you can use the internal memory, just i stal emso and i believe you can just plug card in and use the unlonk mem card option in henkaku settings or the cardunlock app i mentioned above.

i have a strange problem because at first the vita wouldn't recognize the memory card, but after a while after i set up the sd2vita on my pc and copied the file that were made by the Qcma on my pc to the sd2vita and put it in the vita and it recognised it and i was able to copy the h-encore to the system, and launch it, install vitashell, app manager and cardunlock.
if fact the enso_ex put the sd2vita as the ux0, so when i insert the memory card cardunlock can't mount it (is there a way to change sd2vita directory?) and if i launch the normal enso, will it overwrite the enso_ex an in turn disable the sd2vita ? thank you for your help.. i only have one vita for the moment

kaymynd · May 23, 2019

kotoar said:
i have a strange problem because at first the vita wouldn't recognize the memory card, but after a while after i set up the sd2vita on my pc and copied the file that were made by the Qcma on my pc to the sd2vita and put it in the vita and it recognised it and i was able to copy the h-encore to the system, and launch it, install vitashell, app manager and cardunlock.
if fact the enso_ex put the sd2vita as the ux0, so when i insert the memory card cardunlock can't mount it (is there a way to change sd2vita directory?) and if i launch the normal enso, will it overwrite the enso_ex an in turn disable the sd2vita ? thank you for your help.. i only have one vita for the moment

Ok first make sure you have enso installed, once dond if you can access vitashell you're good to go first you do need to move the cardunlock app to ur0 partition using the app manager plus i linked above, once cardunlock is in ur0 you're ready for the next step,

Go into vitashell and into ur0:tai folder you should have storagemgr.skprx or gamesd.skprx delete whichever one you have, and there should also be a config.txt file there, open it up and delete the storagemgr/gamesd line by highlighting it with square and then hitting delete in the menu opened by triangle, then reboot and maybe your sony mem card will boot but if it still gives you the format loop, turn off your vita, remove the sd2vita adapter and sony mem card. Turn vita back on and if you installed enso correctly cardunlock will still be on the livearea and will still run, open up cardunlock and then insert mem card while cardunlock is open and follow the directions in the app, just what ever you do whenever it asks you any dialog ALWAYS select no if you press yes ypu run the risk of formatting your mem card and having to start all over.

kotoar · May 23, 2019

kaymynd said:
Ok first make sure you have enso installed, once dond if you can access vitashell you're good to go first you do need to move the cardunlock app to ur0 partition using the app manager plus i linked above, once cardunlock is in ur0 you're ready for the next step,

Go into vitashell and into ur0:tai folder you should have storagemgr.skprx or gamesd.skprx delete whichever one you have, and there should also be a config.txt file there, open it up and delete the storagemgr/gamesd line by highlighting it with square and then hitting delete in the menu opened by triangle, then reboot and maybe your sony mem card will boot but if it still gives you the format loop, turn off your vita, remove the sd2vita adapter and sony mem card. Turn vita back on and if you installed enso correctly cardunlock will still be on the livearea and will still run, open up cardunlock and then insert mem card while cardunlock is open and follow the directions in the app, just what ever you do whenever it asks you any dialog ALWAYS select no if you press yes ypu run the risk of formatting your mem card and having to start all over.

i should launch enso on top of the existing enso_ex? and can i move h-encore to ur0/ is it possible? thank you

kaymynd · May 24, 2019

kotoar said:
i should launch enso on top of the existimg enso_ex?

If you're already using enso_ex and it hasn't given you any problems you should be good using that instead. Just follow what i said in my last post with enso_ex, I recommend ppl use regular enso though, just because enso_ex has given many ppl problems.

I don't think you can move h-encore to ur0 i tried once but it just gave me an error when i tried to launch it so i moved it back to ux0 the only apps that have ever worked for me on ur0 has been cardunlock and vitashell i keep em there to this day just in case i ever get locked out of my mem card again

godreborn · May 24, 2019

you may not have changed ux0 to ur0 in the app.db. I don't know if you can store apps or games in that partition, but that's a way to know.

kaymynd · May 24, 2019

godreborn said:
you may not have changed ux0 to ur0 in the app.db. I don't know if you can store apps or games in that partition, but that's a way to know.

Interesting! I wasn't aware of this, not sure if editing the app.db entry to point to ur0 is all that's needed, but I'll experiment with it later on today, try to see if i can get h-encore to run on ur0.

duwen · May 24, 2019

I have a similar issue as detailed by OP... Installed Trinity, downgraded to 3.60 with Modoru, exploited via henkaku.xyz and then enso'd with Enso Ex... main difference between my install and OP's is that everything seems to be working as expected (SD2Vita runs perfectly as ux0, and when not inserted I still have enso)...
It's at this stage I'll point out that this is on a PSTV. My issue is that Enso Ex seems to have completely removed/lost the 1Gb of internal storage, and the bootable 'internal os' instead seems to be on the protected 1.5Gb, so all the apps I'd added to my internal 1Gb before running enso ex are gone (no molecular/vita shell etc).
Using the henkaku 'unlink card' option just gives an error (and even if it worked, it's a PSTV so I can't physically remove the card).
When opening vitashell via sd2vita (which is my ux0) the 1Gb internal partition (that was my ur0 prior to enso ex, current ur0 is 1.5Gb) is completely missing.
I injected vitashell into an app so that I could inspect via the 'os' on my ur0, but that too shows no 1Gb partition.
Because the 1.5Gb partition is presumably protected space I cannot install/copy/move any homebrew other than the injected vitashell.

Like I said, sd2vita is working fine - everything else is fine, so it's not a major issue just an annoyance.
I'd like that internal storage back, mainly so I can keep dlc for my physical carts installed and still be able to swap out my sd2vita to play those legit cards.
But the biggest concern is that without that accessable internal storage a risk of bricking is way more likely.

Any suggestions?
Would the tip posted about deleting storagemgr.skprx or gamesd.skprx likely restore my missing internal storage?

kaymynd · May 24, 2019

duwen said:
I have a similar issue as detailed by OP... Installed Trinity, downgraded to 3.60 with Modoru, exploited via henkaku.xyz and then enso'd with Enso Ex... main difference between my install and OP's is that everything seems to be working as expected (SD2Vita runs perfectly as ux0, and when not inserted I still have enso)...
It's at this stage I'll point out that this is on a PSTV. My issue is that Enso Ex seems to have completely removed/lost the 1Gb of internal storage, and the bootable 'internal os' instead seems to be on the protected 1.5Gb, so all the apps I'd added to my internal 1Gb before running enso ex are gone (no molecular/vita shell etc).
Using the henkaku 'unlink card' option just gives an error (and even if it worked, it's a PSTV so I can't physically remove the card).
When opening vitashell via sd2vita (which is my ux0) the 1Gb internal partition (that was my ur0 prior to enso ex, current ur0 is 1.5Gb) is completely missing.
I injected vitashell into an app so that I could inspect via the 'os' on my ur0, but that too shows no 1Gb partition.
Because the 1.5Gb partition is presumably protected space I cannot install/copy/move any homebrew other than the injected vitashell.

Like I said, sd2vita is working fine - everything else is fine, so it's not a major issue just an annoyance.
I'd like that internal storage back, mainly so I can keep dlc for my physical carts installed and still be able to swap out my sd2vita to play those legit cards.
But the biggest concern is that without that accessable internal storage a risk of bricking is way more likely.

Any suggestions?
Would the tip posted about deleting storagemgr.skprx or gamesd.skprx likely restore my missing internal storage?

This is normal, once you start using a sony mem card or sd2vita the internal mem will become part of ur0 if i recall correctly, I'm not 100% sure but i think you can just switch the partitions around if using storagemgr and your internal mem will pop back up as ux0 i think. In storagemgr there is an option for internal mem you can set it as ux0, uma0 or whatever you like.

CTR640 · May 25, 2019

Why is it a lot of people using Enso_Ex? And how is it it's not noob-proof?

This is the main reason why I'd like to use h-encore. Of course there is the regular enso but I have no reason for that.
If something works, don't change anything.

duwen · May 25, 2019

kaymynd said:
This is normal, once you start using a sony mem card or sd2vita the internal mem will become part of ur0 if i recall correctly, I'm not 100% sure but i think you can just switch the partitions around if using storagemgr and your internal mem will pop back up as ux0 i think. In storagemgr there is an option for internal mem you can set it as ux0, uma0 or whatever you like.

Ok - it just seemed odd to me that if I boot without the sd2vita card the ur0 (internal storage) has lost all previously installed apps (which included molecular shell, vhbb, antiblacklist, etc) as well as the enso installer which means I can't change or uninstall enso from the 'base' ur0 install.
It was also alarming to see that the 1Gb internal storage had vanished - prior to enso ex I had both a 1.5Gb and 1Gb showing up through vitashell, with all previous installations being on that 1Gb, now it just shows the 1.5Gb.
I should also point out that enso ex made these changes when installed without sd2vita ever having been used in the PSTV (I just happen to have one in my 1000 that I could use to get me out of trouble). If I didn't have that sd2vita I'd have been left with an enso enabled henkaku PSTV with no way of getting any apps on it or any access to shell.

CTR640 said:
Why is it a lot of people using Enso_Ex? And how is it it's not noob-proof?

The installer is no less 'noob-proof' than the official enso installers, it just seems to be prone to a lot of glitches.
I've got both the 3.60 and 3.65 legit installers as well as ex. When I came to downgrade my PSTV with modoru I was unsure what it's base firmware would be (so I had update dats for both 3.60 and 3.65 on standby)... using ex was just (in hindsight) a dumb time saving move as it would work with both 3.60 and 3.65.

kaymynd · May 25, 2019

CTR640 said:
Why is it a lot of people using Enso_Ex? And how is it it's not noob-proof?

This is the main reason why I'd like to use h-encore. Of course there is the regular enso but I have no reason for that.
If something works, don't change anything.

Enso_ex just has alot more features whereas in regular enso simply makes henkaku/h-encore permanent and you have to manually install the other features afterwards so i think that's why alot more ppl are using it.
I used regular enso before enso_ex was released and saw no real reason to switch over. It's like duwen says it's not less noob friendly but i think ppl who are just getting into hacking their vitas/pstv and don't yet know very well how everything works are running into issues with it installing everything at once, so that's why i reccomend anyone new into vita/pstv hacking should just use regular enso and install everything manually afterwards, this way they learn how everything works too. Users that know how it all works can go ahead and use enso_ex since they probably won't run into any problems with it.

duwen said:
Ok - it just seemed odd to me that if I boot without the sd2vita card the ur0 (internal storage) has lost all previously installed apps (which included molecular shell, vhbb, antiblacklist, etc) as well as the enso installer which means I can't change or uninstall enso from the 'base' ur0 install.
It was also alarming to see that the 1Gb internal storage had vanished - prior to enso ex I had both a 1.5Gb and 1Gb showing up through vitashell, with all previous installations being on that 1Gb, now it just shows the 1.5Gb.
I should also point out that enso ex made these changes when installed without sd2vita ever having been used in the PSTV (I just happen to have one in my 1000 that I could use to get me out of trouble). If I didn't have that sd2vita I'd have been left with an enso enabled henkaku PSTV with no way of getting any apps on it or any access to shell.

The internal may be named uma0 due to the sd2vita plugin, check to see if you have this folder and look at it's size.

If using storagemgr you need to switch the partitions before you reboot or if using gamesd you need to disable/delete it. This will put internal mem back to ux0 and everything should still be there, the only way i know it gets deleted is if you insert a sony mem card.

duwen · May 25, 2019

kaymynd said:
The internal may be named uma0 due to the sd2vita plugin, check to see if you have this folder and look at it's size.

If using storagemgr you need to switch the partitions before you reboot or if using gamesd you need to disable/delete it. This will put internal mem back to ux0 and everything should still be there, the only way i know it gets deleted is if you insert a sony mem card.

Like I said, enso_ex has completely "hidden" the internal 1Gb of storage, and did so without sd2vita having been used on my PSTV - thus storagemgr was never installed. Prior to enso vitashell correctly showed the 1Gb internal as well as the 1.5Gb "protected" internal, now it just shows the 1.5Gb as ur0. I've tried to copy apps to the 1.5Gb but none of them show up on the homescreen when booting without sd2vita installed (leading me to believe that the partition is still somewhat protected, despite actually being able to copy to it. The only exception being using HBI, via sd2vita, to inject vitashell into the email app).
I'll see if adding storagemgr lets me reconfigure boot options, but as the 1Gb space doesn't even show up I'm skeptical.

kaymynd · May 25, 2019

duwen said:
Like I said, enso_ex has completely "hidden" the internal 1Gb of storage, and did so without sd2vita having been used on my PSTV - thus storagemgr was never installed. Prior to enso vitashell correctly showed the 1Gb internal as well as the 1.5Gb "protected" internal, now it just shows the 1.5Gb as ur0. I've tried to copy apps to the 1.5Gb but none of them show up on the homescreen when booting without sd2vita installed (leading me to believe that the partition is still somewhat protected, despite actually being able to copy to it. The only exception being using HBI, via sd2vita, to inject vitashell into the email app).
I'll see if adding storagemgr lets me reconfigure boot options, but as the 1Gb space doesn't even show up I'm skeptical.

Enso_ex installs a sd2vita driver either storagemgr or gamesd unless you chose not to install it, but it is one of it's features.
The only thing in ur0 you need to worry about is it's tai folder don't copy anything onto here it is not for the live area and has always been there, for vitashell (if you want you can use app manager plus to move vitashell to ur0 partition so it will load even without mem card or in this case internal mem, but you need to go into ur0:tai and delete gamesd.skprx or storagemgr.skprx whichever one is there, then go into config.txt folder and delete the line with gamesd or storagemgr, whichever one is there, this should return it to normal with everything still there.

duwen · May 25, 2019

kaymynd said:
Enso_ex installs a sd2vita driver either storagemgr or gamesd unless you chose not to install it, but it is one of it's features.
The only thing in ur0 you need to worry about is it's tai folder don't copy anything onto here it is not for the live area and has always been there, for vitashell (if you want you can use app manager plus to move vitashell to ur0 partition so it will load even without mem card or in this case internal mem, but you need to go into ur0:tai and delete gamesd.skprx or storagemgr.skprx whichever one is there, then go into config.txt folder and delete the line with gamesd or storagemgr, whichever one is there, this should return it to normal with everything still there.

Niether storagemgr or gamesd were in the tai folder, and there was no corresponding text in the config.txt.

...but I now have a bigger problem; I just created a duplicate config.txt, renamed the original, added storagemgr to tai (and storage_config text) and corresponding line to the new config.txt, and now the PSTV won't boot up. I get the safe mode boot screen, but restart and rebuild just hangs the system. What are my options?
What will 'Restore System' do? I'm okay with re-installing henkaku (especially if I get my 1Gb of internal back, and can correctly install legit, non-ex, enso), I just don't want to run the risk of bricking it... or bricking it more than it currently is.

kaymynd · May 25, 2019

duwen said:
Niether storagemgr or gamesd are in the tai folder, and there's no corresponding text on the config.txt.

...but I now have a bigger problem; I just created a duplicate config.txt, renamed the original, added storagemgr to tai and corresponding line to the config.txt, and now the PSTV won't boot up. I get the safe mode boot screen, but restart just hangs the system. What are my options?

Really? That's strange? how did you have sd2vita working then? It requires either storagemgr or gamesd to work.

And on vita you hold L while booting to load with plugins disabled, I'm not sure how to do it on pstv though sorry,

You need to also add storage_config.txt and set it however you want this is probably why it's not booting

In ur0:tai/config.txt after *KERNEL create a new line and write: ur0:tai/storagemgr.skprx

Configure ur0:tai/storage_config.txt to what you want.

The available devices are :

MCD : official SONY memory card

INT : internal memory 1GB (on all PSVita SLIM and PSTV)

GCD : microSD inserted into SD2VITA (also called gamecard2sd)

UMA : USB mass (for PSTV) OR microSD inserted into PSVSD (for PSVita 3G)

The available mount points are :

ux0

xmc0

imc0

uma0

grw0

As long as you can access safe mode you can also reinstall firmware or update through qcma and start all over.

wownmnpare · May 25, 2019

Why did you go to EX? You're already in the golden enso state.

duwen · May 25, 2019

kaymynd said:
Really? That's strange? how did you have sd2vita working then? It requires either storagemgr or gamesd to work.

And on vita you hold L while booting to load with plugins disabled, I'm not sure how to do it on pstv though sorry,

You need to also add storage_config.txt and set it however you want this is probably why it's not booting

In ur0:tai/config.txt after *KERNEL create a new line and write: ur0:tai/storagemgr.skprx

Configure ur0:tai/storage_config.txt to what you want.

The available devices are :

MCD : official SONY memory card

INT : internal memory 1GB (on all PSVita SLIM and PSTV)

GCD : microSD inserted into SD2VITA (also called gamecard2sd)

UMA : USB mass (for PSTV) OR microSD inserted into PSVSD (for PSVita 3G)

The available mount points are :

ux0

xmc0

imc0

uma0

grw0

I've got no idea how it was loading sd2vita without the plugins, I'd guess that enso_ex implements it differently somehow.
I edited more details into my last post - note; I did configure the storage_config.txt (I'm proficient with it from using it on my 1000).
I've now got no access to the system config, being stuck at the safe mode screen no matter what I try.
I just reformatted the internal memory, so the only 2 options left from safe mode are Restore and Update.

I need to reinstall henkaku on my 1000, but when that's done I can unlock and use its 4Gb memcard on my PSTV to hopefully reboot the PSTV, but tbh I'd rather start fresh with it. Enso wasn't uninstalled, so would "Restore" be likely to brick the system?

kaymynd · May 25, 2019

duwen said:
I've got no idea how it was loading sd2vita without the plugins, I'd guess that enso_ex implements it differently somehow.
I edited more details into my last post - note; I did configure the storage_config.txt (I'm proficient with it from using it on my 1000).
I've now got no access to the system config, being stuck at the safe mode screen no matter what I try.
I just reformatted the internal memory, so the only 2 options left from safe mode are Restore and Update.

I need to reinstall henkaku on my 1000, but when that's done I can unlock and use its 4Gb memcard on my PSTV to hopefully reboot the PSTV, but tbh I'd rather start fresh with it. Enso wasn't uninstalled, so would "Restore" be likely to brick the system?

I see i really don't know what to say I've never been in this situation before. As it is right now i don't know if it will brick or not, but i do know that restore doesn't remove enso, only a firmware reinstall or up/downgrade

So i do recommend you use the sony mem card to try and restore since using the mem card should remove the internal 1gb anyway, then i recommend reinstalling or updating/downgrading firmware and starting all over.

duwen · May 25, 2019

kaymynd said:
I see i really don't know what to say I've never been in this situation before. As it is right now i don't know if it will brick or not, but i do know that restore doesn't remove enso, only a firmware reinstall or up/downgrade

So i do recommend you use the sony mem card to try and restore since using the mem card should remove the internal 1gb anyway, then i recommend reinstalling or updating/downgrading firmware and starting all over.

Thanks for the help. I'll let you know how I get on.

edit

@kaymynd So, I just risked running "Restore System" and it seems to have worked without bricking. However, it was reporting being on 3.65 which seems odd considering I went from 3.70 Trinity directly to 3.60 via modoru and was spoofing as 3.70.
More concerning is that the internal memory was still stating to be 0Gb, so restoring/reformatting didn't reinstate the internal storage that enso_ex had hidden.

The henaku menu in settings was unsurprisingly not showing, but weirdly I could still access vitashell that I'd previously injected into the email app... although I don't think it would've been particularly useful to me - it wasn't showing sizes for any of the displayed locations, and the tai folder in ur0 was completely empty.

I just tried a system restore from the system memory, which asked if I wanted to also reformat the internal 1Gb, which I did, but after getting back to the homescreen content manager it was still stating 0Gb storage.

...so, I've re-updated to 3.70 and have now got my 1Gb internal back!
I've got backups of all my Trinity stuff, so it shouldn't take too long to get myself back to a proper enso.

2nd edit

Fixed everything now: Back on a 3.60 enso install, with sd2vita as ux0, internal 1Gb as imc0, and 1.5Gb system storage as ur0.

Thanks again for the help, and hopefully this thread may prove useful to others in the future.
I'd definitely advise against using enso_ex, especially on Vita models utilising internal storage.

kotoar · May 25, 2019

could someone point to a tutorial to a clean start? un-hacking the ps vita/ thank you

Hacking Screwed up installing Enso EX

New Member

Well-Known Member

New Member

Well-Known Member

Welcome to the Machine

Well-Known Member

Old Man Toad

Well-Known Member

Well-Known Member

Old Man Toad

Well-Known Member

Old Man Toad

Well-Known Member

Old Man Toad

Well-Known Member

Well-Known Member

Old Man Toad

Well-Known Member

Old Man Toad

New Member

Similar threads

Popular threads in this forum