Anyone confirm OTA rootkeeper still keeps root after latest OTA updateT889UVBMB4-WiFi - T-Mobile Samsung Galaxy Note II

Anyone confirm https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper still keeps root after latest OTA update T889UVBMB4 ?
No LTE yet here but happy with current speeds should I update? Does T889UVBMB4 interfere with WiFi Tether working with TrevE mod?
-Thnx
http://forum.xda-developers.com/showthread.php?t=2111188&page=4
SMARTPHONEPC said:
Below is the updated steps that worked for me:
Step1: Install ExynosAbuse APK v1.40 & Run SuperSU & update SU binary if prompted.
Step2: Install & Run https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper & select protect root.
Step 3: Install OTA T889UVALL4
Step 4: Run https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper again to restore root backup?
-
You da man kozmo21..
I did uninstall all root apps & unrooted in SuperSU right before the OTA update (when I noticed modified status) & began again with the above simple steps as I also had installed WifiTether-TrevE_Mod_11_22_2012_driverReload2 (defaults to Wifi Driver Reload 2) - http://www.androidfilehost.com/?fid=9390208427046731813 with settings changes as outlined at http://forum.xda-developers.com/showthread.php?p=35476525 & attached thumbnails at http://forum.xda-developers.com/showpost.php?p=37109011&postcount=7 . . as described http://forum.xda-developers.com/showpost.php?p=37172883&postcount=10 in addition to Titanium Backup. I will ask the WiFi Tether working with TrevE mod thread whether modified status is expected with WifiTether_TrevE_Mod_11_22_2012_driverReload2.apk & implications..?
- Thanks
Click to expand...
Click to collapse

I can't confirm OTA rootkeeper works but I can confirm that the similar function in SuperSU Pro worked for me for the last 2 OTA updates. I went through the LLA4 and the BMB4 updates using the OTA method and SuperSU Pro's rootkeeper function and kept root through both updates.
From what I know about how both applications work, they use a similar method to keep root and if one works the other one should work also.

Yes it works. SuperSU price works as well. Though avoid the hassle and use mobile odin pro if you use stock roms.
Sent from my SGH-T889

Related

[Howto] Preserve Root on Fire !

Fellow Fire Users .
I think we can preserve the Root and Reroot in a single click after the 6.2.1 update. It worked for me and Market,Rootexplorer is working for me after the update.Hopefully it should work for you also.
What Needs to be done ?
Before updating to 6.2.1 i assume that you have already rooted the previous version and you are on any of the previous version of the stock rom.
1. Download Voodoo OTA Rootkeeper
2. Click on Backup Root
3. Now you may update to the 6.2.1 version
4. After updating open Voodoo OTA Rootkeeper again and click on Restore root.
5. You have preserved the root.
Note: I cannot be held responsible if this does not work for you. Try at your own risk!
didnt work for me
had it day one to use prime video streaming
sxrmafia said:
Fellow Fire Users .
I think we can preserve the Root and Reroot in a single click after the 6.2.1 update. It worked for me and Market,Rootexplorer is working for me after the update.Hopefully it should work for you also.
What Needs to be done ?
Before updating to 6.2.1 i assume that you have already rooted the previous version and you are on any of the previous version of the stock rom.
1. Download Voodoo OTA Rootkeeper
2. Click on Backup Root
3. Now you may update to the 6.2.1 version
4. After updating open Voodoo OTA Rootkeeper again and click on Restore root.
5. You have preserved the root.
Click to expand...
Click to collapse
You apparently never read any of the many other threads that this method has already been debunked.
This was proven to not work when the first update to 6.2 occurred. It also has failed to work for the 6.2.1 update. DOES NOT WORK!
Note: I cannot be held responsible if this does not work for you. Try at your own risk!
Click to expand...
Click to collapse
What exactly are they trying. Most people who rooted used OTA Rootkeeper so they could use Amazon Prime... that is all it was good for though.
It worked for me , maybe i was lucky or what but it did
sxrmafia said:
Fellow Fire Users .
I think we can preserve the Root and Reroot in a single click after the 6.2.1 update. It worked for me and Market,Rootexplorer is working for me after the update.Hopefully it should work for you also.
What Needs to be done ?
Before updating to 6.2.1 i assume that you have already rooted the previous version and you are on any of the previous version of the stock rom.
1. Download Voodoo OTA Rootkeeper
2. Click on Backup Root
3. Now you may update to the 6.2.1 version
4. After updating open Voodoo OTA Rootkeeper again and click on Restore root.
5. You have preserved the root.
Note: I cannot be held responsible if this does not work for you. Try at your own risk!
Click to expand...
Click to collapse
I'm still 6.2. Will install the app and try to restore if ever the update takes place on my device.

[How To] Install OTA and root.

I've seen and answered this question quite a few times so I thought I'd just write down the procedure once so everyone can find it.
So you want the latest OTA and want it rooted but you have no idea how to get there? I can help.
Prior to yesterday I was running rooted stock with TWRP recovery. The OTA failed of course.
In order to install it and root I did the following.
1) install rooted stock image via odin (found at http://forum.xda-developers.com/showthread.php?t=1739426) This re-nstalled stock recovery.
2) install and run voodoo ota root keeper from the play store to preserve root.
3) took OTA download and let it install
4) ran voodoo OTA rootkeeper to restore root again
5) Install goo manager from play store
6) install twrp via goo manager
7) made a rooted stock nandroid backup.
The above procedure didn't wipe any of my data or settings because I came from rooted stock to begin with. I just used odin to restore the recovery and missing bloatware..
Hope this helps
Do you have the clockworkmkd recovery file I need to flash through odin? Does this mean I don't have to use adb?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Mastermachetier said:
Do you have the clockworkmkd recovery file I need to flash through odin? Does this mean I don't have to use adb?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I didn't use ADB. I used twrp for my recovery, but you can install rom manager and cwm recovery with it instead of goo manager and twrp.
I lost my root when i did the update...
can you give step by step on how to root again after the update and install the google universal search?
thanks...
Flashed the rooted stock image via Odin, update failed at 27%. Any ideas?
No idea. Just reporting on what worked for me.
Tlo218 said:
Flashed the rooted stock image via Odin, update failed at 27%. Any ideas?
Click to expand...
Click to collapse
If you've disabled or uninstalled stock at&t and Sammy apps (like Flipboard, clocks, etc.) the update will fail. You need to enable/reinstall stock apps.
Hi, I used Voodoo Root Keeper to regain root. However, in my device status it is now saying modified instead of normal. How can I fix that?
You can't. Don't worry about it.
one028 said:
I lost my root when i did the update...
can you give step by step on how to root again after the update and install the google universal search?
thanks...
Click to expand...
Click to collapse
That's beyond the scope of my original post.
knarfl1 said:
If you've disabled or uninstalled stock at&t and Sammy apps (like Flipboard, clocks, etc.) the update will fail. You need to enable/reinstall stock apps.
Click to expand...
Click to collapse
It looked like reflashing the rooted stock rom did reinstall the bloat I removed.
gunnyman said:
I've seen and answered this question quite a few times so I thought I'd just write down the procedure once so everyone can find it.
So you want the latest OTA and want it rooted but you have no idea how to get there? I can help.
Prior to yesterday I was running rooted stock with TWRP recovery. The OTA failed of course.
In order to install it and root I did the following.
1) install rooted stock image via odin (found at http://forum.xda-developers.com/showthread.php?t=1739426) This re-nstalled stock recovery.
2) install and run voodoo ota root keeper from the play store to preserve root.
3) took OTA download and let it install
4) ran voodoo OTA rootkeeper to restore root again
5) Install goo manager from play store
6) install twrp via goo manager
7) made a rooted stock nandroid backup.
The above procedure didn't wipe any of my data or settings because I came from rooted stock to begin with. I just used odin to restore the recovery and missing bloatware..
Hope this helps
Click to expand...
Click to collapse
worked fine for me
There's a much easier method to get root back after the update.
Flash CWM/TWRP
Flash the file I attached below.
Install Busybox from market
Reboot
Done deal
It does work. I tested earlier today from G1 stock unrooted. Pulled and installed the update, flashed CWM. Flashed the attached file, busybox download and profit. Then used gooomanager to change to TWRP
Here's the original site I read about this method way back when...
http://www.theandroidsoul.com/easy-guide-root-att-galaxy-s3/
Gunny's method does work, just giving another option
OP guides worked for me. Thanks
I like the new keyboard, less errors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks for the info just would rather have a CMW flashable with root
I just want to say thank you I really appreciate your help and the time you put in to provide this info it worked like a charm and I really appreciate the help
I didn't loose root
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
z45123 said:
I just want to say thank you I really appreciate your help and the time you put in to provide this info it worked like a charm and I really appreciate the help
Click to expand...
Click to collapse
You're welcome.
So does this work if I lost root during the process?
There's a much easier method to get root back after the update.
Flash CWM/TWRP
Flash the file I attached below.
Install Busybox from market
Reboot
Done deal
It does work. I tested earlier today from G1 stock unrooted. Pulled and installed the update, flashed CWM. Flashed the attached file, busybox download and profit. Then used gooomanager to change to TWRP
dahlem said:
So does this work if I lost root during the process?
There's a much easier method to get root back after the update.
Flash CWM/TWRP
Flash the file I attached below.
Install Busybox from market
Reboot
Done deal
It does work. I tested earlier today from G1 stock unrooted. Pulled and installed the update, flashed CWM. Flashed the attached file, busybox download and profit. Then used gooomanager to change to TWRP
Click to expand...
Click to collapse
Yes, it does work. Get a custom recovery back (CWM) and flash the file I attached in my earlier post. Saves the time from flashing a stock rooted ROM and going from there as a starting point.

Anyone tried the recent OTA update using the "OTA survival" option in superuser?

Anyone tried the recent OTA update using the "OTA survival" option in superuser?
I'm in AT&T S3, rooted but with stock recovery, using mrrobinson's method, building number I747UCALEM.
Wondering whether anyone has tried doing the OTA update and keeping root by using the "temp unroot" and/or "OTA survival" options in Superuser? If so, was it successful, and would you mind giving a quick rundown of the steps?
Thanks!
I did it, I installed Voodoo root keeper backed up my SU app with this app then I removed root with this app also, after thid I just hit the check for update and applied the OTA.
After appling OTA I went to Voodoo app and restored root.
It was very easy let me know if you need any more help.
Sent from my SAMSUNG-SGH-I747 using xda premium
IcOpRo said:
I did it, I installed Voodoo root keeper backed up my SU app with this app then I removed root with this app also, after thid I just hit the check for update and applied the OTA.
After appling OTA I went to Voodoo app and restored root.
It was very easy let me know if you need any more help.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. Sounds like you used another app, Voodoo Root Keeper, not Superuser?
Just to err on the side of caution, I should do the following?:
1. get voodoo root keeper
2. go into Superuser and check the "ota survival" box
3. go into voodoo hit "protect root"
4. still in voodoo hit "temp. un-root (keeps backup)"
5. go to about device>software update to check for update
6. apply update
7. once update completes, go back to voodoo? or superuser?
If you're on UCALEM and you're trying to get to the latest version (LH9), you'll have two OTAs to apply: LEM->LG1 and LG1->LH9.
Save yourself a headache and just flash a full LH9. That way you won't have to worry about root. You can find a full flashable LH9 here and also here (in the PIECES section at the bottom of the post).
Either way you go, make sure you make a nandroid first.
drothenberger said:
If you're on UCALEM and you're trying to get to the latest version (LH9), you'll have two OTAs to apply: LEM->LG1 and LG1->LH9.
Save yourself a headache and just flash a full LH9. That way you won't have to worry about root. You can find a full flashable LH9 here and also here (in the PIECES section at the bottom of the post).
Either way you go, make sure you make a nandroid first.
Click to expand...
Click to collapse
Thanks for this advice. I currently don't have a custom recovery installed. How do I go about making a nandroid without it? Do I need to install a custom recovery first?
jhc5 said:
Thanks for this advice. I currently don't have a custom recovery installed. How do I go about making a nandroid without it? Do I need to install a custom recovery first?
Click to expand...
Click to collapse
Sorry, I missed that you still had stock recovery installed. You'll need to have a custom recovery to use the zips from either of the links I posted. If you want to stay on stock recovery, you'll need to apply the two OTAs from AT&T to upgrade.
To install a stock recovery, you can:
Install ROM Manager and use that to flash CWM
Install GooManager and use that flash TWRP
Follow the instructions in this post

[Q] Superuser binary will not update to 3.1.1 (from 3.0.3.2)

See attached screenshot. When I try to update to the latest binary, it fails when trying to gain root access.
Root seems to be working fine - all apps that require it have not had errors. Voodoo OTA Rootkeeper and Titanium Backup both tell me I do have root access. However, Superuser seems to be messed up since updating from 4.0.4 to 4.1.1. It is not showing toasts when apps are granted access and the log is not keeping track of anything. If I delete an app that requires root (from Superuser) it won't let it have root back...
So, is there a way to fix this? Do I need to just download SuperSU instead?
Thanks
EDIT: Let me add that I used Voodoo OTA Rootkeeper to preserve root during the 4.1.1 update.
jeffreii said:
See attached screenshot. When I try to update to the latest binary, it fails when trying to gain root access.
Root seems to be working fine - all apps that require it have not had errors. Voodoo OTA Rootkeeper and Titanium Backup both tell me I do have root access. However, Superuser seems to be messed up since updating from 4.0.4 to 4.1.1. It is not showing toasts when apps are granted access and the log is not keeping track of anything. If I delete an app that requires root (from Superuser) it won't let it have root back...
So, is there a way to fix this? Do I need to just download SuperSU instead?
Thanks
EDIT: Let me add that I used Voodoo OTA Rootkeeper to preserve root during the 4.1.1 update.
Click to expand...
Click to collapse
well what i see is that its finding a higher version than what that phone is wanting to update well you see were the green is well its all green so its acting as if your su binary is already updated all the way try rerun the root program or flash the su update on su page
jeffreii said:
See attached screenshot. When I try to update to the latest binary, it fails when trying to gain root access.
Root seems to be working fine - all apps that require it have not had errors. Voodoo OTA Rootkeeper and Titanium Backup both tell me I do have root access. However, Superuser seems to be messed up since updating from 4.0.4 to 4.1.1. It is not showing toasts when apps are granted access and the log is not keeping track of anything. If I delete an app that requires root (from Superuser) it won't let it have root back...
So, is there a way to fix this? Do I need to just download SuperSU instead?
Thanks
EDIT: Let me add that I used Voodoo OTA Rootkeeper to preserve root during the 4.1.1 update.
Click to expand...
Click to collapse
I had the same issue with SU on an older device (captivate i think) in any case i would just download SuperSU and see if it works there. I've never had any problems with it and is a better root management app in my opinion.
Thanks guys but this post was from February...two phones ago for me lol

[Q] 4.3 ota Root Question

sooo i was stock i took the OTA update to 4.3 mk6
i decided i didn't care about the knox counter so i rooted and custom recovery (this is the rom location http://forum.xda-developers.com/showthread.php?t=2589891) and this is the recovery location http://forum.xda-developers.com/showthread.php?t=2159652
now every thing is working (SU, Titanium Back up, and so on)
however when i try certain apps (game killer, game chi) it says i don't have root
i have searched everywhere but i am not seeing any posts about this
any help would be greatly appreciated
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
thanks for the help i will try this now
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
i uninstalled superSU then went to the market and downloaded and updated that didn't work it was still the same
no i have downloaded and installed from customer recovery and when i open superSU it says i need to manually re-root my phone so i guess i need to re flash my rom from original post?
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Zen Arcade said:
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Click to expand...
Click to collapse
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Remove them from SU list. Restart app and approve the SU request again.....
dicksteele said:
Remove them from SU list. Restart app and approve the SU request again.....
Click to expand...
Click to collapse
okay done and no change
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Which apps?
Zen Arcade said:
Which apps?
Click to expand...
Click to collapse
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
mrnewspaper said:
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
Click to expand...
Click to collapse
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Zen Arcade said:
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Click to expand...
Click to collapse
i didn't see those notes but thanks to everyone for all the help and i will look in to stepping back again (i bricked the first time)
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Zen Arcade said:
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Click to expand...
Click to collapse
awesome thank you
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
pavanchirmade said:
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
Click to expand...
Click to collapse
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Zen Arcade said:
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Click to expand...
Click to collapse
I flashed the same one.
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Zen Arcade said:
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Click to expand...
Click to collapse
Here's a screenshot.
That's the correct file...
A deeper dive would involve looking at the permissions and properties of su and daemonsu in /system/xbin as well as a few other SuperSU related files in /system and subdirectories.
If you are running a custom kernel it's possible that it is pushing an older version of SuperSU (or other superuser app).
Do you have only the SuperSU app installed (i.e. no SuperUser or other app in the app drawer)?
Reaching at this point as it's not typical for the current versions of SuperSU to lose root.
One thing you can try is root with current, boot phone, immediately run SuperSU, choose "Full Unroot", reboot boot phone, then shutdown and reflash cf-auto-root and see if it sticks.
As for flash counter, once you get root to stick, you can use Triangle Away to reset that to zero - works for everything but the knox warranty counter.

Categories

Resources