OK, I know this has been asked and asked again, but I have been reading and digging and googling for several days now, and cannot find a solution.
I've got a JB S3 At&t, and wanted to root it, so after reading for a few weeks, I got the "Samsung_Galaxy_S3_ToolKit_v7.0", donated, and got 7.2 (newest version). I flashed with the toolkit to get an unsecured boot image, with SuperSU 1.04, busybox, and TWRP .
Root happened fine. The phone booted, and when I went to open SuperSU (the icon was in my apps), it asked to update the binaries. I said yes, it failed, and the app opened anyway to allow me to access the options. Triangle away worked fine.
The update binaries thing was bugging me, so I updated to SuperSU 1.10 via google store, and the same thing happened, but now I could not access the program after the binary update failed. It still works (triangle away asks and gets permission) but I could not access the program any longer. It just closes after it informs me that updating the binaries failed.
I have tried installing the program as an app, pushing an APK, and installing a zip from recovery. No matter what I do, it ends up the same.
I have also re-flashed the boot several times, and tried a different method using Odin directly and CF-Root. (seems to be the only way to uninstall it) I have tried numerous combinations, but to no avail. I feel like I have done everything I know how to do short of an unroot to stock and try again.
Any helpful suggestions are welcome.
I'd like to be able to use the program, but this is turning into an OCD nightmare. I'd post this in a development forum, but do not have enough posts yet.
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
illmatic24 said:
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
Click to expand...
Click to collapse
Thanks. I ended up doing it the hard way. (I swear I had auto email notification enabled here, or I would have seen your post and tried it)
Anyway, I cleared caches/userdata/wipe cache partition first, then flashed a stock unrooted 4.1.1 rom from here,
Then I used CF-autoroot, and low and behold, SU was showing up as an app. (it was not previously when I used CF-AR)
I let it update itself and bam, it works! Installed adbd insecure, and it works too. (it was not showing up as an app when I did it before either)
Next I added TWRP 2.4.3.0. and everything still works!
Either the stock AT&T rom on this unit had something interfereing with root, or the root image I used in the toolkit has an issue. I'm leaning towards a toolkit issue since when I used it and it installed TWRP 2.4.1.0, I could not get into recovery, just a black screen.
I lieu of this, I'm limiting my use of the toolkit.
Curiously, the toolkit also allows a sideload via TWRP/CWM, but does not provide a driver. Windows 7 cannot recognize the phone in recovery mode with a custom recovery installed, although it does when a stock recovery is. I have yet to find a driver.
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.
Hi Guys,
I am having some issues trying to root my Samsung Galaxy S3. I am currently running the stock Kitkat version of AT&T on my S3(SGH-I747) and trying to root it to be able to install CWM and a custom rom.
I have tried chainfire and towelroot methods.
I used the following tutorial of using ODIN and chainfire image for samsung SGH-I747:youtube.com/watch?v=LwsvPO8jVGE
I was able to get all steps to work and get everything same as the video above except when I install "Root Checker" from android play store it gave me message that "Root method is not properly configured" even after odin showed "Success" after rebooting and applying the patch
I then used the towelroot method by going to the towelroot.eu website on my phone and installing the apk. the towelroot app gave me the message that "I have root and do not need to reboot my device" but Root checker still says that my root is not configured.
I then reset my phone by pressing volume up+power and home button and clearing "Cache" and wiping data" and trying the above methods again but still unable to get the phone to root.
I am completely stumped as to what I am doing wrong. And would really appreciate some help from the pros.I have attached a snapshot of my device info and thanks for the great work and guidance.
Matt
PS. I already made sure that my phone is in the "Developer Mode" and "USB debugging" is enabled
tried another method
Also tried using the casual method but that also failed with the error "Unsupported device" here is the url for the log file:http://pastebin.com/vZRvYH3g
I followed the follwowing thread:
http://forum.xda-developers.com/showthread.php?t=2189536
amti366 said:
Hi Guys,
I am having some issues trying to root my Samsung Galaxy S3. I am currently running the stock Kitkat version of AT&T on my S3(SGH-I747) and trying to root it to be able to install CWM and a custom rom.
I have tried chainfire and towelroot methods.
I used the following tutorial of using ODIN and chainfire image for samsung SGH-I747:youtube.com/watch?v=LwsvPO8jVGE
I was able to get all steps to work and get everything same as the video above except when I install "Root Checker" from android play store it gave me message that "Root method is not properly configured" even after odin showed "Success" after rebooting and applying the patch
I then used the towelroot method by going to the towelroot.eu website on my phone and installing the apk. the towelroot app gave me the message that "I have root and do not need to reboot my device" but Root checker still says that my root is not configured.
I then reset my phone by pressing volume up+power and home button and clearing "Cache" and wiping data" and trying the above methods again but still unable to get the phone to root.
I am completely stumped as to what I am doing wrong. And would really appreciate some help from the pros.I have attached a snapshot of my device info and thanks for the great work and guidance.
Matt
PS. I already made sure that my phone is in the "Developer Mode" and "USB debugging" is enabled
Click to expand...
Click to collapse
After rooting with Towelroot you have to install SuperSU from the store. Then open and let it update its binary.
You dont need root to get cwm.
DocHoliday77 said:
After rooting with Towelroot you have to install SuperSU from the store. Then open and let it update its binary.
You dont need root to get cwm.
Click to expand...
Click to collapse
Hi Doc, I was able to follow one of your other treads at "http://forum.xda-developers.com/galaxy-s3-att/help/att-bricked-s3-help-please-t2817566/page2" and install TWRP. I think my issue was that the firmware had got upgraded to the NE4 and I was not flashing the correct bootloaders.
I do have one more question and I am not sure if it is a ROM related issue or a phone setting. I will understand if you think I should ask in the ROM thread. I flashed CM11 on the phone after installing TWRP and rooting with superSu. I noticed that the led buttons on the bottom of the phone are disabled(the back and the setting buttons) do you know if this is a changeable setting(pic attached)? I would hate to loose the screen-space at the bottom to the buttons and even though that's standard Kitkat layout I wont mind being able to use the phone led buttons to go back and change settings.
I installled the follwoing version of cm11: cm-11-20140805-SNAPSHOT-M9-d2lte.zip from (http://download.cyanogenmod.org/?device=d2lte)
Thanks for your help and guidance.
Matt
Im not sure about that one. I don't use CM so im not very familiar with all of its different settings. Someone else may have the answer for you though. If not, then ask in the rom thread like you mentioned.
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.
Hey, today I flashed Lionage 14.1 in my Sm-j510fn with twrp. Now i wanted to installiert Root and flashed Root in my device. In the dev settings i ticked Apps and ADB. But if i now want to open Root checker and check it, it says that my device is not rooted. In Es file Explorer i also can not tick Root mode.
Anyone help PLZ
Thanks
DoppelM said:
Hey, today I flashed Lionage 14.1 in my Sm-j510fn with twrp. Now i wanted to installiert Root and flashed Root in my device. In the dev settings i ticked Apps and ADB. But if i now want to open Root checker and check it, it says that my device is not rooted. In Es file Explorer i also can not tick Root mode.
Anyone help PLZ
Thanks
Click to expand...
Click to collapse
Download a recovery flashable zip from here: and flash in TWRP.
http://www.supersu.com/download
Sent from my N9515 using Tapatalk
bcrichster said:
Download a recovery flashable zip from here: and flash in TWRP.
http://www.supersu.com/download
Click to expand...
Click to collapse
I would not give up so soon. At least try a clean installation of ROM and addonsu in one twrp session.
DoppelM said:
Hey, today I flashed Lionage 14.1 in my Sm-j510fn with twrp. Now i wanted to installiert Root and flashed Root in my device. In the dev settings i ticked Apps and ADB. But if i now want to open Root checker and check it, it says that my device is not rooted. In Es file Explorer i also can not tick Root mode.
Anyone help PLZ
Thanks
Click to expand...
Click to collapse
https://download.lineageos.org/extras you can download it here just choose 14.1 between the 3 arm arm64 x68 depending on your device. flashing lineageOS nightlies doesnt automatically root your device
shadow_blitz said:
you can download it here just choose 14.1 between the 3 arm arm64 x68 depending on your device. flashing lineageOS nightlies doesnt automatically root your device
Click to expand...
Click to collapse
he said he already did that.
why can no one give a real answer to this issue. Installed the correct extras, says root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
It was a lot better when it was part of the rom, why the decision to remove it? all it causes is headache and people reverting away from the rom.
wrecche said:
he said he already did that.
why can no one give a real answer to this issue. Installed the correct extras, says root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
It was a lot better when it was part of the rom, why the decision to remove it? all it causes is headache and people reverting away from the rom.
Click to expand...
Click to collapse
We are talking about an unofficial LineageOS? Maybe you should talk with the person that built it.
any solution ?
Me 2
I am having the same issue.
I installed the su extra package using TWRP 3.2 .
I now have the "root" and "manage root acesses" menus under development options.
I enabled "apps and adb" option.
When I type "su" in any terminal app (including the built in one), I get "permission denied"
With root access set to "disabled", when I type "su" I get "command not found".
With root access set to "apps and adb", if I run a root checker app or try to use any app that requires root, I do not get a prompt to allow root access, and I do not get any notifications from Privacy Guard, either.
The root checker apps all say that I do not have root.
Even after running apps that should request root, when I look in the "manage root accesses" menu, it says that no apps have requested root yet.
What gives? I am really trying to use the built in root access features, I do not want to use SuperSU. Partly because SuperSU did not work either (same behavior as above), and because I don't like SuperSU's bloated code and proprietary implementation.
I really hope we can get this working, If I can provide any other info to anyone who wants to help, let me know.
I am seeing a lot of posts about this in relation to Lineage 14.1 and 15.1 and roms based on those builds. The issue is apparent on multiple different devices, so I suspect it is an issue with the base lineage source somewhere. I havn't looked at the source, though, so I don't really know... All I do know is that this is very frustrating.
m1st3r3 said:
I am having the same issue.
I installed the su extra package using TWRP 3.2 .
I now have the "root" and "manage root acesses" menus under development options.
I enabled "apps and adb" option.
When I type "su" in any terminal app (including the built in one), I get "permission denied"
With root access set to "disabled", when I type "su" I get "command not found".
With root access set to "apps and adb", if I run a root checker app or try to use any app that requires root, I do not get a prompt to allow root access, and I do not get any notifications from Privacy Guard, either.
The root checker apps all say that I do not have root.
Even after running apps that should request root, when I look in the "manage root accesses" menu, it says that no apps have requested root yet.
What gives? I am really trying to use the built in root access features, I do not want to use SuperSU. Partly because SuperSU did not work either (same behavior as above), and because I don't like SuperSU's bloated code and proprietary implementation.
I really hope we can get this working, If I can provide any other info to anyone who wants to help, let me know.
I am seeing a lot of posts about this in relation to Lineage 14.1 and 15.1 and roms based on those builds. The issue is apparent on multiple different devices, so I suspect it is an issue with the base lineage source somewhere. I havn't looked at the source, though, so I don't really know... All I do know is that this is very frustrating.
Click to expand...
Click to collapse
I bet you have installed unofficial lineageOS. On all my officially supported devices root works as expected.
kurtn said:
I bet you have installed unofficial lineageOS. On all my officially supported devices root works as expected.
Click to expand...
Click to collapse
Essentially saying 'it works great for me, you must be doing something wrong' isn't actually a very practical troubleshooting approach. While there is definitely the possibility that I am doing something wrong, troubleshooting will reveal if I have made a mistake and will also benefit the loads of other people posting about similar or same issues. That's why we have forums, right?
You bet wrong, do I win anything?
Like I mentioned, I have experienced this issue with both Lineage 14.1, 15.1, as well as unofficial builds and ROMs based on Lineage.
It is hit or miss, in most cases I just tried flashing different ROMs on my devices until I find one that has working built-in root.
I had a lot of issues installing the official builds on my 'bacon' device, I eventually went with resurrection remix instead. That was the only Oreo build that built-in root packages worked with.
In the case of my 'klte' (g900v variant), I installed 7 different Oreo based ROMs. Since there is no official Lineage build for the 'klte' (which is sad, it's a great device), I was using all unofficial builds in the case of this device. They were all based on Lineage, or just unofficial Lineage builds focused on supporting the klte. I couldn't get the built in root functionally working on any of these builds (Lineage unofficial 14.1 & 15.1, Havoc OS, etc). If anyone thinks it will help, I can elaborate further on which packages and versions I used...
Rooted lineageos not recognized
I have exactly the same issue with my Samsung S3 I9300.
I flashed it with lineageos using CWM and thereafter I flashed with the extra armsu. I cannot see anything I could have done wrong. However, neither Titanium nor a root checker recognizes the rooted state. As far as I can see there are quite many having the same issue. Unfortunately most replies are just best guesses like flash with TRWP or add gapps (the katter didn't solve the oroblem either. I am not an expert but I successfully got rid of extremely persisting boot loops most probably caused by Magix which I avoided therefore with this try to root the lineageos.
warbexda said:
I have exactly the same issue with my Samsung S3 I9300.
I flashed it with lineageos using CWM and thereafter I flashed with the extra armsu. I cannot see anything I could have done wrong. However, neither Titanium nor a root checker recognizes the rooted state. As far as I can see there are quite many having the same issue. Unfortunately most replies are just best guesses like flash with TRWP or add gapps (the katter didn't solve the oroblem either. I am not an expert but I successfully got rid of extremely persisting boot loops most probably caused by Magix which I avoided therefore with this try to root the lineageos.
Click to expand...
Click to collapse
So what's your goal? Just moaning or asking for help? In the 2nd case you should provide more details like filenames and procedures.
And yes. Root works well on my S3.
kurtn said:
So what's your goal? Just moaning or asking for help? In the 2nd case you should provide more details like filenames and procedures.
And yes. Root works well on my S3.
Click to expand...
Click to collapse
Yes you are right. Just moaning is not an option. Here are the details:
1. Flashed with lineage-14.1-20181025-nightly-i9300-signed.zip using CWM
2. Installed Titanium (with "not rooted" as result of course)
3. Installed addonsu-15.1-arm-signed.zip using CWM and changed the setting to "apps and ADB" , an option which I didn't have before - however, with no effect on Titanium
4. Checked root status with "Root Checker" which resulted in "not rooted"
5. Installed open_gapps-arm-7.1-pico-20181120.zip using CWM (because someone suggested it as solution) - with no effect.
Now to the observed "irregularities":
1. The installation of the "addonsu" which I repeated had a "Warning: No file_contexts." but ended successfully
2. The reboot metioned: " Root access possibly lost. Fix?" which I replied with "Yes fix root (/system/xbin/su)"
Possibly worth to be mentioned: Titamium tries with command "system/bin/su". I've checked that su resides in both directories bin and xbin with identical size
In writing this I realized the version mismatch 14.1 lineageos and 15.1 addonsu. I uninstalled addonsu 15.1 and installed addonsu 14.1 instead and THIS SOLVED THE PROBLEM
Many thanks for your help.
warbexda said:
Yes you are right. Just moaning is not an option. Here are the details:
1. Flashed with lineage-14.1-20181025-nightly-i9300-signed.zip using CWM
2. Installed Titanium (with "not rooted" as result of course)
3. Installed addonsu-15.1-arm-signed.zip using CWM and changed the setting to "apps and ADB" , an option which I didn't have before - however, with no effect on Titanium
4. Checked root status with "Root Checker" which resulted in "not rooted"
5. Installed open_gapps-arm-7.1-pico-20181120.zip using CWM (because someone suggested it as solution) - with no effect.
Now to the observed "irregularities":
1. The installation of the "addonsu" which I repeated had a "Warning: No file_contexts." but ended successfully
2. The reboot metioned: " Root access possibly lost. Fix? Which I replied with "Yes fix root (/system/xbin/su)"
I hope this helps.
Click to expand...
Click to collapse
Ha! For a 14.1 Rom you need a 14.1 addonsu
For future readers:
There are two versions of lineage os root images, 32 and 64 bit. Please check that you installed correct one, this way I solved this problem!
Solution
wrecche said:
he said he already did that.
why can no one give a real answer to this issue. Installed the correct extras, says root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
It was a lot better when it was part of the rom, why the decision to remove it? all it causes is headache and people reverting away from the rom.
Click to expand...
Click to collapse
Did you get any solution???????
Atharva C said:
Did you get any solution???????
Click to expand...
Click to collapse
Solution for what? I think lineageOS people found the best way to ship a non-pre-rooted ROM with native root solution.
NO ROOT Access
kurtn said:
Solution for what? I think lineageOS people found the best way to ship a non-pre-rooted ROM with native root solution.
Click to expand...
Click to collapse
Are u able to provide a way to Root?
Atharva C said:
Are u able to provide a way to Root?
Click to expand...
Click to collapse
Flash the su package from download/extras matching your lineageOS version. Enable root in settings/developer
NO ROOT Access yet #failed
kurtn said:
Flash the su package from download/extras matching your lineageOS version. Enable root in settings/developer
Click to expand...
Click to collapse
Root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.