Answer to SU problems on CM7???

Answer to SU problems on CM7??? - Motorola Droid X2

I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.

jsgraphicart said:
I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.
Click to expand...
Click to collapse
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!

Moon Shadow - NM said:
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Click to expand...
Click to collapse
Thanks Moon Shadow. The only time I had it hang on "asking for root access" is with Titanium Backup. I think that had to do with the SuperSU app freezing though when trying to get into the settings tab in the app. It just freezes up when selecting that and I had to go into application seetings and manually force stop the app. After that, everything worked fine. I think its just that settings tab for some reason.
The way I installed it was installed SuperSU from the market, then uninstalled the old Super User through the market. I then opened SuperSU and it asked to update so I did. After that, I went through all my root apps and the new SuperSU prompt popped up for all and I granted access. I too see the old SU in the app drawer. Opening that though shows that the only thing that its granting root access to is the new SuperSU app. It doesnt seem to be conflicting with anything so far.

Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.

xawen said:
Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.
Click to expand...
Click to collapse
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Sent from my MB870 using Tapatalk

i find this relevant to my interest any one else test

Xb0i said:
i find this relevant to my interest any one else test
Click to expand...
Click to collapse
Follow xawen's directions and you'll be fine. It works like a charm.
Sent from my MB870 using xda premium

cant uninstall superuser from settings- applications. doesnt give the option

Xb0i said:
cant uninstall superuser from settings- applications. doesnt give the option
Click to expand...
Click to collapse
Did you go Settings> Applications> Manage Applications and hit the app? If you dont see that option, go into Titanium Backup (an app you have no excuse not having) and uninstall it. Then go into Root explorer and follow the above directions to totally remove it. Then reboot. It may seem like it isnt totally gone cause you may see the icon somewhere, but it likely is gone and a reboot is needed in order to confirm.

yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.

Xb0i said:
yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.
Click to expand...
Click to collapse
Its what I did. Its a bit of a deviation but it got the job done and thats what matters, ya know?

wow pretty bizzare i cant find superuser in TiBu! whats goin on lol

Xb0i said:
wow pretty bizzare i cant find superuser in TiBu! whats goin on lol
Click to expand...
Click to collapse
Did it disappear after you rebooted? If you have root explorer, go into system/app and see if SU is still gone. If so, you're in good shape.

to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd

Xb0i said:
to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd
Click to expand...
Click to collapse
I can't find superuser in TB either... it is kind of weird...

i believe u cant delete superuser from tibu cus u need superuser for root access so its like a paradox. i dunno y instructions were as someone showed cus it seems the only way to get this to work properly is delete from root explorer. but im gunna hold off till someone confirms this more legit

I don't understand why you're holding off...if SuperSU is active, go for the reboot and see if the old superuser app clears.
Sent from my MB870 using xda premium

id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053

Xb0i said:
id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
It's odd that you guys don't see the uninstall option for it... Do you see it in Market (err...Google Play, stupid name)? That's another way to get the uninstall done. If it doesn't show up there, you should be able to use root explorer and delete it from /data/apps and /system/apps.
When we installed CM7, the instructions had us update Superuser from market. That would have installed it in /data/apps, so it just needs to be yanked from there. Uninstall via market, tibu, settings>apps or manual through root explorer should all do the same thing. Then you can delete the built in one from system.
Also, if for some reason the whole process breaks down on you...there's a flashable version of the original Superuser that will probably get you going again. I haven't tried it on CM7 though...
jsgraphicart said:
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Click to expand...
Click to collapse
The most recent update (pushed yesterday) fixed this for me.

Related

how do I uninstall Tmobile Visual Voicemail on Axura

So I just flashed Axura 2.2.5.9 and have kernel version 2.6.32.9 and well I wanted to use visual voicemail from Tmobile, but it won't let me install the newest version. So I tried to uninstall the older version that came with the rom and it won't let me.
The uninstall button is grayed out.
When I try to download the newer version from the market it says, "duplicate provider authority."
Thanks

vahdyx said:
So I just flashed Axura 2.2.5.9 and have kernel version 2.6.32.9 and well I wanted to use visual voicemail from Tmobile, but it won't let me install the newest version. So I tried to uninstall the older version that came with the rom and it won't let me.
The uninstall button is grayed out.
When I try to download the newer version from the market it says, "duplicate provider authority."
Thanks
Click to expand...
Click to collapse
easiest way is through Root Explorer, simply delete the .apk file from /system/app
or, if you have ADB on your PC, access your device through adb, and type the following commands:
adb shell
su
mount -o rw,remount /system
cd /system/app
rm nameof.apk
reboot
hope this helps

Well, using the app "Super manager" as my root explorer didn't work, so I ended up purchasing "SystemApp Remover" from the market and it worked well. As for the other method you described above was above my tech level and knowledge so I figured I'd find an easier method with keeping that as a last case scenario.
I got rid of Voicemail notifier, google voice and visual voicemail. Worked like a charm.

vahdyx said:
Well, it didn't work, but I ended up purchasing "SystemApp Remover" from the market and it worked well.
I got rid of Voicemail notifier, google voice and visual voicemail. Worked like a charm.
Click to expand...
Click to collapse
yes thats a good app....but the above methods undoubtedly work. did you even try them? if they didnt work, which method did you try, and what part of it didnt work? they are two of the original ways of removing system apps, theyve been around almost as long as root access for Android was discovered....good things to know and learn
if someone is trying to help you, dont just say the methods dont work.......either admit that you didnt even try, or post what went wrong, cause it couldve been something you did...because if another person who has this same problem sees this thread, they will automatically think these things dont work and will lose solutions to their problem.
^^^this goes for any situation, not just this one

Okay my apologies,
I went to the market and tried to find a root explorer but couldn't find a free one so I downloaded "Super Manager" app
I went into system file and long pressed on the file and tapped delete, the file just sat there. I did it again and it wouldn't delete. I restated my phone and it still didn't work.
So it wasn't necessarily the above method that didn't work it was the app that didn't work. I'll correct the post above as well.

I had a problem with system app remover before as I think it didnt just delete the apk but core processes linked to the apk I had a unbelievable flurry of fc maybe that was just my experience but root explorer is indisputably the easiest way to delete apk's cause you don't need anything other than the phone to do so

Yeah, ditto that @wills, I would advise to just freeze the process in titanium and go from there. I wouldn't remove it.
Don't blame me, blame my keyboard's autocorrection algorithm.

I deleted about 10 apps from system/app using root explorer. Not sure why a lot of the bloat was left in/inluded in the latest axura... I wish apps that can be grabbed for free from the market could be left out. ESPECIALLY the bloat from samsung.
I mean, why include samsung widgets when you removed touchwiz?

[Q] Permissions issue

I'm getting permissions issues whenever I try to run any root apps. I get a message like this: "SetCPU could not obtain root access. Did you allow SetCPU through Superuser Permissions? Operating in read-only mode." Everything is set to "allow" in Superuser, and I have tried rebooting into recovery and clicking "fix permissions." It tells me that permissions were fixed, but when I reboot, the problem persists. I'm on the latest Synergy. What do I have to do to get my phone back to normal?

SamOliver said:
I'm getting permissions issues whenever I try to run any root apps. I get a message like this: "SetCPU could not obtain root access. Did you allow SetCPU through Superuser Permissions? Operating in read-only mode." Everything is set to "allow" in Superuser, and I have tried rebooting into recovery and clicking "fix permissions." It tells me that permissions were fixed, but when I reboot, the problem persists. I'm on the latest Synergy. What do I have to do to get my phone back to normal?
Click to expand...
Click to collapse
Sounds like maybe SuperUser is still denying these apps (although a user would have to tell super user whether or not to allow a root app). Run Super User and delete these apps from the list and re run the problem app and set allow again.
Sent from my brain.

baronmxc said:
Sounds like maybe SuperUser is still denying these apps (although a user would have to tell super user whether or not to allow a root app). Run Super User and delete these apps from the list and re run the problem app and set allow again.
Sent from my brain.
Click to expand...
Click to collapse
That didn't work, and when I try to update Superuser the last thing it says in the log is "Gaining root access... fail!"
I'm gonna re-install my ROM and see if that does the trick.
EDIT: I think it might have gotten messed up when I pulled the battery out when it was booting. In case anyone has the same issue in the future, I just flashed my ROM again (right on top of the old one) and it fixed the problem.

I've had that issue with shootme since superuser/su updated last, but haven't bothered to really look into it since cyanogen has screen shot built into it.

[Q] CM7.2 RC1 and Google Play

So I jumped on the cyanogen colored band wagon. Don't' get me wrong, this is the ROM I've been waiting for. Only now I am having issues. Google Play (formerly Marketplace) force closes every time i start it up.
I've done the required, check to see that English (united states) is set. Even did a wipe dalvik from CWM. so far Play has not responded to my advances. I was wanting to get it back up and running cause with out it, I don't' have Gmail, Google Maps, and a few other apps I use.
My atrix timeline:
Bought the phone with Froyo on it, and used this guide to unlock and root. Then I installed Alien ROM 4 to my device to get me to Gingerbread (2.3.4.) I stuck with that build till last night when I flashed CM7.2 RC1 to my phone.
Nothing strange happened while I did this. Followed the guides to the Tee.
What I think may have happened, when I used TiBu to restore my apps, it may have borked Play/Market.
Also, not sure why some of the gapps didn't' come along. I did flash them, right after CM7, then rebooted. I got a screen/list of apps, but not sure what I did to prevent some of them from NOT loading.
I've even tried to flash the gapps from CWM again, in hopes that would fix things... Nope.
The answer is probably, "Do a fresh install of CM7.2," but I want a second opinion before I do this.
Forgot to mention I removed tenfars cwm and used the one in the tuts by the CM wiki

I had the same issue with the play store. The way I fixed it was I first uninstalled the play store. Then I got a copy of the old market. I then renamed it vending and placed the apk in the following directory using root explorer (need to make sure the root explorer is set to Mount R/O):
system>app
After that I changed the permissions for the market apk. I made sure read, write, and execute were all cheeked under owner and clicked ok. I then exited root explorer and rebooted the phone. Once the phone booted back up I had the old market again. Then I went back to the system>app directory and changed the permissions back to the default (probably don't have to do this, but did it just in case). After that I opened the market and agreed to the terms. I then exited the market and waited a few minutes and went back it. I was then automatically pushed the play store and had no more FCs.
Attached is the original market.

Permissions should be set to RW/R/R and none set to executable.
Sent from my MB860 using xda premium

CaelanT said:
Permissions should be set to RW/R/R and none set to executable.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I know that's what permissions are suppose to be set to, but it wouldn't install the app for me until I also checked execute.

Dark9781 said:
I know that's what permissions are suppose to be set to, but it wouldn't install the app for me until I also checked execute.
Click to expand...
Click to collapse
Happened with me to..all i didwas uninstall updates through the app settings. I think it has something to do with corrupted cache data. Before i got it fixed I'd clear cache from there to and it'd work for a little bit.
Sent from my VS910 4G using XDA

I've not had time to get back to this yet but may work on it tonight. Firstly I don't have root explorer on my phone, nor the experience to mess with setting permissions. Will a reinstall possibly fix my issue?
Is there any other way of going about fixing the issue using TiBu? Maybe uninstalling play and rerunning gapps?

ROOT Weirdness

Hi all; I just got a Galaxy Note and successfully installed CWM and rooted using DA_G Odin PDA method.
Could anyone help me with the following please?
1. Superuser app looks funny on screen, like its not formatted correctly some screen layers are on top of others... it looks messed up lol. It does actually work though(grants or denies root access).
2. Titanium Backup is complaining about my root access and how SU is not working correctly. Though if I grant it root access it does actually work correctly.
This seems to have started after a factory reset.

xda1zero said:
Hi all; I just got a Galaxy Note and successfully installed CWM and rooted using DA_G Odin PDA method.
Could anyone help me with the following please?
1. Superuser app looks funny on screen, like its not formatted correctly some screen layers are on top of others... it looks messed up lol. It does actually work though(grants or denies root access).
2. Titanium Backup is complaining about my root access and how SU is not working correctly. Though if I grant it root access it does actually work correctly.
This seems to have started after a factory reset.
Click to expand...
Click to collapse
1) It always looks like this, has nothing to do with a factory reset. Install Super SU from the market if you don't like the look of Superuser.
2) Yes, this is how it works. Titanium Backup requires root to run. So that makes sense that it works correctly when you grant it root. So I am not sure I get the question.

jpeg42 said:
1) It always looks like this, has nothing to do with a factory reset. Install Super SU from the market if you don't like the look of Superuser.
2) Yes, this is how it works. Titanium Backup requires root to run. So that makes sense that it works correctly when you grant it root. So I am not sure I get the question.
Click to expand...
Click to collapse
Point 1- Yes did that, DA_G root method does not come with the superuser app. The superuser app literally looks messed up... from your reply your implying that's normal(or not)?
Point 2- When I start Titanium backup, it complains that my SU is messed up. If this is normal behavior for the Note, so be it, just checking
Moderators- I apologize if this thread does not belong in the general section, I would appreciate if it can be moved, if needed, thanks

When asking for SU acces at TB screen is the "remember" checked off? If it isnt thats why its always asking you. I had an issue like you and a simple reboot remedied it. If that doesnt help, remove and reinstall both apps from market again. Reboot and see if that fixes it.
The SU app does look weird on our phablets. But it works as expected.

several apps having issues now on rooted Marshmallow

I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.

My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.

njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.

dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.

chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app

dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'

chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.

njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?

I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app

after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?

dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?

njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.

dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.

Better Mobile App

welcome