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.
Related
I couldnt find a solid answer, so i was looking for help. I unlocked my phone and installed TWRP. I then flashed the SuperSU and BusyBox .zip file via recovery. But when i open the SU app i get prompted to update binaries and it will crash if i attempt to do so.
I have not flashed the insecure kernel, but I was almost certain that this was not need to gain root access.
Can i get confirmation? Maybe some help too :laugh:
Questions go in Q&A
Sent from my EVO using Tapatalk 2
Same issue
dekend said:
I couldnt find a solid answer, so i was looking for help. I unlocked my phone and installed TWRP. I then flashed the SuperSU and BusyBox .zip file via recovery. But when i open the SU app i get prompted to update binaries and it will crash if i attempt to do so.
I have not flashed the insecure kernel, but I was almost certain that this was not need to gain root access.
Can i get confirmation? Maybe some help too :laugh:
Click to expand...
Click to collapse
I have this exact same issue and I AM running the insecure kernel so I don't think it is an issue of the kernel. I found that using the SuperUser app rather than SuperSU works to alleviate this problem, but now I can't figure out how to uninstall the SuperSU app. If anybody can help me with this let me know
SuperSU wont work you have to use superuser for now..i had the same mistake but when i removed everything and redid it with superuser it been working fine since
Ok, well here's an update. I installed SuperUser via the Play Store, and updated the binaries. Afterwards I reboot and uninstalled the new SuperUser app and. tested SuperSU again. It prompted me to update Binaries again, but this time it worked, and now I am working just fine.
http://www.youtube.com/watch?v=vAwfgi0suJQ&feature=youtu.be
this worked for me on the super user gaining root
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.
(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 guys, I am new to XDA. I've been reading a lot of forums before I decided to register. So, here is my dilemma... I have a Sprint Galaxy Nexus and tried to root it. I rooted it successfully but when I open SuperSU it says something about SU Binaries couldn't be found or old. I downloaded Superuser from the Play Store and that says my SU binary is out of date. When I click on Recovery Install nothing happens. Root Checker says i still have root access. Xposed Framework and GravityBox work like normal. When I clicked on SuperSU again, it said the same thing and this time, after that Root Checker said I have NO root access, but GravityBox and my other Xposed modules still work fine when changing stuff like status bar clock or something. Titanium Backup doesn't work at though, its stuck on "Asking for root rights" I don't know what to do! I don't wanna brick my phone but I want this fixed. Anybody got suggestions?
srv2D said:
Hello guys, I am new to XDA. I've been reading a lot of forums before I decided to register. So, here is my dilemma... I have a Sprint Galaxy Nexus and tried to root it. I rooted it successfully but when I open SuperSU it says something about SU Binaries couldn't be found or old. I downloaded Superuser from the Play Store and that says my SU binary is out of date. When I click on Recovery Install nothing happens. Root Checker says i still have root access. Xposed Framework and GravityBox work like normal. When I clicked on SuperSU again, it said the same thing and this time, after that Root Checker said I have NO root access, but GravityBox and my other Xposed modules still work fine when changing stuff like status bar clock or something. Titanium Backup doesn't work at though, its stuck on "Asking for root rights" I don't know what to do! I don't wanna brick my phone but I want this fixed. Anybody got suggestions?
Click to expand...
Click to collapse
Do you have a custom recovery installed? If not, you should. If you do, then you should be able to just install the latest zip from Chainfire to get your binaries up to date and working properly.
Install this via custom recovery (CWM or TWRP) http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
I have TWRP v.2.1.2 installed, and I also put on a different su binary I found on a website that said modified for Android 4.3 devices, before I did that I didn't have root access even when I tried too
srv2D said:
I have TWRP v.2.1.2 installed, and I also put on a different su binary I found on a website that said modified for Android 4.3 devices, before I did that I didn't have root access even when I tried too
Click to expand...
Click to collapse
UPDATE: Thank you so much! I installed this and now SuperSU works just fine, Titanium Backup works fine, and I can still use GravityBox!:laugh:
:highfive:
So I started with unlocking bootloader and then downgrading my phone and rooted it. After that I installed existenz custom rom, but I had some freeze problems with it, so I downloaded a pre rooted stock 5.1.1 rom. (I wiped the phone in TWRP, before installation)
But know it seems to not be rooted, or at least half way rooted. I have superSU on it. If an app requests root permission superSU shows up and I can grant it etc. But nothing that wants to write in /system seems to work. So I cant use adaway, change DPI for example.
If I try any "root checker" it says i´m rooted.
Solved it with "se linux". I guess it´s something new since the last time I had android.