I have seen a lot of people saying they are losing root access if they update SU Binary. I am to assume everyone who has lost their root access did it via some sort of one-click root app. These will only give temporary root access and will break root at the slightest kick in the teeth.
Anyway, I have updated my SU binary, and I still have my root access, I gained root via [GUIDE] How to Root Sprint 2.1 Release for CDMA Hero and I'm S-off. Hope this helps clear up any issues with SU.
Twolazyg said:
I have seen a lot of people saying they are losing root access if they update SU Binary. I am to assume everyone who has lost their root access did it via some sort of one-click root app. These will only give temporary root access and will break root at the slightest kick in the teeth.
Anyway, I have updated my SU binary, and I still have my root access, I gained root via [GUIDE] How to Root Sprint 2.1 Release for CDMA Hero and I'm S-off. Hope this helps clear up any issues with SU.
Click to expand...
Click to collapse
I rooted same as you. When I updated binary and was on aosp 0.1.2, I did loose ability to use su like in terminal.
I was able to flash a different recovery with adb so I think it didn't wipe root but something with GB and the super user app didn't work together with the new binary.
I successfully updated binary in froyo. Were you using GB when you updated, and if so, which version?
Sent from my HERO200 using XDA App
poashll said:
I rooted same as you. When I updated binary and was on aosp 0.1.2, I did loose ability to use su like in terminal.
I was able to flash a different recovery with adb so I think it didn't wipe root but something with GB and the super user app didn't work together with the new binary.
I successfully updated binary in froyo. Were you using GB when you updated, and if so, which version?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I was running aospGBmod 0.1.4, updated, then went into root explorer (worked), TE (worked), and TB (worked). I also deleted the old SU that came with the ROM, D/L'd the one from market, then updated. I'll try it again with 0.1.2 and test it out. Also, are you S-off or S-on?
Twolazyg said:
I was running aospGBmod 0.1.4, updated, then went into root explorer (worked), TE (worked), and TB (worked). I also deleted the old SU that came with the ROM, D/L'd the one from market, then updated. I'll try it again with 0.1.2 and test it out. Also, are you S-off or S-on?
Click to expand...
Click to collapse
I am S-on.
I just attempted it again using 0.1.4, but I have the same results. Nothing is able to get root rights.
I should've nandroided before trying that. I know better.
poashll said:
I am S-on.
I just attempted it again using 0.1.4, but I have the same results. Nothing is able to get root rights.
I should've nandroided before trying that. I know better.
Click to expand...
Click to collapse
Reboot recovery and go back to your last nand, then reboot into whatever rom you were running. Uninstall SU, reinstall from the market, you should be fine then. But I would make a nandroid just to be safe
I attempted to uninstall and reinstall, but it didn't help.
Now that I have updated to 0.1.5, I can upgrade the binary and everything is working as it should.
Sent from my HERO200 using XDA App
I am on 2.3.3 and just updated SU Binary. Haven't noticed a problem yet. All previously installed root apps still work, newly installed root apps work as well.
disregard. I am retarded and didn't read what forum this was in.
My phone's still rooted, I used the same method as you.
I flashed super su when I rooted my phone but many of the custom roms are now using superuser. Will I encounter any problems? When I flashed my rom all my apps just seemed to go through superuser but when I just rebooted my phone all the requests for root went through super su.
SuperSU was better for 4.2+ for a while there. Both seem equally good now in my opinion. It's really up to you. The downside of having options is second guessing yourself. Ha.
Hello Xda, sorry for such a noob question but i have manually(using Terminal) just tried to root my nexus 4 with a little sour luck. I think the problem came when moving SuperSU to my nexus, i had no idea what to so i simply used Android File Transfer. Then i went to my device and Twrp seemed to be working fine so i installed and backed it up. Then i went to root checker and root checker said my phone was not rooted and although SuperSU was present it said that ther is no SU BInary was installed.
Hi. Go ahead and install this zip in TWRP. http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip?retrieve_file=1
It installs SuperSU and the required binaries.
Sent from my Nexus 4 using Tapatalk
I rooted my T-Mobile LG G2 (D801) and the firmware screen shows the red ROOTED. Also ran Root checker and it says the same. Then I ran TWRP and titanium backup... everything is fine. I then flashed several ROMS (hellfire, paranoid, cm11) all is well.
However, when I ran AOKP unofficial build compiled on 12/27/13 and try to install titanium it says I'm not rooted. Checked the firmware screen - still Red root, but when I run root checker: sorry this device doe not have PROPER root access.
Loaded titantium, because I think this might be the issue. Error message: Sorry, I could not acquire root privileges. This attempt was made using */system/bin/su" command.
Is it looking in the wrong area?
UPDATE:
Problem was with the build of AOKP. Installed the nightly from 2-8-14 and the issue was resolved... hope this helps someone having similar issues.
download and flash the superuser app via recovery. open app and update binaries.
victory
Thanks, but the problem was the AOKP build.
Greetings Folks!!!
I am on CM12.1 Lollipop 5.1.1 Nightly, and ROOT access was working fine on my phone so far. When I launched Thunderzap today, I noticed that the app was waiting on "Requesting ROOT Privileges" for over 2 mins, and also the SuperSU app was missing from the app drawer. Thunderzap had been recently updated, and I suspect that might have triggered the root access to be requested again, but it wasn't given root access for some reason, and I never got a prompt to grant it root access. However, my other apps like ROOT Explorer, Shell Terminal Emulator etc, which weren't updated off lately, worked fine with root access. Not sure why now, but I thought reinstalling SuperSU-v2.46 might be a good idea at that time, and I flashed that file. And ever since I have completely lost my root access. When I launch the SuperSU app now, i get an error saying:- "There is no SU binary installed, and SuperSU cannot install it"
Some help would be appreciated. Screenshots attached.
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
acemccloud1 said:
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
Click to expand...
Click to collapse
can you please share the method u used to flash back CM?
i am unable to re root