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 .
Related
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
Android 4.4.3 Force Update Procedure found :
Disable Google Services Framework and Restart the Phone...now clear cache and Enable the framework and check for the Update.....!!
It's been known for a while.
Also, don't do it... http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
Sent from my Nexus 4 using Tapatalk
Force it but after you will have many problems to resync the phone whit playstore!
I have always forced it this way and have never had any problems with anything afterwards. I just have to accepts G Play terms and conditions after I do it. It might be something Google engineers don't want us doing. I think this process generates a new ID for the phone, which Google might not want.
It doesn't make a difference in getting ota. It is a wasted effort.
raul6 said:
It doesn't make a difference in getting ota. It is a wasted effort.
Click to expand...
Click to collapse
You're wrong, it does. I have always gotten my OTA doing this.
I was also wrong though. I just noticed that my Facebook messenger notifications aren't getting through. So don't do this people, flash the factory images without -w flag instead.
TheNikkoMan said:
You're wrong, it does. I have always gotten my OTA doing this.
I was also wrong though. I just noticed that my Facebook messenger notifications aren't getting through. So don't do this people, flash the factory images without -w flag instead.
Click to expand...
Click to collapse
The syncing problem will resolve itself in a matter of hours. There is no permanent damage done.
Is it really that serious to get the update from OTA with zips and images and roms floating all over the place. We make too much of an incremental update as well..Just my opinion
Just tried it didn't work. Not too fussed about the effects as it only lasts for a few hours.
playya said:
Is it really that serious to get the update from OTA with zips and images and roms floating all over the place. We make too much of an incremental update as well..Just my opinion
Click to expand...
Click to collapse
I did it because the micro USB port is broken, I'm unrooted and have stock recovery (bad situation).
Also, it does work. You just have to repeat the process until it works, it never works the first time.
How can I disable ota notifications here? I am rooted.
Or what could i edit in the build.prop that would show I'm up to date? The build info?
Hello? Is this thing on? Lol anyone know how and also avoid any wakelocks?
Or just update the phone?
You can press and hold on the notification, tap app info and tick hide notifications from this app. Alternatively, you can install an xposed module called notify clean if you have xposed. Incredibly useful.
lolcakes203 said:
You can press and hold on the notification, tap app info and tick hide notifications from this app. Alternatively, you can install an xposed module called notify clean if you have xposed. Incredibly useful.
Click to expand...
Click to collapse
xposed doesn't work with ART (the runtime in Android 5.0) so this isn't a solution
You are absolutely correct, that completely slipped my mind. Sorry!
Take take the easy and just upgrade
xxfwmxx said:
Take take the easy and just upgrade
Click to expand...
Click to collapse
Not so easy if you are rooted or anything modified.
Actually it is as I did so to go from 5 to 5.0.1 I was rooted, had twrp, elementalx kernel, and decrypted. Instead of flashing the entire factory image you just flash the needed images. That's what I did and didn't loose any data. There are a few posts here on how to do it. Here is one http://forum.xda-developers.com/nexus-6/help/5-0-1-wiping-t2975382
xxfwmxx said:
Actually it is as I did so to go from 5 to 5.0.1 I was rooted, had twrp, elementalx kernel, and decrypted. Instead of flashing the entire factory image you just flash the needed images. That's what I did and didn't loose any data. There are a few posts here on how to do it. Here is one http://forum.xda-developers.com/nexus-6/help/5-0-1-wiping-t2975382
Click to expand...
Click to collapse
I understand how to do it. I've done it many times before. But the op asked how to get rid of the notification. For whatever reason, some people may not want to take the update, or are modified & don't have time to restore stock, or will be away from their PC over the holidays. It would be useful to know how to disable the ota notification until we have time/ equipment to return to stock or flash images.
What I have done on my n5 is go to /etc/security & rename otacerts.zip to otacerts.zip.bak & reboot. Then try to take the ota & it will immediately fail verification. Voila, no more ota notification. I think this will last until a reboot & then it will try to verify again.
I'm not sure of a more permanent solution.
Thanks Stumpey. Yea haven't had the time yet. Still setting my phone up and haven't even backed up in Tb or Twrp yet. Plus this update is a relatively small one so not in a hurry to manually unroot-update-reroot.
Anyway just turned the notification off like another poster suggested and that's good enough for now. Didn't even realize you could do that.
So I'm getting my new Fire tablet tomorrow, got it at the $35 sale...
Planning to not allow it to connect to WiFi till I can load Google Play and disable OTA using the script given here (already did it on another one and it worked great) so it doesn't get 5.1.1.
Two questions:
1. How can I tell if it's running 5.0.0 or 5.0.1 (without doing the software update check obviously...)
(also not sure how to see it once OTA is disabled, any other place it shows up?)
2. If it's on 5.0.0. can I sideload the 5.0.1 image using ADB, seems that I should be on that version to get Google Play to work OK.
Thanks
I think Amazon is shipping these new ones with 5.1.1, but if they don't, just go to the latest 5.0.1 in RootJunky's video. After that is done, just skip the part in Setup which requires you to connect to Wi-Fi, disable the OTA Apks, and connect to Wi-Fi. You should be set from there, and you can do whatever modifications you want.
Vlasp said:
I think Amazon is shipping these new ones with 5.1.1, but if they don't, just go to the latest 5.0.1 in RootJunky's video. After that is done, just skip the part in Setup which requires you to connect to Wi-Fi, disable the OTA Apks, and connect to Wi-Fi. You should be set from there, and you can do whatever modifications you want.
Click to expand...
Click to collapse
Any reports of people receiving Fire's preloaded with 5.1.1?
First things first... Don't connect to wifi and disable ota updates.. Root.. Flash cm12.1 and never look back!
@87racer would love if you could capture the 5.1.1 update for us!
tuckerwagner said:
@87racer would love if you could capture the 5.1.1 update for us!
Click to expand...
Click to collapse
thanks @tuckerwagner, looks like we @p0lt just posted one for us. downloading now, should help us discern what happens during the 5.1.1 upgrade and maybe recover our bricks.
87racer said:
thanks @tuckerwagner, looks like we @p0lt just posted one for us. downloading now, should help us discern what happens during the 5.1.1 upgrade and maybe recover our bricks.
Click to expand...
Click to collapse
SWEET! I'd help but in don't know where to even start. Good luck!
The update from 5.0.1 to 5.1.1 isn't instantaneous. The device has to download the new version before installing it. Check your version and if it starts to download 5.1.1, just turn off your wifi. It will say "Download paused." Then disable OTAs or flash one of the two ROMs.
That said, it is highlyunlikely that you would get one that is still on 5.0.0. The one I got last week was already on 5.0.1
register it first so you can contact support for a replacement if it is "defective"... for my $35 fire all you had to do was enable adb, reboot to fastboot, and continue from there. Didn't mess with the fire OS at all except for registering the device.
levytom said:
So I'm getting my new Fire tablet tomorrow, got it at the $35 sale...
Planning to not allow it to connect to WiFi till I can load Google Play and disable OTA using the script given here (already did it on another one and it worked great) so it doesn't get 5.1.1.
Two questions:
1. How can I tell if it's running 5.0.0 or 5.0.1 (without doing the software update check obviously...)
(also not sure how to see it once OTA is disabled, any other place it shows up?)
2. If it's on 5.0.0. can I sideload the 5.0.1 image using ADB, seems that I should be on that version to get Google Play to work OK.
Thanks
Click to expand...
Click to collapse
Update:
Got the Fire tablet and this is what I did if you want to try the same:
1. Turned on the device
2. Skipped configuration process when it asked me to connect to WiFi
3. Setting->Devicve options->System update confirmed I'm on 5.0.1 (yey) it can't update obviously since WiFi is not connected, so I'm safe for now
4. Use the 1-click script to install google play, remove ads (http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
5. Disable OTA using the same script (menu option 3)
6. Reboot
7. Install Gmail (cause later there's a stage where native email app doesn't work...) and email myself the pre downloaded fire launcher (http://forum.xda-developers.com/attachment.php?attachmentid=3528797&d=1446499184) which will fix it
8. Replace launcher, using the launcher replace script (http://forum.xda-developers.com/amazon-fire/general/alternative-launcher-one-click-script-t3239966)
9. install fire launcher apk (because otherwise some stuff doesn't work) - and choose not to use it when clicking the home button
What's left?
1. Didn't root <any reason to root?>
2. Write access to SD card is reported not to work, didn't try that yet... maybe by the time I need it someone will solve it
3. Hope that OTA won't happen and disabling worked... (something is probably done right, because if you try to check for update it says that updates are disabled...) hopefully that's good enough...
4. Say thanks to sd_shadow, ChrBeck, and Awesomeslayerg for the information they provided as well as many others participating in this forum... so Thanks.
levytom said:
What's left?
1. Didn't root <any reason to root?>
2. Write access to SD card is reported not to work, didn't try that yet... maybe by the time I need it someone will solve it
3. Hope that OTA won't happen and disabling worked... (something is probably done right, because if you try to check for update it says that updates are disabled...) hopefully that's good enough...
4. Say thanks to sd_shadow, ChrBeck, and Awesomeslayerg for the information they provided as well as many others participating in this forum... so Thanks.
Click to expand...
Click to collapse
1. Personal choice, but ad blocking alone makes root essential for me.
2. Oh and the SDfix app on Play store needs root for that matter... https://play.google.com/store/apps/details?id=nextapp.sdfix
3. You can now flash the 5.1.1 update as seen in the http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594 thread so wouldn't need to worry about the current update at least.
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.