Problem with Root and SU - Verizon Samsung Galaxy Note II

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.

Related

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.

[Q] Superuser Problems Help!

Hey, Ok so i updated my Huawei u8650 to android 4.4.2 and something went wrong with my root. I can open superuser and it shows my binary and all that and it says im rooted but when i go to a app that requires root access like terminal emulator for example and i type in the command su. nothing happens it just goes to the next line. and i tried to mount my SD card partition in link2sd and it said that the script cant be created because its not allowed to su.
I thought it could be that superuser just wasn't allowing permissions but i open superuser and there's no apps, no logs or anything. I checked my settings and they're all fine and i even tried to use SuperSU instead and i still got the same thing. There's no prompt to allow access either. I don't know if the apps are just not trying to get root access or what? No app can get root permission and i need to get this fixed so i can fix some bugs on the rom. Please Help.
Thanks to all who attempt or do help. Ill be sure to hit thanks for u.
brewsterj98 said:
Hey, Ok so i updated my Huawei u8650 to android 4.4.2 and something went wrong with my root. I can open superuser and it shows my binary and all that and it says im rooted but when i go to a app that requires root access like terminal emulator for example and i type in the command su. nothing happens it just goes to the next line. and i tried to mount my SD card partition in link2sd and it said that the script cant be created because its not allowed to su.
I thought it could be that superuser just wasn't allowing permissions but i open superuser and there's no apps, no logs or anything. I checked my settings and they're all fine and i even tried to use SuperSU instead and i still got the same thing. There's no prompt to allow access either. I don't know if the apps are just not trying to get root access or what? No app can get root permission and i need to get this fixed so i can fix some bugs on the rom. Please Help.
Thanks to all who attempt or do help. Ill be sure to hit thanks for u.
Click to expand...
Click to collapse
i have never used this phone even never shown but i am trying to help you
i think you should change the superuser app that you are using
download the latest version of super user
Vaibhav Chauhan said:
i have never used this phone even never shown but i am trying to help you
i think you should change the superuser app that you are using
download the latest version of super user
Click to expand...
Click to collapse
thank u! u are the only one out of 50 people who's viewed this that's even attempted to help.
I am currently on the latest superuser app and i've also tried Super su as well and both do not do anything.
brewsterj98 said:
thank u! u are the only one out of 50 people who's viewed this that's even attempted to help.
I am currently on the latest superuser app and i've also tried Super su as well and both do not do anything.
Click to expand...
Click to collapse
why don't you try too reroot your phone
Vaibhav Chauhan said:
why don't you try too reroot your phone
Click to expand...
Click to collapse
I just rebooted and it didnt change anything
brewsterj98 said:
I just rebooted and it didnt change anything
Click to expand...
Click to collapse
lol..
i'm not saying to reboot
i'm saying to root it again(reroot)
Vaibhav Chauhan said:
lol..
i'm not saying to reboot
i'm saying to root it again(reroot)
Click to expand...
Click to collapse
oh xD well i tried that and it still wont give anything permissions. when i try to go into root explorer it says " cannot obtain root" then it gives me a error saying "char* ttyname(int)(3) is not implemented on android". i couldn't find anything on google about the error either.
brewsterj98 said:
oh xD well i tried that and it still wont give anything permissions. when i try to go into root explorer it says " cannot obtain root" then it gives me a error saying "char* ttyname(int)(3) is not implemented on android". i couldn't find anything on google about the error either.
Click to expand...
Click to collapse
sorry i don't know about the rooting method of this device
Vaibhav Chauhan said:
sorry i don't know about the rooting method of this device
Click to expand...
Click to collapse
i rooted by SRSroot first then first got the error then i unrooted and re-rooted by using the kingo root method but still received the same error. they are both windows programs u can run for root on multiple devices. They use USB debugging to root then device reboots and bam your rooted.
i used those methods because i tried to just flash the binary files through cwm recovery and it never actually installed into system. The two methods above installed binary and rooted my device but i cant give root access to any apps including superuser or supersu.
If anyone can help me with this it would be appreciated because i hit a wall and don't know what to do. No apps can get root permissions and i cant fix my play store, WiFi, speakers or theme chooser until the root is properly working because the methods to fix those bugs need root to function. so please if anyone has knowledge or any idea why i have root but cant get access please help me out.
brewsterj98 said:
If anyone can help me with this it would be appreciated because i hit a wall and don't know what to do. No apps can get root permissions and i cant fix my play store, WiFi, speakers or theme chooser until the root is properly working because the methods to fix those bugs need root to function. so please if anyone has knowledge or any idea why i have root but cant get access please help me out.
Click to expand...
Click to collapse
If there is a custom recovery available for your device I would recommend flashing that and then flashing the latest SuperSU.zip package in recovery. Part of the problem is the orginal Superuser (by ChainsDD) while excellent at the time is now extremely outdated and no longer really be maintained, as a result make sure you flash a Superuser package compatible with Android 4.4.2 such as the latest version of SuperSU.
shimp208 said:
If there is a custom recovery available for your device I would recommend flashing that and then flashing the latest SuperSU.zip package in recovery. Part of the problem is the orginal Superuser (by ChainsDD) while excellent at the time is now extremely outdated and no longer really be maintained, as a result make sure you flash a Superuser package compatible with Android 4.4.2 such as the latest version of SuperSU.
Click to expand...
Click to collapse
Where can i find it at? I have recovery on here but i cant seem to find the file. At this point i'll try anything.
Ok so i found the SuperSU.zip v1.99 via another XDA Forum(http://forum.xda-developers.com/showthread.php?t=1538053) and i flashed it then rebooted. Now my device says there is no binary and i am not rooted. I tried reflashing but the .zip does nothing. what should i try next?
Rooted again with SRSroot and still cannot get root access.........please help me out.
brewsterj98 said:
Rooted again with SRSroot and still cannot get root access.........please help me out.
Click to expand...
Click to collapse
You can try flashing Koush's Superuser in recovery, after please run root checker and tell me what is says it the status of your device.
I cant install root checker pro for some reason. I have the basic version installed, is that good enough?
brewsterj98 said:
I cant install root checker pro for some reason. I have the basic version installed, is that good enough?
Click to expand...
Click to collapse
The basic version will work just fine for our needs.
shimp208 said:
The basic version will work just fine for our needs.
Click to expand...
Click to collapse
OK so root checker says i have root access but i still cant access root permissions in apps. I took some screenshots of Link2sd, Terminal Emulator and root explorer so you can see what exactly is going on. I get some weird error in link2sd and root explorer that i have no clue what it is.
Anyone got any knowledge of this error?
brewsterj98 said:
Anyone got any knowledge of this error?
Click to expand...
Click to collapse
try root after factory reset

[Q] CleanMaster Root Access Failed

I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
I have been having this same issue on rooted stock gs4. It's temperamental when it comes to root I've noticed. One day I was able to turn it app off of auto start and when I installed a new app it wouldn't let me do it and su says I'm granted
I'm experiencing the same issues. Auto Start Manager is the only feature that has this issue.
Sent from my SPH-L710 using XDA Free mobile app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
I always face this issue also, what I do as a temporary fix is, go to the SuperSU app, then "Forget" Clean Master, open Clean Master and try to disable an app from Auto starting, grant root and the app will be disabled I hope it works for you too
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Unfortunately this does not work for me.
I have granted root access according to SuperSU Pro however when trying to stop autostarting apps in Clean Master it reminds me to allow access.
I even get a popup massage from SU stating that the app got granted root access.
Whats happening here? Does anyone have a work around?
Deleting Cleanmaster in SuperSU doesnt help. It is always the same unfortunately.
Best Regards
J
I too also have problems with the autostart function in Clean Master on my Optimus Zone II
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Re:Re: [Q] CleanMaster Root Access Failed
Vtrendzzy said:
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Click to expand...
Click to collapse
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
DerDoktorEsq said:
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
Click to expand...
Click to collapse
I can't argue over this. Best options for you 1. Root Cleaner (high priority) 2. SD Maid Pro (medium priority)
See the difference yourself.
fix?
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
dillweedinc said:
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
Click to expand...
Click to collapse
Has anyone figured out what the issue is here?²
hey..the main culprit is supersu app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Clean master root access
wow. cool...,ill try that,
thanx
it's supersu problem
StoneyJSG said:
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Click to expand...
Click to collapse
Just go thru my above post..it will definitely work..so give it a try... flashing new supersu 2.49 resolved the problem for me.?
Yep its working again. I tried 2.48 cuz somebody said it worked for them, but i had no luck there. 2.49 did the trick, thx for letting us know in the thread.
tycoon78[stoner] said:
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Its working for me too.
Thanks tycoon78 for the tip
RE:RE:RE: [Q] CleanMaster Root Access Failed/SuperUser
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Ahhh! Thank you so much tycoon! It works for me after updating super user!
QUOTE=Alison.Souza;60674697]Its working for me too.
Thanks tycoon78 for the tip [/QUOTE]
DerDoktorEsq said:
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Click to expand...
Click to collapse
I just rooted my s6 edge and was having the same issue with 2.46. Luckily when I updated to 2.49, I was unable to block the autostartup apps.

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.

How do you completely remove root & Xposed to pass Safetynet Helper Test?

Hello,
I have a Samsung Galaxy S6 Edge SM-G925W8 and had SuperSU root access and XPosed Framework installed. I am now attempting to remove all of it so that I can pass Google's safetynet helper test. I have tried numerous things, but the safetynet result is always:
SafetyNet Request: Success
Response Validation: Success
CTS Profile Match: False
I first attempted to remove Root by clicking "Completely remove root" within SuperSU. After doing this, Response Validation was false, which, after doing some research, I learned was caused by XPosed Framework. I then boot into TWRP recovery and flash the Xposed uninstaller. This causes my phone to boot loop, forcing me to restore a NAND backup to before I removed anything. I then try to flash the XPosed Uninstaller BEFORE removing root access and it runs successfully. After this, I use SuperSU to completely remove all root, which also runs successfully then give the phone a reboot removing the app entirely. This is when I receive the SafetyNet Helper response above stating CTS Profile match is false. I'm not sure how to fix this error.
Any suggestions would be very appreciated! Thank you
Edit: I have no idea why this thread appeared twice...sorry I can't seem to delete one of them
Er.. Any ideas?
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
vgplayer54 said:
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
Click to expand...
Click to collapse
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hello, I attempted to use ES File Explorer to search both the system/bin directory and the system/xbin directories. system/bin does not have the "busybox" or "su" files in them, so I assume they were removed when I uninstalled SuperSU. /system/xbin however does have these two files, but I am unable to delete them. I get the error "Cannot delete file". I'm guessing this is because I've already unrooted?
I then opened the terminal in my TWRP Recovery, however when changing directories into the system folder, the terminal shows that it is empty. when using ls -la, only two files are there, both called root and neither can be opened. rm -r /system/xbin/busybox does nothing either, it claims there's no such directory. Any suggestions? or just wipe?

Categories

Resources