Related
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).
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
This is my problem too. Hopefully there is a way.
Sent from my LG-D800 using xda app-developers app
Maybe doing a factory reset from stock recovery?
Sent from my LG-D805 using xda app-developers app
rohan611 said:
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
Click to expand...
Click to collapse
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
antawnm26 said:
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
Click to expand...
Click to collapse
nope. as i said in the OP< i have a stock recovery.
rohan611 said:
nope. as i said in the OP< i have a stock recovery.
Click to expand...
Click to collapse
then try root keeper it will disable root but back up root path and reinstate it once the update is done
antawnm26 said:
then try root keeper it will disable root but back up root path and reinstate it once the update is done
Click to expand...
Click to collapse
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
rohan611 said:
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
Click to expand...
Click to collapse
lol..yeah i read each statement in your OP just wanted to get to that last part of you saying your going back to stock and going from there, because thats your next option....
Let us know if you went back to stock then did the update and it worked.
I've read that some people kept root through their OTA. Why are some people able to update and others aren't. I've been reading up on this for the VZW update whenever that happens. I hope I haven't kept all this bloatware on my phone for no reason!!
Sent from my VS980 4G using Tapatalk
hinduboy74 said:
Let us know if you went back to stock then did the update and it worked.
Click to expand...
Click to collapse
I reverted back to stock using the instructions in the Stickied post. I was then able to update to D80010o. I had to call to request a rep to push out the D80010q update again though. They're calling it a "security update" so you should use that phrase when talking to the rep so that they don't get confused and think that you're just requesting that they push out the KitKat update.
Once I got the D80010q update, the KitKat update was available and I was able to update. Unfortunately, I didn't try to root it prior to updating - though to be honest, I don't really feel the need to root anymore. Only reason I had it rooted before was to get the multitasking button, but I'm okay with using an S3 layout (Menu, Home, Back) since that's the phone I'm coming from.
I have posted this in Other thread too.. may be this helps (Or save some time)
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
streetsmart999 said:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
rohan611 said:
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
Click to expand...
Click to collapse
That is correct. I was on D80010o all four times I updated to Kit-kat and kept root everytime.
streetsmart999 said:
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
Same thing happened to me. I followed your advice in the other thread and did a reset using the LG flash tool, following rootjunky's guide on youtube and using the files from his website. Everything went smoothly except for at the end I got the same check flag error thing, but it completed the reset perfectly.
I then chatted with ATT and had him push the update to my phone which brought me up to d80010o. It finally went through the update and didn't get me the root error. So I think I'm in the green now. He said that he didn't have an option to push the kit kat update to my phone but it told him to have me do it through the software update in the settings. Which I tried and it said it was up to date. But he said that since they roll out in batches my phone might just not be ready for it yet. I will keep trying though and I'm one step further than I was before. At least it let me update. Shout out to ATT though, chat service is on point.
Anyone receive this update yet?
I took the update and my build number updated, but my baseband and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.
churchey360 said:
I took the update and my build number updated, but my modem and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.
Click to expand...
Click to collapse
Did you have root? Retain root after the update?
No I was unrooted stock NAE
churchey360 said:
No I was unrooted stock NAE
Click to expand...
Click to collapse
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.
troyboytn said:
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.
Click to expand...
Click to collapse
Were you able to obtain root after the update?
chico1983 said:
Were you able to obtain root after the update?
Click to expand...
Click to collapse
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
Worked just like you said. I tried CF-autoroot and did not work for me. Have you been able to get the hot spot mod to work?
churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
but No baseband downgrade on NG2?
Philz still the bomb?
I want to do the reverse
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?
rastapapa said:
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?
Click to expand...
Click to collapse
Read this might help
http://forum.xda-developers.com/showthread.php?t=2840591
This is probably stupid and already answered in another thread but I'm a noob, don't flip out on me... Let's say, theoretically, I was to accept the
NG2 update. I'm rooted with Towelroot, using Supersu and Titanium backup. I've backed up then delete almost all of my bloatware with TB and have no further use for root at the time. If I were to break root with the update, will all that stuff stay the same and be safe until I can root again? I.e. If I break root, touch none of those root apps, then root again later, will they even "know" anything happened?
Since you can't take an OTA while rooted, that won't work.
frostedunit said:
Since you can't take an OTA while rooted, that won't work.
Click to expand...
Click to collapse
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?
tamiller said:
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?
Click to expand...
Click to collapse
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.
2WhiteWolves said:
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.
Click to expand...
Click to collapse
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
Read this, might help with the upgrade. Read all of the thread.
http://forum.xda-developers.com/showthread.php?t=2840591
So far from what I have read, I have know idea where the HD Voice Icon is, and no one else does either, not unless it is known in another thread that I don't know about.
johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
You will have to first install the stock NAE tar file with odin to return your phone to a stock unrooted condition with the stock recovery. Then you can take the ota. After that you can reroot again with cf autoroot.
Now the question is can you keep the domestic sim unlock if you do this?
I just received notification on my phone that there is a new software update. I didn't, nor can i install it because I've removed all of the bloat ware and rooted the phone, and installed TWRP. I'm already on 21q so this must be something newer that AT&T is pushing out. Anyone else get the OTA?
Ahh, it is more security updates. It brings the software version to 21r. It came out on September 10th. They probably patched the ability to root it. Lol
ATT 850
I think you're right, I went back to stock "D" and then took all updates. I didnt like what I saw so went back to stock "D" and now I cant root with any method. My Recent apps is now in a thumbnail format instead of tabs.... not sure there is anything I can do to root.
The Root.bat seems to work but then just hangs at the LG screen and never boots.
louvass said:
I think you're right, I went back to stock "D" and then took all updates. I didnt like what I saw so went back to stock "D" and now I cant root with any method. My Recent apps is now in a thumbnail format instead of tabs.... not sure there is anything I can do to root.
The Root.bat seems to work but then just hangs at the LG screen and never boots.
Click to expand...
Click to collapse
Were you able to get your phone to boot at all? Now I know not to flash it!
Egrier said:
Were you able to get your phone to boot at all? Now I know not to flash it!
Click to expand...
Click to collapse
No it never booted I had to reflash back to stock "D" I am trying it again this time I am taking the "F" update then trying the root
louvass said:
No it never booted I had to reflash back to stock "D" I am trying it again this time I am taking the "F" update then trying the root
Click to expand...
Click to collapse
I was able to root 21q. I'm not going beyond that if you had issues after updating it.
Egrier said:
I was able to root 21q. I'm not going beyond that if you had issues after updating it.
Click to expand...
Click to collapse
I'll keep you posted I'm still playing
UPDATE: after a few tries I was able to stump root "D" once again. I'll install TWRP and a ROM and leave it at that
I think the stupid update tried to install itself without any interaction from me. I had my phone laying next to me on the desk and heard the AT&T jingle playing. I turned to look at it and was rebooting. After it rebooted, a box was up on the screen saying that there was suspicion of my phone being rooted and that it wouldn't install. Fine by me.
Pretty sure this is the patch for the stagefright vulnerability.
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!