I applied the [UPDATE][JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) to my mz604. I applied it on top of the previous stock rooted version. It appeared to update successfully. Most apps worked as required and no data loss.
However, I did notice that I do not have root access. Vodoo OTA reports that it is rooted but superuser permission not granted. Root Checker reports Status: not rooted. Superuser reports root access denied on all attempts since the update.
I have searched the forums for a similar situation but did not find any. I think it may only be a permissions issue. Does anyone have a suggestion on how this could be resolved? If it means wiping, I may just pass on the root for now since everything is working so well. I only rooted in the first place so that I could edit the wifi file for hotspot use from my phone (ad hoc mode). That edit is still intact. Otherwise the only thing I'm not able to use is the usb stick mount app.
Thanks in advance for any advice.
janegraves said:
I applied the [UPDATE][JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) to my mz604. I applied it on top of the previous stock rooted version. It appeared to update successfully. Most apps worked as required and no data loss.
However, I did notice that I do not have root access. Vodoo OTA reports that it is rooted but superuser permission not granted. Root Checker reports Status: not rooted. Superuser reports root access denied on all attempts since the update.
I have searched the forums for a similar situation but did not find any. I think it may only be a permissions issue. Does anyone have a suggestion on how this could be resolved? If it means wiping, I may just pass on the root for now since everything is working so well. I only rooted in the first place so that I could edit the wifi file for hotspot use from my phone (ad hoc mode). That edit is still intact. Otherwise the only thing I'm not able to use is the usb stick mount app.
Thanks in advance for any advice.
Click to expand...
Click to collapse
Did you update superuser or change any settings in superuser yet? I tried this on Stachres build as well and had some issues.
For what its worth...the EOS nightlies are using SuperSU now and I haven't had any root issues with tibu or anttek FE.
Sent from my Xoom using xda premium
tincbtrar said:
Did you update superuser or change any settings in superuser yet? I tried this on Stachres build as well and had some issues.
For what its worth...the EOS nightlies are using SuperSU now and I haven't had any root issues with tibu or anttek FE.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
No. I didn't change anything, just ran the Stachres update file. It said completed successfully. I did get 26 app updates after reboot, and SuperUser may have been one of them, but I didn't pay attention. I'll try the SuperSU. Do I get it from the forum or the google app store?
UPDATE: I just installed SuperSU and when I open it it gets denied superuser access.
I have tried to use the Universal Root Method but No go.....Security Issue that gives Root has been patched in JB.....
Try this Method...... Its a lot of steps but It will work in the end...
Just flash the latest Super User Zip file after rooting using Universal Root and you'll gain root again. That worked for me. Download it from here http://androidsu.com/superuser/ I used the Superuser-3.1.3-arm-signed.zip
Sent from my SAMSUNG-SGH-I747 using xda premium
I tried that process. Still no root. I even did fix permissions, and shelled in to the root prompt and did the chown and chmod commands. They were successful, but when I reboot, still no root access. It is a mystery.
Is it possible to install the 4.0.4 update over the 4.1.1 without losing everything?
janegraves said:
I tried that process. Still no root. I even did fix permissions, and shelled in to the root prompt and did the chown and chmod commands. They were successful, but when I reboot, still no root access. It is a mystery.
Is it possible to install the 4.0.4 update over the 4.1.1 without losing everything?
Click to expand...
Click to collapse
this method has to flash rom, is there a way to root without flash rom. I flashed recovery, but can't choose zip from sd card, though i put su zip in a external sdcard.
Has anyone tried this method.
This would make things much easier. Universal Root/Flash superuser does this work....
Related
OK. So, this is my first time unlocking the rooting. I used the sdk/adb/fastboot method to unlock the bootloader, which worked. I didn't realize this wasn't root access, so I found another set of files that I used to install clockwork mod recovery and flashed superuser from sd. Rebooted and, just like it's supposed to, Superuser was there in my app tray. But when I go to use root apps, the superuser prompt doesn't come up and they aren't granted root access. Is there something different I need to do being on 4.0.4? This is my first time doing it ever, please be gentle Please help me get root access!
Also was just thinking could there be an issue with adb? Is it possible to use fastboot and not have adb work? When I unlocked the bootloader I don't remember if I had USB debugging on or not. Is there a way to check to see if adb did its thing?
I have like no signal where I'm located, so pulling up links is kinda tough , but I should be able to help a little. Make sure you have the latest version of the superuser zip file to flash via recovery. Also, there is a file that keeps CWM there instead of the stock 4.0.4 recovery replacing it. I think there is an app called root checker or something on the Play Store which should check it.
Sent by pocket technology.
Nexus311 said:
OK. So, this is my first time unlocking the rooting. I used the sdk/adb/fastboot method to unlock the bootloader, which worked. I didn't realize this wasn't root access, so I found another set of files that I used to install clockwork mod recovery and flashed superuser from sd. Rebooted and, just like it's supposed to, Superuser was there in my app tray. But when I go to use root apps, the superuser prompt doesn't come up and they aren't granted root access. Is there something different I need to do being on 4.0.4? This is my first time doing it ever, please be gentle Please help me get root access!
Also was just thinking could there be an issue with adb? Is it possible to use fastboot and not have adb work? When I unlocked the bootloader I don't remember if I had USB debugging on or not. Is there a way to check to see if adb did its thing?
Click to expand...
Click to collapse
If you flash a custom rom it will just stick but if you stay on stock...
Try this
http://forum.xda-developers.com/showpost.php?p=27027436&postcount=8
there is also a zip you can use
http://forum.xda-developers.com/show...13&postcount=2
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
http://nexusshacks.com/nexus-s-hacks/how-to-install-nexus-s-windows-usb-drivers/
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.
Twice I have updated from ICD to JB after getting root on ICS then saving my root with OTA.. however after I get into JB and launch OTA, there is no option to restore root.
Superuser is checked and so is /system supports root protection..
can i get some help? do i have to use SU Elite? :/
Beret67 said:
Twice I have updated from ICD to JB after getting root on ICS then saving my root with OTA.. however after I get into JB and launch OTA, there is no option to restore root.
Superuser is checked and so is /system supports root protection..
can i get some help? do i have to use SU Elite? :/
Click to expand...
Click to collapse
bump
Did you temp unroot before accepting the OTA? I don't think it works unless you do this step.
sbdags said:
Did you temp unroot before accepting the OTA? I don't think it works unless you do this step.
Click to expand...
Click to collapse
I have reverted and upgraded 3 times and never "temp unrooted"
If you have a file explorer look for: /system/usr/we-need-root/su-backup
If that exists and if the perms are correct you can regain root. There are guides (I don't know where) but they walk you through regaining root.
Try the instruction here
http://forum.xda-developers.com/showthread.php?t=1926147
I had OTA RK and it didn't work for me either, for some strange reason I never found out. I installed SuperSU from the Play Store and that worked. It's been a loooooooooooong time since I had stock ROM though, so YMMV.
MartyHulskemper said:
I had OTA RK and it didn't work for me either, for some strange reason I never found out. I installed SuperSU from the Play Store and that worked. It's been a loooooooooooong time since I had stock ROM though, so YMMV.
Click to expand...
Click to collapse
Yeah, several guides suggest that you might have "partial root" and that rmoving/reinstalling supersu restores full root access.
Okay so this is getting a little frustrating now..
I never did untemp before with OTA and so i tried that. I rooted at ICS, saved the root with OTA and then untemp rooted and then upgraded to JB.. however I think i got a partial root because when I look at the OTA app again in JB there was no option to restore root..
so i tried SU E and it saus SU binary not found, i had only checked OTA survival though but there was two apps under the allow list: Root Checker Basic and Superuser. After unckecking ota survival i couldnt recheck them though. So here i am stuck on JB without root again. I have not tried bluewr post yet which i am about to. Also i hope flash still works in jb
Beret67 said:
Okay so this is getting a little frustrating now..
I never did untemp before with OTA and so i tried that. I rooted at ICS, saved the root with OTA and then untemp rooted and then upgraded to JB.. however I think i got a partial root because when I look at the OTA app again in JB there was no option to restore root..
so i tried SU E and it saus SU binary not found, i had only checked OTA survival though but there was two apps under the allow list: Root Checker Basic and Superuser. After unckecking ota survival i couldnt recheck them though. So here i am stuck on JB without root again. I have not tried bluewr post yet which i am about to. Also i hope flash still works in jb
Click to expand...
Click to collapse
Flash will work, you just need to install it either in ICS, or after as a third party app, as Google play doesn't allow download, only update now.
And try either SuperSU or Super User only, not both, and before temp unroot, be sure to update the binary on which ever one you use.
bluewr said:
Flash will work, you just need to install it either in ICS, or after as a third party app, as Google play doesn't allow download, only update now.
And try either SuperSU or Super User only, not both, and before temp unroot, be sure to update the binary on which ever one you use.
Click to expand...
Click to collapse
Update binary? How exactly do i do that? thanks for advice
Beret67 said:
Update binary? How exactly do i do that? thanks for advice
Click to expand...
Click to collapse
The trick is once you rooted, you need to launch superuser, and it will auto update your binary, then install OTA root keeper., then save root, then temp unroot, then upgrade, then use ota to restore root.
http://forum.xda-developers.com/showthread.php?t=1241517&nocache=1
Original devs op instructs to temp unroot.
Oops... double post.
Where'd the delete option go?
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
So I flashed CM 11 and I am really enjoying this ROM. When initially setting up I mistakenly let Google restore my apps. I was not aware that SU was already built into CM 11, so I ended with SuperSU and SU installed at the same time. A few of my rooted apps were allowed root access, but now every time a new app ask for SU permission it is denied.I have deleted SuperSu and rootchecker says I have root.
Does anybody have a suggestion?
Reflash SuperSU from custom recovery.
iBolski said:
Reflash SuperSU from custom recovery.
Click to expand...
Click to collapse
Thanks for the reply. This worked. Is their a problem using SuperSu while SU is running as a system app...should I try to delete SU?
blindman75 said:
Thanks for the reply. This worked. Is their a problem using SuperSu while SU is running as a system app...should I try to delete SU?
Click to expand...
Click to collapse
Not that I know of. I've been using SuperSu all the time. I prefer it because:
I paid for it, so I want to get my money's worth!
Chainfire seems to always be on top of the latest fixes, including how Lollipop may have to require custom kernels, which means unlocked bootloaders. Uh oh.