Database Info

[Q] Atrix 2 on 2.3.6 root issue after update

I received a message yesterday to update. I did so and then realized some of the rooted features were not working. It said i had granted superuser permission, but i would get the message saying your phone is not rooted. I tried rooting again and when it got to the bottom line it said something like "failed file already exist" and then "Your Phone is Rooted!"
I guess at this point I would like to unroot and maybe wait for the 2.3.6 root.
I originally used the 1 click exploit method not the superoneclick.
Any help would be greatly appreciated.
Thanks
Info currently on Android version:2.3.6
System version: 55.13.25.mb865.ATT.en.US

Same. Kinda worried, not sure if a lot of rooted stuff is working. Can't really tell. Kind of regret updating.
EDIT:
SetCPU app tells me that it is having trouble accessing 'permissions'. I can't change the CPU or do anything in that app.
Superuser app seems to say that it is 'allowed' though.

Yes. I regret the update now as well. I was'nt thinking when I did it. Superuser will show they are allowed, but they don"t really seem to be fully functional. If you delete a rooted app and reinstall it will not be shown in Superuser. I just want to unroot and wait fo a better option.

I'm not going to 'do anything' about this right now because I feel like a lot of these updates are helpful (like no more carrierIQ according to some post in the atrix 2 forum for this site, and less end call lag). Going to wait and see if someone finds a root exploit for this. Just kinda bummed about not being able to use SetCPU now.

I'm good with the update. At this point I would like to remove the root that isn't really a root anymore. I do miss titanium backup.

Ok, need some major advice re: this OTA update..
I've got the Atrix 2, obviously...and when i got it, i did the one click root, then immediately installed titanium backup and did a full backup to my microsd card. Then i started yanking out all the bloatware. Thats about all i did. No weird mods, etc...
Now im getting this notice that there is a OTA update, i download it, but it has an error when it installs and keeps nagging me about the update.
What does everybody suggest I do at this point? If I restore my phone using the titanium backup, will that allow me to get the update? I'm guessing the error is caused because the OTA is trying to update apps that I removed.
And if I do that and it works... will my phone still be rooted? Or will I have to re-root?
I'm new to this and ANY help or ANY advice would be GREAT.
Please, let me know something =)
~bobby
[email protected]
this is my first time on the XDA dev forums, so please speak slowly and be kind

I also had Titanium backup. I did the upgrade and it did not recognize the root after the upgrade. Therefore Titanium back up was not accessible. I also have not found a way to root the atrix 2 now that it is upgraded to 2.3.6. When I try the "1click exploit" method to root it goes through the process and says its already rooted, but I have no super user capabilities. Let me know if you find a solution. Otherwise if the root for titanium back up is important to you I would hold off on the upgrade for now.

When you did choose to do the update, did it give u errors until u restored your phone back to stock? What I mean is, did you have any errors installing the update when it first rolled out?
Because I have tried to do the update when it first came out, but it downloads, gets about 1/3 of the way installed and then give me an error and reboots. I'm thinking the only way to get past that is to use my titanium backup and put back all the stuff I took off right? Cause I made my backup IMMEDIATELY after I rooted my phone.
Root is important to me, and this stupid update isnt, but I also don't like being nagged about it every time I turn around.
I dunno what to do. :/ Im honestly kinda angry that they would do this and screw up root access for those of us who have it.
Sorta makes me wonder if that was part of the whole idea to begin with.
---------- Post added at 06:25 PM ---------- Previous post was at 06:08 PM ----------
Also, I just found this article. I haven't been a member here long enough for it to allow me to post links to the outside world, but just google these keywords: theandroidsoul, update atrix 2 to 2.3.6 OTA with root retained.
It gives these instructions:
Compatibility
This guide has been specifically written for the Motorola Atrix 2. Do not try to attempt it any other device as it may cause issues with your device. Check your device model number in: Settings » About Phone
How To Apply 2.3.6 OTA Update on the Atrix 4G, with Root retained
Download and Install OTA Rootkeeper on your Atrix 2
Launch OTA Rootkeeper, and Select ‘Create SU backup‘
Once SU backup is completed, Select Temp Unroot .
Now exit OTA Rootkeeper
Uninstall the Superuser app. In case you have Superuser Elite installed, uninstall that too.
Now uninstall OTA Rootkeeper. The backup you created through OTA rootkeeper in Step 2 above will still be retained, so don’t worry.
Now go ahead and download the 2.3.6 OTA update to the phone and apply it
Once the update is complete, reboot the phone. Once it has rebooted, power-cycle the phone ( Switch it off and power it back on after a minute)
Once the phone has booted back up, install OTA Rootkeeper and Superuser again
Launch OTA Rootkeeper, and Select Restore Root. This should bring up a superuser permission prompt, Accept it.
Now reboot the phone.
That’s it!! You have updated to the latest 2.3.6 OTA, and are also rooted.
______________
I am thinking about trying this. Using Titanium backup to get my phone back to how it was right after I rooted it, then following this guide, and then doing the OTA update.
Anybody see any holes in that plot before I go do something stupid?
~bobby

Bobby Anderson said:
When you did choose to do the update, did it give u errors until u restored your phone back to stock? What I mean is, did you have any errors installing the update when it first rolled out?
Because I have tried to do the update when it first came out, but it downloads, gets about 1/3 of the way installed and then give me an error and reboots. I'm thinking the only way to get past that is to use my titanium backup and put back all the stuff I took off right? Cause I made my backup IMMEDIATELY after I rooted my phone.
Root is important to me, and this stupid update isnt, but I also don't like being nagged about it every time I turn around.
I dunno what to do. :/ Im honestly kinda angry that they would do this and screw up root access for those of us who have it.
Sorta makes me wonder if that was part of the whole idea to begin with.
---------- Post added at 06:25 PM ---------- Previous post was at 06:08 PM ----------
Also, I just found this article. I haven't been a member here long enough for it to allow me to post links to the outside world, but just google these keywords: theandroidsoul, update atrix 2 to 2.3.6 OTA with root retained.
It gives these instructions:
Compatibility
This guide has been specifically written for the Motorola Atrix 2. Do not try to attempt it any other device as it may cause issues with your device. Check your device model number in: Settings » About Phone
How To Apply 2.3.6 OTA Update on the Atrix 4G, with Root retained
Download and Install OTA Rootkeeper on your Atrix 2
Launch OTA Rootkeeper, and Select ‘Create SU backup‘
Once SU backup is completed, Select Temp Unroot .
Now exit OTA Rootkeeper
Uninstall the Superuser app. In case you have Superuser Elite installed, uninstall that too.
Now uninstall OTA Rootkeeper. The backup you created through OTA rootkeeper in Step 2 above will still be retained, so don’t worry.
Now go ahead and download the 2.3.6 OTA update to the phone and apply it
Once the update is complete, reboot the phone. Once it has rebooted, power-cycle the phone ( Switch it off and power it back on after a minute)
Once the phone has booted back up, install OTA Rootkeeper and Superuser again
Launch OTA Rootkeeper, and Select Restore Root. This should bring up a superuser permission prompt, Accept it.
Now reboot the phone.
That’s it!! You have updated to the latest 2.3.6 OTA, and are also rooted.
______________
I am thinking about trying this. Using Titanium backup to get my phone back to how it was right after I rooted it, then following this guide, and then doing the OTA update.
Anybody see any holes in that plot before I go do something stupid?
~bobby
Click to expand...
Click to collapse
To answer the first part. I downloaded the update when I recived the message. I wasnt thinking about it giving problems with the root. I had no issues at all with the download. just the root not working afterwards.
The second part sounds like it might work for you, but it must be done before you update. It is too late for me to use this method. If i could unroot it, which I haven't found a way yet. I would try the method to save the root.
At least you thought about the upgrade and the root before thinking "oh boy an update lets do it", like I did. Now I'm stuck with a phone that thinks its rooted, but wonn't grant superuser permissions and won't take another root.

OTA failed
I ran into the same thing, downloaded the OTA today and run the update, really without thinking about the implications ('nother stupid n00b here : )). Interestingly it failed immediately and I still have root, I don't have any idea why it failed except maybe Superuser blocked the OTA packages SU access, is that even possible?
Anyway,,,Has anyone tried the OTA Rootkeeper procedure? I would like to have the update, because of stability issues, but I want to keep root more than I want the update.
Thanks

Did not work for me I back up to SD Card and used Titanium Back up and after the update cant get anything to work. Guess I have to wait until one of the experts comes up with anoter 1-Click_Exploit or Exploit (Manual). I'm new at all this and know just enough to be dangerous:-(

[Q] Root/update question

I have done a lot of reading her about rooting and updating my TF300. After getting a headspinning amount of information, I'd like someone to verify what I think I know.
I have a TF300, stock ROM, no root, running US .17. I have not received any updates after going to Settings/about tab/update and pressing the update button (I get "no updates found') I have cleared DM and CM client and rebooted several times, but no updates are found. I have tried on several WiFI networks I have access to.
1. I should be able to root using one of several one click methods I have found here, correct?
2. Once rooted and root keeper is installed, I should be able to update to .29 and keep root, correct?
3. A manual update to US .29, once rooted, will cause me to lose root, correct?
4. Will I receive Over The Air update once rooted? If not, how can I update to US .29 without losing root?
5. Is this the best path to take, or is there another path that would be easier for a newb like me (I know just enough about Android to be dangerous)? What I mean by another path is, should I manually update to US .29 and wait for a one click solution to come out later, all the while enjoying the new update.
6. All this is to fix some lag issues I have with all browsers....Tried Stock, Dolphin, Firefox, Opera...all the same. Some FC and others just hang for up to 30 seconds, even in Performance mode (With only one tab open!) So this will "FIX" those lag issues, correct?
Thank you for your time

If you're still on .17, root with sparkyroot, save it with ota rootkeeper, update to .29 (if it isn't there, they've been posted in many places on the forums), and restore root. As for fixing lag issues, it depends on what you do, rooting alone won't change anything, but you can try out the different tweaks available.
Sent from my Incredible 2 using Tapatalk 2 Beta-5

Missed a couple of your questions, yes, you will still receive ota updates if you're rooted, as long as you don't unlock the bootloader. This is the easiest way to root too, all you need to do is follow sparkyroot's instructions and back up your root.
Sent from my Incredible 2 using Tapatalk 2 Beta-5

One question always leads to another
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.

Throb1231 said:
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Click to expand...
Click to collapse
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.

Oh, and after you've updated to .29 and rooted; don't forget to use OTA rootkeeper to backup root.
If Asus releases a new update it may save your root.

EndlessDissent said:
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Click to expand...
Click to collapse
He's still on the .17 software, so no need to do that. Just use the sparkyroot method, backup with rootkeeper and then update.
Edit to add that no, rooting will not void the warranty, just unroot before you need to send it back.
Sent from my Incredible 2 using Tapatalk 2 Beta-5

Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.

Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.

Throb1231 said:
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Click to expand...
Click to collapse
No, you need to go to:
h tt p://forum.xda-developers.c om/showthread.php?t=1704209 (sorry for the chopped up link. I can't post links yet)
and root again.

EndlessDissent said:
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Click to expand...
Click to collapse
Ah, ok. Didn't realize you couldn't restore if you updated manually.

Yes, it is as I thought. Tried Sparkys and miloj's root program and I can not get root. I ran the program twice from my lap top. Driver's for TF300 show installed in Device manager (Windows 7). ASUS sync was installed in laptop and recognized TF300 but the program was not running during root attempt.
When I run Superuser and attempt to update SU binaries, I get "Failed" when it attempts pathway to write update.
Attempted to restore using OTA rootkeeper but all I get is "SU Restored". Check boxes indicate no root.
Any other ideas?
Confirmed I am on .29 from a MANUAL update.

Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet

Throb1231 said:
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Click to expand...
Click to collapse
Can you just install Superuser from the market? The su binaries might be there and the app just isn't installing. I may be wrong, not sure how the automated program works, but it can't hurt.

Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution

Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Try manually doing the code from miloj's thread?

While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.

Throb1231 said:
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Click to expand...
Click to collapse
Well, I can't think of anything else, you could just use the downgrade method, that's easy enough. The code really is just copy/paste though.

Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Your problem is not with the superuser apk.
The actual root is when you write an "su" binary to system and makes it executable (there is some access control stuff in between, but it's what's happening in essence).
So - your trouble is not with the installation nor the messages from superuser.apk - it's with the actual rooting method.
Make absolutely sure your adb drivers are working and that you've got the files "debugfs", "su" and the other debugfs file on top of the .bat file, which is the installation script, in the same directory whilst running the .bat file.

Agreed. I posted this in development.
It was surprisingly more difficult to install the drivers correctly than anticipated.
For those noobs like me, here's a step-by-step for installing the drivers before running the root method.
http://transformerprimeroot.com/tra...all-transformer-prime-usb-drivers-on-windows/
Please note that before using the step-by-step guide above, I also had to put the tf300 in Camera Mount to even get the "“ASUS Android Composite ADB Interface" option to show up in Device Manager.
Once you get this far, you can manually update the driver (found in the sparkym3 "Drivers" folder from the download) via the step-by-step.
Sent from my ASUS Transformer Pad TF300T using XDA

[Q] Currently rooted & un-locked, on build 26, what do for JB update??

Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??

Bzktz said:
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Click to expand...
Click to collapse
I'm assuming you still have stock recovery even though you unlocked the tablet. You can't re-lock the tablet so you'll eventually want to start using a custom recovery. However, don't install a custom recovery yet because the firmware upgrades are going to wipe custom recovery every time.
This should help you get started with the upgrade process using only the stock recovery:
Pre-upgrade:
0) HIGHLY RECOMMENDED -- Take the time to make nvflash accessible and make backups so that you'll be able to recover from a brick situation. This is the ONLY chance you have to do this before upgrading to .30:
http://forum.xda-developers.com/showthread.php?t=1901479
0.25) Performing the upgrades shouldn't affect your apps and data, but back them up if you want to just in case.
0.5) Make sure your tablet is charged 60% or higher or is plugged in.
Simple Upgrade Process:
1) Download "Voodoo OTA RootKeeper" from the market to back up your root.
2) Follow these instructions to update to .30:
http://forum.xda-developers.com/showthread.php?t=1755576
3) Reboot the tablet 2 times or so to make sure the .30 update finishes completely -- it updates the camera firmware and some other stuff.
4) Run RootKeeper again and verify you can still restore root. If you have to, re-root and use RootKeeper to back it up. Restoring a backed-up root is is currently the only way to root on Jelly Bean, so this is your LAST chance.
5) Download the appropriate Jelly Bean OTA update zip from here:
http://forum.xda-developers.com/showthread.php?t=1915079
6) Repeat the instructions in step 2, except you can just directly rename the file you downloaded in step 5 (there's no "zip within a zip").
7) After the upgrade is complete, run RootKeeper again and restore root.
8) Install the custom recovery of your choice (edit: when a working one becomes available).

recovery works in JB?

lafester said:
recovery works in JB?
Click to expand...
Click to collapse
sorry my mistake, there isn't one that's working yet.

i tried the manual method and it wont work
i did what the instructions said and in the end when android logo and status bar come out, shortly it display android with red triangle indicating that it failed. it says "ID verification failed." does anyone successfully update their TF700 using this method?

Bzktz said:
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Click to expand...
Click to collapse
If you are still on 26 the first thing i recommend you is to use the NvFlash tool (from the Development forum) so you can recover your device from any soft brick, then update to 30 and JB. Unlocking avoid your warranty so NvFlash tool is a wise thing to go with.

Just went through the motions (Including accessing nvflash)
no worries, I bricked it on purpose and then unbricked it just to make sure. nvflash is rad!
the new JB update, Forget the benchmarks, I don't even care what they say at this point, this is the best user experience I've had on this thing so far and it's just going to get better. at least with nvflash I can still load unsigned bootloaders, that's all I need for native linux experimentation.
yea though I walk through the valley of the shadow of flash I will fear no bricking, for blob.bin art with me. :good:

Thank you very much for the response. I am up to #5 in the process but now I am stuck. I renamed the file and stuck it on my sd card. However I am getting nothing when I then boot in recovery. It tells me SD Installation aborted, and gives me the Red Triangle. What am I doing wrong here?

Successful Update to MF3, and Retaining Root

First off, I am not responsible for anything that happens to your device.
Secondly, the only way I have tested this is with a FULLY STOCK, ROOTED ROM with NO SYSTEM APPS REMOVED (frozen is okay).
I was able to update my I337 to the 7/9 release of MF3 and retain root.
1. Install VooDoo OTA Root Keeper, make sure all 5 boxes are checked (may have to reinstall superuser if "Google Play" displays and grant root to the app)
2. Reboot, double check VooDoo OTA Root Keeper again has all checked boxes, then tell it to save root
3. Defrost/Enable all AT&T update apps, including AT&T Software Update, download the update through the check for software updates option in settings, and apply it.
4. Reboot, Use VooDoo OTA Root Keeper to restore root
5. Profit
props to @gokartracer5 for being the first to find this
SOME USERS WITH CUSTOM RECOVERIES, KERNELS, or DELETED SYSTEM APPS HAVE EXPERIENCED PROBLEMS.

Great news. I posted this in the other thread:
http://forum.xda-developers.com/showpost.php?p=43504854&postcount=407

The real question is, if you have working root on MF3, how to extract it so that everyone on MF3 can reroot.

I have a few questions.
1. did you have a custom recovery?
2. did you go stock before update
3. did you wipe data factory reset

WoodburyMan said:
The real question is, if you have working root on MF3, how to extract it so that everyone on MF3 can reroot.
Click to expand...
Click to collapse
scott14719 said:
Great news. I posted this in the other thread:
http://forum.xda-developers.com/showpost.php?p=43504854&postcount=407
Click to expand...
Click to collapse
..
I am guessing that Voodoo creates a file with all needed files and install locations when it is prompted to save root. If that created file can be found (temporary stored location), extracted, and then put on someone else's phone, Voodoo could theoretically reinstall root on the other phone. The file structure would need to be the same (same build / ROM) and it would only work if Voodoo doesn't give each created file a unique ID that only matches the original phone the file(s) were created on.
A better way would be to simply figure out where and how Voodoo re-injects root and then make a script that follows the same method.

Roadk1ng said:
I have a few questions.
1. did you have a custom recovery?
2. did you go stock before update
3. did you wipe data factory reset
Click to expand...
Click to collapse
At the time I was stock rooted with Xposed framwork and with Nottach's mod, no custom recovery.
I did not have to factory reset.

Maybe the key is that with VooDoo, root remains physically on the device, so there was no need to try to put it back on through an external device.
Which makes me think it may not work for a new unrooted MF3 device...
However, I am no Dev... hopefully this gives the real geniuses something to work with.

Voodoo Description from Play store page...there is also an XDA link:
"Free tool trying to protect root across manufacturer's OTA updates.
Also serves as temporary un-root (see statement)
Distributed as free of charge - no warranty. Open Source license: WTFPL.
Alternative download link: http://dl.project-voodoo.org/apps/VoodooOTARootKeeper.apk
This application makes a backup or a protected backup of your device's root.
This device must already be rooted: OTA RootKeeper doesn't have the ability to root devices.
If several conditions are matched, OTA RootKeeper will make root survive OTAs and... pretty much well anything − except /system partition formatting.
Requirement:
- /system partition as Ext2, Ext3 or Ext4
- Upgrades not formatting or overwriting completely the /system partition.
Typical systems where its perfectly effective:
- Nexus S
- Galaxy Nexus
- Every Honeycomb tablet
Typical system where the protection won't work:
- HTC Desire
- Samsung Galaxy Spica
- Samsung Galaxy S / SII
The application doesn't support original Superuser and not SuperSU for a very simple reason. The same feature OTA protection feature is already present in SuperSU.
In most case, only manufacturer's original recovery is able to install OTAs. It should not interfere with OTA update process itself.
A bonus feature is present, allowing you to un-root your device while keeping a su backup.
This way you can naively hide root until you choose to restore it via without further complications.
This nifty feature work on every rooted device.
** Temporary un-root statement **
This feature is designed for dev purposes in order to test their app with or without root.
The goal here is not to encourage stupid and unacceptable behaviors by movie or content sellers trying to prevent you to purchase or watch digital media you purchased if your device is rooted.
Vote with your dollars: Don't accept being a customer of companies restricting your freedom with defective and and inefficient technical measures.
Source code is available here:
https://github.com/project-voodoo/ota-rootkeeper-app
OTA root keeper is Open Source. Contributions, reviews and comments are welcome!
If you like this app, feel free to donate via PayPal to [email protected] & make my day in the process "
XDA Developers thread: http://forum.xda-developers.com/showthread.php?t=1241517
I posted this for several reasons.
1. The Dev said SuperSU has the same OTA protection feature built in. Has anyone simply tried it?
2. Although the Dev states that Voodoo does not inject root, he did state that it created a "protected" backup...so it still might be possible to locate that protected backup and inject it into someone else's similar device?
3. More information may be available via the XDA link.
I'm not a Developer either, but it seems something could come of this for those that are already on the MF3 firmware without root.

Active devices came with MF3 and we have a working root. Has anyone with a regular S4 on MF3 tried it?
Sent from my S4 Active

TwoStroker37 said:
Active devices came with MF3 and we have a working root. Has anyone with a regular S4 on MF3 tried it?
Sent from my S4 Active
Click to expand...
Click to collapse
Tried, discussed, and tried some more. There is a lot of info available about it in the various threads. I think the general consensus is that the exploit used in the Active Root might work on the New MF3 (non-Active) OTA, however the APK geohot put together verifies that the phone is an AT&T Active or it aborts. People have tried to contact him, but I don't think anyone has heard anything yet.

I'm on Verizon, so its not exactly the same, but I'm having a hell of a time recreating your success. My device keeps error-ing out in the middle of the update

Yeah this is the method I used yesterday. It works. One thing you have to do after is open the supersu app and install the binaries. It will give two options. Choose normal.
Sent from my SAMSUNG-SGH-I497 using xda premium

I have used Voodoo's OTA Keeper on all by devices for years and I had placed the app on my phone and "saved" my Root immediately after I got my phone. I am on Stock and had Froze all update apps so I never got the update and then when I read about update and people losing Root I posted in some thread about possible OTA Keeper use prior to update. The comments I got back was that it would not work for some technical reason. Since I am not a developer I said OK and just went on. I still not done the update and the only thing I really wanted to try in update was the new modem which I just downloaded and Flashed. Still it good to see that OTA Keeper does appear to work. I will keep watching this thread and if everyone that is the trying app and it working I may Unfreeze and get update.

gokartracer5 said:
Yeah this is the method I used yesterday. It works. One thing you have to do after is open the supersu app and install the binaries. It will give two options. Choose normal.
Sent from my SAMSUNG-SGH-I497 using xda premium
Click to expand...
Click to collapse
Yep. I mentioned you in the OP.
SGS4 non stock

If you have root on this update now, would someone be willing to try installing Goo Manager and installing a custom recovery and then flashing a Loki ROM? Now we can finally move forward a little bit at least.

I'm on step 3. Keep getting "Software update interrupted"

AmesCell said:
I'm on step 3. Keep getting "Software update interrupted"
Click to expand...
Click to collapse
Try defrosting all frozen apps first.
SGS4 non stock

I did that. Set TiB to show only frozen and it's got nothing. I tried a few reboots to be safe. This thing has no mods other than root. I use TiB to wipe the ATT updater data and still same thing.

Is anything different about this if you're using custom recovery? I'm on rooted-MDL with CWM.

someone correct me if I'm wrong, but I believe that custom recoveries won't flash OTA updates.
on my s3 I used mobile Odin for flashing firmware .tar files and ota .zip files as it would always root and inject supersu. while mobile Odin is available for the us market s4, it is NOT available for the att s4.

Getting to 4.3...got past 402 error!

Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!

doncaruana said:
Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!
Click to expand...
Click to collapse
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.

buhohitr said:
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.
Click to expand...
Click to collapse
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?

doncaruana said:
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?
Click to expand...
Click to collapse
Sorry but flashing the full firmware will wipe everything bring it back to factory stock phone, so you need to backup all your stuff.

Well, just to share with everyone, I did not flash back to stock. For a number of reasons, that wasn't really an option.
My first step was removing viper4android. That actually got rid of the "custom" screen with the open lock on boot.
Then I uninstalled busybox from within itself. Unfortunately, as noted elsewhere, that leaves several hundred symlinks in xbin, so I removed all of those (I was only left with dexdump and su there). After that, I actually uninstalled busybox via the app manager.
Then I used the unroot option in supersu to clean up the rest and remove it.
At this point, I should be completely unrooted, but still got the 402 error when failing to upgrade with the OTA.
So...I plugged the phone in and ran the software upgrade assistant that shows up on the "CD" that presents itself from the phone when you plug it in to USB to the computer. And, actually, that successfully completed the upgrade to 4.3!
Haven't embarked on re-rooting yet (using saferoot) but that's the plan at least.