Related
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
Hello, I install the android SDK correctly and install all correct drivers, all correct files from the google repository, and reading on unlockr, you need to type CMD and enter a few commands, the final one being ADB devices, which is meant to bring up your device serial/id but doesnt show nothing for me, i deleted all drivers with a program, and it re-installs them, I put the phone into debug mode too, but whatever i try, i cant root my magic (32B), please help!!!!
i have followed every single guide but cant blooming root my phone!!!
HELP!!!!!!!!
Install the HTC Sync software first. If this connects correctly and recognizes your phone, then the ADB will find it too. I use it as a test, whether the drivers are installed correctly or not.
To start the ADB, you have to navigate to the folder where the SDK was extracted using the CMD Prompt, and then into /tools. There you type ADB and the command you want to execute.
done that mate, going to /tools and then adb devices and its meant to say a device serial, but on mine it shows nothing
As far as I know, you have to have a recovery installed to access adb.
Write "fastboot devices" while in /tools to see if the drivers are OK. When you install a recovery, adb should be accessible.
I followed the wiki.
ADB finds my device when cmd prompt
Adb devices.
It runs first part of the code.
But it then tells me fastboot is not a command.
I read a few other posts, but have found no answer to this problem.
Am guessing im missing something. Maybe someone could help me find out what?
Via HTC Desire Z
ADB and fastboot are in two folders of sdk. In command you need to direct to that folder. ADB is in "platform-tools" and fastboot in "tools"
Example, from my computer.
ADB - cd C:\android-sdk-windows\platform-tools
Fastboot - cd C:\android-sdk-windows\tools
From that you can use fastboot commands.
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.
The purpose of this tutorial is not to teach you everything. It's just to give the less-than-average user (noob) an idea of why certain steps are taken and how to prevent and or troubleshoot problems that most people have when rooting or flashing ROMs on their device. I am also assuming that if you do decide to root your device you have at least a basic working knowledge of a computer. If you don't know what a desktop is or how to find the "any" key, you have no business being anywhere near a computer much less an android device…continue no further. Read my tutorial…If you like it, let me know. If I missed anything or got something wrong, let me know…I'll try to fix it. If you're impartial to it, I couldn't care less. If you hate it, PM me…I have some important information for you about anger management.
ROOTING
While there are different rooting "methods" they all rely on the same basic concept. Get temporary root access to your system in order to use the adb (Android Debug Bridge) to transfer necessary files and change permissions to permanently root (take ownership of) the device.
Before programs like KindleFireUtility and KindleWater, rooting the Kindle Fire was done manually through a command line interface (command prompt). Although those programs still use the same methods, you never see it. But why use command prompt? What do those commands mean anyway? Anyone can point and click but if you don't know what is going on behind the scenes then you are big trouble when things go wrong…and they inevitably will. So, let's get started.
From here on out we will consider this the beginning of the tutorial. Read everything first before doing anything. Pay close attention to what's being said and follow instructions carefully. Now...
Before anything your device needs to be fully charged and have the Android SDK and the Kindle adb drivers installed onto your computer. I'm not going to go into how to install SDK or Kindle adb drivers here because there are millions of pages on the internet that will teach you, and quite frankly that's not the purpose of this tutorial. That being said, lets get down to business and talk about the older (manual) methods of rooting the Kindle Fire.
First, lets start with the device turned on. Now go to your Kindle Fire settings and scroll down and select "Devices". Make sure "Allow Installation of Applications" is set to ON. This allows you to install apps not downloaded from the Amazon App Store. Next we open the App Store and search for and install a file management utility (ES File Explorer is a good one to start with). This will be necessary to temporarily root your device. Exit the App Store.
Now plug your device into the computer. For the purposes of this exercise there are two USB modes you will need to know, USB debugging and USB file transfer. On stock devices when you plug into your computer you will see a black screen that says "You can now transfer files from your computer to Kindle". This we will call USB file transfer mode. You will use this to transfer a program to your device that will give you temporary root permissions. The old program for this was ZergRush, nowadays its BurritoRoot and tomorrow it will probably be something else. Whatever it is, find whichever one works for your device's software version and transfer it to your device using Explorer (Windows) or Finder (Mac). Since you don't have root access yet, everything you put on your device for now will go directly to the SDcard partition, far away from system folders (for all intents and purposes).
Press "disconnect" on your Kindle Fire. Now, and by default, your Kindle is in USB debugging mode. What that means is that when you are not in USB file transfer mode your device is constantly listening for debugging commands coming from the USB port. We will be using this to send adb commands to the device which are necessary for rooting and setting up recovery. Now open the file management app you installed from the App Store, navigate to the temporary root program you transferred from your computer and open it. Install and follow the instructions, if any. Next go to your computer and navigate to your Android SDK folder and look for a folder called "platform-tools" if you don't see it, open the tools folder and double-click the file named "Android". Select "platform-tools" and install.
To make things simple, lets to take the platform-tools folder and place it on your desktop (just be sure to put it back when this is all over).
At this point we need to get Superuser. This is what we will use to give your apps root access. Go to http://www.androidsu.com/superuser and download the one for Gingerbread. Extract the superuser.zip file, open the folder and navigate to the system folder inside. There, inside the "app" and "bin" folders you will see two files called "superuser.apk" and "SU". Place them in the platform-tools folder that is now on your desktop. And now the fun part, it's time to start rooting.
Open your command prompt (or terminal for mac users) and type and enter:
cd Desktop/platform-tools
Here, you are telling the computer to cd (change directory) to the platform-tools folder located inside the Desktop folder. This is going to be your workspace. Everything you do from here on will be done from this folder. If you don't get any errors then you are in good shape. Otherwise you messed up somewhere and probably skipped a step...go back and read from the beginning. Make sure your Kindle Fire is turned on and NOT in USB file transfer mode. If you are not sure what mode you're in, go back to the beginning. If this is your second time around, stop. You need to learn more about how to change directories using command line interface.
When you are in the platform-tools folder, type and enter this command:
adb devices
Mac and Linux users will put ./ before all adb and fastboot commands from here on out. It will look like: ./adb devices
Here you are using the adb program to print a list of connected devices. You should see a bunch of numbers that mean nothing to you at this skill level. Move on. If you don't see any numbers then you either don't have your drivers installed properly or you skipped a step; go back to the beginning.
If you do get a bunch of numbers your device is connected. Now type and enter:
adb root
...gives root permissions to the adb
adb remount
...mounts the system partition to a "read/write" state allowing you to make changes to system files and folders. Consequentially, if you enter adb remount a second time, you will change it back to "read only". Don't do that.
adb push su /system/xbin/su
...will push (transfer) the file named "SU" that is in your workspace (platform-tools folder) to the su folder inside the xbin folder of your device's system folder. The SU binary file is what other apps call to when they need superuser rights.
adb shell chown 0.0 /system/xbin/su
...this is where it gets a little funky. It opens a shell interface within the adb in order to chown (give ownership permissions) to user 0.0 for the su folder. A shell is a piece of software with a particular set of commands built in to act as sort of a go-between between the user, operating system and hardware kernel services. But who is user 0.0? [Edit:] User 0.0 is the root user. Thanks to b63 for that piece of knowledge
adb shell chmod 06755 /system/xbin/su
...opens a shell within the adb to chmod (change mode) of the su folder to 06755. What that basically means is you are changing the folder permissions to rwxr-xr-x or read/write/execute for the owner, and read/execute for the group and others.
adb install superuser.apk
...installs the program superuser.apk located in the platform-tools folder. Superuser.apk maintains a database of what apps you allow to access SU binary file.
That's how the rooting process works. Again if you get any errors, you did something wrong. Go back to the beginning and read it all over again. Attention is key.
Also, I suggest you skip the one-click methods for rooting and get used to using the command line interface so you understand how the process works in order to quickly troubleshoot problems should they arise. Oh and congratulations, you are rooted.
RECOVERY
Now lets install a custom recovery utility and a new boot-loader. For this you will be using the fastboot command. Before we go on, one thing you absolutely must get your head around is the difference between how fastboot interacts with your device versus how adb interacts with your device. fastboot deals with the boot portion of the device whereas adb only deals with the system portion. What that means is adb will only work when the device is completely booted. If for some reason your device doesn't boot properly then you should not be issuing adb commands. It's like trying to light a match in a vacuum. Fastboot works in the same way in that you must be in the fastboot bootmode in order to issue fastboot commands. Unless you have custom recovery installed or a factory programming cable there is only one way to get into fastboot mode. We'll talk about that later.
Installing recovery is a simple process but it is where people tend to have the most problems. Part of the reason is the misunderstanding of the different bootmodes. For now, you only need to be concerned with two of them; normal bootmode (4000) and fastboot bootmode (4002). The main reason people run into trouble is that once you are in a particular bootmode, it doesn't change until you tell it to (with the exception of temporary fastboot which we will get into later).
In normal bootmode your device will boot...normally (imagine that). With the fastboot bootmode the boot-loader will hang at the Kindle Fire splash screen (or yellow triangle if you have recovery installed) to wait for further commands. If this happens to you, chances are your only problem is you are in the wrong bootmode, which is easy to fix. Knowing that, installing a custom recovery should be a breeze.
First find whatever recovery you want to use (unzip it if you have to) and place the .img file into your platform-tools folder that you were using earlier. We're going to use adb to change the bootmode to fastboot in order to install custom recovery. Remember, anything that pertains to the boot-loader, (Kindle Fire logo/yellow triangle) will be done in the fastboot bootmode; that includes custom recovery installation. For more information on Kindle Fire bootmodes, boot-loaders, fastboot and just about everything else, see this post:
http://forum.xda-developers.com/showthread.php?t=1552547
From your command prompt type and enter:
adb shell
su
idme bootmode 4002
reboot
What that does is tells adb to open a shell and su (substitute user) for the root user, change the bootmode from normal (4000) to fastboot (4002) and reboot. The root user has the necessary permissions to change the bootmode from the adb. Your device will reboot then hang at the splash screen because it is in the fastboot bootmode.
Now install your custom recovery (we'll call it customrecovery.img for now)
fastboot -i 0x1949 boot customrecovery.img
again, for Mac and Linux you would type: ./fastboot -i 0x1949 boot customrecovery.img
That tells your computer to, using the fastboot program that is in your platform-tools folder, boot the device with the ID of 0x1949 (your Kindle) with the file named "customrecovery.img"
After installation, reboot, but you will still be in the fastboot bootmode. So type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
…tells the device to reset the partition where the recovery(?) is located, change the bootmode to normal (4000) and reboot.
TROUBLESHOOTING
Flashing custom ROMS are another source of frustrations as they add too many variables to the equation. Some ROMS can be very unstable and cause weird things to happen to your device. But just knowing how this stuff works will help you fix 90% of the problems that may come up. If you are having trouble with your device, troubleshoot the problem:
Does the device turn on?
No
Is it fully charged?
No--> Charge it
Is it fully charged?
Yes--> Hold the power button for 30 seconds and restart
Does the device turn on?
No--> Hold the power button for 3 minutes and restart
Does the device turn on?
No--> Google search "Motorola USB factory programming cable"
Does it boot normally?
No
Do you have custom recovery installed
No--> You need to get into fastboot mode to issue fastboot commands. Google search "Motorola USB factory programming cable"
Do you have custom recovery installed?
Yes--> During the first 5 seconds of seeing the boot splash screen (this is temporary fastboot mode that comes with custom recovery) issue fastboot command to change bootmode to 4000. Reboot
Does it boot normally?
No
Can you get into recovery?
No--> During the first 5 seconds of seeing the boot splash screen (temporary fastboot mode) issue fastboot command to install a new customrecovery.img. Reboot.
Can you get into recovery?
Yes--> Re-flash your ROM. Reboot.
Does it boot normally?
No--> Enter recovery, factory reset, wipe cache, wipe dalvik cache, re-flash your ROM. Reboot
Does it boot normally?
No--> Enter recovery, factory reset, wipe cache, wipe dalvik cache, flash a different ROM. Reboot
Does it boot normally?
No--> Post your problem on the XDA forum. Include all pertinent information such as what rom you are using, what the exact problem is, what you were doing before the problem occurred and all the steps you have taken to try and fix the problem.
Does it boot normally?
Yes--> Give yourself a pat on the back, because you rock!
Do you Rock?
No--> Start over from the beginning
nice
--sent from my glacier.