Right now when I enter "adb root", it says "adbd cannot run as root in production builds".
I need adb root to be able to copy files in restricted folders to the PC. I found this https://github.com/evdenis/adb_root that supposedly will replace adbd with one that allows for elevated access, but I have not tried it because it says right at the home page "will not work with Android 11".
Does anyone know how I could get the Mi 11 to allow for "adb root"?
Related
I've been trying to figure this out all day and I'm stumped.
My stock Droid recently failed to get past the bootloader.
I'm following the directions from the CM Wiki titled "Motorola Droid: Full Update Guide" (no direct link because of my new account, sorry) and others I've found and they all seem to be exactly the same.
I've got SPRecovery installed no problem and after I run the update.zip I get a successful install message, including "enjoy your root".
The problem is in the next step where I ADB it doesn't appear I actually have root access.
I think this may be because I'm connecting to my phone from the SPRecovery menu, but I'm not sure.
This is what my cmd screen looks like when I try to follow the steps under "Installing ClockworkMod Recovery" > "Second Method (manual method)".
Code:
C:\Users\XXXX>adb shell
/ # su
su
/system/bin/sh: su: not found
I noticed that in SPRecovery there are "mount options", so I tried mounting /system and trying again and I get basically the same thing, but without the "/" and without the directory
Code:
C:\Users\XXXX>adb shell
# su
su
su: not found
I'm not Linux savvy enough to know the difference unfortunately. I've tried 3 different update.zip from 3 different sources, but all appear to be the exact same thing.
Typing "busybox" in the ADB shell kicks back all the functions so it appears to be installed.
"adb devices" kicks back "040388990E0EDITED recovery"
Any ideas would be greatly appreciated, it's getting very frustrating.
Do you have the opportunity to root your phone from the Recovery-Menu?
I have OpenRecovery (OR) and when I boot in OR i can manually chose to root my phone.
----wrong----
Quinity said:
You can also simply download the SuperUser App from the market. This roots your phone.
Click to expand...
Click to collapse
I'm about 99% certain that is false. If it was that easy, I would have heard about it. Plus the only SU app on the market states " Grant and manage Superuser rights for your phone. This app requires that you already have root.."
I have a problem..... If the title didnt say it, then ill describe my situation
When i open command windows from platform-tools folder in the SDK folder, i type in adb.exe shell. it says daemon started successfully then the line: [email protected]:/$ comes up and i type in: su. but permission denied??????????? I have superuser flashed on my phone and i have root level access on my phone though. Am i doing something wrong????
072665995 said:
I have a problem..... If the title didnt say it, then ill describe my situation
When i open command windows from platform-tools folder in the SDK folder, i type in adb.exe shell. it says daemon started successfully then the line: [email protected]:/$ comes up and i type in: su. but permission denied??????????? I have superuser flashed on my phone and i have root level access on my phone though. Am i doing something wrong????
Click to expand...
Click to collapse
If you're using CM ROM, then you also have to enable ADB root access under Developer options. The default settings is root access for apps only.
itandy said:
If you're using CM ROM, then you also have to enable ADB root access under Developer options. The default settings is root access for apps only.
Click to expand...
Click to collapse
o wow thanks man +thanks
Hello,
Having connected my PC to the G2N, I have made the following discoveries:
1. It is seemingly impossible to get root access. The "sdb root on" command comes back with Permission Denied. There is no "sudo" or "su" command anywhere on the internals. You are logged in as "developer" and I haven't worked out how to get out of there yet.
2. There is no Internet access on the device I can see. As far as I can tell, the only communication allowed is between the 'host' and the 'wearable'. Given root access I can probably work my way around this... but without it, I probably can't...
3. I have managed to install python to the device, but have not yet managed to write to screen yet.
Back to exploring...
root
You have to do that root acess
please use this thread...http://forum.xda-developers.com/showthread.php?t=2711793
I have a moto x without root, and I just follow the instruction of wakelock detector. But when I try to run adb command on the Terminal emulator, it just shows "/system/bin/sh: adb: not found". How can I run the command successfully?
lurenja said:
I have a moto x without root, and I just follow the instruction of wakelock detector. But when I try to run adb command on the Terminal emulator, it just shows "/system/bin/sh: adb: not found". How can I run the command successfully?
Click to expand...
Click to collapse
You can't use adb from a terminal on the phone... Only a convected PC. That is the problem. No way around it. Adb is for PC/Mac only.
samwathegreat said:
You can't use adb from a terminal on the phone... Only a convected PC. That is the problem. No way around it. Adb is for PC/Mac only.
Click to expand...
Click to collapse
Quote:
Originally Posted by ahikmat View Post
Wakelock detector 1.5.7, supports KitKat (rooted, also for non-rooted phones with few steps)
New permission added:
[INTERNET] - WLD does not consume any traffic, this permission is needed for adb self connection purpose
([BOOT] - this permission will be added for calculating screen on time for non-rooted kitkat phones)
Starting from kitkat we retrieve wakelock stats from "dumpsys", that is why your phone either needs to be ROOTED or you need to have adb access to your phone itself.
KitKat owners with ROOTED phones
Run WLD, allow ROOT at first run. It is preferred to check "remember it" option
KitKat owners with NON-ROOTED phones
This option takes few steps to accomplish, but this is the only way to see wakelock stats for non-rooted kitkat phones.
In android phones, by default adbd listens to USB port, we need to change it to listen tcpip for establishing adb connection.
for that we need to run "adb tcpip 5555" from PC. For Windows OS, usb drivers need to be installed. http://developer.android.com/sdk/win-usb.html
Install one of these light adb on your PC:
Windows: http://forum.xda-developers.com/show...php?p=42407269
Mac/Linux: https://code.google.com/p/adb-fastboot-install/
Enable "developer option" on your phone (it is in settings window , if you don't see it click "Build version" 7 times on "About" section)
Run "adb tcpip 5555" from command line.
Then install "Terminal emulator" on your phone and run "adb kill-server" , "adb devices" and confirm self-connection.
You can follow these slides for details: https://docs.google.com/presentation...it?usp=sharing
We are working to make single-click PC app.
If you could have better idea to optimize these steps, share it with us! Thank you!
[updated apk]
Big thanks to Sordna for helping to improve WLD and RootTools performance!
Here's the guide, I am just confused with the bold part, can anyone please explain?
lurenja said:
Quote:
Originally Posted by ahikmat View Post
Wakelock detector 1.5.7, supports KitKat (rooted, also for non-rooted phones with few steps)
New permission added:
[INTERNET] - WLD does not consume any traffic, this permission is needed for adb self connection purpose
([BOOT] - this permission will be added for calculating screen on time for non-rooted kitkat phones)
Starting from kitkat we retrieve wakelock stats from "dumpsys", that is why your phone either needs to be ROOTED or you need to have adb access to your phone itself.
KitKat owners with ROOTED phones
Run WLD, allow ROOT at first run. It is preferred to check "remember it" option
KitKat owners with NON-ROOTED phones
This option takes few steps to accomplish, but this is the only way to see wakelock stats for non-rooted kitkat phones.
In android phones, by default adbd listens to USB port, we need to change it to listen tcpip for establishing adb connection.
for that we need to run "adb tcpip 5555" from PC. For Windows OS, usb drivers need to be installed. http://developer.android.com/sdk/win-usb.html
Install one of these light adb on your PC:
Windows: http://forum.xda-developers.com/show...php?p=42407269
Mac/Linux: https://code.google.com/p/adb-fastboot-install/
Enable "developer option" on your phone (it is in settings window , if you don't see it click "Build version" 7 times on "About" section)
Run "adb tcpip 5555" from command line.
Then install "Terminal emulator" on your phone and run "adb kill-server" , "adb devices" and confirm self-connection.
You can follow these slides for details: https://docs.google.com/presentation...it?usp=sharing
We are working to make single-click PC app.
If you could have better idea to optimize these steps, share it with us! Thank you!
[updated apk]
Big thanks to Sordna for helping to improve WLD and RootTools performance!
Here's the guide, I am just confused with the bold part, can anyone please explain?
Click to expand...
Click to collapse
Yeah....did you install adbd? That is the android adb daemon.....
BEFORE you can use adb on an android device (It was never meant to be run from anything but a PC), you must FIRST *install adbd*, AND *run "adb tcpip 5555" from a ***PC****
This enables you to use the adbd daemon. Don't have access to a PC? No can do...
6719
samwathegreat said:
Yeah....did you install adbd? That is the android adb daemon.....
BEFORE you can use adb on an android device (It was never meant to be run from anything but a PC), you must FIRST *install adbd*, AND *run "adb tcpip 5555" from a ***PC****
This enables you to use the adbd daemon. Don't have access to a PC? No can do...
Click to expand...
Click to collapse
Really thanks for the reply, I didn't install the *adbd*, and I find someone said to run "adb remount" from a PC to install the *adbd*, but when I run the command, it shows "remount failed: Permission denied". Is this the right way? or how can I install the *adbd*?
lurenja said:
Really thanks for the reply, I didn't install the *adbd*, and I find someone said to run "adb remount" from a PC to install the *adbd*, but when I run the command, it shows "remount failed: Permission denied". Is this the right way? or how can I install the *adbd*?
Click to expand...
Click to collapse
I suggest asking the person who wrote the guide that you quoted. Good Luck!
Remember to always hit the thanks button under any post where someone helped you, or that provided useful information. :good:
Problem: I have an Aishon A19 tablet, which it is very hard to find information about. It is an RK3288 tablet running Android 5.1.1.
It is not really rooted in the normal sense. However, "adb root" works; I can get a root shell and mount /system as writeable, I can push any app I want to the device, etc.
Things that will not work:
-- I tried to put on a /system/xbin/su (from SuperSU 2.76), with mode 6755 (rwsr-sr-x) and it didn't work. I also made symbolic links to /system/bin/su and /system/xbin/daemonsu. Running it from a non-root shell in adb prints a 1 and doesn't give me root. Running it from a non-root shell on the tablet does the same thing. Running it from a root shell gives me no error, but that obviously isn't much use.
-- Running SuperSU as an app gives me the error message about "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5....." I have no idea if it actually can't see the ./system/xbin/su or if the error message just isn't that good.
-- Trying to use "adb reboot bootloader" or getting into the bootloader using buttons doesn't work. It reboots the tablet into a blank screen, with the same vendor ID and a new product ID; however, "fastboot devices" shows nothing. This happens both under Windows and Linux, and even when run as root under Linux (thus not having to worry about udev rules). This means that I cannot install TWRP unless someone can explain to me how to install TWRP without using the bootloader.
I *can* use "adb reboot recovery" and get into the recovery menu. And as I mentioned, I can get root access to the tablet and a root shell using "adb root", and push any file I want to it.
Is it possible to use this root shell and/or recovery to install SuperSU somehow, even if I have to just copy files one at a time?
Edit: Moderators., you can lock this. Someone had the same problem in http://forum.xda-developers.com/apps/supersu/how-to-manually-update-su-supersu-file-t3238991 and I was able to folloow that, manually running the commands in update-binary.