My new N6 (Google Play Store) with a Verizon sim card has not been offered the 5.1 update OTA. It was offered the 5.01 OTA update on first boot. I ran across the following statement on the web.
As for who handles updates, it all comes from Google, no matter what. However, Google will withhold updates based on SIM card pending carrier approval. AT&T has not approved Android 5.1 yet, and therefore, anyone with an AT&T SIM card in their Nexus 6, no matter where it was purchased, will not be offered the OTA until AT&T approves it. So far, the only US carriers to approve Android 5.1 are T-Mobile and Sprint.
Click to expand...
Click to collapse
So, has any non-branded Verizon N6 received the 5.1 OTA yet? Please exclude any "forced" or manual OTAs.
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
clairez said:
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
Click to expand...
Click to collapse
Yeah this is a new thing. Ridiculous. Its never been tied to SIM provision before.
clairez said:
My new N6 (Google Play Store) with a Verizon sim card has not been offered the 5.1 update OTA. It was offered the 5.01 OTA update on first boot. I ran across the following statement on the web.
So, has any non-branded Verizon N6 received the 5.1 OTA yet? Please exclude any "forced" or manual OTAs.
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
Click to expand...
Click to collapse
Based on recollection, a few. But not many. And yes, AT&T is definately trying to control updates. I suspect Verizon will, too.
Based on the following article, I doubt that you will ever get a Verizon specific OTA on your device > http://www.androidpolice.com/2015/0...te-one-that-wasnt-purchased-from-the-carrier/
No mine would only update to 5.01. GPS N64.
Maybe pull Sim card reboot and check via only WiFi?
dahlem said:
Maybe pull Sim card reboot and check via only WiFi?
Click to expand...
Click to collapse
You might get D this way, but not E.
dahlem said:
Maybe pull Sim card reboot and check via only WiFi?
Click to expand...
Click to collapse
That didn't work for me - I had to also perform a factory reset to get the "D" OTA (tried this yesterday). I'm on Verizon with a Nexus 6 bought directly from Motorola.
At least this thread sort of answers my question posed in the linked post above. However, I'm wondering if there's something on the phone we can "clear" (so to speak) after removing the SIM in order to help trigger OTAs from Google, bypassing carrier interference.
I've been thinking of staying stock for awhile, due to expectations of quick-from-Google OTAs . . . but, this is driving me to consider custom ROMs and not looking back.
- ooofest
ooofest said:
However, I'm wondering if there's something on the phone we can "clear" (so to speak) after removing the SIM in order to help trigger OTAs from Google, bypassing carrier interference.
Click to expand...
Click to collapse
I'm not sure about this, but when you pull your SIM, I think Google sees it as a generic N6 via WiFi. So if you do generate an OTA download, it's the general one.
I wonder if you have to put another SIM card in. I know in Play, my device shows as a carrier, even though its a play store device. I imagine you'd have to use another sim in it to allow that sim to be "registered" with Google, to "overwrite" the previous one. I doubt there is anything you can clear to do that.
Pulling The String !
What I have learned so far ( rest of you gals/guys already know this! ) is that one has to be very careful with the information in these/all forums.
There are users who say they have received the automatic 5.1 OTA with a non VZ branded phone ( both GPS and Motorola variants ). But when you start to pull the string with more questions, answers start to become vague. And why people post information that is not factual is the subject of another post.
My experience at this point is as follows. With a Verizon nano sim in the N6, I will not receive any OTAs, now or in the future. The reason is not clear at this time. It may be because the N6 is listed as a non-VZ phone in Verizon's system. Which, in turn, may be caused by the IMEI not being registered in Verizon's database. All conjecture at this point. ( More factual information required )
What is clear to me is that Motorola and Google should post a warning about the N6 not being compatible with Verizon (presently). And recommend purchase of the N6 directly from Verizon. Not holding my breath on this one !
Back to the problem at hand. I have tried the various suggestions.
1. Removing the VZ sim and connecting via wifi does NOT produce an OTA (5.1) offer.
2. Removing the VZ sim and connecting via wifi and doing a factory reset DOES produce an OTA (5.1) offer. This requires a backup/restore of user data. Follow this procedure exactly:
a. Backup your Nexus 6 (go to “settings” >> “backup & reset” >> select an account to back-up by clicking on “backup” and selecting the account you want to backup)
b. Remove your SIM card (while the phone is on)
c. Reset your Nexus 6 (go to “settings” >> “backup & reset” >> “factory reset data”)
d. Restore your Nexus 6 during set-up but DO NOT insert your SIM card
e. At the end of the setup, you should be offered the 5.1 update
d. Download (~450MB) will take awhile dependent on connection speed
e. After download is complete, press the "restart and install" button
f. Android icon with spinning symbol during install system update ( 3-5 minutes)
g. N6 will restart automatically (Optimizing apps 126)
h. Home screen, Settings --> About phone --> Build number, LMY47D --> Version 5.1
But, this approach, for me, would be too onerous for future/routine OTAs. My purpose behind purchasing the N6 was the timely, automatic delivery of OTAs by Google without carrier interference. The referenced article by the Android Police may be the reality. The ultimate solution is of course with Verizon, which leaves me with an uncomfortable feeling.
As always, thanks for the help ...
@clairez,
Very good post, and summarized very concisely.
I got mine thru VZ, this is most likely the only time I'll ever say this about them - At least they released it, though being late to the party, with 5.1 already installed.
(I feel so bad for those who may have bricked trying the OTA or image and running into issues ...)
As to how they will affect us moving forward, I'm crossing my fingers, but while I hate it, let me play devil's advocate here, they didn't place a boot animation, sounds, or other oem crap on it, there are the small system services, but that's the same amongst all of the N6's. and the tramp stamp was easily removed aka ATT's.
So far, it could have been way worse as far as getting one from VZ, but I feel for you guys that had it early and are now waiting on them to get an OTA, or even have the unit register correctly on their systems.
But the overall answer to the overall thing, is that if they did hold up updates down the road, we do what any crackflasher would, flash the image when released, right? Why we got the thing in the first place
This emerging situation where carriers apparently delay our Nexus 6 OTA timings is leading me to stay on the flashing path.
Running stock and locked 5.1 E for now, might just run unlocked and accept potential decrease in local security to minimize danger in future flashes. I like stock so far, but being unlocked will probably tempt me to root and try custom ROMs, I expect.
If Verizon wanted us to stay on the pure OTA path with this phone, they don't appear to be showing that intent.
- ooofest
clairez said:
What I have learned so far ( rest of you gals/guys already know this! ) is that one has to be very careful with the information in these/all forums.
There are users who say they have received the automatic 5.1 OTA with a non VZ branded phone ( both GPS and Motorola variants ). But when you start to pull the string with more questions, answers start to become vague. And why people post information that is not factual is the subject of another post.
My experience at this point is as follows. With a Verizon nano sim in the N6, I will not receive any OTAs, now or in the future. The reason is not clear at this time. It may be because the N6 is listed as a non-VZ phone in Verizon's system. Which, in turn, may be caused by the IMEI not being registered in Verizon's database. All conjecture at this point. ( More factual information required )
What is clear to me is that Motorola and Google should post a warning about the N6 not being compatible with Verizon (presently). And recommend purchase of the N6 directly from Verizon. Not holding my breath on this one !
Back to the problem at hand. I have tried the various suggestions.
1. Removing the VZ sim and connecting via wifi does NOT produce an OTA (5.1) offer.
2. Removing the VZ sim and connecting via wifi and doing a factory reset DOES produce an OTA (5.1) offer. This requires a backup/restore of user data. Follow this procedure exactly:
a. Backup your Nexus 6 (go to “settings” >> “backup & reset” >> select an account to back-up by clicking on “backup” and selecting the account you want to backup)
b. Remove your SIM card (while the phone is on)
c. Reset your Nexus 6 (go to “settings” >> “backup & reset” >> “factory reset data”)
d. Restore your Nexus 6 during set-up but DO NOT insert your SIM card
e. At the end of the setup, you should be offered the 5.1 update
d. Download (~450MB) will take awhile dependent on connection speed
e. After download is complete, press the "restart and install" button
f. Android icon with spinning symbol during install system update ( 3-5 minutes)
g. N6 will restart automatically (Optimizing apps 126)
h. Home screen, Settings --> About phone --> Build number, LMY47D --> Version 5.1
But, this approach, for me, would be too onerous for future/routine OTAs. My purpose behind purchasing the N6 was the timely, automatic delivery of OTAs by Google without carrier interference. The referenced article by the Android Police may be the reality. The ultimate solution is of course with Verizon, which leaves me with an uncomfortable feeling.
As always, thanks for the help ...
Click to expand...
Click to collapse
thank you for your helpful post!
i just had a few clarifying questions. my current setup is 5.01 with an unlocked bootloader, rooted phone and twrp recovery.
in order for me to be able to accept the OTA update, i have to flash the stock image and stock recovery, unroot, and relock my phone. is that correct?
gunit34328 said:
thank you for your helpful post!
i just had a few clarifying questions. my current setup is 5.01 with an unlocked bootloader, rooted phone and twrp recovery.
in order for me to be able to accept the OTA update, i have to flash the stock image and stock recovery, unroot, and relock my phone. is that correct?
Click to expand...
Click to collapse
You don't need to re-lock your bootloader. Otherwise, yes on the others.
Evolution_Freak said:
You don't need to re-lock your bootloader. Otherwise, yes on the others.
Click to expand...
Click to collapse
thank you for your reply!
gunit34328 said:
thank you for your reply!
Click to expand...
Click to collapse
No problem at all.
just wanted to give my experience...
bought a nexus 6 from best buy last week and it came with 5.0 installed. right away it took a 5.0.2 update but nothing after that. I had to manually flash the 5.1 "E" build on it, which I did because I'm on verizon and felt it was the best to be on
dansan382 said:
just wanted to give my experience...
bought a nexus 6 from best buy last week and it came with 5.0 installed. right away it took a 5.0.2 update but nothing after that. I had to manually flash the 5.1 "E" build on it, which I did because I'm on verizon and felt it was the best to be on
Click to expand...
Click to collapse
Are you sure it was 5.0.2 ??? Should have been 5.0.1 no? Anyway, good job getting updated anyway. :good: Yes, Verizon users should be on E.
Evolution_Freak said:
Are you sure it was 5.0.2 ??? Should have been 5.0.1 no? Anyway, good job getting updated anyway. :good: Yes, Verizon users should be on E.
Click to expand...
Click to collapse
im sorry, you're right.. it was 5.0.1 because it was LRX22C.. my bad.
Related
How do I update my phone to 5.1, and will Advanced Calling work on my phone once I get it? It is a Motorola Store bought phone, with no Verizon logo, but I am using it on Verizon.
tysdroid17 said:
How do I update my phone to 5.1, and will Advanced Calling work on my phone once I get it? It is a Motorola Store bought phone, with no Verizon logo, but I am using it on Verizon.
Click to expand...
Click to collapse
Are you stock? Or unlocked, rooted, etc?
You want the LMY47E image. Either sideload or use factory image.
tysdroid17 said:
How do I update my phone to 5.1, and will Advanced Calling work on my phone once I get it? It is a Motorola Store bought phone, with no Verizon logo, but I am using it on Verizon.
Click to expand...
Click to collapse
Have you seen this? > http://www.androidpolice.com/2015/0...te-one-that-wasnt-purchased-from-the-carrier/
tysdroid17 said:
How do I update my phone to 5.1, and will Advanced Calling work on my phone once I get it? It is a Motorola Store bought phone, with no Verizon logo, but I am using it on Verizon.
Click to expand...
Click to collapse
I also have a Motorola Store Nexus 6 being used on Verizon.
You can upgrade to stock 5.1 "D" by removing the Verizon SIM, going to Settings -> Backup & reset -> Factory data reset, then after the phone reboots (and you connect to WiFi with SIM still removed) a prompt to update to 5.1 over the air should pop up soon after. You can accept that at your leisure (it's not a fast process.
Or, from the reference above, you can look at sideloading references in this topic and load the 5.1 "E" version, yourself - that's the level Verizon Nexus 6 phones came out with.
I wanted to experiment a bit, so forced the OTA to "D" and - after that worked fine - used the fastboot method (also referenced in the above linked topic) to upgrade to stock "E", even relocked the bootloader to see how that worked out.
- ooofest
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Rachel Ambler said:
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Click to expand...
Click to collapse
The main reason that some users bricked their phone is that they wiped the OS and had a locked bootloader which leaves no possibility ro recover the phone
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Unless something is special about the N6 that I'm not aware of, the OS you update FROM only matters if you're sideloading an OTA file. Flashing factory images, you could be coming from a custom ROM(I just took my old N4 from CM12.1 to stock 4.4 on Sunday).
The current build for VZW is 5.1 LMY47E. I think they are updating to 5.1.1 now(LMY47Z, which seems to be universal now except for maybe T-Mo). I flashed mine from E to Z on Saturday because I bought mine unlocked but it had the VZW build, and I'm on an AT&T MVNO.
gee2012 said:
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
If you root, you'll.never get an OTA anyway, sonit doesn't matter which rom you flash aa you can flash any other rom.over it
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Rachel Ambler said:
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
Click to expand...
Click to collapse
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
danarama said:
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Click to expand...
Click to collapse
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Rachel Ambler said:
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Click to expand...
Click to collapse
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile adds a kernel fix to allow their wifi calling to work. And that's it...
gee2012 said:
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
Click to expand...
Click to collapse
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
danarama said:
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile addsna kernel fix to allow their wifi calling to work. And that's it...
Click to expand...
Click to collapse
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
gee2012 said:
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Click to expand...
Click to collapse
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
danarama said:
"Well all Nexus 6 used to get the same updates but tmob and red, ..."
Click to expand...
Click to collapse
Great info, very useful.
Rachel Ambler said:
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Click to expand...
Click to collapse
There were no carrier specific ROMs when Nexus 6 came out. Using any rom on any Nexus and they will all act the same, except you wont get improved volte or wifi calling on those carriers. Their changes will not prove detrimental on other carriers
danarama said:
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
Click to expand...
Click to collapse
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Rachel Ambler said:
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
Click to expand...
Click to collapse
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on xda that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Rachel Ambler said:
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Click to expand...
Click to collapse
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
danarama said:
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on sea that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Click to expand...
Click to collapse
I'm sorry if that sudden flash of the light coming on in my head just blinded you, but that's what happens when things start to make sense!
OK, so, this all being the case, and that the OTA's are incremental, then in order to go 5.1 with the build from http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 then I WOULD need 5.0.1? Would that work though if I'm on a generic build since, if it's expecting to patch existing VZW files, wouldn't it fail because they're not there? Failing that I'd need to find a flashable 5.1 for VZW (if one even exists)?
endlessryan said:
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
Click to expand...
Click to collapse
But it wouldn't have the VoLTE improvements, etc, right? Besides, right now I'd like to stay as stock as possible as it's not just my phone I'm working on, both myself and my wife got one at the same time and I know she will most definitely NOT want anything other than stock.
Hello guys. Just bought 2 days a go a new Nexus 6. Blue with 32Gb, unlocked.
Tottaly sealed, broke the seal myself, straight from Google.
But the phone says it is updated, and finds no new update. Im on LMY47D with Android 5.1 and I dont even receive 5.1.1
Tried factory reset without SIM Card, cleaning Framework and reboot without card, everything. To no avail.
Any idea what is going on? Shouldnt I get at least Android 5.1.1?
PS: I know I can sideload it, but still, something is clearly wrong, and I would like very much to sort it out.
Thank you very much.
Same issue here. Only I'm on 5.0 and can't find any update and I would prefer to not sideload already.
if you want your phone to check for an update, you have to be on WiFi. if in youre on network instead, itll always say up to date.
I'm on wifi. It still shows no update.
Same situation, on Wifi offcourse.
tryklon said:
Same situation, on Wifi offcourse.
Click to expand...
Click to collapse
Try a factory reset, then remove your carrier SIM and power up on WiFi. My bet is that your N6 will start churning through OTAs in sequence. Not sure that you will get all the way to Marshmallow 6.0, because that last OTA is still being rolled out.
Already did it... waste of time, no updates
If your not willing to simply download and flash the images from googles website, that is your choice... but there is nothing to do but wait.
Hi Guys I am in the same boat, brand new n6 on 5.0.1 and saying up todate . In uk and carrier is Virgin if that helps.
Mal
Something strange is definately happening with Google update servers...
same dilemma and same version as op..
Personally I was like you all. I got my nice shiny new n6 from verizon (free upgrade...) Got it home kept pressing check for updates. Tried all the clearing app data from frameworks and all that.
But in the end I sideloaded it. I documented it over on the OTA url post. It is not that hard, just need some time. If you don't want to wait it might be your only option.
Total time invested was probably 1.5 hours. Downloaded all the files to my laptop and started using WUGFresh.
Stop waiting and update manually? It's not difficult, you can even save your userdata by not flashing it. There are different (and possibly easier) ways to install an update other than sideloading. especially when you can skip all the OTAs and flash directly to 6.0.
No need for a tool kit and it won't take much longer than the time it takes for you to download the factory image and extract the files.
The point is that there might be something wrong with Google's OTA servers.
Or maybe something is wrong about these phones ?
Sent from my VS985 4G using Tapatalk
Thats my point exactly. What if theres something wrong with the phone?
Google should clarify why old updates are not being delivered... not even questioning 6.0, but 5.1.1
same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0
europeanpaul said:
same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0
Click to expand...
Click to collapse
Why not sideload 6.0
jdice said:
Why not sideload 6.0
Click to expand...
Click to collapse
Why is Google not delivering OTA updates to these N6 owners ?
Sent from my VS985 4G using Tapatalk
Because there were a couple of security updates between 5.1.1 and 6.0 (as far AS I remember on my N6) and because I want to be sure OTA works!
This issue is becoming more and more coomon. Lot's of people complaining on several forums about this issue.
At least its easy to see something is clearly wrong with the OTA's, since no one is getting any. There is people stuck on 5.0, 5.0.1, 5.1, etc whichever came preinstalled stays without updates.
I've just taken my phone out of box, this is October 2015, and the moment I opened the phone first it started overheating and second I checked for updates and it says "software upto date".
The software is stuck at 5.0 and I don't know why I'm not receiving a single update when it's the time people are getting Android M. I've a Nexus 5 too and it's up to date to Marshmallow while this one is still stuck at 5.0 Lollipop.
I guess this has got to do something with the OTA feature and I want to fix this instead of flashing OS manually. So please tell me what to do now.
Till now after many Google searches I did twice reset of my phone and cleared data cache everything of Google Services Framework, but still nothing is helping.
Just 1 day old nonrooted nothing ever did, everything's from my side fine, just not understanding what to do.
Please please help me soon, I'm regretting buying nexus 6 now!
Aniket Sarkar said:
I've just taken my phone out of box, this is October 2015, and the moment I opened the phone first it started overheating and second I checked for updates and it says "software upto date".
The software is stuck at 5.0 and I don't know why I'm not receiving a single update when it's the time people are getting Android M. I've a Nexus 5 too and it's up to date to Marshmallow while this one is still stuck at 5.0 Lollipop.
I guess this has got to do something with the OTA feature and I want to fix this instead of flashing OS manually. So please tell me what to do now.
Till now after many Google searches I did twice reset of my phone and cleared data cache everything of Google Services Framework, but still nothing is helping.
Just 1 day old nonrooted nothing ever did, everything's from my side fine, just not understanding what to do.
Please please help me soon, I'm regretting buying nexus 6 now!
Click to expand...
Click to collapse
seriously?? your regretting it ??
you need patience...
patience....
patience....
I think I've mentioned that I'm not even getting 5.1, okay not even 5.0.1
Can someone please understand the level of problem I'm facing?
I've already mentioned while others are at 6.0, I'm not going anywhere ahead of 5.0
Please help!
Where did you buy your phone from? Are you sure it is not running a custom ROM? Is the bootloader locked?
Keep the phone connected to the internet (WiFi or cellular data), and sign into your Google Account, and wait another day. It may take a day or two to get update notification.
Edit - depending on your build#, you can download the OTA files and sideload them using ADB (don't need to unlock bootloader if that is a concern), or the faster option would be to just unlock the bootloader, and flash the latest factory image.
im on my 3rd day on my nexus.. but im not losing hope.. im still waiting for the ota.. its on 5.1 lmy47d...
So here is something funny. I was waiting and waiting for 6.0 on my nexus 6 for days. Never came. I have friends that have the same phone on the same carrier and they had already received their updates. So frustration and being impatient had gotten the best of me and I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING. When the phone rebooted completely wiped i went through the initial set up and it wasn't 5 min later the 6.0 update came rolling in like no big deal. WTF. I don't know why it wouldn't find it on its own but i wouldn't. Needless to day that is what I did and ended up getting it in a round about way. Maybe give that a try if you get to impatient and at that point if it doesn't show up just side load it. Hope this helps
Same, stuck on 5.1 LMY47D
google gives us factory images for a reason. if you arent patient enough to wait for an ota, just flash a factory image yourself, instead of starting threads about how you arent getting an ota. whats the point of a thread about you not getting an ota?
snoprosledneck88 said:
....I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING.
Click to expand...
Click to collapse
Sideloading the OTA using "ADB sideload" doesn't require you to unlock the bootloader.
Unlocking the bootloader is needed if you choose to flash the factory image file instead of the OTA file
jj14 said:
Sideloading the OTA using "ADB sideload" doesn't require you to unlock the bootloader.
Unlocking the bootloader is needed if you choose to flash the factory image file instead of the OTA file
Click to expand...
Click to collapse
Your right, I'm sorry. That's what I meant to say.
Sent from my Nexus 6 using Tapatalk
I got mine today and its on android 5 Doesn't want to update either, keeps saying its up to date. Haven't done anything yet with the phone. Looking now how ADB Sideload works.
jj14 said:
Where did you buy your phone from? Are you sure it is not running a custom ROM? Is the bootloader locked?
Keep the phone connected to the internet (WiFi or cellular data), and sign into your Google Account, and wait another day. It may take a day or two to get update notification.
Edit - depending on your build#, you can download the OTA files and sideload them using ADB (don't need to unlock bootloader if that is a concern), or the faster option would be to just unlock the bootloader, and flash the latest factory image.
Click to expand...
Click to collapse
I've bought it from an online retailer Flipkart in India.
I'm sure there's no changes made in phone and it's original and is as a new nexus 6 should be. Just this software update is causing me problems
snoprosledneck88 said:
So here is something funny. I was waiting and waiting for 6.0 on my nexus 6 for days. Never came. I have friends that have the same phone on the same carrier and they had already received their updates. So frustration and being impatient had gotten the best of me and I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING. When the phone rebooted completely wiped i went through the initial set up and it wasn't 5 min later the 6.0 update came rolling in like no big deal. WTF. I don't know why it wouldn't find it on its own but i wouldn't. Needless to day that is what I did and ended up getting it in a round about way. Maybe give that a try if you get to impatient and at that point if it doesn't show up just side load it. Hope this helps
Click to expand...
Click to collapse
Well I'm damn impatient, if I'd 5.1.1 and waited for 6.0 I'd have definitely had some patience, but waiting from 5.0 doesn't make sense.
Anyways to the point, after listening to your story, I tried same thing, clearing cache and reset from recovery mode, but still it didn't help
Hope there's some other resolution to this now.
I suspect it was your post that I responded to, at another forum - but you have two options really
1. Unlock bootloader (wipes data), and flash latest image
2. ADB Sideload OTAs one after the other in the right sequence (see http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 for OTA URLs) - check your current build and choose a path to get to the build you want
I am having the same problem.
I am having the same problem. Have you tried resetting the phone and starting it without the sim?
Hello all, I have a Nexus 6 and I'm using it on Verizon's network. I have yet to receive the Android 7.0 OTA update. Should I have gotten this already or is there something possibly wrong with my situation? I've searched online and it seems like I should have gotten the update already. I appreciate any help.
You should have had it by now (unless you have modified your phone in any way that might interfere with the OTA process)
Your best bet would be to sideload the OTA from https://developers.google.com/android/ota
Yeah, it's a bone stock Nexus 6. I got it from Amazon around this time last year, and I received the 6.0.1 OTA update and I receive the android security patch updates. Just no update to 7.0.
When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.
I think that there are a lot of N6 (mine is on T-mobile) out there that have not seen an OTA. I got the 6.01 November secuity patch last week. Was expecting 7.0.
I went ahead and did a sideload of the OTA 7.0. This won't break any future OTA updates, will it?
xdatastic said:
When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.
Click to expand...
Click to collapse
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.
russ4h said:
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.
Click to expand...
Click to collapse
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/
xdatastic said:
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/
Click to expand...
Click to collapse
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?
russ4h said:
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?
Click to expand...
Click to collapse
Nope, the sideload doesn't break future OTA updates (however it theoretically could if you flashed a build not intended for your carrier, however usually Google just send a 'Full OTA' which a large download to your device to get it back on the correct build).
Enjoy.
I was offered 7.0 and it took rooted
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.
tbared said:
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.
Click to expand...
Click to collapse
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.
I joined (then left) the Beta program so i can get a stable release of 7.0 Nougat a little over a month ago. Good so far but what I'm concerned about is security patches. Ever since I got on Nougat, my N6 no longer gets OTA security patches. I'm still on the October security patch. Anyone know what's going on?
Regardless, even with a mod'd phone, I got the 7.0 nag 2 weeks ago - which spurred me to wipe everything and flash it with NRT.
alryder said:
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.
Click to expand...
Click to collapse
Thanks as soon as i have some time i will reinstall and flas..