1st is i have rooted my phone with Magisk... everything works well after that
but when I tried to install Xposed Framework, it only bootloops.
by the way im on 8.0.0 (Oreo) 41.3.a.2.192
SUMMARY:
what i installed that causes the firstboot loop was this (systemless Xposed):
https://magiskroot.net/install-system-less-xposed-framework-oreo-8/ (the sdk 26)
then when it boot loops, itried to install the regular Xposed (not the systemless):
https://magiskroot.net/download-xposed-framework-for-oreo/ (the sdk 26)
but still bootloops.
the i used the Xposed uninstaller:
http://dl-xda.xposed.info/framework/uninstaller/xposed-uninstaller-20180117-arm64.zip
still bootloops.
then i searched the net for possible solution:
I restored the boot partition on TWRP... then I used the "uninmod_magisk-v4.zip" on TWRP...
The phone boots... But the root is already lost...
i tried to Install Magisk again. Then it bootloops again.
then i tried to restore the boot partition & install the "uninmod_magisk-v4.zip"--- boots again but no root...
it looks like i need to delete the Xposed Framework files because it looks like its the one having in conflict with the root/magisk.
how do i properly delete Xposed Framework?
i have TWRP back up... before... restored it (except Data partition)...
but still the problem persist...
Bootloop when rooted; No bootloob when not rooted
Related
Using stock rom, unlocked bootloader, root, with I dunno what kernel. Xposed installed. I installed several modules including: boot manager, lucky patcher, no device check, AppsOpsXposed, xposed settings injector, xinsta. After I installed them, I activated and rebooted my phone, at startup, I was greeted with Unfortunately SystemUI has stopped, and then it self reboots. I entered recovery and flashed Xposed uninstaller, so I can boot it up. Forgot to mention I have previously installed modules with which I had no problem at all.
Any help is greatly appreciated
I installed Xposed v86 arm64 successfully using TWRP recovery, after restart, the phone got stuck on a boot loop. i had to go back to recovery and install the uninstall zip. After that process it booted normally and updated the apps. That does mean i cant install or use Xposed on my device or there is something wrong somewhere?
I was stuck with a working(sort of) root after dirty install 8.1->9.0 sideloading official OTA file. I tried to remove the magisk using the official uninstaller. Reinstalled Magisk 16.7 + APK 5.8.3(129) and was slapped with a bootloop.
Used uninstaller again and was able to boot fine, but no root(as expected). Reinstalled magisk and was stuck in a bootloop again.
Fix that worked for me:
1. Sideload latest OTA(9.0). (again)
2. Boot into it.
3. Reboot into TWRP(I load my TWRP using fastboot, not installed to recovery partition)
4. Sideload Magisk 16.7
5. Should work now.
Hopefully it fixes your bootloop.
I've been having a different problem. I'm able to install magisk 16.7 by flashing the patched_boot.img. Everything seems to work fine for a while. But after rebooting the phone a few times it eventually gets into a bootloop. Anyone else having this problem or know how to fix it?
I flashed OxygenOS 10.0.1 by the fastboot method. Then flashed modded TWRP and then Magisk. This all happened successfully. I wanted to install Youtube Vanced but stock Youtube was causing it to not show up. So I tried uninstalling Youtube through Titanium Backup but it said 'apk not found'. So I downloaded some other app (I think it was named 'System App Remover'). Since then I have been getting bootloops. Phone gets stuck on 'Bootloader unlocked warning' screen then goes into Fastboot mode. I had to uninstall Magisk through TWRP to boot the phone. I don't understand what's wrong in this entire process. Please help.
I think the issue is with the System App Remover. I tried using possibly the same exact app previously but I also got boot loops. I would try a factory reset, reflash twrp and magisk and try the Magisk module "Debloater".
You have to clean temporary magisk files.
Probaby you had enabled some magisk modules on previous system and you forget disable them.
Thanks for the replies. I fixed the problem by restoring System from an earlier TWRP backup.
Usually bootloops from Magisk modules can be fixed by deleting problematic module from twrp file explore /data/adb/modules
Don't have to fart around with uninstalling entire Magisk or installing Magisk debloater anymore
Hi all,
Yesterday I was messing around with V4A and following the final installation steps my phone got stuck in fastboot. To fix it I did the following:
1. I extracted the stock boot.img from my current OS version (10.3.12) and flashed it to boot_a and boot_b using fastboot. This restored the phone's ability to boot.
2. I booted the phone and went into the Magisk app to disable/unhide as much as possible and uninstalled the V4A app.
3. Rebooted into fastboot and booted into TWRP to remove Magisk, V4A and Vanced stuff from data/adb with the file manager.
4. Booted and flashed various combinations of TWRP versions (Mauronofrio, Bluspark) and Magisk (from 19.4 to 23.0). TWRP flashes fine and allows system to boot, but as soon as Magisk is flashed and a reboot is tried into system, it gets stuck on bootloader again and I have to repeat step 1.
(5. Tried patching stock boot.img file with the Magisk app. Same results as step 4.)
Does anyone here know what might be wrong? Is there another method I can try to regain Magisk without losing data?
Thanks in advance!
EDIT: really at a loss here. Idk why but as soon as magisk is flashed, the system refuses to boot. Without flashing magisk, system boots fine – am typing from it now. I figured at first that it had to do with remnants of AML, V4A and other Magisk modules not being properly removed, but I've removed those through TWRP file manager.
Really hoping one of you can point out something I've missed or think of something else I can try.
EDIT: solved! See update below.
UPDATE: solved it by forcing a local upgrade of the full OTA through phone settings (same version as mentioned above), causing it to switch slots. On the other slot, the system managed to boot after flashing TWRP and Magisk (latest versions).