Hey guys,
After trying for the past two days and a lot of hours to get a good enough grasp to undo a hasty attempt at rooting my kindle, I've decided to come to you with a request for help!
It all started when I installed the amazon usb drivers for kindle fire and then loaded up KFU. It read that my kindle was in boot mode 4000 (normal boot mode) and I told it to root my device. It seemed to be working fine, until all the sudden, it froze as it was trying to load TWRP onto my kindle. AFter waiting some amount of time, I finally just cancelled the job and tried to reset my kindle.
Ever since my kindle is stuck at the stock loading screen. No FFF, just the regular kindle fire logo and it never dims in light, which is a clear indication that it is in fastboot, and isn't going anywhere. Well at that point, my windows drivers failed me and ceased to recognize my kindle. Well, I tried everything to get windows to recognize the device but it failed. I even tried creating a bootable ubuntu partition and using the linux drivers with firekit. It didn't really work as well as I'd have liked.
Recently, I used my roommate's macbook and fastboot to try and see if there was any hope for communicating with my kindle.
The "./fastboot -i 0x1949 getvar products" command returned "product:kindle" suggesting that the macbook recognized my kindle.
YAYY!
but when i tried to reset the bootmode to 4000, it just sat there with three dots and did nothing. i tried to flash TWRP again, same thing. Each time i would cancel the job and then when i went back to try and recognize my kindle, even the macbook had lost it.
Ideas?
Hold your power button to shut it off, then start it up again. Does the display stay brightly lit?
Related
Hi all,
I have a Kindle Fire HD 7" which I rooted following directions here which went fine and I've been using the rooted kindle for a few weeks. Today when I turn my KFHD on it just sits at the logo screen (no animation or anything) and refuses to boot.
I've tried hard resetting it (holding power button for 30 seconds) which did not help. I found this thread which seems similar to my problem. I was able to add a new vendor ID to the drivers and get the KFHD to show up in device manager when plugged in. However, if I try to use the fastboot command to force it to reboot it sits at "< waiting for device >".
If I do an "adb devices" the KFHD shows up there but I'm unable to do "adb shell". For most adb commands I try it simply sits at < waiting for device >". I'm hoping this means that it's at worst only soft bricked. Interestingly "adb reboot" does work but it goes back to sitting at the logo after rebooting. Does anyone have any suggestions about what to try next?
Does anyone know if the KFHD has a recovery mode I can boot into? I read a few threads that say you can access a recovery/safe mode if you hold down the up-volume button when you power on (and another that says both up and down volume buttons) but I've had no luck with that. It doesn't seem to change anything.
A little more background:
What led to my problem was that I decided to experiment with BotBrew since I'm interested in trying to compile some Linux code to run on Android. The app installed fine and I was using my KFHD normally when all of a sudden I started to repeatedly get a force close messages on some apps (I remember correctly I believe it was the keyboard). Since the message kept popping up I shut down the KFHD and when I attempted to turn it on next this began.
you should post in the HD question thread, not here in the kf1.
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!
My mistake, thought I was in the right forum, but I read the name wrong!
So here's what happened.
About a year ago, I rooted my Kindle and flashed CM 10.1. Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but figured it'd be important to install the latest version of TWRP as well. Before I knew it, my Kindle Fire was bricked. In the process of updating TWRP, I downloaded and flashed the most recent img file (using Flashify), and after the device rebooted automatically, it wouldn't move past the silver/orange "Kindle Fire" screen. I've since tried a number of things, including powering the device on and off, and holding the volume up button to boot into TWRP, but nothing seems to work. I always end up getting stuck at the same screen.
I've also tried using Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses communication.
Am I screwed?
arthurk62 said:
So here's what happened.
About a year ago, I rooted my Kindle and flashed CM 10.1. Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but figured it'd be important to install the latest version of TWRP as well. Before I knew it, my Kindle Fire was bricked. In the process of updating TWRP, I downloaded and flashed the most recent img file (using Flashify), and after the device rebooted automatically, it wouldn't move past the silver/orange "Kindle Fire" screen. I've since tried a number of things, including powering the device on and off, and holding the volume up button to boot into TWRP, but nothing seems to work. I always end up getting stuck at the same screen.
I've also tried using Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses communication.
Am I screwed?
Click to expand...
Click to collapse
Can you get into fastboot? Did you restore your backup?
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
skullarc said:
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
Click to expand...
Click to collapse
I had a feeling that must've been the case.
I followed your directions, but can't get past the "<waiting for device> message in CMD. Turning the kindle on or off doesn't seem to make a difference. Am I doing something wrong? Are there other alternatives?
Did you follow the steps in the right order
Turn of Kindle
connect the wire
type command
when waiting for device is shown then only turn on your kindle
Similar Problem
skullarc said:
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
Click to expand...
Click to collapse
I have a similar problem. I try to give the "fastboot -i 0x1949 getvar product" in windows cmd but it just gves an error. Do I need to install something to fix this
My guess is you don't have the right drivers installed. You have to install the driver while the device is attempting fastboot. If you have the device manager up you'll see it flash for a second when it boots. Right click when it flashes and install the driver.
Before I begin, trust me when I say I have scurried through dozens of Google results, forums, blogs, YouTube videos, FAQ's and other things trying to find out how to unbrick this thing. I have a Kindle Fire first gen which I rooted using Kindle Fire Utility through superuser 3 days ago. All was well, as I had google play and an innovative new launcher. After downloading a few apps, I thought that I had finally made the Kindle the fully-functional Android tablet I had desired. However, after a few hours of seamless use, the Kindle decided to freeze on me. Holding the power button still brought up the "Do you wish to power down your Kindle?" notification, and I shut it down, planning on restarting it. However, when I turned it back on, it would not get past the animated Kindle Fire logo. The weird part was, I could still hear notification tones. I was using my phone to DM on Twitter, and when I would get a message back, I could hear the twitter notification on my Kindle. (No, I was not mistaking it for the phone). After a while, I could hear that sound it makes when the battery was about to die. I plugged it in, and after two hours I unplugged it, held the power button to shut it down, and started searching google for answers. I was advised to use the Kindle Fire Utility to launch it in fastboot mode, which only restars the Kindle with no success. I have tried all options on the KF utility, even Permaroot. If I install TWRP recovery, it gets stuck on waiting for device. On most options, it gets stuck on waiting for device. (I have tried all the unplugging, unpowering options I saw). The computer makes a sound when the KF is plugged in, but it doesn't come up on the devices with removeable storage tab. I have all drivers installed, it is ADB enabled through the device manager, I have the Java Developer Kit, as well as Android SDK. The only thing I can get any utility to do (I have tried many such as Kindle Brick, SuperOneClick,etc) is restart the Kindle as if I did it myself. It still makes all the notification tones I mentioned earlier. One thing I have noticed, though, is that when the Kindle is 10 seconds from dying, the Unlock Screen will appear with no response. I have tried several times to let it get to that point, then quickly plug it in, but no sucess. It just restarts on the same boot screen. I have no idea what to do. I'm not a developer by any means, but I'm good with following directions I'm given to mess with computers and such. I don't have much knowledge of the command prompt, either. I just made this post as a last resort. Someone please help. (Running Windows 10 techncinal preview on a Windows 8, 64-bit laptop if that helps)
Do you know which system version?
Kindle Fire Utility doesn't root the latest system version.
Guessing that you rooted older version, then Kindle downloaded and installed newer system version, it would not ask for permission.
New system version may not have installed correctly.
If system was updated, Kindle lost root.
When powered off, connect to wall charger, does it charge?
Couple of options
See if you can force fastboot mode with adb commands
Or buy a fastboot cable
Then flash fff and twrp so you can reinstall stock rom
See
[6.3.3] Flashing FFF and TWRP without Fastboot Cable
Sent from my XT912 using Tapatalk
I've had a 1st Gen Kindle Fire HD 8.9 (or jem-pvt-prod-04) for ages. Rooted it years ago using KFFirstAide, which installed ADW Launcher (I think), but I never took the custom ROM plunge, and now I hardly ever look at it anymore. When I was thinking about installing custom ROM on my phone for the first time, I thought I'd get some practice on a device I don't mind losing (since I barely know what I'm doing...). Had the Kindle in Fastboot Mode and tried to flash different bootloader & recovery (from http://forum.xda-developers.com/showthread.php?t=2128175 ), and I probably flashed something I shouldn't have and corrupted the bootloader:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 reboot
Upon rebooting, the Orange Kindle Fire logo appeared, and froze (it never became animated or turned blue). It is now stuck there. I have held down power button for 30+ seconds, I have tried that with and without using vol down and vol up buttons. I have fully depleted the battery and recharged. I have attempted six ways to Sunday to get my computer to recognize the device so I could issue ADB or Fastboot commands, but when I connect the USB cable and start up the Kindle, Device Manager (I'm on Win 10) sees it as Android Device and shows Android ADB Interface driver for literally one second, then sees the device as disconnected. When I show hidden devices, I can update the driver for that device, and I've tried various ones, but all to no avail. I went further out on a limb and created a Ubuntu Live USB (though I have never used a Linux OS on my PC). I tried to get Java and SDK working in Ubunto OS, but I'm way out of my depth.
If anybody has any suggestions (other than quit doing things to your devices that you don't fully understand...), or can help me try other ways to get the device recognized and able to receive ADB/Fastboot commands, I'd really appreciate it.
Okay,
So I had an old kindle fire, wanted it to be an android tablet, blah blah blah
I rooted it, successfully installed TWRP and otterx and all even had it up and running
decided I wanted to try an otterx ROM and long story short while I was in fastboot mode I clicked an EXE. on my pc titled "FlashAll" without realizing what it was doing I had closed the prompt but when I looked at the kindle on the fastboot mode screen the bottom left corner said
"Erasing boot...
OKAY!
Erashing Cache..."
by this point I had already unplugged
So i tried a hard reboot
the screen stays black the power button lights up orange
but If i power it off and plug it in it goes to the "Fastbook Mode" screen but will not connect to the computer (windows 10)
I've checked the device manager and it is not there under any name whatsoever
there is no noise when its plugged in
I've traid fastboot and ADB commands and keep getting the <waiting for device>
I've tried KFU and Kindle Unbricker
I'm just at a loss i've gone through about 100+ posts and can't find a way to make my computer recognize a kindle that has no boot files
thenikm said:
Okay,
So I had an old kindle fire, wanted it to be an android tablet, blah blah blah
I rooted it, successfully installed TWRP and otterx and all even had it up and running
decided I wanted to try an otterx ROM and long story short while I was in fastboot mode I clicked an EXE. on my pc titled "FlashAll" without realizing what it was doing I had closed the prompt but when I looked at the kindle on the fastboot mode screen the bottom left corner said
"Erasing boot...
OKAY!
Erashing Cache..."
by this point I had already unplugged
So i tried a hard reboot
the screen stays black the power button lights up orange
but If i power it off and plug it in it goes to the "Fastbook Mode" screen but will not connect to the computer (windows 10)
I've checked the device manager and it is not there under any name whatsoever
there is no noise when its plugged in
I've traid fastboot and ADB commands and keep getting the <waiting for device>
I've tried KFU and Kindle Unbricker
I'm just at a loss i've gone through about 100+ posts and can't find a way to make my computer recognize a kindle that has no boot files
Click to expand...
Click to collapse
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
Sent from my PH-1 using XDA Labs