Database Develop

[Q] Superuser not working after downgrade and re-root

So I finally got around to downgrading my revo to re-root it after the update, but now superuser is not working!
The downgrade worked and the root seemed to go smooth.
I got the "-rwsr-sr-x root root 26248 2011-10-02 18:36 su"
message after rooting with adb so I assumed everything worked.
After downloading and installing superuser nothing is working though.
If I open an app that requires root it cannot gain access.
Also, if I open superuser it says there is an update, but it then crashes when trying to update.
I have even tried the "superuser update fix" app, but that cannot gain root access either.
Any ideas?

same problem here
Same exact thing happened to me...what do I do now?
---------- Post added at 09:11 PM ---------- Previous post was at 09:05 PM ----------
Hey man, try downloading and running Superoneclick version 1.7 (not the latest version) and use the rageagainstthecageexploit in the dropdown. It worked for me flawlessly!

^ What he said. The oldest version of superoneclick, specifically 1.7 still works great. I just had to do this a few days ago when I got my replacement.

Thanks guys for leading me in the right direction. It is in fact the new version of superuser (3.0) that is the problem. The reason SuperOneClick 1.7 is working for some people is because it includes an older version of superuser. Since SuperOneClick 1.7 does not like my computer I rooted the ADB way and just installed the Superuser.apk included with SuperOneClick 1.7 and everything is working now!

bjjryan said:
Thanks guys for leading me in the right direction. It is in fact the new version of superuser (3.0) that is the problem. The reason SuperOneClick 1.7 is working for some people is because it includes an older version of superuser. Since SuperOneClick 1.7 does not like my computer I rooted the ADB way and just installed the Superuser.apk included with SuperOneClick 1.7 and everything is working now!
Click to expand...
Click to collapse
There is also an app in the market called super user update fixer I believe.. Worked when I was having issues with my super user app
Join the revolt!

[TOOL]Auto Install Tools[Windows]

I have made this for people that have suddenly lost root access the installer contains
Superuser Application < Latest
Su Binary < Latest
Root Browser < Latest
Root Browser Thread http://forum.xda-developers.com/showthread.php?t=1338582
Busybox < 1.19.0
i will be adding updates as they come out so i will be updating busybox tomorrow to 1.19.3 i have tested this and it works a charm
Download v1.0.0.1
http://www.mediafire.com/?cl89ngtk4qrv1uh
More to be added like gapps installer and tweak installers

Download Link added

cool! Will try when I go back home on tuesday

thanks eoghan i just realized when i was about to caligrate SDSL v2 that i lost root, and that mite be the reason im getting fc's and busybox doesnt want to install any version, how this happent with murki's versions and others i never had this problem.
ps: btw how does this work?
EDIT: i plugged my phone run the app as admin and no admin and all the times said permission denied, already tried twice and once being in recovery . im tired of all the issues i had had so far with sdsl v2 ill go back to v1. btw also tried Z4root with no success
Veronica

Nice program. In which language have you made this? I suppose it was made in Visual Studio, or am I wrong?

lavero.burgos said:
thanks eoghan i just realized when i was about to caligrate SDSL v2 that i lost root, and that mite be the reason im getting fc's and busybox doesnt want to install any version, how this happent with murki's versions and others i never had this problem.
ps: btw how does this work?
EDIT: i plugged my phone run the app as admin and no admin and all the times said permission denied, already tried twice and once being in recovery . im tired of all the issues i had had so far with sdsl v2 ill go back to v1. btw also tried Z4root with no success
Veronica
Click to expand...
Click to collapse
god this should have worked because all custom rom allow the adb shell command rooted or not it soulds like the rom didn't install correctly.
also it made using notepad++ to make the bat file

lavero.burgos said:
thanks eoghan i just realized when i was about to caligrate SDSL v2 that i lost root, and that mite be the reason im getting fc's and busybox doesnt want to install any version, how this happent with murki's versions and others i never had this problem.
ps: btw how does this work?
EDIT: i plugged my phone run the app as admin and no admin and all the times said permission denied, already tried twice and once being in recovery . im tired of all the issues i had had so far with sdsl v2 ill go back to v1. btw also tried Z4root with no success
Veronica
Click to expand...
Click to collapse
Z4root uses old root exploit that was patched in 2.2.1+, GingerBreak will work also Boot into recovery and mount system and connect then use this app

ill have a look at using gingerbreak aswel in the installer after it tests if root can be used without gingerbreak im currently making a new installer for google apps link market, youtube etc all the latest as possible

eoghan2t7 said:
ill have a look at using gingerbreak aswel in the installer after it tests if root can be used without gingerbreak im currently making a new installer for google apps link market, youtube etc all the latest as possible
Click to expand...
Click to collapse
That would be very Usefull, Instead of having to search for them,
For guys who don't know where the latest are go onto Cyanogenmod's website, they are all there

i will be putting the lastest market and music in it but will give the user the choice to use the old music app

[SOLVED 2.07][BUG 1.94]: endless loading of apps and logs fragments

Thread specifically about finding and solving the issue that some are seeing where the apps and logs screen of SuperSU will load indefinitely, while su access does keep working.

r25txe said:
Hi @Chainfire
I just tried the 2.04BETA to see if my issue was resolved, to no avail.
I was wondering have you had any reports of certain settings not being configurable and the "apps" and "logs" tabs endlessly refreshing, i.e., you cannot see what apps you have approved or denied.
My root does work, I can approve or deny requests normally, it's just I cannot go back if I want to reconfigure an app's root access or review logs. Unchecking the refresh app and logs automatically has no effect.
In the settings, uninstall SuperSU will not work, causes an eventual crash of SuperSU (after quite some time) unless you do a reboot. SuperSU will still be there, too.
I'm a Pro user and unable to set a PIN either as SuperSU will just circle endlessly after trying to set one.
I've been reading about other users' issues mostly related to root access itself, but my issues seem to be interface only.
---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------
Oh, my ..!
It's working now, I just did another reboot (because SuperSU had become stuck again) and on reboot all was working! :good:
:blush:
I'll redownload the licence and test Pro features tomorrow and report back.
Click to expand...
Click to collapse
r25txe said:
All the issues I described are back now.
With or without licence.
Will continue trying/testing see if I can get a pattern.
This is persisting across four phones, one on Gingerbread.
Click to expand...
Click to collapse
mathuaerknedam said:
I'm also seeing this, in 1.94 and 2.02, but I've not yet tried the 2.04 beta. Sometimes it works. I've tried all sorts of different things to identify a pattern, but I've had no luck.
I've also one instance, just last night, of SuperSU requesting root privileges for itself. I can post a screenshot and some log data if that would help.
Sent from my Nexus S 4G using XDA Free mobile app.
Click to expand...
Click to collapse
xlollomanx said:
Same issue I have, is presented from any version after 1.94. However it does not happen always: sometimes shows granted superuser app sometimes not, happens random.
Click to expand...
Click to collapse

It'd be great if we can get a recap of which SuperSU versions, which devices and kernels and firmwares, are affected. Any information you have is welcome. Let's get this issue sorted out.

@Chainfire So I'll start. I own a Galaxy W with unofficial Cyanogenmod 11 ( http://forum.xda-developers.com/showthread.php?t=2588495) and now I'm using this kernel http://forum.xda-developers.com/showthread.php?t=2593027 (I' ve tried also with stock kernel but the problem persist and is the same). I used SuperSU for years and worked perfectly until v1.94. When I installed v2.0 the problem starts. After that I updated to 2.01 and I tried some beta like 2.04 and 2.05 but the problem still persist.
I hope this can help you, thanks for support.
EDIT: Some kind of Log could help you?

xlollomanx said:
@Chainfire So I'll start. I own a Galaxy W with unofficial Cyanogenmod 11 ( http://forum.xda-developers.com/showthread.php?t=2588495) and now I'm using this kernel http://forum.xda-developers.com/showthread.php?t=2593027 (I' ve tried also with stock kernel but the problem persist and is the same). I used SuperSU for years and worked perfectly until v1.94. When I installed v2.0 the problem starts. After that I updated to 2.01 and I tried some beta like 2.04 and 2.05 but the problem still persist.
I hope this can help you, thanks for support.
EDIT: Some kind of Log could help you?
Click to expand...
Click to collapse
How did you update? Via in-app, Play store, or exclusively ZIP updates? Which recovery are you using? Have you tried making a backup, wiping, and install SuperSU cleanly - does the issue persist?

I've definitely seen this with SuperSU 2.02, and I believe I also saw it with 1.94 (but I can't recall for certain). I've not yet tried 2.04 beta.
I'm using the device, rom, and recovery in my sig. I've see this with several different kernels, including the one in my sig, Marmite 10.6/10.5/10.4/10.3, Matr1x 25 cfs and bfs, Devil Kernel 20131025_VC and Air Kernel Weekly r350.
When I flash a kernel, cwm asks if I want to "fix root". I've reboot both fixed and unfixed, and it doesn't seem to matter.
What else can I try or provide?

Chainfire said:
How did you update? Via in-app, Play store, or exclusively ZIP updates? Which recovery are you using? Have you tried making a backup, wiping, and install SuperSU cleanly - does the issue persist?
Click to expand...
Click to collapse
Now I'm using CWM recovery based (6.0.5.0)
I tested the v1.94 and update v2.0 on a " old rom". Few days later, thinking was my device problem's I performed a full wipe with pristine and installed v2.0 directly from play store, so I could try a cleanly installation of SuperSU (but the problem persist). Here I tried all new versions (I also tried the v1.94, which worked fine, but mainly to uninstall the newer version's as I will explain below) but without success.
I tried in different ways:
I downgraded to v1.94(replacing supersu with root explorer), uninstalled SuperSU, reistalled v1.94(via in-app) and then updated to 2.0 and then v2.01 when update came out from play store.
I downgraded again to v1.94(replacing supersu with root explorer), uninstalled SuperSU and then installed v2.0 from zip-updates. Also tried flashing directly over v1.94 ,without uninstall, from recovery with zip-updates.
I downgraded again to v1.94(replacing supersu with root explorer), uninstalled SuperSU and then installed v2.02 from zip-updates. Also tried flashing directly over v1.94 ,without uninstall, from recovery with zip-updates.
I tried v2.04 and v2.05 with zip-update from recovery by flashing directly over v2.02(this v2.02 is a result from previous test).
I uninstalled SuperSU by replacing supersu with root explorer, installed via in-app v1.94(that work perfectly) and then installed 2.04.
I hope I have answered in the right way in all your questions.
Regards

I have similar bug. I am on SE xperia GB ROM and all previous versions below 2.00 were working fine. After that I started to notice various problems.. For ex. on 2.00+ versions I was always getting "update su binary" notification. I tried to update it in both ways and both were sucessufull and root was working but i still was getting that notification. On last beta (2.05) root stopped to work and all root apps are loading continuously... when I enter to supersu app I get a notification that there is no su binary (but it exists). I install supersu on clean rom from recovery.. Here is the source code..for reference..
https://github.com/feravolt/feralab
Thank you.

Been playing around, haven't replicated so far. A common theme seems to be CM and CWM, though it works fine in my own testing still... sigh.
mathuaerknedam said:
I've definitely seen this with SuperSU 2.02, and I believe I also saw it with 1.94 (but I can't recall for certain). I've not yet tried 2.04 beta.
I'm using the device, rom, and recovery in my sig. I've see this with several different kernels, including the one in my sig, Marmite 10.6/10.5/10.4/10.3, Matr1x 25 cfs and bfs, Devil Kernel 20131025_VC and Air Kernel Weekly r350.
When I flash a kernel, cwm asks if I want to "fix root". I've reboot both fixed and unfixed, and it doesn't seem to matter.
What else can I try or provide?
Click to expand...
Click to collapse
Which installation method do you use for busybox? As I recall, the app you use provides several different methods.

Chainfire said:
Which installation method do you use for busybox? As I recall, the app you use provides several different methods.
Click to expand...
Click to collapse
I just clicked the big install button for a regular install.
Sent from my Nexus S 4G using XDA Free mobile app

Chainfire said:
Which installation method do you use for busybox?
Click to expand...
Click to collapse
That seems like a probable culprit. Maybe if someone installed your version of 'busybox' we might see a difference.
Frank

Installed BusyBox as well ... still working for me ...
Can you guys having this issue post your /data/data/eu.chainfire.supersu/files/supersu.cfg file ?

Very important 3d
Inviato dal mio SM-G900F X-Note 5.0 con Tapatalk

Nothing here

FeraVolt said:
I have similar bug. I am on SE xperia GB ROM and all previous versions below 2.00 were working fine. After that I started to notice various problems.. For ex. on 2.00+ versions I was always getting "update su binary" notification. I tried to update it in both ways and both were sucessufull and root was working but i still was getting that notification. On last beta (2.05) root stopped to work and all root apps are loading continuously... when I enter to supersu app I get a notification that there is no su binary (but it exists). I install supersu on clean rom from recovery.. Here is the source code..for reference..
https://github.com/feravolt/feralab
Click to expand...
Click to collapse
These issues are not related, as the problem we're discussing only applies to Android with SELinux, which Gingerbread doesn't have.

Let me know if v2.06 BETA solved the problem, please!
@r25txe @mathuaerknedam @xlollomanx

Chainfire said:
Let me know if v2.06 BETA solved the problem, please!
Click to expand...
Click to collapse
It works!!!
The problem was never entirely consistent, so I'll keep checking and report back. But so far, so good!
Sent from my Nexus S 4G using XDA Free mobile app

Chainfire said:
Let me know if v2.06 BETA solved the problem, please!
@r25txe @mathuaerknedam @xlollomanx
Click to expand...
Click to collapse
Hi @Chainfire
I just flashed 2.0.5 and the problem is persisting after two full reboots.
What kind of logs would be useful to you if you need them?

r25txe said:
Hi @Chainfire
I just flashed 2.05 and the problem is persisting after two full reboots.
What kind of logs would be useful to you if you need them?
Click to expand...
Click to collapse
Flash 2.06 ?
Did you mistype, or ? If you are actually on 2.06 then I'll have to think some more what the issue could be and how to trace it...

Oh, dear.
I am clearly much too tired to be on XDA! I only noticed that you posted 2.0.6. I will try it after work tomorrow, really need to crash now.
---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------
Oh, I see you´re online, I will flash it right now ...
---------- Post added at 01:02 AM ---------- Previous post was at 12:56 AM ----------
2.06 works!!
(Although, 2.0.4 did this to me, too)
We´ll see how we get on tomorrow
Thank you, @Chainfire
---------- Post added at 01:08 AM ---------- Previous post was at 01:02 AM ----------
Not sure its of use, but here is the cfg file after the flash of 2.06.
https://www.dropbox.com/s/2s3kircndbfjqmm/supersu.cfg?dl=0

what does this mean? can anyone help

Please anyone

no idea man, how did you get root in the first place for 5.1.1

It's not totally rooted. I found this site. SRSRoot One Click Root for Android (SuperUser)

https://mega.nz/#!3JlGBRqB!-xgWHVy5HDNiSQc3SSkkI7UTk0SSpjs1EFsfGSUtZxw

GayCasper said:
https://mega.nz/#!3JlGBRqB!-xgWHVy5HDNiSQc3SSkkI7UTk0SSpjs1EFsfGSUtZxw
Click to expand...
Click to collapse
ok cool thanks

If u figure it out let me know

It is rooted if you flashed that one file that was posted but you don't have a Su Binary installed. I was trying to figure out what I have to push to my phone for the su binary, etc but no one seems to know? It sounded like there was script initially posted by Tanh but I don't see a link anywhere to it.
---------- Post added at 10:07 PM ---------- Previous post was at 09:41 PM ----------
rascal00 said:
It is rooted if you flashed that one file that was posted but you don't have a Su Binary installed. I was trying to figure out what I have to push to my phone for the su binary, etc but no one seems to know? It sounded like there was script initially posted by Tanh but I don't see a link anywhere to it.
Click to expand...
Click to collapse
SRS seems to have installed the su binary however it won't run correctly still. It gives an error of "only position independent executables (PIE) are supported."

As far as I know with the last few days of research and flashing:
The "root" that keeps floating around here is not full root. It is an official samsung kernal intended for buisnesses to force apps to the system. It only allows adb root access, it will not allow you to install the binaries needed for su. Either it won't fully install and be useless or it will put you into a boot loop with no current fix.
SRS root does not work. They might claim it roots your phone but it is only a half install of su. I have tried many times, and it will not give you su.
Sent from my SAMSUNG-SM-G925A using XDA Premium HD app

Rooted, but no rooted apps work

Hello,
I recently used the toolkit to unlock and root my Sprint N6. Super user was installed and works. I installed Rootcheck after everything was complete and it verifies that the phone is rooted. I have installed Nexus 6 double tap to wake and LED control and both state that the phone is not rooted. Super user shows both those apps have super user access.
What am I missing? Thank you!!

itlbok333 said:
Hello,
I recently used the toolkit to unlock and root my Sprint N6. Super user was installed and works. I installed Rootcheck after everything was complete and it verifies that the phone is rooted. I have installed Nexus 6 double tap to wake and LED control and both state that the phone is not rooted. Super user shows both those apps have super user access.
What am I missing? Thank you!!
Click to expand...
Click to collapse
use the latest SuperSU

I am on version 2.65 and from what I can tell, that is the latest.

itlbok333 said:
I am on version 2.65 and from what I can tell, that is the latest.
Click to expand...
Click to collapse
you will also need to install busybox as well, as many root apps need it. install from the play store, then install from the app. search busybox in the play store, then choose stericsons version.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
and supersu 2.71 http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Thank you for the reply, Sorry I failed to mention I do have the move listed busy box installed as well. I have clicked on install from within the app as well. Still none of the mentioned root apps work, all say phone appears to not be rooted...

itlbok333 said:
Thank you for the reply, Sorry I failed to mention I do have the move listed busy box installed as well. I have clicked on install from within the app as well. Still none of the mentioned root apps work, all say phone appears to not be rooted...
Click to expand...
Click to collapse
try flashing the supersu 2.71 with twrp recovery, you should have root when you boot up. dont use the toolkit.

simms22,
I flashed version 2.71 through recovery, after reboot it was installed. Same "phone does not appear to be rooted" when trying to use the root apps... Root check still says phone is rooted. This is puzzling!

itlbok333 said:
simms22,
I flashed version 2.71 through recovery, after reboot it was installed. Same "phone does not appear to be rooted" when trying to use the root apps... Root check still says phone is rooted. This is puzzling!
Click to expand...
Click to collapse
very odd! tell me, which rom are you using? and did you wipe your data before rooting? if not, you might have to wipe your data then reflash your rom/gapps, and supersu.

I am stock rooted. Yes I wiped data and started from scratch after unlock and root.

itlbok333 said:
I am stock rooted. Yes I wiped data and started from scratch after unlock and root.
Click to expand...
Click to collapse
when you try to use a root app, so you get a little popup that asks you to give the app root? do yoh have the supersu app installed as well?

Yes SuperSU 2.71 flashed, the popup comes up and I grant access. Then each app says not rooted. Makes zero sense... The apps even show up in SuperSU app.

Yes, there is a popup and I have granted SU access to the above root apps, still no joy. I have SuperSU 2.71 flashed and installed, Root check verifies root.

I had this. The fix is to uninstall Busybox and reinstall into an alternative directory where it can be found. Mine appears to work fine in /su/bin, but if that doesn't work for you try the others (/system/xbin, /system/bin etc.)
It may not even need to be uninstalled - you could just try installing into the different directories until you find the one that the root apps are checking for root, though I'm not sure whether that would clutter your device with redundant binaries. I'm sure someone will be able to advise on that.