How to get rid of system update nag screen? - Moto X Q&A

I'm rooted and unlocked with 4.4.x XT1060 verizon
I don't want to take the OTA but i'm getting tired of being nagged to do so. I've tried moving the update file out of the 'cache' folder to somewhere else, but literally every time i turn on my phone I'm being nagged to upgrade.
Ideas?

peters4n6 said:
I'm rooted and unlocked with 4.4.x XT1060 verizon
I don't want to take the OTA but i'm getting tired of being nagged to do so. I've tried moving the update file out of the 'cache' folder to somewhere else, but literally every time i turn on my phone I'm being nagged to upgrade.
Ideas?
Click to expand...
Click to collapse
I believe using Titanium Backup to freeze the MotorolaOTA application is the usual advice. Older advice is to rename the OTAcerts.zip file in /system/etc/security but I don't know if that still works.

thanik you for the TBU freeze advice. i'll give that a try.

easier than that... go into settings>apps>all, scroll down to MotorolaOTA and untick the "show notifications" box. Done.

Thanks for this insight.

if you are rooted, to stop OTA's you can also rename 3C_OTA.APK and 3C_OTA.ODEX in either /apps or /privapp folder (using a file explorer with root abilities). Then you need to boot to recovery and clear cache..
When you are ready for OTA"s again, just rename them back, and reboot.

KidJoe said:
if you are rooted, to stop OTA's you can also rename 3C_OTA.APK and 3C_OTA.ODEX in either /apps or /privapp folder (using a file explorer with root abilities). Then you need to boot to recovery and clear cache..
When you are ready for OTA"s again, just rename them back, and reboot.
Click to expand...
Click to collapse
I did this but am still getting the OTA screen coming up. Maybe it's because the update file is already downloaded? If so, where does that hide. I've been looking but can't seem to find it. I've also been looking for the MotoOTA app to freeze that but that doesn't seem to exist anymore. I kinda wondering if I delete the update file, having the OTA.apk's renamed might stop it from trying again. Just not ready for the upgrade plus would rather have the full XML update instead of the OTA to be to fix any screw-ups I might have.

Yeah, same. The notifications can be dealt with using the "show notifications" step above. But the full screen pop-up reminder is harder to avoid. I'm surprised Moto is pushing this so hard.
What about uninstalling the Motorola update services update?
Sent from my XT1053 using Tapatalk

eldamobo said:
Yeah, same. The notifications can be dealt with using the "show notifications" step above. But the full screen pop-up reminder is harder to avoid. I'm surprised Moto is pushing this so hard.
What about uninstalling the Motorola update services update?
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Oddly enough, I only got one notification and then never again. Now it's just the full screen interrupt. It was really annoying when at a concert when trying to grab a video or two. Kept popping in and stopping the recording. If I wasn't at work I'd try to remove the update services. For now, I've gotten them frozen so let's see if it still nags like that.
I wish that once you say 'Maybe Later' at the first prompt it just leaves it to the update software menu under 'About Phone' instead of trying to force it.

dandroid213 said:
I did this but am still getting the OTA screen coming up. Maybe it's because the update file is already downloaded? If so, where does that hide. I've been looking but can't seem to find it. I've also been looking for the MotoOTA app to freeze that but that doesn't seem to exist anymore. I kinda wondering if I delete the update file, having the OTA.apk's renamed might stop it from trying again. Just not ready for the upgrade plus would rather have the full XML update instead of the OTA to be to fix any screw-ups I might have.
Click to expand...
Click to collapse
Did you boot to recovery and Erase cache?
When the OTA zip is downloaded, its stored in /cache which is only accessible if you are rooted. So booting to recovery and erasing cache will remove it from your phone.

KidJoe said:
Did you boot to recovery and Erase cache?
When the OTA zip is downloaded, its stored in /cache which is only accessible if you are rooted. So booting to recovery and erasing cache will remove it from your phone.
Click to expand...
Click to collapse
*This is on a Dev Edition if that makes a difference*
I do have access to /cache and it had the same in it as prior to clearing the cache, 3 folders (backup, lost+found, and recovery) and one text file (last_log under recovery.) This is a change from the last Moto I had. Granted that was the Droid X (damn them locked bootloaders) so older Android version. I've also looked for other ZIP's and the newest I can find is from the last time I had to update SuperSU.
I also cleared the davlik-cache on the second attempt but not sure if that would even come into play here. Unless TWRP is borked, cache has been cleared a few times now and now davlik as well.
But will say after freezing the Update Services, I haven't gotten the full screen nag again. Not sure what else is dependent on that but if it works, I'll keep it frozen for now and try breaking it more once home.

did you ever figure this out? My verizon dev edition moto x is driving me crazy with the OTA pop up...
fully rooted, unlocked over here, TWRP recovery.
I just renamed the OTAcerts.zip file in /system/etc/security and the 3C_OTA.APK and 3C_OTA.ODEX files in /system/privapp and rebooted.
I will see if that works...

So with a massive amount of thunderstorms last night I was without power (still am but at work so meh.) So I never got a change to try anything else. But I will report that freezing the Moto Update Services with TBackup worked perfectly. Haven't gotten a nag screen since. I'm just worried about other issues later down the line when trying to update other Moto services.

I'm not rooted, so for those not rooted, I'm using greenify on the update service. It also seems to shut the full screen nag off for now. That said, I think freezing would be better.

Not able to find update file to delete
Trying to get rid of nag screen for update MOTO X 2013 Sprint to version 212.144.2. Unchecked MotorolaOTA app, this did not work.
I am rooted, anyone know where to find file with Root Explorer to delete it? I don't want to accidentally install update.
On a side note, I am being asked to upgrade to v212.144.2 which I don't see anyone installing this OTA. BTW I am using my Sprint phone in South America

Related

What IS the scoop on "check for update is not available"?

Droid 4 running OTA GB 2.3.6 here in W. San Jose, CA
I get "check for update is not available at this time.". For many days now. LTE and Wifi (LTE is almost instant and Wifi takes 5 seconds or so).
I've looked at a zillion posts about "check for update is not available" and none have a definitive explanation. -- and all of them are from a couple of months ago or earlier. Didn't find anything recent.
I understand that the intended meaning of the message is that you can't connect to the update server.
I've read dozens of "solutions" but each one of them didn't work for somebody else so I've got to assume it was just coincidence -- resetting the phone, factory reset, renaming files, and so on. I *have* network connectivity. Data works great. Apparently I'm not able to connect to the update server? That shouldn't have anything to do with rooted or not, frozen or deleted apps, safestrap, etc. Fail to update once you get the download, sure. But I am expecting to be able to connect to the server.
Anybody know for sure?
I could imagine that the connect request might contain info identifying my particular phone model or ESN (would expect software version checks to be exchanged after connecting though). Something like that.
How does VZW roll out the updates? is it strictly by geographic region? or blocks of ESN? or what?
I have the "official" OTA download from here but figured if I side loaded it I might get out of sync or cut off from future OTAs? Failed to find a definitive answer on that too .
#eliot# from dialer then restart and try again... let us know
Sent from my DROID4 using xda app-developers app
---------- Post added at 01:33 AM ---------- Previous post was at 01:29 AM ----------
dbreezy187 said:
#eliot# from dialer then restart and try again... let us know
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
That will check in with Motorola's server btw kinda busy sorry for no further info
Sent from my DROID4 using xda app-developers app
Nope.
That's one of the myriad ones I read about (didn't recognize it right away though 'cause the post I saw it in had it in numbers instead of letters). One guy said it worked for him and the next guy said it didn't.
If you haven't tried it, as soon as you type in the final '#' you get a popup that says "Log Checkin initiated". So it does *something*but it didn't change my Check for update is not available... maybe whatever it is supposed to do never got into the server either.
lol, reminded me that I used to have a comprehensive list of all those codes for my Treo. Now I got yet another mission
[edit] dahaha, "there's an app for that". https://play.google.com/store/apps/details?id=cx.makaveli.androidsecretcodes&hl=en
Other then that Matt had to push the up date to them.. I believe on one post he actually said to get back to stock 100% wipe cache partition then he pushed the ota to said device... he was really nice about the being rooted over there... the forum is closed now so I can't check for more info.. id post over at Motorola owners forum
Sent from my DROID4 using xda app-developers app
I'll give it a bit more soak time I guess. I will try side loading the update before resetting/wiping. Reset/wipe will be my last resort. First choice is OTA.
Part of what prompted my post is that I'm unclear if the phased rollout is complete.
Is it the case that EVERYONE with a Verizon Droid 4 who is going to get the notification should have gotten it by now? Or is VZW still in the middle of the phased roll out for the Droid 4's? Got to wondering since googling for the Unavailable message only returned results that were at least a couple of months old. I figured it's possible that server access was/is part of the phasing mechanism but, then again, expected to find constant posting about that if it was. It seems that the mechanism of the roll out and the schedule is also a well kept super secret.
are you rooted? I had that same problem for days before I realized unrooting will fix that. Despite what a lot of trusted posters have said here and other forums, having root and no other changes will cause that. I used voodoo ota rootkeeper (free on market) to unroot and I had the OTA installed within 10 minutes (downloaded over wifi). it is recommended you update your binaries in your superuser app before using rootkeeper.
if you're not rooted then this doesn't apply.
---------- Post added at 02:57 PM ---------- Previous post was at 02:50 PM ----------
one more note, the stock recovery on the D4 after ICS update now tracks whether you are or you were rooted. Unrooting your phone no longer hides the fact that you were at some point rooted if a service rep goes into the stock recovery screens. this has been reported on other phones earlier in the year, now also true for D4.
No effect.
I've tried all combinations.
I've used the D4 utility only to root and install safestrap ( and used safestrap only to do a backup. nothing else)
Routine goes like this:
- in safestrap: uninstall recovery
- in settings->applications->manage applications: safestrap -> force close, clear data, uninstall
- in ES File Explorer: delete /system/bin/logwrapper
- in ES File Explorer: rename /system/bin/logwrapper.bin -> /system/bin/logwrapper
- power off, reboot
- in Titanium Backup: clear filters (ALL)
- in Titanium Backup: unfreeze all user and system apps
(the only "system" bloatware I've removed was uninstallable through the normal settings->applications -- I did not use TI for that)
- in OTA Rootkeeper: delete su backup
- in superuser: update su binary
- in OTA Rootkeeper: Protect root
- in OTA Rootkeeper: temp un-root
- power off, reboot
Try to check for updates with 4G LTE (i have great reception) - fails in a second or less
Try to check for updates with WiFi - fails but it takes 5 seconds or a little longer for a response/popup
Since you installed Safestrap you can't install the OTA update anyway, so not much of a bother that you can't get it pushed to you It'd fail trying to install as OTA updates require the stock recovery.
Root does not affect it. My wife's Droid 4 was rooted (by me) and many system apps frozen and the OTA was pushed to her the same day the SOAK testers were scheduled to get it (she was not part of the SOAK test, though I was). My sisters Droid 4 was rooted as well and she got the OTA pushed to her and installed a week or so later,
You'll have to uninstall the recovery Safestrap installs, and uninstall Safestrap. You'll also have to edit some files (logwrapper.bin or something like that).
for the ota
sbf 217 4.0.4 with rsd
SBF
http://sbf.droid-developers.org/cdma_maserati/VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml.zip
rsd
http://forum.xda-developers.com/showthread.php?t=1348587
dont forget to install the motorola driver first and enable debugging mode in development in your settings
i think they are here https://motorola-global-portal.cust...e-can-i-obtain-the-usb-drivers-for-my-device?
UPDATE: (lengthy with fairy tale ending)
Management summary: I am now on the OTA ICS (acquired over the air). following a wipe/factory reset
Called *611 tech support yesterday afternoon.
Got someone that sounded like they were located on this continent AND proficient. Always a good sign when they ask what the problem is right after getting your name instead of insisting on the 5 minute scripted generic question and answer form. Stated my problem was related to the system update for my Droid 4 and that I had been getting "check for update is not available..." for a few days now. My questions were "is that expected/normal?", "I understand roll outs are phased. What is the date the roll out is expected to be complete? -- last group has been notified or can pull it?", "If the persistent 'check unavailable' message is indicative of a problem then do they have possible fixes/known problem?".
He checked for the dates and said they expect to have completed the roll out by the end of September -- all Droid 4s should have it or have it available to them by the end of September. That the "check unavailable" did not necessarily indicate a problem but that it was not "normally expected" and more likely indicative of a problem on my end since it was persistent over that length of time. I said I felt better knowing they were still in the phased roll out and maybe I should just wait a while. We tried a soft reset (vol- and power) with no effect. He said he was afraid the next step would be to try a factory reset and advised I wait a while to see if the condition cleared. Went on to say that one effect/risk of the factory reset was that, if there was a software/system problem with GB preventing the OTA check it might also effect the factory reset -- if the phone had a problem coming up it might just pull the ICS update in order to come up from the reset. (Nice! he didn't just assume I would be OK with that following a reset). That I decided to wait I should definitely call back if it didn't resolve in 2 weeks. -- OK, that was a pleasantly refreshing encounter with tech support.
So I figured, fine, I haven't really tested a restore/recovery with Titanium backup and I've never gone through a factory reset so maybe now was the time. Had 2 alternatives. I could try using the D4 utility recovery using the official (same as the OTA) zip I have on my sd card or try the wipe/factory reset and see if OTA started working.
My thoughts (due to lack of any knowledge):
- Apparently once you get on ICS there is no reversion to GB (at least the actual kernel).
- Likely they have history at Galactic Headquarters of OTA and/or physical upgrades at factory or service centers for a particular phone.
- Obviously they check the phone's system version when you connect to the OTA server. Have to in order to determine if you even need an update. Additionally they would probably check if the version the phone reports is the version they expect it to be on -- I would, for technical and support reasons.
- So maybe if I went to ICS myself it might remove me from the OTA path for future updates. Not a big deal in my mind but, heh, why eliminate alternatives if you don't have to.
* reinstall safestrap and do a backup
* uninstall safestrap (uninstall recovery, uninstall safestrap apk, delete logwrapper and rename logwrapper.bin to logwrapper)
* unfreeze everything with Ti
* batch backup all user apps with Ti
* batch backup (green and yellow) system data with Ti
* temp un-root with Voodoo
* wipe/factory reset
It comes up in GB
(lot of activity follows which I didn't write down and can't quite remember)
Basically I waited for some market activity and whatnot to die down and tried update. Immediately said update available!
Cancelled that, got Ti (pro) back from the market, batch restored missing apps.
I have eset security (i don't know... I have it on my PCs so I figured I'd stick it on my phone too. Not that I think there is much in the way of virus for android yet). Eset has an urgent notification that it wants to be added as an administrator for the device so it can protect itself from installation of counterfeit Eset. I understand that but I'm wondering if maybe Eset maybe had something to do with my fail to connect to OTA. Probably not but that's the only thing that presented itself after the reset that looked like it could have been related.
OTA again to download the update -- deferred update after download.
Oh wait, forgot to batch restore system data. Did that, checked for sms messages. All good so I triggered the update.
Holy crap!!! I forgot to temp un-root! Figured the worst thing I could do was try to abort anything and just let it run and expect the update to fail.
It didn't fail. It completed just fine?
I go through the new phone screens far enough to sign into my google account.
Bunch of market update activity.
Restore missing apps with Ti
Restore system data with Ti
Then it strikes me that, sure enough, I'm still rooted. I did not restore root anywhere after the update.
I was rooted before the update (by accident) and still rooted after the update... Whats up with that?
So at the moment I'm a happy camper.
All my apps seem to have been effortlessly restored.
All my app settings seem to be intact.
All my system data seems to be intact with no migration issues.
I'm still (magically) rooted without doing anything.
standard101 said:
[/COLOR]one more note, the stock recovery on the D4 after ICS update now tracks whether you are or you were rooted. Unrooting your phone no longer hides the fact that you were at some point rooted if a service rep goes into the stock recovery screens. this has been reported on other phones earlier in the year, now also true for D4.
Click to expand...
Click to collapse
I am going to have to disagree with this. I was rooted and flashed. Ran the download and the install failed. I then did a factory reset (lost my flash and root as expected) and immediately ran the download. Install went off without a hitch. I even had a support rep from verizon and motorola on the phone during the install when i was doing it because i was so mad about the slow download. They were watching the install once it was done because they both stated that everything on my phone "looked good".
YeeP said:
I am going to have to disagree with this. I was rooted and flashed. Ran the download and the install failed. I then did a factory reset (lost my flash and root as expected) and immediately ran the download. Install went off without a hitch. I even had a support rep from verizon and motorola on the phone during the install when i was doing it because i was so mad about the slow download. They were watching the install once it was done because they both stated that everything on my phone "looked good".
Click to expand...
Click to collapse
I don't think that's what he was saying.
After you go to ICS it tracks (displayed in the recovery screen) if you are or were rooted.
Go into recovery and you will see a yellow "qe 0/0" left of the android.
ge 0/0 -- are not rooted/never been rooted
ge 0/1 -- are not rooted/been rooted sometime prior
ge 1/1 -- are rooted/been rooted
No idea if this was tracked before but not displayed in recovery. I suspect it was. On GB they were checking system files on boot and logging differences (I think I read they were comparing system file CRCs?). The list was getting logged to a qer...something log file (I forgot the file name and where it's at). I verified that. On my rooted GB there were mostly /xbin files and a couple of others listed in the log.
Now on ICS my recovery screen shows "qe 1/1".
Oddly enough I did a factory reset, forgot to temp un-root and my root persisted through the OTA update just fine. No idea why.
Since my root persisted through the update I was not able to check before re-rooting to see if it displayed "qe 0/0". My guess is this was always logged/stored and they just added the display to the recovery screen. I would find it almost inconceivable this information (and other) was not written to NVRAM since day one. Basic support/diagnosis information.

VS910ZVB: "LG Revolution gets bloat-removing OTA update"

From Android Central: "Updates, patches, and bug fixes are included in version VS910ZVB."
I don't have enough posts yet to link, so replace the " [dot] ":
androidcentral [dot] com/lg-revolution-gets-bloat-removing-ota-update
I have remove clock work so I can get the update. Been so long since I connected my phone to my pc to this, I will have to start from scratch. Time to search for all the how to's in here.
Haxcid said:
I have remove clock work so I can get the update. Been so long since I connected my phone to my pc to this, I will have to start from scratch. Time to search for all the how to's in here.
Click to expand...
Click to collapse
I'm rooted but without CWM (still have stock recovery). Can I simply defrost (freezing is all I've done) and get the update? Or do I have to do a hard reset to get back to full stock?
If hard reset to stock is required, any tips or techniques that you use to save time to get back to where you were? Thx.
Well I am updated and while I notice that all the extra Verizon apps are gone here is what I see...
1. Kindle, bing, slacker, tunewiki, and Verizon tones are all still installed and no option to remove them.
2, After I installed a dozen apps of my own, I still have 1gig of app space available.
3. The phone is remarkable faster and smoother.
I am going to see if they fixed the Exchange email client issue I was having...
Haxcid said:
Well I am updated and while I notice that all the extra Verizon apps are gone here is what I see...
1. Kindle, bing, slacker, tunewiki, and Verizon tones are all still installed and no option to remove them.
2, After I installed a dozen apps of my own, I still have 1gig of app space available.
3. The phone is remarkable faster and smoother.
I am going to see if they fixed the Exchange email client issue I was having...
Click to expand...
Click to collapse
Did you need to unroot? If yes how did you do it?
Thx
Mendel
mmp17 said:
Did you need to unroot? If yes how did you do it?
Thx
Mendel
Click to expand...
Click to collapse
Rooted should be ok, you may likely lose your root. It does not install with clockwork. I used lgnpst and imaged my phone, I then did a factory reset, felt like starting from scratch.
Verizon only removed a handful of apps. I am not sure it was worth the trouble. I have to root again so I can go back in and freeze or uninstall all the crap they left.
Id say in the de-bloat department they were a epic fail.
Haxcid said:
Rooted should be ok, you may likely lose your root. It does not install with clockwork. I used lgnpst and imaged my phone, I then did a factory reset, felt like starting from scratch.
Verizon only removed a handful of apps. I am not sure it was worth the trouble. I have to root again so I can go back in and freeze or uninstall all the crap they left.
Id say in the de-bloat department they were a epic fail.
Click to expand...
Click to collapse
I tried to do the update and it fails. I unrooted and it still failed if it is not worth it I'll leave it as it is. let us know if this update can be rooted.
Thx
Mendel
mmp17 said:
I tried to do the update and it fails. I unrooted and it still failed if it is not worth it I'll leave it as it is. let us know if this update can be rooted.
Thx
Mendel
Click to expand...
Click to collapse
yeah I returned my phone to stock with the lg tool and tot file, then did a factory reset, updated, rooted again, used titanium back up to uninstall the rest of the bloat Verizon missed.
While I do not know if the update breaks root or not, you can use the root tool in the dev section (esteem root v2) to root your phone. It works like a charm.
So was anything else updated? Trying to decide if it's worth my time to bother with. I am already running a zv9 that I seriously debloated and tweaked to where it's useable.
Sent from my VS910 4G using xda app-developers app
me too. I am running zv9 with root. And uninstalled lots of useless apps for me. I tried update, but failed.
wslguy said:
So was anything else updated? Trying to decide if it's worth my time to bother with. I am already running a zv9 that I seriously debloated and tweaked to where it's useable.
Sent from my VS910 4G using xda app-developers app
Click to expand...
Click to collapse
It will rebloat your phone. While they did patch some things, my phone did actually run smoother. I did have to root it again and un-install all the bloat they left, vzw tones, navigator, city id, kindle, slacker, etc...
No better battery life and not much of a performance increase. Id wait if you are happy.
keeps trying to update
I was planning on rooting & putting BrokenOut ROM on my revo when my contract ended. Then this OTA update came out, and I was worried that it would prevent that. So, I rooted the phone and put CWM recovery on and did a backup. As expected, the OTA update failed.
But, it hasn't given up. It tries and tries, about once a day. I hear my phone chirp, and it has rebooted and drained the battery, and shows at various times either the "update failed" screen, or the "updating in 2 minutes" screen, or recovery. When I get prompted to run the update, I defer it - but the deferal time doesn't correspond to when the reboot happens.
It's possible that the rooting and recovery are behind the problem, and not the update - but I suspect the update has something to do with it.
So, what I'd like to know is:
1) if I get the update, can I still use ROM Manager to change the recovery back to CWM, and still be able to flash BO on it?
2) to get the update, is it safe to just use ROM Manager to put the stock recovery on it, then run the update? I haven't done any debloating or other rooty stuff not mentioned above. I'd rather not lose data by reset, tot, etc.
3) can I fix my problem without getting the update? Maybe one of the options on the "update failed" screen? I'm not sure if I've selected only "OK" or only "Cancel" so far - or what those are supposed to mean.
4) do the security updates make zvb better than BO? (Does anyone here no what the security updates are?)
Thanks...
Broken out is based off of V9, so unless there are updates to the radio, you will most likely over-write most, if not all, of the updates.
As posted earlier, someone has rooted and installed cwm. But, someone wants to post up the update (you can rip it from the /data/local/tmp directory, iirc) I will try my best to update BO. Also, if someone can do a backup of the new update and post it up, (not the blob crap, the other one ) I'll rip the kernel and post a flashable zip. Maybe they did fix something. We will see.
I.M.famous XMAN said:
Broken out is based off of V9, so unless there are updates to the radio, you will most likely over-write most, if not all, of the updates.
As posted earlier, someone has rooted and installed cwm. But, someone wants to post up the update (you can rip it from the /data/local/tmp directory, iirc) I will try my best to update BO. Also, if someone can do a backup of the new update and post it up, (not the blob crap, the other one ) I'll rip the kernel and post a flashable zip. Maybe they did fix something. We will see.
Click to expand...
Click to collapse
Yeah, I figured current BO would undo zvb, that's why I was wondering which I should go with. The update downloaded several times, but I don't see anything in /data/local/tmp. Don't know if the download failed or just didn't persist. It hasn't tried to update for the last 30 hours or so. I'm not eager to encourage it at the moment.
I see that haxcid re-rooted, but nothing about re-cwm-ing.
can't find update file(s)
I.M.famous XMAN said:
...someone wants to post up the update (you can rip it from the /data/local/tmp directory, iirc) ...
Click to expand...
Click to collapse
I rebooted my phone, and once again it prompted me to install the update. I selected "defer" and then checked settings / about phone / software update / status which says "Package downloaded successfully".
However, /data/local/tmp is still an empty directory, according to ES File Explorer.
That's where the file was stored for v7, v8, and v9. Maybe they changed it for this update. IDK. I'll look into it. No worries. It's all good.
I think it gets downloaded to /cache/fota, but deleted once the process finishes failing. I will try to trigger it again and copy it before the phone reboots. I was not given the defer option this time.
---------- Post added at 01:31 PM ---------- Previous post was at 01:09 PM ----------
OrangeJoe said:
I think it gets downloaded to /cache/fota, but deleted once the process finishes failing. I will try to trigger it again and copy it before the phone reboots. I was not given the defer option this time.
Click to expand...
Click to collapse
Ok, I got it, I think. It's called ipth_package.bin
For now, I'm going to skip trying to attach it, and just give the link from which it seems to download:
https : / / pvzwmdmcdn.vzw.motive.com/firmware/LG_VS910_ZV9_TO_ZVB.bin
~47 MB
OrangeJoe said:
I think it gets downloaded to /cache/fota, but deleted once the process finishes failing. I will try to trigger it again and copy it before the phone reboots. I was not given the defer option this time.
---------- Post added at 01:31 PM ---------- Previous post was at 01:09 PM ----------
Ok, I got it, I think. It's called ipth_package.bin
For now, I'm going to skip trying to attach it, and just give the link from which it seems to download:
https : / / pvzwmdmcdn.vzw.motive.com/firmware/LG_VS910_ZV9_TO_ZVB.bin
~47 MB
Click to expand...
Click to collapse
Is it weird that my phone never prompted me for the OTA? I am on BO 2.0.1 with ZV9
dbeauch said:
Is it weird that my phone never prompted me for the OTA? I am on BO 2.0.1 with ZV9
Click to expand...
Click to collapse
Not really. I believe MT disabled the update feature from BO; hence the 'super fast' FC's at boot.

[Q] Rooted Moto X, OTA update today causing boot loop

Hi, I used PwnMyMoto-1.4.3-TMobile.apk to get root on my T-mobile Moto X.
http://forum.xda-developers.com/showthread.php?t=2444957
Today, there was an OTA update that downloaded and said it would install. Now the phone is stuck in a boot loop. It boots OK but about 45 seconds after loading it shuts down and reboots. I'm guessing its because the PwnMyMoto removed the stock recovery or altered it to be unable to install the OTA update. However I guess the phone still sees the downloaded OTA update and wants to install it, so it reboots the phone to try to install.
I can't post in the PwnMyMoto thread because I'm too new to XDA
I have froze the ota apk to try to prevent this
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
emerica243 said:
I have froze the ota apk to try to prevent this
Click to expand...
Click to collapse
what do you mean by this? Can you tell me how to do that?
jackashe said:
what do you mean by this? Can you tell me how to do that?
Click to expand...
Click to collapse
Freezing a particular app can be done using Titanium Backup. Its available for download on play store. Titanium Backup requires root permissions. Freezing an app will leave the app on your phone but it wont work cuz its frozen lol... the app wont be uninstalled. this way if you decide later that you need the app then you can just unfreeze it and use it.
OK, I have TB and I know it supports freeze. I didn't realize you could freeze the OTA capability as a separate program. However given that I already downloaded the update, its too late to freeze.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
FSRBIKER said:
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
Click to expand...
Click to collapse
Yup I almost unlocked the boot loader but instead I was able to flash stock recovery. I wish android itself was smart enough to not try to install OTA when recovery was gone. I finally read through the jcase thread and I think I might have been able to delete the downloaded OTA by running:
Code:
fastboot erase cache
fastboot erase userdata
But I didn't try that. I also don't know what exactly that would have erased.
I will certainly look into a SquareTrade warranty!
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
so if we freeze updater and ota, we should be covered?
not sure about the other suspect apk with is fota.apk. I rename otacerts.apk as well. I may be a little paranoid about this but bricking is definitely not an option
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
jackashe said:
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
Click to expand...
Click to collapse
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
shane1 said:
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
Click to expand...
Click to collapse
I did try rooting again using PwnMyMoto-1.4.3-TMobile.apk but it failed to install (since one of the exploits it used is patched)
I have t-Mobile but how would I get to the cache? My phone would boot for about 45 seconds and in that time-frame I could adb shell into the phone but could not find the path for the OTA update. Do you mean it would be in /cache/some-build/ or so?
Yes in cache and you would have to attempt from a PC , which might not have been possible because the phone kept rebooting. Also I am sry for your loss
Would ota root keeper do anything for us?
Sent from my XT1058 using XDA Premium 4 mobile app
IncredibleHulk6 said:
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
Click to expand...
Click to collapse
Can you please tell me how you did this? Thanks in advance
Perhaps this thread helps http://forum.xda-developers.com/showthread.php?p=46179190#post46179190
Erk, after getting into the same post-Root update loop, I flashed back to stock using the recipe here: http://forum.xda-developers.com/showthread.php?p=46175635&postcount=8
I now have 13.9.0Q2.X-116-X-17-51 installed.
When I go to System updates to update to the OTA update 13.0Q2.X-116-X-17-54, I get told that I am already updated to the latest version.
Any help would be much appreciated!
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
manfly9884 said:
Can you please tell me how you did this? Thanks in advance
Click to expand...
Click to collapse
You have to make sure you have downloaded & installed the Android SDK and the latest Motorola Android drivers to your computer. On your phone, shut it down before it has the chance to re-enter the boot loop cycle. Then press the down button simultaneously with the power button for a few seconds and release the down button a split second before releasing the power button. This enters the bootloader (you may have to try it a few times to get it). Plug your phone into the computer and open a command prompt on the computer; type "fastboot erase cache", hit enter, type " fastboot erase userdata" and hit enter. You'll see confirmation in the command prompt and your phone will reboot as factory reset.

[Q] New System Update

I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
ace_case said:
I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
Click to expand...
Click to collapse
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
skeevydude said:
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
Click to expand...
Click to collapse
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
ace_case said:
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
Click to expand...
Click to collapse
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
palmbeach05 said:
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
Click to expand...
Click to collapse
I'd say it's more like posting on Craigslist that you're going on vacation and then leaving all the doors open with your debit/credit card on the coffee table. It's a pretty serious bug, and according to wikipedia, 1.5% of the most popular 800,000 websites are still vulnerable to the bug, not to mention running a sideloaded app or connecting to a malicious website.
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
Flashing back to completely stock may be the easiest way to get the update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
If you flash the OTA update manually using something like Philz recovery, you can see the progress on the screen and where it stops updating. For me, it kept hanging on updating the smartactions.apk, which was because I had previously (long time ago) merged updates of the app to my System partition (along with a few other apps that were updated). This will mess up any attempt to do an OTA update, because your "stock" ROM is no longer stock.
I ended up having to flash back to the real stock with Mythtools, then install the OTA zip manually.
If you can't find the zip in your cache, you can download it directly from this post (thanks @skeevydude): http://forum.xda-developers.com/showpost.php?p=52657363&postcount=13

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.

Categories

Resources