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.
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
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
favaron88 said:
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
Click to expand...
Click to collapse
Do you have a bootloader installed? Can you boot into recovery?
Eaffon said:
Do you have a bootloader installed? Can you boot into recovery?
Click to expand...
Click to collapse
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
favaron88 said:
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
Click to expand...
Click to collapse
Hmm... Does it show up in device manager?
Dont throw it.. give it to me. Haha
After my sem I will have plenty of time to do all this stuff..
Sent from my SGH-T999 using xda premium
Eaffon said:
Hmm... Does it show up in device manager?
Click to expand...
Click to collapse
I've uploaded a screen shot of my device manager and in "devices and printers"
as you can see, it shows up as a kindle in devices and printers, and as an android phone in the device manager.
I also uploaded "My Computer" so you can see there is no access to it from there.
Okay.
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Eaffon said:
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Click to expand...
Click to collapse
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
favaron88 said:
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
Click to expand...
Click to collapse
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Eaffon said:
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Click to expand...
Click to collapse
alright, I found it and tried those commands and this is what I got.
favaron88 said:
alright, I found it and tried those commands and this is what I got.
Click to expand...
Click to collapse
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Eaffon said:
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Click to expand...
Click to collapse
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
You could try my prefab ISO soupkit is already ran on it and it has teamviewer installed for assistance measures you can find it here post 7 http://forum.xda-developers.com/showthread.php?t=1413358 but what I think you will need is a factory cable found here ultimately post 9 http://forum.xda-developers.com/showthread.php?t=1392693 . The system is trying to run that's why it comes up android composite adb interface, its busy trying to handle the data that you failed to wipe prior to flashing jelly bean and then stock. You could also see if if will allow you to send twrp and fff back to the device with kfu then enter recovery wipe and reflash another ROM.
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
It's totally fixable.
Thepooch is right. My brother had the same problem with his son's. Just get into fastboot and flash a bootloader and twrp and youre set
Sent from my Amazon Kindle Fire using xda app-developers app
Thepooch said:
It's totally fixable.
Click to expand...
Click to collapse
Awesome
Also I didn't want you to think I ignored your post. I just finished making the usb drive with ubuntu on it and was going to attempt your solution in the other thread if whatever we were trying here doesn't work.
I appreciate y'alls help very much.
Eaffon said:
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Ok I loaded KFU and told went and told it to boot in fastboot, it said that it told the device to do it, but it still says Boot Status: Unknown.
Is this a problem or do we know that it's booting in fastmode now? I'm just not sure how to tell if it was successful since it's not giving me the code.
(Ps - I originally posted this before my previous post thanking you guys, but then came back to this window to see that I had screwed up the Captcha, but it wouldn't let me post for 5 more minutes since I'm a new user. Sorry for the wait.)
Its very common for the boot mode to be unknown in fast boot. Try to send twrp with kfu if it says waiting for device for a long time simply power it off while connected then back on it should then pick up and send twrp. If need be do the same thing with the bootloader just wait longer a failed bootloader flash is far worse than the situation your in.
favaron88 said:
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
Click to expand...
Click to collapse
ADB is connected, therefore you are not in fastboot. The Kindle Fire logo you see is actually the stock boot animation. The difference is whether or not it changes in brightness at any point (obviously it does).
You need access to recovery to fix your problem and you need the ability to change bootmodes to get into recovery. Without a working shell you need access to fastboot to change bootmodes.
Unfortunately, in many situations like yours, there is no working shell to change the bootmode. To confirm this, try to launch the shell by entering "adb shell", respectively.
If you receive an error, your only options are to get a factory cable (recommended) or open the device so you can put it in USBboot via the shorting trick and the use of Firekit (not so recommended).
With access to fastboot, you can change your bootmode to recovery or reinstall a custom recovery if necessary. In recovery, the "fix" is as simple as reinstalling a ROM.
"That's a special kind of stupid. The kind that makes me laugh."
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
Ok, So I am extremely stupid. I installed TWRP, and I clicked on the botton which says "Delete /System", So after that, It seems that when booting up, It displays the Kindle Logo, and that is it. Literally. And when I tries to unbrick it, none of the tools recognize it. I tried FastBoot cables, no luck. And now, the computer seems to recognize it in ADB, but it never able to push back the new bootloader and system file back, just says "Permission Denied", And when I tries to use Shell, it says "./system/./sh: File Does Not Exist"(Since the whole /system folder is gone...)... Does anyone know how to fix this? I'm willing to pay $10-40 for anybody that came up with a solution that works. Thanks. I am trying to fix this for a long time now, And I really don't know what to do at this point. I tried to access TWRP, but it doesn't seems to work anymore. The blue logo doesn't show up.
And I am not sure if this helps, but it is a Kindle Fire 1st generation. It have been lying in a corner of the house for a couple of years now, and I just never been able to fix it,
And it is a Kindle 1st Gen.
connect to pc, power off Kindle, send command
Code:
fastboot devices
Power on kindle
what is response?
Sent from my KFFOWI using Tapatalk