I'm in a recovery boot loop and need to be able to access adb from recovery. I'm running ubuntu and adb devices while in recovery shows ?????????????? no permissions. Can somebody please help me. I think it may be as simple as a rule change somewhere but thats just a guess. Thanks guys.
newellj79 said:
I'm in a recovery boot loop and need to be able to access adb from recovery. I'm running ubuntu and adb devices while in recovery shows ?????????????? no permissions. Can somebody please help me. I think it may be as simple as a rule change somewhere but thats just a guess. Thanks guys.
Click to expand...
Click to collapse
Try this:
sudo su
adb start-server (preceeded by adb kill-server if adb already running). NOTE: You may have to change the path to adb since you are using Superuser to start the server, it may not be in your .bashrc.
exit
Then, run adb devices and see what you get. Happened to me with the EVO 3D and the above worked for me. Starting the adb server with SU permissions works.
pinky059 said:
Try this:
sudo su
adb start-server (preceeded by adb kill-server if adb already running). NOTE: You may have to change the path to adb since you are using Superuser to start the server, it may not be in your .bashrc.
exit
Then, run adb devices and see what you get. Happened to me with the EVO 3D and the above worked for me. Starting the adb server with SU permissions works.
Click to expand...
Click to collapse
Thanks. That got it,
Sent from my T-Mobile myTouch 3G using XDA
The file to check would an udev rules file. See where ubuntu keeps it.
Sent from my i9250
Related
ok so on most roms this happens. i need a SU request but my phone freezes obn a black screen and on the top in gray it says SU request. i wait paciently and maybe 1-2 mins later is asks to FC because its not responding. is there a fix or what am i doing wrong. usb debugging is on and so is install nonmarket apps idk wtf im doing wrong or if somthing is just not working. any input??
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Marisa said:
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Click to expand...
Click to collapse
yes same thing happens to me
plug in your phone
goto your android sdk tools
and input adb shell
now go back to your phone and try it while still plugged
thats what i have been doing...
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
WalkingTaco said:
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
Click to expand...
Click to collapse
Are you getting the same crshes and things, but when you do the adb shell # pops up instead of $?
whenever i do adb shell I get #, so that means SU is already activated, but it's actually not on my phone, so i have no idea what's going on and no one seems to know how to fix it.
no. my Su permissions always force close after a minute of black screen. there is a fix posted above but my nerd level is not high enough to.infer the rest
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know the exact command prompt setup, I'm running linux. However, when you originally rooted your phone you used the Android SDK correct?
With your phone plugged in, and USB Debugging enabled on your phone (Settings -> Applications -> Development -> USB Debugging) Open command prompt and get to the tools directory you used during rooting, I don't know where you installed it, so I cannot guide you through that part. If you used Ivan's guide http://forum.xda-developers.com/showthread.php?t=647707 it's probably best to refresh yourself there.
Once you've found your SDK /tools/ in command prompt, it should be as easy as running the code I mentioned earlier
Code:
adb shell
$su
in the command prompt.
The superuser prompt should show up on your phone, tell it to allow it and it should work without fail until you flash a new ROM that has the bug.
thanks very much. I used Ivans guide. I rooted it yesterday when o got my replacement from Verizon in store. I had been using the 2.1 leak on my old one and complained in store for thirty seconds. they didn't even look at it gave me a replacement in ten minutes
Sent from my Eris using the XDA mobile application powered by Tapatalk
Rock out thanks for the Super Help
Okay, so I'm a bit an ADB noob here. I've been trying to push my avatar apk into /system/apps for awhile here but every time i do so, it fails with this error:
/bin/sh: adb: not found
did I set it up wrong somehow?
Oniyuri said:
Okay, so I'm a bit an ADB noob here. I've been trying to push my avatar apk into /system/apps for awhile here but every time i do so, it fails with this error:
/bin/sh: adb: not found
did I set it up wrong somehow?
Click to expand...
Click to collapse
Make sure you are running the adb command from the directory where your adb is located. There is tons of info on this site and google that will give you everything you need to know about using adb. Try typing the error message into search
yeah, i know to change directories already. this error is happening after i'm in the directory.
i basically start out like this:
cd C:\android-sdk-windows\tools
and after that, switch to adb shell
C:\android-sdk-windows\tools> adb shell
i get some characters and then try for a push
"adb push C:\users\myuser\downloads/avatar.apk /system/app
after that, boom! error.
bump
+10char
Oniyuri said:
yeah, i know to change directories already. this error is happening after i'm in the directory.
i basically start out like this:
cd C:\android-sdk-windows\tools
and after that, switch to adb shell
C:\android-sdk-windows\tools> adb shell
i get some characters and then try for a push
"adb push C:\users\myuser\downloads/avatar.apk /system/app
after that, boom! error.
Click to expand...
Click to collapse
You really should be using either the search bar here or google because this information is in abundance. "adb push" should not be run from inside the shell. adb is not recognized by the shell. Do the same thing that you listed above minus the step where you typed "adb shell"
********
Sent from my Paragon RC3 Captivate using the XDA app
Try 'cd C:\android-sdk-windows\platform-tools', not C:\android-sdk-windows\tools.
Better yet, just add that to the environment variable, PATH.
hth
Hello, I am using a Droid Razr Maxx CDMA (XT912). I have Android version 4.2.2. I am using Cyanogen mod 10.1.
I am having problems opening ADB. When I turn my USB Debugging on under my dev. options, connect my device in PTP mode using the terminal emulator commands:
su
setprop persist.sys.usb.config mass_storage
reboot
I run the ADB program and a window comes up for a brief moment then closes. I am unable to open ADB. I have Java.
Thank You!
ADB Troubles Cont'd.
nathanielhall929 said:
Hello, I am using a Droid Razr Maxx CDMA (XT912). I have Android version 4.2.2. I am using Cyanogen mod 10.1.
I am having problems opening ADB. When I turn my USB Debugging on under my dev. options, connect my device in PTP mode using the terminal emulator commands:
su
setprop persist.sys.usb.config mass_storage
reboot
I run the ADB program and a window comes up for a brief moment then closes. I am unable to open ADB. I have Java.
Thank You!
Click to expand...
Click to collapse
Did adb kill-server and adb start-server several times in cmd with no avail. The device serial number shows up under adb devices, but ADB Program will still not open. I've tried to open ADB up in cmd also.
I also tried typing in the terminal emulator:
su
setprop persist.sys.usb.config mass_storage, adb
reboot
Thanks again!
Can someone please help me with this?
I even tried installing the Universal naked drivers and that wouldn't go through.
nathanielhall929 said:
I even tried installing the Universal naked drivers and that wouldn't go through.
Click to expand...
Click to collapse
I copied your command and pasted here. setprop persist.sys.usb.config mass_storage, adb
And what I find is posted here. setprop persist.sys.usb.config mass_storage,adb
And reboot afterwards.
Notice the extra space in your command before adb?
I found this command structure several locations and only one that reports failed has the space.
For ICS it also shows adb shell as in
adb shell setprop persist.sys.usb.config mass_storage,adb
adb reboot
I hope this helps.
Tried it without the space and still not working
tobdaryl said:
I copied your command and pasted here. setprop persist.sys.usb.config mass_storage, adb
And what I find is posted here. setprop persist.sys.usb.config mass_storage,adb
And reboot afterwards.
Notice the extra space in your command before adb?
I found this command structure several locations and only one that reports failed has the space.
For ICS it also shows adb shell as in
adb shell setprop persist.sys.usb.config mass_storage,adb
adb reboot
I hope this helps.
Click to expand...
Click to collapse
I just tried it without the space, rebooted, and nothing
I don't get it
nathanielhall929 said:
I just tried it without the space, rebooted, and nothing
Click to expand...
Click to collapse
The ADB Program just won't open up on this computer. It opens for a second spewing command info then closes. Is it my Java program?
nathanielhall929 said:
I just tried it without the space, rebooted, and nothing
Click to expand...
Click to collapse
Are you getting an error?
This is the other method I see being used but I'll break the command as I believe it should be.
adb shell
su
setprop persist.sys.usb.config mtp,adb
exit
adb reboot
My problem is I know nothing about your unit and I don't know whether it should be mtp or mass_storage. I see people failing with mass_storage are being told to use mtp.
in terminal it shows
su
setprop persist.sys.usb.config mass_storage,adb
reboot
or
su
setprop persist.sys.usb.config mtp,adb
reboot
To retrieve this info I used the top search that says Search All Forums and typed in your command then hit search. You may need to do the same and only go to the threads that suit your situation.
---------- Post added at 12:38 AM ---------- Previous post was at 12:26 AM ----------
nathanielhall929 said:
The ADB Program just won't open up on this computer. It opens for a second spewing command info then closes. Is it my Java program?
Click to expand...
Click to collapse
Are you opening cmd and going to the directory with adb and issue your commands or are you trying to click on adb and use it that way?
I'm trying to run it in cmd
I've been trying to fix this for two days now. I'll be back tomorrow.
Figured out
Ok, now I feel like I'm a real noob. I just realized that I was thinking too hard about all of this. Adb doesn't open up in a new window as a regular program would. I thought it did. Oops. Maybe I should have been more thourough in my research. I should have realized that I already opened adb by using the cmd prompt.
This is why my device was recognized under adb devices.
Maybe not...
I still can't figure out how to get this:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/attachment/path-adb/
window to come up.
This is what I'm tring to do
nathanielhall929 said:
I still can't figure out how to get this:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/attachment/path-adb/
window to come up.
Click to expand...
Click to collapse
This is what I am trying to do:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/
Figured out finally!!!
nathanielhall929 said:
This is what I am trying to do:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/
Click to expand...
Click to collapse
I finally figured this out!!!
I want to thank tobdaryl for his time.
Thank you for your time tobdaryl
nathanielhall929 said:
I finally figured this out!!!
I want to thank tobdaryl for his time.
Thank you for your time tobdaryl
Click to expand...
Click to collapse
You are welcome.
Can you help me?
Can you check out this thread.. Maybe you can help me.
http://forum.xda-developers.com/showthread.php?t=2260208
Okay... So Here Is Whats Up... The Digitizer On My Lg Optimus L9 Is Broken, Cant Touch The Screen Or Anything... But I Would Still Like To Use My Phone, I Can Can View My Screen But Thats All I Can Do,I Wish To Use The Keyboard And Mouse To Control My Screen,I Know This Is Possible Apperantly The Only Way To Do This Is To Access The ADB Shell, Okay,But What The Problem? Well When I Attempt To Gain Access To The ADB Shell... Super SU Gets In The Way, I Cant Grant Access To The ADB Shell Because I Cant Touch The Screen Do To The Broken Digitizer, And I Cant Click It When It Appears On The Display Because I Dont Have Super SU Permision To Use The Controlls Do To Being Denied Access Of The ADB Shell, If You Under Stand My Cicumstances Please Assist Me In Any Way, The Only Stipulation, No Factory Reset! Please And Thank You!
savagemessiah97 said:
Okay... So Here Is Whats Up... The Digitizer On My Lg Optimus L9 Is Broken, Cant Touch The Screen Or Anything... But I Would Still Like To Use My Phone, I Can Can View My Screen But Thats All I Can Do,I Wish To Use The Keyboard And Mouse To Control My Screen,I Know This Is Possible Apperantly The Only Way To Do This Is To Access The ADB Shell, Okay,But What The Problem? Well When I Attempt To Gain Access To The ADB Shell... Super SU Gets In The Way, I Cant Grant Access To The ADB Shell Because I Cant Touch The Screen Do To The Broken Digitizer, And I Cant Click It When It Appears On The Display Because I Dont Have Super SU Permision To Use The Controlls Do To Being Denied Access Of The ADB Shell, If You Under Stand My Cicumstances Please Assist Me In Any Way, The Only Stipulation, No Factory Reset! Please And Thank You!
Click to expand...
Click to collapse
You should still be able to access adb shell at the shell level, what is likely happening is that you are dropping into a root shell and this is causing SuperSU to prompt if you want to allow adb shell to have root access. What are the exact steps you are taking when you go to use adb shell?
shimp208 said:
You should still be able to access adb shell at the shell level, what is likely happening is that you are dropping into a root shell and this is causing SuperSU to prompt if you want to allow adb shell to have root access. What are the exact steps you are taking when you go to use adb shell?
Click to expand...
Click to collapse
I Use Android Screencast Plus Android SDK, Then I Use Command Prompt
.Adb Shell
.Su
At That Point Super Su Is Prompted
savagemessiah97 said:
I Use Android Screencast Plus Android SDK, Then I Use Command Prompt
.Adb Shell
.Su
At That Point Super Su Is Prompted
Click to expand...
Click to collapse
I would recommend try starting adb shell (adb shell command) and not dropping into a root shell then skip the su command. So just do
Code:
adb shell
To start adb shell, and then skip the su command.
shimp208 said:
I would recommend try starting adb shell (adb shell command) and not dropping into a root shell then skip the su command. So just do
Code:
adb shell
To start adb shell, and then skip the su command.
Click to expand...
Click to collapse
If I Skip su The cmd Says Not Permited
Code:
•adb shell
•su
•chmod 777 /data/dalvik-cache
•cd /data/dalvik-cache
•chmod 777 ./
This Is My Attempt, Is There An Alternative
savagemessiah97 said:
If I Skip su The cmd Says Not Permited
Code:
•adb shell
•su
•chmod 777 /data/dalvik-cache
•cd /data/dalvik-cache
•chmod 777 ./
This Is My Attempt, Is There An Alternative
Click to expand...
Click to collapse
Trying using adb shell from the command line, instead of Android Screencast. Also what are you trying to do with the device extract your personnel information?
Any progress with this? I'm in the same situation
Hi
First of all, sorry for my bad english.
It has been several hours that i'm trying to find a solution to my problem.
I want to wake my nvidia shield via adb command throught network.
I installed android tools on my raspberry pi, and when i connect to it via command line everything work, i can wake up the Shield.
But when i put my command line in a bash script
Code:
#!/bin/bash
adb kill-server
adb start-server
adb connect 192.168.1.38:5555
adb shell input keyevent KEYCODE_WAKEUP
adb kill-server
i have this error :
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I dont know why, when i am execute the command line in a bash script it can't find the rsa key, who is there and should be used.
Any ideas
Thanks in advance.
darkouz said:
Hi
First of all, sorry for my bad english.
It has been several hours that i'm trying to find a solution to my problem.
I want to wake my nvidia shield via adb command throught network.
I installed android tools on my raspberry pi, and when i connect to it via command line everything work, i can wake up the Shield.
But when i put my command line in a bash script
Code:
#!/bin/bash
adb kill-server
adb start-server
adb connect 192.168.1.38:5555
adb shell input keyevent KEYCODE_WAKEUP
adb kill-server
i have this error :
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I dont know why, when i am execute the command line in a bash script it can't find the rsa key, who is there and should be used.
Any ideas
Thanks in advance.
Click to expand...
Click to collapse
Normally on Windows the first time you turn on usb debugging it will pop up and ask you to accept the adb key. This is what is preventing you, I haven't had to resolve this in Linux, but essentially you need to go to C:\\Users\You\.android\ (in Windows, path will be different in Linux) and copy the file adbkey. Now you need to move it to data/misc/adb/
This will most likely require root or TWRP. Good luck, my friend.
Sent from my KYOCERA-C6745 using Tapatalk
Hi
Thanks for your quick response.
I couldn't make the connection via USB my adb tells me that there is no emulated device. But it work with network And yeah the first time I made the connection, the authorization pop up appeared on my shield. I checked, always authorized this device.
I have the key in /root/.android on my raspberry pi
I don't think I have the access to the /data/ folder in my shield.
But what I don't understand is why when I execute the command in a terminal like that, it work and when it's from the bash script it won't work anymore
darkouz said:
Hi
Thanks for your quick response.
I couldn't make the connection via USB my adb tells me that there is no emulated device. But it work with network And yeah the first time I made the connection, the authorization pop up appeared on my shield. I checked, always authorized this device.
I have the key in /root/.android on my raspberry pi
I don't think I have the access to the /data/ folder in my shield.
But what I don't understand is why when I execute the command in a terminal like that, it work and when it's from the bash script it won't work anymore
Click to expand...
Click to collapse
Option B would be to dump your boot.img and use Assayed's kitchen to add insecure kernel and adb direct root, then the adbkey doesn't need to be on the device.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Option B would be to dump your boot.img and use Assayed's kitchen to add insecure kernel and adb direct root, then the adbkey doesn't need to be on the device.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Yeah as you said in your previous post, i think the solution is to root the nvidia shield cause the rsa key doesny copy itself on the device.
But would you able to explain to me why if i execute those command individually in the terminal it works.
But if i put them all in a bash script that i execute it doesnt work anymore, what's the difference between those two procedure ?
darkouz said:
Yeah as you said in your previous post, i think the solution is to root the nvidia shield cause the rsa key doesny copy itself on the device.
But would you able to explain to me why if i execute those command individually in the terminal it works.
But if i put them all in a bash script that i execute it doesnt work anymore, what's the difference between those two procedure ?
Click to expand...
Click to collapse
How are you executing the script? There's some (hopefully) helpful info here.
https://community.spiceworks.com/topic/433656-command-not-running-in-batch-but-will-run-in-cmd
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
How are you executing the script? There's some (hopefully) helpful info here.
https://community.spiceworks.com/topic/433656-command-not-running-in-batch-but-will-run-in-cmd
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
i m doing : sh script.sh
i m gonna read that, thanks
I found the solution.
I don't really understand why, but adding
Code:
sleep 1
before
Code:
adb shell input keyevent KEYCODE_BACK
resolved the problem, maybe the script execution was to fast for adb to adjust, dont know.
All i know is, that works
darkouz said:
I found the solution.
I don't really understand why, but adding
Code:
sleep 1
before
Code:
adb shell input keyevent KEYCODE_BACK
resolved the problem, maybe the script execution was to fast for adb to adjust, dont know.
All i know is, that works
Click to expand...
Click to collapse
Glad you got it.
Sent from my KYOCERA-C6745 using Tapatalk
sudo rm -rf /home/(username)/.android
that worked with my kde neon machine