Hacking HENkaku Enso Source Code Released

[Deleted member 381889]

Molecule released the HENkaku Enso source code today, 6 months after its original release. HENkaku Enso is a consistent permament CFW exploit for the PS Vita, which installs HENkaku on boot. HENkaku allows you to install custom, user-made applications onto your console, including emulators and other tools. If you are looking to hack your PS Vita or PSTV, follow this guide.

Molecule advises you to not use the source, and to use the pre-built package on their website, as installing modified source code may result in an unrecoverable brick and your device will be made useless. They say that "even if you just change the logo, there's a good chance you will perma-brick your Vita". You have been warned.

You can find yifan_lu's writeup of Enso here.

You need vitasdk.

1. make the payload
2. Copy fat.bin to installer/res
3. CMake the installer mkdir build && cd build && cmake .. && make

Firmware specific offsets are in first.c and nsbl.h. Logo is raw framebuffer data gzipped. If you make this too big (bigger than original logo size), you WILL perma-brick your Vita.

The source is for advanced users only. Users should download the prebuilt package. If something goes wrong, you WILL perma-brick your Vita. There is no recovery, even if you have a hardware mod. The only possible recovery is if you have a hardware mod and you dump the eMMC before getting bricked, then you can restore the dump. Dumps are device-specific and encrypted with a device-specific key.

Again, even if you just change the logo, there's a good chance you will perma-brick your Vita. You have been warned.

GitHub

 

[KiiWii]

Very cool! Custom boot logos!

Shame I just sold my Vita.....

 

[nero99]

of all the times to not have a vita.

 

[gnmmarechal]

Very cool! Custom boot logos!

Shame I just sold my Vita.....

Custom boot logos he says

When it is advised not to do it specifically lul

 

[KiiWii]

Custom boot logos he says

When it is advised not to do it specifically lul

More recently: Advised not to exceed the file size.....

 

[gnmmarechal]

More recently: Advised not to exceed the file size.....

I can expect people not to follow that and brick lul (isn't that how it usually goes)

 

[Billy Acuña]

Custom boot logos he says

When it is advised not to do it specifically lul

Someone can make it to load a custom boot logo if found in ux0/uma0, if not found then load default molecular's logo.

 

[OperationNT]

I think you don't even have file system management when the Enso logo is displayed (you are really far from ux0/uma0 partition mount at this moment of the boot process).

 

[ScarletDreamz]

Does Henkaku enso counts as a Custom Firmware or a Signature Patcher?

 

[OperationNT]

From what I understand (don't hesitate to correct me if I am wrong), it is the "equivalent" of A9LH on 3DS: an "unclean way" to patch the boot process.

This "unclean way" should even works up to 3.65 (included) but it requires a kernel exploit in order to apply the modifications (on the MBR and the bootloader):
http://www.logic-sunrise.com/news-973321-vita-yifan-lu-redonne-de-lespoir-sur-les-fw-361-a-365.html

 

[Billy Acuña]

I think you don't even have file system management when the Enso logo is displayed (you are really far from ux0/uma0 partition mount at this moment of the boot process).

Damn, I completly forgot the FS stuff init [emoji53]

Edit: But isn't Enso doing FS init while loading kernel plugins?

Edit: Nvm, looks like Enso is just an simple bootstrap which loads your alreally installed Henkaku which loads your plugins.

 

[Deleted member 381889]

Damn, I completly forgot the FS stuff init [emoji53]

Edit: But isn't Enso doing FS init while loading kernel plugins?

That's taiHENkaku, not Enso

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

Edit: Nvm, looks like Enso is just an simple bootstrap which loads your alreally installed Henkaku which loads your plugins.

yup

 

[SKGleba]

I think you don't even have file system management when the Enso logo is displayed (you are really far from ux0/uma0 partition mount at this moment of the boot process).

You can use ux

Someone can make it to load a custom boot logo if found in ux0/uma0, if not found then load default molecular's logo.

its not a jpg/png image.
Quate from dev wiki about sceDisplay: "
Embedded in this module is also the boot logo (the PS logo seen on boot) which is gzipped. On module_start, after setting up the drivers, it gunzips the logo into the SceCamera SRAM (which is unused at this time since camera is not enabled yet). Then it sets the framebuffer to the camera SRAM and turns the brightness up in incremental levels."

 

[DinohScene]

As much as I'd like to modify the bootlogo to Cat's paw, it's best to leave it alone.
To bad there's no brick recovery/hardware NAND access.

 

[Ryccardo]

To bad there's no brick recovery/hardware NAND access.

There is, actually (limited to a 100% backup valid for the exact same board only, but enough for this) - it's exactly the same as a 3DS hardmod, but the pins are all small (no testpoints)

 

[DinohScene]

There is, actually (limited to a 100% backup valid for the exact same board only, but enough for this) - it's exactly the same as a 3DS hardmod, but the pins are all small (no testpoints)

Now that you mention it, I did see something like that yeh.