pstv enso problem after modoru 3.65 downgrade from 3.70 trinity

Discussion in 'PS Vita - Hacking & Homebrew' started by ym2612, May 16, 2019.

  1. ym2612
    OP

    ym2612 Advanced Member

    Newcomer
    1
    Jan 24, 2017
    Austria
    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!!!
     
  2. kaymynd

    kaymynd GBAtemp Regular

    Member
    3
    Sep 19, 2018
    United States
    Try to reinstall current firmware through recovery in qcma.
     
    ym2612 likes this.
  3. ym2612
    OP

    ym2612 Advanced Member

    Newcomer
    1
    Jan 24, 2017
    Austria
    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?
     
  4. kaymynd

    kaymynd GBAtemp Regular

    Member
    3
    Sep 19, 2018
    United States
    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.
     
  5. ModderFokker619

    ModderFokker619 GBAtemp Advanced Fan

    Member
    5
    Oct 2, 2015
    United States
    California
    If your on 3.65 use enso 3.65 non updater
     
    ym2612 likes this.
  6. ym2612
    OP

    ym2612 Advanced Member

    Newcomer
    1
    Jan 24, 2017
    Austria
    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 ?
     
    Last edited by ym2612, May 16, 2019
  7. Hayato213

    Hayato213 GBAtemp Psycho!

    Member
    10
    Dec 26, 2015
    United States
  8. ModderFokker619

    ModderFokker619 GBAtemp Advanced Fan

    Member
    5
    Oct 2, 2015
    United States
    California
  9. Vinceherman

    Vinceherman GBAtemp Regular

    Member
    3
    Feb 9, 2018
    United Kingdom
    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
     
    Last edited by Vinceherman, May 16, 2019
    ym2612 and ModderFokker619 like this.
  10. godreborn

    godreborn GBAtemp Guru

    Member
    10
    Oct 10, 2009
    United States
    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.
     
    Last edited by godreborn, May 16, 2019
  11. paulzheng

    paulzheng GBAtemp Regular

    Member
    2
    Dec 10, 2013
    China

    reinstall your current firmware with qcma.

    — Posts automatically merged - Please don't double post! —

    what kind of your psvita. a psvita TV?
     
  12. CTR640

    CTR640 GBAtemp Regular

    Member
    3
    Nov 24, 2018
    Netherlands
    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.

     
    Last edited by CTR640, May 17, 2019
    ym2612 likes this.
  13. ym2612
    OP

    ym2612 Advanced Member

    Newcomer
    1
    Jan 24, 2017
    Austria
    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.

    — Posts automatically merged - Please don't double post! —

    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.

    — Posts automatically merged - Please don't double post! —

    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?
     
    Last edited by ym2612, May 18, 2019
  14. CTR640

    CTR640 GBAtemp Regular

    Member
    3
    Nov 24, 2018
    Netherlands
    @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.
     
  15. ym2612
    OP

    ym2612 Advanced Member

    Newcomer
    1
    Jan 24, 2017
    Austria
    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
     
Loading...