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.
I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!
crimsontide said:
I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!
Click to expand...
Click to collapse
If you used BurritoRoot and you were able to successfully install the Market, then you likely have root.
Easiest and simplest way to 100% know is connect your KF to your PC. Run the following:
Code:
adb shell
su
If it says "su: Permission Denied" you don't have root (or at least it is not currently enabled). If it just gives you a prompt run:
Code:
id
If it comes back and says "uid=0(root) gid=0(root)" then you are good.
Make sure you use the superuser posted in the burritoroot post. There was one posted originally that was no good with the kindle fire but they updated to a working one.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
http://www.mediafire.com/?jj8sx4ojvq9i198
litotamez said:
if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
I tried that app and it reports, "Sorry, you don't have root access."
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac devices
List of devices attached
7766000600000001 device
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell
$ su
su: permission denied
$
Looks like I have some more work to do, and I am not sure where to start.
I have installed on the KF:
BurritoRoot: Kindel Fire Edition 1.0.0
version 1.0.0
SuperUser version 3.0.6
Click to expand...
Click to collapse
Ok I went back and re-ran everything. Had to uninstall SuperUser in the middle, but things seem to be working better now!!!
HTML:
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac root
adbd is already running as root
Traveler:KindleFireRootMacLinux crimsontide$ adb push su /system/xbin/su
-bash: adb: command not found
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac push su /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chown 0.0 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chmod 06755 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
4426 KB/s (785801 bytes in 0.173s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
2858 KB/s (785801 bytes in 0.268s)
pkg: /data/local/tmp/Superuser.apk
Success
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac reboot
I have a Galaxy S4 (GT-I9507) which is rooted with busybox installed and the CWM custom recovery. I recently made a Nandroid backup and since I don't have an sdcard, it was stored in /data/media/clockworkmod/backup/ or /mnt/shell/emulated/clockworkmod/backup/. Now, I can't move this using a root explorer app to an area accessible via USB to back it up to my computer since I don't have enough room left on my phone, so I've been trying to copy it to my PC using adb pull. Thing is, I'm on a stock ROM so my original adbd binary does not allow adb root. So I installed Chainfire's adbd Insecure app and enabled it. Now when I run adb root I'm told that adbd is already running as root. When I do adb shell, I get
Code:
[email protected]:/ #
. However, adb is not actually running as root. It just appears to run as root. It says it's running as root but if I try
Code:
adb shell ls /data/media/
I get Permission Denied. Until I actually do
Code:
adb shell
su
ls /data/media/
I continue to get Permission errors. This means that
Code:
adb pull /data/media/clockworkmod/
or
Code:
adb pull /mnt/shell/emulated/clockworkmod/
both fail too because despite adb saying it's running as root and looking like it's running as root it does not actually have root privilege. My question is how on earth do I actually get it to have root privilege so I can pull my CWM backups without permission errors?
Spec info:
Samsung Galaxy S4 (GT-I9507) running KitKat 4.4.2 connected via USB Cable to a PC running Windows 7. Command prompt with Administrator privileges is used to access adb.
I have Samsung Intercept from Sprint with Android 2.1, locked. Tried to root it with SuperOneClick 2.3.3. It seems device is rooted (it is not failed during the rooting, and Root Checker shows phone is rooted). SuperUser was installed.
su in /system/xbin
remounting system with read only access
I used simple Root and not Shell Root. I installed Titanium Backup but was unable to start it. I've got the following error:
Could not acquire root privileges. This app will not work. Verify rom is rooted. Attempt was made using /system/xbin/su command.
In Titanium: Root access failed.
So, it seems I'm able to install non-market app but unable to run it, because SU failed to recognize it.
How to root this phone in a right way? Should I unroot it and make Shell Root? Will this unlocked the bootloader? Would this affect the wifi and other phone functions? If the system was mounted with read access only how to get write access rights?
Thank you for your suggestions
I was able to apply temporary root by InterceptRoot software. Unfortunately, permanent root on my device doesn't work.
Hello everyone,
I am working on a pre-rooted Android head unit. I can do "adb root" or "adb shell su" using wifi adb. So there is root access and Su binary on the device. But I can't use root applications because there is no app to grant root access. I have tried installing supersu or superuser on /system/app. I made it install the apps but they say "device not rooted" when I try to run them.
So how can I make supersu see my su binary?