Develop Bugs

[Q] SuperSU not updating, etc

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.

Rooting t800 kind of gone wrong advice needed

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.

Disabling Knox on Tab S 8.4 4G

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.

Why won't SuperSU update on CM13?

My Tab Pro 8.4 has been bootloader unlocked since I got it months ago. It has always run a custom ROM, usually just CM12 nightlies with root from SuperSU flashed in TWRP and no Xposed or other "fancy" stuff installed. Since the CM nightlies shifted to CM13 I can't get SuperSU to "update" (the notice that says you must update SuperSU). I've tried reflashing, I've tried wiping and doing new installation from CM13, I've tried different versions of SuperSU. Nothing works to successfully install an updated SuperSU. I've never had this problem before. I've read everything I can find and found several places where something like this is being discussed, but no path to resolution. How can I fix this?

I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.

Sicron said:
I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.
Click to expand...
Click to collapse
I've tried using only the built-in root method. I set it to "both APPS and ABP" (or whatever that last option is). That's not enough for Root Explorer, not enough for PIE Control, not enough for AdAway, at least in my case. All those apps still indicate that I'm not rooted.

Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.

Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Hmmm. Well, that'd be a great solution for me so I'll give it another go. Wipe wipe wipe, flash a CM13 daily, flash CM13 GAPPS, wipe Dalvic cache and cache, reboot. In Settings, enable Developer Options, set Root Access to Apps and ADB. Reboot. If that's not the recommended procedure I hope someone will let me know.

Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Well, maybe the problem I have is different than the one I THOUGHT I had. Wiped, installed CM13 daily, installed CM13 GAPPS, set Root Access in System/Developer Options/Root Access to Apps and ADB. I guess root access exists but I'm not sure. In Root Explorer I CAN switch folders from Read/Write to Read Only (normally a root only option) and AdAway installed and ran fine. BUT -- in PIE Control I still get "Can not, rooted only" when I try to use the "Back" command. There is often a "hashtag" (or "pound sign") symbol in the Status Bar, just as there would be if I needed to update SuperSU, but the symbol is on the far RIGHT and doesn't correspond to any message in the drop down box. Plus, I have never seen the pop up box that normally appears to ask me if I want to grant root access to an app or process. So, what am I? Partially rooted?

It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)

otyg said:
It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)
Click to expand...
Click to collapse
What I'm reading here makes sense but there must be another variable. My phone (Moto X Pure) is running a custom MM ROM, SuperSU DOES install and run just fine, I get all the expected root prompts and controls and the Back button (which requires root) works in PIE Control. I'm guessing, therefore, that the "problem" lies with CM13 as a specific MM ROM rather than with all MM ROMs. Time to flash a different MM ROM on my SM-T320.

Snapchat gives "login temporarily failed" error with CM ROM

Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!

saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.

NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!

I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.

This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk

Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app