Need Help!
I want to side load OTA update. Phone security patch says November 5, 2017.(Build number- OPP6.171019.012)
My question is:
Do i need to sideload updates one by one or should i flash the latest OTA, which is 1GB?
If i skip to latest one will that cause any problem?
I have to sideload 10 update if i go incrementally.
masudrana4 said:
Need Help!
I want to side load OTA update. Phone security patch says November 5, 2017.(Build number- OPP6.171019.012)
My question is:
Do i need to sideload updates one by one or should i flash the latest OTA, which is 1GB?
If i skip to latest one will that cause any problem?
I have to sideload 10 update if i go incrementally.
Click to expand...
Click to collapse
No, just sideload the Full April OTA image. No need to sideload each update.
Sent from my Nexus 5X using Tapatalk
Related
So, since I updated my device to the final version of Android 7.0 nougat "via Android Beta program".. I've never received a security update.. I'm still on August security patch.. Any help??
P.S.. I know how to flash the updates manually.. My problem is that I want them OTA I don't want to do it every month!
Thanks in advance
MohamedAly92 said:
So, since I updated my device to the final version of Android 7.0 nougat "via Android Beta program".. I've never received a security update.. I'm still on August security patch.. Any help??
P.S.. I know how to flash the updates manually.. My problem is that I want them OTA I don't want to do it every month!
Thanks in advance
Click to expand...
Click to collapse
Did you manually flash a developer preview at any point? If so, Google stops pushing OTAs to your device:
https://developer.android.com/preview/download.html#flash
Idk about how to properly return to the "receive OTAs automatically" path. My guess would be to opt out off the beta program, factory reset then ADB sideload the latest November 7.0 OTA image. Then wait and see if you receive the December OTA.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Did you manually flash a developer preview at any point? If so, Google stops pushing OTAs to your device:
https://developer.android.com/preview/download.html#flash
Idk about how to properly return to the "receive OTAs automatically" path. My guess would be to opt out off the beta program, factory reset then ADB sideload the latest November 7.0 OTA image. Then wait and see if you receive the December OTA.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've manually flashed developer previews and still got the new OTA.
SlimSnoopOS said:
Did you manually flash a developer preview at any point? If so, Google stops pushing OTAs to your device:
https://developer.android.com/preview/download.html#flash
Idk about how to properly return to the "receive OTAs automatically" path. My guess would be to opt out off the beta program, factory reset then ADB sideload the latest November 7.0 OTA image. Then wait and see if you receive the December OTA.
Click to expand...
Click to collapse
No.. I didn't..I waited until the final version came out and opted out of the program.. So.. Now I'm opted out already.
But I'm gonna try this thank you
Want to change my build from Verizon NBD91V to N4F26O for all other carriers. Any easy way to do it? Can I side load an OTA or do I have to side load a factory image and lose all my stuff? Any other way to do it? I'm stuck on 7.0 and would like to update to 7.1.1. or 7.1.2.
Thanks
Sent from my Nexus 6P using Tapatalk
Yes, you can easily flash between builds/carriers with no ill effects. Download the full Google stock image (not OTA) and do it manually with flash-all.bat (first edit this file in Notepad to remove the -w (wipe) switch so as to not lose your userdata) or you can install and use a toolkit like NRT or Skipsoft found here on XDA to automate the process. Google has released a few images specific to Verizon that included a modified radio, but that radio also works well on all networks. Current radio version is v03.79 for Verizon and v03.78 for all others.
You could always flash a custom rom.
So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Click to expand...
Click to collapse
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
v12xke said:
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Click to expand...
Click to collapse
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
v12xke said:
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
Good to know, thanks.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
Good to know, thanks.
Click to expand...
Click to collapse
Boom!
Tonight recieved this new security patch update but unfortunately still 7.0
Peoples said that the next update is for 7.1.1 but still 7.0.
http://cloud.tapatalk.com/s/58a62f345fd02/Screenshot_20170217-035016.png?
http://cloud.tapatalk.com/s/58a62f4e01c2e/Screenshot_20170217-035003.png?
Still waiting for 7.1.1
Anyway here is the full detail of this security patch
https://source.android.com/security/bulletin/2017-02-01.html
Sent from my Nexus 6 using Tapatalk
And what question do you have exactly? Why the new thread?
Shabby The Dev said:
Tonight recieved this new security patch update but unfortunately still 7.0
Peoples said that the next update is for 7.1.1 but still 7.0.
http://cloud.tapatalk.com/s/58a62f345fd02/Screenshot_20170217-035016.png?
http://cloud.tapatalk.com/s/58a62f4e01c2e/Screenshot_20170217-035003.png?
Still waiting for 7.1.1
Anyway here is the full detail of this security patch
https://source.android.com/security/bulletin/2017-02-01.html
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6/general/n6f26r-7-1-1-february-image-posted-t3551869
Can a rooted stock 7.0.0 install this Feb patch? I see that update notice too.
The OTA can certainly easily be sideloaded on a rooted Nexus - you'll need to root again after the update. I've never tried the direct OTA, so I'm not sure - I've seen conflicting information on whether it works or not. If you try, the worst that will happen is that it will fail and you'll be back where you started - if you're running systemless root it may work, and if your root has changed the system partition the OTA will just stop without changing anything.
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
Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??
scrin378 said:
Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??
Click to expand...
Click to collapse
No, ADB sideload will fail. 8.1 DP2 is on a newer branch than December 8.1 stable. You could install via fastboot or wait until Google pushes the OTA for preview users.
Sent from my Nexus 5X using Tapatalk
Opt out beta tester
mr.joshuanice said:
Opt out beta tester
Click to expand...
Click to collapse
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.
luk.giak said:
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.
Click to expand...
Click to collapse
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...
scrin378 said:
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...
Click to expand...
Click to collapse
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
No, i opt out from beta program, and then i get official version..i lose my data, but nothing special, most of pics, docs, etc...is on the cloud storage ..so no big deal for me.. good luck with patience
whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash
luk.giak said:
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash
Click to expand...
Click to collapse
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?
whpsnp said:
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?
Click to expand...
Click to collapse
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.
luk.giak said:
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.
Click to expand...
Click to collapse
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?
whpsnp said:
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?
Click to expand...
Click to collapse
:good:
I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Sent from my Nexus 6P using Tapatalk
OT
As a side note for all people who do not want to unlock the bootloader. Please consider at least to:
* activate developer options (tapping 7 times on the build number under phone information)
* enter developer options and activate 1) Debug USB and 2) Enable OEM Unlock
As you probably know, the nexus 6p is subject to the bootloop of death. It is hardware based and, when it happens, the only way to give a second life to the Nexus 6p is to flash a special boot.img (or kernel) that enable only 4 cores (over 8). You can perform this procedure only if you can unlock the bootloader. Hence, only if you have previously enabled the two options above (debug USB and Enable OEM Unlock).
---------- Post added at 07:17 PM ---------- Previous post was at 07:05 PM ----------
Ulver said:
I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Click to expand...
Click to collapse
Google is really messing up with OTAs. You should consider to manually flash a factory image or to adb sideload a full OTA (available on the official website).
Same situation for me, i get ota 8.1 ~ 10 December then 8.1 dp2 ota. And for now no ota I am still on security update from November...
One question, if im rooted, can i flash full OTA with flashfire??
sideload the DP2 to Final ota (Dec patch).
Then unenroll your device from beta, you will get an update (Jan patch)
https://android.googleapis.com/pack.../105818de493dde2bb290a13474a367f78ac6122f.zip