Samsung Vibrant uninstall (permission denied) - General Questions and Answers

Hi All,
So I've rooted my phone and I'm trying to uninstall the silly bloatware apps.
in cmd
adb uninstall /system/app/Telenav.apk
Failure
adb shell
su
rm /system/app/Telenav.apk
Permission Denied
...any clues as to why I am being denied access?
Thanks,
West
EDIT:
When I put in
adb root
adbd cannot run as root in production devices
is that normal?

Fixed. Busybox not installed.
-West

Related

[Q] Odd permissions issue with rooted optimus

How come this works:
Code:
[[email protected]:~/android-dev/optimus_m]$ adb shell su -c id
uid=0(root) gid=0(root)
But this:
Code:
[[email protected]:~/android-dev/optimus_m]$ adb shell su -c pm disable com.seven.Z7
Permission denied
Fails?
In the first example superuser prompts for permission and then allows the command, in the second it doesn't prompt and just instantly fails. There are no related saved settings in superuser.
If there isn't a way to fix this, is there another way to execute commands on the phone as root from a script on the host computer?
Nothing?
Looks like I'm on my own. :\

[Q] Problem with adb (permission denited)

I have a Problem with my adb:
Code:
c:\android\platform-tools> adb shell
$
But why there this a "$" and not a "#"?
and when i type for example:
c:\android\platform-tools>adb shell
$ su
su
su: permission denied
$
Click to expand...
Click to collapse
can some one help me??
su permission denied
I just bumped into the same problem with a unlocked Nexus One. Can anyone help? How do you get the permission to remove files?

[Q] Not prompted for superuser ??

On 4.1.1 completely stock. I used OTA Root Keeper to retain root successfully.
TiBu and Root Explorer were already running as root and still get root access.
Any new apps never prompt for superuser authority??
Root Checker Pro says I'm rooted,
OTA Root Keeper says:
x Superuser app installed
x Device rooted
Root permission granted
x /system supports root protection
x Protected su copy available
I tried to install SuperSU but that also failed, it doesn't
prompt for superuser rights so it can't write the su
binary.
I'm confused, what changed? how do I fix it?
I can't go into details now but your su binary is the problem. Do not uninstall anything that still has root as you will lose it. I can go into more details when I get to the office later this morning.
Sent from my SCH-I510 using xda app-developers app
su binary issues?
Reilly1812 said:
I can't go into details now but your su binary is the problem. Do not uninstall anything that still has root as you will lose it. I can go into more details when I get to the office later this morning.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I do have root access from adb I should be able to push a new binary
then set its perms, from adb shell.
Where would I find the binary I need?
I was using Superuser.apk and its binary.
Shouldn't OTA rootkeeper have saved a copy?
it says I have root, and it has copy somewhere.
--> Root Checker output
Congratulations! You have root access!
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-01-29 02:14 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your ASUS Transformer Pad TF300T device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market - http://goo.gl/NcnHn
I had exactly the same problem when I first upgraded from ICS to JB. Thought I had root until I decided to try AdAway. I uninstalled AdFree and attempted to install AdAway. The install failed stating that I did not have root. Of course I did since AdFree worked, ES File Explorer worked, Terminal Emulator worked, etc. Searched and searched and found discussion which highlighted the su binary to be the issue. Attempted to use the app to update the binary and it failed. I believe (and watch how fast I get corrected!) that the implementation of multiuser support in android is what requires the new versions of superuser and the binary. I documented the permissions of the existing su in /system/bin/ and ensured that I did not have another in /system/xbin/. Using ES File Explorer I copied and pasted on top of the existing su in /system/bin, checking to ensure permissions were good. You should then be able to download the latest and greatest binary using the app. This was all done with superuser. I have not worked with SuperSU. I crossed my fingers and restarted the tablet. I was good to go and have full root.
Please note that others have come back and stated that it did not work for them. I can tell you what worked for me and why I believe it did. I will add the link to the post discussing this problem as soon as I find it again.
Check out this thread which worked using adb.
http://forum.xda-developers.com/showthread.php?t=2183105
[Solved] that seems to have worked
downloaded updated su binary
adb pushed to /sdcard
adb shell
Code:
/system/bin/su
mount -o remount,rw /system
mv /system/su /system/su.bak
cat /sdcard/su > /system/bin/su
chmod 6755 /system/bin/su
exit
adb reboot

Imposible to uninstall APPs with adb

I need help, I want to uninstall some applications from my phone with adb, but typing the command: ". \ Adb shell pm uninstall --user 0" app_to_remove ".
I get the error: "Failed to remove package from user owner's system."
I follow the commands correctly from beginning to end, but it does not allow me to uninstall applications, my phone is an "Alcatel 1 5033e
.
1. The command used is unusual. It should be adb uninstall <PKG-NAME>
2. Apps housed in /system partititon can only get uninstalled by ROOT user and if partition /system is mounted as RW ( means: Read / Wrire access )
jwoegerbauer said:
1. The command used is unusual. It should be adb uninstall <PKG-NAME>
2. Apps housed in /system partititon can only get uninstalled by ROOT user and if partition /system is mounted as RW ( means: Read / Wrire access )
Click to expand...
Click to collapse
how can you how can I get root access from adb?
Install a temporary ROOT.
Example
Code:
adb devices
adb push <LOCATION-OF-SU-BINARAY-ON-COMPUTER> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
adb shell "/data/local/tmp/su -c '<SHELL-COMMAND-TO-GET-RUN-HERE>'"

Permission denied [cat /proc/partitions]

Dear all,
The Redmi S2 is
- rooted;
- bootloader unlocked;
- oem unlocked;
- on PTP default (Photo transfer).
In ADB debugging,
C:\platform-tools>adb shell
ysl:/ $ cat /proc/partitions
cat: /proc/partitions: Permission denied
How to solve it?
Thanks in advance.
Regards,
Run cmd in Android shell's root mode
Code:
adb shell 'su -c "cat /proc/partitions"'
xXx yYy said:
Run cmd in Android shell's root mode
Code:
adb shell 'su -c "cat /proc/partitions"'
Click to expand...
Click to collapse
Thanks for the reply.
After "adb root", it prompts "adbd cannot run as root in production builds".
And installation of an app "adbd insecure" as below, it produced the same result.
[2014.11.10][ROOT] adbd Insecure v2.00
adbd Insecure lets you run adbd in root mode if your device is rooted. (Note that if you are running a custom kernel, it is likely that it already implements this functionality) If you are running a stock (made by the phone manufacturer) kernel...
forum.xda-developers.com
But "adb shell" apparently works.
On production builds the ADBD server on phone doesn't use root permission. You can't change this.
Simply try what suggested by me.
xXx yYy said:
On production builds the ADBD server on phone doesn't use root permission. You can't change this.
Simply try what suggested by me.
Click to expand...
Click to collapse
I just tried your code in CMD. It returns as follows:
C:\platform-tools>adb shell 'su -c "cat /proc/partitions"'
/system/bin/sh: su -c cat /proc/partitions: not found
That's a complete other issue.
Under "adb shell su", after granting the super privilege, AND then "cat /proc/partitions", I was able to view the partitions.
Thanks.

Categories

Resources