my device keeps booting into fastboot after I tried removing a magisk module. I just installed twrp and magisk after i had gotten rid of them a while back and I still had modules left from before. I had viper4android fx and i tried enabling it but it didn't do anything so I uninstalled it. before rebooting I installed viper4android xhifi then rebooted. now viper4android xhifi wasn't working so i uninstalled it and rebooted which is when I ended up in fastboot. I booted into twrp and i have tried reflashing magisk, i installed mm to try do remove all my magisk modules and found that viper4android xhifi was still present and marked for removal. i tried unmarking it then i tried marking all my modules for removal neither of which worked. now I have tried flashing the oos rom and i am getting the error: error creating fstab. I don't know what this means and I have not done anything else after this. I am currently in twrp and I don't know what else to try from here. the only other module I had enabled when i got stuck in bootloop was busybox which i had enabled before I uninstalled viper4android fx. im currently on the latest open beta build. anyone know how to fix?
i had that happen, i switched to the other slot, and it booted up
bluechimecho said:
my device keeps booting into fastboot after I tried removing a magisk module. I just installed twrp and magisk after i had gotten rid of them a while back and I still had modules left from before. I had viper4android fx and i tried enabling it but it didn't do anything so I uninstalled it. before rebooting I installed viper4android xhifi then rebooted. now viper4android xhifi wasn't working so i uninstalled it and rebooted which is when I ended up in fastboot. I booted into twrp and i have tried reflashing magisk, i installed mm to try do remove all my magisk modules and found that viper4android xhifi was still present and marked for removal. i tried unmarking it then i tried marking all my modules for removal neither of which worked. now I have tried flashing the oos rom and i am getting the error: error creating fstab. I don't know what this means and I have not done anything else after this. I am currently in twrp and I don't know what else to try from here. the only other module I had enabled when i got stuck in bootloop was busybox which i had enabled before I uninstalled viper4android fx. im currently on the latest open beta build. anyone know how to fix?
Click to expand...
Click to collapse
Did you find any solution? Same thing happened to me. I am able to get into phone by using repair boot option in twrp. But then it unroots my phone. when I flash magisk it goes into bootloop again.
Any solution worked for you?
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
Has anyone gotten Magisk to work on DP2? Whenever I flash it through TWRP the phone just ends up in a bootloop with the "G" logo. I know the problem is with Magisk (I've tried Magisk 16.1-16.4) and not with TWRP because when I installed TWRP by itself the phone booted fine. However, once I flashed Magisk I ended up getting stuck in a bootloop again. Any help would be greatly appreciated!
akablasian said:
Has anyone gotten Magisk to work on DP2? Whenever I flash it through TWRP the phone just ends up in a bootloop with the "G" logo. I know the problem is with Magisk (I've tried Magisk 16.1-16.4) and not with TWRP because when I installed TWRP by itself the phone booted fine. However, once I flashed Magisk I ended up getting stuck in a bootloop again. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Working here.. on magisk version 16.4. Have not changed from stock kernel and had only added my google account at that point.. not sure what else to tell you. Try booting it a few times, magisk seems to cause it to get stuck sometimes for me on 8.1, probably same problems on 9.
Magisk and its SU are working fine -- Systemless Ad Block however does not seem to be.
sulpher said:
Working here.. on magisk version 16.4. Have not changed from stock kernel and had only added my google account at that point.. not sure what else to tell you. Try booting it a few times, magisk seems to cause it to get stuck sometimes for me on 8.1, probably same problems on 9.
Click to expand...
Click to collapse
Thanks for trying to help. I tried rebooting it several times but had no luck. However, I just decided to try wiping data during the DP2 installation and now it seems to have worked.
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
after updating OS to 10.3.5 i cant boot after installing Magisk 20.4
i hade to uninstall or not installing Magisk to be abele to boot
any help ?
i guess uninstalling should fix
I'm having same problem.
Both magisk 20.3 and 20.4 don't work for me.
The canary build doesn't work either.
I had a somewhat similar issue.
I used Oxygenupdater in 'automatic mode' and it flashed 10.3.5 but lost root.
So I did fastboot with TWRP 3.2 (the same with which I initially rooted) which did not work. I got Qualcomm Crashdump error Ugh.
Then I downloaded TWRP 3.4.0.3 (latest version) and that worked and flashed this TWRP and then Magisk and so I got root back.
So NEVER use Oxygenupdater in Automatic mode, even when you specify you are rooted.
For TO: try latest TWRP and latest Magisk, and more importantly, the latest ADB and Fastboot tools ! And use original USB cables.
I've tried latest TWRP and magisk. Still same problem, I'm stuck at bootloop
Edit :
Turns out one of the magisk module was causing the bootloop. After removing modules folder in /data/adb the bootloop was fixed