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.
UPDATE: I added "solved" to the title since I am now unbricked. That said, I do hope someone will pop in and tell me how to run the shell scripts on a mac...
Click to expand...
Click to collapse
Hi there. I have spent several days searching xda forums, popping into the kindlefire irc channel, and searching google however have not yet figured this out, could use some help.
I have read: the Kindle Fire Beginners Guide, the Kindle Fire Unbrick thread, The Kindle Fire Utility thread (yup the whole thing), and more.
According to the Kindle Fire Beginner's Guide, only 1% of all brick situations are actually a brick, so I'm going to persevere and go ahead and ask for the help, because also according to the guide, if your fire can't be seen as a device then actually it's a brick. To quote: " unless something else was done to the device after the change in bootmode preventing access to adb or fastboot commands. Then it’s actually a brick at that point."
I can't be sure if anything else was done after the change in bootmode so I'll just explain how I got here and hopefully someone can help out.
I have a mac mini running Os x 10.6.8, and the Kindle Fire which was running stock version 6.2.2.
I used the kindlewater root method to install firefirefire and cwm recovery. Was able to boot into recovery by pressing on the power button for it to go orange and then load the recovery options.
Before doing anything at all (and in consultation with St3p_2 of this forum, one of the kindlewater developers), I decided to perform a backup in preparation for flashing a ROM.
so, I booted, went into recovery, navigated to "install a .zip" and chose "backup" at which point I got a message/nag/reminder that this was a permanent change, and I selected "ok". It did it's thing for a while, went into reboot, and I then had the firefirefire logo blinking in a very very slow loop.
It was recommended to me to perform a factory reset by holding the power button for 2 solid minutes, which should then have returned me to stock. Actually, the first time i did it for minutes I went from having a very slow blinking firefirefire to having a rather fast blinking firefirefire. Following a suggestion i then tried it with the kindlefire unplugged. This resulted in a plain black screen until the fire was plugged in again: no boot, no indication of response to use of the power button. Once plugged in, it has gone back to the rather fast blinking firefirefire logo.
I read through the Kindle Fire Utility thread, found the v0.9.2 version prepared for mac and linux, and downloaded it. Although I am not new to terminal, I am not familiar with what command language is necessary to perform the actions required by this tool. If I open the install_drivers.sh with terminal, i get this:
Reverie:~ apple$ /kindlefire/Kindle_Fire_Utility_MacLinux_0.9-1.2/install_drivers.sh ; exit;
This file will install the correct adb_usb.ini file for proper Kindle Fire detection.
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
so I tried running it in the console. I will spare you the output of the console as it appeared to be merely a printout of the actual code of the file and was quite long.
Trying to run the file runme.sh in terminal before running the install_drivers.sh in the console, I got error messages stating there is no such command, or no such file, depending on my command language.
After running the install_drivers.sh in the console, when I try to run runme.sh in terminal, i get this:
/kindlefire/runme.sh ; exit;
Reverie:~ apple$ /kindlefire/runme.sh ; exit;
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure adb is in your path
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue... --- STARTING ----
--- WAITING FOR DEVICE
Which I affirmed because all the requirements had indeed been set that way on the device before the bricking happened. After "starting" and "waiting for device" nothing happens even waiting indefinitely (more than half an hour) and then it never finds the device.
When I go into terminal and type: "adb devices" I get:
Last login: Sun Mar 18 17:08:38 on ttys001
Reverie:~ apple$ adb devices
List of devices attached
Reverie:~ apple$
This result is the same both before attempting to use the 0.9.2 mac utility and after.
I really am stuck at this point, as everything I find with instructions on how to "unbrick" does require that the machine recognize that your kindlefire is attached. Running any of the tools I find requires that basic bottom dollar, which I don't seem to have.
That said, the behavior of "nothing at all: blank screen" when unplugged, and the behavior of "blinking firefirefire logo" when plugged in would tend to indicate that at the very least the device knows it's plugged in and getting juice, and some process is happening when that's true.
Can someone help? Is my next step to purchase a factory cable, or do I have a software solution available to me that I just didn't find in this haystack of solutions?
nothing doing when unplugged seems like a dead battery
would try to charge it with the wall charger for some hours regardless if the orange light comes up - this can last a while
furthermore i don't know which version of kfu for mac you'r using but zergrush is'nt working any more since stock rom 0.6.1
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
for rooting use kindlewater:
http://forum.xda-developers.com/showthread.php?t=1443071
as far as i know the commands need to be entered with a ./ in front ie: ./install_drivers.sh
sisterdelirious said:
Can someone help? Is my next step to purchase a factory cable, or do I have a software solution available to me that I just didn't find in this haystack of solutions?
Click to expand...
Click to collapse
Thanks for reading my guide. I hope it helped you a bit.
Mac OS X is also my primary OS and I take my hat off to you for even trying things this way. I took the easy way out from the very beginning and just used Parallels Desktop to build Windows and Linux virtual machines. If things ultimately don't work out, you might want to try going that route as well. I believe Parallels offers a demo version if you want to see it in action. Regardless, I don't think that matters quite yet, because I tend to agree with b63 here. I think the biggest problem you have right now is a dead battery.
I've never had a dead battery, so I can't comment directly, but take a look at this thread, starting at post #226...
http://forum.xda-developers.com/showthread.php?t=1392693&page=23
There some back and forth for a couple of pages, but that user describes symptoms that sound very much like what you are seeing right now. I think you should try the wall charger first. Plug it in, force the Kindle Fire to turn off and just try to let it charge overnight or something. If you cannot get your KF charged with the stock wall charger, you might want to buy a factory cable. From what I gather, that user reported that his Kindle Fire booted into fastboot mode by using the factory cable even with a (nearly) dead battery. He was then able to flash the stock software, which is able to handle the dead battery situation better than some alternative ROM and have it go through the charge cycle.
Wow... so simple...
b63 said:
nothing doing when unplugged seems like a dead battery
would try to charge it with the wall charger for some hours regardless if the orange light comes up - this can last a while
Click to expand...
Click to collapse
This was the deal. When plugged in with the usb cord it didn't seem to be giving it power and being powerless could not be recognized by the computer. Plugged it into the wall charger and Voila! was able to start up just fine, still rooted via the kindlewater method, capable of being booted normally or booted into CWM recovery. Awesome!
I also did a quick double-check, and now that it's powered-up, running a terminal and typing "adb devices" actually returns a list with the kindle (serial number?) on it.
furthermore i don't know which version of kfu for mac you'r using but zergrush is'nt working any more since stock rom 0.6.1
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
Click to expand...
Click to collapse
I read through everything and the version of kfu that was modded for mac was 0.9.2 which I mentioned in my original post. Sounds like since I was on 6.2.2 that mac version is definitely not going to help me (both kfu out of date and stock version out of date on zergrush) if I were to want it for rooting purposes.
for rooting use kindlewater:
http://forum.xda-developers.com/showthread.php?t=1443071
Click to expand...
Click to collapse
that is the one i used. I was looking for a mac tool for post-root rescue methods...i had thought that the kfu mac version had valuable rescue/unbrick capabilities but at this point I don't remember.
as far as i know the commands need to be entered with a ./ in front ie: ./install_drivers.sh
Click to expand...
Click to collapse
[/QUOTE]
Thankfully, I don't need to try that. my kf got properly unbricked just by plugging it into the wall charger.
Great guide, it was the battery
kinfauns said:
Thanks for reading my guide. I hope it helped you a bit.
Mac OS X is also my primary OS and I take my hat off to you for even trying things this way. I took the easy way out from the very beginning and just used Parallels Desktop to build Windows and Linux virtual machines. If things ultimately don't work out, you might want to try going that route as well. I believe Parallels offers a demo version if you want to see it in action. Regardless, I don't think that matters quite yet, because I tend to agree with b63 here. I think the biggest problem you have right now is a dead battery.
Click to expand...
Click to collapse
Thank you for your guide. I thought it was extremely well written and very helpful. It definitely helped me relax a little stress-wise while looking for a solution.
That was it (dead battery). I did try meddling around a bit with virtualbox virtual machines: a windows 7 ultimate, and a linux box that I have that does not have internet access making doing anything realtime while reading suggestions just isnt easy/feasible right now. I found that the virtualbox vms did not have access to the usb devices (flash drives, external hard drives, ostensibly if it were visible to the computer the kindle) despite my installing some optional extension packs for that purpose. I didn't explore the vms further to linux or xp simply because of the time required to install and configure a vm. I also didn't rewire my home so net access went to the linux box for the same reason... ultimately both are possible but both more hassle than it seems to be worth before simply asking the question, can it be done on a mac?
I've never had a dead battery, so I can't comment directly, but take a look at this thread, starting at post #226...
http://forum.xda-developers.com/showthread.php?t=1392693&page=23
There some back and forth for a couple of pages, but that user describes symptoms that sound very much like what you are seeing right now. I think you should try the wall charger first. Plug it in, force the Kindle Fire to turn off and just try to let it charge overnight or something. If you cannot get your KF charged with the stock wall charger, you might want to buy a factory cable. From what I gather, that user reported that his Kindle Fire booted into fastboot mode by using the factory cable even with a (nearly) dead battery. He was then able to flash the stock software, which is able to handle the dead battery situation better than some alternative ROM and have it go through the charge cycle.
Click to expand...
Click to collapse
I'm just so glad this worked. Thank you for your help!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Similar issue
My KF is seeming to have a similar but distinctly different issue as the OP. Because I can turn on the KF without it being plugged in, I cannot imagine that it is a battery issue.
When I plug it in to a Windows machine, the FFF bootloader comes on, the KF seems to connect, be recognized, fail at driver installation (which I have done manually, with no success), and then disconnect. This prevents me from running any sort of commands.
When I connect to my Mac, I get the FFF bootloader and then no response whatsoever.
Trying to run commands from Terminal or the Command line or using KFU on my Windows machine all result in a "waiting for device" message.
Not sure what I should do from this point to get it back to accepting adb commands. I'm confident that once I do I'll be able to save it, but at this point I'm stuck.
Any ideas?
So, Ive been searching for over 6 hours now and I really cant seem to root my kindle fire. I tried basically everything, and when things went wrong, I just deleted the files and started again. On my last try, I was able to fastboot it (at least I think so). When I ran KFU, ADB was online and Boot: 4002.
When I tried to root it always got stuck trying to find twrd.img. Then I tried option number 4, Installing Clockwork Recovery (because option number 3 was a dead end) and twrd.img was installed. But everytime something seemed to go right, the process wouldnt finish, it would just be <waiting for device>. I thought my problems would be over, so I tried to root it again. Now whenever I turn on the device, KFU is unable to locate my kindle, and it doenst appear on the device managing tab either. Even using the kindleunbrick.bat that worked for me the last times, it just gets stuck at <waiting for device>. ADB is offline and Boot: Unknown for now.
I really need to root my kindle because I dont live in America, so I dont have access to most stuff. I already changed the language when installing the driver, however, everytime I hooked my kindle up, a windows message would pop out saying that there was a problem with the driver, but when I went to device managing tab and tried to uptade the driver to "user\.android" it always came back as updated.
I am really noob at this, but I have read all the guides I found and something always went wrong. I hope someone can help me with this, please.
Thanks
Is your kindle turning on? If I could suggest you should put off anymore attempts to root your device till you know precisely what your doing and why. My biggest guess right now is your drivers are the greatest pitfall. You seriously don't want anything going wrong with them in the process of sending recoveries boot loaders or rooting you will end up with a really fancy paperweight. Privy to to attempting anymore you need to know that your drivers are functioning 100%.The fact that you pushed cwmr to your device after twrp should hurt a thing hopefully one should overwrite the other if all goes well . Since rooting is the primary goal go with that until you have verified root then recovery and bootloader can be done easily later with safer methods. Hold off awhile as long as your device will boot until you have found the knowledge and support to make it happen right. Start here http://forum.xda-developers.com/showthread.php?t=1552547 then go here http://forum.xda-developers.com/showthread.php?t=1638452 plan to use this method to root http://forum.xda-developers.com/showthread.php?t=1568340 ask a lot of questions don't be hasty or you will spend a lot of time trying to fix it instead of enjoying it.
As I said, I read all those guides already. I can use my kindle normally, but when I connect it to my computer, it is unrecognized. I tried every method I found to root, even though I just wanted to watch stuff and download a few games for my spare time(my intention was to watch stuff from premium features, but Im not really sure if root will allow me to do that from a foreign country*, so Im a little hesitant to extend premium).
I guess I wont try anything else for now because my main goal was reading, and this I can still do, but I am puzzled with the fact that I was unable to root it. Ill try to understand a bit more (hopefully with some tips). Thanks
*Geographical restrictions
OK well youve read the guides but in what you say it appears you are doing some of the wrong things why would you unbrick if your not bricked? Your drivers are your only issue as of this point but your methods are pushing you close to bricking your kindle. I would like to see you succeed in rooting your device and avoid bricking it.
---------- Post added at 11:59 PM ---------- Previous post was at 11:36 PM ----------
When your around we can try to get your drivers working
It would be nice to know what os your running on your computer. If you are on windows 7 use system restore to roll your computer back to a date before you started messing with the drivers or anything. Once it completes plug your kindle into your computer check to see if you can access the SD card contents and if it appears as a kindle in your device manager. Important now if all is good unplug your kindle and run the .bat file that comes with kfu. Then plug your kindle in let windows install the driver. Open up kfu find the tools folder shift plus right click select open command window here. Then type adb devices if its followed by a string of numbers this shows your kindle connected via adb . At this point you should obtain some help from some of the pros here at xda at fastboot and adb commands to safely root your kindle. If you decline and still wish to use kfu then only select install permenant root. If at any point in this process it fails and you loose adb connection do not unplug your kindle run the driver file again then recheck device status with kfu I believe its option 0 to see if your back online again. Pay attention to the dialogue that takes place in the kfu window you see verbatim that says failed or permission denied then quit after that. One important thing is you need to allow installation from unknown sources in the kindle settings on the kindle under device or it won't push the required files anyway.Wait to install twrp and fff until later there are easier safer methods. If your kindle hangs for a long time at the kindle fire logo select boot mode normal in kfu before unplugging. If at anytime kfu states waiting for device do not unplug it rather power it completely off then power it back on while connected .
---------- Post added at 01:53 AM ---------- Previous post was at 01:32 AM ----------
Just a side note I have rooted 4 different times with kfu without a single failure or mishap including the ones you are experiencing. I'm inclined to feel that relates mostly to your computer and drivers which makes kfu an unsafe approach for you I'm not responsible If you brick it!!!
I unbricked my device before I even came here, I tried an youtube tutorial and then it got stuck on the kindle fire logo, but after I unbricked it, it was fine. I know that something is going wrong, but Im following step-by-step the guides (at least I think so). As I said, everything was going correctly, ADB was online, Boot:4002, but when I tried to root it would be on an endless search for the file twrp.img, and after I succesfully downloaded it (I guess), my computer is unable to find my Kindle.
I run Windows 7, but it isnt properly activated (my room mate threw out the serial code), I dont know if this would interfeer in any way. When I conect the kindle, it appears to be in USB mode and says that I can transfer files, but my computer wont even find it. Ill try to restore my computer now and then Ill come back.
I know that doing this is my responsibility, but not being able to download apps is pretty annoying, so I have to keep trying.
If you can get adb status online then, why don't you install TWRP manually? Or use the "smirkit"?
Once you get recovery installed, you're set.
Also, be sure to "disconnect" from USB storage mode before trying to use adb commands or they won't work.
I dont even know how to use ADB comands. Is there anyway to make my computer recognize my kindle other then doing a system recovery? I dont know how to do that, and after searching, they say I need the CD (which I dont have).
Shift+right click your KFU "tools" folder and select "Open command window here"
From there, enter:
Code:
adb devices
If the output is something like:
Code:
List of devices connected
123456789ABCDEF
then you can install TWRP
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
If the output is:
Code:
List of devices connected
(null)
then you need to reinstall your drivers
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Thank everyone that helped me, I managed it!
Actually I was doing everything right, but I guess the problem was my computer, because when my girlfriend came over I tried connecting it to her netbook and it recognized my kindle. I just downloaded the kfu, installed drivers, reconected kindle and let it update, ran KFU and selected option 2. All done now
I have no idea why this didnt work before, but at least now I can really enjoy my kindle.
Thanks again!
saybhausd said:
I dont even know how to use ADB comands. Is there anyway to make my computer recognize my kindle other then doing a system recovery? I dont know how to do that, and after searching, they say I need the CD (which I dont have).
Click to expand...
Click to collapse
Not system recovery bud system restore two different things go to accessories system tools system restore choose a date chose to restore to that point. System recovery is way way different. Glad you got it going
It has been an awful while since I have posted on a forum, let alone start a thread; Yet, after the "ordeal" I just endured it seemed as though I ought to share what had happened with hope that it may help someone in the future. I apologize if all this is in the wrong sub/sub/sub-forum or anything like that, kindly let me know and I will do my best to rectify my mistake.
So I got a Kindle Fire HD 7" today and the first and most painfully apparent aspect of the device which I noticed was that Amazon decided to viking-rape android; I don't care what anyone says, what they did- well, it's awful. Not being too much of a stranger to rooting, user ROMs, and the like, it seemed only natural for me to try and pursue something similar with this device. So, I do the research, settle on a first ROM to try and hope it's a keeper, gain root, get TWRP working and would you believe it: I forgot my ROM.
Well, I assumed that the Kindle HD would just send me back to the AmazonOS or whatever they call it- but it didn't. It simply kept oscillating from the white/orange kindle logo to the white/blue. I started to get a bit worried, but it's been quite a while in Android (in almost any software/OS, really) when getting bricked means getting BRICKED. So I did some more research. Simple solution worked for me to get me back into recovery:
If your Kindle Fire HD 7" is continuously booting ("bootloop") after installing TWRP
Try holding down the "volume up" section of the volume toggle when the white/orange kindle logo appears, just like you did when you first installed TWRP, for at least three seconds. There's no vibration and nothing changes, really- it seemed like it would bootloop for 10 minutes again, but instead this time after about maybe one minute I was back into TWRP.
At this point, the plan was to ADB my ROM and GAPPS to the Kindle. Unfortunately, for whatever reason the Kindle Drivers that had served me so well, until this point in time, ceased to form a connection between the two devices. This happened at 3pm- it is now 9:20pm (as of this sentence) and I finally got it to work. I will spare you descriptions of all the things that were tried which did NOT work. Needless to say, I did in fact try a significant number of "solutions," and yet; only one thing (or a combination of things culminating with this one thing, in which case maybe i SHOULD try and list everything else I tried... but I can't remember it all so nevermind, anyways...) wound up working then and now:
If Your Kindle Fire HD 7" is not being recognized by your PC
First download these drivers from XDA user stunts513.
Then connect your kindle to the PC. Navigate to "Device Manager." The most simple way would be to type "Device Manager" into the search box located in the Windows Start Menu. If you don't see "Kindle" (it may be under "Other devices") then this solution will not work for you, and you might have an issue with your hardware (perhaps either the Kindle, the PC, or the USB cable.) If you see "Kindle" it will most probably have a yellow triangle on it; if so- lets continue.
That file you downloaded a moment ago is designed to be a component of ADB (this thread is not the place to explain ADB, how to install it or use it; if you are asking those questions at this point I urge you to turn to the XDA search bars and 'ole Googly before proceeding.) Next, regardless of if it actually "does" anything or not, I moved the "usb_driver" folder to the appropriate ADB sub-directory ("c:\Android\sdk\extras\google" in my case, perhaps not in yours, but really i don't think this aspect matters much, anyways.)
Returning to the Device Manager: At this point you may right-click on the "Kindle" listing with the yellow triangle. Having messed around with various drivers I thought it would be a good idea to click on "uninstall." After that I unplugged the Kindle and plugged it back in. It came back up in the list with a yellow triangle. At this point I highlighted and clicked on "Properties." Then selected the option that states either "Update Driver" or "Install Driver," can't remember really. A new window opens and asks if you want Windows to search for a Driver, or if you want to. Say you want to manually designate a driver. This should launch a file browser and now you can navigate to where you placed the "usb_driver" folder earlier. I went as far as "c:\Android\sdk\extras" before checking the "search sub-directories also" check box. Windows foudn the driver, installed it and HOLY MOTHER OF GOD I GOT MY ADB BACK.
At that point I pushed my stuff to the Kindle, flashed it and went merrily along. Hopefully this helps someone- if not, my bad; I still love you all. Except for Jim. **** Jim. He knows what he did.
BAI GAIS!
wrong forum my friend...
http://forum.xda-developers.com/forumdisplay.php?f=1784
My kindle fire 2 rooted was working fine until I launched this program called GOLauncher. I didn't like it and tried to uninstall it, but the darn thing wouldn't remove and the the next time I turned on my kindle, all I would get was a flashing loading screen. Nothing else. I soon thereafter discovered (when the 1-step program I had previous successfully used about 10 times before) would go no further that daemon starting. I noticed that instead of a Kindle in my device manager, there was now only a Portable Device with E: showing as active.
I've tried every solution I could find from here, but 90% of them assume you have the whole driver .exe to install or some other such stuff. Every driver that doesn't, doesn't work for my computer, and won't put the kindle device back on my computer. So now, I have no way to communicate between my kindle and my computer, which I need to do frequently.
I've uninstalled each adb between installs, I've tried all the drivers I can find, I've deleted hidden devices (there were no kindles there either)
Plus, I can't get these apps I installed on the third party sites (which I miss) to uninstall. All they say is "move to favorites" in both my app folder and in the cloud. I am assuming it's because I no longer am able to access those sites.
Could someone please help me? I'm pretty computer literate, except where it comes to DOS commands. Sigh, the one thing I didn't learn in high school.
I promise I've been spent the last 5 days and nights (and even restored my device to factory settings just to get it to work) searching through so many pages of this site that I'm starting to get confused. Will someone please help me?
OK lemme get this straight, you are stuck in a boot loop at the kindle logo and want adb access but nothing is showing up( except maybe a portable device)? If its showing up as a portable device during a boot loop that strikes me as odd, usually you don't have adb access during a bootloop , much less and mtp connection. If it's stuck in a boot loop you will typically need a fastboot cable to get out of it. Also what os are you running? I might be of more assistance after I get a better idea of what your kindle is doing exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK lemme get this straight, you are stuck in a boot loop at the kindle logo and want adb access but nothing is showing up( except maybe a portable device)? If its showing up as a portable device during a boot loop that strikes me as odd, usually you don't have adb access during a bootloop , much less and mtp connection. If it's stuck in a boot loop you will typically need a fastboot cable to get out of it. Also what os are you running? I might be of more assistance after I get a better idea of what your kindle is doing exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
This is what happened. I installed a program from the Google Play store, wasn't happy with it, and botched the uninstallation. I was messing around on my computer to see how I could fix the problem (after just rooting hubby's kindle fire 2nd generation and discovering I had not ADB drivers and my device manager wasn't recognizing my requests). I notice that once again the kindle is missing on device manager when plugged in to the computer. What is showing up is a Portable Device labeled E:. So I go looking for answers here.
One of the things I noticed I could do with the broken kindle was that about 1 out of 5 times it was on, I could swipe the top of the screen and have the settings menu come up. And out 1 out of those 5 times, I could actually get a setting to appear by pressing on it. So I literally spent 17 hours trying to time the swipe, press, press to get the restore to factory settings program to work. And when it finished, I had a useable device, but all the kindle programs were gone (they were still on my cloud) and I could run all the programs installed from other android stores (but I can't uninstall them). And, of course, I can't get my computer to recognize the device. But I do have program called file manager that allows me access to shared files on my family's three computers so I can transfer files over the LAN if I need to.
I hope that helps. Thanks for taking the time to help me.
I am running an Intel i5 with 64-bit Windows 7 Home Premium Service Pack 1. It has all Microsoft updates and it is my pristine baby that I bought 18 months ago (my last computer was 9 years old that I built with an AMD processor and an 17 and 20 GB hard drives that were donated to me. It was a real POS, but it's still running to this day as a backup.
I know the feeling, before i got my new laptop from a friend a few weeks ago i had a pc with a pentium 4 and 2gb of ram, and like 3 hard drives. Anyways I'm assuming at this point you want to try restoring the system partition? Have you tried the drivers in my signature for adb access? If you can reboot into fastboot you could restore the system image from kindle fire first aid, should fix any problems with the os. It all depends on if USB debugging is turned on on your kindle, and if you can get the PC to detect it as such, usually I would just uninstall the MTP device and try searching for drivers on the new device detected and point it to my drivers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Have you tried a factory reset?
--》Sent from my mind to your screen
mindmajick said:
Have you tried a factory reset?
--》Sent from my mind to your screen
Click to expand...
Click to collapse
Thanks for both of your information. I did get the ADB drivers to show up - in the most stupid of ways. I changed from by brand new monster gold plated cable to a Wal-Mart special. Suddenly, everything worked perfectly! I use KFFirstAide to restore the device to the #1 setting, and then rooted it using the #23 setting. I also installed the Google Play store (though I installed the wrong, more complicated, version of if the first time.
Now I have a problem I can't see to fix. Ever since I got everything set up, there are certain programs on my kindle (cloud and device) that I can't get rid of. They are No Lock, Talk, News & Weather, Majic Locker, Google Voice, and Gl Launcher HD. I've tried downloading both ES Task and File Manager and deleting or startup disabling these apps, and while they say they are deleted, they reappear back on the active list as soon as I turn on my device (yes, I've rebooted), but I can't get them off my kindle Apps pages. And Go Launcher starts up every single time I turn on my device, and I hate this program, because it is not what I was looking for. Now I always have to look at it.
These .apk's are all in the system/apps folder. That's why I've tried to use the above file apps to get rid of them.
Also, my Silk browser doesn't work (I can open it and it immediately closes), and while I know I can download dolphin browser or firefox, I want the browser built for tablet speed and efficiency. Plus, when I had multiple browsers before, I always got the popup asking me which app I wanted to use to perform that function. But I can't find an apk for silk anywhere, and my device won't uninstall Silk.
Can anyone help? I feel so stupid about the cable issue. You wouldn't think a 3 day old cable would not properly transfer data.
OK to fix your launcher, go into the setting>apps and find go launcher and clear its defaults. That's kinda unspecific but I haven't been on amazon os for a while. To get rid of system apps, use es file explorer, enable root access, if on the older version, mount the system, if you have a panel on the left its the new version. Anyways from there you can simply hold down on the app and hit delete. Not too sure why silk isn't on the list. Though I though I might say consider this, you have no way of using flash with silk, so other browsers are kinda useful because you can. Then again I like flash. Kinda sounds like silk got deleted.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Not entirely true
stunts513 said:
OK lemme get this straight, you are stuck in a boot loop at the kindle logo and want adb access but nothing is showing up( except maybe a portable device)? If its showing up as a portable device during a boot loop that strikes me as odd, usually you don't have adb access during a bootloop , much less and mtp connection. If it's stuck in a boot loop you will typically need a fastboot cable to get out of it. Also what os are you running? I might be of more assistance after I get a better idea of what your kindle is doing exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have gotten several tablets to respond to ABD commands while soft bricked or not booting all the way. This is actually how I became an authorized MID repair facility. I have repaired a few kindle's that would only boot the to logo. If the device is loading as portable device, go to device manager, update driver for portable device, manually update the driver to whatever ADB driver you have extracted and it should at least respond to adb wipe command. once done you should be able to use the KFU to restore the tablet to factory state.
At least this is the process that has worked for me several times.