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.
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
Aside from Euphoria are there any others that currently have OTA updates? I ask mostly because there are some out there which I have not seen on XDA.
Sent from my Nexus 6 using Tapatalk
smodom said:
Aside from Euphoria are there any others that currently have OTA updates? I ask mostly because there are some out there which I have not seen on XDA.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Simple answer... None. Only stock can accept updates. Once you modify anything in the system or boot partition , game over for OTA.
obsanity said:
Simple answer... None. Only stock can accept updates. Once you modify anything in the system or boot partition , game over for OTA.
Click to expand...
Click to collapse
I'm not looking for stock OTA updates. I'm looking for delta updates OTA for the installed custom ROM. I work for a bank and need my phone to access the bank network with my RSA token app. I can't be down every time I flash an updated ROM. I'm essentially on call 7 days a week from 9-9.
Sent from my Nexus 6 using Tapatalk
smodom said:
Aside from Euphoria are there any others that currently have OTA updates? I ask mostly because there are some out there which I have not seen on XDA.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm using Cyanogenmod just for that reason. I don't know if the OTA updates are working in Settings yet, but using CyanDelta is so much better. Instead of downloading 434mb updates you download a 20mb update from cyanogen using the app. (In a nutshell This works by only downloading files that have changed, to save space.) You can even have it automatically flash other zips too, like kernels or mods etc. https://play.google.com/store/apps/...andelta&pcampaignid=APPU_A6O8VIA3hZ6DBI6PgsgO
smodom said:
I'm not looking for stock OTA updates. I'm looking for delta updates OTA for the installed custom ROM. I work for a bank and need my phone to access the bank network with my RSA token app. I can't be down every time I flash an updated ROM. I'm essentially on call 7 days a week from 9-9.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I don't understand the problem. Flashing an OTA update takes a few seconds in recovery. Flashing a full ROM.zip takes a few seconds more. What am I missing?
rootSU said:
I don't understand the problem. Flashing an OTA update takes a few seconds in recovery. Flashing a full ROM.zip takes a few seconds more. What am I missing?
Click to expand...
Click to collapse
He just wants ota updates on a ROM, also what Roms have that
cg14 said:
He just wants ota updates on a ROM, also what Roms have that
Click to expand...
Click to collapse
That, I know. What I am querying is his reason, as he said "I can't be down". It doesn't make sense. I'm assuming OP thinks he needs to spend lots of time re-setting up his phone if he updates using a full rom.zip, which is incorrect. So I am trying to understand the exact issue
rootSU said:
That, I know. What I am querying is his reason, as he said "I can't be down". It doesn't make sense. I'm assuming OP thinks he needs to spend lots of time re-setting up his phone if he updates using a full rom.zip, which is incorrect. So I am trying to understand the exact issue
Click to expand...
Click to collapse
Ahhhh OK, mabey slow internet? ie 100 mb =3 hours of download
That's what I'm stuck with out in the country
rootSU said:
That, I know. What I am querying is his reason, as he said "I can't be down". It doesn't make sense. I'm assuming OP thinks he needs to spend lots of time re-setting up his phone if he updates using a full rom.zip, which is incorrect. So I am trying to understand the exact issue
Click to expand...
Click to collapse
You are correct. I was under the assumption if no delta update was available and I flashed the newest version of the full ROM I would lose all settings and apps. Is there a downside to flashing a newer version on top of the older version of a ROM?
smodom said:
You are correct. I was under the assumption if no delta update was available and I flashed the newest version of the full ROM I would lose all settings and apps. Is there a downside to flashing a newer version on top of the older version of a ROM?
Click to expand...
Click to collapse
Ah OK I was hoping that was the case so I could set your mind a ease
So I'll start with why we have to wipe sometimes.
When we flash a ROM to the /system partition on a wiped phone, there are no settings. When you set up your phone, all your settings are stored in databases in /data partition (/data/data specifically). This is also where all your user apps settings and data are stored too.
The problem is, let's say you have ROM x. It has a display time out setting of 33 minutes. You set the display to this and it is stored in the relevant database. Then you flash ROM y. ROM y doesn't have a display setting of 33 (because let's face it, 33 is not common). So ROM y expects the database to say 5, 10, 15, 30 minutes. It doesn't know what to do with the entry of 33. Imagine this problem happening across multiple settings lots of things will break. Sometimes even, it wont boot.. So the problem really is that you have incompatible settings between some ROMs
Typically, I would always recommend wiping between major android versions. Also some custom ROMs will change a setting and this can cause problems
But in your ccase ultimately, there's no difference between a delta and a full ROM. If a setting is going to become incompatible, its going to happen whichever way you update.
I hope this helps somewhat and opens your choices..
rootSU said:
Ah OK I was hoping that was the case so I could set your mind a ease
So I'll start with why we have to wipe sometimes.
When we flash a ROM to the /system partition on a wiped phone, there are no settings. When you set up your phone, all your settings are stored in databases in /data partition (/data/data specifically). This is also where all your user apps settings and data are stored too.
The problem is, let's say you have ROM x. It has a display time out setting of 33 minutes. You set the display to this and it is stored in the relevant database. Then you flash ROM y. ROM y doesn't have a display setting of 33 (because let's face it, 33 is not common). So ROM y expects the database to say 5, 10, 15, 30 minutes. It doesn't know what to do with the entry of 33. Imagine this problem happening across multiple settings lots of things will break. Sometimes even, it wont boot.. So the problem really is that you have incompatible settings between some ROMs
Typically, I would always recommend wiping between major android versions. Also some custom ROMs will change a setting and this can cause problems
But in your ccase ultimately, there's no difference between a delta and a full ROM. If a setting is going to become incompatible, its going to happen whichever way you update.
I hope this helps somewhat and opens your choices..
Click to expand...
Click to collapse
This makes perfect sense. I suspected it might this way but without confirmation I couldn't take the risk. This is exactly the answer I was hoping you would come back with. I greatly appreciate your time. I almost didn't ask the question because I see so many similarly trivial questions asked and the OP gets bashed for it. Again, thank you! My flashing addiction just got much worse
smodom said:
This makes perfect sense. I suspected it might this way but without confirmation I couldn't take the risk. This is exactly the answer I was hoping you would come back with. I greatly appreciate your time. I almost didn't ask the question because I see so many similarly trivial questions asked and the OP gets bashed for it. Again, thank you! My flashing addiction just got much worse
Click to expand...
Click to collapse
No worries. We all don't know some tthings until we do, and asking is the first step!
PURE SHAMU has a delta update if that counts as OTA.
Hey there,
I got quite a serious problem. Since i updated to 5.1 my phone sometimes suddenly restarts, followed by a message which says "optimizing apps", which ranges from 30 to 150 apps. At first, it was no big problem, now it occures nearly every 10 minutes, so currently i can't really use my phone.
What i tried to do:
Factory reset, reflash 5.0 - 5.1.1 (every single image available)
The problem is still there.
Now my question, is it a Softwareproblem, which will be updated soon (should i try Android M (what about the warranty?))?
Or is it quite a serious hardwareproblem (i read somewhere that it could be because of overused RAM modules)?
I tried to use the searchengine, but i didnt find a specific thread in this subforum.
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
danarama said:
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
Click to expand...
Click to collapse
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Haabiii said:
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Click to expand...
Click to collapse
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Evolution_Tech said:
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
Click to expand...
Click to collapse
Thanks, I didn't know that.
Evolution_Tech said:
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Click to expand...
Click to collapse
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
Evolution_Tech said:
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Click to expand...
Click to collapse
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Haabiii said:
Thanks, I didn't know that.
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Click to expand...
Click to collapse
Personally, I'd boot to bootloader and do:
fastboot format cache
Evolution_Tech said:
Personally, I'd boot to bootloader and do:
fastboot format cache
Click to expand...
Click to collapse
Already done and i also reflashed the whole cache image. I hope the Android 6 Update will help solve my issues. The problem is, that i usually get really upset about little stuff like that just because i don't get why it's happening.
I updated monday evening to the Android M Preview, for now it only restarted once to, as it said, install a update (?), since then no reboot at all. It worked like a charm yesterday. I really hope the problem is fixed that way.
Just wanted to let you know if you have a same problem.
Just restored my N6 and am getting ready to sell the phone, I will be turning on the hotspot feature, and need to make sure that the phone does not notify or download OTA's - I do realize that's why we have our Nexus' but the person that I am selling it to can't sideload OTA's himself. He will be giving it to me periodically to upgrade and doesn't want to be bothered with the notifications... is there an easy way to do this? Thanks!
BL
blemert said:
Just restored my N6 and am getting ready to sell the phone, I will be turning on the hotspot feature, and need to make sure that the phone does not notify or download OTA's - I do realize that's why we have our Nexus' but the person that I am selling it to can't sideload OTA's himself. He will be giving it to me periodically to upgrade and doesn't want to be bothered with the notifications... is there an easy way to do this? Thanks!
BL
Click to expand...
Click to collapse
do you have root on it?
simms22 said:
do you have root on it?
Click to expand...
Click to collapse
I do not, just flashed fresh M. I am not opposed to rooting, what are your thoughts?
blemert said:
I do not, just flashed fresh M. I am not opposed to rooting, what are your thoughts?
Click to expand...
Click to collapse
well, if you do ever get an update notification, you can always long press on it then turn it off.
simms22 said:
well, if you do ever get an update notification, you can always long press on it then turn it off.
Click to expand...
Click to collapse
I do not want any notifications to appear...
Unless things have changed in Marshmallow, but I am pretty sure disabling notifications from Google Play Services disables the OTA update notification. I don't remember what else this gives notifications for, but there is probably something you may be blocking as well with this.
With Lollipop and above, all OTAs check for modifications before installing. Root and/or the changes you would need to stop the OTA notification would make it so you can't install an OTA. You would need to flash the factory images, then re-root and make the changes to stop the next OTA notification again. So this would be a bit more work on your end to install an update for the owner.
cupfulloflol said:
Unless things have changed in Marshmallow, but I am pretty sure disabling notifications from Google Play Services disables the OTA update notification. I don't remember what else this gives notifications for, but there is probably something you may be blocking as well with this.
With Lollipop and above, all OTAs check for modifications before installing. Root and/or the changes you would need to stop the OTA notification would make it so you can't install an OTA. You would need to flash the factory images, then re-root and make the changes to stop the next OTA notification again. So this would be a bit more work on your end to install an update for the owner.
Click to expand...
Click to collapse
Yeah - I am aware that OTA's check for mods... What about disabling the "SystemUpdateService" - I know that would require root, but has anyone else had success with this?
blemert said:
Yeah - I am aware that OTA's check for mods... What about disabling the "SystemUpdateService" - I know that would require root, but has anyone else had success with this?
Click to expand...
Click to collapse
Flash a custom stock based rom on it.
Sendt fra min D6603 med Tapatalk
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.