So I am enrolled in android beta program. I was running latest version of 7.1.2 beta. I turned on phone today and had notification that the 7.1.2 N2G47H stable version was available, so I downloaded and installed. Once it installed and rebooted I received notification that 7.1.2 beta version NPG47I is available for download. Downloaded and installed and when rebooted, it told me that 7.1.2 N2G47H is available for download. This update loop is continuous, if I download one then I am notified the other is available, over and over again. Please help. What do I do? Should I just download beta NPG47I and ignore N2G47H stable update, since it looks like beta version is newer release? Unfortunately either way I am still going to have persistent notification of an update available.
peklucher said:
So I am enrolled in android beta program. I was running latest version of 7.1.2 beta. I turned on phone today and had notification that the 7.1.2 N2G47H stable version was available, so I downloaded and installed. Once it installed and rebooted I received notification that 7.1.2 beta version NPG47I is available for download. Downloaded and installed and when rebooted, it told me that 7.1.2 N2G47H is available for download. This update loop is continuous, if I download one then I am notified the other is available, over and over again. Please help. What do I do? Should I just download beta NPG47I and ignore N2G47H stable update, since it looks like beta version is newer release? Unfortunately either way I am still going to have persistent notification of an update available.
Click to expand...
Click to collapse
Unenroll from the beta program.
If I unenroll from beta program , it will completely wipe my phone right?
Got this issue as well, surely it should remain on the stable till the next beta, possibly O and not notify about an old beta. Never happened before. Unenrolling from the beta means a factory reset? Must be a universal problem.
sleeves007 said:
Got this issue as well, surely it should remain on the stable till the next beta, possibly O and not notify about an old beta. Never happened before. Unenrolling from the beta means a factory reset? Must be a universal problem.
Click to expand...
Click to collapse
Same problem here
When do you stop and just ignore the update
Sent from my LEX727 using Tapatalk
I came on here to find out if it was just me having this issue! I've done the pair 3 times now just in case, so now I've installed the massive update, then the smaller one and am just going to leave it and ignore the update available notification!
Not quite up for a factory reset, they'll notice soon enough and sort it out!
beko1987 said:
I came on here to find out if it was just me having this issue! I've done the pair 3 times now just in case, so now I've installed the massive update, then the smaller one and am just going to leave it and ignore the update available notification!
Not quite up for a factory reset, they'll notice soon enough and sort it out!
Click to expand...
Click to collapse
I got the small update first
Should I stop after that or after the large one?
Sent from my Nexus 6P using Tapatalk
clsA said:
I got the small update first
Should I stop after that or after the large one?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I've pushed so many buttons since starting I had to think, and your right, the small update came first (25mb) then the large (1.3gb) one...
It's currently asking me to install the large one (NGP47I) again. Might let it do that, then at least it's had the pair and Google can kill the request when they wake up to hopefully lots of notifications and bug reports about it in the morning!
Although I'm not sure what overwrites what... I presume the NGP47I is the big update, then the small one is just a mop up?
Currently looking in the custom rom section though, that always leads to me wanting to customise it and leave the stock ecosystem...
Same issue there. I may unenroll anyway, since my phone has been laggy as hell recently.
Sent from my Nexus 6P using Tapatalk
beko1987 said:
I've pushed so many buttons since starting I had to think, and your right, the small update came first (25mb) then the large (1.3gb) one...
It's currently asking me to install the large one (NGP47I) again. Might let it do that, then at least it's had the pair and Google can kill the request when they wake up to hopefully lots of notifications and bug reports about it in the morning!
Although I'm not sure what overwrites what... I presume the NGP47I is the big update, then the small one is just a mop up?
Currently looking in the custom rom section though, that always leads to me wanting to customise it and leave the stock ecosystem...
Click to expand...
Click to collapse
murso74 said:
Same issue there. I may unenroll anyway, since my phone has been laggy as hell recently.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Large update = March security patch
Small update = April security patch / N2G47H is newer
peklucher said:
If I unenroll from beta program , it will completely wipe my phone right?
Click to expand...
Click to collapse
sleeves007 said:
Got this issue as well, surely it should remain on the stable till the next beta, possibly O and not notify about an old beta. Never happened before. Unenrolling from the beta means a factory reset? Must be a universal problem.
Click to expand...
Click to collapse
NPG47I is beta 2 and N2G47H is stable. There is not a newer beta, just the timestamp. Un-enrolling from the beta program will not wipe your phone. They will "eventually" send down an downgrade 7.1.1 OTA that you can flash if you decide to... or not. Nothing happens to wipe your phone in the background unless you decide to flash the downgrade OTA. If you are unlocked just flash the full stable image from Google. If you do this, you will not get any more notifications. If you are not unlocked and doomed to only OTA's, then unenroll and leave it on N2G47H until the May security update in 2.5 weeks. You can also try turning off "Automatic system updates" in dev settings but some ppl report mixed results.
So I installed stable version of 7.1.2 and unenrolled my phone from the beta program. Shut down and restarted phone and now all is right in the world. No more loop or persistent notification, and nothing got wiped. Sucks not being in the beta but I guess I can wait until the next beta release and re-enroll myself.
Left it on the stable 7.1.2, persistent notification present, disappeared today and all is good, still enrolled.
Related
Hey,
did you receive the official Update allready?
I got mine today and is working so far.
Update came OTA and installed without problems.
How ist it running for you?
Einherjer* said:
Hey,
did you receive the official Update allready?
I got mine today and is working so far.
Update came OTA and installed without problems.
How ist it running for you?
Click to expand...
Click to collapse
Where you enrolled in Android Beta Program or you got it from android 7.0?
I got it from stock 7.0
Einherjer* said:
I got it from stock 7.0
Click to expand...
Click to collapse
Wow tThat was really quick even for Google! That's good news!
and what about us?? i am in beta program i must go again to official? or they will rollin out here too?
bromoxitos said:
and what about us?? i am in beta program i must go again to official? or they will rollin out here too?
Click to expand...
Click to collapse
I'm thinking those of us on beta 7.1.1 may have to roll back to 7.0 to catch OTA but not sure. Good question.. I'm gonna roll back and try and force update, no luck for me thus far on beta 711.. I'll report back later..
Edit
toro_37 said:
I'm thinking those of us on beta 7.1.1 may have to roll back to 7.0 to catch OTA but not sure. Good question.. I'm gonna doll back and try and catch it force it and will report back later.
Click to expand...
Click to collapse
I hope no need to do this, i can't make all this settings in my apps, tnx for your try to do this.
Stinks that they got rid of night light mode.
bromoxitos said:
I hope no need to do this, i can't make all this settings in my apps, tnx for your try to do this.
Click to expand...
Click to collapse
Rolled back to 7.0 via ota and I've been manually hitting update and done so about 30 times.. so far no luck...
If and when I get the ota I'll report back here immediately..
NEXUZRIP2016 said:
Stinks that they got rid of night light mode.
Click to expand...
Click to collapse
I agree! :/
Does anyone know whether it is possible to install the previous Google camera apk without root in Android 7.1?
bromoxitos said:
I hope no need to do this, i can't make all this settings in my apps, tnx for your try to do this.
Click to expand...
Click to collapse
Looks like beta people will get ota as well. This article says so..
Google launches Android 7.1.1 for select Nexus models
http://in.pcmag.com/google-nexus-6p...-launches-android-711-for-select-nexus-models
Another article on an update for our Google camera: https://www.xda-developers.com/new-shooting-modes-in-google-camera/
toro_37 said:
Looks like beta people will get ota as well. This article says so..
Google launches Android 7.1.1 for select Nexus models
http://in.pcmag.com/google-nexus-6p...-launches-android-711-for-select-nexus-models
Another article on an update for our Google camera: https://www.xda-developers.com/new-shooting-modes-in-google-camera/
Click to expand...
Click to collapse
Great news tnx a lot for this info
I got the stock 7.1.1 OTA yesterday it's running good.
Hit the check now button to check manually, even if it already did automatically you can find the update manually.
Do anyone know if stock nexus builds support f2fs, and if, for which partitions? (I've done some mild google'ing on the topic with no definite answers).
I'm on the beta still no OTA update even when checking it manually
lefantome said:
I'm on the beta still no OTA update even when checking it manually
Click to expand...
Click to collapse
I checked mine about 100 times manually then downloaded full ota and flashed it using FlashFire app yesterday.
Any word on the Bluetooth issue from DP1+DP2 going away?
I had the beta 7.1, and had not received the official OTA.
my wife also has a 5X, but on 7.0, she got the notification the day after I read that they were rolling it out "in the next few weeks"
so I updated hers, then un-enrolled my device and as soon as I restarted mine I got the notification for 7.1.1
So far life is good with it, nothing major
the 2 things I am most peeved about is no Daydream VR and still have the Google search bar front and center (figuratively)
I enrolled my Nexus 5X in the beta program and when I try to side load the official 7.1.1 release it gives me an error: "Can't install this package over newer build. Installation aborted". Is there any significant change taking about stability and battery from the DP2 and the official release? Thanks!
Got the update to stock 7.0 few days ago. This is the fastest I have ever received any android update.
Did not even check manually for updates as I was not expecting this to be available or few weeks!
Just a heads up that if you check manually for the system update it might find it right away. 5th month in a row this has worked for me first day first try, running 7.1.2 stock OTA now.
It worked right away
I love you
Has anyone on the beta got it yet? Its annoying that once again they leave us hanging for the official release and security update.
Oblox said:
Has anyone on the beta got it yet? Its annoying that once again they leave us hanging for the official release and security update.
Click to expand...
Click to collapse
I know really annoying. I tried sideloading the full OTA over 7.12, but it refused, as the beta is a newer build date (but older code).
Anyone know of a way to keep my data, but get back onto stock 7.12?
CrazyPeter said:
I know really annoying. I tried sideloading the full OTA over 7.12, but it refused, as the beta is a newer build date (but older code).
Anyone know of a way to keep my data, but get back onto stock 7.12?
Click to expand...
Click to collapse
I dont think there is a way to be honest. Just wait and hope its not as long as it was with the official nougat release.
CrazyPeter said:
I know really annoying. I tried sideloading the full OTA over 7.12, but it refused, as the beta is a newer build date (but older code).
Anyone know of a way to keep my data, but get back onto stock 7.12?
Click to expand...
Click to collapse
Use the factory image and flash it with fastboot or if you rooted, flash with flashfire
Oblox said:
I dont think there is a way to be honest. Just wait and hope its not as long as it was with the official nougat release.
Click to expand...
Click to collapse
I had to unroll from beta program to be able to receive the official 7.1.2
CrazyPeter said:
I know really annoying. I tried sideloading the full OTA over 7.12, but it refused, as the beta is a newer build date (but older code).
Anyone know of a way to keep my data, but get back onto stock 7.12?
Click to expand...
Click to collapse
The sideloading error might be because of the newer ADB tools. Try reverting back to platform tools rev.25.0.3.
Here's the issue tracker https://code.google.com/p/android/i... Priority Owner Summary Stars Reporter Opened
sitarumadalincosmin said:
I had to unroll from beta program to be able to receive the official 7.1.2
Click to expand...
Click to collapse
And no data loss?
Oblox said:
And no data loss?
Click to expand...
Click to collapse
I've made a backup first . All your data will be lost but you just need to restore from Google account.
sitarumadalincosmin said:
I've made a backup first . All your data will be lost but you just need to restore from Google account.
Click to expand...
Click to collapse
Ah thats what I thought. Ill wait (not rooted) as I cant be bothered to reinstall everything at the moment.
Oblox said:
Ah thats what I thought. Ill wait (not rooted) as I cant be bothered to reinstall everything at the moment.
Click to expand...
Click to collapse
As you wish
Very strange. I'm on DP4. About 10 minutes ago I checked for an OTA to the new official 8.0 build and hey presto, up came the Android Oreo update available message. When I hit download and install, I got an error message and now the update is no longer available. Just says I have the latest version. Anyone else experience this?
I joined the beta program today. My version is 8.0.0. Is that beta or final?
Sent from my Pixel XL using Tapatalk
SpaceGooner said:
Very strange. I'm on DP4. About 10 minutes ago I checked for an OTA to the new official 8.0 build and hey presto, up came the Android Oreo update available message. When I hit download and install, I got an error message and now the update is no longer available. Just says I have the latest version. Anyone else experience this?
Click to expand...
Click to collapse
I'm having the exact same issue and Google's help don't know ****. She keeps telling me it's not even available even though I can clearly see the update smh
Sent from my Pixel XL using XDA Free mobile app
Mine is stuck like this, lol. I have a great WiFi signal and everything. Not sure what's up.
I have this and amazing Internet speeds.
Exact same issue here
Wonder if it's those that are on DP that are effected, anyone confirm they flashed OTA successfully via DP or N?
It has been removed and is supposed to be online again, that says Google. Waiting and relaxing
I'm now on the latest version according to the updates section. Meh, I'll factory install it in the morning.
According to other threads, they had problems with signature of the update packages being incorrect. They stopped otas, and are dropping them again, I believe.
Just a second ago the OTA was available again. Tried to download it and got the same error message as the first time around. Once again it has been replaced by your system is up to date. Some crazy weirdness definitely going on here. I think I'll try again tomorrow.
noidea24 said:
According to other threads, they had problems with signature of the update packages being incorrect. They stopped otas, and are dropping them again, I believe.
Click to expand...
Click to collapse
Ah, that would explain things.
I started a help session, and they said I needed to be unrooted for the OTA to be able to do anything. I'm going to try unrooting, but tbh I'll probably just end up flashing from the factory image.
SonarMonkey said:
I started a help session, and they said I needed to be unrooted for the OTA to be able to do anything. I'm going to try unrooting, but tbh I'll probably just end up flashing from the factory image.
Click to expand...
Click to collapse
That would be pretty obvious, you can't get system updates if you're rooted on literally any device.
richfreestone said:
That would be pretty obvious, you can't get system updates if you're rooted on literally any device.
Click to expand...
Click to collapse
I knew it wouldn't install, but it usually downloads it so that I can use Flashfire. This time around it seems that it won't even do that.
I have got 2 OTA URLs for build OPR6.170623.011/8.0.0 from my Australian Telstra carrier Pixel XL registered in Beta Program.
One is incremental from DP4, the other I'm not sure but is 951MB.
Will post them up here and update with the exact contents shortly...
64MB:
https://ota.googlezip.net/packages/.../75739c219338945fd6460465b0ec6346c56235ca.zip
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:2654:68615126,payload_properties.txt:68617832:154,care_map.txt:569:156,compatibility.zip:772:1841,metadata:63:464
ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR6.170623.011/4283328:user/release-keys
post-build-incremental=4283328
post-timestamp=1502993522
pre-build=google/marlin/marlin:8.0.0/OPP4.170623.014/4187591:user/release-keys
pre-build-incremental=4187591
pre-device=marlin
951MB for OPR6.170623.012 (it disappeared before i could accept the OTA) (update - is now trying to push this OTA to my Telstra carrier Pixel XL which seems to be incorrect as I should be on the .011 build not .012):
https://android.googleapis.com/pack.../8cfe91d60eafcec2c74e3eef4c2506473b2d7187.zip
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:2549:996875675,payload_properties.txt:996878276:154,care_map.txt:464:156,compatibility.zip:667:1841,metadata:63:359
ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR6.170623.012/4283428:user/release-keys
post-build-incremental=4283428
post-timestamp=1502994895
pre-device=marlin
From another post on XDA for OPR6.170623.012:
https://android.googleapis.com/pack.../80cafb69c50be0fb6ed197998bd7434b26155355.zip
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:2654:52977084,payload_properties.txt:52979790:154,care_map.txt:569:156,compatibility.zip:772:1841,metadata:63:464
ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR6.170623.012/4283428:user/release-keys
post-build-incremental=4283428
post-timestamp=1502994895
pre-build=google/marlin/marlin:8.0.0/OPP4.170623.014/4187591:user/release-keys
pre-build-incremental=4187591
pre-device=marlin
In the US and just enrolled in Beta, got the update, unenrolled in Beta and all is good.
dhaugru said:
In the US and just enrolled in Beta, got the update, unenrolled in Beta and all is good.
Click to expand...
Click to collapse
I tried that, still no OTA update, it's been about 2 hours.
Sent from my Pixel XL using Tapatalk
imnuts said:
I tried that, still no OTA update, it's been about 2 hours.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
No update for me either.
Sent from my Pixel XL using Tapatalk
imnuts said:
I tried that, still no OTA update, it's been about 2 hours.
Click to expand...
Click to collapse
millerd79 said:
No update for me either.
Click to expand...
Click to collapse
And it's coming down now, almost 3-4 hours after signing up for the beta.
Sent from my Pixel XL using Tapatalk
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
Unless he is willing to manually update, there are only a few options. One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA. The other is borrowing a SIM from a different carrier for a few minutes, trying to update the system in settings, and then switching the SIM back. This will sometimes trigger an OTA. Finally, a more drastic measure would be to do a factory reset. Other than that he will just have to wait.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
NoobInToto said:
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
Click to expand...
Click to collapse
I'm in the same boat ?
v12xke said:
One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA.
Click to expand...
Click to collapse
Didn't work.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
My wife's Nexus 5X on T-Mobile just got Oreo a few days ago. I'm still waiting (but hopeful) for my Nexus 6P update. Neither of us were rooted or beta.
I was stuck on the August security patch too. I didn't realize it until September and then October rolled around.
I'm also on TMobile. I ended up just ended up manually updating. Worked without issue.
Did anyone else get an update notification that failed? Oxygen 11.0.1.1? Not on oxygen updater
Sent from my IN2025 using Tapatalk
Yes just checked and it's there.
Sent from my IN2020 using Tapatalk
Yup got it earlier today. It's weird cause it looked different than normal update app, and I'm on OB3 so I shouldn't get notif from stable channel. Tried to download it anyway to upload later and share on forums, but fails every time so I gave up.
Same. I try to install and it says failed.
I installed it. No problems so far.
cant see anything for eu, is that global one?
Not present on the UK/EU variant by OOS or OU.
Soon as it is I'll update my update thread.
It self installed on my OB3, and after reboot, that was inevitable, it wiped my phone
what the actual f....k
It's almost midnight here, and I'm just trying to figure out how to restore and setup my phone.
Hi after updating to 11.0.1.1. the volte icon on the status bar is missing
Did it happened to anyone? How did you fix it?
Just popped up on oxygen updater
Updated and got wiped. Noice.
MrSnowball said:
Updated and got wiped. Noice.
Click to expand...
Click to collapse
Did you update from Beta or Stable?
I just got the notification this morning, but I don't want to risk wiping my handset or losing root. (I'm on Stable, rooted with Magisk. I'm new to OnePlus so am cautious about how I update...)
Philip said:
Did you update from Beta or Stable?
Click to expand...
Click to collapse
I was on OB3 (Beta). Looks like now I am on stable again.
Yeah, I got the update notification as well. I woke up in the morning, and it was already installed, couldn't do nothing. After restart, my device was wiped. I installed Magisk before restarting, didn't do anything.
My current firmware is 11.0.1.1.IN11AA. Is that Open Beta 3 or the stable 11?
Also updated to 11.0.1.1.IN11BA and the Oneplus Launcher, navigation gestures and the notification bar doesn't work...
Well done OnePlus :/
Very glad I didn't switch to beta. I need everything to work on my phone every day for work and restoring exchange email etc isn't a quick easy task, which is why I didn't go with beta even though people were reporting better luck with ob3 than the last stable.
That's a pretty bad screw up on OnePlus this time.
On the upside, no issues so far with the update on mine.
Sent from my IN2020 using Tapatalk
OnePlus have halted the roll-out until they have resolved the issue with forcing the update (and wipe!) to those on Beta.
https://forums.oneplus.com/threads/oxygenos-11-0-1-1-for-the-oneplus-8-and-oneplus-8-pro.1340016/ (see the second post in the thread).
accurate timing... ?
Philip said:
OnePlus have halted the roll-out until they have resolved the issue with forcing the update (and wipe!) to those on Beta.
https://forums.oneplus.com/threads/oxygenos-11-0-1-1-for-the-oneplus-8-and-oneplus-8-pro.1340016/ (see the second post in the thread).
Click to expand...
Click to collapse
---------- Post added at 09:13 AM ---------- Previous post was at 08:40 AM ----------
OMG
...you can't make this sh.. up
After my phone self updated and wiped lat evening; I downgraded to OOS 10, then updated to OB3 again, with full wipe; turned off Auto-download on wifi in settings. Thought that would fix any future updates...
HA! I just woke up to the same update notification. Saying phone updated please reboot. It's has now self updated and wiped itself again
FML and F.. OnePlus engineers responsible for this
Wow, this is one crazy roll out update!
hold my beer...
after my phone just wiped itself again, I was about to do the same thing from last night, when I downgraded to OOS 10 then updated to OB3 again
but now I'm looking at the About section of the phone and it still says OB3
Naturally, what did it it exactly download to update to wipe itself, if I'm still on OB3 right now
What did OnePlus push this morning..
And why was the not to auto-update flag ignored...
Phenomenal