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.
Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Not sure what to do at this point. Any ideas?
Thanks!
mobbdeep said:
Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Edit sorry I updated magisk and now I don't have twrp
Not sure what to do at this point. Any ideas?
Thanks!
Click to expand...
Click to collapse
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry
SirFronts said:
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry
Click to expand...
Click to collapse
I guess I will just backup my phone completely, factory reset it, and re-root the device again.
mobbdeep said:
I guess I will just backup my phone completely, factory reset it, and re-root the device again.
Click to expand...
Click to collapse
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
I'll give that a try tonight.
I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?
SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
alex.coffen said:
I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?
Click to expand...
Click to collapse
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Boot TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
I tried something and soft bricked my phone...
Anyway, lucky that I did a backup with twrp for boot when magisk was 19.3, then i can get into twrp by "fastboot boot" the twrp boot img temporarily and restored the boot.
Now everything works fine.
Ps: fastboot boot is not 100% safe...
mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
My TWRP is gone too. But I can temporarily get in TWRP using my computer.
How do I flash OOS firmware? I am currently on PIE 9.5.13 intl. version. Should I download the full zip OOS and then flash it via TWRP ?
Then flash TWRP ?
And then flash Magisk 19.4 ?
Another question: DO you think uninstalling magisk via magisk uninstaller and installing the canary version of it would allow TWRP to stick ? There's threads that mention that the canary version doesn't erase TWRP.
mobbdeep said:
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.
redpoint73 said:
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.
Click to expand...
Click to collapse
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh?
Dogstarlooma said:
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh
Click to expand...
Click to collapse
I just read that Magisk 20 has a bug, that prevents TWRP from "sticking", and to use 20.1 (or in your case, looks like 19.4).
Anyone know how to fix this problem? I flash using twrp 3.3.1.70 and using Magisk v20. Every time I root the oxygen os 10.1, it seems to work fine but only the wifi won't stick. From what I can tell the wifi won't connect to any network and after a brief search it shuts off automatically. I have a oneplus 7 pro 1917
It happened to me as well. Sometimes, the boot version is meant for a similar version but not the same, and the phone loses the drivers to the wifi. You might need to download the full original stock and flash it again to get the drivers back, however, you will need to deal on how to root it afterwards.
Have you tried
Rooting via flashing your phone with a pre patched boot img?? Then install magisk. Install twrp via magisk???
The only way I have been able to get this to work is use the MSM tool to stock firmware. I root the device and then manually update to 10.0.1, but when i restart, it gets stuck in a boot loop back to fastboot mode. to to get out of the boot loop, I use TWRP boot loop recovery, however, this also removes the rooted device.
Hi there,
after a few unplaned experiments this week I think it's a problem with the unlocked bootloader.
I have an unlocked BL and rooted Device via Magisk (V20.0.0).
1) After the first OTA my device did not restart with Qualcomm crash mode -> dm-varity - device corrupted.
2) I had reflashed my OP7 pro with the msm-tool back to 9.5.3AA. Then unlocked and rootet again. Everything worked fine.
3) OTA to 10.0.1AA -> No Wifi, unstable Bluetooth, No Speakers (Calling and Music/Video), Camera crashed and i regulary needed to reboot afterwards.
4) Again MSM-downgrade to Android 9, direct upgrade to 10.0.1AA with locked BL. Everything was OK (WiFi, BT, Speakers, Camera)
5) Unlocked again, then i has the same Problems as described on 3).
Can someone confirm if it's a problem with the unlocked BL.
Hopefully it is fixed with the next Update.
18os13 said:
The only way I have been able to get this to work is use the MSM tool to stock firmware. I root the device and then manually update to 10.0.1, but when i restart, it gets stuck in a boot loop back to fastboot mode. to to get out of the boot loop, I use TWRP boot loop recovery, however, this also removes the rooted device.
Click to expand...
Click to collapse
Hmm. .. if you have a TWRP..
WHY NOT just
1. Flash a 10.0.1 full rom
2. Flash TWRP INSTALLER
3. REBOOT TO TWRP
4. FLASH MAGISK??
5. REBOOT
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
etwas42 said:
Hi there,
after a few unplaned experiments this week I think it's a problem with the unlocked bootloader.
I have an unlocked BL and rooted Device via Magisk (V20.0.0).
1) After the first OTA my device did not restart with Qualcomm crash mode -> dm-varity - device corrupted.
2) I had reflashed my OP7 pro with the msm-tool back to 9.5.3AA. Then unlocked and rootet again. Everything worked fine.
3) OTA to 10.0.1AA -> No Wifi, unstable Bluetooth, No Speakers (Calling and Music/Video), Camera crashed and i regulary needed to reboot afterwards.
4) Again MSM-downgrade to Android 9, direct upgrade to 10.0.1AA with locked BL. Everything was OK (WiFi, BT, Speakers, Camera)
5) Unlocked again, then i has the same Problems as described on 3).
Can someone confirm if it's a problem with the unlocked BL.
Hopefully it is fixed with the next Update.
Click to expand...
Click to collapse
Nope.. unlocking the bootloader doesnt have anything to do wity your problem..
Hm.. have you tried the steps i mentioned above??
If you have magisk v20.. why not
1. Install twrp v70 via magisk..
2. Install magisk again (choose recommended)
3. Reboot to twrp
4. Flash a full android 10.0.1 rom
5. Re flash twrp installer
6. Reboot to twrp again
7. Flash magisk v20
8. Reboot.
I saw this in a kernel flash thread. It may help but can't confirm. Although I have run into similar issues after rooting then trying the no limits optimizations. I finally decided not to use it because it kept breaking my wifi and USB c audio. Try this maybe it will help?
From kirusakura kernel thread.
"Question: My WiFi is not working after flashing the kernel. I can´t toggle it on.
Answer: That means something happened to your device, that is causing some stuff to not get loaded properly when booting. I ran into the same issue once. Read through the thread to find the cause.
I wrote a guide in the linked thread, that explains step by step, how to return to a working condition without the need to wipe the phone completely.
Click the following link to find the post: post is linked here
"
santiagoruel13 said:
Hmm. .. if you have a TWRP..
WHY NOT just
1. Flash a 10.0.1 full rom
2. Flash TWRP INSTALLER
3. REBOOT TO TWRP
4. FLASH MAGISK??
5. REBOOT
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
Nope.. unlocking the bootloader doesnt have anything to do wity your problem..
Hm.. have you tried the steps i mentioned above??
If you have magisk v20.. why not
1. Install twrp v70 via magisk..
2. Install magisk again (choose recommended)
3. Reboot to twrp
4. Flash a full android 10.0.1 rom
5. Re flash twrp installer
6. Reboot to twrp again
7. Flash magisk v20
8. Reboot.
Click to expand...
Click to collapse
Problem is even when it initally roots after I restart it does not work anymore. The only way I have been able to do it somewhat successfully is through using an older version of magisk.
Hey guys the best and fastest way to resolve this is to install a custom kernel. Took me less than 5 minutes and it works now!
sonvotrung said:
Hey guys the best and fastest way to resolve this is to install a custom kernel. Took me less than 5 minutes and it works now!
Click to expand...
Click to collapse
Yeah for me it solved the problem. After the TWRP and Magisk install i didn't able to use wifi. But after i installed a custom kernel (arter97 r32) the wifi works again! Thanks!
Guys, I lost root after OTA from 9 to 10.0.1. To try to recover it I have done:
1. I reinstalled TWRP
fastboot flash boot twrp-3.3.1-71-guacamole-unified-Q-mauronofrio.img
Click to expand...
Click to collapse
On TWRP:
2. uninstalled Magisk using Magisk-uninstaller-20191102.zip
3. installed full OOS 10.0.1 OnePlus7ProOxygen_21.O.21_OTA_021_all_1910071446_6f7c731d5aa7dbe.zip
4. run the twrp installer twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
5. Reboot into Recovery twrp again without issue
6. Installed Magisk Magisk-v20.1.zip
7. Reboot into System
Root still doesn't work. What am I doing wrong?
PS: When my wifi broke after the update, I re-flashed the boot.img from OOS 10.0.1 OnePlus7ProOxygen_21.O.21_OTA_021_all_1910071446_6f7c731d5aa7dbe.zip and all worked fine.
haverlok said:
PS: When my wifi broke after the update, I re-flashed the boot.img from OOS 10.0.1 OnePlus7ProOxygen_21.O.21_OTA_021_all_1910071446_6f7c731d5aa7dbe.zip and all worked fine.
Click to expand...
Click to collapse
I flashed a Magisk-patched boot image and lost wifi, but the phone never gained root; I tried to reflash the stock boot image to fix the wifi but nothing has changed. I seem to be stuck with no wifi and no way to reflash anything in TWRP. Any ideas?
isellmidgets said:
I flashed a Magisk-patched boot image and lost wifi, but the phone never gained root; I tried to reflash the stock boot image to fix the wifi but nothing has changed. I seem to be stuck with no wifi and no way to reflash anything in TWRP. Any ideas?
Click to expand...
Click to collapse
I have moved away from OOS. Too many unknown apks. I am now using LOS17 no issues so far and GCam.
Hi,
I have a rather odd problem:
My phone simply does not boot when Magisk is installed
Installed Magisk 20.0 on Stock 10.0.1-GM21BA a while ago and everything was fine.
Today it won't boot any more (stuck on the warning that my bootloader is unlocked, then bounces to fastboot)
As soon as I uninstall Magisk from TWRP it boots again
Then I Install Magisk 20.1 from TWRP, it does not boot.
Then I uninstall Magisk 20.1 from TWRP, it boots again
Then I flash the pre-patched boot image from here and it does not boot again
Then I flash the stock boot image from here and it boots again
I also tried installing Magisk without dm-verity (only forceencrypt), still not booting beyond unlock warning and fastboot
Does someone know what is going on with my phone
Can I root it without Magisk?
Thank you for any help
Try TWRP 70
Maybe you're on twrp v71... Try reverting to the older v70
had same problem.i reflashed stock and locked bootloader back to offical, andriod 10 lets twrp work but not masgik. i even used magisk manager to patch file and flashed that file to have no more root
NateDev said:
Try TWRP 70
Click to expand...
Click to collapse
santiagoruel13 said:
Maybe you're on twrp v71... Try reverting to the older v70
Click to expand...
Click to collapse
Thanks for the ideas, did not fix it unfortunately
Guess I will stay without Magisk for now
do you have any modules hanging out?
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
you could try that.
Hmm.
Try this with twrp v70
1. Boot to twrp
2. Flash the full a10.0.1 rom
3. Flash twrp v70
4. Reboot to twrp
5. Flash magisk v20.
Reboot
Thats what i do if something is wrong.. i always reflash a rom..
---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------
Re flashing a rom also saved my friend's phone..after flashing boot.img for rooting purposes..he always boot without a wifi. So we dirty flash a rom.first . Then using that same rom that we flashed.. we extrscted its boot.img then patched it with magisk. Then re flashed.. then boom.. its working now..
Reflashing the full a10.0.1 rom.solved the issue..
---------- Post added at 07:24 AM ---------- Previous post was at 07:22 AM ----------
My idea here is that
Flash the rom..
Then using the rom that you just flashed..
Get its boot.img.. then patch it then flash it again.. it will now boot. I havent tried directly flashing a patched boot.img without reflashing the rom first..
I met the same problem this morning. Did the following thing to let phone boot with magisk.
1. install magisk 74
2. install Magisk-uninstaller-20200110.zip
3. reboot magisk
4. install magisk-v20.3.zip
5. boot system
coolguy001 said:
I met the same problem this morning. Did the following thing to let phone boot with magisk.
1. install magisk 74
2. install Magisk-uninstaller-20200110.zip
3. reboot magisk
4. install magisk-v20.3.zip
5. boot system
Click to expand...
Click to collapse
do you mean in step 1, Magisk Manager v7.4.0
Did anyone figure out how to fix this issue? I have tmobile and after updating to 9.5.5 and installing magisk it works until I reboot again and then it hangs and goes to fastboot. I try to narrow down the problem and it happens after I install adaway maybe after I choose system less. Or after installing YouTubevanced. Idk what I'm doing
Did anyone find a fix to this ? I'm having the exact same issue.
Flashing magisk 20.4 gives a bootloop. Uninstalling via TWRP allows me to boot to system. No overlays no modules etc,everything uninstalled but still cant boot with magisk. Have I missed something? The only solution I can find is factory reset and begin again, which I can do but as a last resort.
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