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
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
Ive pushed all kinds of other stuff, I did do the add system enviromental variable to XP so this could be my issue, though like i said its worked for other things ...
ERROR I GET>
CANNOT STAT
adb push stock-hc-flyer-hboot_1.11.0006.nb0 / && adb shell dd if=/stock-hc-flyer-hboot_1.11.0006.nb0 of=/dev/block/mmcblk0p18
NO SUCH FILE OR DIRECTORY
a thourough explanation or a cut and pastable pointing my adb to this file, its in the root, the variable is to the root C also, so....
PLEASE HELP, to get me past this 10+hours of hell
May be a connection between your computer and phone issue. I have this error when I wanted to root my nexus s. Try different driver for your flyer.
Accidentally sent from my Google Nexus S using XDA Premium
Make sure the adb works via "adb devices" and "adb shell". If it does not work you can try "adb kill-server" first.
I don't think you can write (push) to "/" without "adb remount". Not sure if it is a good idea to write to root directory.
Alternatively, you can use the storage in /data/local/tmp, it is always writable.
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
Hi.
It's not first time for me to root or flash rom or sth like that.
It's also not the first time for me to use the adb.exe or the android sdk.
Today, I installed the sdk and the java and everything I need. Everything works great until I tried to use the adb.exe.
When I click on adb.exe, it pop out for a second and then disappear. I can see a lot of commands within that second.
Then I try to use cmd and the commands are the following:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
These commands are obviously the command: [abd help]
Why the hack would they show out instead of running the normal adb.exe???
Also, any other adb command turns to the same things above( result of the [abd help] command)
Need help, can't use any adb functions..........................
What command are you typing? What guide are you following? This is all very vague!
Kangburra said:
What command are you typing? What guide are you following? This is all very vague!
Click to expand...
Click to collapse
First, thanks for replying me.
I didn't really follow any guide as i know how it works...
I installed the driver >java pack>sdk and I just run C:\SDK\platform-tools\adb.exe
NokiaBigS said:
First, thanks for replying me.
I didn't really follow any guide as i know how it works...
I installed the driver >java pack>sdk and I just run C:\SDK\platform-tools\adb.exe
Click to expand...
Click to collapse
What do you mean run adb.exe?
adb.exe doesn't run, its a service.
you should set it up your path on your computer to make life easier.
Open a command prompt (search for cmd in start menu) and type "set PATH=%PATH%;C:\sdk\whateverthepathis"
Then once that is set you can just type adb into command without the need for writing the whole path every time.
Like C:\sdk\platform-tools\adb.exe\adb devices becomes adb devices.
Sent from my GT-I9300 using xda premium
NokiaBigS said:
First, thanks for replying me.
I didn't really follow any guide as i know how it works...
I installed the driver >java pack>sdk and I just run C:\SDK\platform-tools\adb.exe
Click to expand...
Click to collapse
succeed code
Code:
C:\SDK\platform-tools>adb devices
List of devices attached
TA53808AMN offline
TA53808AMN offline
nodstuff said:
adb.exe doesn't run, its a service.
you should set it up your path on your computer to make life easier.
Open a command prompt (search for cmd in start menu) and type "set PATH=%PATH%;C:\sdk\whateverthepathis"
Then once that is set you can just type adb into command without the need for writing the whole path every time.
Like C:\sdk\platform-tools\adb.exe\adb devices becomes adb devices.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
shoot....I don't know about that.....I thought exe is to run........
sorry about that.
So what if I got such result after using command: adb devices
Code:
C:\SDK\platform-tools>adb devices
List of devices attached
TA53808AMN offline
TA53808AMN offline
Glad it is working for you.
NokiaBigS said:
shoot....I don't know about that.....I thought exe is to run........
sorry about that.
So what if I got such result after using command: adb devices
Code:
C:\SDK\platform-tools>adb devices
List of devices attached
TA53808AMN offline
TA53808AMN offline
Click to expand...
Click to collapse
Ya I thought you were going to the platform-tools folder and clicking adb.exe the icon.
Well try set up the path so you don't need to type all the long path to adb.exe whenever you want to use it.
When you set it up all you need to type in is adb devices. That's it.
Its up to you though.
Sent from my GT-I9300 using xda premium
solved issue
Hello all
So here I am in my first topic :laugh:
For Mac users can be tough to work with commands, which most of it has to be done in order to perform stuff in our Moto X.
Instead of having to mount virtual machines in order to have access to Windows' stuff. Or the Android SDK has to be installed, browse to specific folders to run commands from them, etc.
We can work directly in our precious Terminal! :victory:
So, I made a little script that will allow Mac users to work directly on Terminal, no matter which folder we are working on. I've included the following files:
adb
fastboot
mfastboot (Motorola's modified version of fastboot)
To Install
Run Terminal (/Applications/Utilities/Terminal.app)
Browse to the folder in which the script resides, i.e., if it’s in Desktop, then type in Terminal “cd Desktop/ADBInstall” (without quotes).
To run the script type “./install.sh” (without quotes).
You will see input on the screen.
That’s it
To Uninstall
You can safely remove the 3 files in one command, just run the uninstall.sh script by following step 1 and 2 from the Install section. Instead of following step 3, type the following in Terminal: “./unistall.sh” (without quotes).
Hope you like it
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
HeroOfTime said:
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
Click to expand...
Click to collapse
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
MoisesPerez said:
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
Click to expand...
Click to collapse
Thanks for looking into this for me. Yes, it did ask for my password. Here is what I get after running the installer:
Jareds-MBP:ADBinstall Jared$ ./install.sh
This will install ADB, Fastboot and mFastboot on your computer.
Root Permissions required. Please type your password.
Password:
Changed directory to /Users/Jared/Desktop/ADBinstall
Copying ADB...
ADB copied to /usr/bin/adb
Copying Fastboot...
Fastboot copied to /usr/bin/fastboot
Copying mFastboot...
mFastboot copied to /usr/bin/mfastboot
You may now run Android Debug Bridge, Fastboot and mFastboot commands
Have a nice day
I'm attaching a screenshot of the output as well, but that is the output I get, which seems correct.
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
MoisesPerez said:
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
Click to expand...
Click to collapse
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
HeroOfTime said:
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
Click to expand...
Click to collapse
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
MoisesPerez said:
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
Click to expand...
Click to collapse
Well thanks a lot for your help. Still a great resource. I will keep playing around with things and maybe get it to work.
Thanks again!
Not a problem my friend. Good luck!
worked great for me on 10.9!
worked for me as well on Yosemite 10.10.1. thanks!
Glad it did! Regards.