Dealing with plugins is kind of annoying and hard to debug in some cases. If it bootloops, we need to find the culprit plugin(s) through a witch hunt. Fortunately, through previous community experience, we can narrow down the issue. Note : thanks to teakhanirons (from the cbps team) you can use a tool for the futur to ease the process. I'll describe it at the end of the tutorial.
It may sound unrealistic but yeah. Plugins are microprograms that affect the system. You wonder why your phone/computer runs slowly when you have a ton of apps installed and running? Well it's the same case here. The more plugins you try to load, the more system resources they will need, like RAM. If it asks for too much, it will lead to a bootloop. That's why you should moderate yourself and not install all plugins you can find. (Someone once reached out to me because he couldn't boot his vita after installing ALL the plugins he found in autoplugin 2)
We will use an example on a common case i found during my time helping people :
# 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.*KERNELur0:tai/minivitatv.skprxur0:tai/ds3.skprxur0:tai/music_premium.skprxur0:tai/PSVshell.skprxur0:tai/storagemgr.skprxur0:tai/plugins/vitabright.skprxux0:app/PSPEMUCFW/sce_module/adrenaline_kernel.skprxur0:tai/plugins/nonpdrm.skprxur0:tai/ioplus.skprxur0:tai/AnalogsEnhancer.skprxur0:tai/NoPowerLimits.skprxur0:tai/0syscall6.skprxur0:tai/ds4vita.skprxur0:tai/udcd_uvc.skprx# henkaku.skprx is hard-coded to load and is not listed here# main is a special titleid for SceShellur0:tai/henkaku.suprx*NPXS10015# this is for modifying the version stringur0:tai/henkaku.suprx*NPXS10016# this is for modifying the version string in settings widgetur0:tai/henkaku.suprx*mainur0:tai/LowMemMode.suprxur0:tai/plugins/download_enabler.suprxur0:tai/plugins/shellbat.suprxur0:tai/volume_profile.suprxur0:tai/quick_volume.suprx*ALLur0:tai/BackTouch2L2R2.suprxur0:tai/vitagrafix.suprxur0:tai/remaPSV.suprx*NPXS10013ur0:tai/ps4linkcontrols.suprx
That's a pretty big list there. It's no wonder why his vita doesn't load anymore. Unfortunately, in most cases of bootloop the config looks like this. So let's take this exemple and see how we solve it.
*not talking about the fact that he put some plugins inside a plugins folder which is not recommended*
Yep that's his first mistake. Let's take a closer look. This guy want to use his DS4 (PS4 controller enabler) plugins, but he loaded all the plugins for it : minitv, ds3 and ds4. He needs to make a choice, either use minitv or ds4. In this case let's go with minitv (which uses DS3 as a dependency)
Another common mistake is to not put the SD2VITA at the begining of *KERNEL. This is very important as normally every plugin need to be loaded after the storage is mounted or else there will be problems upon boot because of the sudden storage change. As for ioplus it is a dependency used by other plugins to have access to more IO operation in userland. It needs to be loaded before them.
UCDCD's uvc plugin for streaming the PSVita screen through the usb is one of the most heavy plugins and need a lot of resources. If you want to use it, make some room for it. Let's see :
I don't think you need to activate the music related plugins, that already removes 3 plugins from the list.
PS4 link controls? Not useful in that case.
Nopowerlimit, unless you really want to leave the wifi open while playing a game that disables it you can also remove this one
Adrenaline plugin is one of the most useless plugins there. Just to avoid launching the app twice (one time to inject the adrenaline.skprx, and a second time to open adrenaline). Let's free our config from this one too.
Using remap plugins, analog enhancer and BackTouch when we use a DS4 controller is also useless. It's just wasting memory at this point since you will use your PS4 controller and not the vita control. We did some cleanup so lets see what the config looks like
# 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.*KERNELur0:tai/storagemgr.skprxur0:tai/minivitatv.skprxur0:tai/ds3.skprxur0:tai/ioplus.skprxur0:tai/PSVshell.skprxur0:tai/vitabright.skprxur0:tai/nonpdrm.skprxur0:tai/0syscall6.skprxur0:tai/udcd_uvc.skprx# henkaku.skprx is hard-coded to load and is not listed here# main is a special titleid for SceShellur0:tai/henkaku.suprx*NPXS10015# this is for modifying the version stringur0:tai/henkaku.suprx*NPXS10016# this is for modifying the version string in settings widgetur0:tai/henkaku.suprx*mainur0:tai/LowMemMode.suprxur0:tai/download_enabler.suprxur0:tai/shellbat.suprx*ALLur0:tai/vitagrafix.suprx
It looks way more clean now. As you have seen, people always tend to load more plugins than they really need. Using only the plugins you need for the game session you will do allows you to enjoy your system without being blocked by a bootloop. You can create multiple config.txt's for each case if you want as long as the config isn't heavy (more than 10 plugins at the same time is not recommended). By following the same logic you can clear your config.txt easly without scratching your head over why it won't boot.
Note : If vitabright doesn't work for you even though you did what i told you to do, then look at this : https://github.com/devnoname120/vitabright/issues/13
A app was made so that if you use the uvc plugin, you could control what plugins were enabled when you connected the Vita to a big screen, or disabled when you're using it as a handheld. You can get it here
This plugins will save you a lot of trouble in case you run in a situation like this. And there's many thing you want to avoid :
Loosing all your icon organisation you spent hours to finally complete it to your taste because it will trigger a database refresh (Or for sd2vita user, you will simply boot in a blank live area without access to any app). Also making the boot time much longer than what it is originally
Especially for 3.65 users, being stuck with either formating the memorycard or update since pressing L will remove the version spoof.
It will mount one of those partitions : sonymc, internal storage, usb or ur0 (what we really care) through usb and you will have access to it with your computer (just like what vitashell does). Then you can open the config.txt with notepad and edit it.
That's simple. Remember when i said that for storagemgr to work correctly we need to put it first? Well change of plan. We need to put emergency mount right below *Kernel (yeah since bootloop means some pugins cause it, and plugins that are loaded before emergency mount can crash before even letting emergency mount run.) So like before, you edit the config.txt like that
and then you add your favorite plugins after that line (add storagemgr in second place ofc, the only case you want to still let it in first place would be to allow Emergency Mount to mount sd2vita, but let's be honest, we don't need that option.) When you're stuck in a bootloop, simply press the triangle button at boot and it will bring the menu of the plugin. Then you can mount the partition you want. You can also customise the background if you want. I recommend this plugin because it make it easier to edit config.txt, instead of doing the taihen reset option in henkaku/hencore that would reset the whole config so you need to rewrite every lines again (time consuming), you can just remove the faulty plugin line and reboot. For more information about the plugin, you can see the release post in the CBPS forum and talk with the dev.