Not that Magisk is working for our phones and we have dedicated TWRP, does anyone have working modules? I tried to flash IYTPS from inside Magisk and my phone boot looped
Related
So I was rooted and had TWRP, I installed the OTA via the OnePlus Updater. Then I proceeded to flash TWRP in fastboot again, flashed twrp installer afterwards and finally flashed magisk 19.3. Then I rebooted into system, but whenever I 'm at the pin field the device shuts down and reboots to TWRP.
I uninstalled magisk via the zip file and succesfully rebooted into my system. Why is this happening and how can I get back Magisk?
Maybe you have some Magisk module causing this. There is an option to disable Magisk modules through command line.
memocatcher said:
So I was rooted and had TWRP, I installed the OTA via the OnePlus Updater. Then I proceeded to flash TWRP in fastboot again, flashed twrp installer afterwards and finally flashed magisk 19.3. Then I rebooted into system, but whenever I 'm at the pin field the device shuts down and reboots to TWRP.
I uninstalled magisk via the zip file and succesfully rebooted into my system. Why is this happening and how can I get back Magisk?
Click to expand...
Click to collapse
If you used magisk uninstaller and the reboots are gone then just flash magisk again. Also it's best to use 19.4 magisk
Google pixel 3 Android 10 (blue line)
Because of a module I've already installed which my phone didn't like (which is causing the boot loop) I can't get into my phone when I enter through the magisk boot img and have to stick with my non rooted img. Any help on how to delete a module without having magisk? (ALREADY TRIED GETTING RID OF DATA IN MAGISK SETTINGS!)
See this thread.
https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433
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?
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
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).