I rooted my Motorola Charm with superoneclick 1.7, or atleast I thought I did. superoneclick 1.7 did say the rooting was succesful and I have superuser installed.
But when using Link2SD it says I didn't have root access. So I checked with Root Checker and apparantly Link2SD is correct. This is what Root Checker has to say:
Root Access is not properly configured or was not granted.
Alternate su binary location:
/sbin/suermission denied
SU binary not found in the system delcared PATH
Does anyone know what could be the issue? And if not, then would anyone know what is the safest way to proceed from here? I already have superuser and superoneclick says it is Rooted, I'm not sure what would happen if I were to root it again.
I had the same problem with my Milestone, rooted it using AndRoot. I used Superuser to update the su binaries, but still nothing. Then a simple reboot fixed it
My Milestone2 rooted successfully by SuperOneClick 1.3 ,
you can use the 1.3 version to root
milest0ne2 said:
I had the same problem with my Milestone, rooted it using AndRoot. I used Superuser to update the su binaries, but still nothing. Then a simple reboot fixed it
Click to expand...
Click to collapse
Edit: after a second reset it worked! Thank you very much!
Related
First time I rooted using "One-Click Universal root for stock firmware - V4" and its worked.
After few firmware updates using CWM, When I open Titanium Backup it says root access failed. I root again using above method and it says same thing. I can't assess root apps and Can't update Su Binaries in SuperUser app. Every time says Don't have root permissions.
I install Razorclaw and its says This device already has correct su binaries(already rooted). Cannot continue.
Please help me to solve this problem. Thanks !
Try this to see if it work.
http://forum.xda-developers.com/showpost.php?p=19555429&postcount=234
Hi
I am on RE-odexed JPU.
I have problem with root ...
I tried Superoneclick 1.9.1, 1.9.5 and 2.3.3
1.9.1 worked upto JPS.
2.3.3 does not work on JPU, even it said root access passed, it does not really,
Same problem is when update for superuser APK + SU binary by Google market ,,,
After factory default, it mostly works, but it is only question of time when some or all apps said they have no root access even allowed before or superuser does not respond and I get no root access :-(
anyone knows how to root re/odexed or odexed stock JPU permanently ?
radek.god said:
Hi
I am on RE-odexed JPU.
I have problem with root ...
I tried Superoneclick 1.9.1, 1.9.5 and 2.3.3
1.9.1 worked upto JPS.
2.3.3 does not work on JPU, even it said root access passed, it does not really,
Same problem is when update for superuser APK + SU binary by Google market ,,,
After factory default, it mostly works, but it is only question of time when some or all apps said they have no root access even allowed before or superuser does not respond and I get no root access :-(
anyone knows how to root re/odexed or odexed stock JPU permanently ?
Click to expand...
Click to collapse
You should have root and update Superuser before you re-odex. To solve it, just download the latest Superuser here, removed Superuser.odex from "/system/app/" with Root Explorer or ADB, then install the .zip through CWM recovery.
radek.god said:
Hi
I am on RE-odexed JPU.
I have problem with root ...
I tried Superoneclick 1.9.1, 1.9.5 and 2.3.3
1.9.1 worked upto JPS.
2.3.3 does not work on JPU, even it said root access passed, it does not really,
Same problem is when update for superuser APK + SU binary by Google market ,,,
After factory default, it mostly works, but it is only question of time when some or all apps said they have no root access even allowed before or superuser does not respond and I get no root access
anyone knows how to root re/odexed or odexed stock JPU permanently ?
Click to expand...
Click to collapse
adb push su & binary to system/xbin/*...or system/bin/*....and superuser.apk to system/app/*...
you can do this if you have adb access via kernel...use qtadb for pushing files
Sent from my SGS-II powered by CM9
I rooted my phone back on ICS and when I updated to Jelly Bean, I used root keeper and restored the root. Voodoo rootkeeper says that I my device is rooted. My titanium backup shows that I have root and the program works perfectly Lightlow has root and works perfectly. The problem is that I can not grant root permissions to other applications. Superuser is installed, but shows outdated binaries.. I tried to update them but it says no root. Rootchecker also says that I do not have root. What I dont get is that the programs I already granted root access still work but I cant add more. Any ideas on what is going on? Thanks!
Unlocked bootloader. Installed twrp successfully. Flashed majisk successfully yet busybox will not install and root checker reports root not obtained... Huh?
Is this because root checker and busybox look for supersu to be in a certain place and when they can't find it they report no root?
If majisk is essentially root then why does it fail the checks? I am able to install and use apps that require root... What gives? (Sorry for being dumb)
kerryh420 said:
Unlocked bootloader. Installed twrp successfully. Flashed majisk successfully yet busybox will not install and root checker reports root not obtained... Huh?
Is this because root checker and busybox look for supersu to be in a certain place and when they can't find it they report no root?
If majisk is essentially root then why does it fail the checks? I am able to install and use apps that require root... What gives? (Sorry for being dumb)
Click to expand...
Click to collapse
IDK about the root situation, but the way I usually install busybox on the pixel is goto the play store and search busybox and pick the one by meefik. Then open it and change the install location from system/xbin to just system/bin (so remove the x)
kerryh420 said:
Unlocked bootloader. Installed twrp successfully. Flashed majisk successfully yet busybox will not install and root checker reports root not obtained... Huh?
Is this because root checker and busybox look for supersu to be in a certain place and when they can't find it they report no root?
If majisk is essentially root then why does it fail the checks? I am able to install and use apps that require root... What gives? (Sorry for being dumb)
Click to expand...
Click to collapse
This is the best BusyBox installer in my opinion.
From this thread. Works for system or systemless installations.
Flash in TWRP.
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that kingoroot superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the kingoroot superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Couldn't get it to install says it's arm device tries to install and says it's an arm64 device. Plus has to be flashed in recovery and one hasn't been built yet
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
erono said:
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
Click to expand...
Click to collapse
I installed supersu to find out if it was rooted since the root checker said it was not. the binary error was a confirmation that it was in fact rooted and it doesn't matter what superuser is used it will not allow pop up or apps to draw over other apps so when it's rooted with kingoroot it automatically grants root without a confirmation,as long as the kingoroot super user app is not installed and if SuperSU is kept installed default permission has to be set to grant for root to work. I in fact installed the SuperSU binary through an older version of the apk and it installed but still has no control over denying or granting permissions. Thanks for the advice though. I appreciate your willingness to help me
Joker1716 said:
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Click to expand...
Click to collapse
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
smam1338 said:
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
Click to expand...
Click to collapse
Prompt dialog not working in amazon fire devices.
erono said:
Prompt dialog not working in amazon fire devices.
Click to expand...
Click to collapse
Set prompt to grant and fixed.
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
stevenchun said:
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
Click to expand...
Click to collapse
One can try this improvement :
SuperSU access workaround for Fire devices
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269