theofficialflow / update365 Goto Github PK

Custom Firmware 3.65 HENkaku Ensō Updater for PS Vita

Makefile 0.28% C 85.58% Python 1.04% CMake 3.38% C++ 9.72%

update365's Introduction

3.65 HENkaku Ensō Updater

This software is outdated, please use the real enso installer

Custom Firmware 3.65 HENkaku Ensō is a port of henkaku to the latest possible firmware that does still have the bootloader vulnerability.

Pros and cons

Pros

You will be able to access the PSN store, activate your device and download your purchased games again (only as long as Sony doesn't decide to release a new update that prevents you from doing that).
You will be able to play all games that were released for firmwares 3.61-3.65.

Cons

You will not be able to downgrade back to 3.60 if you find that this custom firmware doesn't suit you.
You can lose the ability to run homebrews, if you modify the OS and end up in a semi-brick where you are forced to reinstall the firmware. This should however not happen to a regular user, but I'd rather not install applications that modify read-only partitions like os0: or vs0:.
Some applications may not work on the new firmware and need to be ported.

Instructions

If you are on a firmware below 3.60, update to 3.60 and install henkaku.
Update VitaShell to v1.82 or later (if you get an error when trying to install the vpk, simply rename the vpk to zip and manually copy the eboot.bin file to ux0:app/VITASHELL/eboot.bin).
Make a CMA backup of VitaShell. This is very important, since if you lose VitaShell, this is the way you restore it.
Download updater.vpk and PSP2UPDAT.PUP.
Install updater.vpk using VitaShell and put the PSP2UPDAT.PUP file at ux0:app/UPDATE365/PSP2UPDAT.PUP.
If you have already been 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 (NOT FORMAT) just before you uninstall enso, 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).
Reboot your device, start HENkaku and directly launch the updater, without launching anything else before like VitaShell or Adrenaline (since they start kernel modules). Also make sure that your battery is at least at 50%.
Follow the instructions on screen and enjoy the update process.
When the updater finishes flashing the new firmware, custom modules will be written to vs0:tai and the bootloader hack injected to the eMMC. You should now be on 3.65 HENkaku Ensō.

FAQ

"Are Adrenaline, DownloadEnabler, NoNpDrm and SD2VITA compatible on 3.65?" - Yes they have all been updated and are available under my repositories.
"Is it risky to perform this update?" - All my betatesters have successfully updated and have no issues so far. The updater has been designed carefully, so you don't need to worry.
"Will I lose the hack if I format my Memory Card or restore the systems settings?" - No, you can nearly do everything with your device and you will not lose HENkaku. You must just NOT reinstall the 3.65 PUP.
"I have installed a bad plugin and now my device doesn't boot anymore" - Try to enter the Safe Mode and choose 2. Rebuild Database. This will allow you to boot the device with plugins disabled and fresh config.txt files.
"Will I be able to hack my device that is on 3.65/3.67?" - Not with this software. I will release my exploit chain by the end of this year or next, so you have to be patient.
"I have lost molecularShell/VitaShell!" - You proceeded through the updater without carefully reading it. Congratulations! You can simply restore it by using CMA and psvimgtools, but since you didn't made a backup as it was CLEARLY stated in the updater, it's your own fault and you will now have to figure out yourself how to solve this problem.
"I forgot to unlink the Memory Card before uninstalling enso now I can't use it!" - simply start HENkaku again through the browser, open settings app and then choose HENkaku Settings.
"I have only got a SD2VITA but no Memory Card, how can I update?" - If you are using a PS Vita Slim or PSTV, you can just use the Internal Storage to update, otherwise you can't. When you use SD2VITA you have to use a plugin for that. But plugins are dangerous since they can interfere with the update process which can lead to a brick in the worst case. An other reason is that I want to prevent this scenario: Imagine an user forgets to update the SD2VITA plugin and updates to 3.65, then realizes that the driver is unsupported. He will then be forced to buy a Memory Card in order to do anything with the new custom firmware.

Donation

If you like my work and want to support future projects, you can make a small donation with via bitcoin 361jRJtjppd2iyaAhBGjf9GUCWnunxtZ49. Thank you!

Compiling

Compile enso, henkaku and taihen, then put the binaries fat.bin, henkaku.suprx, henkaku.skprx and taihen.skprx at installer/res. Then you can compile the installer. It is however very dangerous to do this by yourself if you don't know what you're doing. One mistake means a bricked device. If you want to only compile the installer, then simply open updater.vpk as zip file and use the three binaries from there.

Credits

molecule for their original work.
Mathieulh for providing his devkit.
Freakler for his LiveArea design.

update365's People

Contributors

Stargazers

Watchers

update365's Issues

PSPUPDAT.PUP disappears

While still on 3.6 firmware (I'm now on 3.65, so won't risk testing further)

When:

PSPUPDAT.PUP is in ux0:app/UPDATE365/
VitaShell.vpk (1.83) is in ux0:VPK/
updater.vpk is in ux0:VPK/

From MolecularShell install VitaShell.vpk
Exit MolecularShell and enter VitaShell.
in VitaShell install updater.vpk.

I'm not sure if it's VitaShell install, or the updater's install, but on of the two deletes PSPUPDAT.PUP, and populates the ux0:app/UPDATE365/ with:

eboot.bin
kernel.skprx
kernel2.skprx
user.suprx
/livearea/contents/icon.png
/livearea/contents/param.sfo
sce_sys/livearea/contents/bg0.png
sce_sys/livearea/contents/startup.png
sce_sys/livearea/contents/template.xml
sce_sys/package/head.bin
sce_sys/package/work.bin

Requiring you to re-upload PSPUPDAT.PUP to the ux0:app/UPDATE365/ folder.

This happened twice on a PSTV while trying to get the updater to work, so not a one-time glitch.

Save data is not read by application

after upgrading to 3.65 applications' save data is still present but not read by any application, thus prompting to start "New Game" for each title. The weird thing is that the save data is still there in ux0:user/00/savedata. I haven't done anything else so i suppose this issue comes with upgrading the fw? I appriciate you work so much, keep it up. Cheers.

i got some old data after update with h-encore

i find some old files from the update365 after patch with h-encore:
vs0:tai/ (all files are from henkaku)
ud0:PSP2UPDATE/ensoswu.self and ENSOUPDAT.PUP

is safe to delete?? and how delete it in vs0??

uma0 not accessible after activating sd2vita for CFW 3.65

I was able to access uma0 after fresh install CFW 3.65 but when I turned on gamesd.skprx from https://github.com/xyzz/gamecard-microsd/releases/tag/v1.1 it does not show up on MolecularShell, VitaShell 1.82, even on Adrenaline v6.1

Enso Brick - PLEASE fix this terrible program

So i have installed enso on my 3.65 vita, the OFW i left it on when i purchased it on Amazon, i had so much newbie trouble trying to get nonpdrm to work after installing sd2vita, i tried to reinstall 3.65 ofw thinking i made a mistake or an error during the process of installing all these plugins addons apps etc. I finally gave up and updated to 3.68 thinking fck enso it isnt worth the trouble, so the next day i wake up get all my stuff installed again, (but i didnt reinstall adrenaline) ignoring pkgj, since i used Nopaystation from my pc and USB'd Call of duty over to my vita, i refresh the live area after the usb transfer completes, no call of duty (not sure wtf is going on still having issues apparently) so i notice i have Adrenaline back and the Enso Bubble, both back! how? idk i really dont so i go to Enso, i use the enso-built in uninstaller, it succeededs and forces a restart. Now i have reached the BRICKED phase, where my system will power on but show a black screen. I have tried holding the power button for 20+ seconds, it only cycles the power from on to off and right back to on and still sits on a black screen. A fix would be nice, i bought this ps vita, an sd card and an sd2vita last week, hoping to play some games now ive got 150$ down the shtter and a dead psv. Please fix Enso so this doesnt occur to other users!
this appears to be the wrong Enso program, i DID NOT use this program i used the 1.0 release version of 3.65 enso
this version of enso to be specific is the cuplrit that i used that f*cked my vita over
https://github.com/TheOfficialFloW/enso/releases
if anyone has a fix for a bricked vita thru enso's unreliable flaws id be glad to try it. also i didnt know anywhere else to contact theflow, considering i dont have twitter

also, what more can/shall i do with my bricked vita? bring it to gamestop and tell them i dropped it and the screen no longer works and have them give me like 10$ for it? (im not the real thief here... we all know gamestop policy is a joke on returns)

The file is corrupt. (C1-2738-0)

I keep getting this error when trying to run the 3.65 updater. I'm trying to run this on a PSTV.

I'm following this video for running the update: https://www.youtube.com/watch?v=itG8GyErwyg

I've redownloaded both pspupdat.pup and updater.vpk several times, and keep getting this error.

Could I get a CRC and/or MD5 for both files to hopefully get this working?

Rebooting relinks memory card

In the guide it says to unlink the memory card... and then reboot. Rebooting relinks the memory card, so you need to disable PSN spoofing beforehand.

update365 working with VitaShell 1.9?

Just the topic. I think it will. Or should I download 1.82?

ur0:tai config.txt not working?

Has anyone been able to get plugins working through the ur0:tai/config.txt? I deleted ux0:tai/config.txt

Trying to get StorageMgr.skprx working, but it's not even making the log file which makes me think the plugin isn't loading at all. I'm using their latest compile which says 3.65 compatibility, but nothing is happening.

an FTP issue in vitashell v1.94

Recently i discovered that while using vitashell and creating a FTP connection, if you leave it on in the background and install a package for instance after the installation is done vitashell forgets the FTP as if it wasnt turned on. it shouldnt happen since when you have FTP on vitashell wont let you exit till you close it. tested twice on 3.60 henakku enso with sd2vita.

Cannot Mount Memory Card to um0

Hi,
I think there's a closed issue about this and no result at all.
Maybe this isn't the right place to ask about why we can't mount memory card as um0 while using SD2VITA as ux0 (I should ask this at SD2VITA forum). But this issue happened when using 3.65, and we cannot mount um0 because this slot, for USB flash. Maybe someone had figured it out how to change this config so will not be overlapped by this setting.
Thanks.

Never mind. I think I'm so stupid lol.

Cant get Molecularshell or Vitashell back after "Restore this system"

"I have installed a bad plugin and now my device doesn't boot anymore" - Try to enter "Restore this system"
After that's done, there is no molecularshell or vitashell. Henkaku and Enso are still installed though.Any way to fix it?

People can update with an older version of Vitashell installed on their system

Because Vitashell is not installed by the enso installer and the auto update feature is broken as github enforced tls 2.0 (or the vita is not connected online), some users update to enso 3.65 while having a version of vitashell incompatible with 3.65, leaving them in dissaray. The only workaround to this issue is to import a modified CMA backup with the latest version of Vitashell in it. Vitashell should be installed by the enso installer or installing the latest version of Vitashell should be clearly mentioned in the readme.

Cant get Molecularshell or Vitashell back after database rebuild

In the FAQ it states:

"I have installed a bad plugin and now my device doesn't boot anymore" - Try to enter the Safe Mode and choose 2. Rebuild Database. This will allow you to boot the device with plugins disabled and fresh config.txt files.

After that's done, there is no molecularshell or vitashell. Henkaku and Enso are still installed though, just not sure how to get them back since the web browser exploit returns an error and won't re-install the app.

Network Operator bubble missing after update

Thank you for making this update possible, TheFloW. The only issue I ran into was that my Network Operator bubble disappeared after completing the update. I did exactly as you specified for the update process starting from 3.60, and everything was intact except for that bubble.

This was on a PCH-1100 Japanese 3G model with a standard official 16 GB memory card and no sim card inserted. The Network Operator bubble showed "NTT Docomo", which indicates that it's associated with NPXS10042. I've already tried refreshing the LiveArea via VitaShell and rebuilding the database, but it still hasn't come back.

clean up after install

can I delete the updater app and the content of ux0:/app/UPDATE365/ after the update?

What's the cleanest way to get back to stock 3.65?

I want to reapply stock FW 3.65 and use h-encore.
What should I consider? Or just apply stock FW with FWupdater?

3.65 henkaku enso updater says file is corrupt.

I contacted you over at reddit about this as well, but the henkaku enso updater is constantly telling me the update file is corrupt when I go to install it. I have it placed at ux0:app under the UPDATE365 folder you specified. I have downloaded this file at least 3 times from your own release page here on github, and nowhere else. Neither time did it seem to want to work. Just the file is corrupt from the updater. I've only transferred the file over via vitashell 1.82 to it's proper location via usb drive after download from my pc. Just to be clear I have restarted and re-installed henkaku after use of vitashell 1.82 each time. So it's definitely not a error on my end.

So I got no idea what's going on. Only thing as I noted on reddit that is different is the file sizes. Your release page here says the file should be 128MB where as vitashell and molecular shell (I checked both) report it at 127.56 I believe the exact figure was. Just wanted to let you know about this as I'm sure I'm not the only one with this peculiar issue. Thanks.

i cant connect pc on 3.65 enso

i just need some helps about my brother ps vita's problem. He updated his ps vita from 3.60 to 3.65 enso yesterday but he lost the vitashell and molecular, the system setting shows the device on 3.65 enso, we can spoofing to psn but installing vpks. He asks me to fix it so I google and find a way to get vitashell by psvimgtoolfrontend but a problem occurs : i can't connect his ps vita to pc through either qcma or cma with a notification (https://drive.google.com/open?id=1N1hildGXA4GngP0P7o4l7lx5-N23cKhP). I checked the cable and pc , they works well with my ps vita so the problem is just came from my brother's ps vita. I rebuilded the database, restored the device , formated memcard but nothing changes . Any solution ?

Can't see memory card??

I purchased a 64 gb memory card after upgrading to 3.65 ... I cannot get the device to recognize it...

As in I did not have a memory card before the upgrade.

Any ideas?
Thanks
K