Related
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!
My phone is rooted and it wont update OTA. How can i permanently ignore this stupid dialog box popping up every 2 minutes on my phone about the upgrade to 4.0.4?
You could try freezing the update process through your task manager/etc. Hope this helps.
Sent from my Amazon Kindle Fire using XDA
Just change your build prop and add the latest version to it. Its a quick 2 second text change. I just don't have the exact text to be copied. Its around here somewhere in one of the threads though.
cleoent said:
My phone is rooted and it wont update OTA. How can i permanently ignore this stupid dialog box popping up every 2 minutes on my phone about the upgrade to 4.0.4?
Click to expand...
Click to collapse
Rooting has no impact on OTA updates' ability to install. You must have something else that is not stock on your device.
As for how to disable it, you need to edit your build.prop file. Change the line that starts with ro.build.fingerprint to whatever it is on an IMM76K ROM. Ask someone who is already running it for the correct text.
Sent from my Galaxy Nexus using Tapatalk 2
is this all you need?
ro.build.fingerprint=google/mysid/toro:4.0.4/IMM76K/336647:user/release-keys
slimb9 said:
is this all you need?
ro.build.fingerprint=google/mysid/toro:4.0.4/IMM76K/336647:user/release-keys
Click to expand...
Click to collapse
Yup, that is what the OP needs. All he has to do is change his ro.build.fingerprint to match that, and he will no longer get the OTA notification.
I dont know anything about build props. Damn.
I also have nothing else done to my phone, just root. I dont think i even have any programs that need root, just did it to do it.
Ballarous said:
You could try freezing the update process through your task manager/etc. Hope this helps.
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
Bingo, freeze the Software update app with some like ROM toolbox.
cleoent said:
I dont know anything about build props. Damn.
I also have nothing else done to my phone, just root. I dont think i even have any programs that need root, just did it to do it.
Click to expand...
Click to collapse
Build.prop is just a text file in the root directory. You can browse to it with root explorer and edit it. Just make a copy of the original and stick it somewhere sexy before doing your edits incase you change something incorrectly.
That way you can come back and ask how to copy a backup to another location when your phone wont boot .
And heres some props for rooting just to root.
Sent from my Galaxy Nexus using Tapatalk 2
cleoent said:
My phone is rooted and it wont update OTA. How can i permanently ignore this stupid dialog box popping up every 2 minutes on my phone about the upgrade to 4.0.4?
Click to expand...
Click to collapse
I encountered the same thing after rooting. I know there are ways to force the message to stop, but it will time out after a few days. I no longer get the pop-up.
Also, even though your phone is rooted, if you click the OTA dialogue box, your phone will attempt to download the OTA update. And this could brick your phone or put you into a boot loop. So be careful not to activate it.
OTA updating a rooted phone shouldn't brick or boot-loop it. Only thing that should happen is that you won't have root after the update.
That is, unless you install OTA Rootkeeper from the app store.
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!
Okay, what the hell?! Every now and again (usually when I'm running Dolphin Browser and/or trying to cut/copy/paste) I get a floating notification at the bottom of the screen that says 'shell has been granted Superuser permissions'! It flashes a few times and then my phone restarts. When it turns back on, I have to restart Juice Defender and SwiftKey (default keyboard ALWAYS comes back, even if I shut down or restart myself!) manually. I went into the Superuser application the other day and there was nothing in there by the name of 'shell.' In fact, the only two things I have granted Superuser permissions to are Titanium Backup and the Android System (is this the culprit, I wonder). Either way, this problem has become a real pain in my ass. It always happens at the most inconvenient times. I would really, REALLY appreciate a solution to this problem.
Also, I have my phone set up just the way I like it, as far as the layout and what not. I've only rooted my phone, I have not replaced the G/UI or OS. If I backup my phone on Kies, wipe it and restore the backup, will it restore the root, Superuser, etc? Or just my apps, data, UI layout and what not? I'm beginning to think that I don't know enough about rooting, or just have horrible luck with it, and need to just run the phone stock. Is there a way to root, delete bloatware and unroot?
Thanks in advance for the help! I appreciate it.
KL
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Seriously? No one knows anything about this? There's another post about the same problem that has also gone unanswered.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
klewis1x said:
Okay, what the hell?! Every now and again (usually when I'm running Dolphin Browser and/or trying to cut/copy/paste) I get a floating notification at the bottom of the screen that says 'shell has been granted Superuser permissions'! It flashes a few times and then my phone restarts. When it turns back on, I have to restart Juice Defender and SwiftKey (default keyboard ALWAYS comes back, even if I shut down or restart myself!) manually. I went into the Superuser application the other day and there was nothing in there by the name of 'shell.' In fact, the only two things I have granted Superuser permissions to are Titanium Backup and the Android System (is this the culprit, I wonder). Either way, this problem has become a real pain in my ass. It always happens at the most inconvenient times. I would really, REALLY appreciate a solution to this problem.
Also, I have my phone set up just the way I like it, as far as the layout and what not. I've only rooted my phone, I have not replaced the G/UI or OS. If I backup my phone on Kies, wipe it and restore the backup, will it restore the root, Superuser, etc? Or just my apps, data, UI layout and what not? I'm beginning to think that I don't know enough about rooting, or just have horrible luck with it, and need to just run the phone stock. Is there a way to root, delete bloatware and unroot?
Thanks in advance for the help! I appreciate it.
KL
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Does it happen every time you copy paste something? Have you tied other browsers to copy paste from?
Something could have happened during rooting. I assume you have a cusom recovery? I might try and flash Chainfire's root method found here http://download.chainfire.eu/324/SuperSU/UPDATE-SuperSU-v1.30.zip It will just overwrite the supersu and the su binaries.
If that doesn't do anything for ya I would Odin back to the stock rooted ROM found here http://forum.xda-developers.com/showthread.php?t=1739426 and start over. Or try one of many great custom ROM that are available.
I don't know what else you could do. If you could get a logcat it would definitely help find out why you are having these issues, and actually solve them. There are plenty of resources on how to obtain a logcat here on xda. Or try an app from the store to save the logcat. PM me with the attachment and I will look at it for you.
I could be totally wrong. BUT I think its samsung doing it. When I denied it permissions it restarted. I did it again and it did the same. I think its intertwined b.c I never had it with AOSP roms