Nexus 7 32GB Will not get OTA - Nexus 7 General

Hi, I just got a nexus 7 32GB to replace my 16GB. The problem is that I'm not getting the OTA. I'm stock 100%, but don't want to install 4.3 via adb.
I have tried the following:
1 - clearing cache and data from framework services, then look for update. = NOTHING
2 - clearing cache and data from framework services, stopping service, then look for update. = NOTHING
3 - clearing cache and data from framework services, restart, then look for update. = NOTHING
4 - clearing cache and data from framework services, stopping services, restart, then look for update. = NOTHING
Been doing this for 2 days now, do you guys have any other suggestions. Or maybe using only one method from above over and over.
Thank you!!!

Seems like adb is your only option. Besides, rooting and playing with your tablet is fun and teaches you more of your device. You'll also appreciate the fact that since this is a nexus device, the factory image is readily available at your disposal if anything happens.

You have a nexus device. You are on a developer web site.
Why on Earth would you wait for an OTA? Grab the image from Google's Nexus Images site and flash it.

GldRush98 said:
You have a nexus device. You are on a developer web site.
Why on Earth would you wait for an OTA? Grab the image from Google's Nexus Images site and flash it.
Click to expand...
Click to collapse
And that, my friends, is logic
Sent from my SGH-M919 using xda app-developers app

It's a lot more fun to flash it manually, and you learn a lot in the process. Next time your Nexus bricks, you'll now how to fix it (if you didn't copy paste commands )

Don't want to unlock bootloader, that is the logic. Don't want to flash via adb, read it, it's in the first post. I'll do it if it's my last option, i'll wait a couple of days, if no OTA by then, i'll flash. Thank you all!!!

Did you try hard rest
Sent from my SGH-M919 using Tapatalk 2

Hi, zcucurullo...
There are links for Jellybean 4.3 OTA .zips here (you'll have to wade through a fair amount of text to find 'em) for both WiFi only Nexus 7(Grouper/Nakasi) and WiFi/3G Nexus 7(Tilapia/Nakasig) which you should be able to flash via stock recovery and ADB (unfortunately), but without unlocking the bootloader.
Some instructions here.
--------------------------------------
I can't think of any other way of doing it to be honest... other than as Nasser suggests, and try a hard reset/factory reset (although you will loose all your data).
Kind of odd though, you haven't been pestered with endless notifications about the OTA, which has been available for, I think, 4 weeks now.
Anyway... good luck.
--------------------------------------
Edit & additional...
XDA Recognized Contributor, oldblue910, maintains an archive of Nexus 7 Stock OTA URLs here... http://forum.xda-developers.com/showthread.php?t=1745781
Rgrds,
Ged.

I have nexus 7 32gb. Got the ota when it was released.
Skickat från min Galaxy Nexus med Tapatalk 4

GedBlake said:
Hi, zcucurullo...
There are links for Jellybean 4.3 OTA .zips here (you'll have to wade through a fair amount of text to find 'em) for both WiFi only Nexus 7(Grouper/Nakasi) and WiFi/3G Nexus 7(Tilapia/Nakasig) which you should be able to flash via stock recovery and ADB (unfortunately), but without unlocking the bootloader.
Some instructions here.
--------------------------------------
I can't think of any other way of doing it to be honest... other than as Nasser suggests, and try a hard reset/factory reset (although you will loose all your data).
Kind of odd though, you haven't been pestered with endless notifications about the OTA, which has been available for, I think, 4 weeks now.
Anyway... good luck.
--------------------------------------
Edit & additional...
XDA Recognized Contributor, oldblue910, maintains an archive of Nexus 7 Stock OTA URLs here... http://forum.xda-developers.com/showthread.php?t=1745781
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you my friend, will try hard reset, don't have anything inside at the moment. Do I have to add my google account before trying the update after the reset?:cyclops:

Hard reset did not do the trick, still on 4.2.2 i'll give it a few more days and will try to connect to different internet providers just to see. Thank you all!!!

Oops

zcucurullo said:
Hard reset did not do the trick, still on 4.2.2 i'll give it a few more days and will try to connect to different internet providers just to see. Thank you all!!!
Click to expand...
Click to collapse
by changing the internet provider will your device get priority for OTA update even if you are in the same country? or does having a different internet provider change your device information for OTA update?
i thought it does by device firmware information, as long as your online, you will eventually get firmware OTA update?
i'm confused, not that it matters. just curious how OTA updates are actually pushed.

FYI installing the factory image from Google does not install over adb, it installs over fastboot

Just change your vpn to some US location and then try 1 and 2 as given in op. (preferably 2.)

lekhwani said:
Just change your vpn to some US location and then try 1 and 2 as given in op. (preferably 2.)
Click to expand...
Click to collapse
I saw somewhere that if google can't find your device you wont get the update. That's why I wanted to try out using internet from different carriers. Thank you all for your help on the issue.

AuroEdge said:
FYI installing the factory image from Google does not install over adb, it installs over fastboot
Click to expand...
Click to collapse
Fastboot adb, etc... Just want to get OTA. Don't want to push manually to device by downloading the update and connecting via USB and using fastboot command. Dont want to unlock bootloader also. So the problem is OTA. Thank you!!!

lekhwani said:
Just change your vpn to some US location and then try 1 and 2 as given in op. (preferably 2.)
Click to expand...
Click to collapse
SOLVED, SOLVED, SOLVED.
JAJAJAJAJA, you rule, just changed my VPN to a free Canadian one, and the nexus 7 is downloading the Update as I type. Thank you, Thank you, Thank you!!!

Related

Failed OTA to 4.2

I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Update just failed for me too, which having read up, looked like it might have been because of having an alternate recovery installed.
So I removed the recovery .................UPDATE FAILED
Removed root.....................................UPDATE FAILED
Locked Bootloader..............................UPDATE FAILED
Full system wipe.................................UPDATE FAILED
You can force a retry by going to App,------All-------Google Services Framework and stopping the process and wiping the data
Then checking for update manually.
Some folks say you can have problems with Play and push notification after the framework wipe, but as I had gone the route of restoring to default, I wasn't bothered as I will just do the same again.
I wonder if there is a deeper issue however, than just my tablet.
Phil
jonchill said:
I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Click to expand...
Click to collapse
did you guys did anything or change anything from system, like change the proxyprovider.apk for flash support? Mine failed through OTA and even via manual update but then I changed back the those apks and things went well and now I am on 4.2. Just sharing my experience and hope it can help you guys. somewhat.
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
My tablet updated just fine and it is both rooted and unlocked. My galaxy nexus which is the same (both rooted and unlocked) for some reason fails on the 4.2 update.
I had the exact same problem over the past two days, I don't have a custom recovery, just unlocked bootloaded and root.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
OOOOOH! I froze then deleted the KOREAN IME app, because why the heck do I need a Korean app on my tablet? Hmm, so what are my options? Can I just redownload the Korean IME off the play store and OTA will work then?
Was there any other forced IME like Chinese that's 'baked in' to the Google ROM? I forgot if I may have deleted any others, but I think it was only Korean.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
That explains it then I've deleted and frozen stock apps.
Thanks
I'm the same, i deleted system apps.
Is the only way to fix this to use a pc and adb the 4.1.2 zip and gapps?
Is there any way to fix it from the device itself?
(I've tried flashing the 4.1, 4.1.2 and 4.2 via CWM)
Would reflashing the 4.1 gapps help?
Sent from my Nexus 7 using xda premium
I had the same problem. Used titanium backup and the "integrate system apps updates into ROM" option and then couldn't update to 4.2.
Tried several things I read in this forum but nothing worked.
Had to erase everything and flash the stock ROM I downloaded from Google. They have a 4.2 stock ROM too so didn't need to update afterwards.
Then restore all your apps from backup and you are set.
Sent from my Nexus 7 using Tapatalk 2
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Chocoburger said:
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Click to expand...
Click to collapse
The alternative is that you restore your system folder to its original state (i.e. get hold of that Korean IME app, stick it back in /system/app and set the correct permissions). I had to do this with Google Wallet but it can be done if you know exactly what you've changed and avoids flashing a factory image and setting your device up again (albeit that Titanium makes this relatively painless now).
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
Me too. Also a 32gb N7. I owned it less than a week. Multiple factory resets didn't correct the issue either. I returned it to the store for a refund. Didn't want to keep a device that would never install updates.
I have 32 gigabyte Nexus 7 and it came with Android 4.2 out of the box so I guess no problems with the updates
Sent from my Nexus 7 using XDA Premium HD app
CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
So your saying you opened it, turned it on, signed in.....then your status bar should show system update available, click it, accept, let it do its thing and it just failed?
Sent from my Nexus 7 using Tapatalk HD
If you search the forums this has been addressed and solved. You need to reflash the os - you don't need root. Use wugs toolkit. Its a problem on googles end where the nexus was formatted incorrectly, and a reflash fixes it.
Sent from my Nexus 7 using Tapatalk HD
Yep. Got the Android robot on his back, with the triangle/exclamation point on top of him, after downloading, restarting and almost complete install. I've tried multiple times and miserably failed each time, at the same point. Eventually, I was able to manually update it using Wug's Nexus Toolkit, since all other methods failed. Thank you Wug
Sent from my Nexus 7 using Tapatalk 2

[SOLVED] Stock 4.2.1 upgrade failed.

I've bought my son and daughter a nexus 7 each for Christmas.
His upgraded over the air fine, hers downloaded the firmware, rebooted and the installation started.
After a couple of minutes the Android fell over with a red exclamation mark.
I've tried forcing the upgrade and the same happened.
Any ideas how to upgrade her nexus 7?
Thanks
Fastboot mode is working ?
Sent from my GT-I9100 using xda premium
I've not tried it.
How do I try it?
Assuming it's ok, does that help with upgrading?
Any issue truing fast boot mode?
Any ideas? Or will it need replacing?
Factory reset and try again
Sent from my Nexus 7
I have the same problem.
Hey guys,
I made an account just to post this, however it was all done my G2 so I apologize for poor formatting and/or not completely clear instructions. This issue has kept me up for hours upon hours, and I finally figured out how to fix it. The issue apparently has something to do with the way the Nexus was formatted, prohibiting the update from working. Google/Asus support have been useless regarding the issue which is a very simple fix just requiring the user to reflash the N7 with a stock image. It has been confirmed working by not just me but other people on the reddit nexus 7 board. Here is what I did (copy/pasted from my reddit thread):
---------------------------------------------------------------------------------------------------------------------
There are two methods to fix this, an in depth method, and an easy and quick method. My first time I used the in depth, but I tested this with the easy method too so I'll just post that. I'm on a cell phone so I'm not going into the in depth method - I'm posting this so hopefully the other people like me who got this on Christmas won't have to return it.
----------------
For the quick and easy method, download Wug's toolkit here:
(google this, forums wont let me post links until I reach 10 posts)
Run the driver install guide, making sure to follow the parts about uninstalling previous drivers. Follow this to a T. Next, unlock your bootloader. Its painless and takes seconds. Next, go here and download your Nexus specific update.
(Find this on google developer site, you can google it too - forums wont let me post links - also make sure its 4.2.1)
Click on the "back to stock + unroot" -- we never rooted, but just do this. Select other/browse and browse to the image you downloaded. Flash this. You WILL fail on three files - it says something like recovery.sig failed - it will do it for two other .sig files. This is fine. Let it do its thing. A few minutes later your android will boot up. Log in, and go to settings. Click about tablet. Click on build number like 10 times, until it tells you developer options unlocked. Go into developer options and enable USB debugging. Now, go back to Wugs toolkit and lock the bootloader. There you have it, an updated nexus running stock everything, and locked so your warranty is not void.
----------------------------------------------------------------------------------------------------------------------------
This was a very sloppy guide put together on my cell phone. Any questions just post and I'll do my best to get back to you. Goodluck!
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
albert_htc said:
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
Click to expand...
Click to collapse
This is definitely the easiest way for you to fix your problems. The risk of your device becoming unusable is practically none. This is the beauty of nexus devices, Google provides official factory reset ROMs for you to flash in these sorts of situations. You can either use Wugs or mskip's tookit as advised to automate the process (fastboot commands used to flash the recovery image, fastboot commands are simply used to flash it to your device) or you can use fastboot to flash it yourself manually (still very easy)
I would 100% do this to fix your device. Don't be scared! This is the official way of fixing a nexus device when it doesn't function.
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
albert_htc said:
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
Click to expand...
Click to collapse
I'm not certain about the driver issues because I don't use Wug's toolkit, sorry!
However, when you get this completed, it should solve this problem in the future.
I've had to go with option 1 for the drivers..
but it's done and working
One thing I did have to do after unlocking the boot loader was reset up on the wifi and re enable USB debugging before I could continue.
all sorted thanks
albert_htc said:
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Click to expand...
Click to collapse
Let us know how it comes out and if there's problems, exactly where you're hitting the problem. I will try to help you out and later today I could probably get on team viewer and help you figure the drivers out.
Sent from my Nexus 7 using Tapatalk HD
Hi CharliesTheMan..
It's working. Had to use option 1 for the drivers.. but its updated and working
Thanks
Glad it worked out!
Sent from my Nexus 7 using Tapatalk HD

How to get a download URL for a Nexus OTA update

I always see people asking how to get the download url every time there's an ota, so I thought I'd post this where it can be found, rather than get lost on page 137 of the ota announcement thread like always seems to happen.
The following requirements must be met:
latest stock android (ota or factory image will do)
stock recovery (you will get an error if you try to install an ota with a custom recovery)
contrary to common belief, root does not matter!!
adb installed on your computer (installing the android sdk is the most common way to do this)
When you get the ota notification DO NOT download the update, and DO NOT reboot your phone!
plug your usb cable into your computer (not a front port)
open the command terminal (start>accessories>cmd or type cmd in the search under the start menu)
enable usb debugging (settings>development>enable usb debugging)
type the following line exactly as it's written then press enter
adb logcat
it will print out a whole bunch of text below this line in the command terminal.
start the OTA download.
copy and paste everything from the terminal into a notebook text document and attach it to your post if you can't find the url in this text yourself. someone will help you, for sure!
now it is safe to reboot your phone and install the update
It's OTA Update season for Nexus users...this thread needs to be up top so we can ensure we get the OTA link ASAP
Good luck, everyone!!
To the top!!!!
Looking forward to kit kat
Sent from my Nexus 4 using xda app-developers app
kitkat available for nexus4?
Sent from my Nexus 4
Wouldn't it make more sense to do it in this order:
1. Receive update notification
2. Start recording logcat
3. Begin download
4. Stop logcat
CMIIW
Sent from my AOSP on Mako using Tapatalk
sayogs said:
kitkat available for nexus4?
Sent from my Nexus 4
Click to expand...
Click to collapse
not yet.
For those that have root, by far the easiest way is to look in /cache before installing the update. The file will be there after you download it.
I'm on stock 4.3 with custom recovery and LTE radio .84 to get the 4.4 OTA I will need to return to stock recovery? I know applying the OTA I will loss LTE.
Sent from my Nexus 4 using Tapatalk
LowQue27 said:
I'm on stock 4.3 with custom recovery and LTE radio .84 to get the 4.4 OTA I will need to return to stock recovery? I know applying the OTA I will loss LTE.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
LTE mod has modified the system files.
You need to get the original system files.
Also just download the factory image from Google when it's available instead of the hassle with OTA.
Sent from my Nexus 4 using xda app-developers app
failly said:
LTE mod has modified the system files.
You need to get the original system files.
Also just download the factory image from Google when it's available instead of the hassle with OTA.
Thanks. I didn't think losing LTE would be this tough choice. (LTE vs. 4.4.) FML.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
//
I am sad! I still haven't gotten 4.4 on my Nexus 4.
Rody2k6 said:
I am sad! I still haven't gotten 4.4 on my Nexus 4.
Click to expand...
Click to collapse
Don't worry! Nobody did!
The OTA is now live, guys!! It's worth noting this post by Dan Morrill:
(In reference to clearing Google Play Services appdata in an attempt to force the OTA notification)
Dan Morrill 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.
----------
Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure nothing looks wrong before sending it to more. Then typically it goes to 25%, 50%, 100% over the course of a week or two.
What the percentages mean is that when your device checks in, it has a 1% chance (for example) of being offered the OTA. If it doesn't (randomly) get an offer, it will never get an offer until the next batch.
IOW, once your device checks in and gets turned down, that's it until the next batch. Mashing on the "check for updates" button just causes your device to check in again, and get automatically turned down again. Think about how that makes your device feel! WON'T SOMEONE PLEASE THINK OF THE PHONES?!
That said, once the new batch does start, hitting that button does give you a new roll of the dice -- but once. Since devices usually only check in for system updates every 24 hours (I think? Certainly on a many-hours basis) this can get you your shot sooner than it would happen on its own.
So, mash away. Just be patient, and mashing on it more often than once or twice a day isn't going to gain you anything.
Edit: also, keep in mind that this isn't first-come/first-served. You're not racing other devices to get your slot in the current batch, or something.
Click to expand...
Click to collapse
Source:
Android Police
Sorry, couldn't get adb logcat, but here's screenshot of /cache folder for OTA 4.4 https://twitter.com/caplang/status/403643070748446720/photo/1
No need of worrying.
Just download the update and flash it through adb sideload by going into recovery.
Sent from my GT-P3100 using xda app-developers app
thanks pal,it helps

New Nexus 6 with no available updates (stuck on old 5.1)

Hello guys. Just bought 2 days a go a new Nexus 6. Blue with 32Gb, unlocked.
Tottaly sealed, broke the seal myself, straight from Google.
But the phone says it is updated, and finds no new update. Im on LMY47D with Android 5.1 and I dont even receive 5.1.1
Tried factory reset without SIM Card, cleaning Framework and reboot without card, everything. To no avail.
Any idea what is going on? Shouldnt I get at least Android 5.1.1?
PS: I know I can sideload it, but still, something is clearly wrong, and I would like very much to sort it out.
Thank you very much.
Same issue here. Only I'm on 5.0 and can't find any update and I would prefer to not sideload already.
if you want your phone to check for an update, you have to be on WiFi. if in youre on network instead, itll always say up to date.
I'm on wifi. It still shows no update.
Same situation, on Wifi offcourse.
tryklon said:
Same situation, on Wifi offcourse.
Click to expand...
Click to collapse
Try a factory reset, then remove your carrier SIM and power up on WiFi. My bet is that your N6 will start churning through OTAs in sequence. Not sure that you will get all the way to Marshmallow 6.0, because that last OTA is still being rolled out.
Already did it... waste of time, no updates
If your not willing to simply download and flash the images from googles website, that is your choice... but there is nothing to do but wait.
Hi Guys I am in the same boat, brand new n6 on 5.0.1 and saying up todate . In uk and carrier is Virgin if that helps.
Mal
Something strange is definately happening with Google update servers...
same dilemma and same version as op..
Personally I was like you all. I got my nice shiny new n6 from verizon (free upgrade...) Got it home kept pressing check for updates. Tried all the clearing app data from frameworks and all that.
But in the end I sideloaded it. I documented it over on the OTA url post. It is not that hard, just need some time. If you don't want to wait it might be your only option.
Total time invested was probably 1.5 hours. Downloaded all the files to my laptop and started using WUGFresh.
Stop waiting and update manually? It's not difficult, you can even save your userdata by not flashing it. There are different (and possibly easier) ways to install an update other than sideloading. especially when you can skip all the OTAs and flash directly to 6.0.
No need for a tool kit and it won't take much longer than the time it takes for you to download the factory image and extract the files.
The point is that there might be something wrong with Google's OTA servers.
Or maybe something is wrong about these phones ?
Sent from my VS985 4G using Tapatalk
Thats my point exactly. What if theres something wrong with the phone?
Google should clarify why old updates are not being delivered... not even questioning 6.0, but 5.1.1
same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0
europeanpaul said:
same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0
Click to expand...
Click to collapse
Why not sideload 6.0
jdice said:
Why not sideload 6.0
Click to expand...
Click to collapse
Why is Google not delivering OTA updates to these N6 owners ?
Sent from my VS985 4G using Tapatalk
Because there were a couple of security updates between 5.1.1 and 6.0 (as far AS I remember on my N6) and because I want to be sure OTA works!
This issue is becoming more and more coomon. Lot's of people complaining on several forums about this issue.
At least its easy to see something is clearly wrong with the OTA's, since no one is getting any. There is people stuck on 5.0, 5.0.1, 5.1, etc whichever came preinstalled stays without updates.

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?

Categories

Resources