I got an update notification yesterday, from the DM, and the notification is persistent, popping up and reminding me every few hours. But I do not want to try it since I'm rooted, so many application level mods, and at&t crapware removed.
how do I avoid updating and remove update notifications?
Or, is there a safe way to upgrade while still retaining root and other app mods?
thank you.
I was rooted when I got the ota and it worked fine. I still had the bloatware, no lagfix or other mods. You could always do a Clockwork of the update I897UCJH7 - OTA System, Kernel, Modem - Clockwork Flashable - Rooted and then restore.
Related
I'm running stock rooted with a few minor tweaks - Notification toggles and Google now installed. Last night I received the message that there was an software update. What happens if I install it? Will I just lose root or will everything be changed back to stock?
EDIT: I misclicked and posted this in the wrong forum. Mods, can you move it?
JoeyBert said:
I'm running stock rooted with a few minor tweaks - Notification toggles and Google now installed. Last night I received the message that there was an software update. What happens if I install it? Will I just lose root or will everything be changed back to stock?
EDIT: I misclicked and posted this in the wrong forum. Mods, can you move it?
Click to expand...
Click to collapse
I updated mine and lost root.
Went through the rooting process again and I have root. No big deal.
I unfroze all the apps I had frozen and tried the OTA and it still failed.
I am rooted with just the stock ROM.
Anything I am missing here?
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
No OTA updates will work on a rooted phone. If it somehow does work it will likely break your root privileges
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Plunkyxda said:
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
Click to expand...
Click to collapse
You can do a OTA with root but you will just lose it. If you altered some system files it will fail or if you run a custom recovery it will fail.
I've had similar issues, on other devices, with ota updates not working because of root, and more specifically I believe, cwm recovery. Unfortunately I've had to use kies to update.
Sent from my SCH-I535 using xda premium
kendive said:
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Click to expand...
Click to collapse
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Yea I agree... I did not really need the OTA and I plan on installing CleanROM 5.6 tmr.
I just froze all that bloat back. I can't stand all that S***T running in the back ground.
Plunkyxda said:
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Click to expand...
Click to collapse
I am on stock 4.1.2, VRBMB1. I am rooted, unlocked and with TWRP recovery. I have used Titanium to freeze SDM 1.0.
I am considering going to VRBMF1. I don't know how to safely get there. I also don't know what improvements might come with the OTA to MF1. Should I just hang out with VRBMB1 until the rumored update to 4.3 arrives? I would like to be in the position to return to what I have now (just in case), or be able to move to 4.3 if, and when, it come out. How do I proceed? Thanks
I have the same question... subscribed!
Is there a rooted/unlocked update file, or do I just run the VZ update and use Voodoo rootkeeper to restore root (or Casual unlock again, if needed)? Or dirty-flash one of the rooted/unlocked stock ROMs (and then the firmwares)?
So many ways to get there, just looking for the safest... I figure the VZ update might be best.
So, I finally bit the bullet. I backed up all kinds of things before running, but it seems I didn't need to. I unfroze SDM, and then checked for updates. It downloaded and then rebooted to install. Since CWM was installed, it tried to perform the update, gave a few errors, but I let it go anyway. After the main install was done, CWM asked me if I want to let the updater install a new (stock) recovery - I said no. Then it said that I may have lost root, so do I want CWM to fix it - I said yes. Then I cleared the cache (just in case) and rebooted. The phone booted up, said it completed the upgrade, and then dropped me back into the rooted OS. Pretty cool.
SDM did complain to say that the updated "didn't happen" but the phone shows the new MF1 version, and a few new apps as well. So, obviously, the update happened... and I didn't lose root or recovery. Damn nice...
I wonder if TWRP does the same things (disable the stock recovery and restoring root)...?
EDIT: Reading the TWRP page says that they don't support nor recommend applying a stock ROM update.
Secondly, I found that while my phone was working fine, when I tried to get into recovery, it popped up the unauthorized software error. Meh. I used the Casual rooting tool to reroot, apply the insecure aboot, and then reapply CWM... and I'm back to normal now. Not a big deal, but still more steps than I thought I needed above!
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
filmfanatic09 said:
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
Click to expand...
Click to collapse
You cannot be rooted or you must hide root w/ voodoo or super su. Also you must use stock recovery.
the update will not actually fail if you are rooted, although it may report failing.
if it actually fails, you can obviously see it doesnt go through the process, then there is some other factor causing it to fail.
some things that would cause it to fail all together are: non stock recovery, freezing any bloat, removing any bloat, pretty much any modifications to the stock software other than rooting will cause it to fail.
once you have any system deficiencies fixed, use voodoo from the market to protect root and temp unroot before taking the update.
if you cant figure out what you did to the system to fix it, you may want to re-flash using the proper utility for your current system, re-root, protect and temp unroot through voodoo, then try the update again.
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
filmfanatic09 said:
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
Click to expand...
Click to collapse
you can flash the hole system using this http://forum.xda-developers.com/showthread.php?t=2474393 get the 1.33 version to match what you are on or the 1.34 to go right to the version you are trying to upgrade to. either is fine.
I noticed that the pro version of SuperSu has a survival mode option. Should I have this enabled all the time? or should it only be enabled when I am ready to make a OTA update?
Just leave it where it is. I'm not even sure if it'll work with an ota. The nexus 5 is so easy to root that I've never tried it. It had been helpful on some other devices butt it's not needed with the n5
gee2012 makes a good point for cm roms of you want to maintain supersu
Edit out of curiosity I did enable survival mode on 4.4. It does survive update to 4.4.2
Sanvido said:
I noticed that the pro version of SuperSu has a survival mode option. Should I have this enabled all the time? or should it only be enabled when I am ready to make a OTA update?
Click to expand...
Click to collapse
You can turn it on all the time, also when you flash CM superSU will remain the main superuser app.
You leave it on all the time as I assume it has scripts to reinstall SuperSU if certain files are removed. It currently works fine for me with OmniROM OTA updates.
Thanks guys for the answer.
Charlular said:
You leave it on all the time as I assume it has scripts to reinstall SuperSU if certain files are removed. It currently works fine for me with OmniROM OTA updates.
Click to expand...
Click to collapse
^^^
Well, of course you would keep root with OmniROM, since it is a rooted rom.
Why wouldn't it keep root when you're using a ROM that requires root to begin with?
Forgive me for being a compleat (sic) Nitwit... but I thought that Rootkeeper and Survival Mode in SU were supposed to keep root through an OTA update for the stock ROM, like going from 4.3 to 4.4 which I think is impossible because when I tap 'check for updates', the message comes up that (and I'm paraphrasing here'... can't be updated because your system has been modified.
When reading through all the caveats in OTARootkeeper in the Play Store, it seems to say that you can un-root temporarily in order to install a new ROM update, and then re-enable root.
Of course, then the Dev. goes on to say that OTARootkeeper won't work with SuperSU installed because OTARootkeeper has it's own version of SU built in.
Am I right or wrong... and if I'm wrong, I wish that somebody would explain it to me exactly where.
Am I correct in assuming that OTARootkeeper will allow temporarily un-rooting for the purpose of installing let's say, an update to the stock ROM which I happen to be running, and then re-rooting and still keep root status?
I've had OTARootkeeper installed for quite a while, but I read that it no longer works with 4.3 to 4.4 stock ROM updates anyway, so I guess my comments become moot.