I really don't know what to do.
I have a rooted nexus 5 running stock 5.1.1 with xposed framework. The installed SuperSU version is 2.79 and works fine. But, Google play keeps asking me to update SuperSu. The updated SuperSu version that then installs is 2.82. If I go ahead and install it, every reboot takes 30 minutes as every installed app gets "optimized".
Fortunately I had a recent twrp nandroid backup that restored things to normal.
I am aware that the developers know SuperSu 2.80 and 2.81 had problems but for me 2.82 still has problems. Chainfire seems to think that 2.82 has resolved the problems, but it hasn't. I sent him an email and tried to post on the SuperSu forum but my message was deleted, I guess because someone thought I had not read the sticky about the 2.80-1 problems.
I tried to find the SuperSu 2.79 apk to download as a safety but found there exist several versions of it and I don't know where to find the correct version.
For now I am sticking with 2.79 but how do I stop the play store from continuingly asking to update SuperSu which I might accidentally reinstall.
Finally, how do I make Chainfire aware of the persistent problems with 2.82?
Thank you.
Related
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
I finally got root to work, but now some apps when requesting root re-boots my phone.
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
In regard to all fo the problems below:
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
wowens0822 said:
I finally got root to work, but now some apps when requesting root re-boots my phone.
Click to expand...
Click to collapse
theguitarhero94 said:
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
Click to expand...
Click to collapse
BigRed35m said:
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
Click to expand...
Click to collapse
eddiecanuck said:
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
Click to expand...
Click to collapse
Listen up guys I'm assuming most of you are bone stock and freshly unlocked the problem is the SuperSU APP it is stated in the OP for the unlock method and most of the root threads around here that currently the binaries we have for supersu that is flashed in recovery during the root process are not compatible with the SuperSU APP from the market. Downloading "superuser" from the market will fix all of your problems.
download this > https://play.google.com/store/apps/details?id=com.noshufou.android.su&feature=nav_result#?t=W10.
Until further notice this will be necessary. There are some people that have hacked in different binaries for their updates/roms just make sure you read OP's first before tryingto switch back to the SuperSU app.
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
eddiecanuck said:
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
Click to expand...
Click to collapse
Did you make a NAND b4 supersu app installed? Revert if so if not i recommend UKB in the development sections its a solid rom right now with lots of options. I'd say fix it now so it doesnt bite you later. Also you could try freezing in tibu then using tibu to uninstall SuperSU that is.
I did an uninstall updates for SuperSU to get it back to what was flashed, and I can uninstall Superuser. Haven't done a NAND yet but will. Looking at UKB, was going to stay stock for a while but after looking at that I probably won't.
Most likely flash it tonight, has some nice features. Thanks again for the input.
A couple of weeks ago I successfully rooted my Galaxy S3 using the toolkit - everything including superSU worked fine and dandy.
Because of problems with the device freezing I downloaded the latest update to 4.1.2 using KIES - this of course took away root access.
I uninstalled all the various root apps I had installed and used the phone for a few days to make sure the problem was solved
Today I re-rooted using the toolkit in the same way - all went fine and the phone was rooted and I reinstalled rooted apps like ROM Toolbox Pro that I had already paid for.
When I loaded root apps I got the superSU prompts to allow them which all worked ok. However when I went into SuperSU itself it tried to update the binary and failed each time. Chainfire let me have the latest update which I installed with Mobile ODIN - after that it still worked but the problem of failing to update binary still occured.
I then tried installing the same zip file in recovery using TWRP seemed to work ok BUT now I have the "No SU Binary installed and cant install - this is a problem". I tried again after a fresh install of the latest UPDATE SuperSU v1.10 from here - but still the same and now no rooted apps will run. Super User cant be uninstalled as Play reports that it is installed!I
can fathom a few possible options:-
1) Can I just install SuperUser (chains DD) from the Play store - will this work in place of SuperSU or is it just going to make it worse
2) Can I just re-run the Root Option in the toolkit again in the hopes that it will at least give me superuser rights even if I can actually updated SuperSU (as I had before) or do I need to unroot before rooting again
3) If I could find the download I could use CF-Root via desktop ODIN but I do want TWRP installed for ROM Toolbox to work at its best
Suggestions on these or other solutions welcomed - the phone is still working fine just no root access!
Try flashing cf auto root with Odin.
Sent from my Nexus 7 using Tapatalk HD
Cant update SuperSu v1.10
Im having the same problem! I tried using Superuser to update the binary and it did it successfully but when i try to open the app the problem's still there(I attatched a screenshot)! I was running the free v1.04 of this app and I liked it so much that a few days ago I decided to buy the Pro Version 1.05 through Google Play! Everything was working great than the next day I got a notice saying there was an update to this app (v1.10), so I install it and now it tells me to update the binary but when I choose to update, it gives me an error and restarts my phone ! I attached a screenshot of the error right before it crashes!!! I'm running a rooted HTC one S, with stock ROM (Jelly Bean 4.1.1) and custom recovery (ClockWorkMod), I have enough memory in my entire system!! I hope they fix this soon, I email the developer . If i get an answer i will post back the results here!!
CF Root
Theshawty said:
Try flashing cf auto root with Odin.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks
I just installed CF-Root using ODIN and my rooted apps can now access again BUT when I open SuperSU I am still getting the message to update the binary and the update then fails. The first time it failed it left SuperSU open and apparently functioning, not sure it registered the fact that I have paid for the pro version, though Google Play reports the pro update is installed and wont let me uninstall/re-install. If I cancel the option to update the binary the app just closes now. (odd that it didn't the first time)
So I am still where I started in that it will not update the binary and I am certainly not going to flash the update.superSU V1.10.zip file again because the first time I did that it made no difference and the second time it lost the binary file altogether. I imagine more S3 owners are going to come across this so I will sit tight with what I have and hope that Chainfire can get it working again
I downloaded the md5 file for TWRP and installed that with Mobile Odin so now I have TWRP back as well - still cant open supers but it is doing its job in the background which is the main thing for now
It doesn't seem to be a GS3 related problem. I have a HTC One S, yesterday I updated SuperSU to v1.10 and the app also asked me to update the binaries (as with any update). As you can imagine binaries installation failed.
I have tried to uninstall updates (via app manager) but it doesn't help because su has been deleted. I will have to root again and wait until SuperSU is fixed before updating.
http://forum.xda-developers.com/showthread.php?t=1538053
It has a thread .
jje
Updated SuperSu with CWM through desktop!!
I got an email from developer with a link to download the zip file! After downloading it to my desktop, I plugged in my HTC one S to move the zip file to my root folder the I booted the phone into HBoot and installed it in CWM recovery. Rebooted an done, I double checked by clicking on the SuperSu app and now no more binary update warning and in the settings it says SuperSu Pro v1.10!!! Awesome, here's the link to the download :
download.chainfire.eu/312/SuperSU/UPDATE-SuperSU-v1.10.zip
---------- Post added at 08:38 PM ---------- Previous post was at 07:42 PM ----------
gbswales said:
A couple of weeks ago I successfully rooted my Galaxy S3 using the toolkit - everything including superSU worked fine and dandy.
Because of problems with the device freezing I downloaded the latest update to 4.1.2 using KIES - this of course took away root access.
I uninstalled all the various root apps I had installed and used the phone for a few days to make sure the problem was solved
Today I re-rooted using the toolkit in the same way - all went fine and the phone was rooted and I reinstalled rooted apps like ROM Toolbox Pro that I had already paid for.
When I loaded root apps I got the superSU prompts to allow them which all worked ok. However when I went into SuperSU itself it tried to update the binary and failed each time. Chainfire let me have the latest update which I installed with Mobile ODIN - after that it still worked but the problem of failing to update binary still occured.
I then tried installing the same zip file in recovery using TWRP seemed to work ok BUT now I have the "No SU Binary installed and cant install - this is a problem". I tried again after a fresh install of the latest UPDATE SuperSU v1.10 from here - but still the same and now no rooted apps will run. Super User cant be uninstalled as Play reports that it is installed!I
can fathom a few possible options:-
1) Can I just install SuperUser (chains DD) from the Play store - will this work in place of SuperSU or is it just going to make it worse
2) Can I just re-run the Root Option in the toolkit again in the hopes that it will at least give me superuser rights even if I can actually updated SuperSU (as I had before) or do I need to unroot before rooting again
3) If I could find the download I could use CF-Root via desktop ODIN but I do want TWRP installed for ROM Toolbox to work at its best
Suggestions on these or other solutions welcomed - the phone is still working fine just no root access!
Click to expand...
Click to collapse
I got an email from developer with a link to download the zip file! After downloading it to my desktop, I plugged in my HTC one S to move the zip file to my root folder the I booted the phone into HBoot and installed it in CWM recovery. Rebooted an done, I double checked by clicking on the SuperSu app and now no more binary update warning and in the settings it says SuperSu Pro v1.10!!! Awesome, here's the link to the download. Just copy and paste the link in your browsers address bar!! Hope this helps, good luck!!
download.chainfire.eu/312/SuperSU/UPDATE-SuperSU-v1.10.zip
(I cant post to the original thread, but im hoping someone here can help me please?)
Ive rooted 6 or so different android phones mainly using cf-autoroot, including an i9300, and never had any issues. But I have had a few issues rooting my 9503 using the cf-autoroot method (method #1 in this post). It aooeared to work, but SuperSU subsequently fell over, and Knox complained but after reading other posts I rectified that, but obviously not quite correctly:
After using cf-autoroot, SuperSU DID NOT appear in the apps list, but Google Play said it was installed but only presented the option to open it (not update or remove).
So I then tried flashing twrp (as per method #2 in this post) which all appeared to go successfully according to Odin. I was expecting to install superSU updater, as per step 3, but recovery mode appeared unchanged/stock so of course I couldnt flash anything as there was no option to do so. Yet there were no errors reported by Odin?
So I then got hold of the app file for SuperSU 1.93 and installed it (via Airdroid). It ran. It found knox. It removed it, and root was installed successfully (as verified by root checkers, titanium backup, droid wall and the like). So I concluded I had successfully rooted my 9305.
But when I reboot SuperSU falls over again on boot up, and the version I added via Airdroid has disappeared, and of course there is no root mode.
But I can then restore root access after a reboot simply by following the same process, namley installing the supersu apk via Airdroid.
Can anyone suggest what is the easiest way to get round this, or even why it's happening? And why is the later version of SuperSU disappearing on reboot?
non persistent SU after rooting Android 4.3 - solved
OK, so Im still unsure how I ended up successfully rooted ,but then reverting back to a non-working or incompatible SU version on reboot (presumably the version installed via cf-root?). It's news to me that an app installed via standard means can be overridden for any reason on reboot. One day someone might explain that or tell me the appropriate phrase to use for my friend google so he can explain it to me.
So what I was then trying to do was install a custom recovery so I could flash the latest SU, as per OP. Try as I might I cant. Even removing the battery once TWRP has been transferred using Odin the standard recovery still prevails. So that one is still unresolved.
But in the meantime, as with most well written apps, the answer is within SU itself. Going into Options in the Su installed via the standard app installer, I selected the option to install that SU as a binary. And it worked, so now SU persists across reboots.
Just in case someone else has the same issue, although judging by all the replies I suspect not (or maybe everyone else is able to post to the original thread, although I dont see this exact problem or solutio there).
If it didnt help anyone, sorry for wasting your time!
Hi,
I have the same problem : my root is lost after each reboot.
I must uninstall SuperSU, then update SuperSU end reboot to have the root again.
Could you give me your solution with simple words because I don't understand what you posted befort. Sorry for my bad english ...
Thanks.
Hello is there a way to root the stock mm rom?
If I flash the super su binaries manually will it work? i've already got my TWRP installed on my device.
thanks for your help (if you help me )
SuperSU version 2.65-3
Yes you can root it but it is BETA
So don't expect it to work perfectly like it does on Lollipop.
There was security changes in Android that made things different on MM.
I advise people be extra cautious when planning on Rooting with MM.
There is a bunch of topics created on how to do this (i made one for example)
What you HAVE to do is get a special version called SuperSU "systemless" installed
this is a new way to get root on that was made because of security changes on Marshmallow.
Don't just start flashing things on your phone with out researching first or you may brick your phone.
I know i did that myself LOL
Then realize because the new Root works different then you may have some app's now not work properly.
For example make sure you use the most current updates if you use Stericson's BusyBox (35 pro or 41 free or higher)
Research and read on it then make sure to only use the Flashable zip format's shared by chainfire.
Don't just install APK's.. he tells you this on his pages over & over.
xpmule said:
Yes you can root it but it is BETA
So don't expect it to work perfectly like it does on Lollipop.
There was security changes in Android that made things different on MM.
I advise people be extra cautious when planning on Rooting with MM.
There is a bunch of topics created on how to do this (i made one for example)
What you HAVE to do is get a special version called SuperSU "systemless" installed
this is a new way to get root on that was made because of security changes on Marshmallow.
Don't just start flashing things on your phone with out researching first or you may brick your phone.
I know i did that myself LOL
Then realize because the new Root works different then you may have some app's now not work properly.
For example make sure you use the most current updates if you use Stericson's BusyBox (35 pro or 41 free or higher)
Research and read on it then make sure to only use the Flashable zip format's shared by chainfire.
Don't just install APK's.. he tells you this on his pages over & over.
Click to expand...
Click to collapse
Thanks, i know just installing the APK won't do anything, actually after posting this i tried the latest version of the systemless root, and my phone bricked, it wouldn't even show me the boot logo, and in the bootloader I didn't have a baseband version, thank god I had a back up
I'm now following your post and i'm going to try and root my phone after i'm done backing it up, btw do you know if xposed works with this systemless root? I want to use gravity box so I can add a few tweaks to the stock rom... and I also want to unnintall system apps with titanium backup, but these aren't that important as the tweaks..
Not too sure never used Xposed but i was Google searching and found a fix from guys for the Moto-G
I had to use, BETA-SuperSU-v2.62-3-20151211162651.zip
Newer versions failed to patch the bootloader and do a systemless install.
Use a newer one and then look in the TWRP console (after flashing from TWRP)
You can see on newer versions it simply does a normal install.
So if it does NOT patch your Bootloader for you then your screed.. bricked !
Re-Install the firmware then..
SO far installing BETA-SuperSU-v2.62-3-20151211162651
worked to get the Bootloader patched and the systemless version installed.
Then before exiting TWRP i have flashed over-top (with out restarting) BETA-SuperSU-v2.67-20160121175247
Get them from here..
EXPERIMENT: Root without modifying /system #2: Automation
Supposedly updating to 2.71 Beta is suppose to work.
But i am sketchy about it and 2.67 is for sure working good.
I just tried tonight 2.71 beta updating over-top via TWRP
and i think it was ok i guess.. i have not tested it much though.
(not sure if it will auto-patch the bootloader on a fresh install on it's own with out needing an old version first)
Get 2.71 here.. Note, i am sure chainfire said he merged those older versions into 1 beta version now.
[BETA][2016.03.30] SuperSU v2.71
You have to make sure you have these versions downloaded and ready on your SD card before you start fiddling..
Because if you are on MM and you install and it does not tell you in the console log you got your bootloader patched
..you got a brick on your hands when you reboot LOL
NOTE:
2.65 stable (on Play Store) will NOT work for Marshmallow guys.. it's too old etc.
Hi
so I bought a new Moto Z because I wanna use Xposed. Had already another one, updated to Nougat unfortunately. So I bought a new one.
Unlocked bootloader, flashed Recovery, flashed TurboZ Kernel, (all after this guide) tried to root it. There is the problem.
Once I flashed SuperSU.zip and booted, opened SuperSU everything is fine. But when I open an app which requires root access, the grant access dialog opens, I grant access, but then the app freezes or doesnt recieve the access. I open SuperSU again and now theres a pop up dialog which only says "root undeteced" and a link to "How to root" on the SuperSU Homepage.
I tried with 2.82, 2.81, 2.79 (which has another dialog coming up saying "there is no super su data installed and super su cant install it) with the same link). Tried with 2.46, doesnt even install it via recovery flashing. Soooo....I dont know. Xposed is somehow working since I flashed it and modules are working fine but everything else isnt. Which is super weird.
I googled it of course and it seems that there is a problem with newer versions of super su atm where other people have the same issue. But I wanted it to use as my daily driver now and dont want to set it up if root doesnt work properly.
In some thread some guy suggested to install Magisk. Never heard of it. Read a bit about it....didnt quite get it. Is this a root alternative or something?
Can someone please help me. Its pretty annoying.
Thanks a lot already!
Cheers
Had issues with supersu, too. Installing magisk is indeed the way to go, and, yes, it is an alternative root method and more. Flash zip file in twrp, then install magisk manager from play store.