I'm using a CM11 ROM, and Superuser is giving me problems - throws up errors now & again. I like and want to use SuperSU, but Superuser is integrated into the ROM.
How can I get rid of Superuser and replace with SuperSU (preferably just using my phone, no ADB).
setspeed said:
I'm using a CM11 ROM, and Superuser is giving me problems - throws up errors now & again. I like and want to use SuperSU, but Superuser is integrated into the ROM.
How can I get rid of Superuser and replace with SuperSU (preferably just using my phone, no ADB).
Click to expand...
Click to collapse
in the integrated superuser menu(can be found in device settings), if you open settings, you have the option of giving superuser access to "disabled" (by default it is apps only).
after disabling you just have to flash the supersu zip file(can be found on the supersu xda forum) via recovery mode. and you're done.
I flash the superSU.zip after flashing CM11 and Gapps so superSU is the main root app. Never had an issue.
Please keep it friendly and there is no need for name calling of any kind. We tend not to like people resurrecting old threads, but seen as this came in handy for someone there's no harm done.
Thread cleaned.
wedgess said:
Please keep it friendly and there is no need for name calling of any kind. We tend not to like people resurrecting old threads, but seen as this came in handy for someone there's no harm done.
Thread cleaned.
Click to expand...
Click to collapse
Thank you, mod. Wasn't trying to cause any problems, just trying to help a new member.
rdx93 said:
in the integrated superuser menu(can be found in device settings), if you open settings, you have the option of giving superuser access to "disabled" (by default it is apps only).
after disabling you just have to flash the supersu zip file(can be found on the supersu xda forum) via recovery mode. and you're done.
Click to expand...
Click to collapse
i'm having some problems in cm11 with superuser too so i took your advice and disabled it and flashed the supersu.zip but still no root and then i went back to enable it again under settings but now the superuser option is gone.
how do i fix this?
Just make clean flash of CM, then get SuperSU via store
JimZiii said:
i'm having some problems in cm11 with superuser too so i took your advice and disabled it and flashed the supersu.zip but still no root and then i went back to enable it again under settings but now the superuser option is gone.
how do i fix this?
Click to expand...
Click to collapse
In the SuperSU settings, there is a setting called something like "Respect Cyanogenmod Settings". Uncheck that.
Thnx alot! Works great! Now i just have to change that stupid google dialer that's in cm11
Sent from my GT-I9300 using Tapatalk
Related
Which one is better?
Whats the difference between the 2?
Im using rom toolbox pro and in the toast message when phone boots it tells me to use supersu
How do i get rid of the installed superuser and add supersu without losing root or bricking my phone?
Thanks in advanced
FingerBlastJ said:
Which one is better?
Whats the difference between the 2?
Im using rom toolbox pro and in the toast message when phone boots it tells me to use supersu
How do i get rid of the installed superuser and add supersu without losing root or bricking my phone?
Thanks in advanced
Click to expand...
Click to collapse
Install SuperSU from the Play Store, grant it root access, then delete SuperUser using a file browser. Or you can try flashing the SuperSU zip from the official xda thread and it should replace SuperUser automatically.
I haven't noticed a difference between the two. Used both on various ROMs for a decent amount of time. AFAIK, they are only there to handle root permissions for apps. That said, never had a problem with either.
I'm using a cm nightly with the new super user built into the ROM. So, can I uninstall the app or what?
Free your mind!
50cr473s said:
I'm using a cm nightly with the new super user built into the ROM. So, can I uninstall the app or what?
Free your mind!
Click to expand...
Click to collapse
Uninstalling it would remove root. You can replace it with another superuser app.
I'd be careful with this. I did it by accident (switched ROMs, had a had SuperSU installed on my old ROM, but new ROM came with its own SU program. When I reinstalled everything I included SuperSU) and it messed everything up - no programs could successfully get root access. I ended up just wiping and re-installing the ROM, this time not re-installing SuperSU on top of it and sticking with the built-in one on Viper.
Is there really any difference between SU apps? Hardly seems worth the hassle.
I'm using cm's app which is open source and built to be compatible with android platform, thus the ability to be integrated into the ROM. I've noticed that when I switch ROMs(e.g. carbon's unofficial port) Supersu is there in the app tray(instead of cm's) and cm's is in the settings. I had supersu installed before, but removed it when I installed cm's app. Oh my I've gone crosseyed. I've decided that it works as is and my only need is to clean up a little. I was just wondering if any one knew about specifically CM's super user?
Free your mind!
50cr473s said:
I'm using cm's app which is open source and built to be compatible with android platform, thus the ability to be integrated into the ROM. I've noticed that when I switch ROMs(e.g. carbon's unofficial port) Supersu is there in the app tray(instead of cm's) and cm's is in the settings. I had supersu installed before, but removed it when I installed cm's app. Oh my I've gone crosseyed. I've decided that it works as is and my only need is to clean up a little. I was just wondering if any one knew about specifically CM's super user?
Free your mind!
Click to expand...
Click to collapse
Well here's two cents for what its worth. When I moved from Rooted Stock (with SuperSU) to CM10 based Rom (LiquidSmooth), the CM10 app superseded from under Settings. SuperSU had to ask that app for permission before opening its own shop. From then on SuperSU ruled.
You don't necessarily have to do this. I did it because I like and support Chainfire's work. You can uninstall SuperSU if you are getting a CM based ROM with their app. It does not matter either way. They both are good.
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Perseus71 said:
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Click to expand...
Click to collapse
You could have flashed root back just the root zip
a box of kittens said:
You could have flashed root back just the root zip
Click to expand...
Click to collapse
I tried and failed. Recovery Flash had error unable to obtain Root.
Perseus71 said:
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Click to expand...
Click to collapse
The SuperUser in CM now is not the same as it used to be, this is a new, open source SuperUser built by Koush and designed to be integrated into the system. Also this new version has two ways of updating the binary should one fail you.
Sent from my One X using Tapatalk 2
bliind said:
The SuperUser in CM now is not the same as it used to be, this is a new, open source SuperUser built by Koush and designed to be integrated into the system. Also this new version has two ways of updating the binary should one fail you.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes I am aware of CM's inbuilt app. My comment that you quoted, pertains to the SuperUser App by ChainsDD as against SuperSU by Chainfire. This for the part 2 of OP.
Do either of the devs have a thread pertaining to switching su apps? I couldn't find anything?
Free your mind!
50cr473s said:
Do either of the devs have a thread pertaining to switching su apps? I couldn't find anything?
Free your mind!
Click to expand...
Click to collapse
Here's SuperSU. Best to download the App from Google Play. The thread can be confusing.
The CWM Superuser app on Google Play.
The original Superuser App by Chainsdd. As before best get it on Google Play.
i always download the supersu cwm flashable from the supersu thread, then after you flash it you can disable the original one.
Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Cloonix said:
Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Click to expand...
Click to collapse
What happens if you delete the file with a file manager and reboot?
Aerowinder said:
What happens if you delete the file with a file manager and reboot?
Click to expand...
Click to collapse
I used Solid Explorer as a file manager and tried to delete /system/app/Browser.apk. The root-confirmation (CM11 superuser) pops up, asks for superuser (i grant) and Solid Explorer deletes the file without error. But the file is still there (without reboot).
Issue with superuser?
Edit: Stop... I noticed /system is mounted as read-only.
I tried to analyze the problem... and the only conclusion is, that my superuser is not working. Also Super SU ist not working. I also flashed Omni ROM instead of CM11 with no success. I used an older version of TWRP without success. Does anybody has an idea?
Edit: Before with Stock ROM and Super SU it was working.
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Me to, cm11 for a850L build on crdroid nexus4
Cloonix said:
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Click to expand...
Click to collapse
Did you leave out Franco kernel this time?
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
es0tericcha0s said:
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
Click to expand...
Click to collapse
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
Aerowinder said:
Did you leave out Franco kernel this time?
Click to expand...
Click to collapse
No I flashed Franco after CM.
Cloonix said:
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
No I flashed Franco after CM.
Click to expand...
Click to collapse
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
es0tericcha0s said:
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Cloonix said:
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Click to expand...
Click to collapse
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
es0tericcha0s said:
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
Click to expand...
Click to collapse
I tried this. And it was successfully changing selinux to permissive with every reboot. But doing this I noticed that even permissive doesn't solve the problem. CM11 built-in superuser just don't work for me. Only "Super SU" by Chainfire works well. And permissive solves a few other problems besides TiBa.
Personally I've always eventually had issues with Superuser unmounting the system as rw causing issues with apps like Titanium. Had it happen many many times on my old phone as well as the Nexus 5 across multiple ROMs. I just stick with SuperSU now.
Haven't had too many issues with that part it seems, but glad you narrowed down the problems.
I find this issue sometimes on varous flashes of CM 11 on different devices.
I use ROM toolbox fo manage apps, and sometimes it just wont delete. The solution is strange: I install adaway - somehow, that "unlocks" something that lets you delete apps. You can uninstall adaway once you have run it!
Galaxy Nexus
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
es0tericcha0s said:
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
daniu said:
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
Click to expand...
Click to collapse
If you are already using CM11, then yes, you can install SuperSu from the Play Store. Once you do and open the app, it will prompt you to update the SuperUser binary. You should be able to do the "normal" method, and then once that updates, reboot, then try the SELinux app again and then everything should start to work like you would expect. If the normal method doesn't work, then you can let it download the newest zip for you if you choose the CWM/TWRP method, and then boot to recovery and install the zip it downloads for you.
SeEsAw12 said:
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
Click to expand...
Click to collapse
No clue why, but this worked for me. Permissive didn't do it (was already permissive using CM 11 for tf201) and AdAway didn't do it. Didn't matter that Wanam Xposed is for Samsung devices, once given root to this app, Titanium got its head out of its rump.
UPD: So, if i uninstall Wanam Xposed then TB sticks its head back up its rump. Whatever giving root to that app does, its fixing usage issues with TB.
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
TraderJack said:
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
Click to expand...
Click to collapse
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
S1L3nTShaDoWz said:
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
Click to expand...
Click to collapse
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
TraderJack said:
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
Click to expand...
Click to collapse
Yeah on the kernel my bad, didn't see it had a normal one for non 2.23 firmware users lol, if you don't wanna use that kernel you can always use one of the other ones, maybe Faux's or Evolutionmods kernel. I actually currently use Evolutions kernel and it's quite nice. Also that ROM will work fine I believe, quite sure 1.55 is the latest OTA and if not it doesn't really matter. All though as some people have stated on your previous thread (i think?) you might as well use an optimized stock ROM such as CleanROM or ARHD (Android Revolution HD 8.1), all it is is a stock ROM thats been optimized for better performance and maybe has some tweaks to make it better. To be clear on the ARHD ROM, I stated the version because any higher version than that is for 4.4.3 which we currently don't have the firmware for.
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Glad you got your issue solved!
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
TraderJack said:
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
Click to expand...
Click to collapse
Can't say I ever used that option, it probably just didn't flash it correctly. You may want to post the problem in the recovery thread so they know about it.
In theory it should've worked the same way as flashing the zip. The only thing I could think of is how old the binary was or the location of the flash was incorrect.
Sent from my HTC6525LVW using Tapatalk
****EDIT****
Please see http://forum.xda-developers.com/showpost.php?p=56539897&postcount=9 for the Answer
*************
Hi all ,
I'm wanting to use NowTV (like SkyGo) on my OnePlus , however they are using a type of Root check that most root hiders cannot bypass.
Therefore I'm looking for a way to temp unroot and then root back again with ease.
just wondering if there are any tools or easy to follow guides?
thanks
Disable Superuser in SuperSU settings.
zoro25 said:
Hi all ,
I'm wanting to use NowTV (like SkyGo) on my OnePlus , however they are using a type of Root check that most root hiders cannot bypass.
Therefore I'm looking for a way to temp unroot and then root back again with ease.
just wondering if there are any tools or easy to follow guides?
thanks
Click to expand...
Click to collapse
Or if you are on a Cm nightly you can turn them off in the developer option
Disabling super user doesn't work, their detection method is unknown and they check more than the su binary.
I might try the nightlies, however I need stability.
Thanks for the responses so far
Outside of the nightly wing if you want stability use the M releases, they are designed to be more stable than the nightly branch
zoro25 said:
Disabling super user doesn't work, their detection method is unknown and they check more than the su binary.
I might try the nightlies, however I need stability.
Thanks for the responses so far
Click to expand...
Click to collapse
The problem isn't really the SuperSU as such, it's CM. They flag CM as a rooted ROM, it'll even happen if you're on stock un-rooted CM11S.
Transmitted via Bacon
I'm pretty sure that I saw an xposed module that could hide superuser completely. Might want to give that a try
skyguy126 said:
I'm pretty sure that I saw an xposed module that could hide superuser completely. Might want to give that a try
Click to expand...
Click to collapse
As per my post right above yours, it isn't SU that's the problem, it's that the ROM is CM.
Transmitted via Bacon
Timmaaa is correct and that's the info I wanted, I had tried the xposed modules but none worked and now I know why.
I'll contact sky and see if I get anywhere
****EDIT****
So it seems that Timmaaa is NOT correct as there is NO CyanogenMod or any ROM check, it's all to do with the the name of your Root App
Short Version is unroot and uninstall SU app for this to work (removing SU Binary or removing Root alone is not enough)
So we need to have a new Root app with a new AppID and name , and also the SU binary to be identified as something else for this to possibly work.
I now have NOWTV working , and it's on an Unrooted One+One with no SU App installed after running full Unroot (however my SUPro app is still installed)
Note that SUPro does nothing really and just gives extra functionality when the main SU app is installed.
Thanks for everyone help and input on this.
So it seems that you would have to
1)Full UnRoot (Which also uninstalls the main SuperUser app)
2) Watch what ever you wanted to on NowTV or SkyGO
3)Go through the Rooting process again as if it were a new device. (which will again stop NOWTV/SkyGo) from working.
Do steps 1 and 2 again to watch.
This would have to be done everytime you want to watch NowTV
zoro25 said:
Timmaaa is correct and that's the info I wanted, I had tried the xposed modules but none worked and now I know why.
I'll contact sky and see if I get anywhere
****EDIT****
So it seems that Timmaaa is NOT correct as there is NO CyanogenMod or any ROM check, it's all to do with the the name of your Root App
Short Version is unroot and uninstall SU app for this to work (removing SU Binary or removing Root alone is not enough)
So we need to have a new Root app with a new AppID and name , and also the SU binary to be identified as something else for this to possibly work.
I now have NOWTV working , and it's on an Unrooted One+One with no SU App installed after running full Unroot (however my SUPro app is still installed)
Note that SUPro does nothing really and just gives extra functionality when the main SU app is installed.
Thanks for everyone help and input on this.
So it seems that you would have to
1)Full UnRoot (Which also uninstalls the main SuperUser app)
2) Watch what ever you wanted to on NowTV or SkyGO
3)Go through the Rooting process again as if it were a new device. (which will again stop NOWTV/SkyGo) from working.
Do steps 1 and 2 again to watch.
This would have to be done everytime you want to watch NowTV
Click to expand...
Click to collapse
This is just a theory... may be wrong:
Can't you move the SuperSU app into /system/app instead of /data/app. Or does the NOWTV app have perms to check the integrity of /system also. Or can you change the app id of the SuperSU app with a simple decompile tool.
I did that while using cm11s. But still had problems trying to watch skygo. In the end I had alter my buildprop to a phone which supports skygo as at the time it didn't support oneplus one. Then full unroot etc to watch then root back to get root access again.