With the new 3.65 HENkaku Enso update, you might format and find yourself without a way to access homebrew. While there are other ways to reinstall it, this tutorial will leave VitaShell installed as a system app, meaning it won't be wiped or written over when formatting. This guide will replace a system app with VitaShell, so that application will not be usable afterwards.

Guide EDIT: Tool made obsolete by release of h-encore

EDIT: Do I make a typo in every single title ffs

 

[Deleted User]

nice!
I still use near sometimes so this is not fully ideal
would it be possible to replace the connect with provider thing on the 3g models or would it cause issues?

 

[Deleted member 381889]

nice!
I still use near sometimes so this is not fully ideal
would it be possible to replace the connect with provider thing on the 3g models or would it cause issues?

You could just replace another system app which you don't use
i thought near was dead anyway

 

[Deleted User]

You could just replace another system app which you don't use
i thought near was dead anyway

ok
so welcome park and parental controls would work too?

 

[Deleted member 381889]

ok
so welcome park and parental controls would work too?

not welcome park

 

[slaphappygamer]

Can we do this with other apps too? Say maybe, vitadoom?

 

[Deleted member 381889]

Can we do this with other apps too? Say maybe, vitadoom?

I think so, you'd have to check what else inside the app folder is needed

 

[hellionz]

this guide can be use on 3.60?

i want to install it as system app before upgrade to 3.65

Greetings

 

[Ryccardo]

not welcome park

Actually yes, see the bug report on the 3.65 updater

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

this guide can be use on 3.60?

Yes, but you will have to repeat it after updating to 3.65 (if you still want vitashell as system app, of course)

 

[Deleted member 381889]

Actually yes, see the bug report on the 3.65 updater

you can't replace it with the same method, it's on another partition
i mean you can replace it but it's not as easy

 

[queiroxo]

okay i already did what i should,t, what ways are to get vitashell back?

 

[Reploid]

Just install appmanager plus and move all essential apps to ur0. Including appmanager itself. Bulletproof!

 

[Deleted member 381889]

Just install appmanager plus and move all essential apps to ur0. Including appmanager itself. Bulletproof!

No, restoring wipes ur0
the point of this is to keep the app even after a restore

 

[Reploid]

No, restoring wipes ur0
the point of this is to keep the app even after a restore

Well, bummer.

 

[Deleted member 381889]

Guide now uses HBInjector so you can't mess shit up with VitaRW lol

 

[Versa]

I'm getting a failed to copy VitaShell error whenever I try to inject it to one of the apps. Any ideas about this?

 

[Deleted member 381889]

I'm getting a failed to copy VitaShell error whenever I try to inject it to one of the apps. Any ideas about this?

Does ux0:app/HBINJECT0/VitaShell.bin exist?

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

Nvm, issue with mounting vs0, fixing now

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

I'm getting a failed to copy VitaShell error whenever I try to inject it to one of the apps. Any ideas about this?

https://github.com/emiyl/HBInjector/releases

 

[Localhorst86]

can we have two different versions of vitashell installed that way? 1.82 as a permanent system app and the most current as a regular app?

 

[Deleted member 381889]

can we have two different versions of vitashell installed that way? 1.82 as a permanent system app and the most current as a regular app?

hbinjector includes 1.83, but yes

 

[Localhorst86]

hbinjector includes 1.83, but yes

With 1.83, auto-update has been fixed. Is there any risk in updating a "system-app-injected" Vitashell install? If not, will disabling auto update in the injected Vitashell disable the update check on the "regular" version?