Ok. Let me preface this with I know that there are many different forums/posts/discussions/whatevers concerning that the first generation Kindle Fire gets stuck in a bootloop. I have scoured the web and tried every solution I could find. The most recent one was using the soupkit to try and fix it. I even bought a factory cable to attempt to gain access to fastboot mode for the soupkit. With a normal USB cable, the soupkit recognizes the kindle fire with adb access. When I connect the factory cable, however, neither fastboot commands or adb commands work. The kindle fire has no animation at all and just stays at the white and orange kindle fire logo, regardless of a cable plugged in. The battery is charged, as indicated by the LED light and the fact that it will stay on when not connected to a power source. The kindle has been in this state for month, but if I recall correctly it was running Jelly Bean. Then, I was trying to get back to the stock Amazon OS. I flashed their files, but apparently that just bricked the kindle fire. Sorry for such a long post, but anything is worth trying at this point. I have access to all operating systems as far as computers go (Linux, Mac OSX, and Windows XP) Thank you in advance.
Sent from my Galaxy Nexus using xda app-developers app
I think you tried to flash the stock firmware for the 2nd gen kindle fire. for the original kindle fire the firmware will always be in the 6.x.x range. for the second gen it will be in the 10.x.x range. I'm sorry to say though i'm not going to be any help here because i haven't ever hit a brick on my kindle (just on my Optimus V). If you look in the general section i think there is an unbrick utility though. Post results.
I do remember someone said that when they used kfu on xp it works fine. You may want to use it so that you can restore as kfu gas the ability to restore it.
Sent from my YP-G1 using Tapatalk 4 Beta
Use Linux and this to correct your boot mode http://forum.xda-developers.com/showthread.php?t=1850038 xp flat sucks when it comes to easy driver installs.
Thepooch said:
Use Linux and this to correct your boot mode http://forum.xda-developers.com/showthread.php?t=1850038 xp flat sucks when it comes to easy driver installs.
Click to expand...
Click to collapse
Oh I'm sorry I meant Windows Vista not XP
Sent from my YP-G1 using Tapatalk 4 Beta
Related
I'm tired of searching Google for answers and not finding them. So the problem is my Kindle Fire won't connect via USB to my PC, it will charge on it though. Now, this is where MY SITUATION IS DIFFERENT. Yes that is all caps for people who want to skip over these crucial details.
Kindle Fire was rooted, now it is not.
I do not have a Kindle Fire or Amazon device under device manager
Installing the adb drivers does nothing
I see nothing when Kindle Fire is plugged in to PC other than it is charging, NO MATTER HOW I DO IT
I feel like I'm forgetting some of the other more common answers that don't apply to me. Basically, I want to connect to my Kindle Fire to my PC but I have nothing on the PC end to recognize the Kindle Fire. It was rooted using the Kindle Fire utility 0.9.6, I unrooted using said utility as well and had to go and manually delete something IIRC so that it would boot normally into Kindle Fire, but it also not takes a lot longer to boot than it did out of the box. Is it possibly still rooted?
ALSO, Kindle Fire utility 0.9.6 can't find the Kindle Fire either.
What do I do?
Dou you have custom recovery installed?
I don't believe it did, or does. Whatever KFU put on it as standard is what it had on it. The most frustrating part of it is I don't have anything in Device Manager for it. No android phone, no Kindle/Kindle Fire, or Amazon, nothing. Installing the drivers does nothing, I even did a factory reset on the Kindle Fire and got nothing. I'm lost on this and I really want to put some books on my Kindle Fire so I don't have to read them on my iPhone.
When you boot your device, what does the boot logo look like (images, color, etc.)?
Kindle Fire logo, then blinks back on and glazes over from right to left and stays there for a while before turning on.
Go go gadget Tapatalk
Orange and white Kindle Fire logo? Since you didn't specify I'll just assume that is correct.
Drivers are most likely the reason your computer won't detect the device correctly. Unfortunately with Windows, there is about a hundred solutions to this problem and none of them are effective enough to be called a real fix.
If you have a flash drive, you can set up a Linux LiveUSB and run SoupKit so you can issuee adb and fastboot commands, without dealing with Windows based driver problems and you can work to get to the root of your problem more effectively.
soupmagnet said:
Orange and white Kindle Fire logo? Since you didn't specify I'll just assume that is correct.
Drivers are most likely the reason your computer won't detect the device correctly. Unfortunately with Windows, there is about a hundred solutions to this problem and none of them are effective enough to be called a real fix.
If you have a flash drive, you can set up a Linux LiveUSB and run SoupKit so you can issuee adb and fastboot commands, without dealing with Windows based driver problems and you can work to get to the root of your problem more effectively.
Click to expand...
Click to collapse
Yes, orange and white Kindle Fire logo. Any links to Linux LiveUSB, SoupKit and how to use them? I am a noob at a lot of these things.
Go go gadget Tapatalk
yes here`s some info http://forum.xda-developers.com/showthread.php?t=1882565
Thanks, is there an easy to understand quick guide on adb commands? I'm ping to pick up a small storage flash drive tonight for Linux LiveUSB.
Go go gadget Tapatalk
http://forum.xda-developers.com/showthread.php?t=1638452 and http://forum.xda-developers.com/showthread.php?t=1552547
Thank you very much, will mess with this later, waiting another hour for the Apple Store to open to get my iPhone 5.
Go go gadget Tapatalk
All right, do I need to download and install android sdk for Linux? Using terminal and looking for adb devices using the Linux LiveUSB with SoupKit didn't find any adb devices with the Kindle Fire plugged in. So I assume I need to download sdk to install drivers?
Go go gadget Tapatalk
metllicamilitia said:
All right, do I need to download and install android sdk for Linux? Using terminal and looking for adb devices using the Linux LiveUSB with SoupKit didn't find any adb devices with the Kindle Fire plugged in. So I assume I need to download sdk to install drivers?
Go go gadget Tapatalk
Click to expand...
Click to collapse
If you used the preconfigured iso no other steps are needed. Adb and fastboot are already setup. Time to consider your cable and or USB port that you are using.
Might be cable, plugged it into another computer (running windows) and it didn't see it.
Go go gadget Tapatalk
Yeah, it was the cable, I'll have to go pick up one for myself.
Go go gadget Tapatalk
I accidentally wiped the OS yes I know it was stupid but it was long time ago and I don't remember why. Anyways, the kindle fire is stuck in the logo screen and will always stay like that (until I turn it off). I can't seem to do anything with it. I'm on my linux live cd typing this. I am using ubuntu and I tried the Soupkit. It didn't work because it said my device was offline. I don't know what to do. I tried switching cords but it did not do anything. Now I did successfully install the Google usb driver for the kindle fire on my windows, And when I go to My Computer I see the kindle but you cant click on it. When I tried using KFU it said my device is online but it still didn't help me recover because it failed to get the downloads necessary. I am open and thankful for your suggestions. Thanks.
You need a factory cable to get into fastboot since you don't have access to the shell.
Sent from my KFHD 8.9 using Tapatalk 2
hi.
after i rooted my kindle with success i restarted it and it stack to the boot logo screen.i cant see the kindle anymore as a device in the computer.when i connect my kindle it appears for 1 second to the hardware devices and then disappears.so i cant send any command through fastboot.anyone has any idea what to do so i can fix the kindle?i ve tried everything there is in this forum but with no luck
Try running this with your kindle unplugged and off,
fastboot -i 0x1949 getvar product
Once u run that it should say waiting for device, now plug the kindle in, and if it doesn't automatically power on, then power it on. It should go into fast boot I think. I am a bit unsure if it will because of the fact I don't own an 8.9" kindle, but I think I remember this method didn't work on the 7" model, but read it was more so intended for the 8.9" model. This would probably be more likely to work on Linux, because if you haven't installed the adb drivers before on fast boot, then I don't think windows will finish installing them before then device disconnects, but that's just what I think. Post results plz.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I agree that it's probably a problem with the fastboot drivers not being installed on your PC, so the tablet leaves fastboot mode.
Does the Composite ADB Interface driver on the 2nd bootloader guide include fastboot driver? Perhaps if you install it as a legacy device via device manager without the device connected, it will connect after?
Personally I had difficulty installing these drivers as I'm on Windows 8 which disables installing drivers that arent digitally signed by default, if you use this OS then you need to toggle this via advanced startup options first.
O yea I know windows 8 is a total pain when it comes to unsigned drivers, had to deal with that on my friends pc. You can always try an Ubuntu live CD since the drivers won't be an issue. Is it staying on the non animated logo or the animated kindle logo after the device disappears?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
O yea I know windows 8 is a total pain when it comes to unsigned drivers, had to deal with that on my friends pc. You can always try an Ubuntu live CD since the drivers won't be an issue. Is it staying on the non animated logo or the animated kindle logo after the device disappears?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
the device disappears after one second from the hardware devices.it is staying on the non animated logo forever till the battery is dead.i have tried everything.i have installed the drivers with no problem and i even rooted the kindle.but after i restarted it the problem appeared.i ve tried to run the command with the kindle unpluged but when i plug it to the computer nothing happens.i tried usb2 and usb 3 ports, i tried windows 7 and windows 8 and pretty much everything i found here in the forum.still no luck
First off, your device is not in fastboot. Second, it is very unlikely that rooting alone would cause your device to hang at the Kindle Fire logo. Is there anything else that you attempted to do to your device before this happened?
Before getting to the appropriate solution, it would be beneficial to know what you used to root your device, whether or not you tried installing a custom bootloader/recovery, and what device you have in the first place.
i have a kindle fire hd 8.9" with 4.1 in it. i have followed this guide http://forum.xda-developers.com/showthread.php?t=2277105 so i can have root access. i used the binary method for the rooting.after i succesfully rooted the kindle i installed the astro file manager just for testing the root and it worked.then i followed the steps for installing the 2nd bootloader with twrp. it installed succesfully and i was able to boot in twrp mode. then i restart the kindle then it stack in the logo.thats pretty much all
doltrin said:
i have a kindle fire hd 8.9" with 4.1 in it. i have followed this guide http://forum.xda-developers.com/showthread.php?t=2277105 so i can have root access. i used the binary method for the rooting.after i succesfully rooted the kindle i installed the astro file manager just for testing the root and it worked.then i followed the steps for installing the 2nd bootloader with twrp. it installed succesfully and i was able to boot in twrp mode. then i restart the kindle then it stack in the logo.thats pretty much all
Click to expand...
Click to collapse
Now we're getting somewhere. You should do as stunts says to get your device booted into fastboot (see below)
stunts513 said:
Try running this with your kindle unplugged and off,
fastboot -i 0x1949 getvar product
Once u run that it should say waiting for device, now plug the kindle in, and if it doesn't automatically power on, then power it on. It should go into fast boot
Click to expand...
Click to collapse
If that doesn't work, you need to either fix your drivers in Windows, or use Linux (I believe he mentioned that as well)........Those are your only two options.
You'll need fastboot restore the partition images you saved in step one of the 2nd bootloader thread and start over.
at last.thanks a lot mate for your time and the tool you have created.i installed ubuntu then i used the soupkit and it finally went into fastboot mode and then i used kffirst aide and managed to make kindle work again.thanks so much.now i will try again to load the 2nd bootloader and install a custom rom.
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
z1326 said:
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
Click to expand...
Click to collapse
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Once the tablet is connected to the computer it will fall into red screen and become invisible to the computer in 1 second so the computer is not able to recognize the tablet.How can i install the necessary drivers?
BTW,you mentioned the instructions to factory reset,could you give me the link of the thread?
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have opensuse installed in my PC but that doesn't work either. Connect the tablet with the computer and the red screen shows up then the connection breaks and the tablet become invisible to the PC,just the same situation as it is in windows.
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you for you reply.I'd like to know if I could use this method in opensuse?
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I tried thay in suse but it didn't work.I think when the yellow kindle fire logo shows up the tablet is in fastboot mode but I'm just wondering why the tablet can't stay in fastboot after the screen truned into red.
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
So your suggestion would be
step1，Download a Ubuntu live CD image file，write the image into a usb disk，and reboot into the live CD.
step2，Open a terminal，input the fastboot command，then connect the tablet to the PC when the terminal says"waiting for device"
step3，Then the tablet should stay in fastboot and it is now possible to fix the bootloader and system with fastboot command.
Did I understand that correctly？
stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
And since my tablet is dead now， is it possible to install the fastboot driver in windows without the tablet？
It would be very difficult' unless you can get the driver into the driver cache but I haven't looked up how to do that, also on Ubuntu you will have to install the fastboot command, it should be in the Ubuntu software center, I'd give u the terminal command but I don't know the package name offhand.
Sent from my Amazon Kindle Fire HD using Tapatalk
Just out of curiosity have you tried KFFirstAide?
Sent from my KFTHWI using xda app-developers app
I have the Kindle 8.9 HD with the front-facing camera. I tried to flash CM 11, but now it's stuck at the bootscreen. It has the orange and white boot screen and a second later, a pixelated white bar pops up on the left, then it stays frozen until I shut it down. Windows doesn't seem to detect it at all, and I can't seem to get fastboot mode except for in Ubuntu using Soupkit. However, even if I do manage to get it into fastboot on Soupkit, SK says the device is offline afterwards even though the tablet displays fastboot on the screen.
It should be said and might be obvious, I'm not entirely sure what I'm doing. I spent a great deal of time reading into how to troubleshoot it myself. I do have previous experience with flashing roms on my Android phone, but that's about it.
Once it is in fastboot, reboot into windows and use kindle fire first aid. As I recall soupkit wasn't meant for 2nd gen kindles, only the kf1, but I could be mistaken, I use Ubuntu and know what I'm doing so I don't use these kinda things. Windows should detect the device as a jem device, so download drivers in my signature, extract them somewhere and in the device manager right click the jem device, hit update drivers, and point it to where you extracted mine. Once that is done kindle fire first aid should be able to reflash it.
Kffa: http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Once it is in fastboot, reboot into windows and use kindle fire first aid. As I recall soupkit wasn't meant for 2nd gen kindles, only the kf1, but I could be mistaken, I use Ubuntu and know what I'm doing so I don't use these kinda things. Windows should detect the device as a jem device, so download drivers in my signature, extract them somewhere and in the device manager right click the jem device, hit update drivers, and point it to where you extracted mine. Once that is done kindle fire first aid should be able to reflash it.
Kffa: http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Just like that. It's working! Didn't realize SK wasn't for 8.9, so when it didn't work, I stopped and just assumed it was fastboot on the tablet that wasn't working. I guess thinking it was hard-bricked might have been a bit dramatic.
Thanks, man! You're a lifesaver. You know your ****.