Hi all,
These days my phone, running stock JRO83D updated from jb-takju.zip provided by ClockworkMod, sometimes vibrate, and "shell has been granted superuser permission" floats several times, and then it let me choose Dropbox or Gmail.
The dump file is here: https://hexchain.org/pub/bugreport-2012-07-13-14-15-39.txt (Too big to attach here )
I didn't see anything wrong with my phone, it functions smoothly and nothing is wrong.
Chainsdd also ran into the shell being granted root multiple fines as well. (He's the one working on the su binary and superuser app). I don't know if there's a fix yet, but he's working on it when he can.
I've also had this issue, and I just rebooted my phone and haven't seen it since.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
Chainsdd also ran into the shell being granted root multiple fines as well. (He's the one working on the su binary and superuser app). I don't know if there's a fix yet, but he's working on it when he can.
I've also had this issue, and I just rebooted my phone and haven't seen it since.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you!
Related
Like I said I'm a noob.But I've rotted several phones with Z4,but i tried Rooting a Evo 4g with O.T.A 2.2 update using Unrevoked. Everything went ok until I tried using anything that needed Superuser Permissions. Superuser would pop up every time i pressed Allow.I'm trying to Flash to CM7,but can't get passed SU problem. Has any one came across this problem and solved it. Any help would be Greatly Appreciated..
512heroATX said:
Like I said I'm a noob.But I've rotted several phones with Z4,but i tried Rooting a Evo 4g with O.T.A 2.2 update using Unrevoked. Everything went ok until I tried using anything that needed Superuser Permissions. Superuser would pop up every time i pressed Allow.I'm trying to Flash to CM7,but can't get passed SU problem. Has any one came across this problem and solved it. Any help would be Greatly Appreciated..
Click to expand...
Click to collapse
No I haven't had that issue, and I'm kind of confused about what you are saying.
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
try that.
What Im trying to say is. When trying to backup with Titanium Backup or use Rom Manager SU keeps popping up with no progress in the App. Say for instense i want to use WirelessTether it would say asking for Root rights, SU would pop up and ask Allow or Deny. I'll press Allow then SU would pop up again and again. Every time i pressed Allow.
512heroATX said:
What Im trying to say is. When trying to backup with Titanium Backup or use Rom Manager SU keeps popping up with no progress in the App. Say for instense i want to use WirelessTether it would say asking for Root rights, SU would pop up and ask Allow or Deny. I'll press Allow then SU would pop up again and again. Every time i pressed Allow.
Click to expand...
Click to collapse
Try installing superuser with the link I sent you or search super user in the market.
That seem to do the trick. Thanks for the help
My Verizon GNex is rooted, I have CWM, superuser etc, even installed this rom, but I keep losing root after an hour or so. I use root explorer, open a terminal, su, do things, do it again in a few minutes and it suddenly won't log in as root.
When this happens, my wifi also craps out. It shows signal strength too low to connect when I'm standing next to the router. Reflashing CWM or superuser does nothing. Last night I wiped and went back to stock and it worked for a while, but I've found I can also flash that rom and it will work for a while and that is easier. Root survives multiple reboots but just stops working for no reason after a while.
Example: I flashed that rom this morning and rebooted 2-3 times, went to the mall and kept opening root explorer to see if root was working. I sat and watched my daughter play at the mall for nearly an hour. When she wanted something to drink, I checked and root was still working. I went to the store nearby, got a water, sat back down and no longer had root.
I'm not getting any OTA notification or anything, it just stops being rooted out of the blue.
Any ideas?
Darn, halfway down page two already and no replies...
same issue here
I'm glad I'm not the only one. How did you root?
followed this until step 5 http://forum.xda-developers.com/showthread.php?t=1392310
Me too. I used a different guide, but it looks like it was exactly same.
Do you use root explorer? I was only using it to check if I had root yesterday -it opens when rooted, doesn't when root is lost- and after losing root I noticed its battery usage was nearly as high as the displays although I had only opened it for 2 seconds several times.
Last night I rerouted before bed and didn't touch root explorer and im still rooted ten hours later. May not be related, and I could lose root at and time, but I was losing it every hour or two, so I'm starting to get optimistic that root explorer may have had something to do with it.
Sent from my Galaxy Nexus using Tapatalk
fubaya said:
Do you use root explorer? I was only using it to check if I had root yesterday -it opens when rooted, doesn't when root is lost- and after losing root I noticed its battery usage was nearly as high as the displays although I had only opened it for 2 seconds several times.
Last night I rerouted before bed and didn't touch root explorer and im still rooted ten hours later. May not be related, and I could lose root at and time, but I was losing it every hour or two, so I'm starting to get optimistic that root explorer may have had something to do with it.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Haven't seen this specific issue much with the Galaxy Nexus yet. I had this problem 1.5 yrs ago with an older Samsung Android device though. Solution was a bit complex, but haven't seen this issue in a long while.
I know root can be a bit hidden from Android unless adb is connect or using a terminal application. For this reason, m root check application is generally a good program to run a simple diagnostic of the root configuration on the device.
The Pro version, 99 cents in the Market and free on XDA has a widget which will update at the interval you pick, 1-24 hrs with the root status and gives a more thoroughly diagnostic output of the system su binaries and their properties.
Hope that helps!
Try putting the su binary in /system/xbin. I lost root after the OTA update to ITL41F, but busybox in /system/xbin survived.
I have root checker and when I lose root, it still says everything is OK. Superuser logs also show that apps have been allowed, but the apps just don't get root. When it happens, everything loses root, terminals root explorer, titanium backup etc. even the superuser app can't update the su binary.
I still have root after 11+ hours (crossing fingers)
Sent from my Galaxy Nexus using Tapatalk
motopig said:
Try putting the su binary in /system/xbin. I lost root after the OTA update to ITL41F, but busybox in /system/xbin survived.
Click to expand...
Click to collapse
The su binary will have also remained after an OTA, same as busybox. The difference is their permissions. Every OTA re-sets the binary direction permissions as 755 stripping out the setuid attribute required by su, but not required by busybox.
This would explain why after using an OTA the user will lose "root" access but maintain busybox access. Both binaries persist, but the su binary loses the setuid attribute required to elevate access for root.
fubaya said:
I have root checker and when I lose root, it still says everything is OK. Superuser logs also show that apps have been allowed, but the apps just don't get root. When it happens, everything loses root, terminals root explorer, titanium backup etc. even the superuser app can't update the su binary.
I still have root after 11+ hours (crossing fingers)
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Well the key here, as I stated above, would be to see whether or not the su binary still has the setuid attribute and UID/GID set as root.
Any of those changes could remove the ability of the su binary to esclate permissions as root. In theory, any application which has been granted root access through Superuser, could remove root access for the whole system.
I can't imagine any reason why a developer would intentionally write an application to do that under a different title which you would be using.
Hope the technical details help!
I never had an OTA update after rooting, at least there were no notifications or anything. I do agree it acted as if the binary permissions got screwed up somehow, I don't know why I didn't check. Reflashing the su.zip didn't help. I assume flashing would set the permissions.
Well, nearly 24 hours and I still have root so, whatever it was, I'm happy now.
I just realized i no longer have root and i did the ota update recently. Problem is i cant get root back no matter what i try. I reinstalled the latest superuser from market with no luck. Any advice?
I forgot to mention i am completly stock on 4.0.1 and ITL41F. All i did with this phone is unlock the bootloader and the guide i used i think pdanet put SU apk automatically installed. My apps like root explorer all showed they did have root access. But now i tried to use root explorer and it claimed it had access, but couldnt get root.
My SU apk was updated to latest from the market. I just uninstalled the update and still no luck. Reinstall update and still no luck..
When it happened to me, the only thing that worked was to reflash the rom and go through the rooting process again. There is a thread in the development section about going back to stock where you can find the stock rom. you'll lose apps and things and may want to back them up first.
You could probably flash a new rom instead. I don't remember which one it was, but I was using a 4.0 rom that had su and didn't require wiping anything so reflashing was painless.
Sent from my Galaxy Nexus
Crap ok thanks. I cant backup anything with titanium cause it cant get root, so i guess i jyst have to lose everything. Might as well go with one of the roms i guess. I kinda was just enjoying stock with root.
Oh the other problem i have is i'm getting a fastboot error. Boot into bootloader and at the bottom of the screen says "fastboot FAILstatus" below. Any idea what thats about?
Some apps can export their settings the sdcard so don't forget to check them. I know when I lose everything there's really only 4-5 apps that require much setup while the others just require a login, but luckily those 4-5 apps can export their settings.
I don't know about the error, I'm not very good with fastboot. I use it when I get a new phone then go a couple of years without using it.
i finally got rooted again. For some reason it just wouldnt take. I had to use superboot over and over and over again and then finally it just took successfully even though i didnt anything differently. Very strange.
I'm sure the answer is no but when I brought my Nexus home and began playing with it I noticed that Superuser had already been installed on the device. At first I thought it was because I had it installed on my previous phone and it just got restored with all the rest of my apps. When I checked its install location however, I noticed it was installed in /system/app/. I don't think this is possible without root.
The conclusion that I have come to is that Verizon sold me a phone that someone had rooted and returned. Any different theories??
Refot_Sirk said:
I'm sure the answer is no but when I brought my Nexus home and began playing with it I noticed that Superuser had already been installed on the device. At first I thought it was because I had it installed on my previous phone and it just got restored with all the rest of my apps. When I checked its install location however, I noticed it was installed in /system/app/. I don't think this is possible without root.
The conclusion that I have come to is that Verizon sold me a phone that someone had rooted and returned. Any different theories??
Click to expand...
Click to collapse
SU is an app, so it might have been restored. Are you rooted?
One thing is sure though, superuser does not come pre installed.
Sent from my Galaxy Nexus using Tapatalk
Herman76 said:
SU is an app, so it might have been restored. Are you rooted?
One thing is sure though, superuser does not come pre installed.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Rooted now, yes. But I noticed that it was installed in /system/app/ before I rooted it. Also I know that the su binary wasn't present either because when I opened Root Explorer I was never prompted to allow root privileges.
As soon as the Galaxy Nexus knows your Google account, it starts loading all the apps you used on a previous Android phone. So, if you had SU installed before, you'll have SU on your Galaxy Nexus now, even if your Nexus is unrooted.
Sweerts said:
As soon as the Galaxy Nexus knows your Google account, it starts loading all the apps you used on a previous Android phone. So, if you had SU installed before, you'll have SU on your Galaxy Nexus now, even if your Nexus is unrooted.
Click to expand...
Click to collapse
I thought this too but as far as I know apps cannot be installed to /system/app without root. I had not yet rooted it when it was being restored.
That seems simple to me: market has superuser permissions.
Sweerts said:
As soon as the Galaxy Nexus knows your Google account, it starts loading all the apps you used on a previous Android phone. So, if you had SU installed before, you'll have SU on your Galaxy Nexus now, even if your Nexus is unrooted.
Click to expand...
Click to collapse
This is not true. If you install SU through rooting, it will NOT install the SU from the market. The OP had SU installed in /system which is NOT possible for a market app to do if it is just being restored. If you root a phone and install the non-market SU, then logging into another phone will not restore the SU app since it is not from the market.
Refot_Sirk said:
The conclusion that I have come to is that Verizon sold me a phone that someone had rooted and returned. Any different theories??
Click to expand...
Click to collapse
That would be my theory, also...
Post deleted.
Post deleted.
Refot_Sirk said:
I'm sure the answer is no but when I brought my Nexus home and began playing with it I noticed that Superuser had already been installed on the device. At first I thought it was because I had it installed on my previous phone and it just got restored with all the rest of my apps. When I checked its install location however, I noticed it was installed in /system/app/. I don't think this is possible without root.
The conclusion that I have come to is that Verizon sold me a phone that someone had rooted and returned. Any different theories??
Click to expand...
Click to collapse
I'd be going with your theory, take it back and demand a new unit
Sent from my Galaxy Nexus using xda premium
One of my friends also got this phone from Vodafone and the box was opened and the security tag was broken. He asked me to root it so I went through the motions only to discover that the bootloader was already unlocked. He doesn't know much about Android so i don't expect him to be lying about the bootloader being unlocked. He also mentioned that the unlocked lock came up the first time he turned it on. Odd isn't it?
Not to mention that he pre ordered it here in australia and got one from the first batch. Mine was perfect and sealed..?
Sent from my Galaxy Nexus using XDA App
Refot_Sirk said:
I'm sure the answer is no but when I brought my Nexus home and began playing with it I noticed that Superuser had already been installed on the device. At first I thought it was because I had it installed on my previous phone and it just got restored with all the rest of my apps. When I checked its install location however, I noticed it was installed in /system/app/. I don't think this is possible without root.
The conclusion that I have come to is that Verizon sold me a phone that someone had rooted and returned. Any different theories??
Click to expand...
Click to collapse
What did you use to view files in/system if you weren't rooted?
Sent from my Galaxy Nexus using XDA App
artvandelay440 said:
What did you use to view files in/system if you weren't rooted?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Siri.
artvandelay440 said:
What did you use to view files in/system if you weren't rooted?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Obviously he was rooted if SU was installed..
Two points:
1 - /system is visible, but not writable without root (/data is writable, but not visible)
2 - he had SuperUser installed, which is a type of firewall, not root. Su, the binary is root, and SuperUser is not...
The fact that SuperUser the app was installed in /system indicates that the phone was rooted at some point and may still be... For me, that's scary!
I used this guide - http://forum.xda-developers.com/showthread.php?t=1399872 and it seemed to work, because I'm S-off now. But it did not root me at all, because I don't have superuser access. So now what do I do?
I have a Wildfire S through Metro PCS, and it doesn't seem like any one click method works for some reason. :-\
Try installing busybox and superuser from the market
When I install busybox, it says "The su binary was not found on your phone. This application will not work without root."
It's just weird, it made my phone S-off with the one click method, but didn't root it for some reason. It's causing more headaches than triumphs.
Resendetra said:
When I install busybox, it says "The su binary was not found on your phone. This application will not work without root."
It's just weird, it made my phone S-off with the one click method, but didn't root it for some reason. It's causing more headaches than triumphs.
Click to expand...
Click to collapse
Just flash this in clockworkmod recovery and you will have root.
http://fs05n5.sendspace.com/dl/a83155f4163080858a07a7f72736c2fc/4f56054b28b6e784/2l50jw/root.zip
Thanks to MrTaco I am finally rooted and it feels great. Hah! I clicked thanks also. After almost 12 hours and a bunch of coffee, I feel completed.
Although, superuser wants to keep force closing on me, but I don't care right now.
Resendetra said:
Thanks to MrTaco I am finally rooted and it feels great. Hah! I clicked thanks also. After almost 12 hours and a bunch of coffee, I feel completed.
Although, superuser wants to keep force closing on me, but I don't care right now.
Click to expand...
Click to collapse
Your welcome and you should update superuser to the latest version and if it proceeds just fix permissions using ROM Manager.
I was just using the browser on my e4gt running the leaked fk23 rooted rom, and I got a pop-up that said "shell has been granted superuser permissions". it kept popping back up about 15 times in rapid succession and I was never prompted to allow or deny it. I got scared and turned off wifi and went to airplane mode, but my phone seems fine now. im clueless, so can someone clear this up for me? im using chainfires superuser, not supersu, and there is no app on my phone called shell
shall is the system. Look in the su app at the log and see what's been asking. Also get the exynos abuse apk by chainfire
sent from MY BAD A$$ ET4G
oops. wrong thread. my b.
I saw in another thread that I didn't notice to switch to super su, and I haven't gotten It since. I figured something or someone was trying to open a shell. all it said in the log was shell permission granted or whatnot.
Shell is the VM android runs in ontop of the linux kernel. Anytime you want to know what gaining root access check the log in su or supersu app it will show all allowed and blocked root access attempts
Sent from my SPH-L900 using Xparent ICS Tapatalk 2