Related
I'm on the last release of the beta, stock beta.
I took my Nexus off the beta... But I'm not getting any OTA updates.... Am I stuck on the beta now? I thought I would get the new version people are talking about from the other day.
God.... I don't want to ADB flash it.
Flashing has gotten so much more complicated the last couple years. And with all the talk about people bricking, I don't want to take any risks.
I apologize if this has been asked already, any useful information gets buried so fast these days.
Maybe I'm just getting old. ****.
Sent from my Nexus 6P using Tapatalk
I'm on nrd90m I left the beta, and nothing happens. Why isn't it updating g to nrd90u ....
Sent from my Nexus 6P using Tapatalk
The ota rolls out in stages. Give it time, youll get it
Okay. Thanks. That's sort of what I was thinking. But I couldn't find anything that said I would go forward out of the beta and not wiped and back to mm
Sent from my Nexus 6P using Tapatalk
I'm on NRD90M same as u we will get the update to U also jus give it time
Sent from my Nexus 6P using Tapatalk
I installed NRD90M through beta and immediately un-enrolled.
Do i need to re-enroll in beta to get the NRD90U OTA update ?
Salim Zhulkhrni said:
I installed NRD90M through beta and immediately un-enrolled.
Do i need to re-enroll in beta to get the NRD90U OTA update ?
Click to expand...
Click to collapse
No, the OTA will come to your device soon and if you can`t wait flash the firmware in fastboot.
Now that the official release is out is it possible to dirty flash, unenroll from beta and not lose data? I know unenrolling will instantly result in a wipe... Which is kinda ridiculous. Windows phone just leaves you on your current build till public releases catches up... Is there a way to do this on android and still get OTA official updates?
Sent from my Nexus 6P using Tapatalk
letrain02 said:
Now that the official release is out is it possible to dirty flash, unenroll from beta and not lose data? I know unenrolling will instantly result in a wipe... Which is kinda ridiculous. Windows phone just leaves you on your current build till public releases catches up... Is there a way to do this on android and still get OTA official updates?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Unenroling now won't wipe the phone as it did on the beta releases.
It will just sit and wait for nrd90u to roll out? Then flash OTA without losing data? Do I need to fastboot nrd90u? Or just wait?
Sent from my Nexus 6P using Tapatalk
All the little warning says is "if your on a beta version" we will OTA flash and erase all. Wish it was more clear on their website. Technically nrd90m is the beta version.
Sent from my Nexus 6P using Tapatalk
Thanks for the help.
Sent from my Nexus 6P using Tapatalk
I'm still on NRD90M and still enrolled in the Beta Program.
I'm just waiting for the OTA to be pushed to my phone.
If you want you can go ahead and Fastboot the NRD90U image and jus don't wipe your data u should be fine since u already on Nougat.
I wouldn't recommend dirty flashing as sometimes it can lead to fc's and such. But that's me I've never dirty flash period. But I know some peeps do it and have no issues.
But far as I know I haven't heard of anyone that's on NRD90M receive the OTA update to NRD90U yet..
Sent from my Nexus 6P using Tapatalk
I may be missing something, but according to Google, NRD90M is an official release as it is not prefixed with NP. It states, all beta builds are prefixed with NP.
'Ok. I tried to unenroll when google first said they released N officially but it wanted to flash OTA downgrade me and wipe data. I'm guessing because it hadn't been officially released for Nexus 6p yet. Now that it has been released officially. Even though a different build number, apparently it doesnt ask that anymore.
Sent from my Nexus 6P using Tapatalk
If you download the factory image, extract it and edit in notepad the flash-all.bat script with removing the -w behind update command at the end you will get up to the latest version without the need to wipe and unregister from the beta.
I unenrolled from the beta program and didn't get any notification to install a system update. I then flashed the official version posted by Google and wiped data on purpose to start fresh.
I wiped and flashed factory a few days ago, this morning unenrolled from beta. No notifications on my phone, checking for system update doesn't say download available.
Should mark this as solved but I can't edit the title in Tapatalk. Unenrolled, not notification like before. But the official nrd90u has come through OTA yet...or will it?
Sent from my Nexus 6P using Tapatalk
im pretty sure the NRD90M build is the official build along with the NRD90U
Not according to google....https://developers.google.com/android/nexus/images
It's solved now. No problems.
Sent from my Nexus 6P using Tapatalk
guys help. I was on the NRD90M build on the Nexus 6P. I got an OTA for the Septemeber Security Patch, installed it and now my build number has changed to NRD90T. Does anyone know what is going on?
Septemeber Security patch with an August kernel version?
So, if NRD90M is beta and I'm not in the beta program any longer, how do I get on official track without losing data? I'm not rooted and bootloader is locked.
Sent from my Nexus 6P using XDA-Developers mobile app
The understanding I've read from info in the beginning of the thread is to wait for OTA, or adb flash "official" and take out the -w...it's in an earlier post
Sent from my Nexus 6P using Tapatalk
What I mean is, will I get an OTA or do I need to manually flash one. And if manual, which do in flash? I haven't seen a definitive answer on what you should expect if on NRD90M. Wrist case, I re-join the beta, get a OTA then leave and get the OTA that wipes data.
Sent from my Nexus 6P using XDA-Developers mobile app
I was on NRD90M up until yesterday and I decided to go ahead and fastboot the NRD90U Factory Images back to all stock then flashed TWRP 3.0.2.2 made nandroid then flashed SuperSU 2.78 all good now.. only reason is BC nobody had a definite answer if I would receive a OTA or not so I went ahead now no more concern's.
But I can say for sure 90M and 90U are definitely different as I have noticed little things here n there..
Sent from my Nexus 6P using Tapatalk
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.
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
Hi all
im currently running on the latest update which is july updates with android 8.0 and july security. i havent got any updates. when i go on to check software updates it says "your system is up to date" with android version: 8.0.0. and security patch level: July 5, 2017. any help will be great.
thanks
Your best bet would be too download the update manually. Do you have access to a computer?
Kermit404 said:
Hi all
im currently running on the latest update which is july updates with android 8.0 and july security. i havent got any updates. when i go on to check software updates it says "your system is up to date" with android version: 8.0.0. and security patch level: July 5, 2017. any help will be great. thanks
Click to expand...
Click to collapse
Manually update. Even if your bootloader is locked you can sideload a new OTA. Why wait?
Just leave the beta programm. Got the September patch 30 seconds after leaving. Also it won't make any difference until Google uploads the first Android 9 dev builds, wich probably won't come for the 6P anyway
I'd try to sideload the OTA manually if I were you. Using the stock recovery.
If that goes well then you are done.
Sent from my Nexus 6P
I also had to unenroll from the beta to get the Sept updates.
I'm on T-Mobile and have not received any September security patch. I am going to have to side load
ZombieUsr said:
I'm on T-Mobile and have not received any September security patch. I am going to have to side load
Click to expand...
Click to collapse
Was there a question in there somewhere? Yes is the answer.
v12xke said:
Manually update. Even if your bootloader is locked you can sideload a new OTA. Why wait?
Click to expand...
Click to collapse
is there any video on how to manually update. since im been trying its not helping when there is no tutorial on how to manually update
I'm experiencing the same issue. I already unenrolled & re-enrolled in the beta once to try to fix my battery issues and it's stuck at the July update. If I unenroll it again, will it wipe the phone?
thesebastian said:
I'd try to sideload the OTA manually if I were you. Using the stock recovery.
If that goes well then you are done.
Sent from my Nexus 6P
Click to expand...
Click to collapse
sideload OTA on mac is not working it still says ota is directory. but it did not send to my nexus 6p
Kermit404 said:
sideload OTA on mac is not working it still says ota is directory. but it did not send to my nexus 6p
Click to expand...
Click to collapse
Update your platform tools and try again. If you receive another error or the same one, post a screenshot.
Sent from my Nexus 5X using Tapatalk
anotherjmartin said:
I'm experiencing the same issue. I already unenrolled & re-enrolled in the beta once to try to fix my battery issues and it's stuck at the July update. If I unenroll it again, will it wipe the phone?
Click to expand...
Click to collapse
No, it won't be wiped.
Hello everyone
i managed to manually sideload OTA update to my nexus 6p. its officially working. all good. i had issues than managed to fixed it.
SlimSnoopOS said:
Update your platform tools and try again. If you receive another error or the same one, post a screenshot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
i did update platform and perform SIDELOAD OTA update. its working. thanks