- Since V17 the installer mod detects if your device runs into a boot loop after flashing it. If it does, and this will happen on any device not running stock Android 12 Pixel ROM, it will force a new reboot and will try to boot your device running a mod "Lite" version. The "Lite" version is nothing more than a mod version where the only features available are the ones above the red line text.
- If you want those "exclusive features", the ones after the red line text, working on your current ROM you will have to port them yourself. I explain how to later on this post.
- Those "exclusive features" are based on xml and smali changes made on stock SystemUI and framework-res. Without these changes the, "exclusive features" won't work.
- Since this module replaces stock SystemUI and framework-res for modded ones, you could run into problems if some other module tries to do the same or it's simply incompatible with it. If you want to try any other mod that changes SystemUI, or framework-res, there's an option on ROM Control that allows you to disable those "exclusive features". After disabling them, your Pixel device will reboot with a "Lite" version as well.
- Make sure that you're able to run adb shell as root before flashing this module and reboot your device. Just in case something went really wrong and you need to remove the module manually.
- If your device really refuses to boot, after flashing this mod, connect your phone to your PC during boot and run this:
rm -rf /data/adb/modules/AddonFeaturesForPixel/system/framework/ && rm -rf /data/adb/modules/AddonFeaturesForPixel/system/system_ext/ && reboot
This will only remove framework and systemui "modded" files. Without them, you're device will boot and the other features, that don't require modding, will work just fine.
In fact, if you remove these files from the module zip before flashing, you can flash that modified zip on any device running any AOSP, or close to it, ROM.
In case you want to completely remove the mod, you can just run this:
rm -rf /data/adb/modules/AddonFeaturesForPixel/ && reboot
- If you forgot to enable the ability to run adb shell as root, and if your device fails to boot, you can fix that by removing all Magisk modules you have installed. That can be achieved by running the following commands even without root shell during boot:
- If none of the above methods work to get your device booting, then you have to boot into safe mode. By doing so, Magisk will disable all modules for you (it doesn't uninstall them, just disables them). To force a boot into safe mode all you need to do is to keep pressing volume down button during boot animation. After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled). If you get stuck during boot animation again, just force another reboot (I've had to do that during my tests).
- When a new OTA update comes it's possible that the MOD will force boot with Lite version. Why? Because Google may change things on stock SystemUI and/or framework-res between builds. When that happens, I have to recreate the module again to adapt those changes. Rest assured that I'll always test the module with new builds and update as necessary.
- In case your device gets caught in a boot loop, please provide me a logcat so I may try and look if anything can be done about it. To do so, during boot connect your device to your PC and grab a logcat with this adb command:
After grabbing the log, please open the txt file and search for "FATAL". Afterwards post here the lines where the "Fatal error occurred".
- I've made these modules for my personal use and just decided to share with all XDA community. Having this in mind, there's no need for donations (although I won't refuse them if you want to buy me a beer). As for requests or whatever, I can only add more stuff when, and if, I have time for it. I'm a really busy man in real life so I can't promise anything nor ETAs.