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.
Related
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.
Hi I have a rooted Nexus 7 and wanted to keep root when updating. I already have SuperSU and wanted to know what is the best way to keep root when updating. Should I use SuperSU Survival mode or download Root Keeper to keep root?
Are there any conflicts having/using both at the same time? Any advice or info on this would be great.
Thanks
randomvector said:
Hi I have a rooted Nexus 7 and wanted to keep root when updating. I already have SuperSU and wanted to know what is the best way to keep root when updating. Should I use SuperSU Survival mode or download Root Keeper to keep root?
Are there any conflicts having/using both at the same time? Any advice or info on this would be great.
Thanks
Click to expand...
Click to collapse
All I can tell you is Voodoo OTA Rootkeeper has worked great for me. Restored root with no problems after 4.2 update.
On my system - however - root causes lag on multi-user that makes it unusable, even with updated SuperSU.
So I am back to being temporarily unrooted because multi-user is more important to me than root.
Just install the latest CWM recovery
It gives you the option to fix the permissions of the su binary after installing an update so you can keep root.
steevp said:
Just install the latest CWM recovery
It gives you the option to fix the permissions of the su binary after installing an update so you can keep root.
Click to expand...
Click to collapse
Well funny thing - su works fine for primary user. Only goes ape on creating or using secondary user.
Over and over, asks if /system/bin/id can have superuser permission. 20 minutes to create a secondary user...
rmm200 said:
Well funny thing - su works fine for primary user. Only goes ape on creating or using secondary user.
Over and over, asks if /system/bin/id can have superuser permission. 20 minutes to create a secondary user...
Click to expand...
Click to collapse
Hmm I didn't experience anything like that, but I only played with multi-user for a few minutes then I deleted the secondary user.
steevp said:
Just install the latest CWM recovery
It gives you the option to fix the permissions of the su binary after installing an update so you can keep root.
Click to expand...
Click to collapse
I am running the stock ROM as i want to receive the updates and have the standard google recovery and do not have CWM installed. My bootloader is unlocked and rooted that's it. I am not using multiuser on my Nexus 7. I think I'll use Root Keeper and keep SuperSU survival mode off.
randomvector said:
I am running the stock ROM as i want to receive the updates and have the standard google recovery and do not have CWM installed. My bootloader is unlocked and rooted that's it. I am not using multiuser on my Nexus 7. I think I'll use Root Keeper and keep SuperSU survival mode off.
Click to expand...
Click to collapse
I'm also running the stock ROM, and updates have worked fine with CWM recovery so far.
I believe it is compatible with the stock recovery.
rmm200 said:
Well funny thing - su works fine for primary user. Only goes ape on creating or using secondary user.
Over and over, asks if /system/bin/id can have superuser permission. 20 minutes to create a secondary user...
Click to expand...
Click to collapse
I'm using SuperSU and had no issyes with setting up a secondary user.
steevp said:
I'm also running the stock ROM, and updates have worked fine with CWM recovery so far.
I believe it is compatible with the stock recovery.
Click to expand...
Click to collapse
Really, can you have a custom recovery like Clockwork manager or TWRP and still receive OTA updates?
GldRush98 said:
I'm using SuperSU and had no issyes with setting up a secondary user.
Click to expand...
Click to collapse
When I get brave - and bored - I will try uninstalling / reinstalling SuperSU again.
For right now, I am just a happy tablet user.
Hi,
I rooted my wifi Nexus 7 using Wugfresh toolkit and everything worked fine. After that I installed SmoothRom 4.3, which again went without a glitch. However, at some point I have noticed that the root is gone. This may have happened when I flashed Trinity kernel, but I am not sure. The Superuser SU is still there and couple of programs still have root access (e.g. Nova launcher), but Titanium backup no longer has root access (and it worked before). I re-rooted this morning using Wugfresh and everything went to the completion. I have Superuser SU and Busybox icons, but Busybox would not install and Titanium backup would not work due to the absence of root access. Any thoughts of what can be done to fix this?
Did you flash with TWRP or CWM? I have heard that you have to re-name some of the file names so that you do not lose the root access. You may have to re-flash and start from scratch but I am not sure. Personally i used MSKIP's toolkit. His has basically a 1.2.3........... root and flash setup. It is very easy to follow, plus one of the steps states "Do you wish to re-name file names so as not to lose Root access on restart." or something pertaining to that, I forgot exactly what it says, but I know that it is there.
visia said:
Hi,
I rooted my wifi Nexus 7 using Wugfresh toolkit and everything worked fine. After that I installed SmoothRom 4.3, which again went without a glitch. However, at some point I have noticed that the root is gone. This may have happened when I flashed Trinity kernel, but I am not sure. The Superuser SU is still there and couple of programs still have root access (e.g. Nova launcher), but Titanium backup no longer has root access (and it worked before). I re-rooted this morning using Wugfresh and everything went to the completion. I have Superuser SU and Busybox icons, but Busybox would not install and Titanium backup would not work due to the absence of root access. Any thoughts of what can be done to fix this?
Click to expand...
Click to collapse
I had the same issue. If you reflash the ROM, the problem corrects temporarily. It may be something w/the most recent version of Smooth- particularly when updates are made to Super User. I tried several different kernels and still "lost" root. Eventually I moved on to another ROM and have not had the issue since.
Thanks for the suggestions. I am using CMW. Tried MSKIP toolbox, but same result. Titanium gave back an error message that device appears to be rooted, but Superuser SU is not working properly. So, I went back and did CMW restore from an earlier backup, which seems to have fixed the problem. Titanium is working again.
Hi Guys.
As the title suggests root access suddenly disappeared from my nexus 6p yesterday.
DigitalHigh rom 7.0 was flashed through the latest twrp (3.0.2-2) and everything was running fine. I got the notification that the SU binary is out of date from PHH's SuperUser. Opened it but nothing really happened. So I downloaded superSU and suddenly it prompted me that the device isn't rooted. Being unfamiliar with PHH's SU I decided to flash the latest SuperSu through TWRP but the phone wouldn't boot.
Right now it has been restored to a backup taken just before flashing SuperSU which means everything is running fine and even android pay works however there's no root access. Is there something specific that might have caused this?
Are there any ways to re-gain root?
Haven't gone through the process of a clean flash yet as the phone is needed for work however even if all of that is done the SU binary will still need to be updated. Is there a different method for updating PHH's root?
So far I have tried clearing cache etc. but noting worked.
apostol96t said:
Are there any ways to re-gain root?
Click to expand...
Click to collapse
Phhusson's superuser and SuperSU don't mix. If you're back to booted, but not rooted with Phh, you'll need to either flash one of the Nougat boot images from the nexus/angler folder or the latest superuser.zip (I think the latest is r229) from http://superuser.phh.me
Hello ^^
I am hoping that some of you guys can help me out of a little issue that i am having, i will try and explain what has happened up until now as best i can:
As many people know, the latest update to Pokemon GO, knocks out rooted users. I did not know this and updated last night, however, dispite running a custom ROM (PureNexus) and being rooted, my game loaded up like normal and let me play. It wasn't until i checked that my SuperSU that i found that root wasn't actually working at that time, so i re-flashed the latest Super SU and all was good, but, obviously, this knocked out Pokemon GO.
I read up on the trick of using Magisk to be able to turn off root and when was needed as to get the game to work, so i went about trying to get it working. I unrooted via Super SU and then rebooted and flashed the Magisk installer and PHH Superuser (as i heard this was best for compatability). After the phone rebooted i, installed the Magisk launcher and the PHH SU program from the Play Store, but when i opened any app that reuqited root, it was still telling me i wasn't rooted anymore, and thus, when i opened PGO, it worked.
I am kinda lost from here, i want to get my phone rooted again, and i want to get Magisk working so i can still enjoy PGO and some of my occasionally used apps that require root, so my questions are as follows:
1. Can you re-flash an SU over an old one to get root back, or do i need to fully un-root and root again?
2. If i was to re-flash SuperSU (with Magisk support), would this get me rooted again and allow me to flash Magisk as normal?
I am a little lost here, any and all help would be appreciated.
Thanks to all in advance.
Have you tried Root Cloak xposed module?
Sent from my Nexus 6P using Tapatalk
jxcorex28 said:
Have you tried Root Cloak xposed module?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
i have, it doesnt work as PGO uses safetynet, like Andriod Pay
Ohh snap, well that's all I had...I don't play PoGo
Sent from my Nexus 6P using Tapatalk
For magisk to work, you have to use it to root and unroot. From what I understand, it temporarily removes root system wide when you do this. Basically it's a more convenient way to root and unroot.
Android Police has an article on it right now. The instructions for installation and usage are correct.
The problem is probably related to a failure to make sure all traces of previous SuperSU installations are gone.
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk
For magisk to work it's best to fully unroot, maybe try unsu.zip,
Then have a 100% stock system and boot (kernel)
And before flashing magisk and phh, try the SafetyNet checker app in the playstore. (PoGO uses SafetyNet to check for root, same as Android Pay)
If you pass then go ahead and flash magisk, phh, and then phh app followed by magisk manager
In the magisk thread are all the instructions to follow
Sent from my Nexus 6P