Related
How can I make OTA updates work again? I'm running 2.1 right now. But would like the critical update that will fix my phone from double dialing and lagging. My phone was rooted with Universal Androot, and I unrooted it with that app and tried unrooting it again and it said my phone is no longer rooted.
I go to Settings>About Phone>System Updates>HTC Software Update>Check Now. Then it says, System Upgrade to 2.31.651.7 (7.49 MB). Then I hit Install Now. Then it goes to the boot screen HTC and white background. And then it just stays there forever. I have to take out my battery To reboot it. I already unrooted my phone so I don't know what the problem is. And I can't find a way to download it online. Sometimes on the Sprint site they don't have the OTA update because they are slow. So is my phone soft bricked? I am trying not to do a factory reset.. so any suggestions or solutions? Appreciate the help.
iTHiZZ said:
How can I make OTA updates work again? I'm running 2.1 right now. But would like the critical update that will fix my phone from double dialing and lagging. My phone was rooted with Universal Androot, and I unrooted it with that app and tried unrooting it again and it said my phone is no longer rooted.
I go to Settings>About Phone>System Updates>HTC Software Update>Check Now. Then it says, System Upgrade to 2.31.651.7 (7.49 MB). Then I hit Install Now. Then it goes to the boot screen HTC and white background. And then it just stays there forever. I have to take out my battery To reboot it. I already unrooted my phone so I don't know what the problem is. And I can't find a way to download it online. Sometimes on the Sprint site they don't have the OTA update because they are slow. So is my phone soft bricked? I am trying not to do a factory reset.. so any suggestions or solutions? Appreciate the help.
Click to expand...
Click to collapse
If you want to keep root you should download the root version of the newest update, not the OTA version
I believe the update is rootable. But if not, at this point I don't care. I just want my phone to work without having the lag and constant double dialing. The update fixes all that. So what do I have to do? Where can I download the OTA if not from my phone?
iTHiZZ said:
I believe the update is rootable. But if not, at this point I don't care. I just want my phone to work without having the lag and constant double dialing. The update fixes all that. So what do I have to do? Where can I download the OTA if not from my phone?
Click to expand...
Click to collapse
Search in the development section on here for a rooted stock .7 rom, and then just flash from recovery
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.
Well I am surprised I received the 5.0.1 update notification but after agreeing and letting device restart, it didn't happen and device claims that is up to date and still on 5.0
Did Google retired the OTA?
Your not alone im having the same issue. My 6 is on verizon and the same issue has happened that you described. Cleared data in the frame service. Phone claims up to date...still 5.0
Darn it....
At least AT&T and Verizon respect the "direct updates form Google" advantage of the Nexus brand.
Anyone able to help?
If you've flashed a custom recovery and/or are rooted, the OTA will fail. It will just reboot without doing anything, then the OTA disappears when back in Android and autoupdate says you're up to date.
You can download the image from the Nexus factory images site, extract the system and radio images, and flash them yourself with either fastboot or Nexus Root Toolkit.
This post gave me the idea:
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
And here's the link to the latest N6 image from Google:
https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
You'll need WinRAR or similar to extract the download from Google.
It failed for me too, bone stock. Connect your phone to a charger . it reappear and I was able to update
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Same here.... Verizon/Stock Nexus 6. Mine didn't even reboot. After I chose to accept the update, screen just flashed to up-to-date. Now claiming up-to-date each time.
Strange I'm in the UK and have the exact same problem. Got a notification thru last night for the 5.0.1 update, decided to leave it until this morning and it's gone. Must be something to do with Google.....
I am bone stock and have the same issue . Last night it said there was a new update and I said ok lets do it.. It said it was going to restart and then it never restarted or nothing and says its up to date even though its on 5.0 . I am on verizon !!!
StrangeTimes said:
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Click to expand...
Click to collapse
Immediately. I guess I was lucky
I did not root/installed custom ROM neither, which boost the upset. But again, I am glad that I should not worry for update delays due the device being from a carrier's branded, and evidently I am not the only one, I will give Google the opportunity before opting for manually flash the update which that means dealing with an 20+ GB backup first.
Sent from my Nexus 6 using XDA Free mobile app
Question
Hey i was wondering, I got my OTA update last night and of course my phone is unlocked and rooted but i still attempted to download and install it. I was successful in downloading the update and my device rebooted. I shortly got the error message so i rebooted the device and when i logged back on i was still on 5.0 and the OTA notification is now gone.
My question is, since i downloaded 5.0.1 and the device rebooted in the attempt to complete the install will this now cause my phone to no longer get the 5.0.1 update notification? I plan on unrooting once i get the notification so i can go ahead and OTA and when that is completed root the phone again. Or am I now forced to flash a factory reset in order to get that OTA update again?
ideally i would prefer to wait for the OTA so i dont have to factory reset.
ATT Stock
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
gleonard3 said:
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
Click to expand...
Click to collapse
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
You are correct! Thanks. Reading elsewhere had it backwards. This worked. Off to update now. Thanks again.
No worries bud
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Do I need to be rooted to flash update? On my one plus I could download update and the go to recovery and flash it.
Tia,
Ian B
Slorks said:
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just for literally a second or so..
Hi
I've run into a problem while trying to update my Moto X (gen 1) XT1053 from 4.4.4. to 5.1. through standard OTA update. Here is the scenario:
- My phone is not unlocked or rooted, nor does it have modified firmware of any type. It is a fully stock XT1053 purchased directly from Motorola in the US that I have not tinkered with in anyway
- My phone downloaded and applied the update on Saturday morning and after the first section of the install rebooted. It sat at the screen with the M and "powered by android" at the bottom and vibrated once, then the screen went off, the same screen came back on and the phone vibrated again. Then an Android on it's back with a red exclamation and "Command" was shown.
- I figured out how to get into the recovery menu and wiped the cache, rebooted and no change. I then attempted to factory reset the phone, it did this but again no change.
- I spoke with a Motorola chat representative who was unable to help but I managed to follow some instructions on this forum to enter the fast boot menu, download and re-flash android stock 4.4.4 using RSDlite and get the phone working again.
- The phone attempted to apply the 5.1 update again yesterday and encountered the same issue again.
Would anyone have any ideas about what could be going wrong with the update process? Or ways that I can go about getting this to install correctly. The motorola rep seemed to think it was to do with my carrier, but as it was downloaded over wifi can this be the case?
If not, would anyone know how to stop android from continously prompting me to update to 5.1? I'm happy to remain on 4.4.4. if it means the phone will still remain functional.
Thanks in advance for your help.
Did you try going to settings and about phone, update
Sent from my Nexus 4 using Tapatalk
Correct, the update was applied through settings > about phone > system update
Delta117nz said:
Would anyone have any ideas about what could be going wrong with the update process? Or ways that I can go about getting this to install correctly. The motorola rep seemed to think it was to do with my carrier, but as it was downloaded over wifi can this be the case?
If not, would anyone know how to stop android from continously prompting me to update to 5.1? I'm happy to remain on 4.4.4. if it means the phone will still remain functional.
Thanks in advance for your help.
Click to expand...
Click to collapse
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
dtg7 said:
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
Click to expand...
Click to collapse
Thanks dtg7, I'll give that a try in the next day or so (updating via the recovery menu) otherwise will hold out for the 5.1 firmware and try RSDlite again.
dtg7 said:
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
Click to expand...
Click to collapse
Worked perfectly downloading the OTA update and applying through the recovery screen. Thanks for your help
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?