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
Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boots normally.
Thanks in advance.
RealDanyo said:
Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boot normally.
Thanks in advance.
Click to expand...
Click to collapse
I had the same issue this morning when trying to update to 10.0.1. Just boot to bootloader and boot twrp then install 10.
I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2
ItsTecnoDavid said:
I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2
Click to expand...
Click to collapse
I have no issues with magisk or twrp.
It might be the way you are installing ota or rom.
Might be model specific not sure as I don't know what model you are on. Mine is GM1915.
I'm talking about the official recovery
GM21AA, exactly the same situation (from 10 stable to 10.0.1 and magisk from 19.4 beta to 20) and the stock recovery bump into Qualcomm Crashdump problem here, system bootup normal as well as bootloader.
Troubleshooting:
1. Local update twice, install magisk at inactive slot OTA before reboot, for Android 10's A/B partitions machinasm , try let magisk patch both boot.img. Same...
2. Local update and reboot, lost root but stock recovery work, Fastboot boot twrp.img (latest, not flash, cause I don't need the permanent twrp)->twrp install magisk, reboot system, then, again, same problem.
Todo:
Magisk manager or twrp uninstall magisk, but if it's fail maybe ended up to bootloop, scary.
May try to install back old 19.4 magisk.zip via twrp, it's working in 10.0.0
Anyone with the same problem have any idea?
Thats the exact same error I ran into.
But as mentioned earlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?
RealDanyo said:
Thats the exact same error I ran into.
But as mentioned erlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?
Click to expand...
Click to collapse
The recovery here is the one to use.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Be sure to read through
So thanks erveryone who helped.
I now have TWRP running as recovery. So there is no need for official recovery. (and no Qualcomm CrashDump Mode)
Had this happen to me earlier this week. Just ended up using the MSM tool and restoring shipping firmware. You can look for the unbricking thread here for more info on that.
Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...
I don't get it why it have to be so hard.
I'm constantly soft bricking/ bootlooping this phone when trying to do simple things such flashing magisk and twrp. I remember it being so much easier with my Poco F1, never got close to bricking it.
Now every little mistake ends with a bricked phone and 5 hours on the internet trying to understand why
WillyRy said:
Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...
Click to expand...
Click to collapse
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.
JLine05 said:
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.
Click to expand...
Click to collapse
Yea man, things are hinkey this update.
My big problem was i had twrp but it got wiped i guess (could no longer access) and couldn't access adb nor fastboot. But finally got into bootloader (cmd fastboot) so was able to fix.
Easier solution than installing Magisk uninstaller (presuming one has twrp installed, which would be the case if able to flash Magisk uninstaller) is go to TWRP>advanced>file manager and navigate data/adb/modules and delete from there
DO you guys know if there is an updated magisk being developed or what is the way to fix it? Uninstall magisk via TWRP (since I can temporarily install and get into TWRP using the all in one tool by the TWRP developer). Then install TWRP and then Install Magisk ?
I have same problem
How to fix it and bring back stock recovery?
wawanRedblack said:
I have same problem
How to fix it and bring back stock recovery?
Click to expand...
Click to collapse
Can you boot OS?
Can you get to bootloader?
WillyRy said:
Can you boot OS?
Can you get to bootloader?
Click to expand...
Click to collapse
Yes i can boot os and bootloader is ok
Hello,
I have been struggling to root my device. I have not wiped and rooted it in some time and now coming back to it again magisk keeps breaking my device.
I have clean flashed the latest android 9.0.0 build. I have flashed TWRP custom recovery 3.3.0 successfully. I have tried to flash magisk 3 times now and afterwards my phone wont boot. I originally used magisk manager to get the latest zip and patch my boot image. I then rebooted to to bootloader and ran fast boot flash boot patched_Magisk.img. This wiped out my twrp recovery and my phone wouldn't boot, i couldn't get back into twrp recovery. I reflashed latest 9.0 build and wiped everything. I flashed twrp again and tried to flash Magisk 20.0 from recovery. It was successful but again i couldn't boot into my phone and it eventually restarted back into recovery which i still had twrp this time. I then tried it again with 19.3 and the same thing happened. can anyone tell me what is going on here? What am I missing? I have been having reflash factory 9.0 build each time just to get it to remove the patched boot image and boot up again.
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
Hello,
So my phone was in a recovery boot loop and had to rebuild the boot partition in twrp. So I'm back in my phone now and everything is the same but have lost root. Still have access to twrp. It's been a while since I rooted it and don't have any of the files anymore. What do I need to flash to get root back? Do I need to back up all my data or will it be safe?
I am still running android 9 and oos 9.0.7 and I assume bootloader is still unlocked. Orignally rooted with magisk.
thanks
kaotik123 said:
Hello,
So my phone was in a recovery boot loop and had to rebuild the boot partition in twrp. So I'm back in my phone now and everything is the same but have lost root. Still have access to twrp. It's been a while since I rooted it and don't have any of the files anymore. What do I need to flash to get root back? Do I need to back up all my data or will it be safe?
I am still running android 9 and oos 9.0.7 and I assume bootloader is still unlocked. Orignally rooted with magisk.
thanks
Click to expand...
Click to collapse
Damn it, so I booted into twrp and then flashed latest magisk v23 zip but when it finished it said failed to mount partition in red and now the phone just boots to fastboot mode.. I can get back into twrp.. and all my files are still there in file manager.. but it won't boot into my phone.. only fastboot mode. Any advice?
First, boot into TWRP and delete all Magisk Module files and folders:
How to Uninstall Magisk Modules Using TWRP Recovery
Removing the Magisk module manually causes bootloop. You can easily uninstall Magisk modules using TWRP recovery without resetting your device.
www.droidviews.com
I had the same and it seems a module was causing fastboot mode. If that doesn't work try downloading and flashing the stock boot image for your OOS version in TWRP (remember to flash TWRP again before reboot). At least then you will have your phone back.