I’m no expert but I think if you uninstall a theme from the apps list before disabling it in substratum, it might leave leftovers in the system and cause problems. After opening you app, I chose this theme and used my phone for 1-2 days regularly. After that I found another theme and wanted to apply this one. If you like black themes and you love Google’s Android design, this merges the two ideas together.
You signed in with another tab or window. I had to copy the URL from one to another device, where I’m still logged in into GitHub. It took a long time, but I’m sure it is useful to understand the issue here and for you handier to improve your app. I’m using LineageOS 14.1 on my Motorola X Play and installed substratum via Play Store.
I’ve tried the legacy zip before and I’ve tried manually deleting the files before as well. @arvindbadri Flash the substratum rescue zip from /sdcard/substratum/ and if that doesn’t work, wipe data. First off, uninstalling causes bootloops but not installing?
Urgent help required: Bootloops after messing with Substratum
I tried flashing Substratum Rescue and Rescue Legacy through sideload, since the phone is encrypted for some reason . It didn’t work and flashing OOS thorugh sideload crashes immediately. The theme installs through an app that this app will link you to, where you will have to buy an add-on made by Substratum developers. We don’t provide a ton of support for legacy. Either it works or it doesn’t, we don’t have control over it. Some themes like the Swift series will provide support for it and it’s up to the themers to handle the issues that come of it.
Currently uninstalling framework overlay in legacy roms causes phone to be stuck in infinite boot. This happens with most themes except swift black which only has a placeholder overlay for framework. Interestingly, as long as the placeholder overlay is installed, uninstalling other framework overlays does not cause bootloop. Earlier, to solve the substratum problem, I reinstalled substratum, gave required permissions to andromeda and was able to start substratum.
I logically came to the same conclusion and went through a factory reset … In case you end in bootloop flash the rescue zips that you find in /sdcard/Substratum/, if you have custom recovery, and ask for refund, also by e-mail if you need. @MSF-Jarvis still doesn’t work for every case though. There are situations where even updating an overlay causes a reboot, so missing files shouldn’t be a problem.
Try flashing the ZIP and get back. Before doing this a uninstalled all overlays and apps began to crash so I restarted my phone. It works long enough for me to be able to go to settings and perform a factory reset. But I have about 40GB of data on its internal storage, including my personal photos and memories, which I don’t want to lose and need to back it up before trying to reset.
- AospUI Black is the first and most strongly AOSP user interface inspired black theme.
- If nothing helps, I’ll have no other option than to reset it.
- XDA Developers was founded by developers, for developers.
- Tried this 3-4 times but it restarted everytime.
- I’ve tried the legacy zip before and I’ve tried manually deleting the files before as well.
Well, during boot it is I guess trying to compile all the apps, because I wiped the ART cache and the normal cache. However, after this it is crashing, because it can’t find a file (the mentioned IO Error…). Have a question about this project? Sign up for mediatekout a free GitHub account to open an issue and contact its maintainers and the community. Of course there’s better options if you’re willing to flash TWRP but remember to get your boot.img of your stock rom since yes recovery and boot are on the same particion.
I wish they had more warnings in the Substratum Andromeda app for the non-rooted owners that this could happen, so make sure to not try things without at least a custom recovery …
Substratum Bootloop – PLEASE HELP!!!
AospUI Black is the first and most strongly AOSP user interface inspired black theme. Our hands are tied for RRO2 support. Right now, I’ll let the files copy to my PC and then try to solve it again. If nothing helps, I’ll have no other option than to reset it. Trying to go to the recovery menu also reboots my device.
What device, Android version, etc because something about that sounds fishy. Wow, so that was quick, I already have a bootloop. I didn’t even make a backup, just went with the routine setup and after building Clean Lock and Swift Black on Substratum my phone shut down. When I power it on it goes into the boot animation and the restarts into twrp .
I tapped the trash icon on the top and chose “Remove all overlays”. It gave a toast notification that overlays are being removed in the background and then again my device restarted. Tried this 3-4 times but it restarted everytime. If substratum app itself installs a placeholder framework overlay whenever it detects legacy, it would make a lot of themes run on legacy without issues. If you’re locked on bootloader with no way to unlock it, and want a easy fix on your phone, unfortunately a factory reset is your best option but you will loose all your data. Just go to recovery mode and do a factory data reset.
Instead of blaming you guys, I’d like to provide additional info and help out to fix that. Therefore I began to enable adb rooted via TWRP. I’ll make it short and try to provided the most details possible.
If placeholder overlay is installed first, any overlay applied after that would override and theme properly. On Lineage official builds yes you will be using the legacy mode of substratum. @AllanWang #122 is a legacy bootloop condition arising from uninstalling overlays including framework and the recovery zips fixed it. Your link is 404’ing https://coinbreakingnews.info/ so I can’t really see what happened there and will simply have to go by your rather surprisingly detailed research (thanks for that, it’s appreciated). The system is most probably looking for idmap files. For that you would like to get rid of /data/resource-cache/ which the SubstratumRescue_Legacy zip in /sdcard/substratum/ already wipes.
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Not much can be done about OnePlus’s modifications from our end.
- Earlier, to solve the substratum problem, I reinstalled substratum, gave required permissions to andromeda and was able to start substratum.
- Our hands are tied for RRO2 support.
- Just go to recovery mode and do a factory data reset.
- Googled it and this link saved the day.
- And I have debugging enabled ever since I purchased this device and adb commands are working.
Just my two cents, but there’s clearly more going on with Substratum than just the overlays folder. When the bootloop occurs, it’s typically because of a modification to the framework overlay, be it an update or uninstallation. Neither recovery zips help, nor does dirty flashing the rom. The only solution is a clean installation. Just having a placeholder framework overlay (that doesn’t theme anything) fixes this. Multiple overlays can remain installed for framework.
It might be worth considering if it’s possible to just try catch the issue so that it isn’t a problem to begin with. Either way, I’ve stopped with Substratum on my main phone which has Oxygen OS. This is just a heads up that the problem still exists. Gonna try dirty flashing the ROM once, and if that doesn’t work, wiping data. A lot of themes rely on framework to make their themes look good, we can’t just override that. There’s this mini tutorial involving recovery mode, not sure if unrooted. You signed out in another tab or window.
Hit me up on telegram if somebody has anything to add to this. Make sure it’s that one and if it doesn’t work, yes, you will most likely need to clean flash. And I have debugging enabled ever since I purchased this device and adb commands are working. So what I notice from the logcat, is, that is still looking for the apk with the overlays inside.
I am Unrooted, Bootloader locked. Was messing with Substratum themes, finally messed something up where it’s bootlooping. I used this after I applied a theme and the system ui would stop continuously. Googled it and this link saved the day.