Related
Hi there,
I Installed SuperSU 2.36 using TWRP (following the process in Nexus Root Toolkit app) and it looks fine but when I'm trying to run some app with root permisions like XMODgames or GameKiller the root permission screen appear and I select Allow (Permitir) but when the app is trying to run some game it say No Root access... I saw the register into Supersu (even I bought the Pro Version) and it show error: only position independent executables (PIE) are supported...
I verified the root permission with Root Checker App and it looks fine as rooted... even I tried successfully to re-install Supersu and update the binary and everything looks fine but all the app's that are asking root permission (and I already granted) does not work. the register show the same error message about PIE on each app...
I have a Nexus 7 (wifi 2013) with 5.0 LRX21P compilation...
Could you please help me to fix this?
Thanks in advance!
Those app are not supporting Lollipop yet. Contact their developers, this is not fault of SuperSU.
Srandista said:
Those app are not supporting Lollipop yet. Contact their developers, this is not fault of SuperSU.
Click to expand...
Click to collapse
oh really? Thanks a lot!
I will review with another apps
Thanks
Hello.
I'm having a problem using SuperSU 2.46. When I first installed it from Google Play it wouldn't work right but after reinstalling it, it worked fine until I rebooted my phone. After doing that it no longer prompted for root access. The only way I could grant root access was if I enabled root access for all apps without prompt and even after that my phone would freeze up after a while and I'd have to do a battery pull. Before I installed SuperSU, root access worked for most apps without a superuser prompt but I've found one or two apps on my phone that required superuser before enabling access to root features. The binary installation/update worked fine so I'm at a loss for what to do. I've tried uninstalling/reinstalling it several times.
My phone is an LG Ultimate 2 (lg l41c) running Android 4.4.2. I rooted it using towelroot. It does not have a recovery flashed as I have yet to find one designed for it. I thought that could be the problem but I'm not sure. As I said, most root capabilities worked before I installed a superuser app but it all ceases to work after rebooting my phone with SuperSU on it and the only way I can get it to work is by granting root access to all apps without prompt and even then my phone freezes and needs a battery pull. I'll take any help I can get.
I have the same issues in my note 4 except the freezing part
Any idea for this?
The problem seems to have solved itself. I installed SuperSU again today and everything seems to be going fine for now. I don't know what changed but I'll post again in the future if I run into any more problems.
Sent from my LGL41C using XDA Free mobile app
Same problem happening here on a Galaxy S5 Active. I've reinstalled and even put 2.48 beta on it.
The strange thing is the "Apps" list remains blank the entire time. Log shows apps using root, but they never get added to the list and I have to default "grant" everything for apps to work (at least, the ones that will work with this half broken root).
harmgsn said:
Same problem happening here on a Galaxy S5 Active. I've reinstalled and even put 2.48 beta on it.
The strange thing is the "Apps" list remains blank the entire time. Log shows apps using root, but they never get added to the list and I have to default "grant" everything for apps to work (at least, the ones that will work with this half broken root).
Click to expand...
Click to collapse
I wonder if some userids got munged. Try this in a terminal:
find /data/data/eu.chainfire.supersu -exec stat -c %u {} \;
You should only get about three owner ids: 0; 1023(or other 4-digit); and only one 5 or more digit number for SuperSU.
Frank
Find and Stat command not found.
harmgsn said:
Find and Stat command not found.
Click to expand...
Click to collapse
You can check the owner IDs in that directory with
ls -l eu./data/data/chainfire.superuser
If I got the path right -- it should be what I have in my previous message but I can't see it right now.
Frank
drwxrwx--x u0_a184 u0_a184 2015-04-17 08:05 cached
rwxrwx--x u0_a184 u0_a184 2015-04-17 08:08 files
lrwxrwxrwx install install 2013-12-31 18:00 lib -> /data/app-lib/eu.chainfire.supersu
drwxr-xr-x root root 2015-04-17 17:33 logs
drw------- root root 2015-04-16 23:58 requests
drwxrwx--x u0_a184 u0_a184 2015-04-17 08:08 share
Starting with Android 4.4 (KitKat) Better Battery Stats (BBS) require installation as system app to be able to collect the stats.
BBS must re re-installed as system app after each ROM upgrade (upgrade that does not preserve third party system apps).
I have found an alternative to this - the required permissions can be granted to BBS when it is installed as a regular user app by running these commands in Android Terminal (or ADB shell session):
Code:
su
pm grant com.asksven.betterbatterystats android.permission.BATTERY_STATS
pm grant com.asksven.betterbatterystats android.permission.DUMP
After using these commands it might be required to restart BBS process (e.g. reboot the device). Permissions granted this way will be preserved across ROM upgrades (even across those completely overwriting /system partition).
This has been tested on CyanogenMod 12.1 nightlies (Android 5.1.1).
Update! This post on BBS thread describes a related method for granting (at least part of) the permissions without root.
Hi DavisNT,
I'm confirming that your adb code appears to be a successful workaround for the normal version of BBS downloaded from the Play Store when the phone is running Lollipop. I'm running the paid version of BBS, on the current CM12.1 Nightly (jfltetmo for my T-Mobilr SGH-M919 Galaxy S4).
Procedure:
1. Install BBS from the Play Store.
2. Use ADB (easy to cut and paste from here) or another terminal program (you'll be typing) to install the code.
3. Reboot the phone.
You'll notice that when you launch BBS, CM's "Privacy Guard" will see that BBS is trying to gain root access, and will prompt you to allow this. I selected "Always Allow" until I'm done my battery testing. You'll notice that you now see "#" up on the phone's status bar. That indicates an app is running with root access. You could probably quiescence this by choosing "Ignore" via Privacy Guard.
Could the developer please approve that this relatively easy workaround is kosher?
Thanks . . .
Moved to main thread to avoid orphan
For apk downloaded from xda change the code to
pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS
pm grant com.asksven.betterbatterystats_xdaedition android.permission.DUMP
I tried this method, but failed on the BATTERY_STATS permission, the error said this 'permission type is not changeable'
is this method still valid?
andycjw said:
I tried this method, but failed on the BATTERY_STATS permission, the error said this 'permission type is not changeable'
is this method still valid?
Click to expand...
Click to collapse
On what version of Android did this fail? And was 'su' used before 'pm grant'?
Same problem. I'm on CM, Android version 4.4.4. Used 'su' before.
bobcote said:
Same problem. I'm on CM, Android version 4.4.4. Used 'su' before.
Click to expand...
Click to collapse
Most likely this method works only on Lollipop and Marshmallow.
Looks like on KitKat BATTERY_STATS permission does not have development in its protectionLevel, but on Lollipop and Marshmallow it has.
I assume (please correct me if I am wrong, preferably with link to some authoritative documentation) that development in protectionLevel allows a permission to be granted by pm grant command.
Thanks
I can confirm that this method works flawlessly for the Sprint version of the Galaxy Note 3 5.0. Many thanks.
Guys where is the main thread? Pls ?
DavisNT said:
Starting with Android 4.4 (KitKat) Better Battery Stats (BBS) require installation as system app to be able to collect the stats.
BBS must re re-installed as system app after each ROM upgrade (upgrade that does not preserve third party system apps).
I have found an alternative to this - the required permissions can be granted to BBS when it is installed as a regular user app by running these commands in Android Terminal (or ADB shell session):
Code:
su
pm grant com.asksven.betterbatterystats android.permission.BATTERY_STATS
pm grant com.asksven.betterbatterystats android.permission.DUMP
After using these commands it might be required to restart BBS process (e.g. reboot the device). Permissions granted this way will be preserved across ROM upgrades (even across those completely overwriting /system partition).
This has been tested on CyanogenMod 12.1 nightlies (Android 5.1.1).
Click to expand...
Click to collapse
Does this method work on marshmallow?
Thank you
RoxAbout said:
Does this method work on marshmallow?
Thank you
Click to expand...
Click to collapse
Most likely yes. Feel free to test. [emoji2]
Can anyone post BBS apk please!! TQIA
Thanks dude. The command for xdaedition worked flawlessly on my RR rom. Android 6.0.1 Galaxy S3
Worked! Thanks.
Does this works on a non-rooted phone? if it works, is uninstalling as simple as accessing app under setting to uninstall?
Thanks.
nuthing03 said:
Does this works on a non-rooted phone? if it works, is uninstalling as simple as accessing app under setting to uninstall?
Thanks.
Click to expand...
Click to collapse
AFAIK This method should NOT work on non-rooted phones (but you can still try it :fingers-crossed: ). If it will work, uninstalling the app (via Settings - Applications) would also revoke the granted permissions.
Original Thread here: http://bit.ly/1ov1NNy
Can confirm that the workaround is OK on Samsung S6 with Android 6.0.1 (stock DTM/rooted).
Best regards
Glad I found this, thought BBS was bugged when it kept wanting the BATTERY_STAT permission despite having the XPosed module :\
Executing those 2 lines fixed the problem.... wonder why it's not like that by default. I even checked AppOpsXposed and didn't see anything about DUMP/BATTERY_STAT
Installing BBS into /system would break OTA, no? I've read somewhere the claim that it doesn't--maybe even in the app itself
I'm using official Omni 8.1. The issue I'm facing is that the Magisk Manager can't seem to remember the apps it has granted Superuser permission. Even in the Superuser tab it shows "No apps found". Result being I have to grant Superuser permission every time when I open an app like Root Explorer.
Please look into this issue.
Magisk Manager: v5.5.2
Magisk Root: v15.1 Stable
I don't have this issue on version 5.5.0 and 15.1 on the latest Omni 8.1 weekly on my Oneplus 3T.
Edit: You didn't mention what device, so I doubt anyone would be able to help you. But I guess you're running a Oneplus 3T or a Oneplus 5 since there are no 8.1 Omni weeklies for any other devices, yet. Maybe you could try to attach some logs.
For me Magisk v15.1 doesn't boot anymore, it just fails and goes back to recovery.
v14.6 works fine.
Omni 8.1 on Oneplus 5T
Same problem here. Any solution?
Look into this issue, doesn't boot, solutions?
Where are the logs?
How do you expect someone to help you without that?
For all the praise Magisk seems to get, it sure does have some issues. Lately, it's been kind of a lottery figuring out which version will work with which ROM... These things never happend to me on SuperSu
Jazavchar said:
For all the praise Magisk seems to get, it sure does have some issues. Lately, it's been kind of a lottery figuring out which version will work with which ROM... These things never happend to me on SuperSu
Click to expand...
Click to collapse
I'd say it has to do with the incredible speed that the Magisk development has been going at. Looking back over the past year, a lot has happened. This kind of speed can cause instabilities...
Now, it's most likely at a point where the focus will be on stability and compatibility development.
Having said that, though, all users experiencing issues can help with that by providing as much details as possible and relevant logs.
I can confirm this. It seems Magisk has a problem opening the sqlite3 database, on OmniROM 8.1 at least.
The Superuser request can be granted, and it goes through (as in the app gets its root access), however nothing is permitted "forever".
Superuser log in Magisk Manager is empty, so is the list of apps granted Superuser access.
From my log:
Code:
sqlite3 open failure: unable to open database file
Either the sqlite3 database is located somewhere else, or Magisk didn't get the correct writing rights during the install. Did something change regarding this in 8.1?
There is also a somewhat unrelated issue with Magisk Hide, where the hidelist-file doesn't exist/wasn't initially created upon installation:
Code:
fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
Full log attached.
debichu said:
I can confirm this. It seems Magisk has a problem opening the sqlite3 database, on OmniROM 8.1 at least.
The Superuser request can be granted, and it goes through (as in the app gets its root access), however nothing is permitted "forever".
Superuser log in Magisk Manager is empty, so is the list of apps granted Superuser access.
From my log:
Code:
sqlite3 open failure: unable to open database file
Either the sqlite3 database is located somewhere else, or Magisk didn't get the correct writing rights during the install. Did something change regarding this in 8.1?
There is also a somewhat unrelated issue with Magisk Hide, where the hidelist-file doesn't exist/wasn't initially created upon installation:
Code:
fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
Full log attached.
Click to expand...
Click to collapse
Two things I'm curious about (at the moment):
What are the permissions for /data/adb/magisk.db?
Do you now have a hidelist file in /sbin/.core/img/.core?
Didgeridoohan said:
Two things I'm curious about (at the moment):
What are the permissions for /data/adb/magisk.db?
Do you now have a hidelist file in /sbin/.core/img/.core?
Click to expand...
Click to collapse
There is no such file in that location. There is a magisk.img in that folder with -rw-r--r--, and a magisk/ folder but not containing any magisk.db file either.
Yes, there is now a hidelist file in /sbin/.core/img/.core with -rw-rw-rw-
Bonus info:
I did a complete wipe (I initially did that but I wanted to be certain), and I got this error while installing Magisk right after OmniROM (also see attached):
Code:
! System installed root detected, mount rw :(
Now, OmniROM doesn't ship with root built in - at least not to my knowledge. So I don't know what this "system installed root" Magisk is detecting.
debichu said:
There is no such file in that location. There is a magisk.img in that folder with -rw-r--r--, and a magisk/ folder but not containing any magisk.db file either.
Yes, there is now a hidelist file in /sbin/.core/img/.core with -rw-rw-rw-
Bonus info:
I did a complete wipe (I initially did that but I wanted to be certain), and I got this error while installing Magisk right after OmniROM (also see attached):
Code:
! System installed root detected, mount rw :(
Now, OmniROM doesn't ship with root built in - at least not to my knowledge. So I don't know what this "system installed root" Magisk is detecting.
Click to expand...
Click to collapse
Number 1 is an issue, because that's the su database... If there is none, it's no wonder why granted superuser requests aren't saved.
Hi, do you have a solution?
@Didgeridoohan i am facing same issue like this . it keeps asking for superuser req .
cpt.macp said:
@Didgeridoohan i am facing same issue like this . it keeps asking for superuser req .
Click to expand...
Click to collapse
As far as I know, so far the only known working solution is to reformat /data as ext4. Or stay on an old version of Magisk.
Didgeridoohan said:
As far as I know, so far the only known working solution is to reformat /data as ext4. Or stay on an old version of Magisk.
Click to expand...
Click to collapse
which version you suggest also my /data is ext4 only .
also i would like to tell you one more thing after tinkering little bit and observed following things
as soon as i dont open the magsik app and using root by simple toast and granting the permission it works but as soon as i open the app , it starts misbehaving . i wonder why .
cpt.macp said:
which version you suggest also my /data is ext4 only .
also i would like to tell you one more thing after tinkering little bit and observed following things
as soon as i dont open the magsik app and using root by simple toast and granting the permission it works but as soon as i open the app , it starts misbehaving . i wonder why .
Click to expand...
Click to collapse
Let me guess: you're not using OmniROM...
Since you're posting in this thread, I kind of assumed you did, so my answer was given accordingly.
If you need help, post all possible details and lots of relevant logs.
I've had the same error. Magisk seems unstable on OmniROM 8.1 on OnePlus 5. Probably an issue with the ROM, but the developer seems like the kind of guy who will tell you to go f*ck yourself if you have a problem like this.
Sometimes it works sometimes it doesn't.
A temporary workaround with the permission issue on /data/adb/magisk.db, even after not working trying 0666 permissions, was to change ownership. None of many other solutions worked for me until I found the user for Magisk. You can use a shell as root or with apps like FX File Explorer with root capability to see which user owns files in "/data/adb/magisk/" . Then I applied that user as the owner of magisk.db. Verified that apps which ask for root permission get saved now. The user of Magisk will be different for you since it is marked as "app_##' which I suppose is up to the amount of apps you have installed.
I have a problem and think it caused by the same reason other users here.. My issue is after installing omni rom and gapps ONLY i can't use my banking apps because ( i guess) it thinks my device is rooted.
Device : oneplus 5
I wasn't planning to root my device to keep those kind of issues away
saidmsb said:
I have a problem and think it caused by the same reason other users here.. My issue is after installing omni rom and gapps ONLY i can't use my banking apps because ( i guess) it thinks my device is rooted.
Device : oneplus 5
I wasn't planning to root my device to keep those kind of issues away
Click to expand...
Click to collapse
No... I don't think so. This thread is about an issue with Magisk and f2fs on Android 8.1 ROMs. Your issue could be that OmniROM sets some sensitive props to triggering values.
That can be taken care of by using Magisk and MagiskHide. Take a look here for more info:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Sensitive_props
If you decide to install Magisk, this part of the guide might also be useful (all of it is useful, really):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
I just installed magisk succesfully(?) on my xperia 5 ii following this guide:
https://forum.xda-developers.com/sony-xperia-5-ii/how-to/guide-magisk-twrp-recovery-t4177209/page7
Using the beta channel (stable simply doesn't even boot), magisk manager shows v21 installed. However none of the root apps I tried so far (busybox, adaway, system app remover) works. All of them give some kind of error. The root privileges are being granted (I get the promt to grant/deny and the popup that root was granted). This is very weird and the first time it happens to me on any device. The root browser file managers shows the "root directory" with 0 free space incorrectly (1.6GB used - 1.72 total) I tried copying a file inside the /system directory and it just didn't do anything. I tried reinstalling magisk from the manager, but its still the same. Any help will be appreciated, I really have no idea what to try at this point.
Hard to say... What's "some kind of error"? Maybe the Magisk logs show something (although you'd likely have to switch to the Canary channel to get any useful logs).
I think it's best to wait for a reply to your query in the thread you linked. That's likely to be the best place to get help, since that's where you find other users of the same device...