Am using Ubuntu 11.10 i got my ADB to work flawlesly, but everytime i invoke ¨fastboot devices¨ i get ¨inssuficient permissions fastboot¨, if i try ¨sudo ./fastboot devices¨ i get ./fastboot unknown commad, then i try ¨sudo fastboot devices¨ get same unknown error, if i go all the way to the folder where i got fastboot(android-sdk/platform-tools/) and invoke ¨sudo ./fastboot devices¨ it works... i got the folders in my bash list, so i can invoke adb/fastboot from anywhere, adb is working flawlesly but fastboot i have to go all the way to the folder and run it using ¨sudo¨.
Any tips on how to tweak the permissions maybe??... or has anyone found a way to make fastboot work from anywhere in the system?? or at least doing ¨sudo fastboot¨ without going all the way to the /usr/loca/android-sdk/platform-tools/(my preffered location) folder????
sairegsx said:
Am using Ubuntu 11.10 i got my ADB to work flawlesly, but everytime i invoke ¨fastboot devices¨ i get ¨inssuficient permissions fastboot¨, if i try ¨sudo ./fastboot devices¨ i get ./fastboot unknown commad, then i try ¨sudo fastboot devices¨ get same unknown error, if i go all the way to the folder where i got fastboot(android-sdk/platform-tools/) and invoke ¨sudo ./fastboot devices¨ it works... i got the folders in my bash list, so i can invoke adb/fastboot from anywhere, adb is working flawlesly but fastboot i have to go all the way to the folder and run it using ¨sudo¨.
Any tips on how to tweak the permissions maybe??... or has anyone found a way to make fastboot work from anywhere in the system?? or at least doing ¨sudo fastboot¨ without going all the way to the /usr/loca/android-sdk/platform-tools/(my preffered location) folder????
Click to expand...
Click to collapse
I had a similar problem on my USB Linux install. My work around was to just move fastboot to /usr/bin
sairegsx said:
Am using Ubuntu 11.10 i got my ADB to work flawlesly, but everytime i invoke ¨fastboot devices¨ i get ¨inssuficient permissions fastboot¨, if i try ¨sudo ./fastboot devices¨ i get ./fastboot unknown commad, then i try ¨sudo fastboot devices¨ get same unknown error, if i go all the way to the folder where i got fastboot(android-sdk/platform-tools/) and invoke ¨sudo ./fastboot devices¨ it works... i got the folders in my bash list, so i can invoke adb/fastboot from anywhere, adb is working flawlesly but fastboot i have to go all the way to the folder and run it using ¨sudo¨.
Any tips on how to tweak the permissions maybe??... or has anyone found a way to make fastboot work from anywhere in the system?? or at least doing ¨sudo fastboot¨ without going all the way to the /usr/loca/android-sdk/platform-tools/(my preffered location) folder????
Click to expand...
Click to collapse
not sure if the issue is still outstanding or not. for anybody who happens across this thread later:
insufficient perms can be related to not setting the binary as an executable. chmod +x fastboot
that should set the binary as an executable. to check, ls -l fastboot and it will
list the permissions/flags on the file.
otherwise the other issue which commnands to mind would be specific uid/gid permissions on the file.
the sudo commad would execute the file from root access and should bypass any uid/gid limitations.
i didn't have to do anything special for fastboot to work on my linux. simply chmod +x fastboot and ./fastboot .
hope that helps!
I ran in to the same annoyance when I was setting up adb. What I did was create an alias, so whenever I type bda the terminal will cd to the adb folder, kill the adb server, start sudo adb server, then cd back to whichever folder I was working it. Aliases are awesome, I recommend checking them out. If you have any questions about setting it up let me know.
Resolved!
joeykrim said:
not sure if the issue is still outstanding or not. for anybody who happens across this thread later:
insufficient perms can be related to not setting the binary as an executable. chmod +x fastboot
that should set the binary as an executable. to check, ls -l fastboot and it will
list the permissions/flags on the file.
otherwise the other issue which commnands to mind would be specific uid/gid permissions on the file.
the sudo commad would execute the file from root access and should bypass any uid/gid limitations.
i didn't have to do anything special for fastboot to work on my linux. simply chmod +x fastboot and ./fastboot .
hope that helps!
Click to expand...
Click to collapse
Thanks everyone for the help, i did what joeykrim said and now it works as is was supposed to!! thanks again joeykrim!!! ^_^
Related
Im trying to get to the tools in the sdk folder from the command line.i went to path ;c:\android\tools.I go to the command line i put in that path and it say that its not recognived as a internal or external command what am i doing wrong.and when its done wright how should it look. Im doing the 1.5 to 2.1 walkthrough. im new to all this i wanna get it right.
skd05 said:
Im trying to get to the tools in the sdk folder from the command line.i went to path ;c:\android\tools.I go to the command line i put in that path and it say that its not recognived as a internal or external command what am i doing wrong.and when its done wright how should it look. Im doing the 1.5 to 2.1 walkthrough. im new to all this i wanna get it right.
Click to expand...
Click to collapse
you are headed in the right direction but it needs too look like this
cd C:\android\tools
Click to expand...
Click to collapse
Hope this helps you out.Btw what are you trying to do push a bootanimation or something
rooting the eris im trying to enter these codes in the command promt..
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
I do:
cd C:\AndroidSDK\tools
that was after I moved the tools folder otherwise it was:
cd C:\AndroidSDK\android-sdk-windows\tools
im try to get to command prompt and go to your tools directory am i typing the right thing ;C:\android\tools or is it cd c:\android\tools in trying to Flashing a Custom Recovery so i can flash the 2.1 rom
have you made it to the tools directory? if you actually go to the tools file on your computer, on the address bar you will see what you need to type.... either (red font)
cd C:\AndroidSDK\tools
that was after I moved the tools folder otherwise it was:
cd C:\AndroidSDK\android-sdk-windows\tools
type one or the other exactly how I have it up top....cd and all....
Hi guys, I am trying to move some files into ext partition. I want to do it via adb but ...
It came to my attention that adb shell isn't the solution for adb push or adb pull. I need to do it via windows but whenever I do adb remount or adb kill-server and adb pull or adb push . When I input and press enter it shows an arrow I press enter cuz I dont know what I could input. It just tells me "push not found" or "adb not found" if I say adb push.
Please don't ask me what I do exactly just tell me the exact steps ^^
I would like to move Htc ime mod by jonasl by example.
Hope you will help me out guys
copy tools adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the .../windows/system32/
Thank's but doesn't seem to work
I tried doing : cd C:\Program Files\Android SDK
adb push C:\Program Files\Android SDK\tools\su-2.1-e-signed\system\xbin\su \system\xbin\
but this just gives me all adb commands.
Doing this inside adb shell gives me the adb : not found
Any idea/ workaround? (< only adb plz I dont want to install linux)
Code:
cd C:\Program Files\Android SDK
adb remount
adb push tools\su-2.1-e-signed\system\xbin\su \system\xbin\
Give that a try.
You can't use push or pull with shell.
The biggest problem you sill face is having spaces in the PC side path names, try moving the SDK to c:\Android_SDK if the above fails
Try this:
Code:
cd C:\Program Files\Android SDK\tools
adb remount
adb push C:\Program Files\Android SDK\tools\su-2.1-e-signed\system\xbin\su /system/xbin/
AH great, by removing the space beetwin android and sdk I managed to get out but now I am facing Out of memory error
Damn I have like 1.5 gb of memory on my ext2 partition
Where can I check the remaining memory?
EDIT : su is 22ko so I dont think memory is the big deal. However I would still like to know what is left
Maybe my microSD is dying... Any idea?
Mister-Tea said:
yy whatever, if you don't want to answer then don't but don't look high on me.
lol......
Click to expand...
Click to collapse
1/ he already answer your question
2/ it's android DEV section, your question if far away from DEV
3/ You have to learn how to use command-line application (Windows suck at this, so you should try on a linux OS)
BTW: a little how-to
cd: a great command, you'll be able to change directory (yes you have "adb" on your harddrive, but you have to tell your computer where is it)
cp : copy
mv: move
ls: list content of working directory
pwd: print current working directory
Now: let say "adb" (adb.exe) is located here: /home/carbonyle/androidSDK/tools/
launch a terminal (WindowsKey + r on windows host, then type "cmd")
Yyour working directory maybe "C:" , or whatever (/home/carbonye/ for me)
now use "cd"
Code:
cd /home/carbonyle/androidSDK/tools/
<. of course adapt this to your environnment
(use ls / pwd to convince you what you're doing)
Code:
./adb reboot recovery
<- for linux user
Code:
adb reboot recovery
<- for Win**** users
Of course this will reboot your phone into recovery mode, just adapt command to your need
Right, this thread has gone far enough with enough flaming for today.
To all of you, im disappointed and you should all know better.
PLease refrain from further flames, tidy up in progress. I am also moving this to QnA.
@ Mister-Tea
You are equally responsible for the flaming by flaming yourself.
@ you all, quit it or i will take further action.
THanks.
I just did a major mistake by copying sh from Windows to /system/bin/sh. Not haivng the execute bit has stopped me from using adb shell.
Could someone provide a clockworkmod recovery file that restores sh & it's permissions? I would greatly appreciate it. Thanks!
Why not just run the fix permissions script from the advanced menu in clockworkmod?
Sent from my SCH-I500 using XDA App
well, would be easier from a linux box:
chmod 755 sh
adb push sh /system/bin/sh
adb reboot
i_am_enderst said:
well, would be easier from a linux box:
chmod 755 sh
adb push sh /system/bin/sh
adb reboot
Click to expand...
Click to collapse
Thanks. I fixed it through recovery mode shell via adb.
I'm getting the following garbage when I do ls within adb shell. Is there any way to fix this?
Code:
# ls
ls
←[1;34mcache←[0m ←[1;32minit.rc←[0m ←[1;34msbin←[0m
←[1;34mconfig←[0m ←[1;32minit.smdkc110.rc←[0m ←[1;34msdcard←[0m
←[1;34mdata←[0m ←[1;32minit.smdkc110.sh←[0m ←[1;34msqlite_stmt_journals←[0m
←[1;34mdbdata←[0m ←[1;34mlib←[0m ←[1;34msys←[0m
←[1;32mdefault.prop←[0m ←[1;32mlpm.rc←[0m ←[1;34msystem←[0m
←[1;34mdev←[0m ←[1;34mmnt←[0m ←[1;32msystem.prop←[0m
←[1;34mefs←[0m ←[1;34mpreinstall←[0m ←[1;34mtmp←[0m
←[1;36metc←[0m ←[1;34mproc←[0m ←[1;34muserdata←[0m
←[1;32mfota.rc←[0m ←[1;32mrecovery.rc←[0m
←[1;36minit←[0m ←[1;34mres←[0m
Those are bash color escape codes but I don't know why adb is outputting them since I'm new to Android.
It's a windows command prompt thing..
Easiest solution, do this from your adb shell (you'll need to do it each time)
export LS_COLORS=none
alternatively you can installed cygwin and spend a little time setting it up so that the ANSI colors are displayed when using adb shell.
I assume the colors show up fine under linux, which is why this got included in some kernels/rom packages without anyone addressing it.
Thanks for the info. It shows up correctly through a cygwin terminal. I'll just use that for now on.
I have a few questions on some of these steps:
On the checksum part below, it says to redownload the file if the checksum does not match, does that mean to re push the misc.img and run step three again.
Step 3
This step will gain temp root and flash the custom misc.img. Run:
adb shell
Now the shell should display "$".
Run:
/data/local/psneuter
You will now be kicked out of adb, and adb will restart as root. Let’s confirm the md5 of misc.img:
adb shell
At this point, the shell should display "#".
Run:
/data/local/busybox md5sum /data/local/misc.img
Output should be "c88dd947eb3b36eec90503a3525ae0de." If it’s anything else, re-download the file and try again.
On step 4 below how do I put the file on the phone? Can I just use windows and copy the file to the sd card?
Step 4
Here you will rename the downgrade RUU as PG05IMG.zip and place it on your SD card. Then, run the following command:
Ok in step 3 below, it says if the checksum does not match to delete and re-download. How do I delete the file? Is there a command to do this? I assume re-downloading refers to pushing the file again correct?
Step 6
Please pay attention – this is very important. This step involves a small chance of bricking if you mess up.
To push the eng bootloader:
adb push hbooteng.nb0 /data/local/
adb shell
/data/local/busybox md5sum /data/local/hbooteng.nb0
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb" exactly, stop, delete it, and re-download it. Otherwise, continue.
to delete in adb you need to use the command "adb shell" and the command in there is "rm /path/to/file" no quotes. This is where being a Linux user helped me out lol. As for moving the file, yes. Move it to SD any way at all that you'd like.
kdb424 said:
to delete in adb you need to use the command "adb shell" and the command in there is "rm /path/to/file" no quotes. This is where being a Linux user helped me out lol. As for moving the file, yes. Move it to SD any way at all that you'd like.
Click to expand...
Click to collapse
Is it "adb shell" one one line and then "rm /path/to/file" on next line or is it all one line like this "adb shell rm /path to file""
Strife21 said:
Is it "adb shell" one one line and then "rm /path/to/file" on next line or is it all one line like this "adb shell rm /path to file""
Click to expand...
Click to collapse
It's all on one line. FYI you only have to adb shell, once. In the tutorial for the root, he has you doing 'adb shell reboot bootloader'. However, you are already in adb shell, at that point. All you need to type is 'reboot bootloader'.
[Guide][ARM now supported] Android development/debugging on ChromeOS - ADB & fastboot
What you need to know before we begin:
ChromeOS (Or Chromium OS if you installed it on a non-chromebook) is based on Unix, and you can access a terminal with button combinations. This part of the guide is easy, but if I can get apt-get working, that's where it gets really complex.
What you'll need
A computer running ChromeOS/Chromium OS
An internet connection on it, or the files on a USB drive (and you to copy them to Downloads)
A little Linux knowledge
Some patience
1.) Download the correct files for system:
ChromeOS/ChromiumOS on an x86 based PC
ChromeOS on an ARM based PC
2.) When the zip has downloaded, extract it so both the adb and fastboot files are in the Downloads folder
3.) It's now time to access the terminal mode. It might be a good idea to get this guide on a phone or some other device so you don't have to switch out at any time.
If you're using a chromebook or an official chromeOS build, you need to access developer mode. Note: this will wipe all your data for security reasons. Full info is here: Chromium Project: Developer mode
4.) Press Ctrl-Alt-F2 on your keyboard, and the whole screen will be a terminal. Read the info at the top, and then login
NOTE: If you're using Chromium OS vanilla builds, the username and password are as follows:
Code:
User: chronos
Pass: facepunch
5.) You now have a localhost terminal, with no root permissions.
6.) Run this code, to locate the location of your Downloads folder:
Code:
ls /home
7.) Mount the filesystem as follows:
Code:
mount -o remount,rw /
8.) Using the name other than "root" and "user", run these commands:
Code:
cp /home/<name>/user/Downloads/adb /sbin/adb
For example, the Chromium one would be:
Code:
cp /home/chronos/user/Downloads/adb /sbin/adb
Repeat for Fastboot (replace "adb" with "fastboot" without the quotes)
9.) Test that it has worked by running:
Code:
adb
It should result in adb working
10.) You're done, adb and fastboot should work. You might need to reboot in some cases for it to work fully
11.) For more stuff, like Java and ant, wait a while until I work out how to get apt-get installed from dpkg
Credits:
Thanks to KMyers for compiling Fastboot for ARM devices, thread here
Reserved
And again
Once more, just in case
Whenever I go to check my path I get this response:
"cat: /usr/local/bin:/usr/bin:/bin:/opt/bin:/home/chronos/user/Downloads/android-sdk-linux/platform-tools: no such file or directory"
Help?
awacker89 said:
Whenever I go to check my path I get this response:
"cat: /usr/local/bin:/usr/bin:/bin:/opt/bin:/home/chronos/user/Downloads/android-sdk-linux/platform-tools: no such file or directory"
Help?
Click to expand...
Click to collapse
That is perfectly normal, every Linux based thing says no file or directory after the path to my knowledge
Sent from my GALAXY NEXUS using Tapatalk 4 (VIP)
Quinny899 said:
That is perfectly normal, every Linux based thing says no file or directory after the path to my knowledge
Sent from my GALAXY NEXUS using Tapatalk 4 (VIP)
Click to expand...
Click to collapse
And so it seems! Now it appears that any adb command returns a "Permission denied" message. Ideas?
Update: Same response for fastboot commands.
awacker89 said:
And so it seems! Now it appears that any adb command returns a "Permission denied" message. Ideas?
Update: Same response for fastboot commands.
Click to expand...
Click to collapse
Try this:
Code:
cd /home/chronos/user/Downloads/android-sdk-linux/platform-tools
chmod 755 adb
chmod 755 fastboot
Then exit back to the login screen on the terminal, login again and try running adb
Quinny899 said:
Try this:
Code:
cd /home/chronos/user/Downloads/android-sdk-linux/platform-tools
chmod 755 adb
chmod 755 fastboot
Then exit back to the login screen on the terminal, login again and try running adb
Click to expand...
Click to collapse
Still no dice
I'm starting to lose hope. I just keep getting "permission denied."
I thought maybe trying this would do the trick but still no response.
Code:
sudo ./adb devices
[code]
P.S. Guess I should mention that running just adb returns command not found, so I've been using ./adb. Maybe I just don't know what the hell I'm doing but I just can't get it to work.
Hmmm. Well, The SDKx86 (87mb) that were in the instructions so, I downloaded the ADT (399mb) instead, just a hint.
Is there a specific branch that is required to be on in chromeos in order for terminal to act correctly? I never get any chance to login once i get into the "crosh" terminal.
Quinny899 said:
That is perfectly normal, every Linux based thing says no file or directory after the path to my knowledge
Sent from my GALAXY NEXUS using Tapatalk 4 (VIP)
Click to expand...
Click to collapse
Instead of doing
Code:
cat $PATH
you should do
Code:
echo $PATH
The cat command is trying to concatenate a file with the name of your full path, which obviously doesn't exist. echo tells you the value of the $PATH variable, which is what you're actually trying to do.
I was trying to get this to work on my Chromebook Samsung Series 5 550
Furst thing I noticed was the absence of an f2 key - tried a usb keyboard no joy
I assume what I am trying to launch is Shell which can only be accessed with a Chrome OS device in developer mode. I really want to get this working so I will try activating developer mode and report back.
Update:
So Developer Mode resets and wipes your device (doh!) back to Step 1
Update 2: (Dev Mode activated function key labelled as "->" works as f2 and launches shell successfully"
Has anyone got this working? I noticed that the folder coming out of the SDK zip is called "sdk" but all the commands listed in the guide use "android-sdk-linux"
I used "sdk" and just get the Permission Denied issue even after chmod on adb
Will this work on the Samsung Series 3 with the ARM processor?
imtoomuch said:
Will this work on the Samsung Series 3 with the ARM processor?
Click to expand...
Click to collapse
Supposedly pulling the adb binary from an android device (/system/bin/adb) and using that would work. Don't know about fastboot though
Sent from my Galaxy Nexus using Tapatalk 4 Beta
jambamkin said:
I was trying to get this to work on my Chromebook Samsung Series 5 550
Furst thing I noticed was the absence of an f2 key - tried a usb keyboard no joy
I assume what I am trying to launch is Shell which can only be accessed with a Chrome OS device in developer mode. I really want to get this working so I will try activating developer mode and report back.
Update:
So Developer Mode resets and wipes your device (doh!) back to Step 1
Update 2: (Dev Mode activated function key labelled as "->" works as f2 and launches shell successfully"
Has anyone got this working? I noticed that the folder coming out of the SDK zip is called "sdk" but all the commands listed in the guide use "android-sdk-linux"
I used "sdk" and just get the Permission Denied issue even after chmod on adb
Click to expand...
Click to collapse
I had the same problems. And just stopped trying about 2 days of trying to figure it out.
I was able to find a version of adb compiled for ARM but it was from an older version which made it a no go on my Nexus 4 (4.2.2 requires updated adb to work with the new security enhancements built in).
I tried it on my Series 5 550 chromebook. Can't seem to get it to work.
I do all the commands and it shows up in echo $PATH but then when i try adb anything it says permission denied. I do the chmod 755 and still permission denied.
i tried to exit back to the login and then the folder wasn't in the echo path anymore. adb not working either. I tried rebooting chromebook and it wasnt there either.
Would it be cheating to get it running with crouton? Because I did get that done.
Sent from my NookColor using xda premium
yeah i've been having the same issue with my samsung 5 series chromebook. "permission denied" and all that. But on the fun side, i learned if you want to really make your chromebook bug-out; type cat adb whilst in /platform-tools.