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!
I have rooted my device, and was looking to have orbot torify all apps. However, as soon as it finishes establishing a circuit, the the phone crashes and reboots, similar to what happens when the governor is set to msm-dcvs. The last event that occurs before this happens is orbot is granted superuser access.
The superuser app I'm using is SuperSU. The rom and kernel are stock.
Things I have tried to resolve this issue:
Uninstalling and reinstalling orbot
Clearing data from orbot
Changing superuser app from SuperSU to superuser.
Only torifying certain apps
Over an hour of searching Google, bing, and duckduckgo turned up nothing.
I am certain that the problem is local my s4, since I had no problem torifying all apps on my nexus 7.
Sent from my SPH-L720 using Tapatalk
I have been watching all the changes and progress for a couple months and gave in to the 110g update a couple weeks ago just to get the icon off my screen. Now Tmo decided to push 4.4 and i've had that icon again sitting there for 2 weeks. I've been debating on what direction I want to go, rooted 4.4 with no real benefits working yet, or keep 4.2 with known possibilities.
So I think I'd like to stay 4.2 for now and be done with it. But.. how do I disable the 4.4 install when I reboot the phone to do other things?
I've had no luck googling it since everything references 4.4 now.
I know that if you have titanium backup pro you can freeze a specific app which is the one in charge of updates(I don't remember the name) and your phone won't show that there's an update
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
disable the check automatically for update in update center under software update and when the update menu uppers after booting up click cancel.
don't forget to hit thanks if i helped you anyway.
and if i was wrong i was just trying to help.
edit:iam a stock user not rooted.
My phone doesn't reboot on it's own often but when it does and powers back on it shows an app that needed updating in the notification bar and updates it. I have auto-updating off in the play store. What is the rebooting about anyway. Why couldn't it have updated without rebooting????
Doesn't matter what ROM/kernel combo I use (AOSP). Doesn't typically happen on stock or stock-based roms
TLDR: App Manager crashes Settings on selection in all scenarios tried, both rooted and unrooted. Solutions or explanations?
So it's basically as described there. App Manager is crashing on a new Moto G4 XT1625 no matter what I do. I am at a loss. It crashes while rooted with Magisk, crashes when Magisk is uninstalled, crashes when I do a fresh flash of the Motorola stock ROM. I've even rooted and gone into Titanium Backup and ensured nothing is frozen, and it crashes.
I can long press apps on the drawer to reach individual app settings, but I cannot get into the App Manager itself. I've tried clearing the cache via this entry into the settings app info, and I've cleared the cache via TWRP. Neither has seemed to affect the crash either.
The only common denominator I can think of between all attempts is that the bootloader is obviously unlocked, but I can't connect that to the crash in my head.
At a loss here - any ideas? What am I missing, or what else might I try? Thanks for any education.
got this crash as well on my xt1622, TWRP, marshmallow, rooted
BUT THE MOST IMPORTANT REASON that cause this is because I deleted some unused (india) apps after rooting. Then the app manager messed up.
I just flashed the stock Nougat yesterday (https://forum.xda-developers.com/moto-g4/help/xt1622-nougat-root-questions-t3701145) - clean, no root, no TWRP, no modifications. Then, the app manager worked as expected. I doubt this will help as you stated that you already tried to flash the stock rom. You might have some other problem there.
libralibra said:
got this crash as well on my xt1622, TWRP, marshmallow, rooted
BUT THE MOST IMPORTANT REASON that cause this is because I deleted some unused (india) apps after rooting. Then the app manager messed up.
I just flashed the stock Nougat yesterday (https://forum.xda-developers.com/moto-g4/help/xt1622-nougat-root-questions-t3701145) - clean, no root, no TWRP, no modifications. Then, the app manager worked as expected. I doubt this will help as you stated that you already tried to flash the stock rom. You might have some other problem there.
Click to expand...
Click to collapse
Indeed I have, which makes it all the more confusing as to what could remain unchanged and still affect it. Although, it is something that you encountered it under the same general environment (twrp, marshmellow, rooted). I disabled a few apps when I first rooted, and assumed that was the cause as you saw, but no idea why the flashing did not fix it...