Hello,
So as the forum discussion I have the AT&T S3 I747 - Initially I rooted the phone to be able to use it at as a wireless hotspot and everything worked great the method i used was galaxys3root .com (I cant post the actual link <10 posts)
What I thought was a notification OTA triggered me to opening superuser and doing an uninstall/permanent unroot to ensure i didn't brick my phone, well I was wrong about the notification feeling like an idiot i decided to go ahead a reroot the phone again.
I followed the same procedure as linked above this time with problems, I have no Superuser Icon in apps tray, under applications manager it appears but only gives me the option to "Uninstall Updates" and that all
Things I have tried
- installing both versions onto the phone Clockwork mod simply just sits there under "Installing Superuser" Chain version installs but appears to do nothing.
- Used odin to reflash the stock rom then tried the re root process again
- reinstalled the wifi app to see if working but no longer is
I am not looking for a custom rom I like the default one I have I just want the Superuser app to show up again, anyone know what I could do to fix this?
Thanks for all your help
Flash the rooted stock version with Odin
mrhaley30705 said:
Flash the rooted stock version with Odin
Click to expand...
Click to collapse
Thanks for your reply I seem to have got it solved. I downloaded a File Explorer Went into system/Apps found the SuperUser APK opened it, let it install updates and what not after done the app showed back in my apps drawer, installed my wifi mod and superuser granted permissions so everything is good
Questions and help issues go in Q&A and Help section
Thread moved
FNM
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
kingart93 said:
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
Click to expand...
Click to collapse
Have you checked to make sure you haven't lost root? When you install an app from Google play, you get the latest version.
sent from my GS3
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
I did it!!!
Mr. Struck said:
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
Click to expand...
Click to collapse
Yes I finally got it to work I just re rooted the device and superuser was gone. However, i downloaded supersu and it prompted me to update, i did and I was able to bypass knox! I think it was a problem with the method I used to get my phone rooted the first time. The video tutorial I watched the first time told me to uncheck the 2 boxes that come prechecked on odin i believe one of them was auto reboot i cant recall the other one. Then I took out the battery of the phone and selected the root file through mod recovery mode and that was it. The second time around I left the boxes checked and my phone auto restarted. I then downloaded supersu updated,rebooted, and Visalia!!!
Thanks guys I appreciate the help.
[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with this phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
In SuperSU, try the clean-up for reinstallation option.
DocHoliday77 said:
In SuperSU, try the clean-up for reinstallation option.
Click to expand...
Click to collapse
when launching SuperSU it needs root access to begin with and SuperUser wont allow..this clean up for reinstall is still doable?
Get the recovery flashable SuperSU then. It'll get rid of the other one in the process. You can get it from my sig, but it'll need to be updated after.
Hi, I'm super new to this I have no clue what I'm doing, but I did manage to follow the instructions of http://forum.xda-developers.com/gala...-t800-t3079488 and get my t800 rooted.
Until problem occurs, at http://techbeasts.com/2015/05/01/roo...-lollipop-502/ step 9 "Once it has booted up, check out the SuperSu application in the app drawer. If it asks you to update SU binary, update it." When I open supersu app it only ask me to follow someone on google+ but didn't mention anything about update, couldn't find an update option anywhere in the app either.
I ignored this potential problem and then downloaded rootvalidator, everything was green only busy box was yellow and SELinux was blue saying something enforcing, I don't have a screenshot but these 2 were the only one that's not green. I installed busybox free and got busybox in rootvalidator green (from yellow). Not sure if the enforcing part was an issue so I left it like that.
So I use this guide to root t800 is to use xmod, and XMOD actually have their own tutorial on how to root and install and get it to work etc. just didn't have one for this model. I think I made a huge mistake of following their guide after this one, and got mislead not knowing wtf is going on..
I installed xmod and found out it isn't working, I installed kingroot from within xmod app and when I opened kingroot it shows my tab is already rooted. So I was sure it's not a rooting problem, I then found out xmod isn't working because SE is enforcing and I followed the video guide (from xmod faq) on how to make xmod work on enforcing device. I downloaded Link2SD and clear data+ unistalled xmod. But I also clear and unistalled kingroot (and kinguser i think?) and another app that came along with kingroot when i got it (It was in chinese)...
After this I lost root access and when I check rootvalidator it show my device is not rooted anymore. When {I click on supersu it asks me to update normal or from twrp/cwm...
Everything seem to be a mess so I'd like some advice is it better for me just to restore everything back to factory settings and root the device again? Sorry for this long and noob post I'd really appreciate if someone can help me out. Thank you so much!
Edit: Hey Ashyx thanks for replying so fast, I can't reply due to not enough post.
Just to make sure, I just need to go back to download mode and use cf-autoroot-twrp-t800 with odin to root it again. (then it reboots)
After it reboot, turn off and go back to download mode again and install the tar you provided with odin similar to rooting it? Is there any specific options I need to tick or untick in odin?
Thanks again!!
Just reroot that's all you need do.
The same way you did it the first time.
For permissive mode. You need a kernel that allows it.
I have built a stock kernel that will allow you to set permissive mode:
https://www.androidfilehost.com/?fid=24052804347765648
Install with odin.
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
ashyx said:
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
Click to expand...
Click to collapse
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
UPDATE: So now I have managed to try and install the version of superSU that you have released in the dev thread, using TWRP. seemed to work fine, but i still got the same binary missing error.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
ashyx said:
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp
Click to expand...
Click to collapse
So this is what I do.
Power off device.
Restart in Download Mode.
Use Odin to install the cf-autoroot-twrp-t705.tar from the development section.
When device restarts I put supersu version 2.52 (beta) on the devices memory, then turn off device.
Restart in TWRP Recovery mode, hit install, choose the zip file, install, reboot device.
When device reboots, open superuser and get this message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device".
I swear i'm not blonde. :good:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
ashyx said:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
Click to expand...
Click to collapse
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: So I went into my Samsung account and Performed a factory reset. Only had the device a few days so no biggy. Then as it reset i chose not to put in and Samsung details and skip all the options i could, assuming this would help. Flashed cf autoroot with odin, then updated supersu through twrp... still nothing
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
clint.fish said:
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
Click to expand...
Click to collapse
This doesn't make sense. Something is amiss if you can't root with cf_autoroot or twrp. You are the only one as far as I'm aware that has experienced this.
Reactivation lock is under 'Find my phone' in security settings.
clint.fish said:
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Click to expand...
Click to collapse
Chimed in with some feedback but noticed your problem solved after I replied. Unable to delete. Glad to see you're good to go though.