Hacking PS TV Brick?

[Gaara4]

I follow the instructions of the 3.65 HENkaku Ensō Updater github website to update my PS TV to 3.65. Before i start with this, i format my sd card and reinstall 3.60 to get a clean system. After that i install henkaku and vita shell with the updater + Update. Of course i do the backup and reboot the system to directly start the updater. I get the message to uninstall enso which i tought would be gone because i reinstall the firmware. So i install the enso install and let it uninstall.
The system trys to reboot and i only get a black screen. I try to get into the recovery menü, but nothing really works. My TV receive some output from the HDMI port, but i get no signal.

Any ideas what i could do, or what i do wrong?

 

[Ryccardo]

You're the 3rd person I know about who this happened to (the other 2 being me and someone from that reddit site - both of us have handheld models though, in fact I later successfully did it on a PSTV), as you may have noticed it's not the fault of 3.65 anything but only of the Enso uninstallation. I wrote to Yifan back then, but she had no real idea of what could have happened

If you have a nand backup of your console on 3.60 (yeah, sure) you can reinstall it via hardmod, which is an euphemism for new motherboard

 

[SKGleba]

Mbr damage, happens at uninstallation, theres no fix for that.

 

[Tony_93]

That happened to me once while on 3.60, my TV "received signal" (only a black screen), even the power button would not work, had to unplug it from AC everytime and the system would try to autp start everytime I plugged the AC.

I was able to get into recovery mode eventually and formatted the system, which then of choose removed all hacks and had to start over. If you don't mind shipping it to me could take a look at it, good luck getting to come back to life either way

 

[godreborn]

uninstalling ensou seems to be extremely buggy. I uninstalled it from my pstv when I thought the ensou logo was supposed to appear. however, after doing so, all default icons disappeared. I think it also said I had to reformat, but I don't believe that fixed it. I think I was only able to fix it by reinstalling the firmware. I haven't uninstalled ensou since then.

 

[GothicIII]

Oh man what kind of shit is this? I uninstalled enso with the vpk from enso.henkaku.xyz and updated over usb.

Black screen nothing works. Thank you


I am so so mad right now at the developer!

 

[Hayato213]

Oh man what kind of shit is this? I uninstalled enso with the vpk from enso.henkaku.xyz and updated over usb.

Black screen nothing works. Thank you

What you used to update?

 

[GothicIII]

What you used to update?

Used the 3.65 update file from vita.guide

What kind of lame shit is this? Recovery is working but all options do nothing. They went successful through but the device won't boot. I thought it was patched?
Who is responsble for this?

 

[Hayato213]

Used the 3.65 update file from vita.guide

Did you powered it while it is updating?

 

[GothicIII]

Did you powered it while it is updating?

Yes I had to powercycle it because it got a blackscreen after reaching 100%. It restarts after the update is installed and stays forever at a black screen.
What a waste of hardware. I have all my PSP games installed on it.

 

[Hayato213]

Yes I had to powercycle it because it got a blackscreen after reaching 100%.

You shouldn't , usually it brick if it shut off when it updating, probably you brick im afraid.

 

[GothicIII]

You shouldn't , usually it brick if it shut off when it updating, probably you brick im afraid.

After staying like that for over 20 minutes? No this is the fault of uninstalling enso which messed around with mbr.

I am so mad! My ass the problem is not known. I wanted to upgrade to 3.65 and if enso is uninstalled and the firmware updated then you brick. Thank you very much for this information.

 

[Hayato213]

After staying like that for over 20 minutes? No this is the fault of uninstalling enso which messed around with mbr.

I am so mad! My ass the problem is not known. I wanted to upgrade to 3.65 and if enso is uninstalled and the firmware updated then you brick. Thank you very much for this information.

Uninstalling enso before updating that is correct, but you can't shut off while it is updating the firmware, that result in brick because it haven't finish writing to system file that it needs to, on the guide it said it should automatically restart, I don't get why you attempt to update when you can do everything on 3.60 that 3.65 can do.

 

[GothicIII]

Uninstalling enso before updating that is correct, but you can't shut off while it is updating the firmware, that result in brick because it haven't finish writing to system file that it needs to, on the guide it said it should automatically restart, I don't get why you attempt to update when you can do everything on 3.60 that 3.65 can do.

I haven't done anything wrong. Just wanted to update to 3.65 to experiment with psn activation.

-Got enso.vpk from enso.henkaku.xyz to uninstall 3.60 enso. If you use the vpk from the github page (from TheFlow which is for 3.65) you'll get "Failed to load kernel module: 0x8002d003"
-uninstall was successful rebooting pstv works.
-initiated 3.65 update installation through recovery mode (copy to usbdrive:/PSVITA/UPDATE/PSVUPDATE.PUP)
-update copies successful and the update is installed
-after reaching 100% the device automatically reboots but the device won't show the warning screen anymore. You are bricked. The controller is recognised over usb and connects successful but the pstv doesn't show any screen output unless you boot into recovery.

All options in recovery mode don't help to get the pstv properly booting again.

EDIT: Replacing it will cost me over 120$+shipping. It was bundled with my PS4.
EDIT2: I opened an issue on Github for enso. It seems it is not the fault of enso since I can boot recovery mode.

TL : DR If you have a working Vita setup never update it. Even removing everything associated with CFW (plugins, files etc) the brick chance is not zero.

 

[Glyptofane]

Wow, I guess I'm going to be on 3.60 forever then.

 

[GothicIII]

Just for future reference. My setup was like this:

-storagemgr (to use sd2vita)
-renpdrm (to use my forcefully deactivated act.dat and playing my bought games)
-rotm0 (readonly tm0 partition so sony can't delete my account files)

Of course I removed everything beforehand and booted the console from internal storage with every plugin disabled.

 

[GothicIII]

Ok I went do discord and wrote down everything I knew.

My brick occured eventually because updateblocker messed with the vs0 filesystem and didn't restore it properly. (I didn't have any other homebrew installed which messed with that)
After that the firmware updater from recovery menu stubled upon it while installing and should have ended with errors but ended successful. That made my PSTV unbootable.

Since I can't test it anymore I got following information from >•SKGleba•< to recover from that type of brick:

1) restore
2) update to a different fw, interrupt the update in half of updating (75%)
3) update with a pd pup
4) retry update main
This will force clean, because vs0 filesystem will be corrupted
(Because of how the updater works)

I don't know if it works but if somebody has the same symptoms then he could try that as a last resort since there is no other way to recover from this.

 

[Ryccardo]

-Got enso.vpk from enso.henkaku.xyz to uninstall 3.60 enso.

It seems it is not the fault of enso since I can boot recovery mode.

Yeah, if you used the new Enso installer to fully remove it, it's not going to be the issue that happened to me (and indeed those Enso uninstallation bricks result in a completely unbootable console)

Too bad for you, but many thanks in the name of the public for sharing what you figured out - free speech was intended for tech documentation
And you got the "satisfaction" of having discovered what was the actual cause

 

[kaymynd]

As long as you can access recovery mode you can always just reinstall firmware with qcma, thats should fix your problem.

 

[GothicIII]

As long as you can access recovery mode you can always just reinstall firmware with qcma, thats should fix your problem.

It 'should' but it didn't. Reinstalling from recovery mode didn't fix the black screen.