Related
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
what method did you use (there are a million rooted guides)? did u get the correct OS OTA for you model phone? provide us more info please.
Looks like i forgot to turn off the magisk modules. I had to go into twrp and delete them all and re download the modules. silly me
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
jakemaxfield said:
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
Click to expand...
Click to collapse
I stuck at the same situation. Can you flashboot flash boot.img and then it can boot normally?
Same problem here.
Situation before flash: stock 9.5.8, Magisk, a number of Magisk modules
What I did:
* downloaded 9.5.9 with Oxygen Updater
* disabled Magisk modules
* rebooted
* installed 9.5.9 from the builtin System Update
* went to Magisk, installed it with After OTA
* rebooted to recovery
* installed TWRP and Magisk
* cleared Dalvik
* rebooted to system
The phone seems to start normally, but when it reaches the unlock screen it immediately goes to Power Off, then it reboots to TWRP (not power off). From TWRP I can decrypt data ok etc.
I tried reinstalling the boot loader, OTA image, TWRP, Magisk - same result. Rebooting to system from TWRP just goes back to Power Off then TWRP.
equlizer said:
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
Click to expand...
Click to collapse
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
manor7777 said:
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
Click to expand...
Click to collapse
That's exactly what I did. It landed me to the bootloop.
All you guys had to do is,
Install the full uddate zip in twrp,
Install the latest twrp zip,
Reboot recovery,
Install latest magisk,
Reboot system,
Hope this helps, cheers
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
lcd047 said:
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
Click to expand...
Click to collapse
I'm in the same boat.
My twrp doesn't offer to decrypt partition_b so I cannot manually install Magisk on the new partition.
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
sapalot said:
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
It worked for me for 9.5.8, got the bootloop this time around. I guess this means I'm not the Chosen One.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
djsubterrain said:
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
Click to expand...
Click to collapse
I tried that too. When I switch to the other slot I get to a menu where I can only wipe data, reboot to boot loader, or reboot to recovery. Not particularly useful.
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
mkos86 said:
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
Click to expand...
Click to collapse
What I had to do here was go to fastboot mode and flash twrp img. Then in TWRP I flash the TWRP zip file and magisk and rebooted. All good
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
jakemaxfield said:
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
Click to expand...
Click to collapse
Thank you sir, this fixed it for me, too. So the missing link was that Magisk modules have to be removed completely, not just disabled, before upgrading. Removing all directories except .core from /data/adb/modules allows the phone to boot normally, with Magisk enabled.
schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
Thats the way i tried that time and got stuck in bootloop.
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?
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.
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.
Hey, after installing android 11 on my Oneplus 6 I have servere issues on getting root back.
Both methods I used result in a stuck boot.
Method 1: fastboot boot twrp, then install magisk.zip (tried with both 21.4 (last with a zip) and the renamed 23.0 (from apk to zip)
Method 2: Extracted boot.img from my OTA update, then patched with magisk 23.0.
Flashed the new boot.img -with fastboot -with twrp both result in a stuck boot.
Suprisingly flashing the extracted boot.img from the OTA boots fine, but that image is without magisk
Update: I have extracted the boot.img directly from the phone, patched it and it still doesn't work
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Thratchen said:
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Click to expand...
Click to collapse
twrp actually works, but after flashing magisk or flashing a magisk boot.img it breaks. I have a working version here
Ping me if you get magisk working
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
To remember!
Thratchen said:
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
Click to expand...
Click to collapse
Which installation method of magisk did you use?
How long did you wait after first boot?
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Thratchen said:
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Click to expand...
Click to collapse
Thanks for the reply, as a last question: Which magisk version did you use (could you link i?t). I assume you took the magisk v23 apk and renamed it to .zip? or what did you do?
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Thratchen said:
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Click to expand...
Click to collapse
Hmm, I perfectly copied your instructions and still get a bootloop. Even reflashed 11.1.1.1 again. Might be time for a reset
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
vkass said:
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
Click to expand...
Click to collapse
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp latest zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
tacohell said:
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp lat est zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
Click to expand...
Click to collapse
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
UraniumDonut said:
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
Click to expand...
Click to collapse
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
vkass said:
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
Click to expand...
Click to collapse
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
UraniumDonut said:
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
Click to expand...
Click to collapse
Thhank @UraniumDonut - that worked - I have never before used that method and honestly didn't even know about it. I use the official documented twrp way which is to first fastboot in to twrp and then install the zip file which has to be located on the phone file system. This method seems a lot easier!
As to magisk, I usually flash that from twrp using the zip file method and never have had any issues. But with all the issues surrounding oos 11 I am playing it safe as I don't want to get in to a boot loop. Will do some more research before I try something. But thanks to you I have made 1 step forward progress!
UraniumDonut said:
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
Click to expand...
Click to collapse
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
vkass said:
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
Click to expand...
Click to collapse
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Just for reference here
UraniumDonut said:
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Click to expand...
Click to collapse
I posted detailed steps if you want to give this a try @UraniumDonut: https://forum.xda-developers.com/t/how-to-root-op6-11-1-1-1.4344269/#post-85765879