CMA prompts users to update

[RoyalNexus]

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.

[RoyalNexus]

Here is the PS4-Exploit-Host method:

1. Download PS4-Exploit-Host (github.com/Al-Azif/ps4-exploit-host/releases)
2. Extract it, and navigate to updates/psp2-updatelist.xml
3. Note: For this next step, make sure you change the suitable blocks of code to correspond to your firmware. (The one's with 01.600.000 should stay however.)

• 03.600.000 for 3.60
• 03.650.000 for 3.65
• 03.680.000 for 3.68
  Open it in your text editor of choice, and replace everything with the following:

<?xml version="1.0" encoding="UTF-8"?>
<update_data_list>
   <region id="{{REGION}}">
       <np level0_system_version="01.600.000" level1_system_version="03.650.000" level2_system_version="03.650.000" map="03.650.000"/>
       <np_d level0_system_version="01.600.000" level1_system_version="03.650.000" level2_system_version="03.650.000" map="03.650.000"/>
       <version system_version="03.650.000" label="3.65 (変革 Compatible)">
           <update_data update_type="full">
               <image size="133754368">http://d{{REGION}}01.psp2.update.playstation.net/update/psp2/image/2017_0317/rel_0a0f2a9ae58968ac5d1d2127049c3cba/PSP2UPDAT.PUP</image>
           </update_data>
       </version>
   </region>
</update_data_list>

4. Now simply run ps4-exploit-host.exe and it'll display your IP address, put that IP address as your Vita's DNS server in the Settings menu.
   CMA should no longer prompt you to update.

[RoyalNexus]

A few additional things:

Updating through safe mode bypasses the need to use CMA or any of the methods listed above, but obviously 3.65 and 3.68 users will need to still use CMA to transfer the exploit.

The way we formatted it in our guides on the Vitahacking-Guides Discord is like so:

Section 1: Preparing Final H-Encore.

1. Grab the latest release of Final H-Encore: (github.com/soarqin/finalhe/releases/)
2. Extract and launch it.
3. Proceed to do one of the following:
   • Setting the Vita in airplane mode and then restarting the device, usually works. PSTVs can't do this.
   • Use Vita Update Blocker on your computer. (wololo.net/downloads/index.php/download/8304)
   • Use PS4-Exploit-Host, refer to #pstv-cma-prompt for the method.

That second one might give you an idea on how to format the guides, either way, I still think it's a messy solution to a messy problem. Being able to host a local DNS in order to both update the Vita and bypass update checks is still the best theoretical solution I could come up with.

[Plailect]

Is there any reason why using Molecule's 3.60 server on your >3.60 device would still prompt users to update? Have you tested it?

[RoyalNexus]

Is there any reason why using Molecule's 3.60 server on your >3.60 device would still prompt users to update? Have you tested it?

While using the 3.60 server does actually work to negate update prompts, I believe the server is not operating on a dedicated server (it tends to have periods where it works and doesn't work). So it is up to whenever Yifan wants to host his server.

Now, Molecule seems or is planning to release a new webkit exploit for 3.70. This will drastically change the method from how it is currently detailed (in addition to making it much easier for the average end-user to install, assuming it isn't patched right after the fact). Not only that, but downgraders from both Gleba and thefl0w will be released soon enough. Best way to go about this at the moment might be to implement the methods I detailed in the previous post for the moment as a band-aid solution? I don't know.

[Plailect]

I'll probably just include instructions for airplane mode / using the 3.60 server for now as a stop-gap solution until the new 3.70 exploit is released. If I have time in the future I may also add instructions for the others, but those are more complicated and demand more from users.