Hi all,
In a rooted phone, if an app does not ask for super user access (as reported by the Superuser app), does it have exactly the permissions it has in a non rooted phone?
Thanks,
K.
if it doesn't ask for SU permissions, but it works its not a rooted app, now if it doesnt work it might be a rooted app and you might have to fix permissions
edit: if it works yes it has the same permissions
Related
Is Titanium Backup supposed to not be getting root currently on the A500? Other apps like Root Explorer seem to get root and work fine. Titanium Backup on my A500 complains that it can not get root. I did say allow on the Superuser box and after Titanium Backup complained of not having root, I opened Superuser and saw that it was indeed given permission to have root. Could I maybe not have obtained root correctly with Gingerbreak or is this just a problem for everybody now?
I got root fine after the update. Did you update busybox?
Sent from my A500 using XDA Premium App
I have this problem before, I find out because I didn't root it probably and install superuser
, so titanium backup can not run without root permission which superuser haven't got too.
To fix that, simply just reroot it, step by step again, after that mine run fine.
Sent from my A500 using XDA Premium App
try to update busybox
Luigi
enigmatl said:
Is Titanium Backup supposed to not be getting root currently on the A500? Other apps like Root Explorer seem to get root and work fine. Titanium Backup on my A500 complains that it can not get root. I did say allow on the Superuser box and after Titanium Backup complained of not having root, I opened Superuser and saw that it was indeed given permission to have root. Could I maybe not have obtained root correctly with Gingerbreak or is this just a problem for everybody now?
Click to expand...
Click to collapse
Busybox! 10char
busybox installation solved that for me
Re-ran Gingerbreak everything is great now, thanks for the tip!
I just updated via OTA to build 4.010.40_COM_GEN1 (from 4.010.24_COM_GEN1). After the update when I rooted the tab and started superuser it is giving a warning:
"Package com.acer.android.fixwifi was found to be requesting permission to respond to Superuser requests. It's likely that this app is malicious and attempting to grant superuser access without your knowledge. It is recommended that you should uninstall it."
There is an app by the name of fixwifi, but it is a system app with no uninstall option. And if it is a system app then why the superuser request? Any help is appreciated.
mznk said:
I just updated via OTA to build 4.010.40_COM_GEN1 (from 4.010.24_COM_GEN1). After the update when I rooted the tab and started superuser it is giving a warning:
"Package com.acer.android.fixwifi was found to be requesting permission to respond to Superuser requests. It's likely that this app is malicious and attempting to grant superuser access without your knowledge. It is recommended that you should uninstall it."
There is an app by the name of fixwifi, but it is a system app with no uninstall option. And if it is a system app then why the superuser request? Any help is appreciated.
Click to expand...
Click to collapse
Interesting. I'm guessing that rather than actually fix the wifi bug, they've written an app that detects when it is occuring and simply deletes the dhcp-wlan0.lease file itself with root permissions... Malicious, probably not, but a potential security risk, possibly.
Is this update prerooted? If not, how can they put an app that asks for superuser privileges? Were they expecting the user to root for the fix to work?
I am not an expert, but I think you need to be cautious with it.
Biologos said:
Is this update prerooted? If not, how can they put an app that asks for superuser privileges? Were they expecting the user to root for the fix to work?
I am not an expert, but I think you need to be cautious with it.
Click to expand...
Click to collapse
No clue about the merit of the app.
But if the user is not rooted they would not see the request to allow or disallow. It would just go.
By the way, the fix wifi apk is located in /flexrom/
There seems other apks located there which is flashed by flashing the flexrom.img
Biologos said:
Is this update prerooted?
Click to expand...
Click to collapse
No, it was an official update therefore not prerooted
ardatdat said:
By the way, the fix wifi apk is located in /flexrom/
Click to expand...
Click to collapse
Yes, it is in /flexrom/app along with Kobo, apkinstaller and checkerlaunch(?). But if it is a system app then shouldn't it work in the background without any superuser request.
How can I launch an application to give it root permissions ? Can I possibly edit the apk without writing the program over ?
Sent from my HTC HD2 using Tapatalk
You first need to root your phone. You could use z4root.apk. try searching the forums or google it. Apply permanent or temporary. I applied permanent root. The app will notify if a root is successful. Then you will need to have superuser app installed. Normally all the roms comes preinstalled with superuser. If an app asks for permission for root access just grant it and you're done.
Sent from my HTC Runnymede using XDA App
hairuleff81 said:
You first need to root your phone. You could use z4root.apk. try searching the forums or google it. Apply permanent or temporary. I applied permanent root. The app will notify if a root is successful. Then you will need to have superuser app installed. Normally all the roms comes preinstalled with superuser. If an app asks for permission for root access just grant it and you're done.
Sent from my HTC Runnymede using XDA App
Click to expand...
Click to collapse
?
My device is already rooted with SuperUser added ...... What im trying to do is give an app which was downloaded from the market root permissions . now the only way i personally know how to give an app root permissions is by FIRST programming it with root permissions . Once its compiled i dont thing i can launch an app as root . But i may be wrong . hence the thread
elesbb said:
?
My device is already rooted with SuperUser added ...... What im trying to do is give an app which was downloaded from the market root permissions . now the only way i personally know how to give an app root permissions is by FIRST programming it with root permissions . Once its compiled i dont thing i can launch an app as root . But i may be wrong . hence the thread
Click to expand...
Click to collapse
U can only give Root Permission if the app and for it
Hi!
I've got a problem with root access of an app, it just doesn't ask for root permission but gives me a warning that it needs root access.
I already tried to use superSU instead of Superuser, but it didn't work. I unrooted and rooted the phone back, didn't work either. I'm sure the phone has root permission because after the rooting superuser asked me to give root permission to "system" and I also managed to write files in the obb and data folders.
It's driving me mad because it seems that the root is working but the app just don't ask for root permission.
P.S. The app is Freedom, v1.0.6
Thanks for the help!
What app did you mean which cant get root permission?
Sent from my GT-I9205 using XDA Free mobile app
I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
So to clarify, if we want android pay to work we can't use xposed?
Sent from my Nexus 6P using Tapatalk
Wehdota said:
I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
Click to expand...
Click to collapse
sweet, i flashed 2.62 thinking it was systemless root too and android pay stopped working. came here looking for a solution, deleted /su/xbin_bind and android pay is working again!
Giving Root Access?
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
I'd like to know this as well
leamdav said:
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
Click to expand...
Click to collapse
Some apps don't ask for root by default, and only do so when you tell them you want to enable the features that require root. ES File Explorer is one such app, and to enable root features you have to open the side menu and toggle the option.
IMO this is the way all apps should be, as I don't always need the root features of every app, as it adds a security risk. I like how BoldBeast Call Recorder does this for example.
bkkzak said:
I'd like to know this as well
Click to expand...
Click to collapse
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
It's a compatability mode that was automatically enabled for a while in older SuperSu.zips to allow developer's apps to work until they update their app to work with systemless root. It is now disabled by defult in newer SuperSu.zips, with the user having to explicitly enable it for its use.
Some apps that requires this to work (becuse they haven't updated their app to work with systemless yet) include:
- Secure Settings
- Es File Explorer.
Etc.Etc.
Hope this helps clarify things for you