Hacking Vita downgrader Moduru released
- Thread starter kristianity77
- Start date
- Views 9,738
- Replies 29
- Likes 2
3.68 Vita (pstv) (Soft Bricked by IMCunlock), not a big loss, I have two more working 3.60 and 3.65 (3.68 was very, very bad, to see it soft/hard bricked is no big deal, believe me, sad but, nothing important, it just happened!)
1. 3.68 with IMCunlock installed, no Official Memory Card, with sd2vita card
2. Henkaku Settings/ "unlink memory"
3. IMCunlock - select "0MB (ur0 2.5GB) option, to remove "IMCunlock"
4. Restart with No Official Memory Card, "IMCunlock removed" (no memory card or sd2vita plugged in)
5. (Reinstall 3.68 Firmware over 3.68 Firmware) (Turn off, then Hold Power Button until you enter into "recovery mode" ..... get to the screen where it askes for a "update by usb stick" .................... (formatted fat32 or exfat) ... create a folder named "PSVITA" on the USB flash drive. Inside that folder, create another folder named "UPDATE", inside the "UPDATE" folder, the "PSVUPDAT.PUP" for Official Firmware 3.68 will go inside there.
Soft Bricked, "context manager" always reports "0MB", official memory card will no identify, it will format, but will ask to format at power cycling, it never registers. (Step Number 3) ............. updated firmware to 3.69 ... then to 3.70 Firmware, same problem.(0MB Option, from the IMCunlock installer app, was the only way to remove it, I am the unlucky user on that, will the Mudoru also brick my vita? Guess I'll see)
...............
...............
...............
next try, 3.65 (pstv) on Enso (apparently you don't need to uninstall enso on 3.65 first, that was for 3.60 bricking bug ? brb)
...............
...............
...............
Going Forward
...............
1. (install HBinjector1.2 to run vita shell from system app) "unlinked sd2vita" from settings option, removed sd2vita
2. (using vita shell installed to system app from hbinjector 1.2) Add "Official Memory Card" to vita, or "moduru", when attempting to install without "official memory card", only "error 0x80010013" was given.
3. (Add 3.60 Official Firmware file, "P2P2UPDAT.PUP") ux0:app/MODORU000/PSP2UPDAT.PUP ... power cycle, then launch moduru
4. Success, downgraded to 3.60 Firmware! (gave error when I selected to transfer files from internal memory, after selecting NO it worked fine, right before normal boot) (Didn't use any "enso 3.65 uninstallers", apparently no risk of a brick there, which is good)
.........
# This file is used as an alternative if ux0:tai/config.txt is not found.
# For users plugins, you must refresh taiHEN from HENkaku Settings for
# changes to take place.
# For kernel plugins, you must reboot for changes to take place.
*KERNEL
# henkaku.skprx is hard-coded to load and is not listed here
*main
# main is a special titleid for SceShell
.........
Thats the "ur0:/tai/config file. In step 3, right before you power cycle to immediately install by running moduru, see there's nothing else but that on the file itself.
.........
.........
(Guess back to henkaku.xyz/go/ .... then the enso installer is run ... I'll just report that it worked)
.........
.........
(remove official memory card, power cycle) Restore this System, Delete All Data ............. https://Henkaku.xyz/go/ ... to install molecular shell (sometimes molecular shell won't install with memory card) ... downloadd this "https://enso.henkaku.xyz/" from your PC, the click the big grey box, then you'll have "enso.vpk", install that, setup your plugins, and add back your memory card with all your files, then your finished. (Everything Checks Out, guess i'm finished)
.........
.........
(well not just me, the IMCunlock, softlocked many vitas, no memory card usage or internal memory ........... so its a coaster, its not a big loss ............ now there are rumors the vita has a 800mhz mode, much like the 500mhz mode for #letmaidie killing ............... there are many goodies coming, especially considering the flow's 3.70 method, may fix all our troubles)
1. 3.68 with IMCunlock installed, no Official Memory Card, with sd2vita card
2. Henkaku Settings/ "unlink memory"
3. IMCunlock - select "0MB (ur0 2.5GB) option, to remove "IMCunlock"
4. Restart with No Official Memory Card, "IMCunlock removed" (no memory card or sd2vita plugged in)
5. (Reinstall 3.68 Firmware over 3.68 Firmware) (Turn off, then Hold Power Button until you enter into "recovery mode" ..... get to the screen where it askes for a "update by usb stick" .................... (formatted fat32 or exfat) ... create a folder named "PSVITA" on the USB flash drive. Inside that folder, create another folder named "UPDATE", inside the "UPDATE" folder, the "PSVUPDAT.PUP" for Official Firmware 3.68 will go inside there.
Soft Bricked, "context manager" always reports "0MB", official memory card will no identify, it will format, but will ask to format at power cycling, it never registers. (Step Number 3) ............. updated firmware to 3.69 ... then to 3.70 Firmware, same problem.(0MB Option, from the IMCunlock installer app, was the only way to remove it, I am the unlucky user on that, will the Mudoru also brick my vita? Guess I'll see)
...............
...............
...............
next try, 3.65 (pstv) on Enso (apparently you don't need to uninstall enso on 3.65 first, that was for 3.60 bricking bug ? brb)
...............
...............
...............
Going Forward
...............
1. (install HBinjector1.2 to run vita shell from system app) "unlinked sd2vita" from settings option, removed sd2vita
2. (using vita shell installed to system app from hbinjector 1.2) Add "Official Memory Card" to vita, or "moduru", when attempting to install without "official memory card", only "error 0x80010013" was given.
3. (Add 3.60 Official Firmware file, "P2P2UPDAT.PUP") ux0:app/MODORU000/PSP2UPDAT.PUP ... power cycle, then launch moduru
4. Success, downgraded to 3.60 Firmware! (gave error when I selected to transfer files from internal memory, after selecting NO it worked fine, right before normal boot) (Didn't use any "enso 3.65 uninstallers", apparently no risk of a brick there, which is good)
.........
# This file is used as an alternative if ux0:tai/config.txt is not found.
# For users plugins, you must refresh taiHEN from HENkaku Settings for
# changes to take place.
# For kernel plugins, you must reboot for changes to take place.
*KERNEL
# henkaku.skprx is hard-coded to load and is not listed here
*main
# main is a special titleid for SceShell
.........
Thats the "ur0:/tai/config file. In step 3, right before you power cycle to immediately install by running moduru, see there's nothing else but that on the file itself.
.........
.........
(Guess back to henkaku.xyz/go/ .... then the enso installer is run ... I'll just report that it worked)
.........
.........
(remove official memory card, power cycle) Restore this System, Delete All Data ............. https://Henkaku.xyz/go/ ... to install molecular shell (sometimes molecular shell won't install with memory card) ... downloadd this "https://enso.henkaku.xyz/" from your PC, the click the big grey box, then you'll have "enso.vpk", install that, setup your plugins, and add back your memory card with all your files, then your finished. (Everything Checks Out, guess i'm finished)
.........
.........
(well not just me, the IMCunlock, softlocked many vitas, no memory card usage or internal memory ........... so its a coaster, its not a big loss ............ now there are rumors the vita has a 800mhz mode, much like the 500mhz mode for #letmaidie killing ............... there are many goodies coming, especially considering the flow's 3.70 method, may fix all our troubles)
Last edited by yeshuachrist,
(Like, forgot to mention.there is one or two entries in ux0:tai/config.txt, that wasn't in ur0:tai/config.txt that referenced a henkaku.skprx, so I added the entries to the ur0 tai folder config.txt and deleted the "tai" folder in ux0, before restarting the vita with the sd2vita plugged in)
(I did just delete the, "tai" folder in ux0, before that, to see what would happen, and, after restart, I had to go to the henkaku.xyz/go/ website to install henkaku again, and then run the enso installer again, to fix that, entry that needed to be placed in the ur0 tai/config.txt) (it has a henkaku.skprx, add to, the ur0/tai/config.txt before deleting ux0/tai/ folder ,which has to be deleted)
This leads me to believe, henkaku 3.60 was updated, I know enso was update for 3.60 a while ago..............but for my setup on another pstv/vita with 3.60 from, the original release, I think, I'll delete the config.txt file in the ur0, then run henkaku web installer again, and enso installer again, for that update, because it seems different. (I say this because, the updated henkaku enso combination seems to work better? its only a few clicks on the controller to update, first removing the sd2vita though).
(Sad, but, I finished throwing the, bricked vita, from IMCunlock in the trash ................. that firmware 3.68, may just have a tendency to brick, on certain vita's, hate to say this but, IMCunlock and just leaving your firmware at 3.68 may be the best thing to do....................has anyone on 3.68 bricked by downgrading, just a thought..................I got the feeling that if IMCunlock didn't brick my vita, that the downgrader would ................. I wouldn't upgrade to 3.68 just to try to downgrade, without installing IMCunlock, to see if it does so without brick risk, but I guess 3.68 is ok with the downgrader, any reports)
"ur0:tai/henkaku.suprx", this entry appears, after inserting official memory card and removing the sd2vita, same following the reinstall, actually two entries, and this "ur0:tai/henkaku.suprx", which I didn't need in the previous 3.60 henkaku, but needed to have in the other vita, i'll just go ahead and run henkaku from the website and enso installer again, add them restart and leave it at that, I guess I blame this little mix up on "mlthaku", nobody needs to use that anymore, it was kinda "all in one setup" but it made things confusing by changing things in the long run. ($cratch that, this one was updated to 3.65, back to downgrading!
(this one i did use mlthaku on the past, updated to 3.65 and forgot I did, downgrading went fine, but after, that, when I "restore to factory defaults (with official memory card removed for molecular install, from henkaku website), it asked to restore my sd2vita at startup, after that (after the tai/config.txt was fixed with plugins added)...... I plugged it in after the vita already started, used the option to "unlink", and then restart and it went fine after that)
(I did just delete the, "tai" folder in ux0, before that, to see what would happen, and, after restart, I had to go to the henkaku.xyz/go/ website to install henkaku again, and then run the enso installer again, to fix that, entry that needed to be placed in the ur0 tai/config.txt) (it has a henkaku.skprx, add to, the ur0/tai/config.txt before deleting ux0/tai/ folder ,which has to be deleted)
This leads me to believe, henkaku 3.60 was updated, I know enso was update for 3.60 a while ago..............but for my setup on another pstv/vita with 3.60 from, the original release, I think, I'll delete the config.txt file in the ur0, then run henkaku web installer again, and enso installer again, for that update, because it seems different. (I say this because, the updated henkaku enso combination seems to work better? its only a few clicks on the controller to update, first removing the sd2vita though).
(Sad, but, I finished throwing the, bricked vita, from IMCunlock in the trash ................. that firmware 3.68, may just have a tendency to brick, on certain vita's, hate to say this but, IMCunlock and just leaving your firmware at 3.68 may be the best thing to do....................has anyone on 3.68 bricked by downgrading, just a thought..................I got the feeling that if IMCunlock didn't brick my vita, that the downgrader would ................. I wouldn't upgrade to 3.68 just to try to downgrade, without installing IMCunlock, to see if it does so without brick risk, but I guess 3.68 is ok with the downgrader, any reports)
"ur0:tai/henkaku.suprx", this entry appears, after inserting official memory card and removing the sd2vita, same following the reinstall, actually two entries, and this "ur0:tai/henkaku.suprx", which I didn't need in the previous 3.60 henkaku, but needed to have in the other vita, i'll just go ahead and run henkaku from the website and enso installer again, add them restart and leave it at that, I guess I blame this little mix up on "mlthaku", nobody needs to use that anymore, it was kinda "all in one setup" but it made things confusing by changing things in the long run. ($cratch that, this one was updated to 3.65, back to downgrading!
(this one i did use mlthaku on the past, updated to 3.65 and forgot I did, downgrading went fine, but after, that, when I "restore to factory defaults (with official memory card removed for molecular install, from henkaku website), it asked to restore my sd2vita at startup, after that (after the tai/config.txt was fixed with plugins added)...... I plugged it in after the vita already started, used the option to "unlink", and then restart and it went fine after that)
Last edited by yeshuachrist,
Are you saying savemgr doesn’t work on 3.65? If so, any alternative?
While I’m at it, I might as well just ask a question I always had in mind:
With the exception of game modding, does ref00d render repatch redundant now? Or what’s the pros and cons of each?
--------------------- MERGED ---------------------------
It started working again?
Yeah. We don't know why, but it does, even without the HENkaku DNS.
Correct. rePatch + compat packs load games about a second or two faster than reF00D, but reF00D doesn't need any extra space or putting a file for every game in the right places. rePatch's original purpose was for modding games anyways, the whole compat pack thing was added in much later.
The original version that was current when 3.65 was first exploited (starting from 3.60) certainly doesn't;
I haven't kept up much with it (since I don't edit saves, I just use Content Manager and manual ux0:/user backups) but most likely a version that uses RePatch has been made (it should be not that more than a few edits in the source to make it use RePatch, after all)
Similar threads
- No one is chatting at the moment.
-
-
-
-
@
Psionic Roshambo:
Ken I have that sort of set up on Drastic on Pi for games that don't require touch -
-
-
@ HiradeGirl:
Any TV with your PC connected with Citra and any smartphone to use as a screen using a free play store app.+1 -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
