Related
So I have a Samsung Vibrant with the following specs :
Firmware : 2.1-update 1
Baseband : T959UVJI6
Kernel version : 2.6.29
Build : ECLAIR.UVJI6
I used the Samsung Vibrant 1 click root application, have since verified I do have SuperUser installed as well as BusyBox, with quite a few different root based applications such as ClockWorkMod Recovery, One-Click Lag Fix, Set CPU, Titanium Backup, etc., and I have verified that ADB does work from a command prompt, however when I try to access su through ADB by doing the following commands, this happens :
C:/>adb shell
$ su
su
Permission denied
$
I have also tried to use Android Commander from my PC as a kind of root explorer and the program does detect my device and starts, but shows "Root Access : NO". From all threads I have investigated, this would almost seem as though I don't have "true" root access. Can anyone assist me and let me know what I am doing wrong?
bretjrodgers said:
So I have a Samsung Vibrant with the following specs :
Firmware : 2.1-update 1
Baseband : T959UVJI6
Kernel version : 2.6.29
Build : ECLAIR.UVJI6
I used the Samsung Vibrant 1 click root application, have since verified I do have SuperUser installed as well as BusyBox, with quite a few different root based applications such as ClockWorkMod Recovery, One-Click Lag Fix, Set CPU, Titanium Backup, etc., and I have verified that ADB does work from a command prompt, however when I try to access su through ADB by doing the following commands, this happens :
C:/>adb shell
$ su
su
Permission denied
$
I have also tried to use Android Commander from my PC as a kind of root explorer and the program does detect my device and starts, but shows "Root Access : NO". From all threads I have investigated, this would almost seem as though I don't have "true" root access. Can anyone assist me and let me know what I am doing wrong?
Click to expand...
Click to collapse
When you do "Adb shell" > "su" you have to allow it on your phone. A little popup will appear.
If you can su in a terminal on the phone itself then you can be certain you have root.
Are you sure there is not a prompt on the phone when you are attempting su from ADB? It might be asking for su permissions but timing out and showing denied.
bretjrodgers said:
So I have a Samsung Vibrant with the following specs :
Firmware : 2.1-update 1
Baseband : T959UVJI6
Kernel version : 2.6.29
Build : ECLAIR.UVJI6
I used the Samsung Vibrant 1 click root application, have since verified I do have SuperUser installed as well as BusyBox, with quite a few different root based applications such as ClockWorkMod Recovery, One-Click Lag Fix, Set CPU, Titanium Backup, etc., and I have verified that ADB does work from a command prompt, however when I try to access su through ADB by doing the following commands, this happens :
C:/>adb shell
$ su
su
Permission denied
$
I have also tried to use Android Commander from my PC as a kind of root explorer and the program does detect my device and starts, but shows "Root Access : NO". From all threads I have investigated, this would almost seem as though I don't have "true" root access. Can anyone assist me and let me know what I am doing wrong?
Click to expand...
Click to collapse
So after installing SU Terminal & Root Explorer from Android Market, when I did the following :
C:/>adb shell
$ su
su
#
I have verified that SuperUser permissions through ADB are obviously working. However when I do the following command...
C:/>adb root
adbd cannot run as root in production builds
...is displayed. It seems as though, yes, I do have SuperUser access, I don't have root access through ADB and Android Commander still does not recognize root. Is this because I am running the stock ROM, and if so, is there a general thread with all available/recommended Vibrant ROMs to install?
bretjrodgers said:
So after installing SU Terminal & Root Explorer from Android C:/>adb root
adbd cannot run as root in production builds
...is displayed. It seems as though, yes, I do have SuperUser access, I don't have root access through ADB and Android Commander still does not recognize root. Is this because I am running the stock ROM, and if so, is there a general thread with all available/recommended Vibrant ROMs to install?
Click to expand...
Click to collapse
Just to clarify, you realize adb root has nothing to do with your phone?
adb root restarts the adb daemon on the computer you are on as root (something I usually don't recommend).
When you start Android Commander make sure it has permissions on your phone when it makes the request.
d01100100 said:
Just to clarify, you realize adb root has nothing to do with your phone?
adb root restarts the adb daemon on the computer you are on as root (something I usually don't recommend).
When you start Android Commander make sure it has permissions on your phone when it makes the request.
Click to expand...
Click to collapse
Ok so I now understand the purpose of the adb root command after some additional research. I guess the issue is that when I run Android Commander, even though it does detect my device on the PC, it does not ask for/request SU permissions on my device
The FAQ thread for Android Commander:
http://forum.xda-developers.com/showthread.php?t=628138
** If you using Win7/Vista run Program as Administrator or disable UAC, otherwise this function will fail!
Click to expand...
Click to collapse
Guess I never needed for something like this since I'm comfortable with the command line.
d01100100 said:
The FAQ thread for Android Commander:
http://forum.xda-developers.com/showthread.php?t=628138
Guess I never needed for something like this since I'm comfortable with the command line.
Click to expand...
Click to collapse
I am running the program with both UAC disabled, and running as administrator and still the program does not recognize as root. I am only worried not just about Android Commander, but the possibility for functionality of other programs that require root as well.
Type adb shell
You'll see '$' as your prompt, type 'su'
$ su
You'll see '#' as your prompt, type 'id'
# id
uid=0(root) gid=0(root)
That means you have root.
Further proof you can remount /system from ro to rw.
You have root, Android Commander isn't the standard to judge whether your root is working correctly. Just a cursory glance at the app thread, it requires quite a bit of finesse to get working and it's touchy about which rom you're using. If yours doesn't work and you've actually followed the directions, send the developer your logs in the proper thread.
Why not just download the app Terminal Emulator and just type "su".... you'll either get the # or Permission Denied.
Based off everything you said, yes, you have root... ^ easiest way to test though. No need to deal with adb.
Hello there,
i just wanted to find out where the precompiled su comes from (busybox or coreutils) and why it is not compiled with busybox since it is part of it. I did look on the net and searched the forum, but i didn't find any information.
Would be nice if someone could answer my questions.
It comes from neither of them. The Android su is different from the standard Unix (busybox, coreutils) su in that it calls superuser.apk to decide if root permission is granted instead of asking for a password.
You find the Android su here: Superuser.apk
hi,guys!
as this title says i found a tool named "rageagainstthecage",but i want to know how dose it work.Can anyone help me ? thanks
try superoneclick
Are you using Linux to grant root access on your Defy?
I rooted mine yestarday and I was a little confused on how to make it, I have same file as you as I read. rageagainstthecage is the exploit that will you grant root privileges. The instructions for linux are here [1]. I replaced 'exploit.bin' with 'rageagainstthecage' or you can use the one provided in that post 'psneuter', the proccess is simple
1. Copy files to phone using adb (I used /data/local/tmp as directory in the phone): su, busybox, Superuser.apk and exploit (exploit name, let's say: rageagainstthecage)
2. Make the exploit executable and execute it
3. Give permissions to the commands su and busybox
4. There you go
All the credits for the autor of the post on IBM forum
I hope this help you with your question
[1]
PHP:
www_ibm_com/developerworks/mydeveloperworks/blogs/coolwinding/entry/how_to_root_defy_on_linux1
jianbangguo said:
try superoneclick
Click to expand...
Click to collapse
Dose the superoneclick use "rageagainstthecage" to grant adb root access? i just want to know "rageagainstthecage", how dose it work? can you help me? thanks
cristianpark said:
Are you using Linux to grant root access on your Defy?
I rooted mine yestarday and I was a little confused on how to make it, I have same file as you as I read. rageagainstthecage is the exploit that will you grant root privileges. The instructions for linux are here [1]. I replaced 'exploit.bin' with 'rageagainstthecage' or you can use the one provided in that post 'psneuter', the proccess is simple
1. Copy files to phone using adb (I used /data/local/tmp as directory in the phone): su, busybox, Superuser.apk and exploit (exploit name, let's say: rageagainstthecage)
2. Make the exploit executable and execute it
3. Give permissions to the commands su and busybox
4. There you go
All the credits for the autor of the post on IBM forum
I hope this help you with your question
[1]
PHP:
www_ibm_com/developerworks/mydeveloperworks/blogs/coolwinding/entry/how_to_root_defy_on_linux1
Click to expand...
Click to collapse
pardon my poor english,I just want to know how dose it work, for example : rageagainstthecage's Working principle,not how to use "rageagainstthecage" to grant root access,thank you !!
The principle of how it works is very simple, the rageinthecage exploit just forks proccesses until the proccessor hits the max, then the system will kill the olders apps, because you are using adb and running psneuter, the system will kill the adb shell, and here is the magic, when you restart the adb shell it start with root rights, to prevent that, inmediatly adb starts, the system calls setuid function, but because the proccesses list is full, the explot prevents the setuid call, allowing you to maintain the root rights, and in that point, you push Superuser.apk to allow the root access to the apps, changin before the permissions to the su binary allowing you to call that binary with a less rights user, that is the idea beyond the exploit!, wish that help you!
Sorry for the bad english
LeonardoJegigzem said:
The principle of how it works is very simple, the rageinthecage exploit just forks proccesses until the proccessor hits the max, then the system will kill the olders apps, because you are using adb and running psneuter, the system will kill the adb shell, and here is the magic, when you restart the adb shell it start with root rights, to prevent that, inmediatly adb starts, the system calls setuid function, but because the proccesses list is full, the explot prevents the setuid call, allowing you to maintain the root rights, and in that point, you push Superuser.apk to allow the root access to the apps, changin before the permissions to the su binary allowing you to call that binary with a less rights user, that is the idea beyond the exploit!, wish that help you!
Sorry for the bad english
Click to expand...
Click to collapse
Great info, thanks for sharing this with us I was wondering the same
I have flashed my ZTE Open to FFOS 1.4 with this method (http://forum.xda-developers.com/showthread.php?t=2680514), only some bugs - AND: How can I root the ZTE, this method ( pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions) don't work. My before 1.2-prerelease-version was rooted of course.
martin_s5670 said:
I have flashed my ZTE Open to FFOS 1.4 with this method (http://forum.xda-developers.com/showthread.php?t=2680514), only some bugs - AND: How can I root the ZTE, this method ( pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions) don't work. My before 1.2-prerelease-version was rooted of course.
Click to expand...
Click to collapse
You can install cwm recovery and root first with 1.1 or 1.2 then install 1.4 and do a factory reset from cwm. It should tell you lost root and install it again for you.
Yes, I have done this several times, but i can't get /system/xbin. There is only a "su" in /system/bin.
martin_s5670 said:
Yes, I have done this several times, but i can't get /system/xbin. There is only a "su" in /system/bin.
Click to expand...
Click to collapse
Have you tried if "su" works from ADB?:
1) adb shell
2) su
if it works from there you must be able to use it to install it in xbin.
I'm repeating the process in a new one I got this afternoon... maybe I can make a quick guide from zero.
Exactly that's my problem: su don't work. I get:
...
[email protected]:/ # su
su
/system/bin/sh: su: not found
127|[email protected]:/ #
...
Therefore: How to root a FFOS 1.4?
martin_s5670 said:
Exactly that's my problem: su don't work. I get:
...
[email protected]:/ # su
su
/system/bin/sh: su: not found
127|[email protected]:/ #
...
Therefore: How to root a FFOS 1.4?
Click to expand...
Click to collapse
That means that the utility you've used to root your phone hasn't worked. Just a heads up: you need to be on Firefox OS 1.0 to root your phone, every version after has patched it (because the only reason you can root it in the first place is a vunerability which has since been fixed).
Google search "Firefox OS 1.2 ZTE OPEN" and click on the top link to the Mozilla Hacks website with the title of "Upgrading your ZTE Open to Firefox 1.1 or 1.2 (fastboot enabled)", then scroll down to the bottom and click the 1 to go to the first page of comments, then scroll to the bottom again and click the bottom link to find a google drive download called "update-signed.zip". Download that and install it, enable "Remote Debugging" in developer settings, root your phone, install CWM Recovery and re-download and install the OS you want to use.
Pardon, but I know all this, how to root etc ZTE 1.0 resp. 1.2 - and I have a rooted ZTE 1.2. The problem is, that after installing 1.4 you have no root, you can't get the su-binaries in /system/xbin.
martin_s5670 said:
Pardon, but I know all this, how to root etc ZTE 1.0 resp. 1.2 - and I have a rooted ZTE 1.2. The problem is, that after installing 1.4 you have no root, you can't get the su-binaries in /system/xbin.
Click to expand...
Click to collapse
Oh I'm sorry I understand now! I assume that is an issue with 1.4 not being finished yet, I imagine the only real solution is to revert back to a "finished" build of B2G
I am trying to root my huawei P8 lite but WITHOUT using the propriatery SuperSu binary therefore I managed to install the Superuser. But now I am missing the su binary as far I searched I found this su binary https://download.lineageos.org/extras . After that I rebooter to system and typed in my console (with usb debugging enabled):
Code:
adb shell
In the phone's console I typed:
Code:
su
But I get the following error:
Code:
Permission denied
DO you think that SeLinux block me to run su and how I will ovveride this restriction? If not do you have any idea why I cannot execute the su binary?
pc_magas said:
I am trying to root my huawei P8 lite but WITHOUT using the propriatery SuperSu binary therefore I managed to install the Superuser. But now I am missing the su binary as far I searched I found this su binary https://download.lineageos.org/extras . After that I rebooter to system and typed in my console (with usb debugging enabled):
Code:
adb shell
In the phone's console I typed:
Code:
su
But I get the following error:
Code:
Permission denied
DO you think that SeLinux block me to run su and how I will ovveride this restriction? If not do you have any idea why I cannot execute the su binary?
Click to expand...
Click to collapse
You have to flash superSu or magisk or something similiar. There shouldn't be any work around for this. SeLinux has nothing to do with this(I think).
keikari said:
You have to flash superSu or magisk or something similiar. There shouldn't be any work around for this. SeLinux has nothing to do with this(I think).
Click to expand...
Click to collapse
But all these tools need to install somehow the su binary in order to work. What I am trying is to do is ti install it by hand. On GNU/Linux systems that Android is based on use this binary in order to provide su access.
pc_magas said:
But all these tools need to install somehow the su binary in order to work. What I am trying is to do is ti install it by hand. On GNU/Linux systems that Android is based on use this binary in order to provide su access.
Click to expand...
Click to collapse
But that's been purposely prevented. You need to install TWRP recovery then you flash one of them and now you can use "su" command.
I don't know much(read anything) about how linux system works, so I don't understand why you want to get "su" stuff work other than normal way to do it. Meaning is there some specific reason why you don't want to flash SuperSu?
keikari said:
But that's been purposely prevented. You need to install TWRP recovery then you flash one of them and now you can use "su" command.
I don't know much(read anything) about how linux system works, so I don't understand why you want to get "su" stuff work other than normal way to do it. Meaning is there some specific reason why you don't want to flash SuperSu?
Click to expand...
Click to collapse
Because SuperSu is a propriatery software.
pc_magas said:
Because SuperSu is a propriatery software.
Click to expand...
Click to collapse
I think magisk is open source https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 maybe you want to give it a try.
ps. Is open source opposite of propriatery? if not pls ignore this post
I love you you're awesome!!!!!