Related
i was curious to get get android market on my kindle today.. and looked up how. i used the kindle fire utility to root it. then my KF it started to go into a loop of the boot logo. it just flashes on and flashes off over and over again.hard reset doesnt affect it at all, it wont even turn off unless i unplug it. it doesnt show up on my computer either.
i dont know if this helps but when i ran the Kf utility it said 'findstr' not recognized.. blah blah blah. and it didnt give me the 1234567 options on there. i just typed in '2' and pressed enter because thats what the video told me .-. it doesnt have a triangle, or a blue screen logo either just the kindle fire logo flashing off and on. I honestly am lost. please keep this noob friendly
i am running win 7. 64 bit.
josepho1997 said:
It seems like your stuck in fastboot mode. You need to reinstall the drivers manually and then go into KFU. Press 1(bootmode)and 1(normal). If you still want to root it, when it gets to installing fff, and if it says <waiting for device>, you need to do a hard reset and your Kindle, unplug, plug it back in, and manually install the drivers. Then it will finish rooting.
Click to expand...
Click to collapse
How do you reinstall the drivers manually? and also when i go into the kindle fire utility it doesnt give me 1,2,3,4,5,6,7 options... it just says findstr is not a recognized as an internal or external command, operable program or batch file. and another thing i tried another utility on here and it said it said my device was not found when i plugged it in , is it because it turns off every 5 seconds?
First before you mess with your drivers shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Edit: hit enter after each command
zellerax said:
How do you reinstall the drivers manually? and also when i go into the kindle fire utility it doesnt give me 1,2,3,4,5,6,7 options... it just says findstr is not a recognized as an internal or external command, operable program or batch file. and another thing i tried another utility on here and it said it said my device was not found when i plugged it in , is it because it turns off every 5 seconds?
Click to expand...
Click to collapse
Sounds like there's some sort of PATH problem with your setup, which is why KFU won't work properly. You'll have to manually use ADB/fastboot commands if you want to get things done.
About it turning off constantly, it's probably out of battery. Use the stock wall charger (it provides a greater power output, don't bother with USB or a random clone) so it can refill some. The bootloops may be due to a bad boot mode, but it's a bit hard to pinpont with your description of the issue.
You may want to have a read here, it'll help you to better understand what's going on and how to express yourself about the problems you are experiencing: http://forum.xda-developers.com/showthread.php?t=1552547
zellerax said:
How do you reinstall the drivers manually? and also when i go into the kindle fire utility it doesnt give me 1,2,3,4,5,6,7 options... it just says findstr is not a recognized as an internal or external command, operable program or batch file. and another thing i tried another utility on here and it said it said my device was not found when i plugged it in , is it because it turns off every 5 seconds?
Click to expand...
Click to collapse
You might have corrupt drivers. Here's how to reinstall them:
Try going to your Control Panel >> Device Manager. If you see an entry for "Android Phone," (Android ADB interface) delete it (and any associations with Portable Devices >> KF or Kindle Fire).
Restart computer.
Then go to your KFU utility folder, open "install_drivers.bat" (right-click "Run Administrator"). This shouldn't take long at all.
You might want to restart here too after.
Then open KFU utility, plug in Kindle - if all went well here, you should read something along the lines of "Online" and "4000".
I am a similar situation
Hi Guys,
I rooted my KF with no issues, was able to copy the Jellybean and Gapp zip file to the SD and thought I flashed with no issues. Then rebooted. Now the KF is stuck in a boot loop. If I boot to recovery, that works and allows me the recovery options. if I boot up to normal, it constantly reboots, if I boot to fastboot, it displays the Kindle Fire logo and says "press power button to boot menu" at the bottom and does nothing else. My computer recognizes it as Android ADB interface but will not allow to access the SD ram. Any help would be greatly appreciated.
It's usually better to start your own thread here on Q&A.
Are you able to access the SD Card from TWRP? (Mount USB)
If so and the ROM is still in there, wipe cache, dalvik-cache, factory reset and system, then flash/install the ROM again (don't install gapps yet) and reboot. If it boots all the way to the desktop, reboot to recovery and install gapps.
You may also want to check the ROM's hash.
You haven't mentioned what versions of TWRP and FFF do you have, either. Hopefully 2.1.1 or 2.2 for TWRP and 1.4a (blue "fire" on the kindle fire logo) for FFF.
Dasanko said:
It's usually better to start your own thread here on Q&A.
Are you able to access the SD Card from TWRP? (Mount USB)
If so and the ROM is still in there, wipe cache, dalvik-cache, factory reset and system, then flash/install the ROM again (don't install gapps yet) and reboot. If it boots all the way to the desktop, reboot to recovery and install gapps.
You may also want to check the ROM's hash.
You haven't mentioned what versions of TWRP and FFF do you have, either. Hopefully 2.1.1 or 2.2 for TWRP and 1.4a (blue "fire" on the kindle fire logo) for FFF.
Click to expand...
Click to collapse
Thanks for the info and sorry for the incomplete initial info. I will check this as soon as I get home and can work on it again.
Thanks for your help. It turns out that I didnt even have TWRP installed. Thats fixed. I was able to get roms installed and have different problems. (Will start a new thread in another area) Thank you very much for your help.
My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!
i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks
Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?
Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.
Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?
GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Kamakookie said:
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Click to expand...
Click to collapse
Maybe go into twrp and do a factory reset. Can you get to that menu? Click wipe and then factory reset.
I've tried the factory reset but it seems to have no effect on it. How do I do the adb push? I've tried using the command prompt to run some of the commands on other threads but I'm not doing something right. I always get an 'adb' is not recognized as an internal or external command, operable program or batch file error.
I'll apologize now for my stupidity on this one- I have never worked with android software before this.
The kindle fire utility reads:
ADB status: Offline
Boot Status: Unknown
I can get it to boot in normal and recovery mode, but each time I try to boot in Fastboot I get an error message 'Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on.' The Kindle shows up in Device Manager under Android Phone as Android ADB Interface
When using the twrp, anything that involves writing to or wiping the sd card receives this error E:failed to mount /sdcard (invalid argument)
I'd appreciate any help I can get. I'm at a standstill on this one.
im in the same position you can open it as a USB by selecting mount in TWRP and selecting mount USB Storage
do you have drivers / ADB on your computer ?
I did manage to get my kindle go into a recovery boot loop by doing the root procedure for the original 6.3 original Amazon ROM while my kindle had the 6.2 ROM . After i realized that the root procedure (intended for ver 6.3) didn't work for me, I had to try the procedure for rooting ver. 6.2.
It worked but after a couple of resets, the tablet went into a recovery boot loop.
what i did was to use ADB comands:
enter windows - > start command prompt (start - > run -> cmd)
check if kindle is connected: adb devices
if the device is found then use:
adb shell
su
idme bootmode 4000
exit
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
lukebunny said:
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
Click to expand...
Click to collapse
At startup hold thepower button untill you see the bootmenu come up and select "normal boot"
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
lukebunny said:
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
Click to expand...
Click to collapse
What version of TWRP do you have?
2.2.0
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
jamminjon82 said:
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Tried it, no go.
This is what I get in the command line
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Have you tried reboot to bootloader?
Sent from my Galaxy Nexus using Tapatalk 2
hey i got your answer I think? lol anyways...
soupmagnet said:
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Click to expand...
Click to collapse
i'm pretty sure it's bla bla bla \platform-tools in that picture anyways that my answer anyways, maybe not but goodluck anyways........... and this 5 mins between post for low posting users is for the birds
digital_cha0s said:
i'm pretty surs it's bla bla bla \platform-tools in that picture anyways that my answer anyways goodluck
Click to expand...
Click to collapse
As you can see, the "adb shell" command is successful because of the change in the prompt.
~ # <-indicates the shell is working and active, so the actual /path of adb is irrelavent.
soupmagnet said:
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Click to expand...
Click to collapse
That seems promising, but this is what I got when I tried it.
Also, thanks for your help everyone, I'm learning a lot as I go here!
Hi,
I tried to install the original ROM by TWRP but the process stopped and the kindle fire rebooted.
Now it is stucked on orange boot logo.
When I try to invoke ANY command on KFU, on the screen appears the message <waiting for device>
When I try to invoke ANY "fastboot" command manually, on the screen appears the message <waiting for device>
If I delete the windows drivers and plug the device, I can see the memory but I can't read the content and I can't write any file.
If I install the drivers from the KFU folder (install_drivers.bat), the devices is recognized correctly by the system, but I can't see the memory on pc resources(only on system)
Anyone has some ideas or suggestions in order to install TWRP or the original ROM On my kindle?
Could I solve my problem by a factory cable?
Thanks in advance
It's going to be important for you to figure out where your device is in the booting process when it gets stuck...
http://forum.xda-developers.com/showthread.php?t=1668159
If by "memory" you mean the storage area in the /sdcard partition and it can be mounted on the desktop, you are not going to be in fastboot mode. If it's trying to boot into the system software but it doesn't quite get there, you need to see if you can use an appropriate "adb shell" command to change the bootmode to fastboot. If you can't do that, your next best option is probably to get a factory cable and see if your bootloader can be put into fastboot mode. If what I just said in this paragraph doesn't make any sense to you, take a good look at the guide mentioned in the beginning of the post above.
kinfauns said:
It's going to be important for you to figure out where your device is in the booting process when it gets stuck...
http://forum.xda-developers.com/showthread.php?t=1668159
If by "memory" you mean the storage area in the /sdcard partition and it can be mounted on the desktop, you are not going to be in fastboot mode. If it's trying to boot into the system software but it doesn't quite get there, you need to see if you can use an appropriate "adb shell" command to change the bootmode to fastboot. If you can't do that, your next best option is probably to get a factory cable and see if your bootloader can be put into fastboot mode. If what I just said in this paragraph doesn't make any sense to you, take a good look at the guide mentioned in the beginning of the post above.
Click to expand...
Click to collapse
Thanks a lot for your answer...
The "memory" are the storage area of my Kindle, and it can be mounted on the desktop but is not accessible.
I have tried to boot the system in all fastboot mode (4000, 4002, 5001) but the system shows the <waiting for device> message. I have tried to activate the fastboot also using "adb" command, but I have the same result.
I could reinstall TWRP or the original ROM with the factory cable? When I plug my kindle by the factory cable my pc can communicate with it?
Thanks for your help
kinfauns said:
It's going to be important for you to figure out where your device is in the booting process when it gets stuck...
Click to expand...
Click to collapse
You look like you could use some help figuring this out.
kinfauns said:
Recognizing fastboot mode
The Display - As the bootloader loads up on the device, one of the previously mentioned bootlogos will appear on the display. With fastboot mode enabled, that bootlogo will be persistent and remain bright on the display. If the display blacks out and redisplays the bootlogo with the backlight slightly dimmed, the bootloader has bypassed fastboot mode and moved on in the boot process.
Click to expand...
Click to collapse
Now, are you in fastboot or not?
The orange logo is persistent on the screen, but if i press for 20 sec the power button on reboot the display shows the orange logo, then the display blacks out and redisplays the bootlogo with the backlight slightly dimmed.
I think thant the kindle not is in fasboot mode...is correct?
alchemist said:
The orange logo is persistent on the screen, but if i press for 20 sec the power button on reboot the display shows the orange logo, then the display blacks out and redisplays the bootlogo with the backlight slightly dimmed.
I think thant the kindle not is in fasboot mode...is correct?
Click to expand...
Click to collapse
Anyone?
alchemist said:
The orange logo is persistent on the screen, but if i press for 20 sec the power button on reboot the display shows the orange logo, then the display blacks out and redisplays the bootlogo with the backlight slightly dimmed.
I think thant the kindle not is in fasboot mode...is correct?
Click to expand...
Click to collapse
No, it's not in fastboot mode. Use the Fastboot guide I referred to earlier and try to get the system to set the bootmode to fastboot. This is your next best option to getting the device fixed. I'm pretty sure you have an unrooted stock device, so you'll have to use pokey9000's fbmode. If you can't get it to fastboot mode this way, you need a factory cable. If you don't have a factory cable and you can't make or buy one, then the only option you have left is to open up the case and use Firekit. All of this is detailed in the Fastboot guide. I highly recommend you try using the factory cable.
Once you get the device into fastboot mode, you'll need to follow this guide to flash TWRP and FFF again...
http://forum.xda-developers.com/showthread.php?t=1638452
Once you've done that, the same guide contains instructions on how to revert back to the stock software. Follow those instructions carefully and it will walk you through the process.
Kindle fire stuck on boot logo...the device is corrupted? [SOLVED]
Problem solved by factory cable. In fastboot mode I have installed TWRP and I have launched the restore of a old backup (boot and data).
My Kindle is alive!
Thanks a lot for help.
alchemist said:
Problem solved by factory cable. In fastboot mode I have installed TWRP and I have launched the restore of a old backup (boot and data).
My Kindle is alive!
Thanks a lot for help.
Click to expand...
Click to collapse
I have an other problem. In Kindle Fire Utility the kindle is always offline, and the boot status is unknow (and I can't install FFF and EX Launcher...)
I tried to reboot in normal mode or fastboot mode with KFU and "fastboot" command, but my pc show <waiting device> message.
What kind of command I need to use?
The KFU problem is due to driver issues with Windows.
If you are booted normally, you can use the command line or Pokey9000's bootmode binaries from a terminal emulator to change your bootmode.
soupmagnet said:
The KFU problem is due to driver issues with Windows.
If you are booted normally, you can use the command line or Pokey9000's bootmode binaries from a terminal emulator to change your bootmode.
Click to expand...
Click to collapse
I tried this and it stopped the boot looping but stuck on the Boot Logo. I used the unbrick method and it went back to boot looping. I have restored my KF several times in the past but this one has really stumped me. I have never had this problem. Are there any other solutions out there?
Kindle Fire Stuck at Logo and Screen Flashing
hi i have a kindle fire that is stuck at the boot logo the screen is flashing every 3 seconds or so and the light is flashing as well it has stock everything but the soupkit is just stuck here at waiting for device
truckaveli said:
hi i have a kindle fire that is stuck at the boot logo the screen is flashing every 3 seconds or so and the light is flashing as well it has stock everything but the soupkit is just stuck here at waiting for device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2166668
#31
thanks
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2166668
#31
Click to expand...
Click to collapse
thanks i will try this and see what happens i also have another kindle fire that is operational but the screen flashes randomly and the touch screen in the game sometimes jumps all over the place like i would be touching one area and a selection for another area comes up
Not working
i charged the kindle entire day still no change it wont even read in the system i am in ubuntu 12.04 nothing in soupkit is helping as it is just hanging <waiting for devices>
Did you follow the instructions? What steps did you take to charge it? Is it still on a 3 second bootloop?
Hello all! I currently need help unbricking my Kindle Fire 2nd Gen. My kindle is stuck in the "Kindle is Upgrading" screen after rooting it and accidentally messing up the default launcher. I'm trying to factory reset it, but I can't figure out how. Since my Kindle is in this state of upgrading, my computer won't recognize it, even with EVERY driver that you're supposed to install installed (And yes, I've tried uninstalling every driver and reinstalling them all). I bought a fastboot cable, but of course I can't really do anything with it because I can't install a recovery or even get to the android recovery without it being recognized on my computer. When I plug in my Fastboot cable, it just says "Fastboot" and has a red light and a blinking green light. Is there any way to externally reset it? I tried opening it up and finding a little pin sized hole to reset it, but mine didn't have it like their's did. I really need help, my family is poor and I use this for many things and we can't replace it. Please help!
Hello again.
In your last forum thread, you stated that you got the ADB/fastboot drivers to work on your computer. If that is true, download the latest firmware from amazon here: http://www.amazon.com/gp/help/customer/display.html?nodeId=201016370
Move that to your platform-tools folder. Press shift+right-click and click open command window here then boot your kindle to fastboot mode and type fastboot -i 0x1949 flash system <insert update file name here>.bin and press enter. It should now reinstall Fire OS 10.5.1 to your kindle, but you aren't done just yet...Unfortunately, I can't remember the fastboot command to wipe the dalvik cache (someone please reply with the command, you will be thanked!). After you wipe the dalvik cache, type fastboot -i 0x1949 reboot and unplug the fastboot cable right when your kindle's screen goes black. It should now take several minutes to boot to Fire OS, so be patient! If it has been 10 minutes and your kindle hasn't booted, try to flash the OS again but don't wipe the dalvik cache (since we already wiped it). If it still doesn't boot, then something has gone horribly wrong with your kindle, I'm afraid, but reply if this happens, as there is one thing we can still do.
Hope this helped,
Nick
Sent from my iPhone 4 using Tapatalk
Root Obtained
Thanks for this, after hours of searching through different threads and forums I have finally rooted my old KF2.