Related
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
I have TWRP installed but any time I try to Flash magisk, the boot image seems to corrupt and leaves me on the 'Bootloader unlocked' screen. I have to boot back into bootloader and use the 'repair recovery boot loop' option just to get back into my phone which then doesn't have Magisk available and root has not taken. Does anyone have any advice? Is there a boot image I need to flash after Magisk maybe? I'm fairly new to all this.
Isadorian said:
I have TWRP installed but any time I try to Flash magisk, the boot image seems to corrupt and leaves me on the 'Bootloader unlocked' screen. I have to boot back into bootloader and use the 'repair recovery boot loop' option just to get back into my phone which then doesn't have Magisk available and root has not taken. Does anyone have any advice? Is there a boot image I need to flash after Magisk maybe? I'm fairly new to all this.
Click to expand...
Click to collapse
Hello, would love to know because I have same issue here …
In fact I could effectively have root and magisk installed once, then I installed viper which didn't work... I removed viper module from Magisk Manager, then reboot, then got into the issue you describe. The 'repair recovery boot loop' allows booting but magisk is removed. And if I flash magisk again from TWRP, then the phone won't boot.
I tried reinstall TWRP/Magisk without success, tried lock/unlock bootloader (don't do that ! I could get out of it but no more success with magisk), also tried to remove the viper module with TWRP file manager (I could but it did not solve the issue), not sure what to do now.
What versions TWRP and Magisk?
Hello, So i tried to install GPS joystick privacy mode app as a system app first thru titanium backup then ..., i rebooted and now im on boot loop, what do i do?
Any help is appreciated, Thanks
{Mod edited}
Hold Power + vol up + vol down for several seconds should put you in bootloader. Or alteranately, Power+vol down for several seconds should send you to TWRP if you have it installed. From there, I'm thinking you may need to flash the stock ROM again, since you were messing with the system partition, and the phone is not booting now. Either flash stock ROM in TWRP, or use the fastboot stock ROM.
I didn't have twrp installed and i still dont, i patched the boot image with magisk and all i have is root cause i cant seem to keep TWRP installed after 9.5.3, im currently on 10.3.0
cmurder61 said:
I didn't have twrp installed and i still dont, i patched the boot image with magisk and all i have is root cause i cant seem to keep TWRP installed after 9.5.3, im currently on 10.3.0
Click to expand...
Click to collapse
You should be able to fastboot flash stock boot.img from the fastboot ROMs to get the phone running again: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
This will unroot the phone. But you should be able to easily root again by the method you did originally.
What is the problem you are having with installing TWRP? You haven't specifically described how you tried to install. I've had no issues using the TWRP installer zip, after multiple updates.
You need to re flash stock so, boot lastest twrp (fastboot boot twrp.img) and flash lastest stock rom.
And if you need an app as system use magisk module App Systemizer (you also need busybox module and Termux app from playstore) this is the only way (that I known) to convert user apps to system
Sent from my OnePlus7Pro using XDA Labs
redpoint73 said:
You should be able to fastboot flash stock boot.img from the fastboot ROMs to get the phone running again: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
This will unroot the phone. But you should be able to easily root again by the method you did originally.
What is the problem you are having with installing TWRP? You haven't specifically described how you tried to install. I've had no issues using the TWRP installer zip, after multiple updates.
Click to expand...
Click to collapse
Ive tried that it only boots to recivery, i restarted my phone completely with msm its wokring fine now but even after i root on 10.3.0 i still cant get twrp
when i try to install "fastboot flash twrp" it goes thru but it always boot loops to fastboot but when i flash the stock boot image it goes to normal and i can boot into the phone again
RokCruz said:
You need to re flash stock so, boot lastest twrp (fastboot boot twrp.img) and flash lastest stock rom.
And if you need an app as system use magisk module App Systemizer (you also need busybox module and Termux app from playstore) this is the only way (that I known) to convert user apps to system
Sent from my OnePlus7Pro using XDA Labs
Click to expand...
Click to collapse
tried that first part too, cant get into twrp and that makes sense now, i installed busy box but never opened the app to install to system/xbin
here's how ive done my part so far.. ever since i bricked my device last feb 24 , rendering it totally unresponsive.. that not even vol up & power button dont work
1. had to use msm tool just to boot my device. successfully boot my device to 9.5.3
2. device seemed to have a locked bootloader again so i un.lock it again. downloaded a patched 9.5.3 boot.img and flashed it via fastboot
3. successful root confirmed..
4. downloaded twrp 3.3.1-75 unofficial installer.. about 17.5mb. flashed it thru magisk as a module.. then install magisk ( as recommended) then reboot.
5. after a reboot.. and setting it up to my liking,, i reboot to twrp to flash the latest 10.3.1 stable rom..
6. flash twrp installer again.
7. hit reboot then choose Recovery . phone reboot to recovery again
8. flash magisk.zip which i downloaded earlier. then reboot.
done
updated to 10.3.1 with magisk & twrp intact..
btw.. i really dont know how to force my phone to reboot to twrp via PC ADB fastboot command.. easiest way for me to install TWRP is by flashing the TWRP INSTALLER as magisk module
cmurder61 said:
tried that first part too, cant get into twrp and that makes sense now, i installed busy box but never opened the app to install to system/xbin
Click to expand...
Click to collapse
Use busybox magisk module, don't install busybox apps!
Sent from my OnePlus7Pro using XDA Labs
cmurder61 said:
when i try to install "fastboot flash twrp" it goes thru but it always boot loops to fastboot but when i flash the stock boot image it goes to normal and i can boot into the phone again
Click to expand...
Click to collapse
That is because that is NOT the correct way to install TWRP img. You need to fastboot boot TWRP, then once in TWRP flash the TWRP installer zip, as I already mentioned.
This is described in the TWRP dev's thread (and you will see no mention of fastboot flash TWRP).
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Also make sure you use a current version of TWRP (latest is unofficial -76) which you can get from the above link.
redpoint73 said:
That is because that is NOT the correct way to install TWRP img. You need to fastboot boot TWRP, then once in TWRP flash the TWRP installer zip, as I already mentioned.
This is described in the TWRP dev's thread (and you will see no mention of fastboot flash TWRP).
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Also make sure you use a current version of TWRP (latest is unofficial -76) which you can get from the above link.
Click to expand...
Click to collapse
ive tried that still didn't work but illl try again i guess
santiagoruel13 said:
here's how ive done my part so far.. ever since i bricked my device last feb 24 , rendering it totally unresponsive.. that not even vol up & power button dont work
1. had to use msm tool just to boot my device. successfully boot my device to 9.5.3
2. device seemed to have a locked bootloader again so i un.lock it again. downloaded a patched 9.5.3 boot.img and flashed it via fastboot
3. successful root confirmed..
4. downloaded twrp 3.3.1-75 unofficial installer.. about 17.5mb. flashed it thru magisk as a module.. then install magisk ( as recommended) then reboot.
5. after a reboot.. and setting it up to my liking,, i reboot to twrp to flash the latest 10.3.1 stable rom..
6. flash twrp installer again.
7. hit reboot then choose Recovery . phone reboot to recovery again
8. flash magisk.zip which i downloaded earlier. then reboot.
done
updated to 10.3.1 with magisk & twrp intact..
btw.. i really dont know how to force my phone to reboot to twrp via PC ADB fastboot command.. easiest way for me to install TWRP is by flashing the TWRP INSTALLER as magisk module
Click to expand...
Click to collapse
See the way u did it is diff, i did not root first before installing twrp or install twrp as a magisk mod, what is the mod for magisk? where do i get it
cmurder61 said:
See the way u did it is diff, i did not root first before installing twrp or install twrp as a magisk mod, what is the mod for magisk? where do i get it
Click to expand...
Click to collapse
i just simplified it as magisk mod.. but in TWRP THREAD,, its named by maoronofrio as TWRP UNIFIED UNOFFICIAL INSTALLER
and it can only be installed by installing it as magisk module
here's the link
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943
After i tried to install busybox trough magisk manager on my 7 pro i can't boot in to the system anymore, I already deleted all magisk modules trough recovery and it is still booting directly in to fastboot mode.
Is there any way to boot in to the system again without flashing stock rom ?
Twrp is still accessible.
Im running Android 10, the newest magisk and the newest twrp.
Edit: found the solution, i Just used the fix Recovery bootloop option in twrp and it worked all fine but i needed to flash magisk again
powerbuffboy said:
After i tried to install busybox trough magisk manager on my 7 pro i can't boot in to the system anymore, I already deleted all magisk modules trough recovery and it is still booting directly in to fastboot mode.
Is there any way to boot in to the system again without flashing stock rom ?
Twrp is still accessible.
Im running Android 10, the newest magisk and the newest twrp.
Edit: found the solution, i Just used the fix Recovery bootloop option in twrp and it worked all fine but i needed to flash magisk again
Click to expand...
Click to collapse
Hey powerbuffboy, I have the same issue,
I can't seem to find this "fix recovery bootloop" option.
What version of TWRP are you running?
powerbuffboy said:
After i tried to install busybox trough magisk manager on my 7 pro i can't boot in to the system anymore, I already deleted all magisk modules trough recovery and it is still booting directly in to fastboot mode.
Is there any way to boot in to the system again without flashing stock rom ?
Twrp is still accessible.
Im running Android 10, the newest magisk and the newest twrp.
Edit: found the solution, i Just used the fix Recovery bootloop option in twrp and it worked all fine but i needed to flash magisk again
Click to expand...
Click to collapse
You can also try to flash boot.img ... It may fixed the issue
powerbuffboy said:
After i tried to install busybox trough magisk manager on my 7 pro i can't boot in to the system anymore, I already deleted all magisk modules trough recovery and it is still booting directly in to fastboot mode.
Is there any way to boot in to the system again without flashing stock rom ?
Twrp is still accessible.
Im running Android 10, the newest magisk and the newest twrp.
Edit: found the solution, i Just used the fix Recovery bootloop option in twrp and it worked all fine but i needed to flash magisk again
Click to expand...
Click to collapse
Same problem, solved in same way, but i cant install Magisk again without going to bootloop
Cronoss said:
Hey powerbuffboy, I have the same issue,
I can't seem to find this "fix recovery bootloop" option.
What version of TWRP are you running?
Click to expand...
Click to collapse
Go to TWRP/ Advanced and click on Fix Recovery Bootloop
PS.
Im talking about TWRP 3.3.1.79-maurofrio
PPS.
You will lose ROOT
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).