there are two threads that i've come across: this one here and this one here.
am i missing something!? why can't, after rooting etc, we just disable the ota's under settings on device the normal way? i.e. just unckeck auto download and uncheck 'check for updates'
haven't got the G4 yet, but just researching a bit before i do. maybe those settings aren't there?
can any one shed any light on this, please?
reg66 said:
there are two threads that i've come across: this one here and this one here.
am i missing something!? why can't, after rooting etc, we just disable the ota's under settings on device the normal way? i.e. just unckeck auto download and uncheck 'check for updates'
haven't got the G4 yet, but just researching a bit before i do. maybe those settings aren't there?
can any one shed any light on this, please?
Click to expand...
Click to collapse
AFAIK, LG uses a different approach and could not find the software updates under Settings/About phone. And updating a rooted phone with official OTA can lead to a lot of trouble.
Ota with a rooted device will most likely result in a Security Authentication error and a refusal to boot.
The settings you refer to, are not there.
smknutson said:
Ota with a rooted device will most likely result in a Security Authentication error and a refusal to boot.
The settings you refer to, are not there.
Click to expand...
Click to collapse
thanks, but i read a post from another user (i'll be getting the H815) this: On the H815 under Settings -> General -> About Phone -> Update Center -> Software Update there are checkboxes for Check automatically and Auto-install updates. Unchecking them should prevent OTA.
i'll just have to wait and see
Related
i am currently still on 1.26.401.2. and would like to update all the way to ics 4.0.4.
is it ok if i do all the 4 ota updates at once today, or could it screw up the software somehow?
ty.
[email protected] said:
i am currently still on 1.26.401.2. and would like to update all the way to ics 4.0.4.
is it ok if i do all the 4 ota updates at once today, or could it screw up the software somehow?
ty.
Click to expand...
Click to collapse
I take it you are on stock?
What carrier are you with? Vodafone, Three etc...
Try this to check for any available updates - From the Home Screen on your device go to MENU > Settings > About phone > Software updates > Check now
Jumping from 1.26 to the lates tupdate will cause no problems.
For more answers on this I would recommended taking a look through these forums, the answers are all here
The OTAs have to flash in order (that's how they arrive and they are not.complete).
Or you can flash the latest RUU for your.device (2.17.401.2), which will update it in one go, but wipe your data.
Is there any way I can refuse or block firmware updates on my non-rooted Note 2? I'm happy with 4.1.1 and don't want updated firmware to screw anything up.
Settings-about device-software update- uncheck both boxes
McLaren__F1 said:
Settings-about device-software update- uncheck both boxes
Click to expand...
Click to collapse
Under Settings - About Phone - Software Update, I have no boxes to uncheck. Only two lines are information only in gray text "Status," and "Status last checked on."
Any help?
I think you have to be rooted to disable the update process.
But firmware updates are not forced on you anyway, so it's not like it's really necessary...
Sent from my GT-N7100 using Tapatalk 2
I am a little confused about what constitues an OTA update and wished to clarify this throughly since all rooting methods have a precautionary message regarding this.
From what I know:
1. OTA updates are "only" firmware updates.
What I am confused about:
Considering my above assumption of it being only a firmware update to be right
1. Does OTA update refer to only certain methods of firmware installation?
2.Are there methods to permanently disable it such that only intentional manual procedure will cause it to happen ( E.g: System settings)
Thanks in advance :good:
nashnir said:
I am a little confused about what constitues an OTA update and wished to clarify this throughly since all rooting methods have a precautionary message regarding this.
From what I know:
1. OTA updates are "only" firmware updates.
What I am confused about:
Considering my above assumption of it being only a firmware update to be right
1. Does OTA update refer to only certain methods of firmware installation?
2.Are there methods to permanently disable it such that only intentional manual procedure will cause it to happen ( E.g: System settings)
Thanks in advance :good:
Click to expand...
Click to collapse
OTA updates will never install automatically, so take that off your worry list
1.) OTA updates are downloaded to the phone after you allow the download to proceed. Even if you accidentally click download, it will confirm with you again before rebooting the phone and installing it.
2.) If it does give you the notification, you can just long click the notification and Force Close the process. Then it won't bother you again until the next update comes out, or you choose to unroot and flash preroot, then update.
cmendonc2 said:
OTA updates will never install automatically, so take that off your worry list
1.) OTA updates are downloaded to the phone after you allow the download to proceed. Even if you accidentally click download, it will confirm with you again before rebooting the phone and installing it.
2.) If it does give you the notification, you can just long click the notification and Force Close the process. Then it won't bother you again until the next update comes out, or you choose to unroot and flash preroot, then update.
Click to expand...
Click to collapse
Rooted my device once then after unrooted after that ota update is not working How to fix this issue thank you
anas214812 said:
Rooted my device once then after unrooted after that ota update is not working How to fix this issue thank you
Click to expand...
Click to collapse
Follow this: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
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.
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.