PS VITA / PsTV Help After Updating Enso

LuanTeles

LuanTeles

Developer
PSX-Place Supporter
I brought my ps vita already hacked in version v.3.65

So today i was trying to install CBS-Manager v3.0 and it askes for boot_conf.txt that i read is available in lastest Enso, and its github says to install lastest one

https://github.com/TheOfficialFloW/enso/releases/tag/v1.1

So i installed, the vita restarted fine, but now it prompts YOU MUST UPDATE YOUR SYSTEM, and i hit cancell, and other prompt pops up TO USE THIS MEMORY CARD YOU NEED TO FORMAT IT OR UPDATE THE SYSTEM. and i hit cancel.

So it booted fine, but i can't acess the mememory card, and i dont have any henkaku options in the System Settings.

But the henkaku is there since the molecule boot image is there, and all my plugins still loaded since it is intalled in the INTERNAL partition, with some APPS LIKE VITASHELL ( but i cant acess usb mode) says error


how can i fix it to normall?
 
Last edited:
the boot_config.txt and henkaku.suprx (henkaku settings) are located in vs0:tai. you no longer need henkaku.suprx in ur0. I think it will cause a rebuild of the database if you copy it. I have tried that to see what would happen. it's hardcoded now, so it ignores its entries in the config.txt, stating that it's located in ur0.

if you're going to update enso, you need to uninstall it first or the checksum will come out wrong during reinstallation. it will still install correctly, but it will give you that warning.

if plugins work, I think the boot_config.txt is being read. however, if you were to uninstall enso, you'd need to reinstall ofw to get rid of the boot logo, so that might appear even if enso isn't installed.

if what you installed relates to enso ex, I'd suggest uninstalling it or installing ofw through the recovery menu, then reinstalling regular enso. a lot of people have had problems with ex, and I think some people install it to prevent updates. you can prevent updates with update block (the one from silica and pina), spoofing, disabling the option in system settings, or dns. I wouldn't rely on just the system settings option, because it's been known not to work correctly.
 
Yes, the truth is that I was testing it and I had problems formatting the psvita and the memory card because it detected the main one as uma0 and the sd2vita as ux0 until I realized and very rare things happened I finally left it with a enso 1.1 to 3.65. That's why I say that CBS Manager is for ensoex and is not compatible with normal ensoex. Regards
 
I don't know what cbs manager is nor have I tried enso ex, but from what I've heard, enso ex can lead to bricks if you don't do things exactly right. it's not worth the risk.
 
pinky said:
the boot_config.txt and henkaku.suprx (henkaku settings) are located in vs0:tai. you no longer need henkaku.suprx in ur0. I think it will cause a rebuild of the database if you copy it. I have tried that to see what would happen. it's hardcoded now, so it ignores its entries in the config.txt, stating that it's located in ur0.

if you're going to update enso, you need to uninstall it first or the checksum will come out wrong during reinstallation. it will still install correctly, but it will give you that warning.

if plugins work, I think the boot_config.txt is being read. however, if you were to uninstall enso, you'd need to reinstall ofw to get rid of the boot logo, so that might appear even if enso isn't installed.

if what you installed relates to enso ex, I'd suggest uninstalling it or installing ofw through the recovery menu, then reinstalling regular enso. a lot of people have had problems with ex, and I think some people install it to prevent updates. you can prevent updates with update block (the one from silica and pina), spoofing, disabling the option in system settings, or dns. I wouldn't rely on just the system settings option, because it's been known not to work correctly.
Click to expand...

But since i can lanch homebrews like vita shell doesnt mean it is already jailbroken?

and when the henkaku options to spoof was available i set it to 3.73 and it still show as it
 
Last edited:
I don't know how you wear it. If you had ensoex installed, you had to uncheck it before formatting if it did not loop and the card would not be formatted if you had sd2vita configured. But what I would do would be that. Uninstall enso and do the exploit again and if it doesn't let you it can update using ps3 to 3.73 and download with modoru.
 
I installed Card Unlocker via FTF in the Vita Shell and unlocked it

But how to install enso again? the internal apps works but the ones in the memory card says to insert tge PS VITA cart that contains it

I never did it before

I read that only needs to install enso.vpk as i did, but where is my henkaku settings and etc?
 
Last edited:
if something is wrong with the plugins, you can create a new config.txt on ux0, then move it to ur0. ux0 supersedes ur0 for this very reason.

if you mean what I think you do, all you have to do to unlock the card for another system is delete the id.dat. it contains your account and system information, and it will be recreated at next boot, so there's no risk.
 
when I bought the psvita it had the H encore app too, but since it is permanent it is enso right?
 
pinky said:
if something is wrong with the plugins, you can create a new config.txt on ux0, then move it to ur0. ux0 supersedes ur0 for this very reason.

if you mean what I think you do, all you have to do to unlock the card for another system is delete the id.dat. it contains your account and system information, and it will be recreated at next boot, so there's no risk.
Click to expand...

Yeap the app unlock card deletes the id.dat , now it workes good. the problem now is no henkaku settings.
 
LuanTeles said:
Yeap the app unlock card deletes the id.dat , now it workes good. the problem now is no henkaku settings and i can't launch homebrews in the UX0 only the ones i moved to UR0
Click to expand...

I'd suggest uninstalling enso and starting over. it seems like any attempt to rectify the problem is closed up since you can't access any homebrew. you could try qcma, but it needs a working account on the system.
 
Okay tell me firmware version, if you have sd2vita and in settings / system / system information what memory is being detected and if you have the spoof at 3.73 activated because you still don't need to format anything.
 
pinky said:
if it's permanent, you have enso.
Click to expand...

I installed the enso again, still not henkaku in settings damn, but i checked the plugins folder , it have two henkaku.sprx and henkaku.suprx

but they aren't in the config.txt and never were. if i add the sprx maybe it work?
 
mr_ota said:
Okay tell me firmware version, if you have sd2vita and in settings / system / system information what memory is being detected and if you have the spoof at 3.73 activated because you still don't need to format anything.
Click to expand...


I think i'm on 3.65 =P
but the system information shows the spoofed one 3.73.

I'm using a legit PS Vita memory card.
 
I think the difference might be between 3.60 and 3.65 enso. I don't believe henkaku.suprx is hardcoded in 3.60, but I could be wrong. right now, I'm on 3.65 enso, so it's been a long time. don't put the skprx in the tai folder. leave it alone. it's hard coded on both versions. I don't think the suprx is, so maybe try copying (not moving) it in there. leave it on ux0 for now just as a test that can be corrected if something doesn't work. both the suprx and skprx are in vs0:tai (at least on 3.65). I once had no henkaku settings as well (think back on 3.60), so I just copied the henkaku.suprx from the app folder and they reappeared. that's another place that it'll be on ux0 (i.e. ux0:app/title id). I don't remember if it's in molecular shell or the enso folder, but it should be in at least one of them. here's my molecular shell:
upload_2019-10-23_13-56-56.png
 
ok then if you have just installed just reinstall it and check that it leaves you if you don't see henkaku / reset taihen txt settings / settings so psvita will restart and you will have it with the plugins disabled so you can do it individually later.
 
You must log in or register to reply here.

Similar threads

Back
Top