Related
Ok just got a replacement Vibrant. I Immediately went to the official release of froyo to test. Installed fine using KIES. Attempted to Root and did so successfully using the SuperOneCLick app wich when finished tested and confirmed root. Went to install Busybox and it gives me the Nand locked error.
1)Is there a way to confirm phone is nand locked?
2)Ive only found a way to unlock nand is for the Bell version or requires a paid app or extra non Tmobile sim card (wich I dont have). Is there a way to unlock nand for Tmobile not involving either sim card or cash?
3)Is it possible to odin a different rom/kernel (namely TW's Newest Nero) if phone is nand locked and have working busy box/root?
open titanium backup and click on 'problems?' to d/load busybox, same issue?
Yes it downloads busybox and then says "failed" after verifying busybox. Says cannot get root permissions. Please verify you have root and Busybox.
download terminal
open it
type "su" (no quotes)
what did it return?
SU comes up with "Permission denied". Should I try using the "update.zip" method with froyo? As i said the other program confirmed root supposedly. Super User Is installed BTW.
Did you follow this guide?
http://forum.xda-developers.com/showthread.php?t=925400
Ok that was the guide i was following. Issue was that whenever I tried to dl the recommended file manager from market , It would show the dl completeing and then close with the application never installing and not showing up in applications. I had already had ES File explorer installed as that was my favorite on my initial vibrant (pre official 2.2) because the ease of transferring files wirelessly and other functions. I uninstalled ES and ran Titanium again and this time was prompted for SU rights. After giving rights to Titanium i again ran the "Problems" button and ths time busybox installed. Restarted Ti and ran "Problems" and updated busybox just fine.
Seems my immediate issue is done. Now on to backup and then ROM's.
You, my friend, deserve a big, sloppy, man kiss.
*BTW The app Super Manager is still not installing for me even after removal of ES and reboot of phone.
Open titanium backup
Select "market"
Wipe data
Wipe it again for good measure.
Still in tb
Menu > market doctor
Fix market links
reboot
Open market
Agree to terms
Issue fixed?
Perfect that did the trick. Never knew about that feature in Ti Backup. Again many thanks. Working on the CWR signature issues now, following this guide http://forum.xda-developers.com/showthread.php?t=833423 . Dont want to do anything until I have a nandroid to fall back on.
SOC windows error / help!
Whenever i try to run the Superoneclick program it gives a windows error & doesn't run.
I get it that this is an important help in rooting a phone & none of the other methods work on the X10 mini pro with the same firmware i have which is : 2.1.1.A.0.6 so if there is anyone who can help , thank you in advance
Model No. U20i
Firmware Version 2.1-update1
Kernel 2.6.29
Compilation No. 2.1.1.A.0.6
Long time listener; first time caller.
Short version:
I rooted my SGSII with CF root. Everything seemed fine, but now any app that needs superuser permission says 'Superuser has stopped unexpectedly.' How can I fix it? Can I uninstall and reinstall Superuser?
Long version:
I loved the first galaxy. Then I moved to China. Really missing everything American, so I saved and bought an SGSII in China. Surprised to find no Android Market. Apparently Google and China don't like each other? My phone came with Superuser and Titanium Backup...I don't know what that means; I'm inexperienced at rooting. Used the wonderful instructions in the forums (genuinely appreciative; not sarcastic) to CF root my phone. Went smoothly; now I also have CWM app. But if I try to run CWM or Titanium Backup or anything else that requires Superuser permission, I get a vibrate then a double vibrate and a message that says 'superuser has stopped unexpectedly.' Superuser icon is still there; if I open it, it lists the one program I granted Superuser access to before rooting my phone (Market Enabler). Perhaps the problem is that a second Superuser was added over the first? How can I make Superuser work again? Sidenote, how can I install Android Market now?
I'm a new poster and can't post to development threads. Any help would be greatly appreciated! Thanks!
Reroot .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Thank you JJEgan for your reply! I have tried re-rooting it again, but I'm still having the same difficulty. If I try to open something that requires Superuser permission, I receive the message 'Superuser has stopped unexpectedly.' Also, when I open Superuser or try to search for an update, I get 'Checking available version failed.'
Can I fix this by removing superuser altogether, then flashing again to get the unbroken one back? If so, how can I remove Superuser? Can't seem to find an uninstall button....hahahahaha.
Again, thanks for any helpful ideas anyone has!
Needs to be removed from /system/app, which only a root user can do...
Perhaps you can go to settings, applications, manage apps, show all, clear for superuser, and this might stop it from crashing.
Again, Tonymy01, I greatly appreciate your reply! I have cleared the superuser data, but that didn't help. I also tried resetting to factory then rooting with cf again, but still I have no joy.
Would installing a new version of superuser over the old version solve my problem? Ugh.
A preemptive thanks for any suggestions anyone may have.
ericwadding said:
Again, Tonymy01, I greatly appreciate your reply! I have cleared the superuser data, but that didn't help. I also tried resetting to factory then rooting with cf again, but still I have no joy.
Would installing a new version of superuser over the old version solve my problem? Ugh.
A preemptive thanks for any suggestions anyone may have.
Click to expand...
Click to collapse
i dont know if this would help but try getting superuser from the market and see if that works?
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.
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
Kind of random but Moon, you are a goddamn machine. The moment something great releases you take it apart and make it better. Good **** man, good ****.
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.
So, when I rooted I installed SuperSU and uninstalled Superuser.
Went through the steps to from the mod to get all apps into the multi view window. During the move odex services I got stuck in bootloop and had to re-odin the root image file.
Now that everything is set superuser is obviously the file back in charge of handling SU prompts from apps but for some reason it's not accepting/hearing them so anything I install that requires root is crashing.
Attempted clearing the SU data but it didn't help.
Is there anyway to fix this short of flashing back to stock then back to root?
Would mounting the system as writable, deleting SU and then re-flashing the root image fix the problem?
Basically I'm trying to avoid resetting my phone up to get this done.
Hitman3984 said:
So, when I rooted I installed SuperSU and uninstalled Superuser.
Went through the steps to from the mod to get all apps into the multi view window. During the move odex services I got stuck in bootloop and had to re-odin the root image file.
Now that everything is set superuser is obviously the file back in charge of handling SU prompts from apps but for some reason it's not accepting/hearing them so anything I install that requires root is crashing.
Attempted clearing the SU data but it didn't help.
Is there anyway to fix this short of flashing back to stock then back to root?
Would mounting the system as writable, deleting SU and then re-flashing the root image fix the problem?
Basically I'm trying to avoid resetting my phone up to get this done.
Click to expand...
Click to collapse
I thought for sure that SuperSU is what was used in that file but I guess there must be a couple out there? The method I used never installed Superuser...?
EDIT: Nevermind I see that there are 2 different root methods and one uses SuperSU. Sorry
shojus said:
I thought for sure that SuperSU is what was used in that file but I guess there must be a couple out there? The method I used never installed Superuser...?
Click to expand...
Click to collapse
I used the file from imnuts, which used superuser and not supersu.
I went ahead and deleted superuser, xbin/su and am reflashing. hope this fixes the problem.
which worked until the phone randomly rebooted and got stuck in loop..
and it was either sdpeed increase or lbe privacy guard causing it.
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
droidstyle said:
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
Click to expand...
Click to collapse
Ive even removed superuser and installed supersu and doing the all apps mod was causing this issue.
I have a feeling it could be because I was renaming the services.odex file before replacing it.
Trying a direct overwrite was causing a non stop bootloop I couldn't get out of 4 seperate occassions.
droidstyle said:
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
Click to expand...
Click to collapse
100% agree! I have not used Superuser for ages... Far superior imo...
shojus said:
100% agree! I have not used Superuser for ages... Far superior imo...
Click to expand...
Click to collapse
after rooting I feel like the touch screen has lost some sensitivity. not sure if it's just me and the day or I'm just loco.
and what I mean specifically is when flipping through my home screens they like to snap back now and then.
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.