• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Why is shell asking for su?

h4x0rj3ff

h4x0rj3ff

Chemist
Why is My n7 keeps granting shell su permissions??? Then generating a bug file? I'm on night lies from the 17th...
 
i noticed it like a 4 or 5 days ago and it seems to be at night. today was the earliest it happened at about 5pm... it normally happens around 730pm or 8pm. i can upload the bug report that it generates after getting su constantly for like 200 requests ( i think thats the max enteries in superuser) what is generated in the bug report as far as personal info? is it safe to upload? also i have superuser elite if it matters
 
here is the bug report if anyone can help figure out why the shell needs super.

Edit: sorry I was informed that the bug report has sensitive information and I decided to pull it. Pm me if you have relevant information that would constitute you obtaining my bug report.
 
ok finally got the link situated around and it is working. for some reason google drive was giving me a 404 error... o well its on dropbox now
 
Go into your Superuser app and look for apps that might be using a shell - any scripting apps, for instance. If you can't identify it, revoke permissions for all of the apps that currently have superuser privileges.

The app should request permission next time it needs su. I remember having this problem on my phone once but I can't remember what was causing it.
 
Anyone figure out anything about this? I went in and cleared cache and data for superuser and it was good for a few days and tonight shell was granted su again.... never prompted me or anything. Then it generated a new bug report. Any ideas? Its starting to worry me a bit...
 
matysuty.jpg


I can give you this screen shot and the next time it happens (if it does which it probally will) I will try to get a screen shot.
 
This is what I managed to get. Also I want in while it was asking and granting to auto response to deny.
 

Attachments

  • uploadfromtaptalk1353448243294.jpg
    uploadfromtaptalk1353448243294.jpg
    58.2 KB · Views: 97
  • uploadfromtaptalk1353448254502.jpg
    uploadfromtaptalk1353448254502.jpg
    61.1 KB · Views: 93
  • uploadfromtaptalk1353448265533.jpg
    uploadfromtaptalk1353448265533.jpg
    50.7 KB · Views: 107
  • uploadfromtaptalk1353448275271.jpg
    uploadfromtaptalk1353448275271.jpg
    54.3 KB · Views: 93
I had a problem of it randomly popping up asking me how to complete it and finding random screen shots saved. Never figured out what it was, but it's been a while. It was generating bug reports for something.

Why don't you deny access to shell and see what happens?
 
carracerz14 said:
I had a problem of it randomly popping up asking me how to complete it and finding random screen shots saved. Never figured out what it was, but it's been a while. It was generating bug reports for something.

Why don't you deny access to shell and see what happens?
Click to expand...


Its not in the list. I cleared cache and app data and set auto response to deny and it still was granted su permissions
 
1. Your kernel log (dmesg) shows a lot of cpu_up and cpu_down events (this might actually be absolutely normal and is just the system turning off the processors as a matter of course)

2. The "LIST OF OPEN FILES" section (starting at line 9645) shows a ton of /system/xbin/su references (215 of them :eek:)

3. There are a few "ActivityManager: No longer want com.noshufou.android.su (pid 17900): hidden #16" references of the su package listed in the logcat output

4. Lots of references of "su : Executing exec /system/bin/am broadcast -a com.noshufou.android.su.RESULT --es socket '' --ei caller_uid 2000 --ei allow 1 --ei version_code 18" which I'm guessing is su talking with the Superuser app...

5. Line #12940 in the logcat is the start of a very interesting sequence of the su package:

"su : Executing exec /system/bin/am broadcast -a com.noshufou.android.su.RESULT --es socket '' --ei caller_uid 2000 --ei allow 1 --ei version_code 18"

by line #12971, it looks like the su request loop you were seeing has started (there's a sequence that repeats over and over again).

6. Finally see this at line #17741:

"am_kill : [1003,com.noshufou.android.su,12,too many background]"

"am_proc_died: [1003,com.noshufou.android.su]"

7. Line #17876 starts a series of am_create_service and am_destroy_service instances for the su package and is the last things recorded in the logcat

Not really sure what's going on here, but I'd examine your various root apps, especially those you invoked just before the looping issues and which might process things repetitively (especially in the background).

That's all I got.

Cheers!
 
scary alien said:
1. Your kernel log (dmesg) shows a lot of cpu_up and cpu_down events (this might actually be absolutely normal and is just the system turning off the processors as a matter of course)

2. The "LIST OF OPEN FILES" section (starting at line 9645) shows a ton of /system/xbin/su references (215 of them :eek:)

3. There are a few "ActivityManager: No longer want com.noshufou.android.su (pid 17900): hidden #16" references of the su package listed in the logcat output

4. Lots of references of "su : Executing exec /system/bin/am broadcast -a com.noshufou.android.su.RESULT --es socket '' --ei caller_uid 2000 --ei allow 1 --ei version_code 18" which I'm guessing is su talking with the Superuser app...

5. Line #12940 in the logcat is the start of a very interesting sequence of the su package:

"su : Executing exec /system/bin/am broadcast -a com.noshufou.android.su.RESULT --es socket '' --ei caller_uid 2000 --ei allow 1 --ei version_code 18"

by line #12971, it looks like the su request loop you were seeing has started (there's a sequence that repeats over and over again).

6. Finally see this at line #17741:

"am_kill : [1003,com.noshufou.android.su,12,too many background]"

"am_proc_died: [1003,com.noshufou.android.su]"

7. Line #17876 starts a series of am_create_service and am_destroy_service instances for the su package and is the last things recorded in the logcat

Not really sure what's going on here, but I'd examine your various root apps, especially those you invoked just before the looping issues and which might process things repetitively (especially in the background).

That's all I got.

Cheers!
Click to expand...


It just don't make sense because for 1 it has happened when I had absolutely NO root apps installed and 2 it has happened when I set auto response under settings > security to 'deny'....

From that it looks like it could be es file explorer? Also is it a possibility it can be cyanogenmod updates? I'm on night lies and it checks for updates twice a day... that's the only two things I can think it could be
 
h4x0rj3ff said:
It just don't make sense because for 1 it has happened when I had absolutely NO root apps installed and 2 it has happened when I set auto response under settings > security to 'deny'....

From that it looks like it could be es file explorer? Also is it a possibility it can be cyanogenmod updates? I'm on night lies and it checks for updates twice a day... that's the only two things I can think it could be
Click to expand...

Well, I know ES File Explorer does indeed have a root mode (that's why I used it for so long without needing or wanting to acquire a paid version of Root Explorer (which I have now)).

The update thing is interesting, but I'm not sure that would necessarily require root...(been a long while since I've played with or researched a CM ROM ;)).
 
scary alien said:
Well, I know ES File Explorer does indeed have a root mode (that's why I used it for so long without needing or wanting to acquire a paid version of Root Explorer (which I have now)).

The update thing is interesting, but I'm not sure that would necessarily require root...(been a long while since I've played with or researched a CM ROM ;)).
Click to expand...


Thats why I suggested es... and the cm update downloads the update then it reboots into recovery to flash the update so it could be that too but then there should be somewhere in there pointing to settings or a cm update app of some sorts...
 
OK so I was finally able yo duplicate it. The link you sent me helped quite a bit actually... its when you press all three side buttons(pwr, vol + -) not sure why but I atleast know half of what's going on. Can someone else try to get the n7 to do this? Press and hold all three buttons like your taking a screenshot but with all the buttons... then it could take up to a minute but you'll here a sound and then get the bunch of toast messages about su.
 
You must log in or register to reply here.
Back
Top Bottom