Alright, here's the situation I have going on here. Today I was going through my phone with System Tuner Pro. Looking to get more space to install apps, I went found superuser and tried moving to SD card. At that point the application crashed. When trying to open the app again it gave me a denied permission prompt. I then went ahead and opened Root Explorer and again another deny prompt. I then went to the Superuser website to get a zip file to reinstall the apk. http://androidsu.com/superuser/ I downloaded su bin and apk zips files. And went ahead into the steps on installing them through recovery. Yes I know how to wipe cache and dalvik before hand installing the zip files. I then rebooted it and tried using Root Checker, no access again. Then tried using SU Updater, again it told me to reinstall Superuser, I've already done that, but for the heck of it, I did it again. No luck, I've decided after reading a few articles online about similar problems, to install the Busybox installer. On the front page it says "Your device is rooted.". Yes this phone is rooted before hand if you couldn't tell. Little note Everything is being deny access even the Superuser app itself.
The phone is a LG-VM670
Running on Android 2.3.7
Thank you for your help you kind force hero.
Related
Just got a new thunderbolt and here is where I am at.. I "think" I've tried just about everything before I'd ask here since this whole superuser thing seems to be a problem had by more than a few people.
1. Tried the http://forum.xda-developers.com/showthread.php?t=1005292 root method. Did not work. Never got past step one. No big deal.
2. Followed this http://wiki.cyanogenmod.com/wiki/HTC_Thunderbolt:_Full_Update_Guide and did the root by hand. Went through fine with no problem.
3. Upon reboot noticed that Titanium backup FC's superuser. BUT root explorer works.
4. went to manage app's and cleared data for superuser. Did not work.
5. Redid the final step of pushing su and setting permissions. Did not work.
6. Reinstalled busybox from market. Did not work.
7. Updated superuser from market. Did not work.
8. Loaded Rom Manager and tried to fix permissions. Did not work. could not gain rights.
I'm not against doing the whole process over. Would I just start at step one and redo the whole process?
From a technical standpoint what would let root explorer be able to gain access but no other program? Just for informations sake.
Any other suggestions of what to try? If I missed something I apologize. Still reading.
Thanks
Bruce
Fixed - 7/3/11 - 9:45am EST
Just got an update to SU. Said yes to install and everything is perfect now.
Enjoy
Bruce
Hi guys, i am wondering if anyone have been successful updating their superuser binary files?
My NT is rooted, and i have installed busybox through the android market busybox installer. However I keep getting a message on my NT's notification bar that my SU binary is out of date, but when i go into SU to do a binary update, it show failure to update. So far this has not cause me any issues, but it is annoying that the message keep showing up after every once a while.
Has anyone been successful running the SU binary update on their NT? if so can you share your experience on how you done it?
Thank you.
Uninstall superuser, install it back from market immediately and you should be good to go. At least this worked for me.
That doesn't sound safe to do. Doesn't android need SU permission to install the SU app. That is why most none rooted device cannot simply install SU from the market to get root...
Please correct my understanding of how root works if i am incorrect.
sideload an updated .apk of SU. It will tell you it's replacing an existing file.
I had this problem and just cleared superuser data to fix it.
theundeadelvis said:
I had this problem and just cleared superuser data to fix it.
Click to expand...
Click to collapse
How is that done?
Go to the "manage applications" menu, find superuser, and click on clear data. You'll need need something like AppMenu to get to the applications menu.
Sent from my BNTV250 using Tapatalk
Try this https://market.android.com/details?id=com.noshufou.android.su.fixer&feature=search_result
Have noticed several custom rom but no single solution on how to acheive or even install custom ROMs. I tried VRoot which gave me root but left that method after realizing that i couldnt replace su with supersupro. I also got a vague hint that I was sandboxed. I might be paranoid but as.several other users has reported similar issue i decided to factory reset and also restore from backed up data in the PC suit. Please advice about how to be able to flash custom roms or more desired obtain root on stock ROM. Cause I will want to try out the official Kit Kat when it rolls out. Peace!!
Sent from my C6833 using XDA Premium 4 mobile app
You can replace the superuser app from vRoot.
- Download SuperSU and open it. Update binaries.
- Use a file explorer and go to /system/app
- Find "superuser.apk" and delete it (Superuser will ask for root. Press yes)
- Your file explorer might argue that it can't delete it (since you're trying to delete the app that gave you the permission in the first place. I guess he's not happy about that, but screw him, he's gone)
- Open SuperSU again and see if all is well (update binary if it asks for it again)
- Reboot and you're done
This is what i've done every time i've rooted and it always work
Tried that
LordManhattan said:
You can replace the superuser app from vRoot.
- Download SuperSU and open it. Update binaries.
- Use a file explorer and go to /system/app
- Find "superuser.apk" and delete it (Superuser will ask for root. Press yes)
- Your file explorer might argue that it can't delete it (since you're trying to delete the app that gave you the permission in the first place. I guess he's not happy about that, but screw him, he's gone)
- Open SuperSU again and see if all is well (update binary if it asks for it again)
- Reboot and you're done
This is what i've done every time i've rooted and it always work
Click to expand...
Click to collapse
I tried that method actually before you sent me the instructions. I works fine but or some strange reason I get a lots of chinese characters wile allowing apps root... This vroot seems very keen on holdiong on to the root that it had. ) I need a script or something Iḿ getting tired about al this.
:cyclops:
If there's still a chinese prompt that pops up when asking for root, it means that you haven't removed it. SuperSU is the app that should ask you for root access
I just flashed CM11 onto my Amaze (T-Mobile S-ON) and everything runs fine except when I tried to use titanium to restore my apps, it gave me this message: "Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command." I opened Superuser and scrolled to info. It says "superuser v3.1.3 (46)" and "su binary v3.1.1 (17). When I press on the su, it goes to a binary updater which says "downloading manifest," then, after a minute or so, it says "fail" in red at the end of the "downloading manifest" line. I downloaded superuser by CWM after this problem and when I opened the app, it said: "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." It gives me the option to press cancel or Recovery Install. When I press recover install, it says: "There was an error installing Superuser. Please send a log of the error to the developer." I went onto the superuser website, downloaded the latest arm su and superuser, put them on my sd card, went into 4ext and installed both from sd card and still have the same problem.
Problem: I can't grant superuser permissions to any apps because something is wrong with my su binary. I tried installing su-bin-3.1.1-arm-signed.zip from 4ext and it said the installation was successful, so I do not know what is wrong.
Root?
luisandroid said:
Problem: I can't grant superuser permissions to any apps because something is wrong with my su binary. I tried installing su-bin-3.1.1-arm-signed.zip from 4ext and it said the installation was successful, so I do not know what is wrong.
Click to expand...
Click to collapse
I think you are not rooted.
Try app "Simple Root Checker" from Play Store:
https://play.google.com/store/apps/details?id=com.simonedev.simplerootchecker
If not rooted, try this to gain root:
http://forum.xda-developers.com/showthread.php?t=2437057
pbergonzi said:
I think you are not rooted.
Try app "Simple Root Checker" from Play Store:
https://play.google.com/store/apps/details?id=com.simonedev.simplerootchecker
If not rooted, try this to gain root:
http://forum.xda-developers.com/showthread.php?t=2437057
Click to expand...
Click to collapse
I used that app and it said: "Android 4.4.2 HTC Amaze 4G Application Superuser found Terminal Rooted Busybox installed BusyBox v1.21.1" So I am guessing I am rooted. Should I try using that tool to flash SuperSU anyway? Thanks for helping me out with this.
SuperUserSU problems.
luisandroid said:
I used that app and it said: "Android 4.4.2 HTC Amaze 4G Application Superuser found Terminal Rooted Busybox installed BusyBox v1.21.1" So I am guessing I am rooted. Should I try using that tool to flash SuperSU anyway? Thanks for helping me out with this.
Click to expand...
Click to collapse
Nice--my mistake. In your Superuser info, where you found your su binary listed "su binary v3.1.1 (17)", did it give the file specs right underneath--it does in mine.
Also, if you go into Superuser app, then Preferences->Security->Automatic Response, is that accidentally set to "Deny?" Betcha' that won't work.
Is Titanium Backup listed in your Superuser apps list, and if you open the info there, is it "Allowed?"
Probably what you said about re-flash Superuser is reasonable, and worth a shot if the Automatic Response is already set to Allow or Prompt.
I'll also wager that someone else with good insight and experience will stop in the thread with a working answer for you.
luisandroid said:
I just flashed CM11 onto my Amaze (T-Mobile S-ON) and everything runs fine except when I tried to use titanium to restore my apps, it gave me this message: "Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command." I opened Superuser and scrolled to info. It says "superuser v3.1.3 (46)" and "su binary v3.1.1 (17). When I press on the su, it goes to a binary updater which says "downloading manifest," then, after a minute or so, it says "fail" in red at the end of the "downloading manifest" line. I downloaded superuser by CWM after this problem and when I opened the app, it said: "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." It gives me the option to press cancel or Recovery Install. When I press recover install, it says: "There was an error installing Superuser. Please send a log of the error to the developer." I went onto the superuser website, downloaded the latest arm su and superuser, put them on my sd card, went into 4ext and installed both from sd card and still have the same problem.
Problem: I can't grant superuser permissions to any apps because something is wrong with my su binary. I tried installing su-bin-3.1.1-arm-signed.zip from 4ext and it said the installation was successful, so I do not know what is wrong.
Click to expand...
Click to collapse
The problem you describe is common with more recent versions of CM (at least I've experienced it). It's due to the way CM is now implementing their included Superuser app, which is different from how it used to behave and how many other apps expect it to behave. The solution is to flash SuperSU in recovery from this thread http://forum.xda-developers.com/showthread.php?t=1538053 (if it resolves your issues please remember to thank its creator and consider purchasing the full version).
When you set it up, enable "pro" mode, survival mode, allow it to install the scripts, and respect CM root settings. If installed correctly you should be good to go.
I hope this helps
Odysseus1962 said:
The problem you describe is common with more recent versions of CM (at least I've experienced it). It's due to the way CM is now implementing their included Superuser app, which is different from how it used to behave and how many other apps expect it to behave. The solution is to flash SuperSU in recovery from this thread http://forum.xda-developers.com/showthread.php?t=1538053 (if it resolves your issues please remember to thank its creator and consider purchasing the full version).
When you set it up, enable "pro" mode, survival mode, allow it to install the scripts, and respect CM root settings. If installed correctly you should be good to go.
I hope this helps
Click to expand...
Click to collapse
That solved the problem! Got CM 11 running on my Amaze! I made sure to thank the dev! Thank you for your help as well!
After a complex process to repair my bricked S3 (4.4.2), I rooted the phone with Towelroot (confirmed its rooted) and installed Superuser from the Play store.
I was of the understanding that when Superuser is installed from the Play Store that the binary upgrade is not necessary. However, I have seen no indication that Superuser is working. I explored the system/bin and system/app files with ESExplorer and I got no request from Superuser to allow root access. (there are not Superuser files either location)
I also explored the files with TitaniumBackup Pro and again not peep out of Superuser.
I went ahead and tried the binary update and it fails.
I thought I'd ask for help here before I uninstall Superuser and install SuperSU (I noticed Superuser has been updated since July 2012). At this point I believe uninstalling Superuser would be successful because it is a Play Store install.
Any help/recommendations would be appreciated. As you can tell I'm a novice at this.
NOTE: Just noticed that there are not entries in the Superuser log.
Try rooting with cf-root
dabyd64 said:
Try rooting with cf-root
Click to expand...
Click to collapse
Thank you for the recommendation, however, I just went ahead and uninstalled Superuser and installed SuperSU. SuperSU appears to work and is managing root access as it should.
I probably would not have gone the uninstall method with Superuser, however, I installed it from the Play Store and the Play Store installation is reportedly easy to uninstall because it does not put files in system/app or system/bin......at least I read that somewhere and I checked these locations and there were no Superuser files there.
Thanks again.
Superuser is located on /system/app
su is on /system/xbin