Just realized that there is no guide showcasing users how to manually update to 3.68 with QCMA if they are on odd firmwares (Final-HE is not supported on them). It's probably a good idea to do this now in-case the custom update servers ever go down.

Ideally another custom update server would be nice but again, we can't rely on them forever.

This so called enso ex is not from original developer and can cause soft brick if SD2VITA driver provided by it is enabled.

Source: personal experience and Reddit.

Hey, your new update for the guide is interesting, and using VitaDeploy is a good idea, but there's a couple things wrong:

• Do not tell people on 3.60 to update to 3.73, it actually makes the process way harder than it should.
  By updating to 3.73, people will have to use finalhe in order to hack their console. FinalHE is ok but still relies on Sony's CMA protocol (or more precisely the only client that works sometimes, qcma. Sony's one being so broken it almost never works fine.). FinalHE makes the hacking process way harder for 3.60 users as it requires a PC and requires much more tries to get it to work properly (thank sony for that). You could streamline the process by asking 3.60 users to use Henkaku and then VitaDeploy. VitaDeploy uses Modoru and as such, also allows for updates. Updating to 3.65 is really unnecessary but i get it, until VitaDeploys adds a Quick 3.60 button, it makes the guide easier.

• Do not hide the Henkaku method in a small banner, make it the main process since it will make things way easier and can prevent hours of troubleshooting for the end user. You can keep the 3.73 option as the secondary one, in case the Henkaku method doesn't work.

• People below 3.60 should be redirected to a 3.60 update page, where the DNS would still be available.

• Like other users have said, you should keep a list of useful plugins inside the Finalizing page. Even if those are installed by VitaDeploy, it can still be useful to write down.

• There's no apps that will stop supporting 3.60, at least for the end user. It would just be stupid from the dev. In fact, 3.60 tends to be the most compatible version since every plugin, the VitaSDK or homebrew apps are made with henkaku in mind, and not h-encore. Pretty much all apps will work fine between 3.60 and 3.68, but just in case, remember it is the most compatible firmware.

Not recommend to do so on Mac OS X thanks to the stupid .DS_store contaminating every single folder.

For Windows, need to set view options to show hidden files and disable hiding of system files to see everything.

Seeing id.dat should be a good indicator view options are configured properly. Otherwise tend to lose data during transferring.

Step 8 instructs to replace all instances of "ux0" with "ur0" in the config.txt file. I think this needs a note about the path "ux0:app/PSPEMUCFW/sce_module/adrenaline_kernel.skprx" which is likely to remain on ux0.

Hi

in the guide, say if you have firmware from 1.03 to 3.63, need upgrade to 3.74. but why not upgrade directly to 3.65?

i remember a method to upgrade exact fw version you want

greetings

As said on Discord, I made a small web thingy for people to get VitaShell, VitaDeploy and Hencore² (since it works on 3.65-3.73) as QCMA Backups.
https://api.vita.meek.moe/QuickLinks
The URL is a bit of pain, but it works.

Quick description on how it works:
Its essentially psvimgtools attached to a webserver
for the Account ID its using some RemotePlay URL that Chiaki also uses (https://trinket.io/embed/python3/52183a157e) but converted to C#)

https://www.playstation.com/en-ca/support/hardware/psvita/system-software/

stuff like downgrading guide needs to be updated to have a neutral term like "homebrew enabler" or smth instead of h-encore

Using https://github.com/SKGleba/mincg

Trinity supports 3.65 - 3.70, so there's no need to keep using h-encore now

Footer still links to Plailect/Guide_Vita. That works for now but may break in the future.

The first answer in your FAQ is not correct anymore.
Firmware 3.69 is unhackable (at least for a long time).
So you should change the answer from "Yes!" to "No, at least not yet."

It seems people screw themselves by "cleaning" their memory card after installing StorageMgr (or other sd2vita drivers) and then when they need to skip plugin loading (holding "L" on boot), they have nothing to edit their config.txt with.

(See for example xerpi/vita-udcd-uvc#19 (comment))

So in the StoargeMgr page, suggest keeping uma0:app/VITASHELL, uma0:appmeta/VITASHELL, uma0:license/app/VITASHELL and uma0:user/00/savedata/VITASHELL (did I miss anything?)

The following warnings precedes the YAMT installation guide:

Red Samsung Evo cards are not compatible with YAMT

https://github.com/hacks-guide/Guide_Vita/blob/92bb84773adaa59de00b00322b56c354de75f69b/docs/yamt.md?plain=1#L21C12-L23

At least several reports indicate that there are no issues with red Evo cards. I myself was able to set up YAMT with a red Evo+ 128GB card today with no issues so far.

If formatted with default option provided by operate system, PS Vita may misread the free space and prevent save file creation even when still space available.

I made a stupid mistake of not checking the partition table of my MicroSD before setting it up to use SD2VITA. My default (on Kubuntu 20.04) seemed to format it for GPT. It would appear The PS Vita doesn't understand the GPT table format, and will make the SD card not show up on the Vita, but fine on a computer. This might make some less technically inclined people think that their SD2VITA card is broken.

fdisk -l /dev/sdX will show the partition table type under 'disklabel type:'. If it's shown as dos, it'll appear fine on the Vita.
(I sadly don't know a command to change this. I change the partition table via KDE Partition Manager).

This could've been a glitch on my machine since it was a GPT table prior to being repurposed for the Vita, but might be good to add as a troubleshooting step in case the user is unable to get it working.

Apologies if this was the wrong place to drop this. The whole website was extremely helpful in getting my Vita from fresh to homebrewed, and really appreciate all the hard work and effort that has gone into producing this guide.

https://github.com/Plailect/Guide_Vita/blob/045f2b2c101c34eb03a7cb700756a822ca8b0aa4/_pages/en_US/updating-to-3.65-(enso).txt#L12

There's an extra "which" in the sentence, making the sentence incomplete and a little confusing to read.

Since its official for the VitaDB and does not crash like VHBB it help users better

Brought this up on Discord yesterday but since then have done a little more of the guide and noticed a few more places so figured I'd move here since this works better for it.

When using a Japanese console ○ and × are flipped, so most (some homebrew are hardcoded to a specific button) of the steps saying to press one of them are wrong. I think it could work to say like "Press the Confirm button" and "Press the Cancel button" instead of "Press the (Cross) button" and "Press the (Circle) button" and mention on the home page or so what that means, however that may be more confusing to people with non-Japanese consoles.

I think this is probably worth considering though even outside of like a Japanese translation as the Japanese consoles are significantly cheaper than other ones so I imagine plenty of people buy them for that reason.

Alternatively, could maybe add a step on installing-h-encore.md after Section IV or so saying to change the "○ Button Behavior" (too lazy to check the exact English wording) setting to "Cancel" as then everyone will have the same controls. Personally not a fan of that though as I always prefer to use my PlayStation consoles with ○ = Confirm.

Here's all of the steps I noticed so far that are incorrect, note that I haven't checked every page yet.

Edit: Added yamt.md

#### Section III - Configuring h-encore
3. Press (Cross) to exit the application

#### Section V - Installing essential homebrew
6. Press (Cross) on the VitaShell.vpk file to install it
7. Press (Cross) to confirm the install
8. Press (Cross) to confirm the install again when prompted

#### Section I - Installing homebrew applications
7. Press (Cross) on “Mark all”
9. Press (Cross) on “More”
10. Press (Cross) on “Install all”
11. Press (Cross) to confirm the install
12. Press (Cross) to confirm the install again when prompted

#### Section I - Prep Work
8. Press (Circle) on your device to close the FTP connection

#### Section II - Installing VPKs
4. Press (Cross) to confirm the install
5. Press (Cross) to continue the install each time you are prompted about extended permissions
7. Press (Cross) to confirm the deletion

#### Section III - Modifying Plugin Config
1. Press (Circle) to return to `ux0:`
3. Press (Cross) on config.txt to open it in the editor
7. Press (Cross) to edit the line
9. Press (Circle) to close the editor
10. When prompted, press (Cross) to save your modifications

#### Section I - Prep Work
8. Press (Circle) on your device to close the FTP connection

#### Section II - Installing VPKs
4. Press (Cross) to confirm the install
5. Press (Cross) to continue the install each time you are prompted about extended permissions
7. Press (Cross) to confirm the deletion

#### Section III - Formatting the microSD
4. Press (Cross) on “Format target storage”
5. Press (Cross) on “Reboot your device”

#### Section V - Restoring Data
6. Press (Cross) on “Mark all” to select all folders and files in the ux0: partition
8. Press (Cross) on “Copy”
9. Press (Cross) again when prompted
12. Press (Cross) on paste and wait for it to finish

And finally these steps are hardcoded and should not be changed:

### Instructions
5. Press (Cross) to confirm
7. Press (Cross) again to confirm

#### Section II - Installing iTLS
2. Press (Cross) on “Install the full iTLS package”

#### Section IV - Installing PSP XMB
2. Press (Cross) to download the PSP 6.61 firmware
4. Press (Cross) to install PSP 6.61 the firmware
5. Press (Cross) to boot the PSP home menu

#### Section IV - Installing yamt-vita
3. Press (Cross) on -> Install the lite version

Downgrading to lower versions is ideal.

The guide should ideally tell people to remove YAMT which is installed by VitaDeploy if they are following the StorageMgr guide. This will stop it from working.

A lot of users tend to try transferring the exploit using a wired connection first. However, due to the dodgy nature of Vita's drivers, this doesn't work for everyone straight out of the box and usually requires troubleshooting. WiFi should be the preferred transfer method unless the user does not have access to a WiFi network.

Suggestion:

• Recommend users on the 'installing h-encore' page to try WiFi method first.

I can see on Crowdin several languages that are 100% translated but there are not published.

Current published languages:

• English
• Russian
• Chinese Traditional

Non published 100% translated languages:

• German
• Italian
• Portuguese
• Spanish

Could you update the website to make available translated languages?

This seems easier than having users manually configure everything with somewhat confusing config files.

So, for one reason or another, the DNS to block update prompts (212.47.229.76, featured on the installing h-encore page) for the vita doesn't seem to work anymore (At least in CMA's case). This is a problem because CMA will try and force the user to update to an unhackable firmware in order to transfer over the exploit.

That said, there's an easy way around this, by simply turning on airplane mode and rebooting the Vita, it will no longer check for updates. Allowing users to use CMA freely. However, if this problem isn't specific to CMA (i.e. CMA pings an update server not blocked by the DNS) and spans the entire system instead, it may cause users to accidentally update.

Suggestions:

• Check to see if the problem is simply unique to CMA with 212.47.229.76, and append the installing h-encore page with the airplane mode fix (alternatively, seek out the host of the DNS and ask them to block whatever CMA pings).
• Check to see whether the DNS on the blocking updates page (23.96.6.207) works (I'm guessing this points to 3.69 as the latest update, though).

Seems like an obvious mistake: https://vita.hacks.guide/yamt

This is because you must keep h-encore installed to the memory card so you can enable HENkaku (and therefore StorageMgr) after a reboot.

This should probably be

This is because you must keep h-encore installed to the memory card so you can enable HENkaku (and therefore YAMT) after a reboot.

Users on firmware's lower than the current one will receive a prompt to update, resulting in them not being able to use CMA. We've developed several different methods to combat this, each with varying degrees of success:

• Setting the Vita in airplane mode and then restarting the device, usually works. PSTVs can't use this.
• Using Vita Update Blocker on your computer. (wololo.net/downloads/index.php/download/8304)
• Using PS4-Exploit-Host (method detailed below)

Airplane mode sometimes works, and other times doesn't, not a clue why.

Vita Update Blocker should work in all instances, although some users might have a service already running on the default port (or have it blocked), in which case they need to launch the program through a CMD prompt to specify a different one.

PS4-Exploit-Host is akin to running your own update DNS. In theory users should be able to update with it, however the user I tested this with could not. I'm going to try again with another user if I see one to confirm this though.

Honestly, I think the best solution might be to talk to YifanLu about the Henkaku update server they host. If they could release whatever they use to host it, users could both use it to update their Vita's and transfer the H-Encore exploit.

It is possible to downgrade to the factory version as you stated in the guide.
Please change the FAQ.

Wrong:
https://github.com/soarqin/finalhe/releases/download/v1.9.1/QcmaDriver_winusb.exe

Correct:
https://github.com/soarqin/finalhe/releases/download/v1.91/QcmaDriver_winusb.exe

Specific to the "YAMT (SD2Vita)" page at https://vita.hacks.guide/yamt.html/ .

The instructions begin with Section I - Installing YAMT VPK.
Then the next thing listed is Section III - Formatting the microSD.
There is no section called Section II; that number gets completely skipped.

TO FIX IT: Instead of the 4 sections being numbered I / III / IV / V, they should be renumbered I / II / III / IV.

hiya, i noticed while setting up my japanese vita (that normally uses o to advance) that in HENlo, the x button is used even though the guide suggests that you should press o, this is a small issue but a correction would be nice, thank you.

The macOS Sierra+ recommended version crashes if FFmpeg 3.2 is not installed (and brew installs 4.0 by default)

For people on Trinity who can't downgrade to 3.65, there needs to be a guide for downgrading to 3.68 to install Trinity due to compatibility issues with plugins such as storagemgr etc on 3.69+.

Hi there,

I was wondering if there was a way to uninstall everything installed via this guide? I've looked through community resources, various applications mentioned here, and I can't seem to find anything as it was not manually installed. Is this even possible?

Thanks!

Vita Deploy installs YAMT and the YAMT portion of the guide tells people to install YAMT.

It still says "sometime in September" :p

Currently the guide only works on Windows

Hey,

First of all - thanks for the guide, it was really helpful. I managed to complete the process but I found several confusing items. I'd like to share some thoughts with you then.

I just went through the vita.hacks.guide. I have PS Vita slim, firmware 3.73 so my starting point was: https://vita.hacks.guide/installing-h-encore

• https://vita.hacks.guide/installing-henkaku After installing the exploit the molecularShell bubble doesn't show up. I followed the troubleshooting instruction but it didn't help. The molecularShell never appeard on my LiveArena. Additionally, when I was trying to re-run the exploit by visiting the http://henkaku.xyz site a strange message showed up. It was saying that I'm running unsupported 3.65 software - which wasn't true. That message went away after I restarted the device.
• The Enso link (https://github.com/henkaku/enso/releases/tag/v1.1) points to a wrong page. It should point to: https://enso.henkaku.xyz/
• I ignored that fact and continued to https://vita.hacks.guide/installing-enso-(3.60). The first confusion was caused by the VitaShell requirement. Why it's listed there as a requirement? This app was already installed at the very beginning, in the 2nd step.
• At the same page. the instruction tells to launch the molecularShell. I didn't manage to get molecularShell so I used VistaShell that was already installed. VistaShell allowed me to complete the Enso installation step without any issues.
• There's a link that points to https://github.com/dots-tb/reF00D/releases/tag/1.0 The information there says "Please use: https://github.com/SKGleba/0syscall6/releases instead" The guide doesn't tell anything about it.

The QCMA version of installing h-encore is not included in the sidebar of the site, along with the "proceed to..." part on the bottom.
In order to make that section of the site more user-friendly, I'll make an addition to /docs/.vuepress/configs/en_US.js to (hopefully) rectify this. The pull request will be put into effect once my latest has been accepted in order to avoid any conflict/mistakes.

What I plan to do is:

This following section is from lines 59-72 of en_US.js.

 sidebar: {
      '/': [
        {
          text: 'Guide',
          children: [
            'index.html',
            'get-started',
            'updating-firmware-(3.73)',
            'installing-h-encore',
            'installing-enso',
            'finalizing-setup'
          ],
        },
      ],

What I'll add is this:

 sidebar: {
      '/': [
        {
          text: 'Guide',
          children: [
            'index.html',
            'get-started',
            'updating-firmware-(3.73)',
            'installing-h-encore',
            children: [
             'uninstalling-cfw.md',
              ],
            'installing-enso',
            'finalizing-setup'
          ],
        },
      ],

I have no idea if this'll work, but this is what I plan to do to fix this issue.

For example on Adrenaline page I don't see TheFloW, on StorageMgr I don't see CelesteBlue, yifan lu, xyz, motoharu, etc...

For the new guides, the leftmost section on the guides needs to be updated.

1 Add in the windows tutorial about showing file extension a part to show hidden files and folder (So when the user want to access through the content of his memoyrcard through usb he will have access to all the folders. Like app, tai, pspemu etc
(Enabling those two options in the windows explorer setting)
https://cdn.discordapp.com/attachments/439484919266148362/574687241939451956/unknown.png

2 Add in the finalizing part the plugin Emergency Remount which can help with fixing bootloop easly (caused by improper plugin installation.) As a futur proof solution.
I have detailed its usage on my troubleshoot guide and in which case it can help. (Also if you could link to my guide in your vita hacks troubleshooting section it would be awesome. I have detailed most of problems that a user can encounter with its vita and how to solve them)
https://samilops2.gitbook.io/vita-troubleshooting-guide/plugins-related-problem/plugins-not-loading

3 Blocking update part isn't necessary imo. Henkaku already block the updates by disabling the update menu (replaced by henkaku settings) + the DNS can cause issue with PSN access (mostly noticeable when we want to play online).