After i read that you could keep root with the latest update i gave it a try. Im just rooted with stock recovery. I deleted some bloatware and installed hide soft keys was all i did. I downloaded the update and when it went to install i get an error msg. Message was er: 0x1117008. Then would reboot and a message would pop up saying was a problem during installation, no changes were made. I have since restored all the bloat i deleted thinking that may help, tried again and get same message. Anyone have an idea what it may be?
jmickel99 said:
After i read that you could keep root with the latest update i gave it a try. Im just rooted with stock recovery. I deleted some bloatware and installed hide soft keys was all i did. I downloaded the update and when it went to install i get an error msg. Message was er: 0x1117008. Then would reboot and a message would pop up saying was a problem during installation, no changes were made. I have since restored all the bloat i deleted thinking that may help, tried again and get same message. Anyone have an idea what it may be?
Click to expand...
Click to collapse
Not sure, but you may have to unroot first to install the update. What they probably meant by you can keep root is that they didn't patch it to prevent root. So, once you unroot, install update, then you can reroot again. Just my guess.
Sent from my LG-G2 using Tapatalk
jmickel99 said:
After i read that you could keep root with the latest update i gave it a try. Im just rooted with stock recovery. I deleted some bloatware and installed hide soft keys was all i did. I downloaded the update and when it went to install i get an error msg. Message was er: 0x1117008. Then would reboot and a message would pop up saying was a problem during installation, no changes were made. I have since restored all the bloat i deleted thinking that may help, tried again and get same message. Anyone have an idea what it may be?
Click to expand...
Click to collapse
I get the same error. Any update?
You'll need to restore all bloat. Pretty much need to be completely stock before updating. I was rooted with tethering provisions removed and Stock LG Browser installed. I has to fix the provisioning and remove the Browser (also adding any system/app files I removed) before the update was successful.
Kaiken said:
You'll need to restore all bloat. Pretty much need to be completely stock before updating. I was rooted with tethering provisions removed and Stock LG Browser installed. I has to fix the provisioning and remove the Browser (also adding any system/app files I removed) before the update was successful.
Click to expand...
Click to collapse
i'm am getting this same error and i have restored all bloat and even temporarily unrooted using Voodoo's OTA RootKeeper. i dont know what else to do at this point. any thoughts/suggestions?
brianj320 said:
i'm am getting this same error and i have restored all bloat and even temporarily unrooted using Voodoo's OTA RootKeeper. i dont know what else to do at this point. any thoughts/suggestions?
Click to expand...
Click to collapse
Have you restored your hide nav keys? You can also download a completely stock rooted rom somewhere on here and make sure your system apps are the same. I had to do this to find my BrowserProxyProvider.apk/odex I accidentally deleted and pushed them back into system/app.
Related
I keep trying to install the new voicemail application, but everytime I try to install it, it says Application not installed. Anyone else having this problem?
Nobody can help?
I'm having the same issue too
hmmm i didnt even know about this update until i read this thread.
i just went there and updated it no problem.
i would suggest making sure you are on 3g and not wifi. i am stock unrooted froyo'ed.
Updated w/o problem on Myn's 2.2 rom.
The update is pretty much voice to text service it seems. (Paid service after 1 month trial btw).
Mine just updated fine.
myn's warmtwopointtwo stock kernel
Still not working, and the icon in the notification bar won't go away. Worked fine on my girlfriends evo, both running fresh.
Not working here either.
fmedina2 said:
Still not working, and the icon in the notification bar won't go away. Worked fine on my girlfriends evo, both running fresh.
Click to expand...
Click to collapse
Maybe delete the download and re-download it. See if that helps.
animal7296 said:
Maybe delete the download and re-download it. See if that helps.
Click to expand...
Click to collapse
I am not sure where the app got downloaded to though.
No problem upgrading for me thanks for the notice.
Wipe the data in applications under settings
snandlal said:
Wipe the data in applications under settings
Click to expand...
Click to collapse
That got rid of the notification, but its still not installing. It either says A general failure has occurred, or application not installed.
updated fine on virus airborne 3.1
fmedina2 said:
That got rid of the notification, but its still not installing. It either says A general failure has occurred, or application not installed.
Click to expand...
Click to collapse
It got rid of the notification for like 10 minutes and it came back. This sucks might have to do a freaking nandroid restore just to get rid of this.
If your rooted, replace the SprintVVM.apk in / system/app with the one provided, change permissions to the same as all the other apps and reboot
Upgraded fine on stock 3.30 base deodexed version... I like how it said it was a mandatory update but didn't let me know there was one until I manually checked
Sent from my Super EVO!!
snandlal said:
If your rooted, replace the SprintVVM.apk in / system/app with the one provided, change permissions to the same as all the other apps and reboot
Click to expand...
Click to collapse
Tried. Still got 'application not installed' error.
Deleted the old voicemail app. Now I cant install the new or the old one. Getting the same error on both. Im royally screwed...
Btw, the "Mandatory" new update wont allow you to disable notifications like the previous versions, so if you want have some un-read voicemails sitting around, you're stuck looking at a notification icon forever.
I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Yesterday, I did the same thing you tried and I was successful in rerooting my phone after the OTA update. When you used the 1-click process did you choose option 1 or 2. I tried 2 and it didn't work. I had to chose option 1 (reload everything) to be successful. BTW, remember to make a new recovery backup of the system.
unrooted
xberry said:
I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Click to expand...
Click to collapse
Same issue here - how I fixed
I had already made titanium backups of important stuff - you have to go into applications (that use root) and force stop and clear data. Once this is complete open titanium backup for instance, and you should be asked for super user and then be good to go. Same goes for rest of apps that need root
OTA update Loop?
i have my d2 rooted after the ota 2.2 update. i just received a notification to accept the most recent OTA update ... whatever it is... and assumed it was one of my apps as i didnt read it thru completely b4 tapping 'ok'. now it is stuck in a download, reboot, update, "update unsuccessfully installed", redownload, reboot...........
is there a way to cancel the update? i dont really care if i have it or not
or some way to stop this process aside from the airplane mode i had to set it to so it would stop this madness
So you can do the OTA update without having to unroot and reroot?
Great advice from all - thanks! I'm not sure exactly what fixed it, but I ran DOROOT several times, did the unplug/plug when it hung for a minute, force closed/cleared data from previously rooted items, and also put phone into 'charge only' mode when USB Debugger would not run.
Finally - success! My advice to users with this same issue - try and try again.
Thanks all!
Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.
JadedRescue said:
Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.
Click to expand...
Click to collapse
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.
slogar25 said:
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.
Click to expand...
Click to collapse
I definitely did defrost those apps.
I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.
If you really want the ota then why don't you try mattlgroff's utility here:
http://forum.xda-developers.com/showthread.php?p=39576818
It will return you back to completely stock with one click and then you should be able to take the ota and reroot unlock if desired
Sent from my XT907 using Xparent BlueTapatalk 2
RSD
vLegend said:
I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.
Click to expand...
Click to collapse
I tried using Mattlgroff's method (which i'm sure is fine for most) but seems to be geared towards linux users mostly, and I ran into some issues. I have always used RSD to get back to stock and never had an issue. Check it out How To Restore Stock Firmware on Razr M. This will hard restore your phone to the factory image, as well as unroot it, no need to unfreeze or reinstall bloat. It will also obviously erase the internal SD card contents so make sure you back those up.
Yeah looks like slogar25 and cliMAKtic are right. I tried a few more things and its not working. I'll do an rsd in the next couple days and try the ota again.
I'm going to try rsd sometime tonight, I'll let everyone know how it goes. Thanks for all the help!!
I like rsd too. The point is to return too stock.
Sent from my XT907 using Xparent BlueTapatalk 2
Same issue, stops 1/4 of the way through.
Flashing back to stock with the RAZR M utility 1.10 once my phone hits 100% battery (at 93% now). Will let you know if I can take the update after.
Keep in mind
RSD is great to get back to clean stock, but keep in mind that it will remove your root. After taking the OTA update, you will be running firmware v4.1.2. If you used MotoFail2Go exploit to root your phone originally you should note that the exploit apparently does not work for the updated firmware. Instead you should use motochopper, an updated exploit that works on 4.1.2 to root your phone, developed by Drjbliss over at Droidrzr.
I honestly don't care too much about being unrooted at this point anyway, having root wasn't doing too much for me. I managed to get back to the original stock ICS using RSD and everything worked out! Downloaded one update to 4.1.1, then the second update to 4.1.2, and everything went swimmingly.
Thank you so much for all your help everyone!
The difference between "Official" and "Custom" device status was S-Health.
I was freaking out over being unable to get my S5 to show as "Official" in its device status (wanted to update, but was told I couldn't) .Out of paranoia, I copied over all my Downloads to my SD card and removed it, deleted any root apps and even cleaned it up using SuperSU. And I rebooted a lot. After I finished, I still saw
Device Status: Custom
Then, I remembered the S-Health bug. Since i like S-Health, I had switched it over recently from being a System app to being a User one (because S-Health on a rooted device was, well, broken). So I re-rooted with SuperSU, then re-opened Android Tuner Free and moved S-Health back from being a User app to being a System one again.
Device Status: Official
I didn't even have to unroot, remove the SU app, or reboot it; I just checked back in Settings and it was "fixed."
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
verse187 said:
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
Click to expand...
Click to collapse
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
primetechv2 said:
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
Click to expand...
Click to collapse
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
KennyG123 said:
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
Click to expand...
Click to collapse
I never actually installed a custom recovery, though. I did eventually reinstall the fully stock firmware with Kies and then performed the upgrade, something I'm going to guess wouldn't be possible otherwise... But to be specific, I never had anything installed except got XPosed mods and a moved S Health to get it functioning again.
But I'm really sad that, for whatever reason, my device status kept flickering between Official and Custom, especially when it chose Custom after I disabled root.
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
BlackJou said:
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
Click to expand...
Click to collapse
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
frcollier said:
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
Click to expand...
Click to collapse
It is on Dalvik though :/
well, I did it again.
rooted: Official status
Installed XPosed: Official
Removed S-Health: Official
Reinstalled old S-Health as a user app: Official
Shifted S-Health to System app: Official
Removed XPosed: Custom
Anybody know what permissions SHealth and HealthService (.apk, .odex) should be reinstated with, and in which folder they go, I'd be really happy. Especially if someone got back to me before I downloaded this 1.5GB system file to figure out if it says.
I'm having trouble getting the 027A update. I have been rooted since 024A but otherwise fully stock. I'm now running 026A - and the phone is still stock. Titanium Backup shows nothing is frozen. I even just performed a full factory reset on the phone. The phone automatically downloaded the update but says there is an error installing it because software was modified. Any ideas on how to fix this????
mattd860 said:
I'm having trouble getting the 027A update. I have been rooted since 024A but otherwise fully stock. I'm now running 026A - and the phone is still stock. Titanium Backup shows nothing is frozen. I even just performed a full factory reset on the phone. The phone automatically downloaded the update but says there is an error installing it because software was modified. Any ideas on how to fix this????
Click to expand...
Click to collapse
If you dont have custom recovery idk, try to unroot, also if you have xposed uninstall.
Also restore your hotspot if you modded it.
Sent from my Xposed G2