Related
1) Yes I checked search results.
2) Yes I've googled.
3) Yes I've tried the Kindle Fire Utility, the http://forum.xda-developers.com/showthread.php?t=1356257... links options.
With that being said, here's my issue;
Got a KF a couple days ago...
Yesterday, followed some online instructions to put GO Launcher EX on there to replace the carousel deal.
Followed instructions to the T.
Restarted. Got to "Choose your OS" screen (or whatever it precisely says...)
Picked GO... then it froze.
Now, when it restarts (yes, its the 30 second hard restart), it gets stuck on the Kindle Fire splash screen.
I have tried the above utilities.
I have hard restarted.
I have fully charged and ran the battery dry and tried again.
When I use the utilities, the problem is, my PC will not recognize the Kindle (it see's it as a removable storage device, but it doesn't click over to 'Kindle', and thus the utilities can't interact with the device itself, I suppose).
I've tried different USB ports and connecters (I have 2 regular kindles in the house, too). But I know all the peripherals work through cross-testing.
Essentially, what else can I do? (I got it from WalMart, and they're currently out of stock, so I can't return it till next week, but I'd like it fixed before then if possible)
I've tried several different methods from these forums too, but I *always* hit the same snag... whenever any utility is 'waiting for device', it simply will not find it, because the PC doesn't see it properly. It sees *something* (removable storage) but not as a kindle, and thus won't allow the utilities to interface with it.
Are there any physical things I can do to hard reset it without destroying any warrantys?
Any help appreciated!
there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
first i need to know if you have fff (custom bootloader - yellow triangle) on it ?
then do you have a recovery (twrp) on it ?
what os/bit of computer ?
In kindle utility go to bootmodes and enter normal (4000). Just had that problem last night.
awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
b63 - I hope your right!
no - I do not have the yellow triangle.
no - I do not have TWRP on it, i have tried, but cannot get anything onto the kindle.
my PC is window7, 64bit
Euryon said:
awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
Click to expand...
Click to collapse
Do you have all the kf drivers installed on your computer? I know that when I unbricked mine I had all the drivers installed but I had to reinstall them for some reason. If you do not have them I can post them later on tonight when I'm at home. However, I have TWRP installed on mine, and Cyanogenmod 7.2, so hopefully yours is able to connect to your computer.
---------- Post added at 12:56 PM ---------- Previous post was at 12:50 PM ----------
b63 said:
there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
Click to expand...
Click to collapse
In order to remove the bad launcher, you need to have your device connected to your computer to remove it using adb.
ok so b63 helped me out big time here....
about 2 hours ago we got on a teamviewer session (download this if you want these guys to help you with serious issues!)
took me a minute to figure out how to allow him/her proper access to my screen
anyway
i don't understand the technical stuff
but
what i had done wrong is that i didnt root the KF before trying to install the GO... software (i think)
b63 had a heck of a time trying to discern the problem with me being about as useful as a dead fish, but get there he/she did
after much fanangaling, b63 managed to install the TWRP and ADP on my KF, allowing it to fastboot, and basically allowing it to be read by my PC, and so fixed.
im sure it would have taken b63 all of 5 minutes in real time, but using the quirky teamview and my slow net speed didn't help
still, thanks VERY MUCH to b63 for fixing the **** out of my KF, and being very helpful and patient all along!
thanks
Just wanted to drop b63 a note here that I "thanks"ed their post above - not necessarily for the post but for going above and beyond. The people on these forums are (for the most part) really great. (Too bad there have to be a few who are demanding of the developers to get this feature or that fix done faster without taking into account that the devs do this all in their free time.)
YES, search finally led me here!
Euryon, I have the exact same thing happening with my KF right now.
Do you remember any specifics of how b63 carried out the steps you listed?
b63, any chance you could help me with mine? My issue is identical with Euryon's down to the letter.
Same Problem
Could someone please help me i have the same problem
same problem here! please can someone give a step by step? My fire is unrooted and I did nothing to it except try to install the go launcher and after I selected it as the default launcher it got stuck at the kindke fire logo.
I tried the Kindle unbricking utility but it cannot find the device even after I installed the adb composite interface
also, my fire is not showing up as a kindle - it is showing up as an android device.
rollno88 said:
also, my fire is not showing up as a kindle - it is showing up as an android device.
Click to expand...
Click to collapse
Have you added the fires usb ID to your system?
Sent from my Amazon Kindle Fire using Tapatalk 2
thanks for replying, and I have no clue how to do that. I'll search and get back .
---------- Post added at 10:12 AM ---------- Previous post was at 09:57 AM ----------
okay, I already did that by editing the android sdk(as a prerequisite to rooting, which I planned to do eventually) - so when I connect my fire it first shows up as a kindle, and after updating the software through windows and installing drivers through KFU, it comes up as an android device and the interface is adb composite. Now if I try to install TWRP through KFU it keeps switching between adb composite interface and plain adb. And both KFU and KUFU keep waiting but are unable to find my device.
also, my fire alternately shows up as a usb composite device and an android device. PLEASE help
okay I solved it with KFU (finally!) although I have no clue how I did it as I didn'tdo anything I hadn't tried earlier so, managed to install TWRP and then wiped everything and finally my fire could be read - then I deleted go launcher and now my fire is back from the grave
A big thank you to all the helpful posts at this forum - u guys are the best
Same issue
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
edit: when rerunning KFU, i kept getting the message that many execs failed because "/system/bin/sh" directory does not exist.
I don't know if that helps narrow down what might be happening, but I saw that coming up a lot in the cmd prompt.
zeissbickham said:
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with an emphasis on post #2. You need to know what mode your device is in by looking at the device manager and make sure your drivers are loading correctly for that mode. If you can get to TWRP, you can mount your USB mass storage device, copy a new zip file of either the stock software or a custom ROM and flash it.
Thank you. I will be trying this shortly.
fully bricked
I followed the guide and got to a point where the Kindle Fire animation was playing. It loaded up to the unlock screen and then automatically shut itself down - would not stay on when either connected or disconnected. Tried installing a ROM but still shut down. Started the recovery and hit factory reset, still auto shutdown. Tried clearing a partition as described in the tutorial and now it's fully bricked. Will not turn on when connected to computer, to outlet, to another cable.
Thanks for trying to help.
Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.
Sounds like it's stuck in fastboot bootmode to this noob. I had the same problem at one point and used command line to fix with the simple bootmode switching commands - can't recall if I used fastboot or adb tools..but either should work. And if I'm reading your post right, you've tried these so this is likely above my meager skill level, heh. You are handling it better than I did, I might add.
If I may point out where you went wrong:
Mattamus Prime said:
After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
Click to expand...
Click to collapse
There are apps in the Google Play store that will temporarily remove your root status so you are able to use services that detect and shut down when root is detected. OTArootkeeper.apk is one that I've heard of.
And don't ever chose to lose fff once you have that as this is your lifeline to unbricking.
Hopefully someone with better chops than I on this will post up - continue with your patient reading and take a little comfort that this is most probably fixable.
First off, I applaud you for trying to figure out and fix the problem yourself using the guides available. Thank you. The information you provided will go a long way to getting the help you need.
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Once you have done that and you still can't change your bootmode, try using recovery to flash a custom rom. It's possible the stock boot image you have has been corrupted. You can use the "mount" function in recovery to push another rom to your sdcard. If that works you can stick with a custom rom like MoDaCo. It's the same stock stock interface with Google apps and services installed and you don't have to worry about OTA updates. OTA Rootkeeper will let you easily switch between "rooted" and "unrooted" so you can take advantage of Amazon's VOD.
And if you still want pure stock you can d/l a new copy of the update and try again.
Thanks for the suggestion. I did try OTA Rootkeeper, but when I went into my Instant VOD, it still had the buttons grayed out. I tried temp unroot, reboot Kindle, and still grayed out, so I assumed Rootkeeper wasn't working for me, thus, the looking for the unroot tutorials.
A little bit of extra information, when I hook up my Kindle Fire, my drivers says Android Composite ADB Interface. When I try to switch to Fastboot to have it switch to Android ADB Interface, it doesn't switch. It just stays as Composite.
Thanks again.
soupmagnet said:
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Click to expand...
Click to collapse
I followed the advice in the Beginners Guide, uninstalled whatever drivers I had, rebooted my comp, then installed the ones that came with the KFU download.
Are there any other drivers I should be looking for?
Also, a little bit of more information, I tried switching to Fastboot through KFU, received some messages to the effect of "system/some file name file not found (2)", (I apologize for not being specific, typing from memory), it then reboots my Kindle Fire, then I execute the commands:
fastboot getvar product
After that, it just says <waiting for device>
In fact, after any command I do in cmd, I get that message. So I believe it may be a driver issue, like was suggested, or my Kindle isn't far enough into the boot process to be found.
It definitely sounds like a driver issue. Keep working on your drivers.
If that doesn't work, you can try it on a different computer OR set up a Linux LiveUSB for issuing adb/fastboot commands.
FIX for Kindle stuck on logo
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
MattamusPrime said:
Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.
Click to expand...
Click to collapse
K_Krish said:
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
Click to expand...
Click to collapse
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
me too
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
I am stuck at the very same place you are. I was in an endless bootloop after trying to flas back to the Stock Amazon ROM using TWRP. Once i got the drivers sorted out and ADB could see my device i used KFU to "Install permanent Root with Superuser". The KF went to reboot into fastboot and the screen said "waiting for device" for about ten minutes. Now the KF is stuck at the white and orange "kindle Fire" boot logo. Windows will no longer see the KF as an android device. It only shows up as an "unknown device" in the device manager.
Try this
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Ok, I dont know, how to fix this (as I was not in this situation). Try following the steps - Download update.zip through KFU. Connect your Kindle to PC and install the android driver. If your PC detects the kindle copy update.zip file to kindle and try to install that.
sounds like a job for this http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Im in the same boat you are. I have tried everything stuck on same logo device is recognized in devices as android phone and adb interface but cannot connect to unbrick utility or KFU and doesnt show as a drive either. tried to search devices in cmd using fastboot commands and nothing shows either. I decided to purchase a factory cable today on ebay. Keeping my fingers crossed because after reading everything I could find I think it is my only option.
No, your problem is as "simple" as fixing your drivers so the computer can communicate with the device through adb and fastboot. KFU relies on those two tools to do pretty much anything. Unfortunately, Windows is stupid and is not very effective when dealing with certain USB devices.
In order to, say, install TWRP, you need adb to change the bootmode to accept fastboot commands, and use fastboot commands to overwrite the recovery partition. In the process of going between different boot modes, Windows had a hissy fit and decides not to communicate with the device at all. Hence the need to fix/reinstall the drivers. It doesn't always work out that way and you get stuck where you are right now. A factory cable will put you in fastboot, but it wont make Windows communicate with the device. You can continue to fight with Windows drivers and hope to get lucky, or you could try other, more effective options...
http://forum.xda-developers.com/showpost.php?p=30629067
omg .... I survived a bricking. Soupkit saved me!!!
Somewhere on the many tabs I have open, as I frantically search for ways to unbrick my Kindle fire... I run into " SoupKit" for Linux ... install it... mess around with the Bootloader .. change it to 4002 I believe the value was ... my Kindle that I've been working on for literally 6 hrs is back on! ... now on the figuring out how to root it / remove demo software. SOUPKIT!
E]
Hello-
Quick background. I have a Kindle Fire with the CM9-Reloaded ROM installed. All was going well for a few weeks until my Kindle stopped connecting to the internet. I figured it was just a bug and wanted to reinstall the ROM or choose a different one.
I have FFF v1.4 (with the blue logo) installed. When I get to the screen that allows me to choose "Normal Boot", "Recovery", or "Reset Boot Mode" I choose the "Recovery" to go into TWRP; however, this doesn't happen. It puts me back into a loop to the same screen to choose again. I can do this over and over again and I'm still not able to get into recovery to get to TWRP.
I decided to see if I could use the Kindle Fire Utility to get to TWPR that way. Before everyone asks, my drivers are all updated and functioning properly. I uninstalled and reinstalled just to double check. When the Kindle is plugged in, I can go to the device manager and see my Kindle there. The problem is that KFU says I'm offline and I can get to any of the menus. When I plug in my Kindle I do get the little "bong" that tells me my computer recognized it.
Also, went to my laptop and downloaded the KFU and installed everything. Same result as with my desktop.
What else can I try? I have a factory cable, but I really don't know much about how to use it. I simply followed step by step instructions to root this when I originally got it. Any suggestions? I'd really just like to put this Kindle back to stock, re-root, and try it all over again to eliminate any potential issues in the future. Thanks in advance for your help.
Does "adb reboot recovery" not work from within the ROM either? You can try to reflash TWRP from fastboot, if you're feeling brave enough. Double check the hash first, though.
same boat
hello all
i am in need of dire help working on sister's inlaw kindle fire
i got the KFU newest one and verified the kindle was the newest version software
i started the KFU i must of missed a step and the kindle fire is locked on loadscreen (kindle fire) a soft brick i got the program that u say try and the system will not be found by it
i have removed and reinstalled the Adb rebooted my system and hard reboot kindle........the computer sees the kindle but not as kindle..........in device manger it shows up under the ADB section not the portable..........i only see the ADB there is no kindle hardware tab in windows explorer it is not listed
but it is listed in devices and printers under unspecified with the name kindle in there........... i can not access any info in the tab it list the name as kindle the rest are blank
please help i have no idea what to do on this one.........it is locked on the screen and i can not get the system to fully talk with each other to correct it using the methods u have posted
**note i went to a 2nd computer that has never had kindle or any ADB or any other program dealing with this the system is giving the same results as stated above the system sees it but does not know what it is ...thought it might be a overlapping driver issue on my computer
side note i am kind of poor and really do not have 200 bucks to buy a new one for her i have a week to fix with out getting caught help please
Dasanko said:
Does "adb reboot recovery" not work from within the ROM either? You can try to reflash TWRP from fastboot, if you're feeling brave enough. Double check the hash first, though.
Click to expand...
Click to collapse
No, adb reboot recovery doesn't work. How would I reflash TWRP from fastboot? I'm definitely a rookie at cmd work.
jeffjoleen said:
No, adb reboot recovery doesn't work. How would I reflash TWRP from fastboot? I'm definitely a rookie at cmd work.
Click to expand...
Click to collapse
By it not working, do you mean that it reboots normally?
"fastboot getvar product" to get the KF to stick with fastboot mode when it's loading the bootloader.
"fastboot flash recovery twrp.img" very important to double check the file hash to make sure it's not corrupt.
"fastboot reboot" only in case it doesn't automatically reboot on its own.
EDIT: Keep in mind fastboot mode uses a different set of drivers, so you may have to install those as well (included in KFU, along the ADB ones).
---------- Post added at 06:57 PM ---------- Previous post was at 06:49 PM ----------
Justugh said:
hello all
i am in need of dire help working on sister's inlaw kindle fire
i got the KFU newest one and verified the kindle was the newest version software
i started the KFU i must of missed a step and the kindle fire is locked on loadscreen (kindle fire) a soft brick i got the program that u say try and the system will not be found by it
i have removed and reinstalled the Adb rebooted my system and hard reboot kindle........the computer sees the kindle but not as kindle..........in device manger it shows up under the ADB section not the portable..........i only see the ADB there is no kindle hardware tab in windows explorer it is not listed
but it is listed in devices and printers under unspecified with the name kindle in there........... i can not access any info in the tab it list the name as kindle the rest are blank
please help i have no idea what to do on this one.........it is locked on the screen and i can not get the system to fully talk with each other to correct it using the methods u have posted
**note i went to a 2nd computer that has never had kindle or any ADB or any other program dealing with this the system is giving the same results as stated above the system sees it but does not know what it is ...thought it might be a overlapping driver issue on my computer
side note i am kind of poor and really do not have 200 bucks to buy a new one for her i have a week to fix with out getting caught help please
Click to expand...
Click to collapse
Please don't hijack other people's threads, start your own here on Q&A. Otherwise, handling with two completely different issues in the same place gets awfully confusing. Also, read this: http://forum.xda-developers.com/showthread.php?t=1552547
This post is coming after hours upon hours and days upon days of research, trial, and no success. Hopefully someone can help me out...
I was asked to work on a "bricked Kindle" due to a reputaion among friends and co-workers of being the "go to" guy for rooting, custom ROMs, and the like. I am familiar with adb, fastboot, etc, and have used them often. Even though I didn't know what had happened to this particular Kindle, I was confident I could fix it.
I got it and began investigating. It powered on and FFF 1.4a popped up, followed by the stock Kindle logo where it stayed. I rebooted and used FFF to boot to Recovery, which is TWRP 2.6.3.1. Further checking found that there is no ROM installed, only FFF and TWRP, nothing else. I thought "This will be easy!". Wrong...
I connected it to my Windows 7 PC and ... nothing. Didn't even show as anything being connected at all. Installed drivers, still no luck. ADB doesn't see it either. Tried using 'mount' in TWRP, nope. Then began my trip down the numerous fixit programs KFU, FireKit, ReKindle, etc. Not a thing. Linux doesn't see it either. Like it is not even connected. Even tried the USB Shorting Trick, still wont register on anything, as anything. Bought a Fasboot "Factory" Cable, still nothing. My only hope at this point is the terminal in TWRP. I have successfully run various commands in there, verified the different boot modes with idme. Found that it did change to Fastboot (4002) and back to Normal (4000) when asked. Attempted to use Parted for some investigation but it is difficult to use in that terminal. I did discover that several partitions are screwed up. How to fix them is beyond my expertise. My thought at the moment is to wipe the thing 100%, partitions and all, to see if I can then connect at least with FK or something to reformat and put FFF and TWRP back on (latest versions). Also when looking through the logs in the terminal, it listed failures with an OMAP clock file.
The original owner told me he knew it couldn't be fixed and told me to keep it. I think it is still possible to salvage it. Any ideas?
Thanks.
kyle8b16 said:
This post is coming after hours upon hours and days upon days of research, trial, and no success. Hopefully someone can help me out...
I was asked to work on a "bricked Kindle" due to a reputaion among friends and co-workers of being the "go to" guy for rooting, custom ROMs, and the like. I am familiar with adb, fastboot, etc, and have used them often. Even though I didn't know what had happened to this particular Kindle, I was confident I could fix it.
I got it and began investigating. It powered on and FFF 1.4a popped up, followed by the stock Kindle logo where it stayed. I rebooted and used FFF to boot to Recovery, which is TWRP 2.6.3.1. Further checking found that there is no ROM installed, only FFF and TWRP, nothing else. I thought "This will be easy!". Wrong...
I connected it to my Windows 7 PC and ... nothing. Didn't even show as anything being connected at all. Installed drivers, still no luck. ADB doesn't see it either. Tried using 'mount' in TWRP, nope. Then began my trip down the numerous fixit programs KFU, FireKit, ReKindle, etc. Not a thing. Linux doesn't see it either. Like it is not even connected. Even tried the USB Shorting Trick, still wont register on anything, as anything. Bought a Fasboot "Factory" Cable, still nothing. My only hope at this point is the terminal in TWRP. I have successfully run various commands in there, verified the different boot modes with idme. Found that it did change to Fastboot (4002) and back to Normal (4000) when asked. Attempted to use Parted for some investigation but it is difficult to use in that terminal. I did discover that several partitions are screwed up. How to fix them is beyond my expertise. My thought at the moment is to wipe the thing 100%, partitions and all, to see if I can then connect at least with FK or something to reformat and put FFF and TWRP back on (latest versions). Also when looking through the logs in the terminal, it listed failures with an OMAP clock file.
The original owner told me he knew it couldn't be fixed and told me to keep it. I think it is still possible to salvage it. Any ideas?
Thanks.
Click to expand...
Click to collapse
If you want to re-do the partitions and install the very latest bootloader and TWRP +ROM, you should install otterX (1st gen only!!). Follow the steps in this link and you'll be fine.
http://forum.xda-developers.com/showthread.php?t=2671619
kyle8b16 said:
This post is coming after hours upon hours and days upon days of research, trial, and no success. Hopefully someone can help me out...
I was asked to work on a "bricked Kindle" due to a reputaion among friends and co-workers of being the "go to" guy for rooting, custom ROMs, and the like. I am familiar with adb, fastboot, etc, and have used them often. Even though I didn't know what had happened to this particular Kindle, I was confident I could fix it.
I got it and began investigating. It powered on and FFF 1.4a popped up, followed by the stock Kindle logo where it stayed. I rebooted and used FFF to boot to Recovery, which is TWRP 2.6.3.1. Further checking found that there is no ROM installed, only FFF and TWRP, nothing else. I thought "This will be easy!". Wrong...
I connected it to my Windows 7 PC and ... nothing. Didn't even show as anything being connected at all. Installed drivers, still no luck. ADB doesn't see it either. Tried using 'mount' in TWRP, nope. Then began my trip down the numerous fixit programs KFU, FireKit, ReKindle, etc. Not a thing. Linux doesn't see it either. Like it is not even connected. Even tried the USB Shorting Trick, still wont register on anything, as anything. Bought a Fasboot "Factory" Cable, still nothing. My only hope at this point is the terminal in TWRP. I have successfully run various commands in there, verified the different boot modes with idme. Found that it did change to Fastboot (4002) and back to Normal (4000) when asked. Attempted to use Parted for some investigation but it is difficult to use in that terminal. I did discover that several partitions are screwed up. How to fix them is beyond my expertise. My thought at the moment is to wipe the thing 100%, partitions and all, to see if I can then connect at least with FK or something to reformat and put FFF and TWRP back on (latest versions). Also when looking through the logs in the terminal, it listed failures with an OMAP clock file.
The original owner told me he knew it couldn't be fixed and told me to keep it. I think it is still possible to salvage it. Any ideas?
Thanks.
Click to expand...
Click to collapse
Even people think of me as a 'go to' guy. I love that respect
Sent from my A114 using XDA Free mobile app
Sounds like the USB port could be bad.
Sent from my PHOTON Q using XDA Premium 4 mobile app
Wish I could...
bflobills said:
If you want to re-do the partitions and install the very latest bootloader and TWRP +ROM, you should install otterX (1st gen only!!). Follow the steps in this link and you'll be fine.
http://forum.xda-developers.com/showthread.php?t=2671619
Click to expand...
Click to collapse
I would like to give that a try but the problem is that I cant push anything to the device w/ adb at the moment. No computer, Linux or Windows, will recognize it at all (not even incorrectly). I thought initially that the usb port on the Kindle was bad but I can get it to react differently when it is plugged in vs not. For example, when the fastboot cable is connected it stops at the FFF boot screen as if it is in fastboot, but nothing recognizes it and fastboot doesn't work. When I connect to the computer with a regular cable it will turn the Kindle on and charge it, but no connection. I am still leaning toward it being some kind of software problem on the Kindle.
Return2Stock Tool
kyle8b16 said:
I would like to give that a try but the problem is that I cant push anything to the device w/ adb at the moment. No computer, Linux or Windows, will recognize it at all (not even incorrectly). I thought initially that the usb port on the Kindle was bad but I can get it to react differently when it is plugged in vs not. For example, when the fastboot cable is connected it stops at the FFF boot screen as if it is in fastboot, but nothing recognizes it and fastboot doesn't work. When I connect to the computer with a regular cable it will turn the Kindle on and charge it, but no connection. I am still leaning toward it being some kind of software problem on the Kindle.
Click to expand...
Click to collapse
Hi, Noob here but I faced a similar situation to you just last week. The ONLY thing that helped me is a tool known as Return2Stock by N2A. Since I am new, I cannot post outside links but I made a post on reddit in the kindle fire "hot" section titled Bricked Kindle Fire With No Access to TWRP (it's on the first page about halfway down. It describes what I had to do in order to get it working. But it did work! And I tried EVERYTHING. Good luck
Good morning all. I know you probably see a thousand and one "plz halp" threads on here a day. And I greatly apologize that I have to add to that.
Leading up to this problem, my wife's kindle fire was rooted by me two years ago. It had happily been running twrp and a custom rom [I believe cyanogenmod 9], working extremely well as a full tablet. My wife asked me yesterday if i could update it, as there were a few apps she had on her phone that she wanted on her kindle as well. Her phone runs CM11 and I was pleasantly surprised to find a CM11 rom for her Kindle. So I carefully read the instructions, fired up KFU 0.99, told the kindle to go into recovery bootmode, got into TWRP, updated it to 2.6.3.0, and did my normal ROM install steps from there. Factory reset, dalvik, and system. I installed the rom, then install the CM11 gApps zip, told it to reboot system. And it's been stuck at the stock kindle fire [white and orange] ever since.
KFU shows adb online, boot status unkown. ADB on every computer i've tried shows "0123456789ABCDEF offline" under adb devices. I have read through a rather large number of threads. Tried quite a few troubleshooting steps. Reinstalling drivers, three computers so far, soupkit on ubuntu live persistent, tried using an updated version of adb, tried the unbrick utility. Fastboot commands do nothing, adb commands give me device not connected.
At this point, I would be happy to even get into recovery. From what I have read almost everywhere, she's stuck in fastboot mode, but not responding to anything. adb reacts when i plug it in, but all adb, including soupkit on ubuntu, shows 0123456789ABCDEF offline.
As far as boot behavior goes, when i power on the device or plug it in when powered off, light turns green, two seconds later kindle fire logo comes on, light goes off, five seconds after the logo first appears, it flickers once. brightness remains the same.
Any and all help is appreciated. I have been scouring XDA looking for the same symptoms and haven't found them yet. Hence why I am starting a new thread.
Still Nothing? Trying on several computers, Windows 7 and 8, kali linux, and ubuntu, still no change. I cannot get the kindle to respond to fastboot or adb commands. SoupKit did not work. Followed thread instructions exactly and still no dice. ADB devices shows 1234567890ABCDEF.
How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
If it's in fastboot don't need the fastboot cable.
It could be in low battery mode
Sent from my XT907 using Tapatalk