Hi all,
I got a refurb 8.9 HD for basically free, so I want to flash the best current ROM onto it (which it looks like is CM11 at the moment). I'm having a bit of trouble getting the device into fastboot mode:
What I've accomplished so far:
Have adb and fastboot working in the command prompt
Installed the amazon usb drivers, kindle shows as Android Composite ADB Interface in device manager
Device is recognized by adb devices (shows serial number + "device")
Turned "Enable ADB" to ON in security settings
However, when I unplug the kindle, execute the "fastboot -i 0x1949 getvar product" command, I do get the <waiting for device> message, but when I plug in the turned-off Kindle, I get two quick chimes, then a second later the "device disconnected" sound, then the kindle boots as normally, and nothing happens in the command prompt.
It may be worth noting that when I first connected the Kindle (after installing drivers) I didn't get the "Enable USB Debugging" pop-up that two guides mentioned. Thoughts?
You must be doing it in the wrong order
1. turn of your kindle
2. connect your wire
3. open cmd and type fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
4. now turn on your device it should go into fastboot
Did you get it to work? And are you running 8.5.1? Because that's what I'm running and I'm having the same problem. I've seen solutions all over the place for 8.4, nothing for 8.5. Amazon seems to have a real lockdown on it.
Related
im not sure where to go from here. I attempted to use the Kindle fire Utility to install "permanent root with superuser" on my stock KF. it seemed to be doing its thing until it rebooted and just hangs at the white and orange "kindle fire" logo now.
i have since been searching everywhere for a fix. When I stumbled across this thread (thank you) i made my own factory cable and reinstalled all the drivers and such (which seem to load fine when comparing them to the pics in the op anyway).
My problem is when i try to do anyting with adb or fastboot commands i just recieve a "waiting for device" message.
im pretty sure my factory cable works because my KF starts with it. with another usb cable i just reciceve a mesasage that the KF's battery is too low.
any help would be so much appreciated. thanks in advance!
All the factory cable does is put it in fastboot and your trying to get out of fastboot. Power the kindle off issue the command fastboot -i 0x1949 getvar product (hit enter) when it says waiting for device plug it in powered off with a regular cable not the factory one it should then power on if you get the response product: kindle the type fastboot -i 0x1949 oem idme bootmode 4000 (hit enter) it should say "okay" then type fastboot -i 0x1949 reboot (hit enter) it will say "rebooting" then it will boot in normal mode. Good luck
Edit: also if plug in via usb possibly get that battery some juice if it will not charge your looking at this http://forum.xda-developers.com/showthread.php?t=1430038 to send a bootloader that will charge under low battery conditions
I was waiting for a mod to move this question out to its own thread before I replied. It looks like they didn't get around to it until early this morning.
KFU appears to have a habit of leaving devices in fastboot mode. This usually happens because the device drivers have not been installed or they are not loading properly. You should look into that first.
This guide...
http://forum.xda-developers.com/showthread.php?t=1668159
will tell you if you are actually in fastboot mode.
This guide...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
will tell you if the device drivers are installed and loading properly.
I've also been told that there are some problems with fastboot and USB 3.0 ports. If you are using a newer machine with USB 3.0 ports, try moving the cable to a USB 2.0 port and see if that helps you.
What kinfauns is saying about 3.0 vs. 2.0 is indeed correct once fastboot is initiated the 3.0 usb port literaly stonewalls further communication to and from the device only a 2.0 usb port will work.
After successful root of my kindle fire 2 I moved to next step to install fire fire fire bootloader.
It did not go through by setting bootmode to 4002 and I looked at normal boot value.
Surprisingly, it was 1 instead of 4000.
So decided to set it to 2 (issuing 'idme bootmode 2' with superuser via adb)
After reboot kindle showed 'A n d r o i d' text followed by following screen:
IP = 192.168.101.101
DIV = KC1A3A04-20120809
SN = SOMESERIALNO
MAC = SOMEMACADDR
BATTERY=100
BMID=SwE
TOUCH FVER= 10.2.6.0
I can see the device in Windows device manager as Android ADB Interface, but neither adb nor fastboot can comunicate with device.
I do not own factory cable.
How can I return it to normal boot?
Thank you
dedolini_xda said:
After successful root of my kindle fire 2 I moved to next step to install fire fire fire bootloader.
It did not go through by setting bootmode to 4002 and I looked at normal boot value.
Surprisingly, it was 1 instead of 4000.
So decided to set it to 2 (issuing 'idme bootmode 2' with superuser via adb)
After reboot kindle showed 'A n d r o i d' text followed by following screen:
IP = 192.168.101.101
DIV = KC1A3A04-20120809
SN = SOMESERIALNO
MAC = SOMEMACADDR
BATTERY=100
BMID=SwE
TOUCH FVER= 10.2.6.0
I can see the device in Windows device manager as Android ADB Interface, but neither adb nor fastboot can comunicate with device.
I do not own factory cable.
How can I return it to normal boot?
Thank you
Click to expand...
Click to collapse
I think you need to read this before you do anything else to your device
http://forum.xda-developers.com/showthread.php?t=1928866
soupmagnet said:
I think you need to read this before you do anything else to your device
http://forum.xda-developers.com/showthread.php?t=1928866
Click to expand...
Click to collapse
Thank you, read it.
What I did not understand is my kindle already bricked?
I think your first step should be getting a fast boot cable. My suggestion is not to try anything else from the kf1 threads.
Sent from my Nexus 4 using Tapatalk 2
So far your device is still salvageable. Turn the device off, enter the command "fastboot -i 0x1949 getvar product" then turn the device on when you see "waiting for device". When it boots (if it's like any other KF), it will activate fastboot and you will get an output of "kindle". If not, you need to acquire a factory (fastboot) cable. And you still need to make sure your drivers are working properly.
soupmagnet said:
So far your device is still salvageable. Turn the device off, enter the command "fastboot -i 0x1949 getvar product" then turn the device on when you see "waiting for device". When it boots (if it's like any other KF), it will activate fastboot and you will get an output of "kindle". If not, you need to acquire a factory (fastboot) cable. And you still need to make sure your drivers are working properly.
Click to expand...
Click to collapse
I have ordered fastboot cable and i am awaiting delivery.
Drivers should be fine - they are latest from android sdk and composite driver connected me to adb just ok.
fastboot i try to use also is from latest android sdk.
after issuing getvar product fastboot command, waiting for device
stays for way too long
Since on kindle's screen some ip address is displayed, i wonder if in this bootmode some othe communication with device could be possible?
I am trying to install Cyanogenmod on my kindle fire. However, before I was able to start flashing any images or anything like that, I ran into a problem (although this is probably the best time to have a problem). My Kindle Fire HD 8.9 won't enter fastboot mode.
I'm running Windows 7.
I installed the android SDK.
I installed Amazon's drivers for the Kindle Fire.
When I type in "Adb drivers" into the command line, I get my serial number.
When I type in "fastboot drivers", I don't get anything back.
When I type in "fastboot -i 0x1949 getvar product" , I get "waiting for device", I plug in my Kindle Fire HD 8.9 (Edit: when it is off), but it just says at "waiting for device".
I've tried typing ""adb reboot-bootloader", but that reboots the device normally.
I've read that I don't need a fastboot cable for the Kindle Fire HD 8.9 (unlike the 7).
What am I doing wrong?
Power OFF
Have you tried connecting your Kindle while POWER OFF. (Pressing power button for 20 Sec)
Steps
1. Go to elevated command prompt (admin command window)
2. type "fastboot -i 0x1949 getvar product", "waiting for device" should display on screen
3. Power off Kindle (20 sec press of Power Button)
4. Connect kindle to PC
It should go into Fastboot mode.
This will work. Hit Thanks if I helped you.
Didn't work.
mgaju said:
Have you tried connecting your Kindle while POWER OFF. (Pressing power button for 20 Sec)
Steps
1. Go to elevated command prompt (admin command window)
2. type "fastboot -i 0x1949 getvar product", "waiting for device" should display on screen
3. Power off Kindle (20 sec press of Power Button)
4. Connect kindle to PC
It should go into Fastboot mode.
This will work. Hit Thanks if I helped you.
Click to expand...
Click to collapse
I had already tried that without success. I tried it again, but it just booted into normal mode. I know i must be doing something wrong, but I'm not sure what.
ajshell1 said:
I am trying to install Cyanogenmod on my kindle fire. However, before I was able to start flashing any images or anything like that, I ran into a problem (although this is probably the best time to have a problem). My Kindle Fire HD 8.9 won't enter fastboot mode.
I'm running Windows 7.
I installed the android SDK.
I installed Amazon's drivers for the Kindle Fire.
When I type in "Adb drivers" into the command line, I get my serial number.
When I type in "fastboot drivers", I don't get anything back.
When I type in "fastboot -i 0x1949 getvar product" , I get "waiting for device", I plug in my Kindle Fire HD 8.9 (Edit: when it is off), but it just says at "waiting for device".
I've tried typing ""adb reboot-bootloader", but that reboots the device normally.
I've read that I don't need a fastboot cable for the Kindle Fire HD 8.9 (unlike the 7).
What am I doing wrong?
Click to expand...
Click to collapse
I'm in the slow lane now after trying numerous ways to root this 8.9 8.5.1 fire. Still not showing root but everything goes slow now.
Guess its better than a brick. Wonder if I can load a CM since my root failed.
ant17 said:
I'm in the slow lane now after trying numerous ways to root this 8.9 8.5.1 fire. Still not showing root but everything goes slow now.
Guess its better than a brick. Wonder if I can load a CM since my root failed.
Click to expand...
Click to collapse
Update: restored settings, back to fast but no root.
ajshell1 said:
I had already tried that without success. I tried it again, but it just booted into normal mode. I know i must be doing something wrong, but I'm not sure what.
Click to expand...
Click to collapse
Anyone figure this out? Having the same problem - won't boot into fastboot mode, just boots normally (with cable plugging in and fastboot waiting on the device). Adb also works fine.
Install android studio and get the drivers from that.
Same Problem on Kindle Fire 8.9 HD - Fastboot not work!
Hi,
I have the same problem. Adb works, fastboot doesn't work on my stock Kindle Fire HD 8.9" 2nd Generation. Here is my environment:
Windows 10 Pro x64 with latest MS Patches, Toshiba Patches, Intel Patches
BitDefender Anti Virus
ADB enabled on Kindle
Adb and fastboot Drivers installed via Android SDK
Kindle Driver install downloaded from Amazon
PC is new Toshiba Satellite P50W with USB 3.0
Drivers look okay in Device Manager
- Kindle Fire -> Driver = Android Composite ADB Interface provided by Amazon dated 12/3/2012
- Portable Devices / Kindle -> Driver =provided by Microsoft dated 6/21/2006
Symptoms:
ADB Commands work including adb kill-server, adb start-server, adb devices (returns Serial Number)
- Fastboot -i 0x1949 getvar product shows "waiting for device" in PC's CMD Window and never goes away
- I attach standard USB Cable to the Kindle that is currently Powered Down (not just sleeping) after issuing above command on PC
- Attaching USB Cable simply causes Kindle to power on and boot normally.
What I have unsuccessfully tried to date:.
Tried alternate commands:
- adb reboot bootloader (to start Fastboot)
- fastboot -1 0x1949 reboot (to exit Fastboot)
Tried USB 2.0 Port instead of 3.0 Port.
Tried reloading Kindle Drivers.
Trying Android Platform Tools Ver 23.1 RC1 instead of Ver 23.01
Tried two different "Standard" USB Cables, one Factory Cable by itself
Any Ideas? I've been trying to get FASTBOOT working so I can play with Cyanogenmod for a couple of days without any luck. Thanks.
Ken (Android Noob )
Same
Having the same issues on 5.1.1 5th gen 8.9HD. zero fastboot....
I'm having the same issue. Has anyone found a solution or found another way to root the device with version 8.5.1_user_5159720 installed?
Hate the Kindle version of the OS. I want to install CM or LineageOS (If I can find a build for it!)
Thanks!
---------- Post added at 11:33 AM ---------- Previous post was at 11:08 AM ----------
Sailing_Nut said:
I'm having the same issue. Has anyone found a solution or found another way to root the device with version 8.5.1_user_5159720 installed?
Hate the Kindle version of the OS. I want to install CM or LineageOS (If I can find a build for it!)
Thanks!
Click to expand...
Click to collapse
I did a bit more digging and found a tool that will root the device. You can find it at https://rootmaster.co Just download and install the APK on your device and allow it to root.
emaster101 said:
Having the same issues on 5.1.1 5th gen 8.9HD. zero fastboot....
Click to expand...
Click to collapse
this is a COPY/PASTE of my own post. the files i specify are the exact names, just search this section of X-DA for them. SEE BELOW.
i had the same problem with the "red screen of death" as well. i found that if i installed the "Minimal ADB and Fastboot" and / OR (i did the minimal first.... ) KFHD_SRTv1.3.5 and RUN THE APP FIRST, then when it says "waiting for device" you then plug in the ALREADY OFF tablet it then WORKS!! says "fastboot mode" on the tablet. and it is listed in device manager also.
i got BOTH apps here at this board in this section.
WARNING: i run windows XP with all updates as of 10-31-2017 (pm me for info, 2 lines of text!! ) . NEWER windows versions have "permission issues". fixes are posted in multiple topics here in the Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2 section. READ THEM!!
Start by turning off tablet. type in "fastboot -i 0x1949 getvar product". Get (waiting for device) message. Plug USB into tablet.
Hi Guys!
Picked up a refurb Kindle Fire HD 8.9 on Woot the other day and want to stick CM 12.1 on it. I'm no programmer but I've successfully followed directions to root and install CM on about a dozen devices over the years but this one has me stumped.
I'm running Windows 10 and have apparently successfully installed the Amazon USB driver. When the tablet is plugged in Device Manager shows "Fire Devices > Android Composite ADB Interface" and it reports "working properly." I made sure to install the driver with Windows driver signing OFF. I can do a command prompt "ADB devices" and I get back a single device which corresponds to the device Serial Number (when I disconnect the tablet, I get nothing). So it seems ADB can find the tablet. The tablet has "Enable ADB" set to ON. I have done nothing else with the tablet, no registration, nothing, it's direct from factory and seems to be working fine. Current system version is 8.4.3_user_4308820, I have not updated it from what it came with.
So everything looks good until I try to run fastboot. I punch in "fastboot -i 0x1949 getvar product" and get "waiting for device". I reboot the tablet and it just simply reboots like normal and brings up the lock screen. I can't get Fastboot to show. I've done a simple shut down/reboot, I've held the power button down for like 20 seconds and forced power off. I've also tried plugging into different USB ports and different USB cables. Still nothing, just "waiting for device".
Can anyone offer suggestions to get to Fastboot? Many thanks in advance!
Are you generating your command prompt in the folder where fastboot.exe (and ideally also adb.exe) is located? If not, do so. When you get the "waiting for device" prompt with fastboot, are you then plugging in your powered OFF Kindle? This is one way that fastboot operates in our Kindles. There is also the modified factory cable that will automatically reboot the Kindle into fastboot mode (see the following video: www (dot) youtube (dot) com/watch?v=FFoAvnf7YUQ). Alternatively, you can try using ADB to reboot the device into fastboot as shown in the video. Good luck!
I wanted to root my razer phone 2 because I rooted my old Samsung, but after unlocking my bootloader I decided against it and now ive spent about 2 days trying to lock my bootloader again with no luck.
ive tried many different usb drivers and non of them show my device under the "fastboot devices" command in adb or fastboot but I can show the device under adb devices which im aware is rather easy
ive seen many people have this issue but they don't really show/tell how its fixed! ive tried different usb sockets too!
the device name in my device manager is "SAMSUNG Android Phone" (while the phone is in fastboot mode) with the sub driver called "Android Bootloader Interface" if anyone has any kind of advice or tips to get my bootloader locked again please share!
okay, so after a lot of looking around.. I found this.
"1) - To unlock the razer phone bootloader do the following
2) - Install ADB + Fastboot and google usb drivers
3) - Enable developer mode by going to settings, about phone and hitting build number a bunch of times. then go back to settings > developer options and check USB Debugging and OEM Unlock.
4) - Open a command prompt on your PC and connect the phone's usb cable to your computer. Accept the prompt on the phone for trusting the computer when plugged in.
5) - type the following in command prompt without quotes "adb reboot bootloader"
6) - You'll be at the download mode screen with the razer logo.
7) - Make sure the driver for ADB Bootloader Interface was installed. If not you'll probably have a device called Android under "Other devices" in device manager. If this is the case, install the google usb driver.
8) - In command prompt type the following without the quotes "fastboot -i 0x1532 devices" and make sure your device comes up and not just a blank response.
9) - If it came up now just type without the quotes "fastboot -i 0x1532 flashing unlock"
10) - This will bring up a prompt on the phone itself to unlock the bootloader, use the volume button to navigate to yes and press the power button to confirm.
11) - The phone will reboot and will show a message stating "Your device is unlocked and cannot be trusted" on each boot to show that it is unlocked."
FIX - it was the "fastboot -i 0x1532 devices" I was doing wrong.. I was not putting the "-I 0x1532" i now feel stupid.. but idc i locked my phone and im back to stock finally! (ill probably end up trying to root it again some point in the future :| )