I've been deferring the latest OTA (from end of June) waiting to see on here if people were able to keep root via VooDoo RootKeeper method. But alas I have not seen any post anywhere that specifically states they've done it so finally posting.
I'm all stock, just rooted w/SU. Still have all the bloatware crap so shouldn't have any problems updating - just looking for confirmation that I can use VooDoo and get root back after the update with no problem. If anyone has tried it and can share your success/failure I'd appreciate it.
I kept root with su survival mode. Straight up did the ota.
Surge1223
OTA Rootkeeper worked for me. I was also stock, rooted, with all the bloat intact. Just backup root, temp unroot, take the update, then restore root. Been a couple weeks and I've had zero issues.
Sent from my SCH-I535 using xda app-developers app
Related
Apologies if this question has already been answered, but I have searched here and on Google, but the results that come back are for people who cannot root at all. I have been fully rooted, appear to still be rooted (according to TB), but have come across an issue with TB that has made me want to learn more about the nuts and bolts of the rooting process.
I am usually a Revolver user but I am temporarily visiting rooted stock, currently WW 9.2.1.21. I had installed the full 9.2.1.11 ROM via CWM yesterday and upgraded from there via the CWM flashable updates, using OTA Rootkeeper to restore root.
TB has been working well for me with ICS until yesterday when it refused to restore or freeze my apps, although it can restore data. I have followed this guide on the TB wiki, number 27, http://www.titaniumtrack.com/kb/tit...l#tb-hangs-while-freezing-apps-restoring-apps but I am getting an error saying that /system/xbin/su is not found. Sure enough, a quick browse shows that su is not there. I do have /system/bin/su. Could this be why TB isn't working anymore? Has OTA Rootkeeper only partially completed its job? Does it have nothing to do with anything?
Just copy the su from system/bin to system/xbin.
OTA rootkeeper will only succeed in full root restore if you let it OTA update.
Thanks, your help is much appreciated. TB is now working as expected.
On my rooted TF101 with stock ics and stock recovery, I don't have similar problem with TB, althoug su is only in /system/bin.
As rootkeeper is concerned, the app protects su by creating a /system/su-backup and copy it back to /system/bin/su during restore, nothing else.
mine did same thing and it wont let me paste anything in xbin it says permission denied even though all apps have superuser permission except one..
nvm got thru terminal all it took was a two minute search and i had it :banghead:
Sent from my Transformer TF101 using XDA
If you have working CWM... flash this HERE. Reboot and it should all working again..
If you don't have CWM.. you better install one before attempting to flash this superuser.zip
After you thank me... you must also thank Wolf too(the man who do this magic..
Can you still get OTA updates on a Rooted phone?
You can get notifications, but any updates attempted will fail, especially if you have a custom recovery
Sent from my ice cream powered Nexus S
Root should not be a problem, it is only to obtain root user privileges on the system.
goompas said:
Root should not be a problem, it is only to obtain root user privileges on the system.
Click to expand...
Click to collapse
Updates tend to check that /system has been modified, if it has(ie rooted) then it will fail
Sent from my ice cream powered Nexus S
I believe it will fail to update if you are rooted, certainly you will no longer get OTA updates if you have a new ROM installed
I honestly think that it depends on the phone, the carrier, the rom, etc. Many times you can use a rootkeeper app to backup your SU and then unroot, and so long as you have not deleted apps, you can get the OTA. This is a good reason Titanium backup and freezing apps is so great. Unfreeze then, unroot and you are good.
Disable Sdm 1.0 in Titanium Backup. That should stop your phone from trying to update.
I'd imagine synergy has all this disabled right?
Sent from my SCH-I535 using XDA Premium App
Lord Alekosh said:
Disable Sdm 1.0 in Titanium Backup. That should stop your phone from trying to update.
Click to expand...
Click to collapse
If you just flash a custom recovery you don't have to worry about the update. CWM doesn't allow OTAs to be installed.
can't get a ota on beans rom anyways. all im interested in is the new radios.
Of course, I just imagine there are some people rooted with the stock rom and recovery
thanks so much for this!
tired of searching through 50 replies in other threads of people panicking, when this is the ONLY info i needed to know.
:good::good::good:
Got the update notice last night and it apparently tried to flash the update. Running No Sympathy rom, rooted (of course), bootloader unlocked, TWRP recovery.
Woke up to the TWRP recovery screen. Choose Reboot, System. then after rebooting, there was a pop-up window saying the update failed. Just waiting for the developers to properly incorporate the good stuff from this update.
I've looked around a bit, and while I've seen a few threads from a while back of folks complaining about the issue, I was wondering if we had any sort of fix? Currently I am unable to install any OTAs on my phone, and it's getting annoying. The phone is constantly reminding me of the OTAs, but after installing, they fail when CWM kicks in. Removing ROM Manager didn't help. Do I have to do a factory wipe for this to work?
Do you want the OTA or to stay off it? To take the OTA Odin back to stock but make a backup first with CWM or titanium. Then after the update re-root and restore your apps.
Or freeze the SDM.APK in titanium backup to stop it from pestering you and stay off the OTA track for good. Which is what I'd recommend. You don't need OTA on a Samsung. Unlike Motorola devices we don't need the kernel updates from official ota. We can rip those out and just install the kernel by itself. So using OTA is pointless unless you want verizon garbage apps and a locked bootloader. Cause you know when JB drops they will remove the ability to use the aboot and block us from unlocking most likely.
TLR
If you want stock. Odin. If you want to stay custom freeze SDM or remove it
Sent from a GlaDos Baked Potato
As title says - who has been successful keeping root with Voodoo?
Sent from my XT926 Vanquish
Never mind... Confirmed it myself
Sent from my XT926 Vanquish
Yeah worked for me too
Sent from my DROID RAZR HD using xda app-developers app
Upgrading to 4.1.2 and keeping root worked for me as well but has been causing me issues with 4G data connection. When I first upgraded and kept root my phone would only pick up 3G. I went to Verizon and had give me a new SIM card which fixed my issue and brought my 4G back but now I have the issue where I lose 4G during phone calls. This issue did not occur before 4.1.1.
Didn't work for me, went to click restore root and it there wasn't any backup but I know there was cause I created the backup just before restoring the stock recovery. Now I have no root and it won't let me downgrade.
remijenkins said:
Didn't work for me, went to click restore root and it there wasn't any backup but I know there was cause I created the backup just before restoring the stock recovery. Now I have no root and it won't let me downgrade.
Click to expand...
Click to collapse
did you forget to do the temp unroot before taking the update? that the common mistake most are making.
even me, thanxxx
................................................................................................
I am running 4.1.1 on my rooted DROID RAZR MAXX HD and want to take the 4.1.2 OTA update.
I use Voodoo OTA Rootkeeper Temp Un-Root which successfully makes my device unrooted. However, once I reboot, the phone is rooted again. I thought Voodoo would turn off root until I explicitly go back and Restore Root.
Am I wrong? Is Voodoo supposed to turn off root only until the phone restarts? If so, can I use Voodoo to temporarily un-root, and then immediately install the OTA 4.1.2 update without restarting my phone?
Or, is something wrong with my Voodoo installation since the temp un-root does not survive a restart?