So I'm in my platform-tools directory in the terminal, and here is how my commands go
./adb devices
returns List of devices attached
015d18ad5a27fe04 device
so then I go
./adb reboot bootloader
and my Nexus reboots into the bootloader. And then I enter
./adb devices
And there is no device listed. When I type in
./fastboot oem lock
it returns
<waiting for device>
and it hangs here until I control-c out. Am I missing something? I really hope it's not a syntax error
any help would be appreciated. Also, please note that I am in Ubuntu 12.04 on a native installation, so it isn't a driver issue
Silly question, but did you sudo?
thebobp said:
Silly question, but did you sudo?
Click to expand...
Click to collapse
As a matter of fact, I didn't :crying: I had to kill the server and when I did I left su. That's even more humiliating than a syntax error :crying: thanks for the help
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....
When i try typing " adb devices" in CMD.
I get
"list of devices attached"
what am i doing wrong?
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
I have the exact same problem. Did you ever figure it out?
What directory are you working out of? If you did the default install of the Android SDK. Try this:
Code:
cd c:\android-sdk-windows\tools
Then:
Code:
adb devices
You have to open the command prompt from within the tools folder from sdk folder.
Also, its never worked for me while my phone is in the bootloader, i run abd commands while my phone is booted normally (with debugging enabled).
I use adb shell stop, adb remount, whatever commands you wanted to do originally, adb shell reboot.
Hope that helps, good luck man.
Sounds like maybe the driver isn't installed correctly. Check your device manager and see if the N1 shows up in there and what it's named.
tamarian said:
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
Click to expand...
Click to collapse
That is fastboot, fastboot for the bootloader, ADB for everywhere else
Are you on windows or linux?
Also try "adb remount" when you are in the /tools folder, then try "adb devices"
Make sure USB Debugging is on..that could be it
First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?
mrfilbert said:
First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?
Click to expand...
Click to collapse
no need for usb drivers in linux
you have to be sure that you are su on your pc... (i have fedora)
i think ubunto it´s sudo, isn´t it?
and before you can see your device through adb you have to type "./adb kill-server" and then "./adb start-server"
... then "./adb devices" and so on
Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?
mrfilbert said:
Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?
Click to expand...
Click to collapse
no that happens because you are not root on your pc...
in fedora i have to do the following to see my device:
su (enter)
then enter password
i get this symbol: # = means i´m root on my pc
then i go to my platform-tools directory (cd whatever)
./adb kill-server
./adb start-server
./adb devices ...now you should see your device
then start the rooting procedure, good luck
Use 'sudo su' in ubuntu to get a root prompt.
otherwise you have to set a 51-android.rules file (instructions here http://developer.android.com/guide/developing/device.html)
-Nipqer
I've rooted my kindle fire before but I lost root access so I rooted it again last night via kindlewater (for mac) or some such name like that.
Then I tried to install TWRP via my vmware windows emulator. At some point during the process my kindle fire disconnected from windows and reconnected to my mac and I'm assuming that's where things went tragically wrong.
It looks as if it's stuck in fastboot but windows isn't recognizing it. My drivers are installed and have uninstalled and reinstalled a few times.
I've tried the Kindle Fire Utility 0.9.3 and the Kindle Fire Unbricking Utility. Neither of them have done anything since the only way windows recognizes the KF is as a corrupted USB device.
I've tried boosting it into normal mode but all it gives me is "waiting on device" as it does with any selection in the KF Utility or KF Unbricking Utility.
I've been in web design/computer technology classes for four years (top of my class) but at some point I must have missed the command prompt classes because I can't seem to ever get commands working nor do I have any idea on how to which is why I've been reliant on those two programs which haven't done anything.
I've seen somebody say they forced the correct fastboot with some command line like fastboot oem blablabla and I tried that once or twice or 8 times and it never recognized the command then again though all I typed was the command and hit enter...
I've never seen a yellow triangle when booting I've always been stuck on a static (no animation) kindle fire screen and no matter what I can't get it recognized as anything other than a corrupt usb device.
What makes this all harder is working on a macbook pro with a windows emulator. -_-
I really need some advice here...I'm about ready to say screw it and use my warranty to have the device replaced in a staples store. If I can't figure out how to boot it i'm sure they wouldn't be able to and would just replace it right?
P.S. I'd rather have it replaced then buy a fastboot cord and have to wait a week to have it shipped lol.
Please help a girl out
try this
Symberlei said:
I've rooted my kindle fire before but I lost root access so I rooted it again last night via kindlewater (for mac) or some such name like that.
Then I tried to install TWRP via my vmware windows emulator. At some point during the process my kindle fire disconnected from windows and reconnected to my mac and I'm assuming that's where things went tragically wrong.
It looks as if it's stuck in fastboot but windows isn't recognizing it. My drivers are installed and have uninstalled and reinstalled a few times.
I've tried the Kindle Fire Utility 0.9.3 and the Kindle Fire Unbricking Utility. Neither of them have done anything since the only way windows recognizes the KF is as a corrupted USB device.
I've tried boosting it into normal mode but all it gives me is "waiting on device" as it does with any selection in the KF Utility or KF Unbricking Utility.
I've been in web design/computer technology classes for four years (top of my class) but at some point I must have missed the command prompt classes because I can't seem to ever get commands working nor do I have any idea on how to which is why I've been reliant on those two programs which haven't done anything.
I've seen somebody say they forced the correct fastboot with some command line like fastboot oem blablabla and I tried that once or twice or 8 times and it never recognized the command then again though all I typed was the command and hit enter...
I've never seen a yellow triangle when booting I've always been stuck on a static (no animation) kindle fire screen and no matter what I can't get it recognized as anything other than a corrupt usb device.
What makes this all harder is working on a macbook pro with a windows emulator. -_-
I really need some advice here...I'm about ready to say screw it and use my warranty to have the device replaced in a staples store. If I can't figure out how to boot it i'm sure they wouldn't be able to and would just replace it right?
P.S. I'd rather have it replaced then buy a fastboot cord and have to wait a week to have it shipped lol.
Please help a girl out
Click to expand...
Click to collapse
I had the same thing happen to me (do not use Fastboot in recovery). This worked for me give it a try ; Kindle Fire Unbrick posted on liliputing. You'll need a PC with Windows. Just be sure you have the Kindle Drivers available, otherwise your USB may not see the Kindle.
Good luck
Why were you using Windows emulator to begin with?
Just use terminal and cd to your android sdk tools folder where adb and fast boot are and type: (with device plugged in and turned on)
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
Chances are that it will hang at "rebooting". If so just hold the power button down until it shuts off then turn it back on. It should start normally.
Sent from my Amazon Kindle Fire using xda premium
CD?
How do I CD to something?
I know this sounds stupid and totally noobish but like I said terminal and I don't get together a whole lot XD
Can I just pay somebody to come to my house and do it for me? D=
(Joking of course)
Okay I think I directed myself to fastboot in terminal and I copied and pasted
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
but then it said "-bash: ./fastboot: No such file or directory
mac-users-macbook-pro-1634:~ macuser$ ./fastboot reboot
-bash: ./fastboot: No such file or directory"
Symberlei said:
How do I CD to something?
I know this sounds stupid and totally noobish but like I said terminal and I don't get together a whole lot XD
Can I just pay somebody to come to my house and do it for me? D=
(Joking of course)
Okay I think I directed myself to fastboot in terminal and I copied and pasted
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
but then it said "-bash: ./fastboot: No such file or directory
mac-users-macbook-pro-1634:~ macuser$ ./fastboot reboot
-bash: ./fastboot: No such file or directory"
Click to expand...
Click to collapse
A quick intro:
cd is "change directory"
pwd is "present working directory"
ls is "list directory contents"
What you see in the prompt above is...
mac-users-macbook-pro-1634 - the name of your mac
~ - your pwd
macuser - your username
~ is shorthand for your home directory. i.e. '/Users/macuser'
e.g. If you type 'pwd' you'll get '/Users/macuser'
cd will change your pwd to what you specify
e.g. type 'cd Documents' and you'll change to that directory. This is analogous to opening up your Documents folder in the Finder.
If you then type 'pwd' at the next prompt you'll get '/Users/macuser/Documents'
If you then type 'ls' at the next prompt, you'll get the contents of your Documents folder listed
What the previous poster wants you to do is change directories to wherever you have the fastboot program so you can run it in the terminal. You can do this on the mac by typing "cd " (that's cd followed by a space) and then dragging the folder that contains the fastboot program into the terminal window. The terminal will automatically paste in the complete path (directory location) of the folder for you.
I suggest doing some more reading...
http://osxdaily.com/2007/02/07/basic-command-line-utilities-tips-commands/
Thank you but
Thank you so much that was incredibly helpful =D
it brought up the fastboot program and it says the following
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
mac-users-macbook-pro-1634:~ macuser$
What should I do after this?
*Bump* I still need help D=
I still don't know what to do after that last step or even if I'm in the wrong place. I'd like to have my kindle fire back up and unbricked before the weekends over. Please and thank you
OK so assuming you have terminal open and your current directory is your Android SDK tools folder...
it should read something like iMac-HD~ platform-tools "yourUsername"$
...all you need to do is type:
./fastboot -i 0x1949 oem idme bootmode 4000
Hit enter, then:
./fastboot reboot
It will say "rebooting". If it doesn't reboot right away just hold down the power button until it shuts off, then restart.
If you aren't sure you are in the right directory to start off in, type:
ls
That's "Ls" not "is"...you should see, among other things, adb and fastboot. If you are not in the right directory (edit: type cd in the terminal) find the Android SDK folder and drag it to your terminal window hit enter and type:
cd platform-tools
That should get you going in the right direction
Sent from my Amazon Kindle Fire using xda premium
ERROR:could not get pipe properties
Okay well I finally got all my directories sorted out so those are fine and I entered in your commands which worked fine (THANK YOU SO MUCH) but now I'm getting this error
mac-users-macbook-pro-1634:tools macuser$ ./fastboot-mac -i 0x1949 oem idme bootmode 4000
./fasERROR: could not get pipe properties
< waiting for device >
^R
./ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
_____________
I've tried it again and now I'm just getting "..." and it's not doing anything. :/
mac-users-macbook-pro-1634:~ macuser$ cd /Users/macuser/android-sdk-macosx/tools
mac-users-macbook-pro-1634:tools macuser$ ./fastboot-mac -i 0x1949 oem idme bootmode 4000
...
Success wooooo
OMG THANK YOU SO MUCH! I LOVE YOU! I seriously don't know what in the world I would have done without your help! I'm so happy right now! =D
If you ever need anything digitally designed hit me up at [email protected] I owe you one
Exact same problem resolved, my issue and solution
I've spent the past several hours banging my head against this problem. MBP and an iMac both running OS X 10.7.3 and VM Fusion 4.1. This thread seemed like the best place to share what I learned in case anyone else has a similar issue.
NOTE: I try and run everything inside vms to keep my base OS clean and just revert to snapshots frequently. Also I've rooted/modded a couple android phones with both these vms recently without incident.
Fought with two different XP Pro vms to get the ADB/Fastboot drivers installed. Kept getting an error about unsigned drivers. At some point the SDK drivers did install and I rooted successfully with KFU 0.9.3. Then I tried the TWRP install and had the same issue as the op. Stuck at the static Kindle Fire image. XP refused to recognize my KF and the drivers would not reinstall properly. Fastboot would remain at the "<waiting for device>" prompt when I used the fastboot -i 0x1949... bootmode command. I tried another route and booted a new OS X 10.7.3 vm and installed ADB/Fastboot. The same "<waiting for device>" prompt.
The problem had to do with the vmware usb implementation. I installed ADB/Fastboot to a non-vm install of 10.6.8 and my KF immediately responded to the bootmode command.
So if you're having a problem with the ADB/Fastboot drivers take a hard look at your usb setup.
I can't find any good rooting guides for linux. Anyone know where I can find one?
If you are administrator then all you have to do is to type sudo in the terminal window to execute commands as root. Or type sudo su to become root user during that terminal session.
Muikkuman said:
If you are administrator then all you have to do is to type sudo in the terminal window to execute commands as root. Or type sudo su to become root user during that terminal session.
Click to expand...
Click to collapse
I think he means rooting his phone while on linux.
I've rooted my phones (Galaxy Nexus and Nexus 4) on Linux. As far as I know there aren't any rooting guides for Linux users specifically, but the process is essentially the same as on Windows or Mac OS X.
The only difference is that you might come across of permission issues (like ADB not working without "sudo ./adb ..." when in recovery, Fastboot not working without "sudo ./fastboot ...", etc.) which can easily be fixed.
I can totally help you if you want.
alfonzo1955 said:
I think he means rooting his phone while on linux.
Click to expand...
Click to collapse
Jaja, yes.
starscream92 said:
I've rooted my phones (Galaxy Nexus and Nexus 4) on Linux. As far as I know there aren't any rooting guides for Linux users specifically, but the process is essentially the same as on Windows or Mac OS X.
The only difference is that you might come across of permission issues (like ADB not working without "sudo ./adb ..." when in recovery, Fastboot not working without "sudo ./fastboot ...", etc.) which can easily be fixed.
I can totally help you if you want.
Click to expand...
Click to collapse
If you could that'd be awesome.
You should search first... http://forum.xda-developers.com/showthread.php?t=1999065
If you running ubuntu or mint, commands like adb and fastboot are in the repos...just install them, and from terminal give: sudo fastboot (whatever you want) or sudo adb
I got it! I didn't know that all you had to do was sudo for whatever commands while the phone's in the bootloader. I thought I'd have to do something with the dll drivers. http://forum.xda-developers.com/showthread.php?t=2018179 says that you might need to install them, but I wasn't sure if this was a windows only thing.
Thanks a lot man!