Hacking 3.60 Enso half-installed?

Henrico · Apr 6, 2020

Hi!

New to the forums, not new to PS hacking but this problem is something I can't really get my head around. I'll try to explain.

I have three different Vitas at the moment. One is mine, we can call that Alpha. One is my brother's, we can call that Beta. I also recently bought one for my gf, let's call that one Gamma.

Original setup:
Alpha: 16 GB Vita memcard. 3.65 h-encore non-permanent install.
Beta: 8 GB Vita memcard. 3.60 Enso permanent install.
Gamma: 4GB Vita memcard and a 32 GB Sandisk SD2Vita. 3.60 Enso permanent install.

First, I did the switcheroos of all memory cards so that Alpha would be the top one, with the 32 GB sd2vita and the 4 GB memstick. The other ones would be kicked up a notch so that the Beta would get 16 and the Gamma would get the 8. Went fine enough, some trouble with the Alpha and sd2vita first-time installations but nothing I can't handle. Let's forget about that one for now. The Beta went smoothly, he got his 16 from me by backing up his 8 with QCMA and installing everything onto his new 16 after that. Savefiles were rescued using Savegr beforehand.

What I'm having trouble with is the Gamma one, with the now-8 GB card and a 3.60 firmware. I did what I did with the others regarding QCMA and backups and such, but before installing any backup or anything else I reset it to system settings and formatted the 8 card.

I might have missed some steps in my description but I am stuck in a situation where the Gamma starts up with the Molecular Shell startup screen but thereafter behaves like a normal 3.60 OFW. I try to start Vitashell or anything else and it just kicks me out, like running homebrew on a 3.65 without starting the exploit first.

Rebooting doesn't work.
Putting it into safemode and rebuilding the database doesn't work.
Putting the 8GB memcard into another Vita and deleting id0.dat through Henkaku Settings and thereafter letting the gamma rebuild the database doesn't work.
Formatting the card doesn't work.
Trying to enable h-encore to run homebrew doesn't work, since what I'm trying to do is enable H-encore through henkaku.xyz but the browser keeps dying, even without entering any address at all.
Injecting a previous QCMA backup of any sort doesn't work, since it demands a SEN connection and it won't allow me to log in.

I'm really not sure what to do here, and my gf is leaving in a few days and I don't want to give her a useless Vita that can't even log onto her own official account.

What I need is a way to make this Vita run homebrew again, so that any issue that occurs thereafter can be dealt with through other FW or just plain old Vitashell. It's so strange to have a Vita boot up as if hacked, and then act as if never hacked at all and with reluctance of ever getting hacked again, at that.

Please help!

tosti · Apr 6, 2020

Do you need to change the storage_config.txt file? Since Gamma had the SD2Vita (probably as ux0) and the memory card (probably as uma0). If that was the case but the storage_config.txt file is not changed, it might be looking for an ux0 that isn't there. That's all I could think of. If that might be it, have a look at the StorageMgr page.

Henrico · Apr 6, 2020

tosti said:
Do you need to change the storage_config.txt file? Since Gamma had the SD2Vita (probably as ux0) and the memory card (probably as uma0). If that was the case but the storage_config.txt file is not changed, it might be looking for an ux0 that isn't there. That's all I could think of. If that might be it, have a look at the StorageMgr page.

Thanks for your quick reply!
I'll look into it, but it seems I need to run stuff through Vitashell which is exactly the problem. The Gamma cannot start any homebrew whatsoever. Or did you mean I should be doing some of this stuff through my Alpha?

Thanks

SteVoUniT · Apr 6, 2020

You can edit your storage_config.txt through any memory card setup, because the ur0:/ partition is going to be the same across all. Use vitashell on whatever method it works on and edit it from there. I think you are having an issue with the gamma setup because it might be set default to look for your memory card and not your sd2vita as mentioned earlier.

tosti · Apr 6, 2020

Henrico said:
Thanks for your quick reply!
I'll look into it, but it seems I need to run stuff through Vitashell which is exactly the problem. The Gamma cannot start any homebrew whatsoever. Or did you mean I should be doing some of this stuff through my Alpha?

Thanks

Could you maybe get h-encore on the Gamma Vita again (see Vita Hacks Guide)? With that, I suppose you could always go to henkaku.xyz on the Vita browser, install the molecularShell, and try if you can use that.

Or maybe, with Henkaku (possibly temporarily until the next reboot) installed, your Homebrew will appear again.

In any case, it's just a hunch, but I think rewriting some lines in the storage_config.txt file might do the trick.

Just to be clear: you say your Vita has the custom boot splash for Enso with the molecule icon but it is not running Enso any more. What firmware does it say under Settings, System, System Information?

EDIT:
Perhaps you could try to alter the Sony memory card that you want to put in the Gamma by first putting it into the Alpha or Beta. With those you can use VitaShell to maybe check the storage_config,txt file and its contents. Maybe make some alterations, turn off the Vita, and put the memory card into the Gamma.

Just a thought.

Henrico · Apr 6, 2020

Well, about editing the storage_config.txt file: I cannot reach it. I can't reach it on Gamma because that requires homebrew which cannot be started, and although Beta is capable of homebrew, it cannot run anything since there isn't anything on the memorycard. It might work with some sort of forced installation, but I'm not familiar with those methods. On Alpha, I could start Vitashell running from my sd2vita but as soon as I remove the memorycard (or maybe it's when inserting the Gamma one, I don't remember the details), it says I have removed a memorycard and the system must now reboot. Same goes for Beta. Removing a memorycard prompts a reboot.

Somehow I managed to insert h-encore on the Gamma card (I cannot remeber how anymore) but as soon as I started it, it flashes white and the Vita kills itself and reboots, prompting that it was turned off incorrectly.

What might be possible is to install h-encore from 3.65 through henkaku.xyz after upgrading the semi-OFW-3.60 through recovery mode, or something, but who knows what that will bring since I'm then installing a higher OFW on a semi-CFW to exploit something which will open a loophole in a new firmware which should already have been compromised earlier through the methods I'm unable to use. And either way, I should be able to start the web browser without it freezing all the time. I can't even access google or as much as about:blank. The browser dies before I can enter an address.

Is there any way to reach storage_config.txt on PC?

Gamma says 3.60 under Settings -> System -> System Information.

I'm thinking of installing sd2vita on the Beta one just to be able to insert a (Gamma) memcard in a natively homebrew capable Vita but I believe there would be a risk of getting the same situation on Beta as for Gamma either before booting everything or else after everything is finished.

EDIT: I wouldn't mind blasting this Gamma completely, even being forced to update everything to latest OFW and hack it from start all the way from there. Is there any way to get either there from Failsafe or to boot the system using only ur0 or something, so I can access the memory card?

I also thought of force reinstalling Enso/Hencore on the Beta using the Gamma card, just in case it results in a Vitashell getting installed on the Gamma card alongside a temporary hack (like hencore) and then I put the Gamma card back in the Gamma. Don't know if that's sch a good idea, either.

tosti · Apr 6, 2020

If your firmware says 3.60 (with no kanji symbols directly behind it), and you do not see any homebrew or cannot run any homebrew you do see, this newbie would guess you are running official firmware 3.60.

Before anything else, I would suggest you wait until some experts chime in--I am definitely a beginner. However, if you are on official firmware 3.60, you should be able to follow the guide from Installing Henkaku, then converting OFW to CFW 3.60 Enso, and then see if you need to finalise your setup.

Henrico · Apr 7, 2020

tosti said:
If your firmware says 3.60 (with no kanji symbols directly behind it), and you do not see any homebrew or cannot run any homebrew you do see, this newbie would guess you are running official firmware 3.60.

Before anything else, I would suggest you wait until some experts chime in--I am definitely a beginner. However, if you are on official firmware 3.60, you should be able to follow the guide from Installing Henkaku, then converting OFW to CFW 3.60 Enso, and then see if you need to finalise your setup.

But the 3.60 exploit goes through the web browser, which kills itself even before I can input any address. I read about some guy updating to 3.65 and then doing the h-encore exploit through finalHE on his PC instead. I'm interested in this option but then I'd have to upgrade to 3.65 and I'm not sure how to do that from my state.

And would that really be safe considering the Vita probably already is hacked? Would it be better to accept the official OFW 3.73 version from the Settings -> Firmware Update menu and take everything from there?

Btw I can still see all my homebrew from the Alpha memstick and sd2vita if I insert them into the Gamma (indicating that the sd2vita redirect may still be in place), but I can't run any of the homebrew as it gives the "An error has occurred" message or whatever it is, like when trying to run homebrew on a 3.65 h-encore temporary hack without enabling the h-encore hack first.

tosti · Apr 7, 2020

Henrico said:
But the 3.60 exploit goes through the web browser, which kills itself even before I can input any address. I read about some guy updating to 3.65 and then doing the h-encore exploit through finalHE on his PC instead. I'm interested in this option but then I'd have to upgrade to 3.65 and I'm not sure how to do that from my state.

If your Vita is running official firmware, you can upgrade using the following video. I went from OFW 3.63 to OFW 3.65 following the steps from the video tutorial.

Henrico said:
And would that really be safe considering the Vita probably already is hacked? Would it be better to accept the official OFW 3.73 version from the Settings -> Firmware Update menu and take everything from there?

As to what's safe or not, I really hope some more experienced person can come into this conversation. I dare not deem updating to OFW 3.73 safe or not.

When you post next time your post count will be up to five. After, you could try to edit in a picture of your System Information and firmware information.

Henrico said:
Btw I can still see all my homebrew from the Alpha memstick and sd2vita if I insert them into the Gamma (indicating that the sd2vita redirect may still be in place), but I can't run any of the homebrew as it gives the "An error has occurred" message or whatever it is, like when trying to run homebrew on a 3.65 h-encore temporary hack without enabling the h-encore hack first.

Previously, I have had a scenario like that as well: homebrew bubbles were present yet CFW was not present (or not activated completely) to run it. For the life of me, I cannot remember what my exact situation was so I do not know if it even applies to yours.

Henrico · Apr 8, 2020

tosti said:
If your Vita is running official firmware, you can upgrade using the following video. I went from OFW 3.63 to OFW 3.65 following the steps from the video tutorial.

[youtube]QbF3zUcDnHY[/youtube]

As to what's safe or not, I really hope some more experienced person can come into this conversation. I dare not deem updating to OFW 3.73 safe or not.

When you post next time your post count will be up to five. After, you could try to edit in a picture of your System Information and firmware information.

Previously, I have had a scenario like that as well: homebrew bubbles were present yet CFW was not present (or not activated completely) to run it. For the life of me, I cannot remember what my exact situation was so I do not know if it even applies to yours.

I guess I could post a picture but it really has nothing more to say than that it's 3.60 and without symbols. It boots with the molecule icon.

Unless someone hops in with different advice, I'll try to update it to 3.65 just to get a temporary hack installed and then explore things in Vitashell. If I can fix things through there then I guess I'm happy, I don't necessarily need to burn a hack permanently into the system. If she's been given i Vita as a gift I'm sure she won't mind activating a hack every now and then when she wants to go online or play a homebrew/similar game.

duwen · Apr 8, 2020

What happens if you boot without SD2Vita in it?
Similarly, what happens if you boot without the memcard in it?

tosti · Apr 8, 2020

Henrico said:
I guess I could post a picture but it really has nothing more to say than that it's 3.60 and without symbols. It boots with the molecule icon.

From the previous install of CFW, I guess your boot_splash.bin file has simply stayed in the Vita's internal memory. That's why it boots with the Molecule icon. However, it looks like that's the only trace of CFW that remains, since every piece of information points towards your Gamma Vita running OFW 3.60

Henrico said:
Unless someone hops in with different advice, I'll try to update it to 3.65 just to get a temporary hack installed and then explore things in Vitashell. If I can fix things through there then I guess I'm happy, I don't necessarily need to burn a hack permanently into the system. If she's been given i Vita as a gift I'm sure she won't mind activating a hack every now and then when she wants to go online or play a homebrew/similar game.

If you are on 3.60, you could install Enso 3.60, which is permanent. If you upgrade to OFW 3.65, you could install Enso 3.65, which is also permanent.

Is there a reason why you would want a non-permanent CFW? If it is to allow for the possibility to uninstall CFW, I've uninstalled Enso myself a couple of days ago. If you do not want to stay on non-permanent CFW, why not go from OFW 3.60 immediately to Enso 3.60? That seems the shortest route to the destination you seek.

Henrico · Apr 9, 2020

tosti said:
From the previous install of CFW, I guess your boot_splash.bin file has simply stayed in the Vita's internal memory. That's why it boots with the Molecule icon. However, it looks like that's the only trace of CFW that remains, since every piece of information points towards your Gamma Vita running OFW 3.60

That would be interesting and good news, but it bids for a more fundamental question of Vita hacking. On the PSP, what you did was always flashed into the flash0 and flash1 memories of the PSP system regardless of what card you were using. Cards could be swapped back and forth, even when the system was still on, which isn't the case for Vita, and even those exploits that weren't flashed were at least active in the ROM of the device, such as Fanjita's eLoader exploits and also independent of cards.

If what you are saying is true, it would imply that the only hacking being done is inflicting the memorycard, not the system. If that's so, then I guess it's completely unflashed. The bootsplash makes me doubt it, however, making me wonder if any alteration of firmware from this point would be a safe option and action.

There was also an alternate, slightly equivoque version of the epilepsy warning, stating that if I would be experiencing physical illness I would stick some Valium up my... fundament, and keep playing. That warning screen has been replaced with the normal one since I formatted the card and reset the system to factory settings.

tosti said:
If you are on 3.60, you could install Enso 3.60, which is permanent.

No, I can't, as that exploit goes through the web browser, which kills itself even before I can enter an address. That was one of my first thoughts though. So I cannot do it on the Gamma 8 memorystick in question to install the enso bubble later to be used, but I can put enso on a ms which I then unlink on/from my Alpha. However, when trying to open it on the Gamma (after inserting Gamma 8 from Alpha fixing), it gives my the same error code (C1-6775-5) as when trying to launch any other app from any other card.

tosti said:
If you upgrade to OFW 3.65, you could install Enso 3.65, which is also permanent.

That's interesting, I hadn't heard of that option. Might be something worth looking into for my 3.65 Alpha, once everything is over with. Thanks!

tosti said:
Is there a reason why you would want a non-permanent CFW? If it is to allow for the possibility to uninstall CFW, I've uninstalled Enso myself a couple of days ago. If you do not want to stay on non-permanent CFW, why not go from OFW 3.60 immediately to Enso 3.60? That seems the shortest route to the destination you seek.

Nah, I'd prefer a permanent install for Gamma of course, but it seemed like the non-permanent options were the safer choice.

And, as stated many times now, the browser hack doesn't run so 3.60-anything is out of the question.

duwen said:
What happens if you boot without SD2Vita in it?
Similarly, what happens if you boot without the memcard in it?

Booting without any card brings only the normal icons plus one game I've tested with a retail gamecard.
Booting with just the sd2vita and no ms brings the same result as above. (Indicating that any sd2vita reroute hack is not burned into the system, or is at least not executable in this state. Possibly indicating that the system is not hacked at all.)
Booting with just the formatted Gamma 8 GB ms brings the same result as above since I haven't installed anything on it yet, and cannot do so since the PS Store is shutting me out, homebrew cannot be installed through Vitashell (which I don't have) and finalHe doesn't support 3.60.
Booting with both sd2vita and an Alpha or Beta memstick brings the icons from the other Vita systems, but they are unlaunchable.
Booting with just either the Alpha or the Beta memstick without sd2vita brings the same as above, minus the sd2vita apps of course.

If it really is so that it's not hacked at all, I'll do any normal route towards 3.60 permanent install.

Tom Bombadildo · Apr 9, 2020

Few questions.

1) Which guide did you follow to install Henkaku and Enso on the borked Vita? Judging by the custom epilepsy method, it sounds like you're using some dubious source, because none of the legitimate guides around have anything to do with the Custom Warning plugin (which is what is able to change that method). This almost makes me think you used some shit guide that tried to brick your Vita, but could probably just some dumb joke otherwise.

2) What happens when you hold down "L" while booting? This disables taihen plugins during boot, so if it's simply a case of a bad plugin that should fix the issue.

It kind of sounds like while you were swapping and restoring, you broke the boot_config.txt file that's on ur0 (which is basically the files that tells enso to run at boot, it probably happened when you did a system restore [assuming you did this after installing Enso]). If holding L while booting doesn't fix your browser issue, you'll need to reinstall 3.60 manually using QCMA and safe mode on the Vita.

To do this, download and install the latest version of QCMA, and download the 3.60 update.pup, rename it to "PSP2UPDAT.PUP" (if needed) and put it in the updates folder in your QCMA's content directory. Open QMCA's settings, change the FW version to 3.60 and check "ignore PSP2-updatelist".

Then, boot your Vita into safe mode, plug it into your PC and make sure QCMA detects it, then on your Vita choose "Update System", and then "Update from PC". It should detect the 3.60 update, and reinstall the firmware completely.

Once this is done, you should be able to boot your Vita and run Henkaku, and install Enso as normal (Note: DO NOT CHOOSE TO UNINSTALL ENSO AFTER THIS PROCEDURE IF PROMPTED BEFORE INSTALLING ENSO. THIS WILL BRICK YOUR VITA. It shouldn't prompt you AFAIK, but just in case it does straight up ignore it.)

From this point, everything should be back to normal and you can restore any backups you like.

Henrico · Apr 9, 2020

Tom Bombadildo said:
Few questions.

1) Which guide did you follow to install Henkaku and Enso on the borked Vita? Judging by the custom epilepsy method, it sounds like you're using some dubious source, because none of the legitimate guides around have anything to do with the Custom Warning plugin (which is what is able to change that method). This almost makes me think you used some shit guide that tried to brick your Vita, but could probably just some dumb joke otherwise.

Well, that's the thing. I bought this through a flea market app and asked what memorystick it had. They said "a 32 GB adapter" and I understood it was an sd2vita. However, I also figured it should contain a Sony Vita ms too, as nothing can be launched without a ms to begin with. As expected, there was one, but it was smaller than I expected — only 4 GB.

When it arrived, I was absolutely baffled by how much $h!t one could actually even have thrown into a Vita. I mean, I'm not a pro or anything, but I've been around for a while and there were so many apps and stuff I had never even heard about. I systematically documented what was on the cards and the screens and the Livearea folders to understand things better and pick things up later if I would ever need it. I genuinely thought there would be no danger in formatting the memorycard and resetting the factory settings as I expected that everything necessary for the Vita to be hacked would already be in the core system files, and not getting altered by a system reset. And I had already installed the sd2vita on my Alpha and the only consequence of not having it inserted upon reboot was that it simply didn't show those apps, or wouldn't launch them. Hence, the possibility of consequences for the Gamma would be none or slim, I thought. Didn't expect I would need to uninstall Enso just to switch a card.

That is to say, I either thought all necessary hack files would remain, or they would be wiped out clean. I didn't expect a situation where I would be stuck in no man's land without homebrew or ability to hack. I suppose I was wrong.

I have copied the entirety of the pre-format/reset ux0, uma0 and ur0 folders laying about on my computer, plus a separate QCMA backup of both the MS and the SD cards. If there's anything you'd like to investigate, be my guest to ask and I will provide information and files.

In my detective work, I discovered that most of what he had done was done in 2014, with a few novelties in February of 2019. He had Unity devkits, registry editors, PSP bubble editors, you name it. Seems like he was on the forefront back in the day but not anymore. To be honest, it was a complete mess to navigate and I just wanted to document everything, backup everything and then blow the whole thing to pieces before starting everything fresh. Seems I destroyed something in the process.

Tom Bombadildo said:
2) What happens when you hold down "L" while booting? This disables taihen plugins during boot, so if it's simply a case of a bad plugin that should fix the issue.

Holding down L brings no difference. Browser still dies.

Tom Bombadildo said:
It kind of sounds like while you were swapping and restoring, you broke the boot_config.txt file that's on ur0 (which is basically the files that tells enso to run at boot, it probably happened when you did a system restore [assuming you did this after installing Enso]). If holding L while booting doesn't fix your browser issue, you'll need to reinstall 3.60 manually using QCMA and safe mode on the Vita.

To do this, download and install the latest version of QCMA, and download the 3.60 update.pup, rename it to "PSP2UPDAT.PUP" (if needed) and put it in the updates folder in your QCMA's content directory. Open QMCA's settings, change the FW version to 3.60 and check "ignore PSP2-updatelist".

Then, boot your Vita into safe mode, plug it into your PC and make sure QCMA detects it, then on your Vita choose "Update System", and then "Update from PC". It should detect the 3.60 update, and reinstall the firmware completely.

Once this is done, you should be able to boot your Vita and run Henkaku, and install Enso as normal (Note: DO NOT CHOOSE TO UNINSTALL ENSO AFTER THIS PROCEDURE IF PROMPTED BEFORE INSTALLING ENSO. THIS WILL BRICK YOUR VITA. It shouldn't prompt you AFAIK, but just in case it does straight up ignore it.)

From this point, everything should be back to normal and you can restore any backups you like.

Okay, cool. Sounds thorough and you seem to know what you're doing. In this case, I'm not sure I am, however. Would this process bring me a mint, clean, untouched and unaltered 3.60 Vita with unharmed ur0 and ux0, and any memory of uma0 ever being on this system is wiped off the planet? That would be reassuring, because then I would be on familiar soil once again for the rest of the procedure.

About your warning: Am I to understand there is a possibility they will discover an Enso installation on my Gamma, and that I should ignore any request of uninstalling that before installing it [for the first time]?

Major props to everyone helping me so far. We seem to be clearing things out.

EDIT: I found the boot_config.txt on the ur0 backup folder on my PC. Would it be of interest for you to read?

Tom Bombadildo · Apr 9, 2020

Yes, reinstalling the firmware should put you straight back at stock with no hacks whatsoever, effectively giving you a clean slate (you will need to format the memory card before you can use it, just a note). It's not the preferred method of reverting back to stock (just straight uninstalling the exploit using the appropriate homebrew is, obviously, the best route

) but in cases like yours it's likely the only one that will work.

And yes, it could be a possibility that it might see some trace of the previous exploit and prompt you, but from what I recall it shouldn't after a reinstall of the firmware. There was an issue a while back where someone reinstalled their firmware in preparation of updating to 3.65 to install Enso on 3.65, then tried uninstalling Enso after that reinstall which ended up completely bricking their Vita.

After you reinstall, I assume you're aware but just in case, be sure to follow this guide: https://vita.hacks.guide/installing-henkaku when re-hacking the Vita to install Enso. This should guide you to installing Henkaku and then Enso on 3.60.

Henrico · Apr 10, 2020

Tom Bombadildo said:
Yes, reinstalling the firmware should put you straight back at stock with no hacks whatsoever, effectively giving you a clean slate (you will need to format the memory card before you can use it, just a note).

With "you need to format it before you can use it", do you mean formatting is a consequence after restoring or is it a prerequisite before starting the restoring? I.e., should I format before restoring?

Tom Bombadildo said:
It's not the preferred method of reverting back to stock (just straight uninstalling the exploit using the appropriate homebrew is, obviously, the best route ) but in cases like yours it's likely the only one that will work.

Yeah, well, you live and learn

Tom Bombadildo said:
After you reinstall, I assume you're aware but just in case, be sure to follow this guide: https://vita.hacks.guide/installing-henkaku when re-hacking the Vita to install Enso. This should guide you to installing Henkaku and then Enso on 3.60.

Yeah, that's the one I'm always following.

EDIT: I formatted just to be safe and then put the .PUP straight into the folder containing all the other Vita folders in QCMA. I'm not sure it makes a difference because I put it both there and into the /SYSTEM/ folder, but in both cases it says I've already got the latest version.

Should I rather download the 3.65 and repeat the procedure to install 3.65 instead, or is that a bad idea?

tosti · Apr 10, 2020

Henrico said:
With "you need to format it before you can use it", do you mean formatting is a consequence after restoring or is it a prerequisite before starting the restoring? I.e., should I format before restoring?

With CFW you remove the personal identifier of a Sony memory card so that the card is not tied to a specific Vita or PSN ID. When you restart the process by reverting back to OFW, the OFW will ask to reformat the Sony memory card because it is missing the personal identifier. That would wipe it of all the previous data.

If you have a Slim Vita or PS TV, you do not need a Sony memory card inserted as you can use the internal memory of the Slim Vita or PS TV. If you own one of those models, perhps you can leave the memory card as it is when working with OFW, and maybe start using it again when CFW is installed?

Henrico said:
Should I rather download the 3.65 and repeat the procedure to install 3.65 instead, or is that a bad idea?

As far as I know, there is minimal difference between Enso 3.60 and Enso 3.60. If you're on OFW 3.60, the easiest way forward is to install Enso 3.60. If you are above 3.60 but not yet above 3.65, the easiest way looks to be installing OFW 3.65 and then proceeding with Enso 3.65.

Henrico · Apr 10, 2020

tosti said:
If you have a Slim Vita or PS TV, you do not need a Sony memory card inserted as you can use the internal memory of the Slim Vita or PS TV. If you own one of those models, perhps you can leave the memory card as it is when working with OFW, and maybe start using it again when CFW is installed?

Nah, they're all 1000. I formatted it either way, there was nothing on it.

tosti said:
As far as I know, there is minimal difference between Enso 3.60 and Enso 3.60. If you're on OFW 3.60, the easiest way forward is to install Enso 3.60. If you are above 3.60 but not yet above 3.65, the easiest way looks to be installing OFW 3.65 and then proceeding with Enso 3.65.

Yes, but the question is if the procedure is safe to do when going from crazy-3.60 to OFW 3.65 now that it says 3.60 OFW is already/cannot be installed. Once 3.65 is installed however, I'll go the normal route.

So, is it safe to try 3.65 instead?

tosti · Apr 10, 2020

Henrico said:
So, is it safe to try 3.65 instead?

Honestly, I do not know. Tom has helped me install CFW a couple of weeks ago, so I will defer to their judgment regarding the installation of firmware 3.65:

Tom Bombadildo said:
Yes, reinstalling the firmware should put you straight back at stock with no hacks whatsoever, effectively giving you a clean slate [...] in cases like yours it's likely the only one that will work

And yes, it could be a possibility that it might see some trace of the previous exploit and prompt you, but from what I recall it shouldn't after a reinstall of the firmware.

Hacking 3.60 Enso half-installed?

Member

Well-Known Member

Member

Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Member

Old Man Toad

Well-Known Member

Member

Dick, With Balls

Member

Dick, With Balls

Member

Well-Known Member

Member

Well-Known Member

Similar threads

Popular threads in this forum