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.
Related
I attempted to root my phone using 1-click root app and it looked like everything went well. I was able to tether, titanium backup could access what it needed to, etc. As I continued to try new apps I started to see an error message more and more "<app name> as been denied super user permissions". At first I thought nothing of it but now Im starting to question it my phone is fully rooted.
I down loaded Root check basic which tells me that my SPH-710 is not rooted as I once thought. Now Im not sure what I should do?
It should be noted that when I go into recovery mode sometimes I have issues when attempting to boot. (I know this isnt much to go on but I havent exactly documented whats happening and Im paranoid to try it right now).
So here I am looking to you phone gurus for advice. I should have the correct drivers and development kit installed, but again this isnt something I do on a daily basis and would rather not go into this blind and brick my phone. The last phone I rooted was my EVO 4G and once I got that configured where I wanted it I never touched it again.
Anway.. any links, apps, sites, etc, that you could provide would be appreciated.
Thank you.
The easiest way is to flash a rooted kernel in odin, download a ROM and install it through the recovery if you want to after that.
ryedunn said:
I attempted to root my phone using 1-click root app and it looked like everything went well. I was able to tether, titanium backup could access what it needed to, etc. As I continued to try new apps I started to see an error message more and more "<app name> as been denied super user permissions". At first I thought nothing of it but now Im starting to question it my phone is fully rooted.
Click to expand...
Click to collapse
If you were able to run Titanium you were rooted. You probably got an OTA update recently which disables your root. Just re-run the rooting package and you'll have it back.
Re-root Post OTA
+1, got the update a couple nights ago and also lost root even though I still had the Superuser app and could run the allowed programs there as root.
I used sfhub's method to root again and it was a snap:
http://forum.xda-developers.com/showthread.php?t=1342728
Bonus is s/he now supports a way to turn off CIQ!
I rooted my AT&T i747 with Android 4.0.4 a couple months ago and installed SuperSU as well and was working great. When I upgraded my phone to android 4.1.1 a few days ago I lost all rooting capabilities. My Titanium Backup Pro no longer has root access as well as my SuperSU and a couple of other apps that require it. I also have tried uninstalling SuperSU with no success.
Could I just reflash my i747 just like I did back on 4.0.4 to root it again or is there a way to correct the current root access? What would you recommend?
Thanks in advance!
If you took the official update then you have lost root. You just need to re root and you will be back in business.
Sent from my SGH-I747M using xda app-developers app
jbradbury said:
If you took the official update then you have lost root. You just need to re root and you will be back in business.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
I want to do it but this is what the app says on Google play...
"NOTICE: A SPECIAL PROCEDURE IS NEEDED FOR UNINSTALLATION. IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.
Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser solution you want. (3) Uninstall SuperSU."
Does that mean I will lose root for good if I just try to reroot it a second time without first uninstalling it? That is where I am having trouble as well. The app will not let me properly uninstall it from within the app.
Thanks.
SCADAman said:
I want to do it but this is what the app says on Google play...
"NOTICE: A SPECIAL PROCEDURE IS NEEDED FOR UNINSTALLATION. IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.
Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser solution you want. (3) Uninstall SuperSU."
Does that mean I will lose root for good if I just try to reroot it a second time without first uninstalling it? That is where I am having trouble as well. The app will not let me properly uninstall it from within the app.
Thanks.
Click to expand...
Click to collapse
That warning by Chainfire relates to the various other superuser shells out there (like superuser.apk, ROM-specific superuser shells). Wait, what's the shell? Let me explain:
OK, so having root means you have three folders/files available:
superSU.apk (the shell; it's an interface lets you allow certain apps access to the actual superuser files..think of it as the root gatekeeper..having it alone does not mean you're rooted...seems like you have this)
/system/xbin/su/ (folder with files SPECIFIC to SuperSU.apk...apps can ask superSU.apk to access these "root-enabling" files ...you lost this)
/system/bin/su (folder with files SPECIFIC to SuperSU.apk...apps can ask superSU.apk to access these "root-enabling" files...you lost this, too)
The latter two, the folders, are collectively referred as su binaries. His warning: if don't like using superSU.apk as your shell, do not simply uninstall superSU.apk. Why? I'm not totally sure, but I think it's because that will leave the su binaries, specific to his app! Then, when an app wants to ask for root, it doesn't know what the flip to do. It has to interact with the shell, but the shell is missing!
The special method to really remove root is:
creepyncrawly said:
You can remove root by using a root file explorer to remove /system/app/superuser, /system/bin/su and /system/xbin/su. After you reboot, you'll not longer be rooted.
Click to expand...
Click to collapse
OK, the "what is going on behind the scenes" is over. To get root back:
Basically, you need to replace the su binaries. But, the only way I know how is to replace all three of those parts. I'm pretty sure you're fine to "overwrite" the 1/3 of root you already have (SuperSU.apk). Thus, you have two main options:
1) Use CF AutoRoot (http://forum.xda-developers.com/showthread.php?t=1963790). It will temporarily flash a modified recovery, and then add those binaries and the SuperSU.apk, and then flash the stock recovery back, but it will trip the flash counter. Takes 30 seconds. Should be safe, because it will just overwrite the apk and add the su binaries. [I rooted this way; triangle away is cheap to reset the flash counter!]
2) Use Mr. Robinson's method (http://forum.xda-developers.com/showthread.php?t=1739426). This contain a /system image with all three aforementioned parts. Will take about 15 minutes, but will not trip the flash counter. As long as you're on stock firmware (which I think you are), this won't delete any apps/data.
I got it rooted again. Thanks for help guys. I just reinstalled the supersu.apk and the binary files and it's rooted once again. Whoo-hoo!
What you'll need:
1: USB drivers---> http://forum.xda-developers.com/showthread.php?t=1500669
2: SuperOneClick v2.3.3.0 byshortfuse)
Connect your phone to your computer and run SuperOneClick. It should read "Successful" and then reboot your phone. I went straight to the appstore and downloaded BusyBox, SuperSU, ES File Explorer, and Titanium Backup but the SuperSU is your choice. If you do not grab the SuperSU then go ahead & update SuperUser. If you want to use SuperSU then give it SuperUser permission first. Open your ES file explorer and uninstall the SuperUser. This is a Sprint Kyocera Milano C5120 with 2.3.4 firmware loaded on it. So far I have not found a recovery that will work with this but it has one already there, you can find it by holding the volume down button and power before boot. These are just my findings that worked for me and I am not taking responsibility for your phone if anything happens to it, but mine was easy and painless. This will at least allow you to get rid of the preloaded apps on your phone.
If I've helped you in any way, please click thank you.
gimmeitorilltell said:
What you'll need:
1: USB drivers---> http://forum.xda-developers.com/showthread.php?t=1500669
2: SuperOneClick v2.3.3.0 byshortfuse)
Connect your phone to your computer and run SuperOneClick. It should read "Successful" and then reboot your phone. I went straight to the appstore and downloaded BusyBox, SuperSU, ES File Explorer, and Titanium Backup but the SuperSU is your choice. If you do not grab the SuperSU then go ahead & update SuperUser. If you want to use SuperSU then give it SuperUser permission first. Open your ES file explorer and uninstall the SuperUser. This is a Sprint Kyocera Milano C5120 with 2.3.4 firmware loaded on it. So far I have not found a recovery that will work with this but it has one already there, you can find it by holding the volume down button and power before boot. These are just my findings that worked for me and I am not taking responsibility for your phone if anything happens to it, but mine was easy and painless. This will at least allow you to get rid of the preloaded apps on your phone.
If I've helped you in any way, please click thank you.
Click to expand...
Click to collapse
This does not work. In march of 2012 an update was sent OTA to the Milano preventing zergrush and the other method Superoneclick uses from working.
Not sure if you have a very old phone or what but on any Milano purchased or updated after march 2012 SuperOneClick WILL NOT work.
I have been scouring Google for hours and have yet to find any way to root a Kyocera Milano that has been updated to prevent rooting exploits.
I'm guessing my phone was purchased in April or May of 2012 from Krogers and it probably sat on their shelf for a few months. Whatever the case, I'm sorry that you cannot root your phone as of now and if I run across something, I will share it with you.
Root Milano patched 2.3.4 Gingerbread
gimmeitorilltell said:
I'm guessing my phone was purchased in April or May of 2012 from Krogers and it probably sat on their shelf for a few months. Whatever the case, I'm sorry that you cannot root your phone as of now and if I run across something, I will share it with you.
Click to expand...
Click to collapse
I just got my phone from Ting a couple weeks ago and rooted it yesterday.
Unfortunately I can't directly post Outside links (Not at 10 posts yet, and have no idea what else to post about other than this at the moment, which requires a link (For Credit Due Purposes) and I know it will be helpful to people that were as desperate as me for something that was starting to seem rather impossible and no one was paying that much attention to it.), but this is important enough that I'll try to just chop it up - You'll just have to put it back together to go to that site.
This works:
androidforums
.com/milano-all-things
-root/709963-no
-pc-root-method
.html
Not sure why the guide says "Enable usb debugging in Settings, Applications, Development" since you never use the PC, I enabled it anyway, and also enabled to install third party apps, or else Poot won't install, not sure why that isn't on the guide. (Maybe they got mixed up?)
A few things you might want to know:
After hours I finally found the solution. But the terminal still doesn't work for uninstalling ("pm uninstall com.google.android.books.apk" = Failure), you have to do everything though your phone (I'm using the app "RootAppDelete"). The phone roots itself with a third party app called "Poot" using libraries from "Ministro 2"
Before doing this you're gonna need something like 25MBs of storage or so (Can delete everything afterwards with the exception of SuperUser (Can't delete that) to get the space back (Also, you need a app to actually use root actions). - The "Ministro 2" packages are huge for this phone's tiny internal storage! 11MB around)
Make sure to install anything small first and anything big right before the phone gets over 15MB full, because at that time you can't install anything else, with low memory errors.
Another thing that might have helped me when I did this is - back when I couldn't root I made all apps default install to the phone with the android sdk platform-tools (I didn't want to risk anything so I moved Poot, Ministro 2 and SuperUser back to the phone before running Poot. since they default installed to the SD)
"adb shell"
"pm SetInstallLocation 2"
Know its been said elsewhere, but this works with the Milano. Wanted to say that in case you needed the space to use Poot.
And the last problem is after I did all this, now my headphone jack wants to think it has headphones plugged in all the time, If I move the phone around it starts playing on the phone's speaker. It seems like something is lose. Not sure if that was caused by the root (since it wasn't doing it before, and I've never used the headphone jack before) or because there was lose hardware, not sure. Still working on a solution to that, which I found
something similar here, almost looks like a common problem: http://forum.xda-developers.com/showthread.php?t=817872
I would put my proof of doing this have a screen shot of root checker, but alas its an outside link. Understand though.
And as I've read a million times before this, here's a disclaimer: I'm not responsible and use at your own risk.
I'm not really sure what happened. I followed verbatim the instructions for motochopper, I was able to flash TWRP, and I was even able to flash the 4.2 Camera with Photo Sphere (though it doesn't work at all.), but when I try to run anything that requires root access, (Titanium Backup, for example), it tells me that it was unable to get root access. SuperSU tells me that it needs to update the superuser binary, but it always fails, and never tells me why. ChainsDD superuser is also giving me the same issue. I am very definitely stumped. I am open to all ideas at this point.
It's also starting to get glitchy since I did this, so I may just reset it until I can find some other way to get this thing rooted.
I do love it tho. Surprised a friend by controlling their TV with it. :angel:
I believe you need this: (I had to install before my root worked.)
http://forum.xda-developers.com/showthread.php?t=2271976
seattlestexan said:
I'm not really sure what happened. I followed verbatim the instructions for motochopper, I was able to flash TWRP, and I was even able to flash the 4.2 Camera with Photo Sphere (though it doesn't work at all.), but when I try to run anything that requires root access, (Titanium Backup, for example), it tells me that it was unable to get root access. SuperSU tells me that it needs to update the superuser binary, but it always fails, and never tells me why. ChainsDD superuser is also giving me the same issue. I am very definitely stumped. I am open to all ideas at this point.
It's also starting to get glitchy since I did this, so I may just reset it until I can find some other way to get this thing rooted.
I do love it tho. Surprised a friend by controlling their TV with it. :angel:
Click to expand...
Click to collapse
Thats what happened to me, and this is thread where I asked and got help to fix it.
http://forum.xda-developers.com/showthread.php?t=2288234
Okay, now I have root, verified that with SuperSU, Titanium Backup, and ROM Manager. Schweeeeeeeeet! Now if I could just get the Photospheres to work, I'd be in great shape!
I'm on stock E980 Kitkat and I just rooted my phone using the Root Tool for Kitkat (can be found elsewhere in the OGP forums). Everything went fine and the next step is to install SuperSU or Superuser from the Play store. This has been my routine all through my Android life: Root and then install a superuser app.
Well, currently I don't have any of these Superuser apps installed (honestly, I was in a hurry and simply forgot to install one) and everything is working perfectly fine. According to Root Checker, I have full root access. All apps who require root are working perfectly fine; maybe even better. Titanium Backup restored all my apps. No issues whatsoever!
So my question here is this:
In order to have proper root and for everything to qork perfectly, is a superuser app really necessary? Or can I just keep things the way they are right now (no su app) and expect everything to work just fine?
PS:
I've been having to reflash my rom several times because of certain root-requiring apps constantly force closing on me. I've had SuperSU installed while this has been happening and without an su app, these apps are doing exactly as they are supposed to. I'm now wondering if there is a bug (or just some other issue) in SuperSU or something.
In Beanstalk thread, its OP recommended to install SuperSU App and uninstall it afterwards.
Kinda confusing and i dont know its purpose from a developers perspective.
Sent from my SGH-T959 using XDA Free mobile app
souleater11 said:
In Beanstalk thread, its OP recommended to install SuperSU App and uninstall it afterwards.
Kinda confusing and i dont know its purpose from a developers perspective.
Sent from my SGH-T959 using XDA Free mobile app
Click to expand...
Click to collapse
My guess, and this is coming from the few hours today using my phone without an SU app, is that it's a security thing (?).
Without the SU app, anything on my phone has root access as it pleases and I have no clue as to what is being granted these permissions. This is fine for me personally because everything I have installed that needs root, I WANT to have root access and it's really annoying to me to have to have to manually grant everything access.
So, I'm starting to wonder if the SU apps are simply for managing root access; allowing certain apps permission, while restricting the access of others.
So far, I've been running the phone several hours without any SU app and the phone is working great! I don't have to constantly grant apps permission all the time (or well, first time I guess).
Super SU
It is better if you could have Super Su installed because then you can control apps that needs root permissions. Some times root privileges required apps can harm your device.
romikavinda said:
It is better if you could have Super Su installed because then you can control apps that needs root permissions. Some times root privileges required apps can harm your device.
Click to expand...
Click to collapse
OK, so SU apps like SuperSU are basically used to manage root access from root-requiring apps. A security measue basically.
This is what I figured, but had to make sure.
Thank you