Related
Hey everyone , so I installed Android SDK on my Ubuntu 9.10 machine, the IDE works fine, my problem arises when I want to send commands to the phone using the fastboot command in the terminal. I get command not found error.
I followed both of these procedures:
http://forum.xda-developers.com/showthread.php?t=537508
http://wiki.cyanogenmod.com/index.php/Fastboot
any help would be greatly appreciated.
try this out......(link)
Follow this its better . Just got passed to me I think its cool. Try it out.
http://dennis.christilaw.com/?p=135
blackerwater said:
Follow this its better . Just got passed to me I think its cool. Try it out.
http://dennis.christilaw.com/?p=135
Click to expand...
Click to collapse
well i did try it , and still nothing it still says adb:command not found , fastboot: command not found
i don't know how good your linux skills are. but you might need to
Code:
chmod +x adp
, then you can run it from it's dir with
Code:
./adb
or you can ln or cp it to your bin dir. for fastboot the same applies (mutatis mutandis).
you might have to use sudo, too.
hope that helps
tried that too
Ubuntu still doesnt recognize it
i should tell you im trying to run it from the terminal window.
pk198105 said:
tried that too
Ubuntu still doesnt recognize it
i should tell you im trying to run it from the terminal window.
Click to expand...
Click to collapse
do this:for jaunty/karmic..
step 1
sudo touch /etc/udev/rules.d/51-android.rules
step 2
sudo gedit /etc/udev/rules.d/51-android.rules
#and add this line and save/close:
SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
step 3 (modified permission)
sudo chmod a+rx /etc/udev/rules.d/51-android.rules
step 4( testing device)
./adb devices
step 5 (if works say thanks!))
note: some linux terminal accept ./adb devices or adb devices
Also before that you might want to check and see if the device ids show up when you plug the phone in. Might be something else with your device or rom your running......good luck.
pk198105 said:
Hey everyone , so I installed Android SDK on my Ubuntu 9.10 machine, the IDE works fine, my problem arises when I want to send commands to the phone using the fastboot command in the terminal. I get command not found error.
I followed both of these procedures:
http://forum.xda-developers.com/showthread.php?t=537508
http://wiki.cyanogenmod.com/index.php/Fastboot
any help would be greatly appreciated.
Click to expand...
Click to collapse
These are the best instructions I've found for setting up the Android SDK on Ubuntu:
http://www.futuredesktop.org/developing_android_apps_on_ubuntu.html
The bit you need to get right it setting up the "udev" policy file. The permissions you set here allow you to access the phone from Ubuntu's point of view.
Also....Do you know that to run a program FROM ITS FOLDER from the command prompt in Linux you need to put "./" in front of it? This is telling to look in the current folder for the program to execute it. But you have to be in that folder.
So you would go to [sdk-folder]\tools and type in (you may have to use 'sudo') "sudo ./fastboot devices" and it should list any attached phones that have USB debug turned on in the phone settings (you do have it turned on, right?)
You should see something like (from my phone):
[email protected]:~/android-sdk-linux/tools$ sudo ./fastboot devices
HT95SKF07937 fastboot
If you see this, then you can move to booting a recovery on your phone. If fastboot doesn't list any devices, then your udev probably isn't set up right.
Here is an extract. This works *every* time. The lines below mean you must use sudo to run fastboot or adb....and to start the adb server ("sudo ./adb start-server"). Butif you add GROUP="plugdev" to the end of each line and also add your username to the group "plugdev" (via SYSTEM -> Administration -> Users and Groups), then you don't need to use sudo.
*****
10d) In Ubuntu, create a new rules file for these vendor:device IDs.
Type this command to create the file.
$ sudo gedit /etc/udev/rules.d/51-android.rules
Add the following blue lines (rules) to it and save the file. If your lsusb command reports other, newer product IDs for vendor 0bb4, add them also to the file.
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c01", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", MODE="0666"
--
10e) Re-connect your phone.
Your phone should be detected if you unplug and reconnect it to the computer.
*****
List devices again and you should be fine.
If you're reading and understanding the instructions, it should work. If you're skipping the bits you don't understand.....then go back and understand them. No other way. I'm assuming here that your phone is able to handle fastboot. If you see the three dancing androids, it most likely can.
Try this write up by Google. Hope this one helps. If not then ill do an easy step by step. ....good luck. You know now that I think about it its easy doing it on windows witch doesn't make since it should be easier on a unix box for crap sakes!
http://www.google.com/gwt/n?u=http://developer.android.com/sdk/eclipse-adt.html
finally got it to work. It seems I was missing a file from the Android SDK. Everything is running smoothly, thank you all for your help.
Unfortunately it didnt say which file was missing..
pk198105 said:
finally got it to work. It seems I was missing a file from the Android SDK. Everything is running smoothly, thank you all for your help.
Unfortunately it didnt say which file was missing..
Click to expand...
Click to collapse
try using the sdk manager to update your sdk...see if that gets you the missing file...
-BMFC
i can't get fastboot to work. i placed it in the tools folder. if i enter "fastboot" in a terminal, i get the command line options. "fastboot devices" does not work, though adb and the android sdk are running fine. i'm able to make screenshots, but i'm not able to explore the phone or use fastboot. ideas?
when it says "adb: command not found" it usually isn't in your .bashrc path, or if you did put it in possibly you didn't log out/log back in or restart your computer.
PATH=”$HOME/bin:$PATH:/home/{USERNAME}/android-sdk-linux_86:/home/{USERNAME}/android-sdk-linux_86/tools"
glad you got it working though
could you help me, too?
if i enter fastboot in my terminal i get all the options:
Code:
[email protected]:~$ fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
so the program is working, executable and in my path.
adb does work, as well as the sdk.
i can connect to my phone via ddms and adb, but not via fastboot. it does not find anything....
Hey Boys and Girls,
where i can find an manual to root the tattoo with a mac?
sorry, i have search for this, but i cant find information for this
I don't thing that there is a difference.
As soon as you have SDK installed and adb works, the commands are the same.
hi,
i'm also doing all the rooting process from mac, just put the directory contain 'adb' shell into your home/user places and executing it with 'terminal'..
Same here, using a Mac ever since and also using it for Android development. Due to the underlying Unix core of OS X you just have to follow the steps as described for Linux. If it's just adb commands it's the same on every platform anyway.
You might want to add a
Code:
export PATH=${PATH}:/Users/yourusername/android.sdk/tools
to your .bash_profile file in your home folder so you don't have to cd to the SDK tools folder everytime. Happy rooting!
Mod. edit: not dev related, moved to general
Okay thanks for yours answers but i'm a newbie.
the background story is, I want to edit the boot.mp3. Because the startsound is really annoying
So i have download SDK, open the terminal and switch to usb-debbugging mode on my tattoo.
And now? sorry, I'm still missing a few knowledge
thanks for your help
well just use the various adb commands in Terminal Just type in "adb", press enter and you'll get a list of all possible commands. Assuming you've added the path to your sdk tools folder to your bash profile. Otherwise just drag & drop the adb binary from the tools folder onto your Terminal window, et voila.
The most used commands are probably push and pull where you can, well, push stuff to your phone or pull it to your computer.
So if you want to modify the boot.mp3 you would pull the original from the phone to your computer, modify it and push it back, overwriting the original file. In Terminal speak: ;-)
adb pull /system/media/bootscreen/boot.mp3
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Please note depending on the ROM you're using the paths may be different. To browse the device via Terminal type in "adb shell" and make a simple "ls" to list the directories, "cd" to change directories etc.
Or if you just want to use another mp3:
adb push /path/to/whatever.mp3 /system/media/bootscreen/boot.mp3
Again, on the Mac you can just drag & drop files onto the Terminal to get their full Unix paths like to your custom mp3
Thanks a lot. i love it its really simple
and now i have load and edit the the boot.mp3. But i can't push it to my tattoo, because i can only read but not write
I have tried to root my phone with "adb root" but it is the message "adbd cannot run as root in production builds"
Terminal: "adb remount", then push again
damn the next bad message "remount failed: Operation not permitted"
You need to root your phone first.
http://forum.xda-developers.com/showthread.php?t=637927
Okay i have executed the instructions. But I've stop at this part:
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
Yes i've root but i'cant download the "su binary" because its doesnt exist.
But its absolute essential to need the "su binary" to only copy the boot.mp3 to my phone? Or there is an other way? What are the commands to push the boot.mp3 back to may tattoo then i'm in the root mode like >> "#".
okay hope you understand me
You need "su" to do root stuff... no other way.
Download the package from 1 click root thread and find "su" there...
http://forum.xda-developers.com/showthread.php?t=644279
now, i have install the su binary. Then i does this command
user:~ user$ /Users/user/android-sdk-mac_86/tools/adb shell
$ /data/local/bin/su
#
Click to expand...
Click to collapse
And now? Is there a comand to push the boot.mp3 back to the phone in this mode >> "#" ?
I have try to open an new terminal window and type
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
but the answer is
failed to copy '/Users/android-sdk-mac_86/boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied
Click to expand...
Click to collapse
and adb remount doesnt work to
You also need tattoo-hack.ko file and do insmod tattoo-hack.ko to make /system writable.
Or even better... flash custom amon_ra recovery image and then a custom rom with all this already included.
Mine for example http://forum.xda-developers.com/showthread.php?t=702401
It doesnt have boot sound enabled
Okay thank you very much.
now it was successful
Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Has winxp, tmobile GT
I had this same exact problem, but I was just able to get it working. First, this website is helped a lot:
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
Also, make sure you download the Java SDK package from the link given on that website.
Second, when the website says to "Run Windows command line tool (cmd) and go to D:\android-sdk-windows\tool" open command prompt and enter this code:
cd (enter the path to where the android SDK was installed), for example:
cd C:\android\android-sdk-windows\platform-tools
Notice how I entered "platform-tools" instead of just "tools" because this is the folder where the adb file is download with the android SDK. After you do this, you should then be able to apply adb codes (make sure the screen on your tab is on because you will have to accept superuser prompts, therefore your tab needs to be rooted).
Every time you open command prompt, you will have to enter:
cd thentheplacewheretheandroidSDKisinstalled
as stated above before you are able to enter adb commands.
Hope this helps!
@caveman999 is giving good advice. Working in the command window is weird to those who did not use old pc-dos environment.
You have to be in the tools directory or you have to edit your PATH in windows so you can use adb from any prompt.
thnaks for both of you guys i installed the java jdk and also specified the path in environment variables but still error message!
I could only get adb to work error-free when I was in the same directory as adb.exe program. Just change directories cd..(enter) etc until you are in that directory.
tabing said:
Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Click to expand...
Click to collapse
I had the same error, until I downloaded and placed the .adb files accordingly.
Source: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
"UPDATE: If it says adb not found or something similar, download the ADB files and extract them into the Tools folder of the SDK (they were taken out by Google in the R08 version for some reason and need to be put back)."
download adb files from here: http://www.megaupload.com/?d=RTEY0Q97
The important thing is to put the files really under the "tools" folder.
When you check out above Source I am sure your problem will be solved
Thank you all problem solved
tabing said:
Thank you all problem solved
Click to expand...
Click to collapse
Glad to here it. Why not hit a few thanks buttons?!
Alright so it turns out making ADB work for the Kindle Fire under Ubuntu is just a touch more difficult than in Windows.
Thanks to Gbhil (@ AndroidCentral) for the write up on windows it was a great jumping off point to try to figure this out.
Also thanks to the guys on chat.andirc.net (Skourg3 in particular for helping me figure this out the first time).
Let's get down to the nitty gritty yeah?
First you will still need the entry provided by Gbhil, go ahead and set it using the echo command in a terminal.
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
You can confirm that it took by using the cat command
Code:
cat ~/.android/adb_usb.ini
You should get a return of '0x1949' (plus any other rules that you may have added in the past).
Now really that should work but everytime you run adb you will have to either run it as root or using the sudo command. To allow standard user access we have to setup a udev rule.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
That should open up gedit for you to edit the file 51-android.rules. If this is the first time you have added any udev rules the file will be empty as gedit will have just created it for you. go ahead and add in the following.
Code:
# adb/fastboot protocols for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Save that than add in the user group androiddev.
Code:
sudo addgroup --system androiddev
And add your username to that group.
Code:
sudo adduser <username> androiddev
Replace <username> with your primary username without the <> around it.
After that you will need to logout and log back in for these values to apply. You will probably need to restart the adb server as well.
Change directory to your platform-tools directory and run the following.
Code:
./adb kill-server
./adb start-server
Assuming all went well that should work properly and you can than connect through adb, if for some reason this doesn't work try restarting your computer (though I do not believe this is necessary).
If you don't want to type the "./" before all of your adb and fastboot commands, you need to add their parent directory into your PATH environment variable. For example, (assuming you are using the bash shell) if you have adb and fastboot in your /home/<username>/bin directory, you want to define...
Code:
PATH=~/bin:${PATH}
or
Code:
PATH=${PATH}:~/bin
It just depends on whether you want your own binaries to be used before the system equivalents or after. Most people would probably use the first one to have your own binaries be the preferred ones, but either one should work for adb and fastboot since there are no system binaries by the same names.
If you don't want to have to do this for every shell you open, you can place the definition at the end of your ~/.bashrc file. If you need it for you your login shell, you also need to put it into your ~/.bash_profile file. If you don't want to maintain two parallel files with much of the same information, take a look at this post.
Sblood86 said:
First you will still need the entry provided by Gbhil, go ahead and set it using the echo command in a terminal.
Code:
echo ~/.android/adb_usb.ini 0x1949
Click to expand...
Click to collapse
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
That will create or append to the file as necessary.
no adb_usb.ini file
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
That will create or append to the file as necessary.
Click to expand...
Click to collapse
Somehow the guide I followed for setting up adb/fastboot on Ubuntu did not create the udb_usb.ini file.
I had to go into android-sdk-linux folder on my home directory and copy the one provided with KFU. Only then I could use the echo command.
freefaling said:
Somehow the guide I followed for setting up adb/fastboot on Ubuntu did not create the udb_usb.ini file.
I had to go into android-sdk-linux folder on my home directory and copy the one provided with KFU. Only then I could use the echo command.
Click to expand...
Click to collapse
This...
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
will definitely create the file if it doesn't exist, but only if the ~/.android/ directory exists (with the correct permissions). It won't make those directories if they don't exist. I'm guessing the .android directory wasn't there when you ran the command.
kinfauns said:
This...
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
will definitely create the file if it doesn't exist, but only if the ~/.android/ directory exists (with the correct permissions). It won't make those directories if they don't exist. I'm guessing the .android directory wasn't there when you ran the command.
Click to expand...
Click to collapse
I read a lot of guides and did what they all said and ended up with a working adb command but my kindle was still not detected. At the end it was this thing that solved the issue.
I dont think I had that "android" folder (i did not unhide the home folder to check but since i setup the android sdk inside "android-sdk-linux" folder, i doubt "android" folder was there).
It's because of these tiny details I was sugesting that you, sir, create a how-to for setting up adb on ubuntu (only if you feel comfortable doing it, that is).
Thanks.
Sent from my Amazon Kindle Fire using XDA
My OS is Mint 12, so same as Ubuntu (except for Unity and a bit of non open-source software) and setting up ADB was also a little bit more difficult than I anticipated. I don't know how other distros are.
The guide that got me most of the way there was this one http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62, and then I hit the same problems as the OP. I had to do a bit of mostly useless searching and reading before I found the entry provided by Gbhil and .adb/ devices made the legend "0123456789ABCDEF device" pop up.
I updated every platform in the sdk while I was at it, oops, must get that 4 or 5 gigs of space in my Home folder back sometime.
A kindle fire specific guide for Ubuntu would be awesome, I hereby second freefaling's nomination of you, Sblood86, as author of said guide, if you're into it, because you seem pretty good at it.
Someone asked me about my Ubuntu setup last night and I thought that I should contribute back to this thread with the same information.
You can add another udev rule to cover fastboot commands on FFF so they don't have to be run as root...
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
If you don't want to type the "./" before all of your adb and fastboot commands, you need to add their parent directory into your PATH environment variable. For example, (assuming you are using the bash shell) if you have adb and fastboot in your /home/<username>/bin directory, you want to define...
Code:
PATH=~/bin:${PATH}
or
Code:
PATH=${PATH}:~/bin
It just depends on whether you want your own binaries to be used before the system equivalents or after. Most people would probably use the first one to have your own binaries be the preferred ones, but either one should work for adb and fastboot since there are no system binaries by the same names.
If you don't want to have to do this for every shell you open, you can place the definition at the end of your ~/.bashrc file. If you need it for you your login shell, you also need to put it into your ~/.bash_profile file. If you don't want to maintain two parallel files with much of the same information, take a look at this link.
http://www.joshstaiger.org/archives/2005/07/bash_profile_vs.html
I follow the recommendation at the end.
Hope that helps someone.
kinfauns said:
Someone asked me about my Ubuntu setup last night and I thought that I should contribute back to this thread with the same information.
You can add another udev rule to cover fastboot commands on FFF so they don't have to be run as root...
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
If you don't want to type the "./" before all of your adb and fastboot commands, you need to add their parent directory into your PATH environment variable. For example, (assuming you are using the bash shell) if you have adb and fastboot in your /home/<username>/bin directory, you want to define...
Code:
PATH=~/bin:${PATH}
or
Code:
PATH=${PATH}:~/bin
It just depends on whether you want your own binaries to be used before the system equivalents or after. Most people would probably use the first one to have your own binaries be the preferred ones, but either one should work for adb and fastboot since there are no system binaries by the same names.
If you don't want to have to do this for every shell you open, you can place the definition at the end of your ~/.bashrc file. If you need it for you your login shell, you also need to put it into your ~/.bash_profile file. If you don't want to maintain two parallel files with much of the same information, take a look at this link.
http://www.joshstaiger.org/archives/2005/07/bash_profile_vs.html
I follow the recommendation at the end.
Hope that helps someone.
Click to expand...
Click to collapse
I spent something like 3 weeks trying to find the rule that worked with fastboot lol... thanks!
Your link is dead btw.
Sblood86 said:
I spent something like 3 weeks trying to find the rule that worked with fastboot lol... thanks!
Your link is dead btw.
Click to expand...
Click to collapse
Well it worked a couple of days ago when I made my post. It's not my fault it took you so long to read it.
All it really said was to add...
Code:
if [ -f ~/.bashrc ]; then
source ~/.bashrc
fi
to the .bash_profile file so that it will source the .bashrc file regardless of the way you got to the shell. Then you only have to maintain the .bashrc file and only put login shell specific info into .bash_profile
I picked up another tidbit yesterday while engrossed in the whole CWMR bricking thread. Ubuntu has a plugdev group that's used for (mounting?) hot-pluggable firewire/USB devices... sounds a lot like the KF. The first user created on the system is automatically put into that group. Since most Ubuntu desktop are going to be single user machines anyway, that's going to be THE user for the majority of these cases. So, creating a androiddev group just for the KF is probably not necessary most of the time. You can just skip the addgroup and adduser to group commands if you just want to adjust your rules to use the plugdev group instead.
First I'm going to apologize for not being good with this stuff. Now I'm going to ask questions that will probably frustrate some readers. If you aren't irritated by them please help me out.
Sblood86 said:
First you will still need the entry provided by Gbhil, go ahead and set it using the echo command in a terminal.
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
What is the entry provided by gbhil? Where do I get it? I thought I had adb in here but apparently I don't because when I run the echo command I'm getting "no such file or directory."
Can anyone dumb this down for me just a bit. Add the steps I'm obviously going to need as a newb?
Thanks
hortstu said:
First I'm going to apologize for not being good with this stuff. Now I'm going to ask questions that will probably frustrate some readers. If you aren't irritated by them please help me out.
What is the entry provided by gbhil? Where do I get it? I thought I had adb in here but apparently I don't because when I run the echo command I'm getting "no such file or directory."
Can anyone dumb this down for me just a bit. Add the steps I'm obviously going to need as a newb?
Thanks
Click to expand...
Click to collapse
The most likely cause of that error is you don't have a .android directory in your home directory. You'll need to run the following command before that echo command...
Code:
mkdir ~/.android
That will create a ".android" directory in your home directory (~ is shorthand for your home directory). Then you can create that adb_usb.ini file with the "0x1949" line in it.
Thanks for the help. Stuck again.
After that you will need to logout and log back in for these values to apply. You will probably need to restart the adb server as well.
Change directory to your platform-tools directory and run the following.
Code:
./adb kill-server
./adb start-server
Click to expand...
Click to collapse
logged out and in. what is the name of the "platform-tools" directory?
OK found them and realize they're 2 directories. How to I write to 2 directories at once? I'm going to try one at a time. Looking forward to the elaboration on this.
---------- Post added at 06:16 AM ---------- Previous post was at 06:03 AM ----------
ok followed all the steps except this one.
Code:
PATH=~/bin:${PATH}
Code:
PATH=${PATH}:~/bin
Seems like that's for people that not only know what they're doing in the terminal but spend a lot of time there.
Is there a way to confirm that I've enabled adb before I proceed?
Will I need to follow the latter half of these step everytime I want to enable adb or just the start server command?
Again sorry for newb questions and many thanks for the help.
Tried to push pokey's 9000 fb and it didnt work. I don't think I have adb enabled or something.
hortstu said:
What is the entry provided by gbhil? Where do I get it? I thought I had adb in here but apparently I don't because when I run the echo command I'm getting "no such file or directory."
Can anyone dumb this down for me just a bit. Add the steps I'm obviously going to need as a newb?
Thanks
Click to expand...
Click to collapse
I'm guessing Gbhil is a user who originally posted this information, but not sure...
If you go into a Terminal program, like UXTerm or whatever, you simply type that echo command as shown. It will append the 0x1949 to that .ini file in the hidden folder (.android), so adb can see your device. Of course, this is assuming you have a .android folder. It should be in your Home directory.
When I was playing around with custom ROMs and recovery, my KF stopped registering at 0x1949 at one point. Just in case that is happening to you, plug in your KF to your Linux PC. Go into a terminal program and type lsusb. You will get a list of devices and your KF will be there somewhere. If it is not 0x1949, you will see the correct number. If you get a different number (0x whatever), run the echo command for that number, too. No problem having more than one id num in your adb_usb.ini file.
hortstu said:
Thanks for the help. Stuck again.
Click to expand...
Click to collapse
Don't take this the wrong way, but you might want to take a step back from this and learn a little bit about getting around in Linux before you tackle this project with the Kindle Fire. If this is your primary OS, at least knowing how to navigate around the directory structures, how the PATH variable affects how you run commands, and many other things will be invaluable in your day to day use of the operating system. Linux has come a long way to being user-friendly, but it's still reliant on the users knowing their way around the command line interface... much more than the other two big OS's.
There are countless primers and introductions on the basics of getting around the unix/linux command line. I suggest you search for some and familiarize yourself with them.
In the meantime... the "platform-tools" directory the OP refers to in his post is part of Google's Android SDK distribution...
http://developer.android.com/sdk/index.html
kinfauns said:
Don't take this the wrong way, but you might want to take a step back from this and learn a little bit about getting around in Linux before you tackle this project with the Kindle Fire. If this is your primary OS, at least knowing how to navigate around the directory structures, how the PATH variable affects how you run commands, and many other things will be invaluable in your day to day use of the operating system. Linux has come a long way to being user-friendly, but it's still reliant on the users knowing their way around the command line interface... much more than the other two big OS's.
There are countless primers and introductions on the basics of getting around the unix/linux command line. I suggest you search for some and familiarize yourself with them.
In the meantime... the "platform-tools" directory the OP refers to in his post is part of Google's Android SDK distribution...
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
This would be a good start:
vic.gedris.org/Manual-ShellIntro/1.2/ShellIntro.pdf
Sent from my Amazon Kindle Fire using XDA
OK thanks for the help. Realize I should probably know more about this stuff.
Really want to root for the sake of swype and google store. Tough to commit hours to this stuff since I have a family and a job that is non tech.
I have rooted my evo but that was a while back. Seems a little more complicated on the kindle. Thanks again. Not taken the wrong way.
Sblood86 said:
Alright so it turns out making ADB work for the Kindle Fire under Ubuntu is just a touch more difficult than in Windows.
Thanks to Gbhil (@ AndroidCentral) for the write up on windows it was a great jumping off point to try to figure this out.
Also thanks to the guys on chat.andirc.net (Skourg3 in particular for helping me figure this out the first time).
Let's get down to the nitty gritty yeah?
First you will still need the entry provided by Gbhil, go ahead and set it using the echo command in a terminal.
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
You can confirm that it took by using the cat command
Code:
cat ~/.android/adb_usb.ini
You should get a return of '0x1949' (plus any other rules that you may have added in the past).
Now really that should work but everytime you run adb you will have to either run it as root or using the sudo command. To allow standard user access we have to setup a udev rule.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
That should open up gedit for you to edit the file 51-android.rules. If this is the first time you have added any udev rules the file will be empty as gedit will have just created it for you. go ahead and add in the following.
Code:
# adb/fastboot protocols for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Save that than add in the user group androiddev.
Code:
sudo addgroup --system androiddev
And add your username to that group.
Code:
sudo adduser <username> androiddev
Replace <username> with your primary username without the <> around it.
After that you will need to logout and log back in for these values to apply. You will probably need to restart the adb server as well.
Change directory to your platform-tools directory and run the following.
Code:
./adb kill-server
./adb start-server
Thanks for the post and the guide.
I have a little problem. i.e How do i change the directory to platform-tools directory before i ru the code u gave me. Please dont be mad at me becouse the truth is i am a new user.
Click to expand...
Click to collapse
majexy033 said:
Thanks for the post and the guide.
I have a little problem. i.e How do i change the directory to platform-tools directory before i ru the code u gave me. Please dont be mad at me becouse the truth is i am a new user.
Click to expand...
Click to collapse
As in; from your terminal use the 'cd' command to change directory to where-ever platform-tools is actually installed on your PC.
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
UpsideDownAce said:
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
Click to expand...
Click to collapse
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
uncleswoop said:
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
Click to expand...
Click to collapse
Just to be sure, you've apply sideload from adb in the recovery, correct?
ducatic said:
Just to be sure, you've apply sideload from adb in the recovery, correct?
Click to expand...
Click to collapse
I'm in the same boat! I tried, today, several times to sideload the update but I'm constantly getting the cannot read sideload error message. I guess I'm off to other sites to see what the fix is.
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
adb sideload 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
Click to expand...
Click to collapse
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
I might be just an idiot but why are you guys trying to SideLoad a system update?
AFAIK... sideload is merely to install apps into your rom that Jellybean or the Playstore doesn't like.
I think you guys want to use "ADB Fastboot" commands instead. Get a guide before you attempt to do this though. I used Wugs Toolkit to install the bootloader from 4.2.2 update.
fede01_8 said:
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
Click to expand...
Click to collapse
:laugh: true
For clarity:
- adb sideload can used for installing zip updates from PC, as an alternative for using the ROM/recovery manager on your tablet/phone.
Code:
adb sideload update.zip
- fastboot flash is used for installing img files to a specific partition (boot, recovery, system)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
Thank you!!! Spending hours trying to figure it out, so simple. Although not sure why the toolkit didn't work, but using CMD did work.
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
fede01_8 said:
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
Click to expand...
Click to collapse
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
brandnewyc said:
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
Click to expand...
Click to collapse
This is what got me on the right trail. I opened the command prompt, navigated to the correct folder, used the sideload command and copied the name of the update file into the command prompt window, but it wasn't until I appended it with the .zip extension that it finally worked.:victory:
Hey guys! I don't have the sideload problem anymore, but, I get this error. cannot read '(name of file).zip'
I am either really dumb or this isn't working! I have it connected to adb device number and all working fine. I have the zip in platforms-tools cmd window opened etc. when i go to adb sideload and then top of cmd window edit paste the name of the file add .zip and it says can not read file!
Please help!!
Same problem...fixed
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
jihoon526 said:
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
Click to expand...
Click to collapse
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Fix
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
hkleiner said:
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
Click to expand...
Click to collapse
are you on the same directory as your file?
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
Try addind ".zip" at the end of the file name in CMD. So if the name in the directory is ROM, type into cmd "adb sideload ROM.zip"
DigitalOSH said:
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Click to expand...
Click to collapse
oddly this helped me a lot with another device. i was having the exact same problem and found this topic in searching for a solution. but after removing the extension, renaming, then renaming and re-adding the extension it worked. i also had to type adb sideload fielanme.zip.zip to get it working.