Database Develop

[Q] Rooted Moto X, OTA update today causing boot loop

Hi, I used PwnMyMoto-1.4.3-TMobile.apk to get root on my T-mobile Moto X.
http://forum.xda-developers.com/showthread.php?t=2444957
Today, there was an OTA update that downloaded and said it would install. Now the phone is stuck in a boot loop. It boots OK but about 45 seconds after loading it shuts down and reboots. I'm guessing its because the PwnMyMoto removed the stock recovery or altered it to be unable to install the OTA update. However I guess the phone still sees the downloaded OTA update and wants to install it, so it reboots the phone to try to install.
I can't post in the PwnMyMoto thread because I'm too new to XDA

I have froze the ota apk to try to prevent this

small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php

emerica243 said:
I have froze the ota apk to try to prevent this
Click to expand...
Click to collapse
what do you mean by this? Can you tell me how to do that?

jackashe said:
what do you mean by this? Can you tell me how to do that?
Click to expand...
Click to collapse
Freezing a particular app can be done using Titanium Backup. Its available for download on play store. Titanium Backup requires root permissions. Freezing an app will leave the app on your phone but it wont work cuz its frozen lol... the app wont be uninstalled. this way if you decide later that you need the app then you can just unfreeze it and use it.

OK, I have TB and I know it supports freeze. I didn't realize you could freeze the OTA capability as a separate program. However given that I already downloaded the update, its too late to freeze.

jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.

You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse

FSRBIKER said:
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
Click to expand...
Click to collapse
Yup I almost unlocked the boot loader but instead I was able to flash stock recovery. I wish android itself was smart enough to not try to install OTA when recovery was gone. I finally read through the jcase thread and I think I might have been able to delete the downloaded OTA by running:
Code:
fastboot erase cache
fastboot erase userdata
But I didn't try that. I also don't know what exactly that would have erased.
I will certainly look into a SquareTrade warranty!

Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.

so if we freeze updater and ota, we should be covered?
not sure about the other suspect apk with is fota.apk. I rename otacerts.apk as well. I may be a little paranoid about this but bricking is definitely not an option

jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.

jackashe said:
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
Click to expand...
Click to collapse
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.

shane1 said:
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
Click to expand...
Click to collapse
I did try rooting again using PwnMyMoto-1.4.3-TMobile.apk but it failed to install (since one of the exploits it used is patched)
I have t-Mobile but how would I get to the cache? My phone would boot for about 45 seconds and in that time-frame I could adb shell into the phone but could not find the path for the OTA update. Do you mean it would be in /cache/some-build/ or so?

Yes in cache and you would have to attempt from a PC , which might not have been possible because the phone kept rebooting. Also I am sry for your loss

Would ota root keeper do anything for us?
Sent from my XT1058 using XDA Premium 4 mobile app

IncredibleHulk6 said:
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
Click to expand...
Click to collapse
Can you please tell me how you did this? Thanks in advance

Perhaps this thread helps http://forum.xda-developers.com/showthread.php?p=46179190#post46179190

Erk, after getting into the same post-Root update loop, I flashed back to stock using the recipe here: http://forum.xda-developers.com/showthread.php?p=46175635&postcount=8
I now have 13.9.0Q2.X-116-X-17-51 installed.
When I go to System updates to update to the OTA update 13.0Q2.X-116-X-17-54, I get told that I am already updated to the latest version.
Any help would be much appreciated!
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse

manfly9884 said:
Can you please tell me how you did this? Thanks in advance
Click to expand...
Click to collapse
You have to make sure you have downloaded & installed the Android SDK and the latest Motorola Android drivers to your computer. On your phone, shut it down before it has the chance to re-enter the boot loop cycle. Then press the down button simultaneously with the power button for a few seconds and release the down button a split second before releasing the power button. This enters the bootloader (you may have to try it a few times to get it). Plug your phone into the computer and open a command prompt on the computer; type "fastboot erase cache", hit enter, type " fastboot erase userdata" and hit enter. You'll see confirmation in the command prompt and your phone will reboot as factory reset.

5.01 OTA disapeared

I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,

You're not alone. Several threads on this in general forum and Q&A. Consensus so far is hang tight and the update should resurface.
Sent from my Nexus 6 using XDA Free mobile app

Factory image is still on Google website. Grab it there.

bluh5d said:
I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
Click to expand...
Click to collapse
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers

If I manually flash the image will it change where my future otas come from ? Like doesnt a motorola nexus 6 updates come from a different server than a google play nexus 6 ?

Same thing for me, except I was waiting to be able to charge up my phone before installing. By the time I got to a charger it was gone. I'll probably just wait for it to resurface.

Same same here. Fully stock. Is the common theme for people experiencing this that they are on VZW? I am. Tmo bought phone with VZW sim.
Fyi, rebooting and charging havent helped.
I know i can manually update, but I'm hoping to confirm that the OTA process still works correctly with my stock phone running on VZW.

Its not only VZW.. I'm T-Mobile and the same happened

SirRastusBear said:
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
Click to expand...
Click to collapse
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.

mlevin said:
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
Click to expand...
Click to collapse
Flashed each separately.
Flash bootloader image
Reboot bootloader (important)
Flash radio image
Flash recovery image
Flash boot image
Flash system image (takes a while)
Flash userdata image ONLY if you want to wipe your own data
Reboot when done
Flash custom recovery
Install SuperSU from custom recovery
Reboot
Profit
Cheers

Those like me who don't want to manually flash.. I just got off the phone with Google, and apparently within 24-48 hours the update will be available again for those devices affected by this hiccup. I'll wait.

I do not want to take OTA system updates...

I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?

LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.

LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
Root solved your problem ha ha

simms22 said:
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.
Click to expand...
Click to collapse
And sometimes, even if one is 100% stock, those pesky OTAs won't install.

cam30era said:
And sometimes, even if one is 100% stock, those pesky OTAs won't install.
Click to expand...
Click to collapse
right. any system file changes prevent install.

Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?

Install a custom recovery. Done. OTAs require the stock recovery in order to flash files.

LaTropa64 said:
Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?
Click to expand...
Click to collapse
itll only attemp if you let it(it needs your approval to update), otherwise itll only tell you that an update is available. if you let it, itll try, but fail. if you boot up, youll be where you were before.

Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?

LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
you can always look at your android version in aboy phone, to see if it updated or not.

LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
You'll find update or not optimizing apps happens a lot especially if you clear cache etc...
Your fine otas can't install with root
Just flash twrp it will cone in handy incase you brick it one day you'll have twrp to fastboot fix or sideload a rom to recover from.
ONE NOTE: Never ever ever relock your bootloader with the toolkit you'll be screwed. Always leave bootlaoder unlocked. I just had to rma manufacturer phone replacement I relock mine with toolkit and couldn't flash stock firmware or oem unlock again.
Sent from my LGMS769 using XDA Free mobile app

simms22 said:
you can always look at your android version in aboy phone, to see if it updated or not.
Click to expand...
Click to collapse
I'll take a look the next time I get over there. It's not my phone, I just set it up for someone with accessibility issues and wanted it to stay the same as the day I set it up but apparently it's not done that.

nexus 6 update to 5.1 from 5.0

hey guys, Im a total NOOB to all these things. was using iphone before now shifted to android. Let me start from first. i got a nexus 6 1 mnth bak. So as soon as i got it, i put it for 5.1 update. hours later update got downloaded and i clicked install. then halfway thru the updating it said error and it started to restart. then it kept on bootlooping to the android optmisation screen. I cudnt do anything else. tried doing wipe cache, factory reset- nothing worked. SO i replaced my phone for a new nexus 6.
Now iM Totally scared to update it to 5.1 OTA. iM Ccurrently running android 5.0 build- LRX21O. I Have not rooted my phone. sO Can u please tell me whether i can update to 5.1 directly from 5.0 thru nexus roottoolkit as i dont want to do the hard way by entering commands which i think i will mess it up. or rootkit is just for rooting and unrooting phone? CAN u please give me a guide on how to update it to 5.1. i dont want to root it.
please guys, im a total noob to all this. please excuse if i dont know stuff. i used to jailbreak my iphones and ipad and do all kinds of stuff. but since im knew i dont know many things in android.
thank u so much guys

First thing to do is to unlock your bootloader. That way, if anything goes wrong, at any point, you are almost 100% able to restore your phone again. It's also a good idea to flash TWRP (custom recovery).
You can update through NRT, or as a lot of us recommend fastboot. It's not as scary as it looks, and it's actually easier to mess stuff up with a toolkit if you have no idea what said toolkit does in the background (hint: it's using the commands).
It's a good idea to read, read and then read some more. If you have a basic understanding of things it's easier to get things done correctly. Start off by reading the FAQ-thread, lots of good info there.
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029

Didgeridoohan said:
First thing to do is to unlock your bootloader. That way, if anything goes wrong, at any point, you are almost 100% able to restore your phone again. It's also a good idea to flash TWRP (custom recovery).
You can update through NRT, or as a lot of us recommend fastboot. It's not as scary as it looks, and it's actually easier to mess stuff up with a toolkit if you have no idea what said toolkit does in the background (hint: it's using the commands).
It's a good idea to read, read and then read some more. If you have a basic understanding of things it's easier to get things done correctly. Start off by reading the FAQ-thread, lots of good info there.
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Click to expand...
Click to collapse
thanks for ur reply. Wil do it in fastboot mode only. i will read more about it., One last question. Can i flash to 5.1 directly from 5.0? or to flash to 5.1 i need to update it to 5.0.1( since most of the forums said this). aLSO There are 3 shamu factory images for 5.1 LMY47D, 47E, 47I. Which one should i use?

Unless you're running T-Mobile or Project FI you should use LMY48I. Latest 5.1.1 with almost all the stagefright patches.
Edit: Oh yes... You can flash straight to the latest.

yeshwanter said:
thanks for ur reply. Wil do it in fastboot mode only. i will read more about it., One last question. Can i flash to 5.1 directly from 5.0? or to flash to 5.1 i need to update it to 5.0.1( since most of the forums said this). aLSO There are 3 shamu factory images for 5.1 LMY47D, 47E, 47I. Which one should i use?
Click to expand...
Click to collapse
Didgeridoohan said:
Unless you're running T-Mobile or Project FI you should use LMY48I. Latest 5.1.1 with almost all the stagefright patches.
Edit: Oh yes... You can flash straight to the latest.
Click to expand...
Click to collapse
I concur. Get all you drivers working. Figure out fastboot. There are many different ways to set up adb/fastboot. There is the right way or the fast way. Both work. Can always upgrade so the full SDK is available when you get hooked and have to have all the tools. lol There is a thread for 15 second fastboot. It works. Will at least be what you need to learn fastboot. When got adb/fastboot working we can walk you through the commands.

prdog1 said:
I concur. Get all you drivers working. Figure out fastboot. There are many different ways to set up adb/fastboot. There is the right way or the fast way. Both work. Can always upgrade so the full SDK is available when you get hooked and have to have all the tools. lol There is a thread for 15 second fastboot. It works. Will at least be what you need to learn fastboot. When got adb/fastboot working we can walk you through the commands.
Click to expand...
Click to collapse
ok guys, thanks for ur replies. I downloaded SHAMU lmy48i (5.1.1). im running 5.0, nexus 6 international version. let me just confirm what im going to do after this is right and tell me whether to proceed or not.
1)downloaded sdk tools. installed it. dint create a system wide directory. i opened platform tools and opened command window and typed adb version and it said android debug version 1.0.32 blh blah.
2)next i enabled usb debugging and oem unlock in developer settings of nexus 6.
3)connected my nexus 6.
4)went to platform tools and again typed adb devices. it showed my device serial number
5)then i have to enter bootloader. type fastboot devices and it should show my serial number.
6) then type command fastboot oem unlock
7)then have to run fastboot reboot
8) my bootloader is unlocked. Now i have to load it in bootloader mode.
9) then execute flash-all.
10) android will update to 5.1.1
thats all ryt? did i miss anything in this?

Didgeridoohan said:
Unless you're running T-Mobile or Project FI you should use LMY48I. Latest 5.1.1 with almost all the stagefright patches.
Edit: Oh yes... You can flash straight to the latest.
Click to expand...
Click to collapse
ok guys, thanks for ur replies. I downloaded SHAMU lmy48i (5.1.1). im running 5.0, nexus 6 international version. let me just confirm what im going to do after this is right and tell me whether to proceed or not.
1)downloaded sdk tools. installed it. dint create a system wide directory. i opened platform tools and opened command window and typed adb version and it said android debug version 1.0.32 blh blah.
2)next i enabled usb debugging and oem unlock in developer settings of nexus 6.
3)connected my nexus 6.
4)went to platform tools and again typed adb devices. it showed my device serial number
5)then i have to enter bootloader. type fastboot devices and it should show my serial number.
6) then type command fastboot oem unlock
7)then have to run fastboot reboot
8) my bootloader is unlocked. Now i have to load it in bootloader mode.
9) then execute flash-all.
10) android will update to 5.1.1
thats all ryt? did i miss anything in this?

Looks good. If going to use flash-all.bat make sure SDK platform tools are updated to Version 23+ in SDK Manager. Can also unzip the file a second time and do each image separately. Will find more use for the individual files later.

Looks good.
Quick advice: remember that unlocking the bootloader and flashing the factory image will completely wipe your device. If you've had time to accumulate some data on there that you want to keep, make sure to back it up first.
In the future, if you decide to root or use a custom recovery, you won't be able to take OTA updates (it checks for a tampered system). It's quite easy to update anyway... Just use the same knowledge you've earned doing this and follow prdog1's advice.
Unzip the factory image a second time and flash all images except userdata.img. That way you'll get a nice new updated system without wiping your stuff.
If jumping between roms or doing a major update, it can be good to let the entire factory image flash, though. Just make sure to backup your stuff first...

Why is my Nexus 6 not receiving 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?