Hacking [RELEASE] IMCUnlock v3 - Permanently enable/manage internal ux0 storage.

SKGleba

O ja pierdole!
OP
Member
Joined
Nov 11, 2016
Messages
351
Trophies
0
Location
Warsaw
XP
747
Country
Poland
After 3 weeks of work (i bricked my vita, so almost all tests were done by testers) i present you IMCUnlock v3.

Changelog:
- New flasher (wrote new from scratch), new method of flashing.
- 3 nand types are now supported.
- Fixed common fs errors by moving temp files to ur0.
- Fixed Backup/Restore utility.
- Added support for Slim units.
- Added ability to choose imc size between 0mb, 100mb, 300mb, 1gb, 1.5gb, 2.5gb and 2.8gb.
- Added ability to create hybrid partitions.
- ur0 and ux0 are now resized instead of ux0-ur0 switch (Slim/TV users).

Link to readme: https://github.com/SKGleba/IMCUnlock/blob/master/README.md

Link to vpk: https://github.com/SKGleba/IMCUnlock/releases/tag/v3
 

XploitOcelot

Member
Newcomer
Joined
Feb 13, 2016
Messages
16
Trophies
0
Age
37
XP
127
Country
Thank you for your work!!
I will use your tool tomorrow. I will check with a friend if we can hack his phat vita with my Sony MC + create the ux0 partition afterwards so he can go on alone without an original mc card.
Is there any chance to update the console without risks afterwards? (not that we want to right now, but maybe for future hacks)
 

Gromber

Active Member
Newcomer
Joined
Jan 15, 2019
Messages
27
Trophies
0
Age
49
XP
290
Country
Angola
Hi! great tool!

I recently bought a Vita Fat (3.68). I wanted to have 100mb internal to install h-encore and sd2vita plugin because some user in a forum recommended me this option, and a friend can lend me a memory card, but that user a month and a half later, for no apparent reason, vita stopped working, he used 1gb internal memory option.

I would like to know how many of you have this mod installed, size you unlock and how long do you have it .

P.S. will delete something important from the system if I only use 100mb?

Thanks!
 
Last edited by Gromber,

Ryccardo

Penguin accelerator
Member
Joined
Feb 13, 2015
Messages
7,664
Trophies
1
Age
28
Location
Imola
XP
6,867
Country
Italy
I would like to know how many of you have this mod installed, size you unlock and how long do you have it .
I did 300MB (killing the initial setup video? yes please) shortly after it came out, given I already had one original memory card burn out

So, with this we can use internal as 2.8gb partition+ memory Card? :0
You can (with potentially significant tradeoffs), if you also add an appropriate StorageMgr configuration to mount both imc0 and the real memory card
 

SCOTT0852

Well-Known Member
Member
Joined
Jan 20, 2018
Messages
1,140
Trophies
0
Location
The Moon
XP
1,122
Country
United States
Ok so i've got a fat PSV 3.60 with Henkaku, if i install this, will i be able to update to 3.68 and hack it ?
You could, but there's no reason to as you'd lose stuff like Enso. You can play all newer games on 3.60 anyways with ref00d and even make your own compatibility packs by holding L when launching the game (when ref00d is installed).
 
Last edited by SCOTT0852,
  • Like
Reactions: emuashui

yeshuachrist

Well-Known Member
Member
Joined
Sep 1, 2010
Messages
600
Trophies
0
XP
1,482
Country
United States
IMCUnlock // (Michael Cohen, Donald Trumps Liaison, Prison Sentence)

I can see this value in this but, one recommendation (only if you already have 3.68 firmware or want 3.68 firmware):

1. "Upgrade to 3.68 Firmware First" (reduce the risk, don't use this hack, unless, you want 3.68 firmware h-encore without memory card, requirement)

2. take out the sd2vita card, with all the games on it (make sure to use settings option to "use sd2vita on all vitas)

3. install "IMCUnlock" to Official Memory Card running 3.68 H-Encore Hack. And use 100 mb option (it flashes "enso ? h-encore, at end of install")

4. there's no mention of "vita shell" being installed, so you use, ?, "psvimgtools" to make backup of "internal memory as official memory 100mb" from "qcma", then add "Vita Shell to that" ?

5. Without access to "Vita Shell", there's no way to modify the ur0:tai/config.txt with sd2vita plugin to point in the right path! (your vita would be bricked! by this mod!)

(This Hack is unclear on how "Vita Shell" is installed, or if "HBinjector 1.2.6 that install VITA SHELL to SYSTEM APP internal memory (on 3.68 Firmware), without this mod" can be used to substitute, having to use "psvimgtools and qcma" to install vitashell!)

("enso is installed by IMCUnlock, after reboot, we launch vita shell from SYSTEM APP --* "HBinjector 1.2.6" we installed before, while we had h-encore 3.68 hack running from official memory card)

(after this one issue is resolved, then, best to not use OFFICIAL MEMORY CARD, because of power usage issues with the VITA, when you use both official memory card+sd2vita .................. (POWER USAGE ISSUES, is what killed everyone's preference in USB STICKS!) (so this is a necessary fix, but need more details, about, Vita Shell!)

..................
..................
(3.68 excerpt install, using official memory card, "psvingtools" and "qcma", no previous hack install) The h-encore bubble with a size of around 243 MB should now appear in the Content Manager and that's what you finally need to transfer to your PS Vita.
Launch h-encore to exploit your device (if a message about trophies appears, simply click yes). The screen should first flash white, then purple, and finally open a menu called h-encore bootstrap menu where you can download VitaShell
and install
HENkaku
..................
..................
H-Encore on 3.68 installs Vita Shell, as a download, after the setup, it requires at least 243 to 255 MB, 100 MB, will not be enough! if you need to reformat the "iCUMnlock", partition of 100mb after reboot, it will be blank, then you need to install h-encore to it, but the size will not be big enough. That means using "300mb" option to avoid having to reformat, so the "enso hack?" can be installed during the final "iCUMnlock" install process. The Question is still about "Vita Shell", the "FLOW" has stated a 3.69 firmware release, it may have a "enso installer" and be perma boot like 3.60, this hack is asking to much, it will be too much trouble to undo this hack for the "FLOW'S" New Release Soon!
 
Last edited by yeshuachrist,

SCOTT0852

Well-Known Member
Member
Joined
Jan 20, 2018
Messages
1,140
Trophies
0
Location
The Moon
XP
1,122
Country
United States
1. "Upgrade to 3.68 Firmware First" (reduce the risk, don't use this hack, unless, you want 3.68 firmware h-encore without memory card, requirement)
There's no reason to do this. There is no "risk" that would be reduced by 3.68. Any hackable firmware can use the internal memory card without issues.
2. take out the sd2vita card, with all the games on it (make sure to use settings option to "use sd2vita on all vitas)
What's the point in doing this? The sd2vita acts just like a memory card, why would you need to use a real one?
3. install "IMCUnlock" to Official Memory Card running 3.68 H-Encore Hack. And use 100 mb option (it flashes "enso ? h-encore, at end of install")
How would you install enso if you updated to 3.68? Also, take note of the 100 mb thing.
4. there's no mention of "vita shell" being installed, so you use, ?, "psvimgtools" to make backup of "internal memory as official memory 100mb" from "qcma", then add "Vita Shell to that" ?
You install Vitashell the normal way through h-encore.
5. Without access to "Vita Shell", there's no way to modify the ur0:tai/config.txt with sd2vita plugin to point in the right path! (your vita would be bricked! by this mod!)
Yes there is, h-encore has a "Reset config.txt" option to do just that.
"enso is installed by IMCUnlock
1) No it doesn't, that's what the Enso Installer is for. This would be like if your microwave was also your AC, it makes no sense.
2) How would you install enso on 3.68?
it requires at least 243 to 255 MB, 100 MB, will not be enough!
1) Then why did you tell us to use 100mb?
2) Both finalhe and auto h-encore trim bitter smile down to just over 10mb. 100mb is absolutely enough.
the "FLOW" has stated a 3.69 firmware release, it may have a "enso installer" and be perma boot like 3.60
TheFlow has never said 3.69 will be permanent, iirc he said it won't be.
 
Last edited by SCOTT0852,
  • Like
Reactions: Vinceherman

yeshuachrist

Well-Known Member
Member
Joined
Sep 1, 2010
Messages
600
Trophies
0
XP
1,482
Country
United States
There's no reason to do this. There is no "risk" that would be reduced by 3.68. Any hackable firmware can use the internal memory card without issues.

....................
....................
....................

1) Then why did you tell us to use 100mb?
2) Both finalhe and auto h-encore trim bitter smile down to just over 10mb. 100mb is absolutely enough.

TheFlow has never said 3.69 will be permanent, iirc he said it won't be.

"TheRadziu" Recommends going to 3.68 first before using IMCunlock to avoid the higher risk of a brick (marshmallow smile)

Used MLTHaKu on 3.60 -> IMCUnlock to create internal ux0 -> 3.65 OFW Update(+h-encore +3.65 enso installer) OR 3.68 OFW Update(+h-encore)
While being on 3.65/3.68 already, memory card is used at least once in order to install hack, then create internal ux0 with IMCUnlock
https://gist.github.com/TheRadziu/4d81d7882ebc5da339bc09a0bbe53f4b


The Official IMCunlock, guides tells you to reformat after using the 100mb option, you will lose the hack information from h-encore, if you do that, it will not be transferred over.............its unclear if the 300mb option transfers this information over from h-encore, according to "theradziu's" statement. (3.68 h-encore hack, untrimmed is just under 300 mb) (susposedly, "h-encore" just under 300mb, is transfered over to the new internal partition, with vita shell already preinstalled, then you just take out your official memory card, and it boots using your already configured "tai/config.txt" file with sd2vita plugin) - "TheRadiziu".

(IMCunlock guide is unclear if the "enso" option used on 3.68 firmware after installing the internal memory card, will cause a brick, since "enso" isn't updated to work with 3.68 Official Firmware?) (the assumption is on 3.68 the enso option, would cause a brick, or the program won't install that option, the guide is misleading)


The Official Guide for IMCunlock, does not state, "it trims the less then 300mb h-encore, which according to "TheRadziu", transfers over automatically after installing the internal 300mb option", does not state IMCunlock trimes the h-encore hack to 10mb in size,, the guide does not make this claim (using the 100mb Option of IMCunlock, would require reinstallation of h-encore, and, a special modified or trimmed version .......... why is this necessary - "The Radziu"


Lower than 3.68 Firmware increased Risk of Brick (enso's mods which are perma-type, meaning they mod firmware files specifically, are not specifically designed tobe used with "IMCunlock" ................ ? so that should be clear ................... the "h-encore" type mods, do not modify firmware files like enso, so on that basis, the claim is no additional risk of brick (the IMCunlock, guide and github page is deliberately not clear on this position)

(the fact is if "The Radziu" claim of using the 300mb option of IMCunlock Install, which doesn't require reformatting, automatically transfers the pre-installed 3.68 h-encore files to immediately run after reboot of the vita, why is it necessary to use the 100mb option and a specially modified (or untested as much), version of h-encore, that has a smaller size for 100mb IMCunlock install, requiring a new h-encore installation)

(The Flow's 3.69 Firmware, is going to be released soon? 2019, there is some inconsistencies in the IMCunlock's language, I think, I will continue to wait for the Flow ... there is a risk of a brick when installing or uninstalling the IMCunlock's Internal Memory, but once the Flow abandons his development of firmware, the one time usage install of IMCunlock, is a much better process, don't you agree?)
 
Last edited by yeshuachrist,

SCOTT0852

Well-Known Member
Member
Joined
Jan 20, 2018
Messages
1,140
Trophies
0
Location
The Moon
XP
1,122
Country
United States
Recommends going to 3.68 first before using IMCunlock
Used MLTHaKu on 3.60 -> IMCUnlock to create internal ux0
So we're throwing the whole 3.68 thing out the window?
-> 3.65 OFW Update
Once again, that's not 3.68.
does not state IMCunlock trimes the h-encore hack to 10mb in size
You're correct, because IMCUnlock does not trim h-encore. The h-encore installers trim it. As I stated above...
Both finalhe and auto h-encore trim bitter smile down to just over 10mb.
(bitter smile's demo is used for running h-encore as it is both exploitable & has no DRM since it's a demo)
 

yeshuachrist

Well-Known Member
Member
Joined
Sep 1, 2010
Messages
600
Trophies
0
XP
1,482
Country
United States
300MB - pd0 becomes imc.
1GB - Default on 2XXX and TV units, a ~1GB imc partition, ur0 1.5GB, on Phats requires formatting the new partition via settings or safemode.
.............
.............
.............
HBinjector (install's vita shell/replace system app) (in internal memory)
github.com/emiyl/HBInjector

hbinjector uses the "vs0" partition, (of internal memory ur0 (?)), since "vs0" has system stuff, the IMC-, doesn't use this area, guess that is natural conclusion to make.
.............
.............
.............
So, the 1GB option is closer to a retail memory card's partition size. I'll be going through the tradition-, o, guides for h-encore, after installing IMC- on 3.68 from official memory card..............just like using an official memory. No One's complained really about, "psvingtools/qcma/" or "the vita misreporting file sizes or free space on the sd2vita or memory card so far"
.............
.............
.............
3.68 with 1GB Default, from IMC, has the least amount of Risk..............its not that difficult to undo the mod, what I'll probably do is.................run some checks with the comp. packs and "REFOOD" plugin, the use IMC ............... i think this is a important app, because again, th3, (power issues from the USB stick, and the power issues from using both the memory card and the sd2vita, is what concerns me. (someone can argue the power bar is goodenough but i think this is an issue that needs 'IMCunlock to fix"!)


I'm convinced the app is low risk brick, (refood plugin and compatibility packs, need to check if people have problems with that now)

EDIT

(REFOOD plugin, error c1-6703-6, error, same error without compatibility pack (?) .......... sticking to compatibility pack ............ guess i'm all good .............. going reinstall h-encore after IMCunlock in a few hours) (chronusarc game)
 
Last edited by yeshuachrist,

SCOTT0852

Well-Known Member
Member
Joined
Jan 20, 2018
Messages
1,140
Trophies
0
Location
The Moon
XP
1,122
Country
United States
I don't know anything about the USB sticks, but...
the power issues from using both the memory card and the sd2vita
This would mean there are issues when playing a cartridge game with a memory card inserted. I wonder why nobody's complained about their vitas suddenly dying just because they had both a game cart and memory card inserted... maybe because it doesn't happen?
 

yeshuachrist

Well-Known Member
Member
Joined
Sep 1, 2010
Messages
600
Trophies
0
XP
1,482
Country
United States
Installed (with a few notes - pstv) (1000mb install, if you can't use the trim version of h-encore, your with 100mb install, then you can't do anything with your vita! its bricked!)

(seen no reason to edit the tai:/config.txt to remove plugins, gamesd, nonpdrm, repatch plugins used only)
1. install IMCunlock 3.0 from vitashell (3.68 OFW, on h-encore, with sd2vita plugged in, official memory card also plugged in)
2. backup of "vd0/pd0/tm0/id_data"
3. power cycle vita, install the "1 gig (ur0 1.5 gb)" option ... "triangle to exit", then, "Power Off from main bubbles menu"
4. removed official memory card, vita reports memory card 1075mb w/ 1042 free

PSN UPDATE NAG

(follow the flow's official h-encore guide, for the 243 mb installer, you don't need transfer files to or from your PC, for that, once you finish creating the package, (meaning you will have update nags, just ignore them, qcma will still create folders you can use in the setup guide) (after that you need to do the following to transfer the h-encore package to your vita/pstv)

(create a free psn account from your computer, if you have an account already sign in to that) Factory restore the device, delete all memory. When you vita starts, "SIGN IN", it does not give you a update prompt for just signing in................then you have to
use "VITA UPDATE BLOCKER", just turn that on, it will give you two "XXX.XXX.X.XX:**** (port number = *):

1. go to settings/network/advanced settings ... click USE PROXY, and enter in the "xxx.xxx.x.xx" ip address and then port number below that

2. click the PSN STORE bubble, it will connect or ask you to update, thats ok leave it on the UPDATE screen don't touch anything, the VITA UPDATE BLOCKER, will add a few numbers, just press the PS BUTTON to SHRINK NOT CLOSE, don't close the window.

3. Go back to settings/network/advanced settings ... and change the setting to DON'T USE A PROXY, now close the settings window

4. Connect to Content Manager and transfer the 243 H-encore package to your vita/pstv, it will show the bubble on your vita's main screen, run that, install henkaku, and vita shell (I installed Vita Shell from "HBinjector 1.2.6", before I used IMCunlock to install the internal memory card partition, that also works, no install necessary, incase there is a problem)


(so far everything is fine, just have to add back my tai/config.txt file and plugins, and then restart, then rebuild databases, and I should be fine. antiblacklist1.2 i may need to reinstall that, or I can do psvimgtools from backup will see) (sadly, yes you still need to use VITA UPDATE BLOCKER, and PSN still needs to tell you to update, I just googled that old method but it still works) (3.60 hacks don't have to do that, they have the "henkaku website", sadly 3.68 still nothing) (so if you wait for the Flow's Update, it maybe even harder or impossible to hack your VITA!!)

1. Delete "ux0:tai" (the folder, so it reads the config.txt from ur0:tai)
2. Restart, and refresh the live area from vita shell
***
3. Antiblacklist 1.2 needs reinstall, delete the "ur0:tai/config.txt" file, remove your sd2vita card, if you don't delete the ur0:tai/config.txt file your internal memory will not detect, it needs, none there (or default), after restart.......click "h-encore" bubble, and "install henkaku" again, now, from vita shell install "antiblacklist 1.2" and run it, install both v1 and v2 white lists. then restart, the database will rebuild ............... get back into vita shell and add your custom "ur0:tai/config.txt" file back, power off, and add your sd2vita card back, after restart, go to vita shell, and "refresh database", games will work again.

******
There is a problem in using the Official Memory Card and the SD2VITA ................ one of the problem in addition to the power issue, is, I realized I was providing false information about some translations or game hacks that used MAI DUMP, that they were not working was because of the dual card configuration on the vita (blue reflection was probably one game, plus more)............... now there is just the "sd2vita", but I gave some bad information, long ago, because of that unfortunately!!!!!!!!!!!!!!!!!

...............
...............
...............

If your using 3.60 or 3.65 firmware, you don't need to use IMCunlock ................ if you have 3.68 firmware, and you want to remove the official memory card, you need to act now, before sony cancels or modifies "PSN" like they announced the name change, then you will really have a problem, you'll be stuck with the official memory card, and its problems!!!!!!!!! (The Flow releases the 3.69 firmware, guess what? You have to still deal with PSN in some way, because of Official Firmware, if they change the system for PSN, you forever lose that ability to hack it!!!)
 
Last edited by yeshuachrist,

yeshuachrist

Well-Known Member
Member
Joined
Sep 1, 2010
Messages
600
Trophies
0
XP
1,482
Country
United States
so... there is a great risk or not?

(if your not on 3.68, don't use it .............. I imagine if you were on 3.60 firmware, and wanted to install 3.65 you need an official memory card or something (you could avoid having to use an Official Memory Card with Enso/(brick risk)................. the developers of "enso" have not specifically tested their hack with this) (3.68 H-encore is not permanent, meaning firmware files are not over written, etc.)

(Brick Test? 3.60/3.65 firmware)

(install the internal memory IMCunlock using the 300mb option it deletes an official partition ............ then ............... uninstall IMCunlock the official way ...............(don't restore the data to the 300mb partition using IMCunlock (that it deleted, if you made a backup), so it is blank ...................... then .................. try to install the enso hack on 3.60, it should detec1t the missing data in the pd0 partition IMCunlock delete, and prompt you to reinstall the 3.60 firmware ........... after you do that, your 3.60/3.65 should be bricked?)

(I specifically used 1gig/1000m8 partition, I haven't tested, but there's no "restore data" option built into IMCunlock for that area, its generally blank)


EDIT


(its not pretty, but I used one of the initial enso uninstallers for 3.60 firmware (that was a real brick risk!, as I upgraded one of my psp's to 3.65 (there's no risk, if you follow a certain method with IMCunlock so far)............ but if your on 3.67/68, your doing damage to your vita, and messing up your game compatibility using the official memory card and sd2vita, based on my own results, I no longer have this problem after using IMCunlock)
 
Last edited by yeshuachrist,

yeshuachrist

Well-Known Member
Member
Joined
Sep 1, 2010
Messages
600
Trophies
0
XP
1,482
Country
United States
Didn't you say earlier to install it on 3.60 and update to 3.65? You keep saying contradictory and false things...

("TheRadiziu", implied an "h-encore" installation would be automatically copied over after the internal partition was created, from the source device. I have been doing a lot of reinstallation5.recently which is why the the deletion of the 300mb pd0 partition caught my attention, as the option to avoid, since i intend to have the 243mb installation from the, flow, transferred over, but now I believe more correctly, that option specifically may be tied into a brick or a soft lock)

(sony at any moment can shut Shings down, the risk of the software is not more intimidating then having to deal with sony, update nags specifically, i think that is apart of the whole point ............... if they don't act right now, they are stuck with the official memory card in their vita!)
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Sorry for accidentally bending over