[BETA][2017.10.01] SuperSU v2.82 SR5

tetakpatak · Sep 10, 2014

@Chainfire SuperSU v2.06 works very fine with Android L test version on my Nexus 7 flo.

The only root apps that aren't working are Quick Boot and Titanium Backup. Quick Boot gets granted permission for an interactive shell, but nothing happens. TB can't recognize root access (it prompts in SuperSU window and I confirmed).

Would some logs be useful? I think my BusyBox might be the problem, it isn't working.

tetakpatalked from Nexus 7 flo / Android "L" test version

dhampire · Sep 10, 2014

2nd Report

Hi.

I'm sorry for sending last miss-match log.

This time I did as..

adb logcat > logcat.txt

Regards.

Chainfire · Sep 10, 2014

dhampire said:
Hi.

I'm sorry for sending last miss-match log.

This time I did as..

adb logcat > logcat.txt

Regards.

Slowly but surely zoning in on the issue.

- Install attached version
- Update binaries
- Reboot
- Open SuperSU
- Create a new logcat: adb logcat > logcat.txt
- Before posting, make sure it contains a line saying "[SuperSU][APK][Installer] su --> 207"
- Post the output of (copy/paste): adb shell su --context u:r:system_app:s0 -c id

dhampire · Sep 10, 2014

Hi.

Q:
Post the output of (copy/paste): adb shell su --context u:r:system_app:s0 -c id

What kind of file(where) ? Please inform me.

dhampire · Sep 10, 2014

Hi.

I did as your order.

1) Install attached version
2) Update binaries
3) Reboot
4) Open SuperSU
5) Create a new logcat: adb logcat > logcat.txt

- Before posting, make sure it contains a line saying "[SuperSU][APK][Installer] su --> 207"

=> Sure. I checked it in logcat.txt.

Cheers.

Chainfire · Sep 10, 2014

dhampire said:
Hi.

Q:
Post the output of (copy/paste): adb shell su --context u:r:system_app:s0 -c id

What kind of file(where) ? Please inform me.

Actually the output should be something like this:

Code:

C:\>adb shell su --context u:r:system_app:s0 -c id
uid=0(root) gid=0(root) context=u:r:system_app:s0

C:\>

Please try again.

Once that works, try this and see what the output is:

Code:

adb shell su --self-test

And the output of:

Code:

adb shell ls -lZ /system/xbin

dhampire · Sep 10, 2014

Hi.

1:

Code:

C:\>adb shell su --context u:r:system_app:s0 -c id
uid=0(root) gid=0(root) context=u:r:system_app:s0

=> see 01.jpg

2:[code]
adb shell su --self-test

=> see 02.jpg

3:[code]
adb shell ls -lZ /system/xbin

=> too big... can't catch all.

Chainfire · Sep 10, 2014

dhampire said:
....

That is very interesting. How exactly did you initially gain root on this device? Do you flash full ZIPs through recovery? Or do you use some program like towelroot to get root?

dhampire · Sep 10, 2014

use vRoot (because of no other tool - inclusive towelroot / kingoroot / Framaroot etc.,- can root my device, I try a lot), and flash supersu 1.9.4, then delete vRoot.

Chainfire · Sep 10, 2014

dhampire said:
use vRoot (because of no other tool - inclusive towelroot / kingoroot - can root my device, I try a lot), and flash supersu 1.9.4, then delete vRoot.

Try the attached verion. Would like the logcat and output of --self-test again!

r25txe · Sep 11, 2014

tetakpatak said:
@Chainfire SuperSU v2.06 works very fine with Android L test version on my Nexus 7 flo.

The only root apps that aren't working are Quick Boot and Titanium Backup. Quick Boot gets granted permission for an interactive shell, but nothing happens. TB can't recognize root access (it prompts in SuperSU window and I confirmed).

Would some logs be useful? I think my BusyBox might be the problem, it isn't working.

tetakpatalked from Nexus 7 flo / Android "L" test version

I believe that Titanium is not yet Android L compatible.

How do you install Busybox? Try using Busybox X (Play Store) after uninstalling all traces of Busybox first.

dhampire · Sep 11, 2014

WoW !

Hi, Big Thanks for your strong support!

WoW ! Now no notification "need su binary update" in nortification area.

I attached Logcat3 & self test here.

Regards.

dhampire · Sep 11, 2014

Success !

Hi.

I got success to move SuperSU 2.0.8 to system folder by normal way without problem.

I feel that the stable means happy.

Anyway, Thank you so much for your strongest support!

jurben · Sep 11, 2014

@Chainfire : i waited for days hoping that someone else with the same case as mine would post here, but it seems noone posted yet.

My device is msm8610 based and previously it's system is JB 4.3. I got ota update to kk 4.4.2 then I install it, but first i changed the updater-script to not delete my PhilZ-CWM. My KK runs well, but i cannot get root access for my apps. With cwm and also with towelroot or other rooting tools I can put su binary and other root 'components' (daemonsu, changing install-recovery.sh, etc) but su command takes forever to finish.

(this outputs is after 'rooted' by towelroot, but i got similar output after installing update-supersu whatever version i used):

'su -v' gave output
1.99:SUPERSU

but
'su' and 'su --context u:r:system_app:s0 -c id' and 'su --self-test'
(stuck / takes forever to finish)

if i use / install update-supersu version 2.02 or higher beta version, 'su --self-test' outputs some lines before stuck:
version_code: 202
version_name: 2.02:SUPERSU
sdk: 19
daemon_sdk: 1
multiuser_sdk: 1
multiuser_userid: 0
multiuser_username: (null)
selinux_present: 1
selinux_enforcing: 1
context[base]: (stuck here)

Some output of 'ls -lZ /system/xbin'

-rwxr-xr-x root root u

bject_r:system_file:s0 daemonsu
-rwxr-xr-x root root u

bject_r:system_file:s0 su

I don't know whether this info is relevant or not: These lines exist in kernel's log:

Code:

<5>[  187.801792] (09-11 11:36:02.538477353) type=1400 audit(1410406562.527:31): avc:  denied  { search } for  pid=6242 comm="ainfire.supersu" name="/" dev="selinuxfs" ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir
<5>[  187.802063] (09-11 11:36:02.538747925) type=1400 audit(1410406562.527:32): avc:  denied  { read } for  pid=6242 comm="ainfire.supersu" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file
<5>[  187.802796] (09-11 11:36:02.539480946) type=1400 audit(1410406562.527:33): avc:  denied  { open } for  pid=6242 comm="ainfire.supersu" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file
<5>[  187.803050] (09-11 11:36:02.539734644) type=1400 audit(1410406562.527:34): avc:  denied  { getattr } for  pid=6242 comm="ainfire.supersu" path="/sys/fs/selinux/enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file
<5>[  193.536107] (09-11 11:36:08.272792195) type=1400 audit(1410406568.267:35): avc:  denied  { read } for  pid=6372 comm="su" name="/" dev="selinuxfs" ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir

Chainfire · Sep 11, 2014

dhampire said:
Hi.

I got success to move SuperSU 2.0.8 to system folder by normal way without problem.

I feel that the stable means happy.

Anyway, Thank you so much for your strongest support!

Thank you as well for testing and getting back logs. You're probably not the only person who had this problem, but without you, it would not have been solved today.

jurben said:
@Chainfire : i waited for days hoping that someone else with the same case as mine would post here, but it seems noone posted yet.

My device is msm8610 based and previously it's system is JB 4.3. I got ota update to kk 4.4.2 then I install it, but first i changed the updater-script to not delete my PhilZ-CWM. My KK runs well, but i cannot get root access for my apps. With cwm and also with towelroot or other rooting tools I can put su binary and other root 'components' (daemonsu, changing install-recovery.sh, etc) but su command takes forever to finish.

(this outputs is after 'rooted' by towelroot, but i got similar output after installing update-supersu whatever version i used):

'su -v' gave output
1.99:SUPERSU

but
'su' and 'su --context u:r:system_app:s0 -c id' and 'su --self-test'
(stuck / takes forever to finish)

if i use / install update-supersu version 2.02 or higher beta version, 'su --self-test' outputs some lines before stuck:
version_code: 202
version_name: 2.02:SUPERSU
sdk: 19
daemon_sdk: 1
multiuser_sdk: 1
multiuser_userid: 0
multiuser_username: (null)
selinux_present: 1
selinux_enforcing: 1
context[base]: (stuck here)

Some output of 'ls -lZ /system/xbin'

-rwxr-xr-x root root ubject_r:system_file:s0 daemonsu
-rwxr-xr-x root root ubject_r:system_file:s0 su

I don't know whether this info is relevant or not: These lines exist in kernel's log:

Code:

<5>[ 187.801792] (09-11 11:36:02.538477353) type=1400 audit(1410406562.527:31): avc: denied { search } for pid=6242 comm="ainfire.supersu" name="/" dev="selinuxfs" ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir <5>[ 187.802063] (09-11 11:36:02.538747925) type=1400 audit(1410406562.527:32): avc: denied { read } for pid=6242 comm="ainfire.supersu" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file <5>[ 187.802796] (09-11 11:36:02.539480946) type=1400 audit(1410406562.527:33): avc: denied { open } for pid=6242 comm="ainfire.supersu" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file <5>[ 187.803050] (09-11 11:36:02.539734644) type=1400 audit(1410406562.527:34): avc: denied { getattr } for pid=6242 comm="ainfire.supersu" path="/sys/fs/selinux/enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file <5>[ 193.536107] (09-11 11:36:08.272792195) type=1400 audit(1410406568.267:35): avc: denied { read } for pid=6372 comm="su" name="/" dev="selinuxfs" ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir

Is there no /system/xbin/sugote and /system/xbin/sugote-mksh ?

Those avc lines do not seem to be problematic (SuperSU always generates a number of these)

jurben · Sep 11, 2014

Thanks for your respon.

Chainfire said:
Is there no /system/xbin/sugote and /system/xbin/sugote-mksh ?

They are there.

Some fellow thought there may be scripts or app that blocks/prevent su from getting root so the problem is not from su binary or SuperSU. What do you think?

Chainfire · Sep 11, 2014

jurben said:
Thanks for your respon.

They are there.

Some fellow thought there may be scripts or app that blocks/prevent su from getting root so the problem is not from su binary or SuperSU. What do you think?

I think I don't have enough information to make any assumptions about this. Plainly speaking: absolutely on idea what is going on here, and no idea how to start debugging. Can you give me more specifics about the device ?

jurben · Sep 11, 2014

Chainfire said:
I think I don't have enough information to make any assumptions about this. Plainly speaking: absolutely on idea what is going on here, and no idea how to start debugging. Can you give me more specifics about the device ?

Don't be too bothered. It's ok for me without root access. I just curious.

My device is hisense AD689G / EG668 bundled (locked) with local operator Smartfren.

dacorsa · Sep 11, 2014

Thanks for all !

Inviato dal mio SM-G900F X-Note 5.0 con Tapatalk

Chainfire · Sep 12, 2014

v2.08 beta out now

[BETA][2017.10.01] SuperSU v2.82 SR5

Senior Member

Senior Member

Attachments

Moderator Emeritus / Senior Recognized Developer

Attachments

Senior Member

Attachments

Senior Member

Attachments

Moderator Emeritus / Senior Recognized Developer

Senior Member

Attachments

Moderator Emeritus / Senior Recognized Developer

Senior Member

Moderator Emeritus / Senior Recognized Developer

Attachments

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Moderator Emeritus / Senior Recognized Developer

Senior Member

Moderator Emeritus / Senior Recognized Developer

Senior Member

Senior Member

Moderator Emeritus / Senior Recognized Developer

Similar threads

Top Liked Posts