I just got a prompted notification that 2.3.2 system update is now downloaded and verified in my phone. Just need to go ahead and ok the install/update on my phone. Not sure if most or all are getting this?
Should I? LOL
more info:
"Android 2.3.2
601kb
This system update from Google contains important bug fixes."
Go for it.
This is probably the update that includes the major SMS bug fix. Samsung posted to their official twitter account that and update to address that is coming very soon.
It looks like v2.3.2 is the one.
Funny thing though, I never had problems with the SMS bug. I have sent/received SMS (2k+). And when I got the notification, I just pulled the battery off to check my S/N to register in the Samsung website. LOL
Is there any other bug/fixes with this updates other than the SMS bug?
If you're rooted, you might want to wait and see if it's safe to do it (ie., doesn't break root) unless you're confident on how to get it back. The last update screwed with Recovery and gave some people some slight grief for a short period.
Just rooted
Wouldn't you know it? After I just finish rooting using the step by step guide, the first thing that pops up is that there is an update to install. So my question is, will installing this update kill my root? Or any other negative consequences for my newly-rooted SNS if I update to 2.3.2?
Just rebooted after update, seems that at least the browser got some kind of lagfix, for example www.n4g.com.
"Your system is currently up to date."
hmmm.... what about people on Custom ROMS ?
i check the Settings > About > System Updates
and there's nothing it says
"Your system is currently up to date."
Without thinking I chose to install it while being rooted and not backing up. After it rebooted it froze (when it couldn't find a recovery I'm guessing.) I pulled the battery, let it reboot, and I'm still 2.3.1 and rooted. Just FYI
AllGamer said:
hmmm.... what about people on Custom ROMS ?
i check the Settings > About > System Updates
and there's nothing it says
"Your system is currently up to date."
Click to expand...
Click to collapse
Often one have to wait untill the devs implement the update into the custom rom.
Generally once you're on a custom rom, you're best to wait for the rom dev to give you guidance.
treodoc said:
Wouldn't you know it? After I just finish rooting using the step by step guide, the first thing that pops up is that there is an update to install. So my question is, will installing this update kill my root? Or any other negative consequences for my newly-rooted SNS if I update to 2.3.2?
Click to expand...
Click to collapse
Not sure without being able to open the update file and see what it actually does.
IF you're going to try it. Have a nandroid backup made of your system as it is right now, and have a copy of CWM recovery handy to reflash via fastboot.
You'll probably have to re-root if you can even get the OTA to stick (like the one post above that says it didn't...)
so, back to stock recovery before update?
swype
FYI, swype did not work after update, had to reinstall, now works fine.
How do I get this update?
Made a check for updates in my NS, and I got none.
Still in 2.3.1 here.
Would those of you who get it, if you have a chance, please run the logcat on your phone BEFORE updating and try to catch the url so we can get a manual link for it:
in order to extract the url for the system update, we need to run alogcat from the market, then when the update notification appears look in your logs for a url that says something like clients.google . You can install alogcat, then set filter to clients.google
Click to expand...
Click to collapse
Phantom1275 said:
How do I get this update?
Made a check for updates in my NS, and I got none.
Still in 2.3.1 here.
Click to expand...
Click to collapse
You can try to check in. *#*#2432546#*#*
it just says that checkin succeeded on notification bar and that's all... No updates...
How to root 2.3.2. Are there any differences ? what clockmod recovery use ?
krohnjw said:
You can try to check in. *#*#2432546#*#*
Click to expand...
Click to collapse
That's the check I have mentioned.
Still nothing. Guess I have to wait.
Trinitronik said:
it just says that checkin succeeded on notification bar and that's all... No updates...
Click to expand...
Click to collapse
It's going to roll out slowly, just like the 2.3.1 and Market updates did. I don't think all the checkins in the world will speed it up by any significant amount.
What we impatient types need is someone who is offered the update to grab the url so we can just manually download it.
Udaw said:
How to root 2.3.2. Are there any differences ? what clockmod recovery use ?
Click to expand...
Click to collapse
No one knows yet! Have to get it to see what it changes (breaks).
Related
I have a rooted N1 running 2.2 with no mods installed. I dont want to upgrade to the latest 2.2.1. How do I get rid of or disable the system update available notification? Cant find any settings anywhere to turn it off.
Why the opposition to FRG83 out of interest?
Rusty! said:
Why the opposition to FRG83 out of interest?
Click to expand...
Click to collapse
1. I used the 1 click root
2. I have not found any info on why I need 2.2.1
3. I tried 3 times to install the update with not success
You can't turn off the update notification. You need to modify the build.prop for that.
You can't install update if your system isn't stock.
For me the update notification stopped after I ignored it for 1 week.
Be warned though - my N1 became super unstable at that point (2-3 crashes per day).
I finally gave in and upgraded - did not see any improvements. Battery seems slightly worse. Rooting was easy. And has crashed once. (Compared to NOT a single crash in 4+ months before)
nexusdue said:
did not see any improvements
Click to expand...
Click to collapse
This seems to be the consensus...at least among those I know with Nexus Ones. I'm on CM6 and never received the OTA notification..and I have no intention of updating to 2.2.1....ever... unless it's a CM nightly, but I'm happy with CM6 stable so I'm sitting pat.
So......It looks like I either update my phone, install a rom or get use to pushing "install later" every time I go to use it?
bhds said:
So......It looks like I either update my phone, install a rom or get use to pushing "install later" every time I go to use it?
Click to expand...
Click to collapse
One more thing you can try: Download quickboot from the market. When you get prompted to install the update again, dismiss it and then reboot your device using quickboot. Seems to make it go away, for few days anyway. Check out post 117 on this page and you can read backwards from there and see what I'm talking about.
http://forum.xda-developers.com/showthread.php?t=791124&highlight=quickboot&page=12
Old MuckenMire said:
One more thing you can try: Download quickboot from the market. When you get prompted to install the update again, dismiss it and then reboot your device using quickboot. Seems to make it go away, for few days anyway. Check out post 117 on this page and you can read backwards from there and see what I'm talking about.
http://forum.xda-developers.com/showthread.php?t=791124&highlight=quickboot&page=12
Click to expand...
Click to collapse
I'm currently using this method to "hide" the update prompt. I haven't been keeping close track, but it's seems to have hidden the message for almost a week. I'm trying to decide if I want to root using the new SuperOneClick method (http://forum.xda-developers.com/showthread.php?t=803682), but I want to make sure it's as painless as it sounds. Hopefully, it's just 1) let the phone update to 2.2.1, 2) reboot, 3) run this OneClick method, and I'll have superuser back without having to reinstall my root apps or set them up again.
Anyone know if this is all that's needed to root after letting the phone upgrade to 2.2.1?
bhds said:
So......It looks like I either update my phone, install a rom or get use to pushing "install later" every time I go to use it?
Click to expand...
Click to collapse
I just installed 2.2.1 and used the SuperOneClick method to root the phone again. I had to turn the phone off, run the program, and then boot the phone for it to work. I suggest you try this method. It couldn't be much simpler.
As the title says. I'm currently using 1.83 via SBF flash. Today I received a notification to download and install 1.83 OTA. Kinda strange.
My only thought for cause could be that I'm using gingerblur and it changes the build.prop to look as if I'm using 1.57.
Anyone else getting this?
You can use TiBU to freeze updater. there are several 2 post threads that say the exact same thing..
Must have been in threads that weren't created to address this specific issue and didn't have a title to reflect the same
Sent from my MB860 using XDA Premium App
This happened to me also, so today i flashed back to 1.2.6 and redid everything back to 1.8.3. I had Greyblur installed over 1.8.3 priviously and i was getting that pusshed to me so i redid everything and used the 3.1 version of gingerblur and its perfect.
http://forum.xda-developers.com/showthread.php?t=1053057
http://forum.xda-developers.com/showthread.php?t=1064871
WiredPirate said:
http://forum.xda-developers.com/showthread.php?t=1053057
http://forum.xda-developers.com/showthread.php?t=1064871
Click to expand...
Click to collapse
neither one of these are relevant to this thread. If I had asked "How do I make it stop asking me to update?" then, yes, you would be correct. But I didn't, so you're not.
If you re-read the OP, you will notice that I am inquiring if anyone else ALREADY has 1.83, but yet is STILL being pushed update notifications for.... 1.83.
You used the 1.5 gig SBF file for 1.8.3 correct? I'm GingerBlurred 3.1 on the 1.8.3 and it's fine for me.
Typically when I SBF I go at least one update back and do the OTA update instead.
That's right. I did the full 1.87 SBF, not the little upgrade version
This is happening to me as well... BUT I flashed 4.1.5.7 then did the OTA update. After that I rooted with Gingerbreak and enabled sideloading with Gladenable. Anybody have any idea other than TiBu to fix this issue?
I had this same problem. On a whim, I decided to let it try and apply the update. It rebooted, froze. Pulled the battery, put it back in, restarted. Booted to home screen, said "update failed!" Then I went to check for updates (Settings->About Phone) and it said up to date.
I tried allowing the update. It now says "An update is currently being downloaded. You will be notified when the download is complete" When I click the "OK" box it waits awhile and then says "Failed to download update. The update package is not available at this time. No further action is required."
Now a new question... Can anyone here tell me what to freeze in TiBu to stop this "failed to download update" message??
Thanks!
holtenc said:
neither one of these are relevant to this thread. If I had asked "How do I make it stop asking me to update?" then, yes, you would be correct. But I didn't, so you're not.
If you re-read the OP, you will notice that I am inquiring if anyone else ALREADY has 1.83, but yet is STILL being pushed update notifications for.... 1.83.
Click to expand...
Click to collapse
Okay I see you wanted to know if anybody else was experiencing the issue but had no desire to resolve it. Gotcha.
vertigocreative said:
I tried allowing the update. It now says "An update is currently being downloaded. You will be notified when the download is complete" When I click the "OK" box it waits awhile and then says "Failed to download update. The update package is not available at this time. No further action is required."
Now a new question... Can anyone here tell me what to freeze in TiBu to stop this "failed to download update" message??
Thanks!
Click to expand...
Click to collapse
Freeze 'updater'.
Okay... thanks... done... Now is there any good reason I should want to actually try to fix the problem (maybe by re-flashing?) or am I ok just masking the problem with the freeze?... or is it really even a "problem"?
Sorry if these are stupid questions. I really appreciate the help you guys give here.
Hi guys, after a 6 months period with HTC Wildfire S, i decided it was time to upgrade my device, so here i am, a newbie Nexus S user.
The first things i did with my new toy were unlocking the bootloader, gaining root permissions and installing CWM.
But i noticed that Market isn't updating, it's stuck to THIS version (i think it's 2.13)
Has this anything to do with root and cwm? Or it's just a matter of time and i'll eventually get the update?
Same thing with firmware: at the moment i'm running 2.3.3: looking for updates, and even using the *#*#checkin#*#* code, provided the same result: no FOTA available. Is this due to the root+cwm or i just need to wait?
I know this has already be discussed in the faq, but i find them quite confusing.
I mean, i know i could do a manual update, but i'd like to know whether if i'll ever receive a fota update or if i've lost this chance after root.
Q: I'm rooted with Clockwork and can't install the OTA! I updated to 2.3.1 and lost root! What gives?
most of the time, official OTAs will not install through custom recoveries because of their tendency to break root or restore things like the stock recovery. Also if you've made any modifications to the system files such as replacing the default Mms.apk(messaging) with the custom Black Mms.apk found in the Themes & Apps section, or deleted any .odex files from the system partition, it will not install. The easiest way to update to 2.3.1 is to flash a custom rom such as one of the custom ROMs or use the 2.3.1 Stock NANDROID backup found in the development section. And yes, 2.3.1 "broke root." To regain it, simply follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=884499 (All credit goes to the original author(s) of the linked thread!). The aforementioned procedure is only needed on the Stock Nandroid Backup, not any of the custom ROMs.
Click to expand...
Click to collapse
Thanks in advance for the answers!
There is no update due to the root, i advice you to manually update your phone to the latest version 4.0.3 using cwm, after that root again. finally you will have rooted ics on your nexus s.
uhm, you say i won't receive updates.
FAQ says most of the time i won't receive them.
THIS thread says i will receive them.
I am confused.
from what I can make sense of, it sounds like you should be getting updates. The FAQ you posted says that if you try to install one of the official OTA updates through CWM, it will fail most of the time.
i don't know how reliable that "checkin" trick is, and it may depend on your carrier as well.
if you've already rooted your device, then i would just flash one of the custom roms, you won't want to go back to the OTA after...
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
albundy2010 said:
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
Click to expand...
Click to collapse
Thats correct. It has only to do with the install. (It will fail).. if you dont get the notification for an ota i dont know whats wrong...
Sent from my Nexus S using xda premium
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
If you had 2.3.3 the update was probably the 2.3.6 and after that you would have received the 4.0.3 update....anyway from what I remember the version of the ota update is showed in the notification bar...isn't it?!
Sent from my Nexus S using XDA
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
1. I assume it was the a step up from 2.3.3 to a max of 2.3.6 as OTA updates to 4.0.3 are currently on hold due to battery drain issue
2. your OTA install is failing because you have custom recovery (CWM) but the OTA updates require the stock recovery (3e)
if you really really want to install OTA updates, you gonna have to go back to stock recovery (do a nand restore, hope you have one) then flash the OTA updates for your device
Hi all,
I received the OTA upgrade notice recently and I let it upgrade the device. The installation process can be initiated after reboot, but after a while I get the "Error" screen with the android logo lying down with a triangle exclamation mark at its stomach. It then gets stuck there for a couple of minutes, and then reboot to the original operating system.
Since there isn't any information on the error screen, I can't tell what causes the error. Has anyone encountered this and what should I do (or just wait)?
Thanks!
davidpage said:
Hi all,
I received the OTA upgrade notice recently and I let it upgrade the device. The installation process can be initiated after reboot, but after a while I get the "Error" screen with the android logo lying down with a triangle exclamation mark at its stomach. It then gets stuck there for a couple of minutes, and then reboot to the original operating system.
Since there isn't any information on the error screen, I can't tell what causes the error. Has anyone encountered this and what should I do (or just wait)?
Thanks!
Click to expand...
Click to collapse
If you are on a custom rom/kernel/recovery i.e. not 100% stock, OTA will fail. Even if you are completely stock and rooted, OTA may fail.
venu123 said:
If you are on a custom rom/kernel/recovery i.e. not 100% stock, OTA will fail. Even if you are completely stock and rooted, OTA may fail.
Click to expand...
Click to collapse
It's completely stock. I once used Kingo Root to root my phone, but had soon reversed the operation. Not sure if that is a possible cause, but apart from that I didn't make any material change to the core system.
davidpage said:
It's completely stock. I once used Kingo Root to root my phone, but had soon reversed the operation. Not sure if that is a possible cause, but apart from that I didn't make any material change to the core system.
Click to expand...
Click to collapse
Try to install via adb sideload. A brief guide here:
http://www.reddit.com/r/Android/comments/2mgh8o
Another one here
http://forum.xda-developers.com/nexus-4/general/official-lollipop-5-0-ota-nexus-4-t2942228
venu123 said:
Try to install via adb sideload. A brief guide here:
http://www.reddit.com/r/Android/comments/2mgh8o
Another one here
http://forum.xda-developers.com/nexus-4/general/official-lollipop-5-0-ota-nexus-4-t2942228
Click to expand...
Click to collapse
Thanks for the links. I tried what they suggested but during the update it says the following:
Installing update...
Verifying current system...
"/system/xbin/dexdump" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What should I do now? Seems more complicated than I'd like it to be
Nope, OTA is a no go on your phone. Flash the factory image.
updating to Lollipop
venu123 said:
Nope, OTA is a no go on your phone. Flash the factory image.
Click to expand...
Click to collapse
i was just offered the OTA update for my Nexus 4 in the UK. i accepted the update and as far as i can tell, it downloaded it, then went to install it. however, that didn't seem to happen. after going through the motions and wanting to reboot, which i obviously allowed, the phone still displays as being v4.4.4 when i check for updates though, it tells me the phone is up to date.
i dont know what to do now, so would be glad of any assistance offered, please
just offered and accepted the download again. same result. it appears to be 2 things preventing the update from happening. the first one is about accepting an untrusted/ zip package (or something like that) and the 2nd is about fixing root. i have tried doing 'yes' to both of them and 'no' to both as well. same result, the download downloads but wont install.
could i upgrade using the Android Toolkit? i have paid for it, so have the pro features, but the update wasn't offered through it earlier
Prettygrim said:
i was just offered the OTA update for my Nexus 4 in the UK. i accepted the update and as far as i can tell, it downloaded it, then went to install it. however, that didn't seem to happen. after going through the motions and wanting to reboot, which i obviously allowed, the phone still displays as being v4.4.4 when i check for updates though, it tells me the phone is up to date.
i dont know what to do now, so would be glad of any assistance offered, please
just offered and accepted the download again. same result. it appears to be 2 things preventing the update from happening. the first one is about accepting an untrusted/ zip package (or something like that) and the 2nd is about fixing root. i have tried doing 'yes' to both of them and 'no' to both as well. same result, the download downloads but wont install.
could i upgrade using the Android Toolkit? i have paid for it, so have the pro features, but the update wasn't offered through it earlier
Click to expand...
Click to collapse
Do you have a custom recovery? CWM gives that untrusted package message if you have signature verification turned on. If yes, you need to revert to stock and also unroot. Supersu does have the option of unrooting so you could try that. You could check out the toolkit, at least it can be used for backing up your data to the PC.
tnx for the info, venu123. progress made so far. i downloaded the Lollipop image and put it into the folder within Android Toolkit. i then let it do it's thing. the phone is now updated but i am struggling to get root again and also need some instructions on how to get it to sync again as a lot of the apps i had on the phone are not there now. anyone able to help with this please?
gonna have another try to get root on the phone. if successful, willpost back
---------- Post added at 08:12 PM ---------- Previous post was at 07:47 PM ----------
ok then. Android Toolkit didn't work. i can only assume that it's something to do with the Lollipop image not being in the program. however, i did get root by using the latest wugfresh app. many tnx to you for your efforts, wugfresh.
the one thing left for me to do now is somehow get the apps i had before the Lollipop update on the phone again. any help would be great, as i cant even see an option to sync the phone.
venu123 said:
Nope, OTA is a no go on your phone. Flash the factory image.
Click to expand...
Click to collapse
Is there a way to flash without wiping my data? Clearing my data is the last thing I'd want to do and, if this is unavoidable, I might just stay put.
I have a thought: since the message is telling me that dexdump has unexpected contents (that file actually doesn't seem to be there, as I've just checked), is it possible to just replace this file to bypass the problem? Thing is I cannot find this file anywhere for download.
Nevermind.. I copied that file from the factory image and the installation went smoothly!
My wife has started being prompted to this system update the last week for 24.81.3.en.ca. I'm wondering if she can hit install no problem or if i'll need to unroot (or do more?) before i can install.
I've looked and actually can't find much info on this specific update so not sure why that is but if someone could confirm that would be helpful as i dont want to brick her phone as she already doesn't like me 'fiddling with it' so i'll be a dead man but the constant prompts are also starting to annoy her.
Thanks!
I did this update today. Thought it was nougat. Biggest problem for me, was I seem to have lost 60gb of downloaded music on my 128gb sd card. Google play music started downloading EVERYTHING again. Also, all the programs that were on my SD card, disappeared from my home screens. The apps were still there in the app drawer, just had to put the shortcuts back. Not really sure what the update addressed.
SonnyTheMoney said:
I did this update today. Thought it was nougat. Biggest problem for me, was I seem to have lost 60gb of downloaded music on my 128gb sd card. Google play music started downloading EVERYTHING again. Also, all the programs that were on my SD card, disappeared from my home screens. The apps were still there in the app drawer, just had to put the shortcuts back. Not really sure what the update addressed.
Click to expand...
Click to collapse
October security patch
Sent from my XT1562 using XDA-Developers mobile app
I installed it but, StageFright Detector still tells me that my phone is vulnerable even with this security update. Google needs to make more efforts. Or maybe, Motorola should've given us the December 2016 update instead of a two month old update.
I saw a timeline earlier regarding a Nougat update in Dec for X Play? Any word?
ok so do i just unroot and install or something else? Or is there anyway to hide the update prompts?
farquea said:
ok so do i just unroot and install or something else? Or is there anyway to hide the update prompts?
Click to expand...
Click to collapse
You habe to be totally stock while updating from OTA.
SonnyTheMoney said:
I did this update today. Thought it was nougat. Biggest problem for me, was I seem to have lost 60gb of downloaded music on my 128gb sd card. Google play music started downloading EVERYTHING again. Also, all the programs that were on my SD card, disappeared from my home screens. The apps were still there in the app drawer, just had to put the shortcuts back. Not really sure what the update addressed.
Click to expand...
Click to collapse
Please share ota file on share drive like, googledrive/dropbox/etc.
Yeah if someone can share it, that'd be great. I can't go back to my stock ROM anymore cause I did the update, then tried CM14.1 and now, trying to go back I get (bootloader) preflash validation failed...
bablu048 said:
You habe to be totally stock while updating from OTA.
Click to expand...
Click to collapse
So I'm using the stock Rom but the bootloader is unlocked and rooted so I have to unroot only and install the update then re-root?
farquea said:
So I'm using the stock Rom but the bootloader is unlocked and rooted so I have to unroot only and install the update then re-root?
Click to expand...
Click to collapse
In your bootloader the status should say "unmodified/original(something like that)" you need stock recovery.
Easiest way is to download the new firmware and flash it.
skynetin said:
Please share ota file on share drive like, googledrive/dropbox/etc.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0Bx3VTuhTDlHYY1pDRWc4d1Q2X0E
Do NOT do this update. Nothing but problems since. Now will not recognize my sd card at all. Will not format it, gives tons of errors. Called Motorola support, they are aware of problems. Terrible idea.
Maybe that's why I'm completely unable to relock the bootloader with the official ROM?
SonnyTheMoney said:
Do NOT do this update. Nothing but problems since. Now will not recognize my sd card at all. Will not format it, gives tons of errors. Called Motorola support, they are aware of problems. Terrible idea.
Click to expand...
Click to collapse
Thanks, I was just doing a TWRP backup on my device to start the process of installing this update. I'll subscribe and wait for others opinion before installing.
Prosis said:
Maybe that's why I'm completely unable to relock the bootloader with the official ROM?
Click to expand...
Click to collapse
I've never been able to relock a Moto device. I thought that was a Nexus only feature, but I could be wrong.
AaronCompNetSys said:
Thanks, I was just doing a TWRP backup on my device to start the process of installing this update. I'll subscribe and wait for others opinion before installing.
I've never been able to relock a Moto device. I thought that was a Nexus only feature, but I could be wrong.
Click to expand...
Click to collapse
You can relock them but it will always remain as having been unlocked (status code 2). I've done it several times after tinkering with CM but after yesterday's update I can't do it anymore. I get a preflash verification error.
AaronCompNetSys said:
Thanks, I was just doing a TWRP backup on my device to start the process of installing this update. I'll subscribe and wait for others opinion before installing.
Click to expand...
Click to collapse
To save you looking around, here's a reminder how to stop updates: https://forums.lenovo.com/t5/MOTO-G...llipop-update-notification/m-p/3204499#M19669
If you really want to get rid of the Lollipop update notification go to "Setting" then scroll down to "Apps" and select it. It will take you to another screen. Since it's asking you to update you have downloaded the update that enables you to upgrade. Under the "Download" tab scroll down until you find "Motorola Update Services" and select it. You'll have three options at the top, "Force stop, Uninstall Updates and Disable." Select "Disable." It will then prompt you "Delete data and disable app?" Select "OK." It will then ask "Do you want to replace this app with the factory version?" Select "OK." You will no longer be asked to upgrade. If you ever want to upgrade just enable it under the the app again under the "Disabled" tab in the App menu, just swipe to the far right and enable. Don't forget to download the update from the playstore to enable the upgrade to Lollipop in the future.
Click to expand...
Click to collapse
I simply use Link2SD to freeze apps like this.
SonnyTheMoney said:
Do NOT do this update. Nothing but problems since. Now will not recognize my sd card at all. Will not format it, gives tons of errors. Called Motorola support, they are aware of problems. Terrible idea.
Click to expand...
Click to collapse
That's unfortunate for you. Personally, I don't have any problem after the update. The only trouble I had at first was that it was refusing to install because I had root. I tried to unroot and then reinstall default recovery but I still had the same error. I had to flash factory image on the phone before installing it.
Alright the firmware with the update was added to https://github.com/motoxplay/stock !
Update 24.81.3.en.ca "error!" during install process
Nico3d3 said:
That's unfortunate for you. Personally, I don't have any problem after the update. The only trouble I had at first was that it was refusing to install because I had root. I tried to unroot and then reinstall default recovery but I still had the same error. I had to flash factory image on the phone before installing it.
Click to expand...
Click to collapse
Hi Guys,
Newbie to this forum...here's hoping you can help resolve my issue. The latest update (24.81.3.en.ca ) does not want to install on my x play get an" error!" message mid-way through the install. Performed a factory reset ( a few times) as per Motorola customer support. Still get the same error message mid-installation…Any suggestions? My phone is stock ( not rooted ...yet). I noticed other users having issues with this update. Was wondering if I don't install this update will I still be able to install Nougat (when it becomes available)? Other than this issue the phone works great no problems.
Cheers!