How to adb shell as a root without rooting a android phone (Honor View 10) - General Questions and Answers

Hi Developers,
I want to set/get the GPU and DDR frequencies using devfreq object by changing governor.
i need to run the following command in adb shell.
HWBKL:/ $ echo performance > /sys/class/devfreq/ddrfreq/governor
But i am not able to access below things.
HWBKL:/sys/class/devfreq/ddrfreq $ ls
ls: ./trans_stat: Permission denied
ls: ./target_freq: Permission denied
ls: ./available_governors: Permission denied
ls: ./cur_freq: Permission denied
ls: ./max_freq: Permission denied
ls: ./min_freq: Permission denied
ls: ./uevent: Permission denied
ls: ./ddr_bandwidth: Permission denied
ls: ./bd_utilization: Permission denied
ls: ./available_frequencies: Permission denied
ls: ./governor: Permission denied
ls: ./polling_interval: Permission denied
device power subsystem
-> i tried $adb root
adbd cannot run as root in production builds.
->i tried HWBKL:/ $ su
/system/bin/sh: su: not found
Please let me know is there any possibility.
Thanks

ashokkatha said:
Hi Developers,
I want to set/get the GPU and DDR frequencies using devfreq object by changing governor.
i need to run the following command in adb shell.
HWBKL:/ $ echo performance > /sys/class/devfreq/ddrfreq/governor
But i am not able to access below things.
HWBKL:/sys/class/devfreq/ddrfreq $ ls
ls: ./trans_stat: Permission denied
ls: ./target_freq: Permission denied
ls: ./available_governors: Permission denied
ls: ./cur_freq: Permission denied
ls: ./max_freq: Permission denied
ls: ./min_freq: Permission denied
ls: ./uevent: Permission denied
ls: ./ddr_bandwidth: Permission denied
ls: ./bd_utilization: Permission denied
ls: ./available_frequencies: Permission denied
ls: ./governor: Permission denied
ls: ./polling_interval: Permission denied
device power subsystem
-> i tried $adb root
adbd cannot run as root in production builds.
->i tried HWBKL:/ $ su
/system/bin/sh: su: not found
Please let me know is there any possibility.
Thanks
Click to expand...
Click to collapse
There is no way you can run adb shell as root without rooting. Rooting your phone installs the su binary in your phone. That is needed to run root for any apps.

mohhaxs said:
There is no way you can run adb shell as root without rooting. Rooting your phone installs the su binary in your phone. That is needed to run root for any apps.
Click to expand...
Click to collapse
Thank you mohhaxs.
i didn't tried rooting a phone before. Do you know any rooting procedure for Honor View 10 (BKL-L09)

Related

[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?

x10 mini pro rooted.sh, permission error

Hallo,
i tryed to get root permission on my x10 mini pro using the rooted.sh script.
distro ubuntu 10.04
this is the output...
I also tryed to run the script with sudo user... but it's the same...
any help?
/ROOTer-Linux-v3$ sh ROOTer.sh
ROOTer for Linux by react2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
Remember by using this you understand the risks involved with doing so.
Is your phone already rooted? (y/n)n
Do you wish to continue with the ROOTing? (y/n)y
Is USB Debugging enabled on your phone? (y/n)y
Great lets start the process.
Starting ADB server.
ROOTer.sh: 49: ./adb/adb: Permission denied
Wait for phone to be ready.
ROOTer.sh: 53: ./adb/adb: Permission denied
Push the exploit to the phone.
ROOTer.sh: 57: ./adb/adb: Permission denied
ROOTer.sh: 58: ./adb/adb: Permission denied
Run the exploit. There may be a delay whilst this is happening.
ROOTer.sh: 62: ./adb/adb: Permission denied
ROOTer.sh: 63: ./adb/adb: Permission denied
Mount system as R/W.
ROOTer.sh: 67: ./adb/adb: Permission denied
Push su to phone.
ROOTer.sh: 71: ./adb/adb: Permission denied
Push Superuser.apk to phone.
ROOTer.sh: 73: ./adb/adb: Permission denied
Push busybox to phone.
ROOTer.sh: 75: ./adb/adb: Permission denied
Setting permissions for su.
ROOTer.sh: 79: ./adb/adb: Permission denied
Setting permissions for busybox.
ROOTer.sh: 81: ./adb/adb: Permission denied
Reboot phone.
ROOTer.sh: 85: ./adb/adb: Permission denied
Stopping ADB Server.
ROOTer.sh: 89: ./adb/adb: Permission denied
Your phone should now be ROOTed.

[Q] Root Issues

Hi,
I'm having issues achieving root on my device.
Here is the output of RootCheckerPro:
Superuser Application Status:
Superuser application - version 3.0.7 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rw-rw-rw- root root 22364 2012-04-02 18:53 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 22228 2012-04-02 19:20 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 /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:
SU binary not found or not operating properly
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: root user - ro.secure=0
If anyone has any suggestions, I would appreciate it.
Thanks!
PS: If this thread is not in the right place, feel free to move it.

supersu help

Can someone please walk me through updating supersu? I belive this is the problem I am having preventing me from full root access on my galaxy s4 mk2 build.
This is what shows on root checker pro.
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 46596 2014-02-19 15:22 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 113032 2014-02-22 14:46 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
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:
SU binary not found or not operating properly
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 SCH-I545 device by Root Checker Pro version 1.3.5
When I open supersu after running the script it says to update binaries but no matter how many times I reboot and try again they won't update.
Thanks for any help, Chris

unable to pull files from Android 10

Long story short, I tried to install Company Portal app and failed, which left my phone on 'pixel is starting' screen. I'm fine with resetting the phone, but have some files I would like to transfer first.
The phone is on Android 10 (QQ1A.200105.002), unrooted but debugged. I ran adb on my pc, adb shell ls returns the following:
Code:
ls: ./init.zygote64_32.rc: Permission denied
ls: ./init.rc: Permission denied
ls: ./init.usb.rc: Permission denied
ls: ./ueventd.rc: Permission denied
ls: ./init.zygote32.rc: Permission denied
ls: ./init: Permission denied
ls: ./cache: Permission denied
ls: ./init.environ.rc: Permission denied
ls: ./postinstall: Permission denied
ls: ./init.usb.configfs.rc: Permission denied
ls: ./metadata: Permission denied
acct
apex
bin
bugreports
charger
config
d
data
debug_ramdisk
default.prop
dev
dsp
etc
lost+found
mnt
odm
oem
persist
proc
product
product_services
res
sbin
sdcard
storage
sys
system
vendor
But when I run pull sdcard, which is listed above, it shows that the file does not exist.
Code:
sdcard: No such file or directory
I turned on 'file transfer' in 'USB preference', which still doesn't help.
Any suggestions would be appreciated. I need to get the files off the phone before I could reset and use it again.
I had the same problem when I was un-able to boot.
I researched every possible reason that I would get that "sdcard: No such file..." error, but I wasn't able to fix it. Despite having the bootloader unlocked and being rooted, I still had to wipe it.
You cant pull anything unless phone is decrypted. Which happens after you unlock lockscreen after boot.

Categories

Resources