Hacking HENkaku Enso for 3.65 Released

[aos10]

I suppose I should ask for silly clarification reasons;

After updating, is it okay to remove either the main Enso and/or Updater apps?

(Success from a Vita 1k, btw.)

The old one is already gone, but you should keep the icon just maybe you will need it in the future.

 

[sj33]

Highly doubt Vitamin/MaiDumpTool-based dumps have stopped working.
But you should be using NoNpDRM-based dumps instead, and those (alongside the accompanying plugin that was also updated) work fine.

It does make the English fan translation of Phantasy Star Nova unusable however because they intentionally stuck to using the Mai/Vitamin version for that. There is a prebuilt Nonpdrm version floating around but it’s not updated and doesn’t support the DLC.

 

[wakabayashy]

It does make the English fan translation of Phantasy Star Nova unusable however because they intentionally stuck to using the Mai/Vitamin version for that. There is a prebuilt Nonpdrm version floating around but it’s not updated and doesn’t support the DLC.

here's my point, I want to know if the patched version of various games (trails, chaos omega, phantasy star) will works or not

thanks for help

 

[SeongGino]

here's my point, I want to know if the patched version of various games (trails, chaos omega, phantasy star) will works or not

thanks for help

I don't see what would prevent these from working; unless they are, for whatever reason, tied to a specific firmware (if those are even things outside of plugins...?), they should work like any normal application.

 

[wakabayashy]

it's said that homebrew won't work, to install the games patched, we need maidump so...

 

[Deleted member 381889]

it's said that homebrew won't work, to install the games patched, we need maidump so...

NoNpDrm is superior to MaiDump and Vitamin. NoNpDrm has been updated to 3.65.

 

[wakabayashy]

NoNpDrm is superior to MaiDump and Vitamin. NoNpDrm has been updated to 3.65.

I know, I use Nonpdrm too, but the game patched works only with mai :/

 

[Deleted member 381889]

I know, I use Nonpdrm too, but the game patched works only with mai :/

Oh, sorry, didn't read the rest of the convo

 

[SeongGino]

it's said that homebrew won't work...

...Only if said homebrew rely upon specific kernel modules for a specific firmware; which only accounts for system-tinkering tools.
There's also a list out there that mentions RetroArch of all things being incompatible; I can say for a fact, that's not that case.

... to install the games patched, we need maidump so...

The patched games will work fine, because again, the philosophy only applies to kernel modules that tinker/modify values that are firmware dependent.
I can't speak for MaiDumpTools personally, but isn't that a long-outdated method of dumping games anyways? Isn't Vitamin superior for decrypted copies? Especially considering that it hasn't been updated in over two years...

 

[sj33]

here's my point, I want to know if the patched version of various games (trails, chaos omega, phantasy star) will works or not

thanks for help

It depends if the patches support the Nonpdrm dumps of the game. In the case of Phantasy Star Nova, the devs decided not to switch to using the Nonpdrm version as a base.

Nonpdrm versions are objectively better and we should use those. With fan patches however, we’re relying on the devs.

Vitamin is on github so it in theory could be updated by somebody.

 

[SeongGino]

It depends if the patches support the Nonpdrm dumps of the game. In the case of Phantasy Star Nova, the devs decided not to switch to using the Nonpdrm version as a base.

Nonpdrm versions are objectively better and we should use those. With fan patches however, we’re relying on the devs.

Vitamin is on github so it in theory could be updated by somebody.

It really should be the standard by this point; the only merit MaiDumpTool possesses are the decrypted contents of the installations themselves, which makes slipping in mods easy. But both it and Vitamin 2.0 are donkeys years old, and NoNpDRM is clearly the successor we needed, but not the one we deserved.

AND BECAUSE PEOPLE KEEP ASKING, I FINALLY CHECKED FOR MYSELF.
MAIDUMPTOOL WORKS ON 3.65, AND MAIDUMPTOOL DUMPS WORK AS WELL ON 3.65. THANK YOU VERY MUCH FOR YOUR PATIENCE.

 

[yeshuachrist]

Updated guide for 3.65: https://vita.cfw.guide/more/updating-to-henkaku-enso-3.65/

(enso.vpk on 3.60 firmware checks for any changes to the 3.60 package like removing the "feature page" .............. something which i plan on doing for 3.65 but that required the "VitaRW" app to work ............... so far no mention that installing enso which is done automatically checks for changes to the 3.65 package, also on that link in quote, It says we could use the "RESTORE TO FACTORY DEFAULT"

pause

that if we use the 3.65 installer provided, then we should be ok, but until henkaku's website does not supports the 3.65 firmware, that statement of restoring to default, shouldn't allow anyone to install henkaku in order to install enso on 3.65

pause

so until these issues are ironed out, I doubt "mlthaku" will be officially updated, or because of the increased risk of bricking I doubt that henkaku's official website will ever support anything higher than 3.60

pause

totally worth it for "ys origin" and "berserk" and "super robot wars v in english"

PAUSE

if you have more than one vita that does not need the games which benefit from unsupported plugins, then this is definitely for you, but I think I'll have to wait a little longer since a official update to or for, 3.67 was mentioned, all of these steps could be changed

EDIT

so far this is what i understand, delete dat file from options to use sd2vita memory card on another vita then remove (make sure to backup your tai folder for example)

restore to factory defaults the 3.60, then go to henkaku website, and from vita shell install the update and it will install enso (making sure this is performed with official memory card in unit), then put back in the sd2vita after adding the plugins back into the tai folder

all good and well, but if you can't use the backup of the plugins folder from the mlthaku install of the sd2vita plugin you need to use a updated plugin or manual one (that hasn't been tested as much)

(there's a chance you may not be able to update the 3.65 vita to 3.67 when it is released because you are not going from 3.60 firmware)

(its totally your choice to update and leave the safety of 3.60 before 3.67 is released, already, there is no way to fix a problem if you cause one by modifying files or etc. without upgrading to official firmware because you cannot just reinstall the 3.65 package ............... I just own a few games on my official vita, so its not worth the risk, because its not doing much, very good job though, hopefully there is more in the next few months or next year like the person said about releasing 3.67 for henkaku)

(If I just scared you away, then, take your time and check out the new games added to the nopaystation databases, i'm sure you don't have them all!)

 

[djricekcn]

1. If you are already using 3.60 HENkaku (Enso), uninstall all plugins and uninstall the enso patch. It is recommended to first unlink the Memory Card in HENkaku Settings before you uninstall, so that your Memory Card won't be restricted afterwards due to the spoofed version at ux0:id.dat. Uninstalling all plugins and the enso patch is extremely important, as they can interfere with the update process if enabled (the updater will notice you in case you have not uninstalled them correctly).

how do i do this?

 

[hypergreatthing]

how do i do this?

Run the enso installer. Hit 0 to get to the menu, hit triangle to uninstall enso.

You need to do this to run the updater. If the confusion is the wording "enso patch" I'm fairly sure you can just remove patch and read that as "remove enso".

If you're talking about unlinking the memory card, it's an option when running henkaku under henkaku-options->unlink memory card.

You actually don't need to do this step. Installing enso didn't screw with my psn settings.

If you ever run into the issue where the vita complains that the memory card isn't associated with the psn that's logged into the vita, you can always just go into henkaku settings and unlink the memory card then and reboot. Problem solved.

 

[hiroakihsu]

how do i do this?

Uninstall plugins = comment (with "#") or remove their lines out of the /tai/config.txt
Uninstall enso = install the installer app (enso.henkaku.xyz) if you deleted it afterwards, launch it, press the appropriate button
Update plugins afterwards = like installing them the first time = copy the *.s?prx to any folder (preferably ur0:/tai/) and list them again in /tai/config.txt under the appropriate section

As for HENkaku Settings, it's listed inside the system settings app.

 

[djricekcn]

For this

1. Make sure SD2Vita is not enabled and the SD Card is not inserted

Does this mean to edit that enso text file / plugin document?

 

[hypergreatthing]

For this
Does this mean to edit that enso text file / plugin document?

config.txt in the ur0:/tai folder. Put hash tags in front of the plugins you installed (ur0:tai/gamesd.skprx for example - change it to #ur0:tai/gamesd.skprx).

Before doing any of this you're going to need a sony memory card to use to install the updater on to once you comment out the plugin for the sd2vita.

 

[djricekcn]

thanks guys, I'll try this when i get home.

Just one thing, is there any possible way that 3.65 installs without Enso by doing the steps closely on https://vita.cfw.guide/more/updating-to-henkaku-enso-3.65/ ? I.E. a file not loading properly

 

[hypergreatthing]

thanks guys, I'll try this when i get home.

Just one thing, is there any possible way that 3.65 installs without Enso by doing the steps closely on https://vita.cfw.guide/more/updating-to-henkaku-enso-3.65/ ? I.E. a file not loading properly

No idea. I think the updater has a fairly good success rate that if you follow the steps it should work. Like anything homebrew/enso related your warranty was out the door when you even thought about henkaku so there's always a chance of ending up with a brick.
With the updater however i believe it does check the file integrity of the update file and seems like they put in a bunch of checks into the update process. There's also a bunch of checks they put in place to make sure the system is cleanly rebooted before applying the update.

 

[djricekcn]

Sorry, another thing.

This is more of a curious thing but since I can't find any reason....

I have multiple Vita's but my Vita TV in particular is used for mainly classic console stuff and 0 (zero) vita games. Is there any advantages to update the Vita TV if this is the case for the time being at least (currently on 3.60 enso)?