Woke up this am to an OOS update and remembered that there's a process to go through to not lose root and magisk, so I look up the thread and follow the simple directions.
Allow the OTA but do not reboot.
Go into Magisk and install again to internal
Stay in Magisk and install to inactive slot
Reboot
I did exactly that and upon reboot, my phone booted to my lockscreen pic and just flashes every second. Even in safe mode it bootloops at a flashing lockscreen.
I followed exactly what I was supposed to do, so is there a step missing? Or was I not supposed to take the OOS update that was being pushed today?
I can access TWRP still, and I do have a full backup available if I need it, but I'd much rather figure out how to move forward.
Thanks for any help you can give me!
OnePlus 7 Pro
stock ROM
TWRP & rooted
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
FlipmodeBG said:
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
Click to expand...
Click to collapse
What exactly did you do to uninstall magisk from TWRP? I don't know how to do this...
Did you go into TWRP file manager and just delete /data/adb/magisk folder?
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
FlipmodeBG said:
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
Click to expand...
Click to collapse
Thanks for that, didn't work for me though. I keep bootlooping at insecure bootloader warning.
I have messed something up pretty bad, after the last reboot, I'm met with the Qualcomm CrashDump mode -- dmverity device corrupted force dump
kernel_restart
Now I'm stuck, because I've tried to recover my backup, it goes through the process at just over 1000 seconds, has no errors or failures but still won't boot.
I need some help here.
Nevermind, I have to have this phone back up and running ASAP, so I used MSM Tool and started over. I figured spending a few hours setting it back up from scratch was the best way forward at this point.
I'm unclear on what caused this problem... maybe I had a magisk module that didn't disable, or maybe I forgot to disable a substratum layer or something, but I really borked myself all because of an OTA update.
Any further advice on what I might have done or what might have corrected it will still be appreciated because I'm sure there will be another OTA someday and I'd really like to avoid this happening again.
Thanks!
What I do when there is a new Ota is
download the update from the updater app
remove any passwords or finger prints
reboot to twrp
install the Ota
do no reboot
install twrp installer
do no reboot
install magisk
wipe dalvick
reboot
check if Magisk is installed and if not reboot back into twrp and install Magisk again
Hi. Magisk 20.4 not working my device. Has anyone managed to get it working?
Related
I just installed a module (Active Edge) for the pixel 3 and now my phone is stuck in a bootloop.
Specifically its stuck on a page that says: Can't load Android System. Your data may be corrupt.......
The only options are:
Try Again
Factory Data Reset
I can get it into fastboot mode, but wanted to know if there is a way to disable the modules or uninstall magisk and start over. The instructions that I have found only reference TWRP when uninstalling and I don't have that. Any help is appreciated before I wipe this thing.
Flashing stock boot img will remove magisk
Sent from my Pixel 2 using XDA Labs
I ran into this same issue and solved it, check out my post here:
https://forum.xda-developers.com/showpost.php?p=78075483&postcount=121
thanks guys. I am back into the OS. I used the Sept boot.img as I haven't updated yet. I assume I have to flash the Nov update prior to using the patche_boot.img you linked. In any case, I have a usable phone that is ready for magisk again. Thank you, much appreciated.
In fact, you can just flash Magisk Uninstaller in TWRP then flash Magisk zip again, this will remove all modules installed.
I installed the latest Pix3lify using Magisk, and I was not pleased with the results. So I went back into Magisk and removed Pix3lify. Now it is stuck at the OnePlus animation during boot.
Any ideas?
Try uninmod in twrp and make sure it's completely removed, u may be able to just reflash OS, twrp reboot and flash magisk
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Fixed it
TWRP saved my bacon. I reflashed the Pix3lify and it rebooted nicely.
ButtonBoy said:
TWRP saved my bacon. I reflashed the Pix3lify and it rebooted nicely.
Click to expand...
Click to collapse
Magisk has an uninstaller, might want to download it and keep it with your files.
Thanks, I will look for it
I almost came close to that bootloop result, but in the magisk repo with pixelify, the dev put to properly uninstall the module, you'll need to reflash it again using magisk's temp recovery or manually boot into TWRP and reflash it, and it'll uninstall without any side effects.
Well i have followed multiple tutorials, and idk what im doing wrong, but everytime i go to boot the patched boot image the phone just bootloops. I have tried different versions of magisk stable, beta, canary, but to no avail. I think i need some help, sorry
Thank you
I had to full wipe to stop that from happening. Then the whole Android flash-all, followed by Patched Boot (with latest Magisk) seemed to work fine. Dunno really what caused it. May be left over user data? This thread may help if there is something from a Magisk Module causing the bootloop. I didn't try it during my install attempts but it may be worth a shot?
Exokan said:
I had to full wipe to stop that from happening. Then the whole Android flash-all, followed by Patched Boot (with latest Magisk) seemed to work fine. Dunno really what caused it. May be left over user data? This thread may help if there is something from a Magisk Module causing the bootloop. I didn't try it during my install attempts but it may be worth a shot?
Click to expand...
Click to collapse
would a adb backup up cause any harm? And about how long did it take you to reflash the phone?
Flash the Magisk patched boot to both slots either with a --slot all command or by flashing to one manually changing slots and flashing to the other all before final system boot.
Dallas2346 said:
would a adb backup up cause any harm? And about how long did it take you to reflash the phone?
Click to expand...
Click to collapse
Sorry, missed this (and hopefully you've already resolved the issue). I don't think doing a back up would cause any harm, although to be fair, I've never used adb backup. I don't think it'll help on a restore though. Reflashing took all of 15 minutes... signing in and getting all my apps up and running again was a little tedious as Titanium wasn't restoring some app data correctly (or the apps themselves didn't 'take'). Overall, not the worst.
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Bxperiaz3 said:
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Click to expand...
Click to collapse
Can you boot in TWRP? if can try changing slot and boot from it
Mervingio said:
Can you boot in TWRP? if can try changing slot and boot from it
Click to expand...
Click to collapse
Hi,yes I can. Its loading the logo now so i'll wait and see what happens. If that works then what should be the next thing I do?
Edit: Slot B seems to be bootlooping on the logo unless its meant to take a few minutes
Is there a way to recover without wiping my data?
So slot A sits on the caution device rooted screen then defaults to the fastboot rescue mode which allows me to select reboot to recovery which is twrp. From there I have full access to the phone but still not booting to system. Slot B passes the fastboot screen and hangs on the one plus logo just circling around. This is my first rooted phone and I haven't had any problems until now so I'm hoping its something simple because I didnt do anything big to cause it. Hopefully someone has some insight.
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Bxperiaz3 said:
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Click to expand...
Click to collapse
Yes
MrSteelX said:
Yes
Click to expand...
Click to collapse
Will I lost root or relock the bootloader? I'm trying to find the least destructive way to get back to what I had which was oos 10 with twrp and magisk.
Uninstalled magisk and was able to reboot. However reflashing it as i want to retain root makes it bootloop again. Any possible fix for this that isn't a factory reset and reroot?
I can't get substratum or substratum themes to work on any rom or stock, nothing happens after reboots.....or everything turns this weird orange theme. Then one time it corrupted the whole OS and I had to wipe.
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
i6rb said:
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
Click to expand...
Click to collapse
Thanks, i'll try this. Will I need to install TWRP again once I do this or is it unaffected?
Tried to dirty flash the same stock rom from TWRP but I don't think it did it properly. Can I dirty flash stock rom, flash magisk then try reboot to system?
Any help greatly appreciated.
I know this has been asked but since the xda app is so atrocious now I can't find any answers.
I'm rooted on the Tmo OP9 variant but can't remember how to update from the ota. Can someone run me through it?
Make sure you are using the T-Mobile boot.img and not any other variant. Depending on how you rooted it in the beginning..
The
way I updated my t-mobile one plus 9
Is go to magisk, uninstall, restore images. Go to system update. Download and install. DO NOT REBOOT!!
go to magisk and reinstall magisk in inactive slot after ota , now reboot!
Jg1234 said:
Make sure you are using the T-Mobile boot.img and not any other variant. Depending on how you rooted it in the beginning..
The
way I updated my t-mobile one plus 9
Is go to magisk, uninstall, restore images. Go to system update. Download and install. DO NOT REBOOT!!
go to magisk and reinstall magisk in inactive slot after ota , now reboot!
Click to expand...
Click to collapse
Thanks for the reminder! I remember now but somehow my phone is confused. I did the exactly as you said, which is the correct way, and then I hit the switch slots on magisk after ota when it was done, and it restarted but the OTA wanted to restart too so I guess I let the wrong one restart after updating?
So it wouldn't boot after that so I had to switch slots. Now it tried to update but says something went wrong and to update to finish installation. I'm not real sure how to proceed here other than master reset at this point.
I don't know what happened. Sounds like you did exactly like I did. I let magisk reboot for me and everything went just fine. I have heard problems with magisk having issues with inactive slot and was removed in the canary build... You can try flashing stock boot.img before doing a factor reset and see if that helps at all.