I didn't get the automatic OTA for December, February, or March,and so far no April. Just January came automatically. My Pixel 3XL was bought from Google, but runs on T-mobil. It is rooted via Magisk. Polling just says I'm up to date with the Jan 1 patch.
Are others getting the auto OTA's, and if so whats different?
I know I can sideload but there is a super easy way to keep root with Magisk and the auto OTA. I got the OTA's before December. I know Google had trouble in December, and January was a makeup.
I'm rooted on March's update. I can check for an OTA for you if that will help. I was not sure how to proceed without losing my root privledges!
---------- Post added at 05:39 PM ---------- Previous post was at 05:26 PM ----------
I just checked, it went to preparing and than it stopped. Hope that helps!
kmandel said:
I didn't get the automatic OTA for December, February, or March,and so far no April. Just January came automatically. My Pixel 3XL was bought from Google, but runs on T-mobil. It is rooted via Magisk. Polling just says I'm up to date with the Jan 1 patch.
Are others getting the auto OTA's, and if so whats different?
I know I can sideload but there is a super easy way to keep root with Magisk and the auto OTA. I got the OTA's before December. I know Google had trouble in December, and January was a makeup.
Click to expand...
Click to collapse
There is no super easy way to keep root with Magisk and the auto OTA.
Read #9. B. in this Guide.
Note: If you're using the XDA app: Tap the three dot menu => tap load in Browser => tap three dot menu tap open in Browser.
Homeboy76 said:
There is no super easy way to keep root with Magisk and the auto OTA.
Read #9. B. in this Guide.
Click to expand...
Click to collapse
#9B is exactly what I had been using and what I call the super easy way. The trouble is that I haven't got an auto downloaded OTA to use it with since January.
I'm not sure what you are telling me. Is there some way to use it with an OTA manually downloaded from the factory images?
kmandel said:
#9B is exactly what I had been using and what I call the super easy way. The trouble is that I haven't got an auto downloaded OTA to use it with since January.
I'm not sure what you are telling me. Is there some way to use it with an OTA manually downloaded from the factory images?
Click to expand...
Click to collapse
Edit: Suggestion: Re-Read #9.B.
Homeboy76 said:
If you have been using #9.B. to install the OTA image and keep root. You should know OTA updates must be turned off to do #9.B., and factory images are not the same as OTA images.
Suggestion: Re-Read #9.B. (all of it) again.
Click to expand...
Click to collapse
The toggle in Developer Options "Automatic System Updates, Apply updates when device restarts", refers to running the update automatically, not keeping Google from downloading the OTA either automatically or with a poll. I've always had the toggle as off.
As 9B says the toggle is "so it won’t install OTAs without your acknowledgement"
In the Months before December, and in January the OTA was auto downloaded and I had the option of installing it then, or later. I would just follow 9B at that point. This involves invoking "Settings → System → System Update" on the already downloaded OTA, but not letting it reboot until magisk does its magic.
On your other point, the factory image site has both the full system images and the OTAs. However, its not clear to me how I would trigger the manually downloaded OTA in the same way that "Settings → System → System Update" does with the auto/polled OTA downloaded by Google.
There is another thread on this were many if us are having the same issue while rooted. It seems Google is checking for root before it downloads now. And if you fail that check it isn't offered again. What I did this month was the Monday afternoon that it was released I unrooted, did not reboot and then manually checked for the update. It pulled 8t and applied....then I rerooted in Magisk to the other slot.
kmandel said:
I didn't get the automatic OTA for December, February, or March,and so far no April. Just January came automatically. My Pixel 3XL was bought from Google, but runs on T-mobil. It is rooted via Magisk. Polling just says I'm up to date with the Jan 1 patch.
Are others getting the auto OTA's, and if so whats different?
I know I can sideload but there is a super easy way to keep root with Magisk and the auto OTA. I got the OTA's before December. I know Google had trouble in December, and January was a makeup.
Click to expand...
Click to collapse
Not trying to be a wise guy, but if you know how to sideload and root, why not just do it? Is it worth waiting weeks just to save yourself ten minutes?
kmandel said:
The toggle in Developer Options "Automatic System Updates, Apply updates when device restarts", refers to running the update automatically, not keeping Google from downloading the OTA either automatically or with a poll. I've always had the toggle as off.
As 9B says the toggle is "so it won’t install OTAs without your acknowledgement"
In the Months before December, and in January the OTA was auto downloaded and I had the option of installing it then, or later. I would just follow 9B at that point. This involves invoking "Settings → System → System Update" on the already downloaded OTA, but not letting it reboot until magisk does its magic.
On your other point, the factory image site has both the full system images and the OTAs. However, its not clear to me how I would trigger the manually downloaded OTA in the same way that "Settings → System → System Update" does with the auto/polled OTA downloaded by Google.
Click to expand...
Click to collapse
My intention is to help not get into an argument concerning the specifics of #9.B.
If my response gave that impression, please accept my apology.
I edited my original post because of the A/B Devices portion of the instructions (#9.B.). The Pixel 3 XL is an A/B device.
In your original post, I belive you wanted to update the Pixel 3 XL firmware via OTA and keep root. I pointed you to a thread that provides a link to instructions to accomplish that (Update the Pixel 3 XL firmware via OTA and keep root) that was written by the developer of Magisk (topjohnwu).
You could do #4 'keep data' to install the factory image. Then do #9.A. to reroot. I only takes a few minutes.
TonikJDK said:
There is another thread on this were many if us are having the same issue while rooted. It seems Google is checking for root before it downloads now. And if you fail that check it isn't offered again. What I did this month was the Monday afternoon that it was released I unrooted, did not reboot and then manually checked for the update. It pulled 8t and applied....then I rerooted in Magisk to the other slot.
Click to expand...
Click to collapse
Thanks, thats what I was guessing, that it wouldn't download if it knew I was rooted. I wonder if there is a way to hide root from their check, unrooting is a bit speculative since there isn't a trivial way back if they don't download.
spotmark said:
Not trying to be a wise guy, but if you know how to sideload and root, why not just do it? Is it worth waiting weeks just to save yourself ten minutes?
Click to expand...
Click to collapse
Because its error prone. As far as I know there is no Android 10 Twrp for Pixel 3, and no reroot option other than 9B. The other route patching the boot img just seems messy .
kmandel said:
Thanks, thats what I was guessing, that it wouldn't download if it knew I was rooted. I wonder if there is a way to hide root from their check, unrooting is a bit speculative since there isn't a trivial way back if they don't download.
Click to expand...
Click to collapse
One point I may not have been clear on. Once you fail this new check for a month you are done until next month. It won't try again.
If you don't pull the update you can reroot right away with Magisk with the Direct Install method since you have not rebooted. Not ideal but not the end of the world.
kmandel said:
Because its error prone. As far as I know there is no Android 10 Twrp for Pixel 3, and no reroot option other than 9B. The other route patching the boot img just seems messy .
Click to expand...
Click to collapse
If you know how to ADB and fastboot, you don't need TWRP. The most usual reason for error is user error. Even then it's rare to brick a phone. Worst outcome is you lose your data and have to set your phone back up.
Related
So I have a Verizon Pixel XL that has been unlocked, TWRP alpha installed, and rooted....
How shall I update my build? Should I even update the build?
My goal is to have the latest update running on my system (manually flashing or OTA I don't care) with an unlocked rooted Pixel XL that can broadcast wifi natively.
I have everthing down except the update piece. Any advice?
You have TWRP and root? How is that working? I was reading that SuperSu needs an update to work with it. Also many people who have taken the OTA (or even flash full system image) are getting stuck in the bouncing balls boot loop. I would hold off on updating. No real major changes as of yet.
Twrp is working fine but I have nothing to flash to test...????
networx2002 said:
Twrp is working fine but I have nothing to flash to test...????
Click to expand...
Click to collapse
Yeah that is what I'm hinting at.... There is no updated ROM to work with TWRP yet that is updated to the latest Google Build
Root is working. I have twrp alpha 2. Root and elementalx 8 all installed. Although, im getting my daydream headset tomm. And when you install the app it tells you to check for updates. It says I have one. But if you look at the OTA updates NDE63 is the newest. Which im on. So I dn at this point. I guess i'll just roll with it for now. The dev that made purenexus that I ran on my nexus 6. Says hes working on it already and gets his on the 21st. So i'll just stick with what I have for now. I'm sure we'll see roms pretty soon
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
s1dest3pnate said:
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
Click to expand...
Click to collapse
jreink01 said:
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
Click to expand...
Click to collapse
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
DeathSentinels said:
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
Click to expand...
Click to collapse
If you edit the flash-all.bat file and take out the -w near the end you wont flash user data. So you can skip restoring your cloud backup and apps. Backup just to be safe though.
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
jreink01 said:
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
Click to expand...
Click to collapse
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
TonikJDK said:
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
Click to expand...
Click to collapse
OK, thanks, that's good to know. When I lose root, will that mess with any of my apps that need root to work like titanium backup? Or will I just need to grant it user privileges again? I have never done this particular process before so I am a little weiry. Do you know of a step by step guide to do this? Sorry but I would feel more comfortable that way. Thanks for all you help and feedback, it's been years since I last went through the rooting, flashing process so, I guess I am being extra cautious. I have/am learning by the feedback you have given me.
Sent from my Pixel XL using Tapatalk
I am rooted with TWRP RC1
i never sideloaded an OTA before, alway applied factory images. Too lazy, but tired of all the rework.
i folllowed,
https://9to5google.com/2016/12/05/how-to-sideload-android-7-1-1-nmf26o-onto-the-pixel/
no data loss.
just had to use fastboot to reinstall TWRP and reflash SUPERSU.
All is well.
If I choose to side load it, do I root and install TWRP the same way I did when I first did this, with ADB on my windows PC? And side loading will work with a new operating system (when it comes out) along with the monthly security updates? I just checked and my latest security update is from January. If I updated March's update, would that automatically have the February one with it?
---------- Post added at 02:10 AM ---------- Previous post was at 02:02 AM ----------
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
jreink01 said:
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
Click to expand...
Click to collapse
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
TonikJDK said:
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
Click to expand...
Click to collapse
Yes, I am in the beta program, that's why I am on this version. So, I'm assuming the beta's don't get updates then? I have turned off automatic updates since I'm rooted. Would you recommend I turn that back on or no? If I'm correct, I can't take a OTA since I'm rooted so I was correct in turning off automatic updates then? I will probably stay on this version since the difference is improvement and bug fixes. So, when 7.1.2 rolls out to everyone, then I would assume that that version would show up on the Google page then?
Sent from my Pixel XL using Tapatalk
I have a Verizon Pixel XL with unlocked bootloader, TWRP, and root on NHG47K. I have been updating it via sideloading the OTAs since I got the phone. I've seen on the forums that a lot of people flash the full factory image. I wanted to know what the difference was between sideloading the OTA vs flashing the full factory image?
There is not too much difference,
OTA is changing only what has been changed, size varies with 100 MB to 600 MB of more. But if you had some problems with unchanged partitions they may not fixed.
Factory image flashing has bigger size (latest is 1.8 GB), wiping your data by default (manually editing for non wipe is possible), mainly for fresh start even without wiping data.
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
savi0 said:
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
Click to expand...
Click to collapse
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
5.1 said:
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
Click to expand...
Click to collapse
To clarify your meaning... The May Verizon OTA does or does not break root?
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again. Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
savi0 said:
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again.
Click to expand...
Click to collapse
Hello,
If you try to reinstall Root or TWRP after May OTA I think you are going to have a bad surprise. It's up to you...
savi0 said:
Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
5.1 said:
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
Click to expand...
Click to collapse
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Hey,
As a workaround, you can flash April bootloader. It's not a big deal and works fine anyway.
Cheers...
5.1 said:
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
Click to expand...
Click to collapse
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
sliding_billy said:
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Yeah. A few posts above yours @savi0 pointed to a Chainfire posts relating the issue. You can also check the last posts from EX Kernel. flar2 posted a link to the latest security bulletin...
Normally, we won't have to wait too long to get back TWRP/Root.
Cheers...
sliding_billy said:
I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
Hello,
I don't understand what you mean when you say:
alluringreality said:
That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update
Click to expand...
Click to collapse
If you have issues, just sideload the latest OTA from Google here:
https://developers.google.com/android/ota
Instructions are available on this page.
Good luck...
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
I have been concerned about the system using data while waiting to update the phone, but I do not see that happening. I have automatic update turned off in dev settings as well as the google play services notification disables so as not to accidental click it. I see the update available if I look at the check for updates area in system, but it just is sitting at the download and install option there. I have checked my data use since the BL issue came about, and there is no data use besides normal.
Mainly I was just noting that not taking an update can potentially result in cellular data usage, in case anyone wasn't aware of the possible issue. The top items in my cellular data usage were the same as the images in the following thread when I avoided taking an OTA update.
https://forum.xda-developers.com/pixel-xl/help/android-os-sucking-mobile-data-t3597680/
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
PrettyPistol555 said:
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
Click to expand...
Click to collapse
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
shagbag913 said:
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
Click to expand...
Click to collapse
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
PrettyPistol555 said:
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
Click to expand...
Click to collapse
Yep.
My pixel 2xl is rooted , I rooted my device after getting november security patch
Now Whenever i check for OTA it says your system is uptodate
I thought it's because of the root so i unrooted it by opening magisk app
And choose (1- restore image 2- complete unroot)
My device restarts and i check for ota again but still its not showing any ota
shivangshukla said:
My pixel 2xl is rooted , I rooted my device after getting november security patch
Now Whenever i check for OTA it says your system is uptodate
I thought it's because of the root so i unrooted it by opening magisk app
And choose (1- restore image 2- complete unroot)
My device restarts and i check for ota again but still its not showing any ota
Click to expand...
Click to collapse
Probably some leftovers hanging in there. You should try rolling an update with a factory image but take out the -w from the script first so you don't lose your data. That may not be enough though. Personally if your committed to taking ota updates I would do a completely fresh install and wipe the phone.
All that being said, I'm confused as to why you are routine about ota at all. Doing monthly updates with the factory updates is super easy and very fast.
I'm at work and don't have the time to get you all the details but if @Badger50 is around I'm sure he can copy paste the instructions from one of his many posts.
I've been using the lazy method of rooting my 3XL from an arriving OTA.
https://topjohnwu.github.io/Magisk/tutorials.html
It works great, the problem is the OTA arriving. As was well publicized the December one never arrived, but the January one did. However, I never got the February so I'm still on January. I don't know if that was widespread. Finally, its now March 8 and I haven't gotten the March OTA., which is available on the factory image site. If I didn't get February automatically (and I do poll) I have to wonder if I will get March.
Is there a way to get the phone to treat a manually downloaded OTA the same way as one that was auto distributed? I know about the other ways to update and patch, but I like the OTA method.
kmandel said:
I've been using the lazy method of rooting my 3XL from an arriving OTA.
https://topjohnwu.github.io/Magisk/tutorials.html
It works great, the problem is the OTA arriving. As was well publicized the December one never arrived, but the January one did. However, I never got the February so I'm still on January. I don't know if that was widespread. Finally, its now March 8 and I haven't gotten the March OTA., which is available on the factory image site. If I didn't get February automatically (and I do poll) I have to wonder if I will get March.
Is there a way to get the phone to treat a manually downloaded OTA the same way as one that was auto distributed? I know about the other ways to update and patch, but I like the OTA method.
Click to expand...
Click to collapse
Your phone won't apply the OTA with a modified boot image (magisk modifies it).
If you want to get updates you'll need to manually flash the full system image with the -w removed from the bat file. Head over to the guides portion of the forum for instructions.
ffchampmt said:
Your phone won't apply the OTA with a modified boot image (magisk modifies it).
If you want to get updates you'll need to manually flash the full system image with the -w removed from the bat file. Head over to the guides portion of the forum for instructions.
Click to expand...
Click to collapse
If you look at the url at the top of the thread you will see that first you do is "Magisk Manager → Uninstall → Restore Images" before triggering the OTA install.
It does work fine, I've done it twice. The problem is that Google didn't download the OTA in December or February, and so far in March (though its early).
kmandel said:
If you look at the url at the top of the thread you will see that first you do is "Magisk Manager → Uninstall → Restore Images" before triggering the OTA install.
It does work fine, I've done it twice. The problem is that Google didn't download the OTA in December or February, and so far in March (though its early).
Click to expand...
Click to collapse
I did the Jan OTA update with Magisk and it worked great. I got tired of waiting for the Feb and Mar OTA's so I flashed the full Mar image yesterday. There's another thread with others having the same issue of not getting the OTA https://forum.xda-developers.com/pixel-3-xl/help/preparing-update-t4060613
This is happening to a lot of us. If you time it right you will see it say Preparing to update.....if you manually check before it has tried.
The preparing goes away and then it is stuck on you are up to date. Google found a way to pre check for root I think.
So I can't use adb update in recovery for the May 2023 ota update. I think I know the culprit to my issue. When I saw that the May update was out, I just did the usual check to see if the update was pushed to the phone. When I checked for an update, an update started and I thought it was the May update. But after a restart, I saw that it was the still the April update. I figured out that my google version P6P that I used on Verizon, was updated with the Verizon April OTA update, which is dumb because I already had the global April Update installed (I've always had the global builds on my P6P, instead of the VZW ones). Now when I try to adb upgrade in recovery the May 2023 global ota, I get an error:
"Update package is older than the current bulid, expected a build newer than timestamp 1681504608 but package has timestamp 1679671817 and downgrade not allowed"
So is there a way to be able to hop back on the global ota's without having to reset everything and use a factory image?
Phone is completely stock, non-rooted, and I haven't unlocked the bootloader (but OEM unlocking is activated in dev options).
Unlock the bootloader, if you can, and flash a factory image. You can preserve your data doing this, simply by editing the flash-all batch file: info on how to do this is readily available. After, you can lock the bootloader if you wish.
Strephon Alkhalikoi said:
Unlock the bootloader, if you can, and flash a factory image. You can preserve your data doing this, simply by editing the flash-all batch file: info on how to do this is readily available. After, you can lock the bootloader if you wish.
Click to expand...
Click to collapse
unlocking the Bootloader will wipe the data anyway..
fernoct said:
unlocking the Bootloader will wipe the data anyway..
Click to expand...
Click to collapse
You are of course correct. So he takes a backup of his internal storage at the very least. There are ways to take a full backup and restore it but it's somewhat tedious to do.
Gonna wait till the June OTA (when the timestamp will presumably be later) and update manually going forward.
I'm in the same boat, and have too many work apps to reconfigure for a reimage. Waiting it out seems like the best option.
somethingsomethingroot said:
Gonna wait till the June OTA (when the timestamp will presumably be later) and update manually going forward.
I'm in the same boat, and have too many work apps to reconfigure for a reimage. Waiting it out seems like the best option.
Click to expand...
Click to collapse
Yup, that's probably what i will do. Fight the temptation to flash the vzw ota for may (shouldn't be too hard since May update was for security and bug fixes). If the June global OTA, which will also will be a feature drop, doesn't flash...then I'll resort to unlocking the bootloader and flashing factory image. Thanks to everyone else for chiming in.
For anyone reading this later, remember to turn off automatic system updates in dev options. I forgot to do this and my phone just took the VZW May update by itself. So most likely, I won't be able to adb install the June update, and will have to wait until July.