Database Develop

Force ota update

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.

[Q] Should I try Stock Andoroid before CM12?

My Nexus 6 has finally shipped! It should be here Friday!
This is my first Nexus and I have never rooted, unlocked, flashed, etc. any of my previous phones.
I have been doing a lot of research and have been considering running CM12.
My question is, should I run my Nexus 6 with stock android for a few weeks and then try CM12? Or should I just root, unlock, and flash CM12 as soon as I get it?
I know that if I wait then I will need to back up all my data because it will factory data reset but I am not worried about that... I understand it is easier to do it right out of the box because you don't have to worry about loosing anything but I can just back my info/apps up so that isn't a big deal.
Also, would you guys suggest something over CM12? Right now I am planning on using CM12 and just getting it setup how I like it then leaving it. I don't plan on always flashing and making changes but I might get sucked into it lol
Thanks everyone!

Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ

DebianDog said:
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Good point! I don't know if CM is on 5.1 yet. I just assumed it was but I will look into it. This is all new to me so thanks for pointing that out, didn't even think about that!
I won't know what version is on the phone until Friday. But even if it is on 5.0 I am sure it will notify me that 5.1 is ready to download as soon as I boot up the phone.

On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ

I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.

DebianDog said:
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Okay, thanks for the info!
Since I ordered my phone directly from Google, do I need to debloat? Or is that just for carrier versions?

mlin said:
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
Click to expand...
Click to collapse
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.

Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.

CFrance said:
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Click to expand...
Click to collapse
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.

Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.

gee2012 said:
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
Click to expand...
Click to collapse
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ

DebianDog said:
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.

My two cents. I don't think you've dealt with enough newbies. on another forum it was me and a group of others that would help people get their phones out of boot loops and soft bricks. I have literally helped hundreds of people get their phone back.
even if you look here on XDA you'll see people trying to flash the wrong files download files that are not even for their phone, are following a dated instruction or don't really understand how directories work.
Sent from my Google N6 on VZ

DebianDog said:
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
Click to expand...
Click to collapse
Thanks for the info! I actually had just downloaded this program over the weekend and was planning on using it once I do decide to root... which I am thinking will be as soon as I get the phone. lol other than that I think I am going to run it on stock for a while at first and wait until CM is on 5.1 for a while....

mlin said:
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Click to expand...
Click to collapse
Thanks! I am planning on rooting and unlocking right away for TB and maybe a couple other little things like lightflow just for fun. Being the nerd that I am, I have a feeling that once I start playing with the whole rooting, unlocking, and flashing stuff I am going to really enjoy it.

gee2012 said:
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
Click to expand...
Click to collapse
Thanks for the reply! I see what you are saying, I had already come across Wug's toolkit over the weekend and was planning on using that because it seemed so simple.
However, seeing how I still have two and a half days until my phone will be here, maybe I will look into the manual way a little more to decide which route I want to go.... Any suggestions on where to start? Threads, videos, etc?
Thanks!

Boot into download mode, Unlock bootloader, reboot, boot back into download mode, fastboot twrp recovery, boot into recovery, reboot via recovery and install su when prompted. When you boot into android you will be prompted to update su. You now are rooted. Only other thing I would think about when you first get your device is if you want forced encryption. You will be required to wipe SD data if you decide to go with non forced encryption.
I loved cm on my previous touchwiz devices because I like stock/asop style. I find cm has bugs in early os update releases. I would only install cm if i took advantage of themes which I don't.

CFrance said:
Any suggestions on where to start? Threads, videos, etc?
Thanks!
Click to expand...
Click to collapse
You can waste a lot of time while you're waiting for your phone in this thread http://forum.xda-developers.com/showthread.php?t=2992769
ROM Reviews (5.1) + Nexus 6 Hacking: NRT · Apps · Utilities [3.22.15]
Sent from my Google N6 on VZ

How to install monthly Nexus security firmware updates without starting over?

Usually when a new Android OS version is released, I'll just start over from scratch by manually flashing the seven image files using fastboot. I then install the unencrypt kernel/boot image and also root.
Now that these security updates are coming out every month, is there an easier way in my specific situation to install the update only without having to start from scratch every time like above?

Flash the system image only (if radio is different, flash that too). That won't overwrite your user data/apps
Edit: When flashing the system.img, flash the cache.img as well (to be safe)

Thanks. That is pretty simple. I wish I asked this a long time ago so I could avoided a lot of resetting EVERYTHING up all the time. 2 more clarifications if you don't mind...
1) Would this also work for point releases, like say if a 5.1.2 comes out, or would it be better to reflash everything in that case?
2) No other steps like clear cache or anything? Just flash those 2, reboot, and then I should be good to go?

Toaplan said:
Thanks. That is pretty simple. I wish I asked this a long time ago so I could avoided a lot of resetting EVERYTHING up all the time. 2 more clarifications if you don't mind...
1) Would this also work for point releases, like say if a 5.1.2 comes out, or would it be better to reflash everything in that case?
2) No other steps like clear cache or anything? Just flash those 2, reboot, and then I should be good to go?
Click to expand...
Click to collapse
It should work just fine for point releases. For major releases (like when Android M is released), I will probably flash everything, and wipe everything (including userdata), and start from scratch ! lol!
In theory, it should work find even for major releases, but I'd rather start with a clean slate - especially with the new permissions manager that is being added in this release. I'd rather not take any old incompatible apps thru' - but that's just me
Clearing cache is usually not needed. I've heard of instances where some users get stuck on the Google boot logo for some reason when booting for the first time. If that happens, clearing cache seems to help.
To be safe, it may be a good idea to flash the cache.img too. It takes a few seconds. Better safe than sorry. I'll update my earlier post.

jj14 said:
...
Click to expand...
Click to collapse
Huge thanks. This should make things a lot easier for me.

Is this the system update that just got pushed to my phone? It looks like a small update, like 26MB?
Mine tried to install and failed. My phone is stock, latest official version, never rooted, but the bootloader is unlocked and it is running the no force encrypt kernel, which I believe is probably what is causing the issue?
Only way is to restore completely to stock, take the OTA and then install the no decrypt?

I got the OTA today to upgrade to M from L- (on verizon) where can I Find that system image to flash- I tried sideloading the OTA and it didn't take.

caecusscius said:
I got the OTA today to upgrade to M from L- (on verizon) where can I Find that system image to flash- I tried sideloading the OTA and it didn't take.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images

SquireSCA said:
Is this the system update that just got pushed to my phone? It looks like a small update, like 26MB?
Mine tried to install and failed. My phone is stock, latest official version, never rooted, but the bootloader is unlocked and it is running the no force encrypt kernel, which I believe is probably what is causing the issue?
Only way is to restore completely to stock, take the OTA and then install the no decrypt?
Click to expand...
Click to collapse
I believe it's actually both of these things causing the OTA not to take. If anything, anything is changed from stock...no OTA. Bootloader unlocked, kernel, root, even just changing the build.prop (but you need root for that) would cause it to fail. I believe it checks every file and if anything in /system has changed, no OTA.
I've never messed around with the encryption pieces, but I'm wondering if you only flash the system.img (you'd need to re-root) if that would suffice or not as far as the update. You'd be flashing the entire system file instead of only the delta the OTA provides, but it's probably worth looking into.

Hmmm... Well, it takes 15 minutes to just wipe the phone and flash the new ROM with the toolkit, install my apps, copy my files over and set the phone up, so it isn't a big deal, I just want to make sure that I have the right version before I do that...
(LMY48M) That's the one that I want for the VZW N6, right?

I just use helium to backup my apps and everything. Even if I need to wipe it is a pretty easy restore process. I highly recommend helium backup.

hayzooos said:
I believe it's actually both of these things causing the OTA not to take. If anything, anything is changed from stock...no OTA. Bootloader unlocked, kernel, root, even just changing the build.prop (but you need root for that) would cause it to fail. I believe it checks every file and if anything in /system has changed, no OTA.
I've never messed around with the encryption pieces, but I'm wondering if you only flash the system.img (you'd need to re-root) if that would suffice or not as far as the update. You'd be flashing the entire system file instead of only the delta the OTA provides, but it's probably worth looking into.
Click to expand...
Click to collapse
Unlocked bootloader doesn't affect it, the customised kernel does though . But yes, you could just flash the system.img

T-Mobile says update rolled out. Is there a way to force?

According to this page
https://support.t-mobile.com/docs/DOC-18109#update_download
T-Mobile began rolling out 6.0 on October 5th. It states in the instructions to perform the update manually is essentially performing the android check for updates however I get no prompt to download the OTA.
Has anyone found a way to force the update? Possibly resetting the device?
Thanks!

Wait for the OTA, sideload when someone gets the link or flash the entire image (lose everything)...
Keep pressing that update button, but it does nothing ..

I'm literally going to beat a dead horse but why, are even Google's devices subjected to this ridiculous update process? If someone wants the OTA then they should be able to get it..

I am rooted on TMO and did a manual update to LYZ28K a while back. I clicked on Check for System Update just for kicks and it downloaded a 23.2 MB file. Any idea what that is?

JimSmith94 said:
I am rooted on TMO and did a manual update to LYZ28K a while back. I clicked on Check for System Update just for kicks and it downloaded a 23.2 MB file. Any idea what that is?
Click to expand...
Click to collapse
LYZ28M An update to Android 5.1.1

steve841 said:
Wait for the OTA, sideload when someone gets the link or flash the entire image (lose everything)...
Keep pressing that update button, but it does nothing ..
Click to expand...
Click to collapse
There are methods you can use when manually flashing to not lose data. (Don't flash userdata.img) be it through fastboot cmd directly, or through the use of a toolkit like Wugs.
OP, save yourself the headache and just download the update and fastboot it. It's a unified image so there is no need to wait for a "specific" version.

Peylix said:
There are methods you can use when manually flashing to not lose data. (Don't flash userdata.img) be it through fastboot cmd directly, or through the use of a toolkit like Wugs.
OP, save yourself the headache and just download the update and fastboot it. It's a unified image so there is no need to wait for a "specific" version.
Click to expand...
Click to collapse
Am I going to lose the ability to get future OTAs if I go this route? I've got an unlocked bootloader.... But not rooted and completely stock ROM.

slopokdave said:
Am I going to lose the ability to get future OTAs if I go this route? I've got an unlocked bootloader.... But not rooted and completely stock ROM.
Click to expand...
Click to collapse
You can still get OTA's as long as you're not rooted. Unlocked bootloader doesn't matter. Anyways, even if you did root, you can just manually flash the next update the same way. Takes less than 20 minutes to do.

Peylix said:
You can still get OTA's as long as you're not rooted. Unlocked bootloader doesn't matter. Anyways, even if you did root, you can just manually flash the next update the same way. Takes less than 20 minutes to do.
Click to expand...
Click to collapse
Thanks this worked perfect!

JoshRH said:
I'm literally going to beat a dead horse but why, are even Google's devices subjected to this ridiculous update process? If someone wants the OTA then they should be able to get it..
Click to expand...
Click to collapse
We do, it's called the factory images that google provides, we get the updates immediately (had 6.0 on release day), if you want to "wait" then it's only on you, the means are out there to get the updates right away, otherwise, gotta wait for the carriers. Android isn't and doesn't seem like it'll be like the iphone, independent from carriers as far as updates. Unless Google grows some nads and lays their foot down, this is how it will always be sadly.....once again, unless you just get the update and do it yourself like maybe 80% of the community here.

While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015. I'm not asking for Google to be like Apple, but for a Nexus device, a device designed to offer the latest and most up to date version of android, to be forced to wait for weeks for a proper OTA update is just ridiculous. I simply laugh at the android 6.0 articles that the tech blogs are releasing when 99% of the user base doesn't have access to the software.
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.

JoshRH said:
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015. I'm not asking for Google to be like Apple, but for a Nexus device, a device designed to offer the latest and most up to date version of android, to be forced to wait for weeks for a proper OTA update is just ridiculous. I simply laugh at the android 6.0 articles that the tech blogs are releasing when 99% of the user base doesn't have access to the software.
Click to expand...
Click to collapse
Nope, you don't have to erase your data to sideload an update (keep in mind that sideloading an OTA isn't possible if you have root, custom recovery or custom kernel). You don't even have to erase any data (provided that you don't need to unlock your bootloader prior to flashing) if you flash a factory image (even though it's nice to clean out the old system once in a while).
This was just a tangent, my real reason for replying follows:
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
Click to expand...
Click to collapse
Of course they can roll out the OTA to everybody at once, but they don't want to (and I agree). Check out this article (2 years old, yes, but the base principle still stands):
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/

JoshRH said:
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015.
Click to expand...
Click to collapse
You don't have to wait weeks. You have to potentially wait days, sometimes it is hours. Soon someone will snag the OTA url, if they haven't already, and then you can use ADB to sideload it without needing to wipe anything.
I haven't been following too closely, but I actually haven't seen anyone that has stated they have actually received 6.0 OTA yet. Some people posting they were, but they were getting one of the security fixes. Maybe they actually haven't pushed the OTA to the Nexus 6 yet for some reason?
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
Click to expand...
Click to collapse
It also has nothing with Google's ability to roll updates out to all of the Nexus owners. It is how they decide to stagger their updates out to people. They do this to make sure everything goes smoothly. If they put an update out that causes some sort of major problem, it would suck if it was in the hands of every single user, rather than just 1%.

The only update I received today was LYZ28M sadly. Not sure why they don't just have an app where people can download Nexus updates any time instead of OTA.

I got all the important stuff backed on Drive and most of the time I get all back even without backing it up
JoshRH said:
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015. I'm not asking for Google to be like Apple, but for a Nexus device, a device designed to offer the latest and most up to date version of android, to be forced to wait for weeks for a proper OTA update is just ridiculous. I simply laugh at the android 6.0 articles that the tech blogs are releasing when 99% of the user base doesn't have access to the software.
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
Click to expand...
Click to collapse

Won't stop nagging me to install system update!

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.