Any help, I flashed magisk after latest update and I noticed it didnt reboot itself like it said it would. I clicked reboot myself and now I cant get back into my phone, just keeps saying powering off and takes me bootloader screen where I have enter my pin and it starts decrypting, then options to either reboot to recovery or fastboot. What can I do now?
Happened to me. My bet is you didn't delete all the magisk modules before running the update
mike710_0 said:
Happened to me. My bet is you didn't delete all the magisk modules before running the update
Click to expand...
Click to collapse
Never had to delete them before? What can I do now?
SysAdmNj said:
Never had to delete them before? What can I do now?
Click to expand...
Click to collapse
To be honest I don't know. All I do know is the problem gradually got worse. I ended up having to use that recovery software (can't remember the name of it)
Hopefully someone can shed some more light on what to do though
SysAdmNj said:
Never had to delete them before? What can I do now?
Click to expand...
Click to collapse
Boot into twrp of you have bootloader unlocked (fastboot boot whatever.img) and Flash magisk manager for recovery mode. You can use it to disable or remove modules in recovery
manor7777 said:
Boot into twrp of you have bootloader unlocked (fastboot boot whatever.img) and Flash magisk manager for recovery mode. You can use it to disable or remove modules in recovery
Click to expand...
Click to collapse
That will fix my issue? Never had to disable magisk modules before while doing an update, something changed?
UPDATE: Still need help but I was able to fastboot into twrp. I was able to reboot into Slot A and I was back in my phone ok. I was able to reboot and come back ok. I tried the update again, after it downloaded and installed. I opened magisk manager, went to install magisk, selected Install to Inactive Slot(After OTA) - I've been doing these steps all along - bu this time it failed again and put me in a bootloop. Luckily I know how to get back into Slot A but is something wrong with my other slot that the update isnt installing ok?
Only other weird thing I noticed was that after magisk finishes installing, it said it would force reboot my device but it doesn't. I have to manually push the reboot button and thats when I reboot into a boot loop. Any ideas?
Another thought, could it be that I bought this phone off oneplus but this is a verizon update 9.5.13 GM21AA? Although I do use a verizon sims card as a secondary line. Could this be causing the confusion? Maybe I"m just confused with this Slot A & B stuff :laugh:
SysAdmNj said:
Still need help but I was able to fastboot into twrp. I was able to reboot into Slot A and I was back in my phone ok. I was able to reboot and come back ok. I tried the update again, after it downloaded and installed. I opened magisk manager, went to install magisk, selected Install to Inactive Slot(After OTA) - I've been doing these steps all along - bu this time it failed again and put me in a bootloop. Luckily I know how to get back into Slot A but is something wrong with my other slot that the update isnt installing ok?
Click to expand...
Click to collapse
You need to flash Magisk to both slots. Also need to flash TWRP installer again (if you have been wondering why you can't get into TWRP, that is why).
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
SysAdmNj said:
That will fix my issue? Never had to disable magisk modules before while doing an update, something changed?
Click to expand...
Click to collapse
This isn't new, it's been known for some time. But only a few modules are actually known to cause problem (Call Recording module is one).
I've used the following process successfully every time I've updated, since getting the 7 Pro shortly after it was released.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
The steps have mostly stayed the some. Not sure exactly when the part about removing Magisk modules was added, but it's been a while.
redpoint73 said:
You need to flash Magisk to both slots. Also need to flash TWRP installer again (if you have been wondering why you can't get into TWRP, that is why).
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
This isn't new, it's been known for some time. But only a few modules are actually known to cause problem (Call Recording module is one).
I've used the following process successfully every time I've updated, since getting the 7 Pro shortly after it was released.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
The steps have mostly stayed the some. Not sure exactly when the part about removing Magisk modules was added, but it's been a while.
Click to expand...
Click to collapse
I dont usually flash twrp, I usually just fastboot into twrp. Its how I got out of bootloop this time, then in twrp I selected reboot into slot A.
So those steps are definitely a bit different than how I've been updating recently. I will try those steps. Before I would just download and install update, go into magisk manager and install into inactive slot and it would reboot automatically and that was it.
Related
Okay. I'm late getting into the pixel 3 game because I got my pixel 2 late last year. But i've just purchased it recently and it's great. But iv'e been unable to root it & I've never had any trouble rooting any Google devices in the past, stretching back to the nexus 3. I've always been under the impression that Google encourages rooting, or at least, makes no attempt to stop it. So I'm surprised that I even feel the need to make this post. I can find plenty of people talking about rooting even up to February's security patch, but nothing for Google's current most recent security patch (March 2019). Nothing I do seems to make any difference, I've followed steps on several tutorial threads to the letter and still end up in a boot loop. I'm tempted to downgrade so I can root, but I'd like to avoid that if possible. Am I the only one having this issue? I'm not able to find a wealth of people complaining about it, which strikes me as weird. Has Google done something with this update to actively block Magisk, or what? I'm at a loss. Like I say, never have I ever encountered such a road block in rooting any device.
Anyways, hopefully someone can ease my frustrations by at least sharing in them. Thanks for any replies.
This assumes you have already unlocked the bootloader...
1. Fastboot boot TWRP.
2. If you don't want permanent TWRP, skip to step 5. Otherwise, go to step 3.
3. Flash TWRP zip.
4. Reboot to recovery.
5. Flash magisk zip.
6. Reboot to system
That's it. It's the same on every security patch.
This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.
You need to boot into system before flashing magisk.
watlingj said:
This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.
Click to expand...
Click to collapse
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:
wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've never had issues without booting back to system before flashing magisk.
Badger50 said:
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:
Click to expand...
Click to collapse
Thanks for the suggestion but alas, still boot looping.
wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've tried this, it didn't make a difference.
OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.
wangdaning said:
OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.
Click to expand...
Click to collapse
Sorry for the late reply, i actually ended up returning it to stock and swapping it for a different one, because my speaker was making a weird sound when i was calling and it was having bluetooth issues, this one rooted perfectly fine first try.'
Except, Magisk randomly can't detect it's self through it's own manager app, but all my installed modules are working.. but i can't... manage them..
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Not sure what you're doing wrong but what I can do is tell you my steps:
- Upgrade via stock OnePlus Updater inside system settings
- Make sure it downloads the full OTA (over 1GB file size) if you are rooted
- Let it update
- Flash the TWRP retention script found in the Magisk repo if you have TWRP and would like to keep it
- Install Magisk to inactive slot from the main screen in Magisk Manager
-Reboot and profit
Couple things to keep note of
- Uninstall all Substratum overlays before doing this
- Optional: remove lockscreen security
Personally I don't remove lockscreen security but I do uninstall Substratum overlays and I never have issues.
Anyone know how to root if I'm already on 9.5.6?
hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
You can flash the Magisk installer zip in TWRP, which is what I did.
Or you can wait until someone posts a patched 9.5.6 boot image.
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
(Adb and fastboot on a PC)
(Unlock bootloader): tap build# 6x, Oem unlocking and usb debugging on, connect phone to PC, boot to recovery, "fastboot oem unlock" from PC command prompt which erases phone also, then usb debugging and advanced reboot on again
Download the patched boot image to adb directory
Install the latest version of Magisk Manager to phone
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
larsdennert said:
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
Download the patched boot image to adb directory
Install the latest version of Magisk Manager
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
shadeau said:
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
Click to expand...
Click to collapse
OK question does both these methods get us to the same results? Just they are different ways of doing it. Don't beat me up to bad guys.
The key is flashing a boot image that matches what you are currently running.
The second set of instructions also flash TWRP.
Both flash magisk which is essentially root.
I preferred the first method as it was simple and initially only boots to a modified image. If anything goes wrong in that step, nothing permanent has been done. The first method requires you are at least on 9.5.4 as earlier recoveries did not support booting to an image unless it was flashed.
Sent from my GM1917 using Tapatalk
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Sent from my GM1917 using Tapatalk
larsdennert said:
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Click to expand...
Click to collapse
I flashed the correct boot image, but to the wrong slot which led me to a bootloop. After fixing that problem and getting back to stock I switched slots, flashed the boot image, and didn't have WiFi (I triple checked the version was correct and others have had the issue). That's what led me to flashing the full ROM in TWRP and then Magisk.
To the OP:
I like having TWRP with a rooted device, but if you just want root then follow the first set of instructions
OK guys I'm on Verizon I just got my phone Friday and it had the update 9.5.6GM21AA for the Iphone and 7pro problem so I did it. OK now the dumb question when it says Open Magisk & Install it again. There are talking about the boot image right? I'm sorry guys I've not done this in a long time.
OK guys I googled and found what I needed thank you
With the phone only a few weeks old, we are all experimenting with what works. 1+is also releasing a lot of patches all the time so things are a moving Target. Luckily things are settling and the early adopters have sorted out how to get out of a jamb when it happens.
For others clarity open the magisk app after booting to the patched boot image i provided and do a direct install. This is that step that actually permanently patches your boot image for magisk. There are other instructions floating around that instead flash the modified image provided. Those were earlier instructions They are more hazardous in case there is a problem with the supplied image or it doesn't match your rom, or you don't flash to the correct Slot. That's what happened to the other poster but he was experienced enough to simply fix the issue. It's still a sinking feeling when it happens and you wonder how badly you've just bricked your phone. I've been there many times, lol.
Sent from my GM1917 using Tapatalk
skythian said:
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Click to expand...
Click to collapse
I am in the exact same boat. I went through a bunch of trouble getting my phone rooted for the first time on 9.5.3. Finally got everything setup properly. 9.5.3 with root and twrp 3.3.1-20 (with decryption working).
Wanted to upgrade to 9.5.6 and have been holding off for fear of messing things up and having to wipe and start over.
Decided to go for it. Used the OP system updater. Installed 9.5.6. DID NOT REBOOT. Went to Magisk Manager and installed Magisk using the "After OTA" method. Rebooted. It booted to stock OP recovery.
Frustrated and not quite sure what to do, I went to my computer and installed twrp 3.3.1-20 using "fastboot flash boot twrp.img". I expected it was going to boot into twrp since I installed it on the current slot (A) but to my surprise it booted into system. Unfortunately I lost root, but at least i'm not at the stock recovery.
Then I decided I would try to get root using the patched image that @larsdennert posted on post 5. I went into fastboot and followed his instructions exactly. Waited for it to reboot and ended up at the stock OP recovery screen again. Since the only thing I knew how to get back into my system was flashing the twrp 3.3.1-20, I did that, rebooted, and am now back in Android, but without root.
After reading countless threads about the Slot A and B partitioning, I thought I understood it, but I must not. Or something must be setup wrong. I follow steps exactly and nothing seems to work for me.
Maybe someone can help me out. I'd like to get 9.5.6 rooted, but I am terrified to mess stuff up and have to wipe it clean again.
EDIT:
I got root! Once I got to system I had the idea to boot to recovery to see if twrp was there. Turns out it was, so I flashed Magisk from twrp and rebooted. Saw that it was rooted and direct installed Magisk again from Magisk Manager.
Man, I really have no clue how or why this worked out this way. I feel like i'm going to stay on 9.5.6 for a while out of fear of screwing something up again. This is nothing like my old One Plus 5. lol
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Blackfireball5 said:
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Click to expand...
Click to collapse
flash the Sky-Dragon Kernel, it'll fix the wifi
Marco589 said:
flash the Sky-Dragon Kernel, it'll fix the wifi
Click to expand...
Click to collapse
I'm not really interested in going to a different kernel. I'm going to try to dirty flash the update again and reflash twrp and Magisk. Hopefully that will work.
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.
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.