Hacking pstv enso problem after modoru 3.65 downgrade from 3.70 trinity

[ym2612]

originally i updated to ofw 3.65, used auto-hencore with enso and all worked well for months.
now with trinity available i thought it might be a good idea to "upgrade", so i just formatted the memory card via recovery and updated to ofw 3.70 via recovery menu usb option.
used fin-trinity and was disappointed that there was no permanent way to apply trinity.
so i downgraded with modoru to ofw 3.65, used auto-hencore again but when i run enso it justs exits after some seconds with the error "failed kernel module 0x8002d003"
i tried everything the web recommends (factory reset, delete taihen config, used same enso version as i originally used the first time, updater365.vpk with custom firmware) but nothing works.

here are some questions i can not answer:

since i formatted and up/downgraded several times etc. it seems some enso code still survived somewhere?
since the error is about missing kernel module, which module would that be? i have found no boot_config.txt, just config.txt with default henkaku modules only.
what is this update.vpk with custom firmware, the docs mention something about bootloader code???
since enso gives me that error, i can not use the enso uninstall option. so how can i uninstall enso now?

please, can somebody help me with this problem? thank you!!!

 

[kaymynd]

originally i updated to ofw 3.65, used auto-hencore with enso and all worked well for months.
now with trinity available i thought it might be a good idea to "upgrade", so i just formatted the memory card via recovery and updated to ofw 3.70 via recovery menu usb option.
used fin-trinity and was disappointed that there was no permanent way to apply trinity.
so i downgraded with modoru to ofw 3.65, used auto-hencore again but when i run enso it justs exits after some seconds with the error "failed kernel module 0x8002d003"
i tried everything the web recommends (factory reset, delete taihen config, used same enso version as i originally used the first time, updater365.vpk with custom firmware) but nothing works.

here are some questions i can not answer:

since i formatted and up/downgraded several times etc. it seems some enso code still survived somewhere?
since the error is about missing kernel module, which module would that be? i have found no boot_config.txt, just config.txt with default henkaku modules only.
what is this update.vpk with custom firmware, the docs mention something about bootloader code???
since enso gives me that error, i can not use the enso uninstall option. so how can i uninstall enso now?

please, can somebody help me with this problem? thank you!!!

Try to reinstall current firmware through recovery in qcma.

 

[ym2612]

Try to reinstall current firmware through recovery in qcma.

thanks for your quick reply, but i am not sure how to follow. do you mean to copy ofw 3.65 PSVUPDAT.PUP to qcma updates folder and transfer with content manager from pc to pstv?

 

[kaymynd]

thanks for your quick reply, but i am not sure how to follow. do you mean to copy ofw 3.65 PSVUPDAT.PUP to qcma updates folder and transfer with content manager from pc to pstv?

Yes theres also some options in qcma settings you have to change to the fw you're going to reinstall, here's an old guide only thing is that you have to install in recovery instead of vita settings for it to work.

Spoiler

https://www.guidingtech.com/42173/offline-update-ps-vita-firmware/

 

[Deleted User]

thanks for your quick reply, but i am not sure how to follow. do you mean to copy ofw 3.65 PSVUPDAT.PUP to qcma updates folder and transfer with content manager from pc to pstv?

If your on 3.65 use enso 3.65 non updater

 

[ym2612]

If your on 3.65 use enso 3.65 non updater

do you mean https://github.com/TheOfficialFloW/update365 ? if yes, this also gives the failed kernel module error. or maybe try install update365 on running ofw365 ?

 

[Hayato213]

do you mean https://github.com/TheOfficialFloW/update365 ? if yes, this also gives the failed kernel module error.

That was an one way trip updating from 3.60 to 3.65 for 3.60 users.

 

[Deleted User]

do you mean https://github.com/TheOfficialFloW/update365 ? if yes, this also gives the failed kernel module error. or maybe try install update365 on running ofw365 ?

3.65 perm non updater

 

[Vinceherman]

as far as i am aware the kernal message relates to using incorrect Enso firmware version, but you've tried both Enso firmware options? Vita Homebrewbrowser best option for picking the right version, try there first.

Just delete the current enso you have first (hold down on the icon and delete).

So if neither Enso firmware versions work, I think your best bet is to format, update to 3.70, run trinity again then downgrade down to 3.60 and goto https://henkaku.xyz/ on your Vita browser, and go from there

 

[godreborn]

yes, bits of ensou still remain even after uninstalling it. that's why you'll get some sort of checksum error when reinstalling. it will still install correctly, but that error can be scary.

edit: your problem may be not uninstalling ensou first. I think it says to when updating from 3.60 ensou to 3.65 ensou. bits will remain, but it can be cleaned with a firmware install.

 

[paulzheng]

originally i updated to ofw 3.65, used auto-hencore with enso and all worked well for months.
now with trinity available i thought it might be a good idea to "upgrade", so i just formatted the memory card via recovery and updated to ofw 3.70 via recovery menu usb option.
used fin-trinity and was disappointed that there was no permanent way to apply trinity.
so i downgraded with modoru to ofw 3.65, used auto-hencore again but when i run enso it justs exits after some seconds with the error "failed kernel module 0x8002d003"
i tried everything the web recommends (factory reset, delete taihen config, used same enso version as i originally used the first time, updater365.vpk with custom firmware) but nothing works.

here are some questions i can not answer:

since i formatted and up/downgraded several times etc. it seems some enso code still survived somewhere?
since the error is about missing kernel module, which module would that be? i have found no boot_config.txt, just config.txt with default henkaku modules only.
what is this update.vpk with custom firmware, the docs mention something about bootloader code???
since enso gives me that error, i can not use the enso uninstall option. so how can i uninstall enso now?

please, can somebody help me with this problem? thank you!!!

reinstall your current firmware with qcma.

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

thanks for your quick reply, but i am not sure how to follow. do you mean to copy ofw 3.65 PSVUPDAT.PUP to qcma updates folder and transfer with content manager from pc to pstv?

what kind of your psvita. a psvita TV?

 

[CTR640]

Why the heck would you "upgrade" to 3.70?? TheFlow even mentioned there is no permanent cfw on his github so why bother?
It wasn't a good idea at all, there is a chance you can lose the ability to hack your vita.

Congratulations, your device is now able to run homebrews. It is highly suggested that you downgrade your device to either firmware 3.60 or 3.65/3.67/3.68 using modoru. On 3.60, you can use HENkaku and on 3.65/3.67/3.68 you can use h-encore. If you don't downgrade your device now, you may lose the ability to launch Trinity later and therefore not be able to hack your device anymore.

enso/permanent hack

• "Can I install enso on 3.69 or 3.70?" - Not on these firmwares, but you can downgrade to firmware 3.60/3.65 using modoru and then install enso.

 

[ym2612]

as far as i am aware the kernal message relates to using incorrect Enso firmware version, but you've tried both Enso firmware options? Vita Homebrewbrowser best option for picking the right version, try there first.

problem solved! thanks to your advice i tried installing enso with vhbb and it worked!!! now to be clear: downloading enso v1.1 for ofw 3.65 from github, transfering enso.vpk via ftp and installing enso via vitashell does not work and throws the error. downloading and installing enso v1.1 for ofw 3.65 via vhbb does work. so either enso version is different from github or vhbb installs vpk different than vitashell?

anyways, enso is working again and i'm relieved that my totally unneeded upgrade to 3.70 and downgrade to 3.65 again did not end in a bricked pstv.

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

edit: your problem may be not uninstalling ensou first. I think it says to when updating from 3.60 ensou to 3.65 ensou. bits will remain, but it can be cleaned with a firmware install.

yes, now i know, uninstalling enso first is the proper way, also the enso warning about "permanent changes" is to take seriously, i wrongly assumed formatting the internal memory and re-flashing the firmware would wipe everything!

originally my pstv never was on 3.60, factory firmware was 3.20 and i upgraded to ofw 3.65 via recovery and installed auto h-encore and enso.

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

Why the heck would you "upgrade" to 3.70?? TheFlow even mentioned there is no permanent cfw on his github so why bother?
It wasn't a good idea at all, there is a chance you can lose the ability to hack your vita.

yeah it was stupid and i had to invest some time to undo my mistake, but if i uninstalled enso in the first place then i guess it should not matter to up/downgrade?

 

[CTR640]

@ym2612 It was never needed to update to 3.70. You would end up making it impossible to hack your device if Sony patches it or when you maybe some day have to reset your device and thus, no more using the psp demo to install the hack as Sony maybe released 3.71. It would require you to update. If you either have 3.60 or 3.65, stick to it, don't update because "higher" number is better.

 

[ym2612]

maybe thats why the github enso does not work???

enso v1.1 download from github: build on 2018-08-25T22:16:37Z
enso v1.1 download with vhbb: build on 2018-08-26T10:35:32Z

 

[Boydy86]

maybe thats why the github enso does not work???

enso v1.1 download from github: build on 2018-08-25T22:16:37Z
enso v1.1 download with vhbb: build on 2018-08-26T10:35:32Z

Can you get both files on your computer and run them both through MD5 checker?

 

[ym2612]

//github v1.1
enso.vpk (61.977 Bytes)
md5: B325206344041CA707918538D48249A8

//vhbb v1.1
enso.vpk (62.293 Bytes)
md5: DCA59CF5FD07F6550678432333041705

 

[Boydy86]

//github v1.1
enso.vpk (61.977 Bytes)
md5: B325206344041CA707918538D48249A8

//vhbb v1.1
enso.vpk (62.293 Bytes)
md5: DCA59CF5FD07F6550678432333041705

Cheers mate, I've never used VHBB. That is very interesting... Somethings different.