I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Goooober said:
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Click to expand...
Click to collapse
Use the msm tool to recover your device...
Try booting into the mauronofrio twrp recovery from fastboot. Then wipe the system partition and reinstall your rom.
Then boot mauronofrio twrp again from fastboot and install the zip, and reboot to recovery.
Install custom kernel, Magisk.
Uninstall edexposed
People reply here with no clue and advise to just restore stock. How is this a solution and how did not OP think of it themselves?
This is too little too late, but maybe it helps someone else:
Unofficial TWRP for Android 10 is glitchy. E.g. nanodroid backups are not restoring properly. Given current A/B mess this is not at all surprising.
Solution: wipe everything, reinstall *same* lineageOS version as before, flash same gapps as you had, and if you took the nanodroid backup after magisk, install it as well.
Don't boot yet!
Restore the backup *partially*, e.g. only the data partition.
This should work.
Or, emh, it did for me with some minor glitches. But even Google Authenticator didn't notice spoofing (otherwise RIP my accounts). So, i definitely recommend trying this workaround.
Related
I had rooted my phone on OOS 9.5.8, installed TWRP and magisk, i updated to 9.5.10 without issues, tried installing TWRP again as well as magisk, and my phone went on a bootloop, after several hours of trying to fix it, i decided to use my twrp backup thinking that would fix the issue, i restore everything and my phone is still bootlooping, any ideas how to fix it?
did u remove your magisk modules?
Maybe the backup was from slot A and OTA in slot B and something got messed up. In another note there's no need to clean install OTAs from Oneplus, and then having to restore old data is where complications come
Karmonator said:
I had rooted my phone on OOS 9.5.8, installed TWRP and magisk, i updated to 9.5.10 without issues, tried installing TWRP again as well as magisk, and my phone went on a bootloop, after several hours of trying to fix it, i decided to use my twrp backup thinking that would fix the issue, i restore everything and my phone is still bootlooping, any ideas how to fix it?
Click to expand...
Click to collapse
I had this problem, minus the TWRP. I had to reset to factory default to fix it. Goto bootloader and reset system settings. You'll end up back on 9.5.10 stock but you should be able to boot. Pain in the ass but it stopped my loops. I didn't have a x.x.10 backup so I had to start fresh.
Try to remove Magisk using Magisk unninstaller and reinstall 9.5.10 on TWRP without rebooting.
After, install TWRP installer again and THEN reboot.
After you check all is working, install Magisk again in TWRP and then install your Magisk modules again.
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
Please bear with me.
I was about to upgrade from Magisk 19.4 to 20 and I tapped on "Install to inactive slot (after OTA)" instead of the recommended option "Direct install), then clicked yes without reading because I though I tapped the correct option... and after that, without rebooting, I tapped the Direct install option and rebooted. (Yup, I effed up that whole part.)
Then, when booting up the phone got stuck in fastboot.
I followed @Arden144's steps to install twrp and I was able to boot into twrp and flash magisk.
If I go to power options and tap on reboot to OS, it boots fine and I have Magisk 20. My modules are still there and everything seems fine. Wi-Fi, fingerprint sensor and SafetyNet are fine.
BUT! Now, for my actual problem:
Whenever I use advanced reboot to go to the recovery, go to recovery through Magisk Manager, press Volume Down + Power to boot into recovery or even select "Recovery" in TWRP's power menu, the phone just goes to fasboot and I can't enter the recovery unless I "fastboot flash" a recovery.
Thankfully if I select "Start", the phone starts fine. Previously it just looped back to the fastboot but seems that reflashing twrp at least fixed that.
But yeah, I can't enter TWRP without a computer to fastboot, which sucks.
What can I do? Flashing twrp doesn't seem to stick.
Thank you for any advice you can give me!
Deses said:
Please bear with me.
I was about to upgrade from Magisk 19.4 to 20 and I tapped on "Install to inactive slot (after OTA)" instead of the recommended option "Direct install), then clicked yes without reading because I though I tapped the correct option... and after that, without rebooting, I tapped the Direct install option and rebooted. (Yup, I effed up that whole part.)
Then, when booting up the phone got stuck in fastboot.
I followed @Arden144's steps to install twrp and I was able to boot into twrp and flash magisk.
If I go to power options and tap on reboot to OS, it boots fine and I have Magisk 20. My modules are still there and everything seems fine. Wi-Fi, fingerprint sensor and SafetyNet are fine.
BUT! Now, for my actual problem:
Whenever I use advanced reboot to go to the recovery, go to recovery through Magisk Manager, press Volume Down + Power to boot into recovery or even select "Recovery" in TWRP's power menu, the phone just goes to fasboot and I can't enter the recovery unless I "fastboot flash" a recovery.
Thankfully if I select "Start", the phone starts fine. Previously it just looped back to the fastboot but seems that reflashing twrp at least fixed that.
But yeah, I can't enter TWRP without a computer to fastboot, which sucks.
What can I do? Flashing twrp doesn't seem to stick.
Thank you for any advice you can give me!
Click to expand...
Click to collapse
There's a known issue with Magisk 20 that makes TWRP not stay installed. Downgrade to 19.4 or hold tight without TWRP
Arden144 said:
There's a known issue with Magisk 20 that makes TWRP not stay installed. Downgrade to 19.4 or hold tight without TWRP
Click to expand...
Click to collapse
Oooh. What an awful moment to have this problem, then.
Unfortunately, I reflashed Magisk, (Manager now shows 19.4) but TWRP doesn't stay installed... What worries me is that not even the stock recovery is available to use, just fastboot.
Deses said:
Oooh. What an awful moment to have this problem, then.
Unfortunately, I reflashed Magisk, (Manager now shows 19.4) but TWRP doesn't stay installed... What worries me is that not even the stock recovery is available to use, just fastboot.
Click to expand...
Click to collapse
You can try using the Magisk Canary Uninstaller to completely clean up the Magisk install, or dirty flash the stock ROM
Magisk 20.1 works for me with latest TWRP.
have you tried installing TWRP as a magisk module?
Try this..
To solve the prroblem
1. Reflash the latest rom.you have using system.update...
2. Install magisk to inactive slot
3. Reboot
4. Goto magisk and flash twrp installer v70..
5. Install magisk again as recommended..
Reboot...
when that happened to me i grabbed magisk uninstaller and fadtboot booted twrp flash magisk uninstaller then twrp zip reflashed magisk 20. whatever new version of magisk is
Deses said:
What can I do? Flashing twrp doesn't seem to stick.
Click to expand...
Click to collapse
Flash twrp to ramdisk. It should stick. I have it installed to ramdisk. Also updated from 19.3 to 20 with twrp still there.
Same happened to me. No recovery partition it seems. Lol going to try ecompton's suggestion later.
aNGERY said:
have you tried installing TWRP as a magisk module?
Click to expand...
Click to collapse
Makes no difference. Also, the TWRP issues are pretty random. I have no issues on ob3 with Magisk 20 and TWRP 70
TheKnux said:
Magisk 20.1 works for me with latest TWRP.
Click to expand...
Click to collapse
Me too.
OK, so only way I restored access to my recovery was to flash the OTA update and the stock recovery was there... after that I reflashed TWRP and I can access it just fine.
Please help me i have mistacke i unstall magisk now i went to restore root
I had latest magisk (stable version) installed and tried to disable it from magisk manager->uninstall->restore images.
when i restarted the phone it stuck on bootloader screen.
I tried to got to twrp recovery mode and it's stuck on the flash screen.
Why would magisk manager put a button which is not working at all and bricks the phone? Please guide me what to do.
JerryGoyal said:
I had latest magisk (stable version) installed and tried to disable it from magisk manager->uninstall->restore images.
when i restarted the phone it stuck on bootloader screen.
I tried to got to twrp recovery mode and it's stuck on the flash screen.
Why would magisk manager put a button which is not working at all and bricks the phone? Please guide me what to do.
Click to expand...
Click to collapse
Maybe you did something wrong and this isn't Magisk fault ?
Go to twrp and wipe system and vendor DO NOT REBOOT, flash OOS zip and twrp again, and it shall work,
NOTE: you will NOT lose any files or data
J0nhy said:
Go to twrp and wipe system and vendor DO NOT REBOOT, flash OOS zip and twrp again, and it shall work,
NOTE: you will NOT lose any files or data
Click to expand...
Click to collapse
too late for me i wiped all data. Thanks though, it shall help future readers.
next time, before wipe, try to flash magisk uninstaller first
Try to flash stock boot image.
I installed Magisk via twrp(Temp version). and installed a bunch of modules.
Then I decided to complexly uninstall Magisk. I've done that from the Magisk Manager apk(The Complete Uninstall button)..
The phone rebooted and stuck into the phone logo with red danger logo. which means perhaps the boot img is missing ?
I should have uninstalled the modules first, which might have caused this issue..
Now, I Flashed Magisk again via Temp twrp, but now few apps keeps crashing, even after uninstalling and installing them.
i don't have the stock bot image, otherwise i guess i can do fastboot boot boot.img to escape the boot issue after uninstalling Magisk from the app
Note : i tried flashing the uninstall zip file from twrp but that didn't work, Magisk framework still exists !
What should i do now ?
My HTC is the duel sim version (Asia) and i'm using Magisk 22 latest version
Have you tried cleaning dalvik cache?
XDHx86 said:
Have you tried cleaning dalvik cache?
Click to expand...
Click to collapse
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu
Coldz0 said:
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu
Click to expand...
Click to collapse
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root
XDHx86 said:
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root
Click to expand...
Click to collapse
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !
Coldz0 said:
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !
Click to expand...
Click to collapse
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.
XDHx86 said:
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.
Click to expand...
Click to collapse
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)
Coldz0 said:
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)
Click to expand...
Click to collapse
You can find your device's ROM here (Literally first google results..):
HTC website
HTC dev center
GetDriodTips (Only for U12+)
**Disclaimer:** I don't own any of those ROMs and I don't hold responsibility whatsoever should you brick your phone or anything goes awry.
had exactly the same issue and exactly due to the same reason (I hate those pseudo-secure banking apps).
I couldn't wipe dalvik as TWRP is still not available for my P5.
But it was fixable really easy by reflashing the patched boot.img:
run command "fastboot flash boot magisk_patched.img"
btw I'm still looking for a solution for that stupid banking app.
I tried the above mentioned "magisk hide" and "safety net fix" and tried hiding the app itself but all that does not help.
Can we delete magisk and still use the phone rooted ? Or will it unroot my phone if magisk is removed. I’m planning to sell my s10 and the buyer does not want the application.
Good information from GetDriodTips (Only for U12+). Thank you.