Database Info

Last chance to root

I have seen this discussed in several places, but I think a formal thread on the issue is in order.
Jelly Bean Has been updated with rock solid security and, so far, the only known way to root Jelly Bean at the moment is to unlock the bootloader and flash the su binary from a custom recovery. It is possible, however unlikely, that some dev will find a way to root jellybean that doesn't require unlocking.
If you wish to have root access with Jelly Bean without unlocking, it is highly reccomended that you root your tablet before updating.
Before updating, download the SuperSU app from the market, and let it update the su binary (Rootkeeper has failed to keep root with Superuser on the tf300). Make a backup withVoodoo OTA Rootkeeper. If there already exists a backup, delete it and backup again so that your backup is the SuperSU binary.

Do we have to uninstall Superuser and then install SuperSU or can both be installed?

BTrack said:
Do we have to uninstall Superuser and then install SuperSU or can both be installed?
Click to expand...
Click to collapse
Both can be installed. Just make sure SuperSU updates the binary so that it becomes the dominant app.

BTrack said:
Do we have to uninstall Superuser and then install SuperSU or can both be installed?
Click to expand...
Click to collapse
There's no upside to keeping Superuser if you have SuperSU installed. I deleted it to avoid any confusion personally.

My tf700 is due to arrive next Wednesday and I assume it will want to update when I start setting it up and rooting it, can I dismiss the update notice until I am ready?

maxal said:
My tf700 is due to arrive next Wednesday and I assume it will want to update when I start setting it up and rooting it, can I dismiss the update notice until I am ready?
Click to expand...
Click to collapse
Yes, you can postpone the update.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.

maxal said:
My tf700 is due to arrive next Wednesday and I assume it will want to update when I start setting it up and rooting it, can I dismiss the update notice until I am ready?
Click to expand...
Click to collapse
Also if it has pre .30 firmware you might consider unlocking it and creating the nvflash files for it if you ever plan on doing anything beyond rooting.

rightonred said:
I have seen this discussed in several places, but I think a formal thread on the issue is in order.
Jelly Bean Has been updated with rock solid security and, so far, the only known way to root Jelly Bean at the moment is to unlock the bootloader and flash the su binary from a custom recovery. It is possible, however unlikely, that some dev will find a way to root jellybean that doesn't require unlocking.
If you wish to have root access with Jelly Bean without unlocking, it is highly reccomended that you root your tablet before updating.
Before updating, download the SuperSU app from the market, and let it update the su binary (Rootkeeper has failed to keep root with Superuser on the tf300). Make a backup withVoodoo OTA Rootkeeper. If there already exists a backup, delete it and backup again so that your backup is the SuperSU binary.
Click to expand...
Click to collapse
I've lost root with .26 and .30. have always been able to re root with debugfs.
how can i maintain root this time? i use voodoo each time, and i have deleted su copy, then resaved it, that didn't work last time either.
i have superuser AND supersu installed. i can't uninstall superuser.
if i buy the pro key for supersu, will that save my root?

Man, I'd root if I could but I haven't had any luck. I run DebugFS and it seems to be only partially rooted. Sometimes the Superuser log shows the shell was given access. Root Explorer seems OK. But Superuser Update Fixer, Titanium, Root Checker, Terminal Emulator, and MyBackup all say they've been denied. I don't know what else to do. I've tried all the various fixes in the forums.

Also to note you need to be rooted to use the SuperSU app. I have always been rooted via debugfs method and decided I wanted to preserve come JB. I installed SuperSU and it asked for root permissions. After that I ran the binary updater, and then deleted superuser. THEN I went to OTARootkeeper and deleted old backup, and rebacked up. Now when programs ask for root access the SuperSU asks for root permissions so I know it's worked.

neo1738 said:
Also to note you need to be rooted to use the SuperSU app. I have always been rooted via debugfs method and decided I wanted to preserve come JB. I installed SuperSU and it asked for root permissions. After that I ran the binary updater, and then deleted superuser. THEN I went to OTARootkeeper and deleted old backup, and rebacked up. Now when programs ask for root access the SuperSU asks for root permissions so I know it's worked.
Click to expand...
Click to collapse
What is "the binary updater"? Last OTA, I had SuperSU and Voodoo OTA and lost root, so I'm a bit concerned there may be something I should have done that I missed. I currently have SuperSU (uninstalled old Superuser) and Voodoo OTA. All the boxes are checked on my Voodoo OTA dialog including "protected su backup".

redheadplantguy said:
I've lost root with .26 and .30. have always been able to re root with debugfs.
how can i maintain root this time? i use voodoo each time, and i have deleted su copy, then resaved it, that didn't work last time either.
i have superuser AND supersu installed. i can't uninstall superuser.
if i buy the pro key for supersu, will that save my root?
Click to expand...
Click to collapse
I can't see what the problem is. Make sure all of the checkboxes are checked in Voodoo and you should be good to go. superuser can be uninstalled using the root uninstaller app.
das0527 said:
Man, I'd root if I could but I haven't had any luck. I run DebugFS and it seems to be only partially rooted. Sometimes the Superuser log shows the shell was given access. Root Explorer seems OK. But Superuser Update Fixer, Titanium, Root Checker, Terminal Emulator, and MyBackup all say they've been denied. I don't know what else to do. I've tried all the various fixes in the forums.
Click to expand...
Click to collapse
Root with debugfs seems to be iffy. Try opening the superuser app, then switch out of it. If superuser is running in the background, the apps should be granted root access.

Also, to restore, you just:
1. Run SuperSU manually once
2. Run Voodoo OTA and restore
In that order, right?

Wonder if I'm good?
By default does OTA Rootkeeper keep the SuperSU or Superuser APK? I had SuperSU installed before installing and backing up root. Was curious if I am good to go, or if I will have to redo it?
rightonred said:
Before updating, download the SuperSU app from the market, and let it update the su binary (Rootkeeper has failed to keep root with Superuser on the tf300). Make a backup withVoodoo OTA Rootkeeper. If there already exists a backup, delete it and backup again so that your backup is the SuperSU binary.
Click to expand...
Click to collapse

droidhaxxor said:
By default does OTA Rootkeeper keep the SuperSU or Superuser APK? I had SuperSU installed before installing and backing up root. Was curious if I am good to go, or if I will have to redo it?
Click to expand...
Click to collapse
Whichever app manages root access at the time the backup is made, it backs up the binary for that app.If that binary is the supersu binary than you're good to go. The apk and the binary are separate files though. if you loose the app, you can simply reinstall it from the market. The binary requires root access to manage.

I just picked up my infinity today and want to root it but I usually keep it stock for a little does this mean if I'm on .30 I have to root before I take the job update?
Sent from my EVO using xda app-developers app

scataldo721 said:
I just picked up my infinity today and want to root it but I usually keep it stock for a little does this mean if I'm on .30 I have to root before I take the job update?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
we just don't know if the root method will work after the jb update. we also don't know if a rootkeeper will even work but might as well root now as then you have 2 possible methods of obtaining root once you get the jb update.

fatpandas said:
we just don't know if the root method will work after the jb update. we also don't know if a rootkeeper will even work but might as well root now as then you have 2 possible methods of obtaining root once you get the jb update.
Click to expand...
Click to collapse
If I want to root and unlock should I do it now or after job?
Sent from my EVO using xda app-developers app

scataldo721 said:
If I want to root and unlock should I do it now or after job?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
if you want to root, i would definitely do it now. mainly because the process if very easy and MOST people have had no problems with it. We're not sure what will happen once JB comes out though.
as for unlocking, i'm not too sure. only thing to be aware of would be that you won't get the OTA after unlocked so you would have to flash it manually. though at that point, you may just go flash some custom roms. just take those into consideration and see what is more important to you.

Bump since jb is out.

Cannot restore root

Before I upgraded to JB, I saved the root with OTA Root keeper and after upgrading I restored back root with it but none of my application that require root are working. In OTA Root Keeper it has all the all the checkboxes checked (except Root Permission Granted). I have installed SuperUser and also tried Su but it does not work.
Any suggestion?

reboot the Infinity and then check in OTA RootKeeper and see if it still reports root.

ajamils said:
Before I upgraded to JB, I saved the root with OTA Root keeper and after upgrading I restored back root with it but none of my application that require root are working. In OTA Root Keeper it has all the all the checkboxes checked (except Root Permission Granted). I have installed SuperUser and also tried Su but it does not work.
Any suggestion?
Click to expand...
Click to collapse
If what johnlgalt suggested doesn't work, this may work. No guarantees on anything.
http://forum.xda-developers.com/showthread.php?t=1886460

Private Pyle said:
If what johnlgalt suggested doesn't work, this may work. No guarantees on anything.
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Has anyone confirmed that this will work on ASUS tablets?

Restarting did not fix anything so I installed Root Checker from market and it is saying that I do not have proper root permissions.

In OTA Rootkeeper, it is not showing temp unroot, is it? Also check Superuser app (info page)....

...also lost root!
I have the same probs like the others befor.
- Did a clean install of FW .30
- Then rooted the Infinity with "One-Click" Method ...every thing´s fine!
- Installed Root-Keeper and did backup
- Installed the JB Update from internal SD
...restarted the Pad and lost Root!
I checked it with Root-Keeper and there is no BackUp!
PLEASE HELP!

I did the same but in superuser I also enabled OTA keeper under info. That might have made a difference.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk

freaky01 said:
I have the same probs like the others befor.
- Did a clean install of FW .30
- Then rooted the Infinity with "One-Click" Method ...every thing´s fine!
- Installed Root-Keeper and did backup
- Installed the JB Update from internal SD
...restarted the Pad and lost Root!
I checked it with Root-Keeper and there is no BackUp!
PLEASE HELP!
Click to expand...
Click to collapse
Eexact same thing happened to me. You will need to downgrade to .30 to restore root. Instructions are in the all-in-one thread. This time, do the temp unroot option in rootkeeper before installing jb.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Why there istnt a way to root with one click like under ICS.......

DirtyIdiot said:
Why there istnt a way to root with one click like under ICS.......
Click to expand...
Click to collapse
Because no one has finished the extremely time consuming and hard work and found one yet. If you need root just unlock and flash SU.
Next?

freaky01 said:
I have the same probs like the others befor.
- Did a clean install of FW .30
- Then rooted the Infinity with "One-Click" Method ...every thing´s fine!
- Installed Root-Keeper and did backup
- Installed the JB Update from internal SD
...restarted the Pad and lost Root!
I checked it with Root-Keeper and there is no BackUp!
PLEASE HELP!
Click to expand...
Click to collapse
OTA rootkeeper only works for OTA updates. If you install using the internal SD method you will lose root because it erases the files OTA rootkeeper puts there. Sorry there is nothing you can do to get root back unless you have an unlocked bootloader.
To OP:
Chances are you forgot to temp unroot before doing the OTA, many people are reporting rootkeeper failed if they forgot to temp unroot before OTA.
Try manually installing superuser, maybe that will do it
Check with an app like root checker
If you already have superuser installed try uninstalling and reinstalling it, sometimes that works if its just superuser being annoying.
Hope that helps :/

Just to give an update, I was able to re-root but only after downgrading to ICS. I downgraded to ICS, rooted the device and then upgraded it to JB. Everything is good now.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

It's not working for me...
From ICS 9.4.5.30 I rooted using DebugFS, which installed superuser
Then installed RootKeeper, click on Protect Root, then click on Temp Un-Root
Upgraded to JB 10.4.4.16 through SD card
Open RootKeeper but no Restore button is there
I have unlocked bootloaders prior to all that.
Please help me. This is quite frustrating.

lost root on my tf700 when i updated to .18

So just wondering I have OTA root keeper and superuser SU but i guess when i went from .16 to .18 somehow OTA root keeper lost my root and now I am un rooted without a way to get it back from what I can tell is there anyway to recover this since at one point I did have a protected su with root keeper.

Neriac said:
So just wondering I have OTA root keeper and superuser SU but i guess when i went from .16 to .18 somehow OTA root keeper lost my root and now I am un rooted without a way to get it back from what I can tell is there anyway to recover this since at one point I did have a protected su with root keeper.
Click to expand...
Click to collapse
Try this, download superuser (not superSU), open the app, then download OTA rootkeeper, install and open up, see if you have the "restore" option.

Gave it a try its detecting but doesn't seem the SU survived the OTA update here are some pic's of what I got when I tried it if it helps
imgur.com/zKqqa
imgur.com/Sj7B1
imgur.com/lbkkf

Neriac said:
Gave it a try its detecting but doesn't seem the SU survived the OTA update here are some pic's of what I got when I tried it if it helps
imgur.com/zKqqa
imgur.com/Sj7B1
imgur.com/lbkkf
Click to expand...
Click to collapse
Kinda worried now, is this a common problem or an isolated incident?

Did you use supersu prior to root or just supersu??
Sent from my ASUS Transformer Pad TF700T using xda premium

Somebody know how fix it? I want unlock bootloader, but i worried about warranty. If i can lock bootloader later when i need it, i will unlock tf700 quickly. Unless i`m wrong

Currently this is NO WAY to relock bootloader after you unlocked, so if you want just root your device for now.
Sent from my ASUS Transformer Pad TF700T using xda premium

pileot said:
Kinda worried now, is this a common problem or an isolated incident?
Click to expand...
Click to collapse
I had backed up root with Voodoo OTA RootKeeper SuperSU but lost root in the last update. I uninstalled Voodoo, and then reinstalled it and my root was back.

buhohitr said:
Did you use supersu prior to root or just supersu??
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
I had superuser and OTA root keeper prior to update from .16 to .18 seemed to work from ICS to JB but guess this last update did something that possibly superuser and OTA couldn't protect the su backup from being wiped.

Neriac said:
I had superuser and OTA root keeper prior to update from .16 to .18 seemed to work from ICS to JB but guess this last update did something that possibly superuser and OTA couldn't protect the su backup from being wiped.
Click to expand...
Click to collapse
Give this a shot, open up your superuser and keep it opens, also download SuperSU, open it up also, then download and reinstall OTA root keeper, launch the program and see if you have the option to restore root. I think you should have check the option "protect" root before the update. If you only use "temp unroot", sometime it works sometime it doesn't.

Confirmed. I already had Superuser (and Elite!) installed, as well as Voodoo OTA Rootkeeper, from my trials with the last upgrade.
After installing the update, I simply opened Voodoo OTA Rootkeeper, restore root, closed Voodoo OTA Rootkeeper, re-opened Voodoo OTA Rootkeeper (to verify all 5 check marks show up) and then ran Titanium to make sure it was able to obtain root privileges, and finally verified that the su binary was the most current in Superuser.
Worked like a charm.

didn't work for me,
i had a copy of su,
and temp unrooted.
but i installed the zip file. could that be the reason? (cause on the fly always failed!)
tried to uninstall voodoo and reinstall. open superuser and super SU and then open ota,
all didn't work.
any idea?
geri

I did the swap from prime to infinity. I rooted and installed OTA rootkeeper immediately.
An ICS and JellyBean upgrade later I used it to restore root.
I don't know why it is failing for others
Sent from my MB855 using Tapatalk 2

If you use ota or the dlpkgfile it works, with zip files it does not work!

[Q] Root trouble after updates (JB and Moonshine S-Off)

Hey sorry to bother you but you seem like a guru in almost every Android topic but i have an issue at hand.
I have a HTC One SV from Boost Mobile. At first i was running ICS with root and CWM as my recovery, as your aware the JB update came out and i really wanted to update so i did the method from here http://forum.xda-developers.com/show...0&postcount=18 i was successful in the update, i did not check if i still had roost after the update. So i also noticed that there was a moonshine s-off method available and i proceeded with the method and successfully removed s-off. I also noticed that by doing the s-off method it also included root; so then i decided to check if root survived but i come to find out that i lost it. My original root i was using was ChainsDD superuser and the moonshine uses SuperSU, what options can i do in order to fix and gain root again? or did the JellyBean update patched root access?

monkijuan said:
Hey sorry to bother you but you seem like a guru in almost every Android topic but i have an issue at hand.
I have a HTC One SV from Boost Mobile. At first i was running ICS with root and CWM as my recovery, as your aware the JB update came out and i really wanted to update so i did the method from here http://forum.xda-developers.com/show...0&postcount=18 i was successful in the update, i did not check if i still had roost after the update. So i also noticed that there was a moonshine s-off method available and i proceeded with the method and successfully removed s-off. I also noticed that by doing the s-off method it also included root; so then i decided to check if root survived but i come to find out that i lost it. My original root i was using was ChainsDD superuser and the moonshine uses SuperSU, what options can i do in order to fix and gain root again? or did the JellyBean update patched root access?
Click to expand...
Click to collapse
Did you flash a recovery like cwm or twrp, after the jb update?

old.splatterhand said:
Did you flash a recovery like cwm or twrp, after the jb update?
Click to expand...
Click to collapse
yes i i flashed the CWM recovery for JB but originally it had the CWM ICS recovery, i dont know if that makes a difference.

monkijuan said:
yes i flashed the recovery out from the OTA zip file
Click to expand...
Click to collapse
You need custom recovery for boost, look here.
From within the custom recovery you should be able to flash something like this.
This should bring you Supersu app & SU binaries.

old.splatterhand said:
You need custom recovery for boost, look here.
From within the custom recovery you should be able to flash something like this.
This should bring you Supersu app & SU binaries.
Click to expand...
Click to collapse
OMG!! I have ROOT once again!! Thank you so much for the information and for turning me on to TWRP, i love how the system is set up. Kudos my friend.
God live XDA-Developers!

I'm glad, it worked for you :good:

Trying to root with Saferoot but SuperSU fails to disable KNOX

I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?

voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
I'm not sure if this works at this point but Chainfire had a super SU zip especially for 4.3 roms on his website. This may fix your issue
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
If you have root before 4.3, my experience may be helpful to you: http://forum.xda-developers.com/showpost.php?p=49334077&postcount=21
Though, I didn't have problem with KNOX, my problem was SuperSU fail to update su binary.

voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
Have you verify that your phone successfully rooted? Check it with root checker from the market.

ShapesBlue said:
I'm not sure if this works at this point but Chainfire had a super SU zip especially for 4.3 roms on his website. This may fix your issue
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Have you got a link? I'm looking but not finding.
nook2hd said:
If you have root before 4.3, my experience may be helpful to you: http://forum.xda-developers.com/showpost.php?p=49334077&postcount=21
Though, I didn't have problem with KNOX, my problem was SuperSU fail to update su binary.
Click to expand...
Click to collapse
I did have my phone rooted prior to the OTA. I've been rooting my phones for years, but have never messed with adb shell. I read your post before posting this question but it is kind of greek to me. I've always used the usual run this, run that, Odin this, CWM that type approaches. My SuperSU binary won't update because it can't disable KNOX.
buhohitr said:
Have you verify that your phone successfully rooted? Check it with root checker from the market.
Click to expand...
Click to collapse
I already used root checker to verify the phone did not root successfully.

voigts said:
Have you got a link? I'm looking but not finding.
Click to expand...
Click to collapse
I have the zip file. I downloaded it awhile ago. It's dated from October.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
---------- Post added at 01:44 PM ---------- Previous post was at 01:32 PM ----------
voigts said:
Have you got a link? I'm looking but not finding.
Click to expand...
Click to collapse
Best bet is his thread here on xda. He has a flashable zip
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.

voigts said:
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
Click to expand...
Click to collapse
Use saferoot to install SuperSu, then run adb command as:
adb shell
You should see "$" prompt
Then type
/system/xbin/su
You should see "#"
Please verify.

buhohitr said:
Use saferoot to install SuperSu, then run adb command as:
adb shell
You should see "$" prompt
Then type
/system/xbin/su
You should see "#"
Please verify.
Click to expand...
Click to collapse
I uninstalled SuperSU that I installed via Google play. I ran saferoot and let it do its thing and install SuperSU. When I get to the part of updating SuperSU, it fails to install. I ran your commands in adb, and I got the #.

voigts said:
I uninstalled SuperSU that I installed via Google play. I ran saferoot and let it do its thing and install SuperSU. When I get to the part of updating SuperSU, it fails to install. I ran your commands in adb, and I got the #.
Click to expand...
Click to collapse
Once you got the # , then run the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
After this open SuperSu app and see if you can update. If updated successfully then reboot your phone.

buhohitr said:
Once you got the # , then run the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
After this open SuperSu app and see if you can update. If updated successfully then reboot your phone.
Click to expand...
Click to collapse
Many thanks. It worked! :good: SuperSU updated just fine, and root checker shows root access. What did these commands actually do and what was the problem?

voigts said:
Many thanks. It worked! :good: SuperSU updated just fine, and root checker shows root access. What did these commands actually do and what was the problem?
Click to expand...
Click to collapse
You have Superuser and SuperSu in your phone and the Superuser is the default one which root no longer working. So these commands basically remove the Superuser "su" executable file, which allowed your SuperSu to be updated and became a default root.

buhohitr said:
You have Superuser and SuperSu in your phone and the Superuser is the default one which root no longer working. So these commands basically remove the Superuser "su" executable file, which allowed your SuperSu to be updated and became a default root.
Click to expand...
Click to collapse
Makes sense. I get the concept. Thank you very much for your help. I Googled over and over and couldn't come up with an answer.

Using Saferoot with Knox disable
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
I had tried the saferoot and it failed several times, until i installed kies 3 here's how finally was able to root my SCH-R530u Us cellular phone with JB 4.3:
downloaded saferoot & unzipped, then installed kies 3 & run it (make sure your phone is detected ok in kies) after kies opens & your phone is recognized open saferoot and run it. wait for the phone to restart, then go to play store and download supesu and install it or update it, then open supersu & it should ask to install binary. that should do it! Hope this helps:victory:

voigts said:
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
Click to expand...
Click to collapse
can you please tell me how did you manage to disable knox because i have the same exact problem tnx

LYwaa said:
can you please tell me how did you manage to disable knox because i have the same exact problem tnx
Click to expand...
Click to collapse
I'd try to help but I know hardly anything about Knox. Try sending a PM to the person
Sent from my SCH-I535 using Xparent ICS Tapatalk 2