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
Related
Hi guys,
I downloaded the latest OTA 5.1.9 (full zip), booted to TWRP, flashed the OTA, flashed TWRP 3.2.2.0, rebooted to recovery and flashed Magisk ... same procedure as the last OTA's, but know I get the message "There's an internal problem with your device contact your device manufacturer" on entering the ROM where I have to enter my PIN.
Redownloaded the ROM and flashed again, but the same message occurs. The phone seems to be working but I am a little bit worried.
I appreciate every help oder idea
dre-z said:
Hi guys,
I downloaded the latest OTA 5.1.9 (full zip), booted to TWRP, flashed the OTA, flashed TWRP 3.2.2.0, rebooted to recovery and flashed Magisk ... same procedure as the last OTA's, but know I get the message "There's an internal problem with your device contact your device manufacturer" on entering the ROM where I have to enter my PIN.
Redownloaded the ROM and flashed again, but the same message occurs. The phone seems to be working but I am a little bit worried.
I appreciate every help oder idea
Click to expand...
Click to collapse
It did that to me too. It is a pain but this worked for me to get rid of it.
1. Used a fastboot rom to install 5.1.8 (back to factory)
2. Completed setup
3. Did the whole thing to install TWRP.
4. Flashed Magisk
5. Restored by TWRP backup from before all this started
6. Let everything boot up and downloaded the full download for 5.1.9
7. Flashed the full 5.1.9 in TWRP, and flashed TWRP.
8. Reboot recovery
9. Flashed Magisk 16.4 (not the newer 16.6)
10. Boot to system
11. Use Magisk manager app to update Magisk to 16.6
Every time I have ever flashed Magisk 16.6 I get that same notice you get. Whenever I flash 16.4 and let it update Magisk from there everything is perfect.
tabletalker7 said:
It did that to me too. It is a pain but this worked for me to get rid of it.
1. Used a fastboot rom to install 5.1.8 (back to factory)
2. Completed setup
3. Did the whole thing to install TWRP.
4. Flashed Magisk
5. Restored by TWRP backup from before all this started
6. Let everything boot up and downloaded the full download for 5.1.9
7. Flashed the full 5.1.9 in TWRP, and flashed TWRP.
8. Reboot recovery
9. Flashed Magisk 16.4 (not the newer 16.6)
10. Boot to system
11. Use Magisk manager app to update Magisk to 16.6
Every time I have ever flashed Magisk 16.6 I get that same notice you get. Whenever I flash 16.4 and let it update Magisk from there everything is perfect.
Click to expand...
Click to collapse
Thank you very much, the tip with flashing magisk 16.4 worked! I didn't need to go back, I just reflashed 5.1.9 without magisk and the error was gone.
Hi, I got the same problem.
Until I flashed my custom kernel ElementalX the messege disapeared
Will it work only to flash 16.4 over 16.6 or uninstall 16.6 and then flash 16.4?
why dont you guys stick with stabe 16.0?
I did uninstall of 16.6 and then install 16.4, no error message anymore. Didn't flash directly over it.
Tried as you said but still got that message.
Deacon-Frost said:
Will it work only to flash 16.4 over 16.6 or uninstall 16.6 and then flash 16.4?
Click to expand...
Click to collapse
When you install the update to 5.1.9 you have to reflash Magisk. I just used Magisk 16.4 when I did it.
I can confirm completely uninstalling magisk and then installing 16.0 with an upgrade to 16.6 solves the error
Try this.
https://forum.xda-developers.com/sho...&postcount=386
I had the same problem and this fixed it for me.
The easiest way is explained by XDA user "airtower", read his response at:
https://forum.xda-developers.com/on...-oneplus-6-t3794232/post77104551#post77104551
Thanks!
This hint was really helpful and is highly appreciated. The message is gone. :thumbup:
Uninstall in Magisk app, select restore images. Do not reboot and install it via app again and now you can reboot that's it. very simple
Guys just flash magisk 16.6. It will work without the error message. Just after you flash, boot into system. Then go into magisk manager and click on Uninstall and then Restore Images. Then right away, without rebooting, install using the Direct Install method and making sure that both of the "preserve" options are checked in Advanced Settings before installing it.
So I finally pulled the trigger on updating my Oneplus 6 to the latest OTA PIE update, but when the phone reboots it goes to the system for 2 seconds then immediately reboots to TWRP recovery. I followed the instructions from a thread here that said to immediately flash the TWRP A/B zip from Magisk, followed by clicking install for Magisk to the inactive slot. Now I can't get my system to boot up properly and I'm only able to access TWRP recovery. What should I do, I'm basically locked out of my phone now?!
Module or theme error, flash magisk uninstaller, flash magisk and boot.
If it still doesn't boot, flash magisk uninstaller boot system and remove theme overlays (like substratum or Swift installer)
whizeguy said:
Module or theme error, flash magisk uninstaller, flash magisk and boot.
If it still doesn't boot, flash magisk uninstaller boot system and remove theme overlays (like substratum or Swift installer)
Click to expand...
Click to collapse
I've tried flashing magisk uninstaller 5 times, same result no matter what I do. I finally just wiped the Data partition from twrp and then system boots. I just have to set everything back up on my phone now.
Ive tried uninstalling magisk using the un-installer and no go. Ive tried booting into twrp then flashing the twrp zip then rebooting into recovery and it goes to the stock recovery. How do i get back TWRP?? Im on Pie and was using twrp .65
NVM: I had to re-flash 9.5.11 then twrp then reboot then magisk 19.4
I am in your same situation oneplus7.
Currently I was with twrp 3.3.1.1 but there is no way to catch any recovery. By flashing the image either version 1/65/70 (more current) by fastboot it enters correctly img you access twrp to later flash the zip But it never gets installed.
I tried to uninstall using img twrp Magisk zip uninstaller and install the 19.3 / 20v uninstall it completely and flash back to zip twrp but I am in a dead end.
Right now I am with Magisk v20 root edxposed and everything goes phenomenally as a result that I am going to "peel" without having twrp for my backups or anything.
Anyone have any idea how to install twrp again?
boot into twrp.img then flash the last rom you were using, then flash twrp.zip, reboot into recovery and install magisk 19.4. After reboot you will have to enable all your rooted apps again and install your magisk modules again.
Phone currently rooted and using xxxNolimits rom and Smurf kernel
Update available and getting below warning.
So if I update do I have to start from scratch again and re root.
So download update and then don't reboot system but reboot to twrp and flash Magisk again or do I flash updates and then Magisk
Confused dot com
Come on man, any amount of threads and answers to this throughout the forum via the search box.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
hallo dare said:
Come on man, any amount of threads and answers to this throughout the forum via the search box.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Click to expand...
Click to collapse
Fair cop on my behalf?
Just was not sure what to remove in Magisk as have few modules installed including substratum, you tube vanced theme, systemless hosts and xxxNolimits.
Take it just first 2 I remove
I always flash TWRP as a magisk module before rebooting, reboot into recovery, flash TWRP again, reboot into recovery again (unnecessary I'm sure, but i'm paranoid), then flash magisk, reboot into system and good to go.
funkyirishman said:
Fair cop on my behalf
Just was not sure what to remove in Magisk as have few modules installed including substratum, you tube vanced theme, systemless hosts and xxxNolimits.
Take it just first 2 I remove
Click to expand...
Click to collapse
To be sure to be sure i always remove all modules and reboot phone before doing any updates.
aNGERY said:
I always flash TWRP as a magisk module before rebooting, reboot into recovery, flash TWRP again, reboot into recovery again (unnecessary I'm sure, but i'm paranoid), then flash magisk, reboot into system and good to go.
Click to expand...
Click to collapse
That's what I've done wrong and lose twrp after updates. I need to reboot to recovery with adb commands and install twrp.
sportytony said:
That's what I've done wrong and lose twrp after updates. I need to reboot to recovery with adb commands and install twrp.
Click to expand...
Click to collapse
TWRP is installed to boot partition on this device (no discrete recovery partition). So anytime you update, the boot partition is overwritten with a new stock boot partition (therefore, no TWRP). To update and stay rooted and with TWRP, simply OTA update, do NOT reboot. Go to Magisk Manager. Flash TWRP installer zip as if it were a Magisk module. It will say you are unrooted, so (again, in Magisk Manager) install Magisk again, picking the option "Install to inactive slot (after OTA)". Reboot, and you should be updated and still rooted.
That's how I update everytime. But sometimes just for hahas, I've rebooted to recovery, just because, and it would reboot to factory recovery , and twrp wasn't there. I was rooted, just no twrp. ( I know weird)
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