Related
Droid 4 running OTA GB 2.3.6 here in W. San Jose, CA
I get "check for update is not available at this time.". For many days now. LTE and Wifi (LTE is almost instant and Wifi takes 5 seconds or so).
I've looked at a zillion posts about "check for update is not available" and none have a definitive explanation. -- and all of them are from a couple of months ago or earlier. Didn't find anything recent.
I understand that the intended meaning of the message is that you can't connect to the update server.
I've read dozens of "solutions" but each one of them didn't work for somebody else so I've got to assume it was just coincidence -- resetting the phone, factory reset, renaming files, and so on. I *have* network connectivity. Data works great. Apparently I'm not able to connect to the update server? That shouldn't have anything to do with rooted or not, frozen or deleted apps, safestrap, etc. Fail to update once you get the download, sure. But I am expecting to be able to connect to the server.
Anybody know for sure?
I could imagine that the connect request might contain info identifying my particular phone model or ESN (would expect software version checks to be exchanged after connecting though). Something like that.
How does VZW roll out the updates? is it strictly by geographic region? or blocks of ESN? or what?
I have the "official" OTA download from here but figured if I side loaded it I might get out of sync or cut off from future OTAs? Failed to find a definitive answer on that too .
#eliot# from dialer then restart and try again... let us know
Sent from my DROID4 using xda app-developers app
---------- Post added at 01:33 AM ---------- Previous post was at 01:29 AM ----------
dbreezy187 said:
#eliot# from dialer then restart and try again... let us know
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
That will check in with Motorola's server btw kinda busy sorry for no further info
Sent from my DROID4 using xda app-developers app
Nope.
That's one of the myriad ones I read about (didn't recognize it right away though 'cause the post I saw it in had it in numbers instead of letters). One guy said it worked for him and the next guy said it didn't.
If you haven't tried it, as soon as you type in the final '#' you get a popup that says "Log Checkin initiated". So it does *something*but it didn't change my Check for update is not available... maybe whatever it is supposed to do never got into the server either.
lol, reminded me that I used to have a comprehensive list of all those codes for my Treo. Now I got yet another mission
[edit] dahaha, "there's an app for that". https://play.google.com/store/apps/details?id=cx.makaveli.androidsecretcodes&hl=en
Other then that Matt had to push the up date to them.. I believe on one post he actually said to get back to stock 100% wipe cache partition then he pushed the ota to said device... he was really nice about the being rooted over there... the forum is closed now so I can't check for more info.. id post over at Motorola owners forum
Sent from my DROID4 using xda app-developers app
I'll give it a bit more soak time I guess. I will try side loading the update before resetting/wiping. Reset/wipe will be my last resort. First choice is OTA.
Part of what prompted my post is that I'm unclear if the phased rollout is complete.
Is it the case that EVERYONE with a Verizon Droid 4 who is going to get the notification should have gotten it by now? Or is VZW still in the middle of the phased roll out for the Droid 4's? Got to wondering since googling for the Unavailable message only returned results that were at least a couple of months old. I figured it's possible that server access was/is part of the phasing mechanism but, then again, expected to find constant posting about that if it was. It seems that the mechanism of the roll out and the schedule is also a well kept super secret.
are you rooted? I had that same problem for days before I realized unrooting will fix that. Despite what a lot of trusted posters have said here and other forums, having root and no other changes will cause that. I used voodoo ota rootkeeper (free on market) to unroot and I had the OTA installed within 10 minutes (downloaded over wifi). it is recommended you update your binaries in your superuser app before using rootkeeper.
if you're not rooted then this doesn't apply.
---------- Post added at 02:57 PM ---------- Previous post was at 02:50 PM ----------
one more note, the stock recovery on the D4 after ICS update now tracks whether you are or you were rooted. Unrooting your phone no longer hides the fact that you were at some point rooted if a service rep goes into the stock recovery screens. this has been reported on other phones earlier in the year, now also true for D4.
No effect.
I've tried all combinations.
I've used the D4 utility only to root and install safestrap ( and used safestrap only to do a backup. nothing else)
Routine goes like this:
- in safestrap: uninstall recovery
- in settings->applications->manage applications: safestrap -> force close, clear data, uninstall
- in ES File Explorer: delete /system/bin/logwrapper
- in ES File Explorer: rename /system/bin/logwrapper.bin -> /system/bin/logwrapper
- power off, reboot
- in Titanium Backup: clear filters (ALL)
- in Titanium Backup: unfreeze all user and system apps
(the only "system" bloatware I've removed was uninstallable through the normal settings->applications -- I did not use TI for that)
- in OTA Rootkeeper: delete su backup
- in superuser: update su binary
- in OTA Rootkeeper: Protect root
- in OTA Rootkeeper: temp un-root
- power off, reboot
Try to check for updates with 4G LTE (i have great reception) - fails in a second or less
Try to check for updates with WiFi - fails but it takes 5 seconds or a little longer for a response/popup
Since you installed Safestrap you can't install the OTA update anyway, so not much of a bother that you can't get it pushed to you It'd fail trying to install as OTA updates require the stock recovery.
Root does not affect it. My wife's Droid 4 was rooted (by me) and many system apps frozen and the OTA was pushed to her the same day the SOAK testers were scheduled to get it (she was not part of the SOAK test, though I was). My sisters Droid 4 was rooted as well and she got the OTA pushed to her and installed a week or so later,
You'll have to uninstall the recovery Safestrap installs, and uninstall Safestrap. You'll also have to edit some files (logwrapper.bin or something like that).
for the ota
sbf 217 4.0.4 with rsd
SBF
http://sbf.droid-developers.org/cdma_maserati/VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml.zip
rsd
http://forum.xda-developers.com/showthread.php?t=1348587
dont forget to install the motorola driver first and enable debugging mode in development in your settings
i think they are here https://motorola-global-portal.cust...e-can-i-obtain-the-usb-drivers-for-my-device?
UPDATE: (lengthy with fairy tale ending)
Management summary: I am now on the OTA ICS (acquired over the air). following a wipe/factory reset
Called *611 tech support yesterday afternoon.
Got someone that sounded like they were located on this continent AND proficient. Always a good sign when they ask what the problem is right after getting your name instead of insisting on the 5 minute scripted generic question and answer form. Stated my problem was related to the system update for my Droid 4 and that I had been getting "check for update is not available..." for a few days now. My questions were "is that expected/normal?", "I understand roll outs are phased. What is the date the roll out is expected to be complete? -- last group has been notified or can pull it?", "If the persistent 'check unavailable' message is indicative of a problem then do they have possible fixes/known problem?".
He checked for the dates and said they expect to have completed the roll out by the end of September -- all Droid 4s should have it or have it available to them by the end of September. That the "check unavailable" did not necessarily indicate a problem but that it was not "normally expected" and more likely indicative of a problem on my end since it was persistent over that length of time. I said I felt better knowing they were still in the phased roll out and maybe I should just wait a while. We tried a soft reset (vol- and power) with no effect. He said he was afraid the next step would be to try a factory reset and advised I wait a while to see if the condition cleared. Went on to say that one effect/risk of the factory reset was that, if there was a software/system problem with GB preventing the OTA check it might also effect the factory reset -- if the phone had a problem coming up it might just pull the ICS update in order to come up from the reset. (Nice! he didn't just assume I would be OK with that following a reset). That I decided to wait I should definitely call back if it didn't resolve in 2 weeks. -- OK, that was a pleasantly refreshing encounter with tech support.
So I figured, fine, I haven't really tested a restore/recovery with Titanium backup and I've never gone through a factory reset so maybe now was the time. Had 2 alternatives. I could try using the D4 utility recovery using the official (same as the OTA) zip I have on my sd card or try the wipe/factory reset and see if OTA started working.
My thoughts (due to lack of any knowledge):
- Apparently once you get on ICS there is no reversion to GB (at least the actual kernel).
- Likely they have history at Galactic Headquarters of OTA and/or physical upgrades at factory or service centers for a particular phone.
- Obviously they check the phone's system version when you connect to the OTA server. Have to in order to determine if you even need an update. Additionally they would probably check if the version the phone reports is the version they expect it to be on -- I would, for technical and support reasons.
- So maybe if I went to ICS myself it might remove me from the OTA path for future updates. Not a big deal in my mind but, heh, why eliminate alternatives if you don't have to.
* reinstall safestrap and do a backup
* uninstall safestrap (uninstall recovery, uninstall safestrap apk, delete logwrapper and rename logwrapper.bin to logwrapper)
* unfreeze everything with Ti
* batch backup all user apps with Ti
* batch backup (green and yellow) system data with Ti
* temp un-root with Voodoo
* wipe/factory reset
It comes up in GB
(lot of activity follows which I didn't write down and can't quite remember)
Basically I waited for some market activity and whatnot to die down and tried update. Immediately said update available!
Cancelled that, got Ti (pro) back from the market, batch restored missing apps.
I have eset security (i don't know... I have it on my PCs so I figured I'd stick it on my phone too. Not that I think there is much in the way of virus for android yet). Eset has an urgent notification that it wants to be added as an administrator for the device so it can protect itself from installation of counterfeit Eset. I understand that but I'm wondering if maybe Eset maybe had something to do with my fail to connect to OTA. Probably not but that's the only thing that presented itself after the reset that looked like it could have been related.
OTA again to download the update -- deferred update after download.
Oh wait, forgot to batch restore system data. Did that, checked for sms messages. All good so I triggered the update.
Holy crap!!! I forgot to temp un-root! Figured the worst thing I could do was try to abort anything and just let it run and expect the update to fail.
It didn't fail. It completed just fine?
I go through the new phone screens far enough to sign into my google account.
Bunch of market update activity.
Restore missing apps with Ti
Restore system data with Ti
Then it strikes me that, sure enough, I'm still rooted. I did not restore root anywhere after the update.
I was rooted before the update (by accident) and still rooted after the update... Whats up with that?
So at the moment I'm a happy camper.
All my apps seem to have been effortlessly restored.
All my app settings seem to be intact.
All my system data seems to be intact with no migration issues.
I'm still (magically) rooted without doing anything.
standard101 said:
[/COLOR]one more note, the stock recovery on the D4 after ICS update now tracks whether you are or you were rooted. Unrooting your phone no longer hides the fact that you were at some point rooted if a service rep goes into the stock recovery screens. this has been reported on other phones earlier in the year, now also true for D4.
Click to expand...
Click to collapse
I am going to have to disagree with this. I was rooted and flashed. Ran the download and the install failed. I then did a factory reset (lost my flash and root as expected) and immediately ran the download. Install went off without a hitch. I even had a support rep from verizon and motorola on the phone during the install when i was doing it because i was so mad about the slow download. They were watching the install once it was done because they both stated that everything on my phone "looked good".
YeeP said:
I am going to have to disagree with this. I was rooted and flashed. Ran the download and the install failed. I then did a factory reset (lost my flash and root as expected) and immediately ran the download. Install went off without a hitch. I even had a support rep from verizon and motorola on the phone during the install when i was doing it because i was so mad about the slow download. They were watching the install once it was done because they both stated that everything on my phone "looked good".
Click to expand...
Click to collapse
I don't think that's what he was saying.
After you go to ICS it tracks (displayed in the recovery screen) if you are or were rooted.
Go into recovery and you will see a yellow "qe 0/0" left of the android.
ge 0/0 -- are not rooted/never been rooted
ge 0/1 -- are not rooted/been rooted sometime prior
ge 1/1 -- are rooted/been rooted
No idea if this was tracked before but not displayed in recovery. I suspect it was. On GB they were checking system files on boot and logging differences (I think I read they were comparing system file CRCs?). The list was getting logged to a qer...something log file (I forgot the file name and where it's at). I verified that. On my rooted GB there were mostly /xbin files and a couple of others listed in the log.
Now on ICS my recovery screen shows "qe 1/1".
Oddly enough I did a factory reset, forgot to temp un-root and my root persisted through the OTA update just fine. No idea why.
Since my root persisted through the update I was not able to check before re-rooting to see if it displayed "qe 0/0". My guess is this was always logged/stored and they just added the display to the recovery screen. I would find it almost inconceivable this information (and other) was not written to NVRAM since day one. Basic support/diagnosis information.
I have tried twice now to update my phone to the new 5.1.1 update. Each time it downloads. I tell the phone to restart. When it goes to install it states Error. Then just reboots with out doing the update. No information what is causing the issue.
Now after this 2nd time my phone is stating I have to wait 17 hours to check again to try the update! No idea what is causing it to fail. Wondering if anyone else has had this issue. If not I am thinking tonight I might do a clean wipe of my phone and restart.
If your rooted or where rooted it will fail the update...have to odin back to stock first
Sent from my SAMSUNG-SM-G925A using Tapatalk
I never rooted yet
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Same issue here. After reboot the install fails. Have never rooted this phone.
Quoted from the Android Police article "As mentioned, I could not get my personal AT&T S6 to install the update. I finally got it to work after enabling all the system apps that I had disabled before trying to do it. I have seen others report success with this as well. If you have already tried and failed, just manually set your date a day ahead to check the servers for the OTA again."
check this
akitten007 said:
Quoted from the Android Police article "As mentioned, I could not get my personal AT&T S6 to install the update. I finally got it to work after enabling all the system apps that I had disabled before trying to do it. I have seen others report success with this as well. If you have already tried and failed, just manually set your date a day ahead to check the servers for the OTA again."
Click to expand...
Click to collapse
Thanks giving that a try.
Is there anyway to force my nexus 6 to receive the OTA update for android 6?
Sn0w0nS said:
Is there anyway to force my nexus 6 to receive the OTA update for android 6?
Click to expand...
Click to collapse
you can always flash the factory image, whenever you want.
Yes I know. But I would like to know if their is a way to force OTA update. Thanks.
Sn0w0nS said:
Yes I know. But I would like to know if their is a way to force OTA update. Thanks.
Click to expand...
Click to collapse
Once someone snags the OTA url, then you can adb sideload it (I haven't really been paying attention to see if this has happened yet). Until then there isn't much you can do but wait.
Ok thanks
I had luck with this procedure but it was for 5.1.1 > 5.1.1 and I knew there was an update available (already got it but the OTA failed and lost it):
1. Go to settings
2. Apps ->All running Apps
3. Next-> Google Framework Service -> Click on it.
4. Clear Cache and data.
5. Tap on Force close.
6. Tap on Disable
7. Switch off mobile.
8. Switch on mobile.
9. Go to Google Framework Service in settings ad said above.
10. Clear data n cache.
11. Enable it.
12. Go to About Phone in settings.
13. Tap on System Update.
14. Tap on Check now.
Sn0w0nS said:
Is there anyway to force my nexus 6 to receive the OTA update for android 6?
Click to expand...
Click to collapse
How to sideload OTAs
Where to find OTA files (Still waiting right now for the URLs to get captured for Marshmallow)
boomerbubba said:
How to sideload OTAs
Where to find OTA files (Still waiting right now for the URLs to get captured for Marshmallow)
Click to expand...
Click to collapse
It looks like the URLs have been captured. OP in that thread hasn't been updated, but there are a couple links that seem to be the OTA URLs.
Thanks for all the responses. I allready manually updated using my computer. I couldnt wait for OTA.
Xenosis said:
I had luck with this procedure but it was for 5.1.1 > 5.1.1 and I knew there was an update available (already got it but the OTA failed and lost it):
1. Go to settings
2. Apps ->All running Apps
3. Next-> Google Framework Service -> Click on it.
4. Clear Cache and data.
5. Tap on Force close.
6. Tap on Disable
7. Switch off mobile.
8. Switch on mobile.
9. Go to Google Framework Service in settings ad said above.
10. Clear data n cache.
11. Enable it.
12. Go to About Phone in settings.
13. Tap on System Update.
14. Tap on Check now.
Click to expand...
Click to collapse
this appears to have totally screwed my phone as it's now been "restoring data" for over an hour and I received an email saying "congrats on your new android phone".
MichaelChirico said:
this appears to have totally screwed my phone as it's now been "restoring data" for over an hour and I received an email saying "congrats on your new android phone".
Click to expand...
Click to collapse
that had nothing to do with your issue. congrats email happens every time you factory rest your phone, as of now. and you did factory reset it. your hour long restoring data is just that. if you have a weak signal, it can take days as well. or, it could not be doing anything, just sitting there. if so, youd need to factory reset your data again. but its nothing to do with the procedure that you followed. you can always try just rebooting, that might fix it as well.
Xenosis said:
I had luck with this procedure but it was for 5.1.1 > 5.1.1 and I knew there was an update available (already got it but the OTA failed and lost it):
1. Go to settings
2. Apps ->All running Apps
3. Next-> Google Framework Service -> Click on it.
4. Clear Cache and data.
5. Tap on Force close.
6. Tap on Disable
7. Switch off mobile.
8. Switch on mobile.
9. Go to Google Framework Service in settings ad said above.
10. Clear data n cache.
11. Enable it.
12. Go to About Phone in settings.
13. Tap on System Update.
14. Tap on Check now.
Click to expand...
Click to collapse
Pulled the old Nexus 6 out of the drawer and the update wasn't showing. Followed your instructions and magic happened. Wanted to post a thanks and confirm working instructions =D
Google doesn't recommend clearing the data on Google services framework
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
While it is not going to brick your phone, it can cause "nuisances on the device" - read more at the link above.
jj14 said:
Google doesn't recommend clearing the data on Google services framework
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
While it is not going to brick your phone, it can cause "nuisances on the device" - read more at the link above.
Click to expand...
Click to collapse
From the link: said:
"Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)
How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.
Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.
All of this can be avoided by just doing an 'adb sideload' if you are impatient."
Click to expand...
Click to collapse
I'm perfectly fine doing a fake factory reset like this to be able to get an update only real factory reset phones get. They need to optimize their OTA release system so folks can actually get updates reliably when they arrive. The way they do it now is just terrible and drives folks to do things like this. I didn't notice any weird side effects either. The difference between side-loading and this is often 1.xGB vs 14-150MB for a download as well as the additional necessary work on a PC. I'm no stranger but it's clearly not easier.
Instead of the OTA system seemingly randomly choosing early adopters, it should be up to the user whether or not they want to chance it. The "Check for Update" button, as a result of this silly system lies/is pointless - why even have it. The only time it's useful is if you're several versions behind and even then you usually just get an update prompt because it's often a factory reset phone.
Xenosis said:
They need to optimize their OTA release system so folks can actually get updates reliably when they arrive. The way they do it now is just terrible and drives folks to do things like this.
Click to expand...
Click to collapse
Amen to that
I think a better way would be to make the update available to everyone on day 1 - but don't push it out to everyone on day 1 - do it in a phased rollout as it is done today. But if an impatient person (like me) wants the update, let me go to the "check for updates" screen and if I click it, push the update to me!
This way, a majority of the folks (that are likely not even aware of new updates being released, and don't care) will get the updates in a phased rollout, while the enthusiasts that are waiting around drooling for a specific fix that will be addressed in the next update can get the update when they want.
jj14 said:
Amen to that
I think a better way would be to make the update available to everyone on day 1 - but don't push it out to everyone on day 1 - do it in a phased rollout as it is done today. But if an impatient person (like me) wants the update, let me go to the "check for updates" screen and if I click it, push the update to me!
This way, a majority of the folks (that are likely not even aware of new updates being released, and don't care) will get the updates in a phased rollout, while the enthusiasts that are waiting around drooling for a specific fix that will be addressed in the next update can get the update when they want.
Click to expand...
Click to collapse
Well said. You'd think they would have figured that out if they cared.
Sn0w0nS said:
Is there anyway to force my nexus 6 to receive the OTA update for android 6?
Click to expand...
Click to collapse
Just sideload the OTA update using wugz
Xenosis said:
I had luck with this procedure but it was for 5.1.1 > 5.1.1 and I knew there was an update available (already got it but the OTA failed and lost it):
1. Go to settings
2. Apps ->All running Apps
3. Next-> Google Framework Service -> Click on it.
4. Clear Cache and data.
5. Tap on Force close.
6. Tap on Disable
7. Switch off mobile.
8. Switch on mobile.
9. Go to Google Framework Service in settings ad said above.
10. Clear data n cache.
11. Enable it.
12. Go to About Phone in settings.
13. Tap on System Update.
14. Tap on Check now.
Click to expand...
Click to collapse
Nexus 6P user is here, find this thread on google search.
March update hadn't reached to my device after 15 days, lazy to connect it to computer and sideload the ota but clearing Google Framework Service's data did the job.
Thanks :good:
how?
How does one go about capturing OTA update download URLs?
simms22 said:
that had nothing to do with your issue. congrats email happens every time you factory rest your phone, as of now. and you did factory reset it. your hour long restoring data is just that. if you have a weak signal, it can take days as well. or, it could not be doing anything, just sitting there. if so, youd need to factory reset your data again. but its nothing to do with the procedure that you followed. you can always try just rebooting, that might fix it as well.
Click to expand...
Click to collapse
Those steps worked just fine for me .
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?
My XT1095 is running the stock 6.0 rom and it's rooted. I keep getting the "Install System Update" nag screen all the time. It won't leave me alone. I don't want to update yet because I read it'll cause problems with root and I'll have to unroot or reroot or whatever and I don't want to mess with it right now. I was hoping that it would get bored of me telling it to go away and leave me alone but it hasn't. It shows up every time I unlock my phone if it's been sitting for more than 10 minutes. It shows up when I'm literally in the process of typing a text message, or when I'm surfing a web page, or when I'm in the middle of doing a dozen other things... like it thinks it's so mightily important that it can interrupt anything I'm doing.
It's version: 24.201.3.en.US. Just a security update from what I read elsewhere. It's not a notification so I can't long-press and force stop it or anything. I read that it's supposed to go away on it's own after a week but it's been quite a bit longer than that now. Any ideas on how to get it to stop nagging me? Or an easy way to apply this without screwing up root?
an actual app is in charge of nagging you to update the system software. I cant remember its name but it is located in system/priv-app, "ccc.motorola.ota" or something like that, cant really remember. You can try either deleting it or disabling it.
What i personally did to prevent this is installing fresh stock system image, updating to latest version AND THEN rooting, so updates wont nag me anymore
billybully said:
an actual app is in charge of nagging you to update the system software. I cant remember its name but it is located in system/priv-app, "ccc.motorola.ota" or something like that, cant really remember. You can try either deleting it or disabling it.
What i personally did to prevent this is installing fresh stock system image, updating to latest version AND THEN rooting, so updates wont nag me anymore
Click to expand...
Click to collapse
I did the same, but when I installed a fresh stock image, this new update wasn't available yet. It only came out recently.
DrvLikHell said:
I did the same, but when I installed a fresh stock image, this new update wasn't available yet. It only came out recently.
Click to expand...
Click to collapse
Take a look at this post:
http://forum.xda-developers.com/showpost.php?p=66479956&postcount=15
This should disable the system update nagging.
desertcat said:
Take a look at this post:
http://forum.xda-developers.com/showpost.php?p=66479956&postcount=15
This should disable the system update nagging.
Click to expand...
Click to collapse
I did that, except the app name on my phone was a bit different. So far no more nagging. Thanks a bunch.