Hacking How can I get back Vitashell (3.65)

[lucks]

It should work, unless the spoof has not been updated or something is changed.
Are you blocking psn urls?

 

[Dothackjhe]

It should work, unless the spoof has not been updated or something is changed.
Are you blocking psn urls?

I do not recall configuring my device's setting to block any URL, particularly PSN's. I've just made a fresh transition from 3.60 to 3.65 Enso. Everything was smooth. I even managed to run VitaShell 1.82 after the first boot to 3.65 Enso. The problem with VitaShell 1.82 getting corrupted arose after configuring the device to work with SD2Vita. I tried re-installing VitaShell 1.82 via MolecularShell, it did not fix it.

 

[lucks]

Replace vitashell eboot.bin in your sd2vita


Maybe the spoof is not working but the readme says nothing about it.

Anyone else with the same problem?

 

[Dothackjhe]

Replace vitashell eboot.bin in your sd2vita


Maybe the spoof is not working but the readme says nothing about it.

Anyone else with the same problem?

Where do I get this VitaShell "eboot.bin" at?

Can you share me your installed VitaShell's "eboot.bin" instead?

 

[Justin20020]

@lucks yeah I see. I ordered yesterday one but I only found 8gb. It comes today

 

[lucks]

I m not using vitashell 1.82
You can find it in the vpk, if i remember right

 

[Dothackjhe]

I m not using vitashell 1.82
You can find it in the vpk, if i remember right

I tried your suggestion i.e. replacing the existing "eboot.bin" with that from VitaShell 1.82 VPK. I still am getting a corrupt installation of the app. I guess there is really no other way about this than using QCMA + CMA + PSVIMGTOOLS.

 

[lucks]

Uninstall vitashell and rebuild database or build vitashell from src with a new TID so that you can uinstall the old one and use it to install the official shell again.

Afaik molucular shell is dead and buggy

 

[Dothackjhe]

Uninstall vitashell and rebuild database or build vitashell from src with a new TID so that you can uinstall the old one and use it to install the official shell again.

Afaik molucular shell is dead and buggy

This suggestion is too risky for me. Have you personally tried it, though?

 

[lucks]

Yes, on 3.60
Theflow says the rebuild is safe on 3.65

You can also try opt 2
Build vitashell from src with a new title id and install it

 

[Dothackjhe]

Yes, on 3.60
Theflow says the rebuild is safe on 3.65

You can also try opt 2
Build vitashell from src with a new title id and install it

The first option sounds tempting. But I guess I will just have to wait it out for now and see what TheFlow could come up with in answering this problem. As far as I know, he has his attentions to it, somewhat.

 

[Timburpton]

The first option sounds tempting. But I guess I will just have to wait it out for now and see what TheFlow could come up with in answering this problem. As far as I know, he has his attentions to it, somewhat.

I thought it was mentioned clearly in the Readme.md to backup vitashell so you could restore it if it goes missing?

 

[BADDINOROX99]

I thought it was mentioned clearly in the Readme.md to backup vitashell so you could restore it if it goes missing?

a lot of people who are having issues clearly didn't bother to read the readme a few times before updating

 

[Dothackjhe]

Yes, on 3.60
Theflow says the rebuild is safe on 3.65

You can also try opt 2
Build vitashell from src with a new title id and install it

I manually rebuilt the device's database but was pressed by another problem afterwards. The system is now strictly pointing to Sony's official memory card as default storage instead of SD2Vita and I lost MolecularShell from the LiveArea. I'm clueless at this point on how to fix this.

I thought it was mentioned clearly in the Readme.md to backup vitashell so you could restore it if it goes missing?

I deliberately skipped the step since as I was having issue connecting my device to PC via CMA or QCMA at the time. Also, VitaShell was actually just fine on first boot to 3.65 Enso. It was when I made the transition to SD2Vita that VitaShell went corrupt and everything else went sour from there.

 

[lucks]

Oh, i see, the rebuild option is patched on 3.65 to wipe your config, sorry
(Wtf?)

You should be able to install vitashell with psvimgtools in your sony mc
According to silicia and celeste you can replace the welcome park or near (make a backup) with vitashell (eboot.bin) or molecular so you have a manager to reenable your sdvita when the config is broken/empty.


Usb fix qcma:
Enable airplane mode and reboot to apply(yea it s mandatory)
This way the fw check is skipped.

 

[Timburpton]

I deliberately skipped the step since as I was having issue connecting my device to PC via CMA or QCMA at the time. Also, VitaShell was actually just fine on first boot to 3.65 Enso. It was when I made the transition to SD2Vita that VitaShell went corrupt and everything else went sour from there.

There is your problem.

 

[Dothackjhe]

There is your problem.

Highlighting on it does not make it any better, lolz. I only skipped on it because it poses as a stumblingblock at the time while also being optional.

--------------------- MERGED ---------------------------

Oh, i see, the rebuild option is patched on 3.65 to wipe your config, sorry
(Wtf?)

You should be able to install vitashell with psvimgtools in your sony mc
According to silicia and celeste you can replace the welcome park or near (make a backup) with vitashell (eboot.bin) or molecular so you have a manager to reenable your sdvita when the config is broken/empty.


Usb fix qcma:
Enable airplane mode and reboot to apply(yea it s mandatory)
This way the fw check is skipped.

I managed to restore VitaShell.

 

[Timburpton]

while also being optional.
I managed to restore VitaShell.

Good for you.

The readme does say this "This is very important, since if you lose VitaShell this is the way you restore it."

 

[Dothackjhe]

Good for you.

The readme does say this "This is very important, since if you lose VitaShell this is the way you restore it."

It's completely optional now because of the latest update of PSVIMGTOOLS. The logic is essentially almost the same.