Need some answers/help...
I was stock, rooted on 8.0....saw a pop-up box yesterday about OTA, didn't think much about since I thought being rooted wouldn't allow the OTA. Have seen the occasional pop-up over maybe the last couple weeks, but I don't normally restart my phone unless it starts to lag or freeze up/run slow. A restart usually fixed that. Was perfectly happy staying on 8.0. I did a shutdown on my phone this evening, and when I restarted it, bam, I'm unrooted on 10 now, specifically, QP1A.190711.020
The phone was bought from Google, unlocked in Oct 2017. I immediately unlocked bootloader and rooted at that time and have been running stock 8.0 since. TWRP and Magisk were used following instructions from the thread here on the forum.
No data was lost after the restart today and 10 seems to be running ok. I did download some data and pictures through my USB-c onto a flashdrive and it did seem to drain my battery FAST while doing it.
What I'd like to know now is how to get root back. I wouldn't mind staying on 10, but if I re-root, will another OTA break my root again? I haven't tried to do a shutdown and a restart again to see what would happen because I'm afraid my phone will brick.
I'm kind of a noob at this, and I don't always understand when you all get technical, but I can follow step-by-step instructions.
First off, how did an OTA actually get through, update and unroot my phone?
And second, can someone point me to step-by-step instructions to re-root my phone on 10, and how do I keep it from happening again?
Thanks for looking and I'd be very appreciative if someone could help me out.
Thank you.
Jim
same here
Same here.
I've got a retail (NON-Verizon) rooted, stock OG Pixel with 8.1 and I've been ignoring the nag to update to 10.
My wife has a retail (NON-Verizon) Pixel 2 that was also stock, rooted 8.1 except she just took the update and asked me about it later.
Both were done with TWRP and Magisk, albeit differing versions.
She's now unrooted at QP1A.191005.007.A1
TWRP v3.2.1-0-walleye is installed.
EDIT: TWRP seems to have been nuked by the OTA upgrade.
I just tried to reboot into TWRP recovery and it's gone.
Magisk Manager app version 5.4.0 (57) + "Latest Magisk Version: v16.0" (I'm pretty sure I rooted via v14.5(1456) though) are present.
"Update Magisk Manager" is nagging about updating /installing MagiskManager-v5.8.2
Root Checker Basic v6.4.6 is also installed.
I'm scared to death to update Magisk or attempt root without some guidance from you fine folks here.
Until then, I'll start having her backup everything she wants to keep in case things go sideways.
I didn't think I was the only one this happened to.
Ok...noticed another issue.
I had Titanium Backup Pro installed. I had several apps frozen before the forced upgrade to 10. Guess what? Those apps are listed as disabled in the app list with no button for re-enabling them. Titanium Backup Pro no longer works because I lost root with the forced update to 10, so I can't unfreeze with Titanium Backup.
Is there any way to unfreeze those apps without re-rooting? Not too sure I even want to attempt to root again.
Also, I haven't shutdown or restarted since the forced update. S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
fjm568 said:
S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
Click to expand...
Click to collapse
Correct.
As for "other issues", none that I, or she, have noticed.
Still breathlessly waiting to hear about how I go about re-rooting without data loss.
Preamble / RamblingHello dear xda-community,
I am a little desperate right now. After hours of searching for solutions I am sadly out of luck and afraid I might destroy the system if I try to solve this issue any further by my own. :/
By no means I am an expert in flashing / rooting mobile devices, so please forgive me if I did something stupid.
But with that out of the way I hope you can help me. Thank you already for your efforts.
Have a great day,
TheAverageUser
The ProblemWhen trying to connect to a WiFi the connection disrupts and apparently the entire network management component (?) crashes and restarts.
I suspect it of crashing because the connection to the internet via my SIM card is disconnected as well for a short period of time after the WiFi tries to connect to a base station.
How I got here
Upgraded from LOS 17.1 to 18.1 like so
Installed TWRP as described here
Installed Magisk as described in the "Custom Recovery" section of this guide
Additional Information
After upgrading to LOS 18.1 I noticed that Magisk did not work anymore, so I tried to find a way to re-root my device.
A long search later I decided that I needed TWRP in order to root the device as many guides I found required this to be the case. Sadly I can't remember how I rooted the device the first time.
The mentioned method for installing Magisk seemed to be the only one working for me. (I did not find anything better.)
I would love to fix my current OS without having to start over, because setting it up again is very tedious.
Previous Setup (Before Upgrade)
OnePlus 6 (obviously ^^)
Lineage OS 17.1
Magisk
Lineage Recovery
Updates:
#1 Okay. Now I am even more confused. The phone just connected to my WiFi and it seems to work. I didn't do anything as of yet. I am going to investigate further to find out when exactly the connections fail. Honestly I don't like a 50:50 chance of it working ^^ (Just to be clear. My problem is not fixed as of yet.)
#2 For some reason the WiFi is now working. The only thing that I can think of which might have solve the issue is that I have uninstalled and reinstalled the "F-Droid Privilgeded Extension" for Magisk.
TheAverageUser said:
Preamble / RamblingHello dear xda-community,
I am a little desperate right now. After hours of searching for solutions I am sadly out of luck and afraid I might destroy the system if I try to solve this issue any further by my own. :/
By no means I am an expert in flashing / rooting mobile devices, so please forgive me if I did something stupid.
But with that out of the way I hope you can help me. Thank you already for your efforts.
Have a great day,
TheAverageUser
The ProblemWhen trying to connect to a WiFi the connection disrupts and apparently the entire network management component (?) crashes and restarts.
I suspect it of crashing because the connection to the internet via my SIM card is disconnected as well for a short period of time after the WiFi tries to connect to a base station.
How I got here
Upgraded from LOS 17.1 to 18.1 like so
Installed TWRP as described here
Installed Magisk as described in the "Custom Recovery" section of this guide
Additional Information
After upgrading to LOS 18.1 I noticed that Magisk did not work anymore, so I tried to find a way to re-root my device.
A long search later I decided that I needed TWRP in order to root the device as many guides I found required this to be the case. Sadly I can't remember how I rooted the device the first time.
The mentioned method for installing Magisk seemed to be the only one working for me. (I did not find anything better.)
I would love to fix my current OS without having to start over, because setting it up again is very tedious.
Previous Setup (Before Upgrade)
OnePlus 6 (obviously ^^)
Lineage OS 17.1
Magisk
Lineage Recovery
Updates:
#1 Okay. Now I am even more confused. The phone just connected to my WiFi and it seems to work. I didn't do anything as of yet. I am going to investigate further to find out when exactly the connections fail. Honestly I don't like a 50:50 chance of it working ^^ (Just to be clear. My problem is not fixed as of yet.)
Click to expand...
Click to collapse
Is it not because of your base OOS version?
Just do this and you are 100% okay.
1. Use MSM Tool here (it is like a full factory reset with a clean install - you have to unlock your bootloader again!!!)
2. Download latest OOS Full Update here, latest TWRP here, NikGapps here (Magisk if you like) and copy them into Device
3. Flash OOS, TWRP & Reboot to Recovery
4. Flash OOS, TWRP & Reboot to Recovery
5. Flash LOS-ROM, TWRP & Reboot to Recovery
6. Flash NikGapps (and Magisk) & get back to Menu
7. Select Wipe and just swipe to wipe data
8. Reboot to system
9. Done
Hello @tiga016 and @Pundy,
so here is an update on my situation:
For some reason the WiFi is now working. The only thing that I can think of which might have solve the issue is that I have uninstalled and reinstalled the "F-Droid Privilgeded Extension" for Magisk.
@Pundy
Thank you very much for this guide. For now I will continue to use my device in its current state, but as soon as I try to do a major update I will come back to your guide in order to install everything in a clean manner.
@tiga016
Thank you for your interest in my issue. For now I will consider this problem to be solved.
Pundy said:
Just do this and you are 100% okay.
1. Use MSM Tool here (it is like a full factory reset with a clean install - you have to unlock your bootloader again!!!)
2. Download latest OOS Full Update here, latest TWRP here, NikGapps here (Magisk if you like) and copy them into Device
3. Flash OOS, TWRP & Reboot to Recovery
4. Flash OOS, TWRP & Reboot to Recovery
5. Flash LOS-ROM, TWRP & Reboot to Recovery
6. Flash NikGapps (and Magisk) & get back to Menu
7. Select Wipe and just swipe to wipe data
8. Reboot to system
9. Done
Click to expand...
Click to collapse
Hello Pundy,
I have updated from LOS 17.1 to 18.1 (clean install) sadly wifi was not working with 17.1 and also not with 18.1. Therefore I have installed OOS (without TWRP) one of the latest version and made an update via wifi to the current version. So wifi is ok. Following the LOS howto, I was successful in installing the latest LOS BUT again wifi is not working...
Sadly also using the MSM Tool is not working. The MSM Tool does not connect with the OP6 (Sahara problem). I have tried it many times...
Any alternative?
BR Martin
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
behel1t said:
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
Click to expand...
Click to collapse
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
azoller1 said:
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
Click to expand...
Click to collapse
Hi, correct I am not using twrp. I tried unlocking the boot loader and not rooting. Receiving an OTA works and I can reboot. But oddly enough if I do a --set-active=otherslot, i get a qualcomm crashdump.
It appears that whenever I or magisk force change the active slot, I get a crash dump.
EDIT - Still unsuccessful. I've tried numerous times using MSM Download and the fastboot unbrick method by coomac. I haven't been able to --set-active=b a single time, it always ends up in a qualcomm crash dump. I suspect slot is B is corrupt.
Try to restore both slots with an older version of rom using local update. Then take ota and try.
kjslabber said:
Try to restore both slots with an older version of rom using local update. Then take ota and try.
Click to expand...
Click to collapse
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
behel1t said:
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
Click to expand...
Click to collapse
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
kjslabber said:
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
Click to expand...
Click to collapse
Thanks for the reply. I do yes. I'll give this method a shot. Cheers
UPDATE - Just finished using msm download to restore OOS 11.0.5.6 and then used local upgrade to flash OnePlus8TOxygen_15.O.20_GLO_0200_2011132216 (both 11.0.5.6). I can now successfully boot both slots!
Now I am going to root. install riru and safetynet fix in magisk.
When I am ready to take an OTA, the correct process would be to uninstall the safetynet fix and riru. Then uninstall magisk using restore images, download and install OTA but do not reboot. Go into magisk and install to other slot. Then providing a successfully boot, reinstall safetynet and riru. Is this correct?
UPDATE 2 - Qualcomm crashdump happened after taking an OTA using the method I outlined above. So I reverted back to the previous slot and am in the process of doing a local upgrade again using 11.0.5.6 to hopefully restore that slot to working.
Something about magisk installing to the other slot and forcing a slot change is causing this crash dump.
I had 11.0.5.6 on both slots. I rooted. I then completely unrooted (not restore images). Took an update. That booted. I booted that. Rooted it. Then for testing, completely unrooted again. Then I received the latest OTA. That installed and booted. So I'm rooting now on the latest getting ready for daily use.
I have no idea why using magisk to install root to the other slot and forcing a slot change is not working. I'm grateful that, with extra steps, i can at least reliably receive OTAs and continue on living rooted life.
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
azoller1 said:
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
Click to expand...
Click to collapse
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
behel1t said:
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
Click to expand...
Click to collapse
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
azoller1 said:
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
Click to expand...
Click to collapse
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
behel1t said:
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
Click to expand...
Click to collapse
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
azoller1 said:
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
Click to expand...
Click to collapse
Thanks for bringing this to my attention. This is definitely what is happening. You just just saved me from spending any more time on this mess. Cheers!
I just wanted to add that I had same problem with my OP8T and couldn't reflash the ROM and had to send my phone to OP to get the ROM put back on. Slot B still doesn't work. You at least were able to get the phone back working with MSN.
Unfortunately, I have a problem. My phone was on the power cord overnight and pulled the latest update (EEA 12.5.5.0 Enhanced). It was then booted into OrangeFox (OrangeFox recovery with OTA support) and waited for my OK. I didn't think anything of it and didn't make a backup either, as I assumed that everything would go smoothly like the last update.
The update then went on, but there was probably an error, because now I have a bootloop (yellow Poco lettering for about 2 seconds). I can't use an old backup because I'm abroad right now and I don't want to lose the apps I've already set up (pandemic, tracking apps, certificates, ...).
Does anyone have a quick trick or the latest full ROM that I can just iron over or any other good quick idea? Change bootloader slot or other options? OrangeRecovery and Fastboot are still accessible. Now I only have ADB/Fastboot on my work laptop, but I still can't list the device with adb devices. I guess I still need to install the Xiaomi driver for it, but that should be the minor issue.
Update: I am currently downloading the different ROM versions (fastboot, recovery and incremental update), just in case they are needed.
OTA for the rom and using ofox? hmm it's not supported unless you will flash stock rom maybe. I don't know much more. Correct me if im wrong.
OTA works very well with orangefox and AICP 16.1...