[Q] Gederom serious problem here help me pls! - Kindle Fire Q&A, Help & Troubleshooting

first of all thanks for the excellent rom.since im just trying out this new rom,im intending to change my rom back to modaco gr8 after trying out for some time.
But here's the trouble here.i always can't seem to access twrp through my kf.Each time what i did was i connect my device with USB to the pc and use kfu to reflash twrp to gain access.
But now with this gederom,my pc can't seems to detect my kf and it keeps saying driver is needed.
So what can i do now to once again gain access to twrp??
please please help me im really panic now.

chaukeng said:
first of all thanks for the excellent rom.since im just trying out this new rom,im intending to change my rom back to modaco gr8 after trying out for some time.
But here's the trouble here.i always can't seem to access twrp through my kf.Each time what i did was i connect my device with USB to the pc and use kfu to reflash twrp to gain access.
But now with this gederom,my pc can't seems to detect my kf and it keeps saying driver is needed.
So what can i do now to once again gain access to twrp??
please please help me im really panic now.
Click to expand...
Click to collapse
I had to read this post a couple of times just to make sure I'm not going crazy. So you have been using the KFU to REFLASH recovery every time you want access to it?!
I'm not going to be nice and not say what I really want to say. But do yourself (and everyone here) a huge favor and thouroghly read this thread...
http://forum.xda-developers.com/showthread.php?p=23747567
...before you do anything else on your Kindle and potentially do damage to your device. HINT: the problem isn't the rom
[Edit:] When you're done reading the above posted thread, read this one for good measure:
http://forum.xda-developers.com/showthread.php?p=19837228
Sent from my Amazon Kindle Fire using xda premium

the link is broken.any way to read that?
i Doesn't know what im doing is wrong since no one replies to me in my local forum.
and also i flashed modaco gr8,uses it for around 1 month and its been working great.
But now i realise my mistakes now and any way to change this?
just want to reflash this to my modaco.thanks!

XDA Won't let me copy the full link for some reason.. Go to the General forum under stickies and select Kindle Fire for Beginners.
[Edit:] fixed try again
Sent from my Amazon Kindle Fire using xda premium

sorry first one still can't open.
I know once i reboot my kf i have to either long press or press twice to get my switch into orange colour to get into recovery mode.
But since mine is not the fire triangle anymore (its an android doll on top of the 'kindle fire' logo.i doesn't know why mine is this version but i've read alot with this also ). i couldn't access recovery through the aforementioned method anymore.i tried to ask many people even natmile on facebook and i've got no confirmation from them until now.
i did do some readings including the one for the beginners and i do search for my problem on why i can't access to my recovery.But i just can't find an answer.really need your help.

chaukeng said:
sorry first one still can't open.
I know once i reboot my kf i have to either long press or press twice to get my switch into orange colour to get into recovery mode.
But since mine is not the fire triangle anymore (its an android doll on top of the 'kindle fire' logo.i doesn't know why mine is this version but i've read alot with this also ). i couldn't access recovery through the aforementioned method anymore.i tried to ask many people even natmile on facebook and i've got no confirmation from them until now.
i did do some readings including the one for the beginners and i do search for my problem on why i can't access to my recovery.But i just can't find an answer.really need your help.
Click to expand...
Click to collapse
The "yellow triangle" logo is the FireFireFire bootloader (version 1.2). The "kindle fire" logo with android is also the FireFireFire bootloader (version 1.3). Recovery selection for both versions is the same, only the time span given for you to make the selection has been reduced in v1.3. My guess is that you are not pressing the power button at the right time to make the selection.
This is the thread for FFF v1.3...
http://forum.xda-developers.com/showthread.php?t=1541043
In the first post, it gives you directions on how to make the recovery selection...
Recovery Selection - As the Kindle Fire boots up, the power button LED will change from bright green to a dim green. Once it changes to a dim green, press the power button again and release (repeat a few times to be sure). The LED will then change to an orange color indicating recovery selection and boot into recovery.​
Personally, I keep my fingernail on the button and as soon as the reflection goes dim, I press/release several times. If you want to be absolutely sure, keep pressing/releasing until the LED goes orange. This always works for me without fail. If the LED goes orange and it doesn't get to recovery, something is wrong with your recovery.
As far as gedeROM goes, look in the notification area and make sure it says "Android debugging enabled" when you have it hooked up to your computer. If you still can't send it adb commands, then it's likely a device driver issue. Read the second post of the first link soupmagnet gave you.

chaukeng said:
But since mine is not the fire triangle anymore (its an android doll on top of the 'kindle fire' logo.i doesn't know why mine is this version but i've read alot with this also ). i couldn't access recovery through the aforementioned method anymore.
Click to expand...
Click to collapse
That is a very important piece of information that would have been useful from the beginning. There is no reason for the new version of FireFireFire (Kindle fire logo w/android) to work any differently from the old one (yellow triangle) in regards to entering recovery.
Try reinstalling FireFireFire to see if that fixes the problem.
Sent from my Amazon Kindle Fire using xda premium

sorry...i was too nervous and missed this...thanks for both of your help.i will try the above method and see whether it works.
and i can't reinstall firefirefire since my pc won't detect my kindle fire.and it now detects it as p1000 (samsung galaxy tab).

chaukeng said:
sorry...i was too nervous and missed this...thanks for both of your help.i will try the above method and see whether it works.
and i can't reinstall firefirefire since my pc won't detect my kindle fire.and it now detects it as p1000 (samsung galaxy tab).
Click to expand...
Click to collapse
Try fastboot mode in KFU. Option 1, when it show <waiting for device> then connect the KF, hold down the power button untill it shut down, and hold button again to turn it on.
If you can somehow get to fastboot, try flash TWRP again.
Sine you can get in to FFF, I strongly believe that it's still alive.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2

reinstall drivers
chaukeng said:
sorry...i was too nervous and missed this...thanks for both of your help.i will try the above method and see whether it works.
and i can't reinstall firefirefire since my pc won't detect my kindle fire.and it now detects it as p1000 (samsung galaxy tab).
Click to expand...
Click to collapse
I think you need to go in to device manager and uninstall the drivers and reinstall the drivers . Try it out

i tried using kfu and use fastboot.but can't detect.
since gedeROM design to change our kf into galaxy tab,can i manually change and allows the pc to detect my kf as a kindle fire?Then probably i would have access to kfu.
btw i tried pressing the button but still couldn't access twrp through device.

You're in a pretty tricky spot. Apparently, the way GedeROM was set up, it is causing problems with adb connecting. But it all boils down to a driver issue. You need to somehow get into twrp to flash a different rom and see if it is the rom causing your original problem. But without access to recovery or USB debugging, I can't think of anything that will help you.
Try uninstalling and reinstalling your device drivers until you can get a connection long enough to change your bootmode to 5001 in order to get back into recovery.
You need to be able to get a solid connection with adb and fastboot to further troubleshoot your problem and it looks like you can't do that with the rom you're using.
Sent from my Amazon Kindle Fire using xda premium

I have the same problem, loaded GedeROM got in fatboot, and now I am stuck.

okay.somehow i've managed to get USB mass storage working.But KFU still shows offline.
But then i found out if i ask the kfu to help me boot to recovery it may still works.But can i do this and get to recovery and flash back my modaco?
Or should i manually flash my twrp again?

Flash MoDaCo to see if that helps. If not, reflash twrp. If not still, reflash firefirefire.

very nervous...i flash twrp again and i get to boot into recovery.omg....now im restoring into my modaco backup...hope it works.
Btw my kfu status is now 'online'
thanks so much soupmagnet!
But what if my kf still can't access twrp,should i do everything from the start manually?

power butoon
chaukeng said:
first of all thanks for the excellent rom.since im just trying out this new rom,im intending to change my rom back to modaco gr8 after trying out for some time.
But here's the trouble here.i always can't seem to access twrp through my kf.Each time what i did was i connect my device with USB to the pc and use kfu to reflash twrp to gain access.
But now with this gederom,my pc can't seems to detect my kf and it keeps saying driver is needed.
So what can i do now to once again gain access to twrp??
please please help me im really panic now.
Click to expand...
Click to collapse
start by powering your of, no need to connect anything ( USB) just make sure the from is in your of SD card wait for the yellow triangle any press several times with 3 sec intervals, until twrp shows up...hope this helps you...

ADB Not Working After GedeROM
I've been using the 28-04-2012 GedeROM all weekend, and it works fine, but I still haven't been able to get ADB working. I checked Android Debugging under Developer Options. On my PC, the KF only shows up in my Device Manager as a Disk Drive with the designation "Am", not as an ADB device, and the ADB Devices command doesn't show any devices attached. My computer thinks its an empty disk drive (no data). I have a regular Windows x86 PC. I try and try but I can't re-install any other driver to get the PC to recognize it.
Funny thing-- I tried recovering my stock system and data from TWRP (after factory wiping GedeROM), and it didn't work, I just get a dim lit screen on reboot. GedeROM re-installed ok, so I'm not too upset, just wondering why I can't go back.
I searched around on the lists but didn't see any idea that worked. Any suggestions would be greatly appreciated.
Thanks- Roger

Roger Dives said:
I've been using the 28-04-2012 GedeROM all weekend, and it works fine, but I still haven't been able to get ADB working. I checked Android Debugging under Developer Options. On my PC, the KF only shows up in my Device Manager as a Disk Drive with the designation "Am", not as an ADB device, and the ADB Devices command doesn't show any devices attached. My computer thinks its an empty disk drive (no data). I have a regular Windows x86 PC. I try and try but I can't re-install any other driver to get the PC to recognize it.
Funny thing-- I tried recovering my stock system and data from TWRP (after factory wiping GedeROM), and it didn't work, I just get a dim lit screen on reboot. GedeROM re-installed ok, so I'm not too upset, just wondering why I can't go back.
I searched around on the lists but didn't see any idea that worked. Any suggestions would be greatly appreciated.
Thanks- Roger
Click to expand...
Click to collapse
You need to reinstall the drivers. Long explanation at this link...
http://forum.xda-developers.com/showthread.php?t=1625356

ADB on GedeROM
Thanks for the advice Kinfauns, I'll read your article and try to reinstall the drivers again tonight. I did try over the weekend, checked the drivers, made sure they didn't change somehow, but the system wouldn't accept the drivers-- either "not better than what is already installed", or "can't find any drivers". My PC seems to recognize the KF as a disk drive, not as an ADB or Android device, so it's like the PC isn't even looking for my driver to be a suitable driver for the "Am" disk drive.
Thanks for your help!
Roger

Related

[SOLVED] Stuck on Kindle Fire screen... (and tried EVERYTHING)

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.

[Q] Kindle stuck at static Kindle Fire logo

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]

[Q] Kindle Fire bricked, have factory cable but can't boot recovery, please help!

Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail
farkuldi said:
Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail
Click to expand...
Click to collapse
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.
Socially Uncensored said:
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.
Click to expand...
Click to collapse
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!
farkuldi said:
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!
Click to expand...
Click to collapse
The unbrick program didn't work. It just stayed there t <waiting for device>. How can I use the fastboot cable to fix it?
Thanks.
I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC
ezproxy said:
I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC
Click to expand...
Click to collapse
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.
farkuldi said:
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.
Click to expand...
Click to collapse
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159
ezproxy said:
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I'd say you didn't read the previous posts.
Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.
farkuldi said:
Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.
Click to expand...
Click to collapse
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.
Socially Uncensored said:
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.
Click to expand...
Click to collapse
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?
Gon Rouge said:
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?
Click to expand...
Click to collapse
post in correct forum
Fire Index: Which Amazon (Kindle) Fire Do I have?
"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.
jerry777888 said:
"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.
Click to expand...
Click to collapse
Repost what?
Sent from my ocean using XDA Labs

cm10 logo stuck, boot status unknown, ect

ok first here is my problem
I have a Kindle fire that is stuck at the boot logo for cm10 from what ive found out due to not clearing the cache prior to rebooting
also with KFU running and the KF hooked up it reads adb status online and boot status unknown. when hooked up through the regular usb cable it goes through to the cm10 boot logo and is recognized by the computer and kfu
when hooked up trhough the factory cable its neither recognized by my computer or KFU and only stays at the kidlefire orange and white logo.
NOW how i got here
little sister got the KF and of course wanted more out of it. rooted and installed twrp and proceeded to flash roms through twrp SHE DIDNT INSTALL FFF. she said she got it stuck first on the AOSP? boot logo also what we later found out from not clearing the cache. then was able to get in through KFU to reboot back up to recovery and flash back to factory setting but still with twrp installed. well then went on to flash cm10 again without clearing the cache AFTER flashing the final gapps before rebooting and got it stuck yet again at the boot logo.
so with her being out of town i wanted to fix it for her so i got a factory cable and what not but wanted to try first through kfu so i hook it up and its recognized and what not well when i go to push 1 for bootmodes i accidently hit 4 i think and starting installing twrp AGAIN while it was STUCK at the cm10 boot logo. and that was the last thing that got me stuck to where the boot status isnt noticed
WHAT IVE TRIED. everything
kfu doesnt find the file for bootmodes now so i tried command prompts and thats saying device offline
so i got a factory cable and that makes it to where the computer AND kfu dont recognize it at all???
i also get with the regualr usb cable MTP USB device FAILED with the litt;le yellow caution triangle under Portable Devices but
shows it under Android Phone as Android Composite ADB interface???
but as stated with the factory cable it IMMEDIATELY says USB DEVICE NOT RECOGNIZED
with regular power it boots and gets stuck at the cm10 logo screen
with factory cable it only goes and stops at the orange and white kindle fire logo
i hope ive provided everything i can and hope someone can help out. thanks guys and its been some great reading on this site
Remi85 said:
with factory cable it only goes and stops at the orange and white kindle fire logo
Click to expand...
Click to collapse
This means your bootloader is not the FireFireFire.
Remi85 said:
i also get with the regualr usb cable MTP USB device FAILED with the litt;le yellow caution triangle under Portable Devices but
shows it under Android Phone as Android Composite ADB interface
Click to expand...
Click to collapse
Reinstall Kindle Fire Drivers from the Kindle Fire Utility package. Unzip your download and run the install drivers batch file. Then try to plug the Kindle in again.
Remi85 said:
but as stated with the factory cable it IMMEDIATELY says USB DEVICE NOT RECOGNIZED
with regular power it boots and gets stuck at the cm10 logo screen
Click to expand...
Click to collapse
Best way to get things working here is to run Kindle fire utility, run the "intall FireFireFire" option, it will say waiting on device, with your kindle off, attach the Factory cable to the kindle and then plug it into the PC. Hopefully this will get the bootloader installed, and while you're at it, go ahead and reinstall TWRP, as it shouldn't cause an issue. After you get the bootloader and TWRP installed, you can wipe caches and see if that helps.
mthous01 said:
This means your bootloader is not the FireFireFire.
Reinstall Kindle Fire Drivers from the Kindle Fire Utility package. Unzip your download and run the install drivers batch file. Then try to plug the Kindle in again.
Best way to get things working here is to run Kindle fire utility, run the "intall FireFireFire" option, it will say waiting on device, with your kindle off, attach the Factory cable to the kindle and then plug it into the PC. Hopefully this will get the bootloader installed, and while you're at it, go ahead and reinstall TWRP, as it shouldn't cause an issue. After you get the bootloader and TWRP installed, you can wipe caches and see if that helps.
Click to expand...
Click to collapse
hey thanks mthous
Ya i told her if she would have installed the FFF that alot of this would be a whole bunch easier.
As for installing the drivers ive done that and it IS being noticed by the computer as i stated with the reg. usb cable, In KFU its read as ADB Status ONLINE but bootmode status UNKNOWN. so its being recognized just i think since the Kindle is stuck in whatever bootmode that its not being read.
ONLY WHEN i plug it in with the Factory cable is it completely invisible to the computer and unrecognized IMMEDIATLEY after attached to the KF.
But im going to try that last piece of advice but i had tried something similar with going to the KFU and choosing option 1 then choosing i believe option 2 for recovery mode then hit enter and it said "waiting for device" BUT as usual it didnt even read that the device was connected with the Factory Cable. IS there a special different kind of driver for the FACTORY cable that i dont know about? MAYBE its not made right???? i bought it from a reputable ebay dealer. and it DOES alter the state of the KF by keeping it at the KF logo instead of going on through to the CM10 boopt logo.
i dont know.
ANYONE reading this with some idea please chime in cause its gotten to the point where i just turn the KF on to see it light up and watch the cm10 boot animation thinking of the day that i will one day be able to use it :crying::crying:
so im just going to try this http://forum.xda-developers.com/showthread.php?t=1430038
seems my problem is the drivers and what not so hey why not right. SUCKS i had to search so many places to even know FULLY what pokey (the op) was talking about.
such as making a bootable usb. finding the diagram on how to short out the kindle and things of that but i fully feel confident that this will fix it. also ive included my links incase anyone else is having this problem and isnt as good at searching.
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
http://www.youtube.com/watch?annota...&feature=iv&src_vid=RQLI-p-tRRQ&v=nt7ovI_CLXk
link from the vid
http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3-/
ill let you know what happens CROSS YOUR FINGERS this is the last step before i pay someone to fix it.... ANYONE in TX!!!!
What was your outcome? I'm having the same exact issue, and I'm pulling my hair out!
i have one other option you might wanna try.
using fastboot cable, get to the kindle logo and plug it in to your computer.
delete your .android folder located at c:\users\%your user%\.android
open kfu and it should say offline
run the option to install FFF that might do it.
let me know what happens
goldflame09 said:
i have one other option you might wanna try.
using fastboot cable, get to the kindle logo and plug it in to your computer.
delete your .android folder located at c:\users\%your user%\.android
open kfu and it should say offline
run the option to install FFF that might do it.
let me know what happens
Click to expand...
Click to collapse
Didn't work. Kindle installs as a USB MTP Device.
bondosho said:
Didn't work. Kindle installs as a USB MTP Device.
Click to expand...
Click to collapse
now you cant get into recovery right?
I can't get anywhere, or flash anything. It just boots up, and goes to the off center CM logo.
Sent from my SPH-L710 using xda app-developers app
Might be a stupid question to ask - but it seems like you already have firefirefire due to previous flashing and etc, have you tried pushing the power button repeatedly during the boot to change the bootmode?
This can be an easy way to get into recovery and do a complete wipe then reflash. I had an issue similar to this and it was because I forgot to do my wipes because I was focused on getting my device recognized by KFU.
sorry been lazy and i gotta search where all the links were now... but def going to do this today sometime.....oh ya links are in my post lol ok well i WILL get back to see if this "drastic way" works is it wierd that it doesnt seem that complicated to do it this way??? i feel like im missing something like it should be alot harder. idk ill find out and get back.
zane203 said:
Might be a stupid question to ask - but it seems like you already have firefirefire due to previous flashing and etc, have you tried pushing the power button repeatedly during the boot to change the bootmode?
This can be an easy way to get into recovery and do a complete wipe then reflash. I had an issue similar to this and it was because I forgot to do my wipes because I was focused on getting my device recognized by KFU.
Click to expand...
Click to collapse
I'll try that.
Sent from my SPH-L710 using xda app-developers app
And that didn't work
Here's a quick video:
https://www.youtube.com/watch?v=u5pv-vsUihA

KFU bricked my Kindle

I have read to a nausea thread after thread about fixing my bricked Kindle, unfortunately I cannot post in the development section since I am a big NOOB. I'm sure most have heard this a million times, and have read about it a million times but have I still have not a clue how to go about it.
If anyone can help it would be greatly appreciated.
So story is downloaded KFU, installed drivers via KFU, plugged in Kindle, started option 2(ROOT w/ SU), it chugged away snagged at install FFFing, so I thought okay let me unplug and re do it, but now it is stuck at KF logo white/orange which many of you say is in fastboot mode. I cannot get the computer to recognize when connected, usually you hear a audible tone when connecting via usb, but nothing. Have tried reinstalling drivers again but they show they have already been installed. People say unistall but I cannot find the device to uninstall the drivers!! I have tried the unbrick util, but KF does not show nor on KFU. Thus I think Soupkit would be the same if it cannot see that KF is connected.
Another q, is even if I get it unbricked and use KFU will it still hang at FFF again...is it just dependent on computer or something, I don't understand why it works for some and not for others(causing them to use linux instead of windows?)
Please help me
You can still reboot to normal mode. Load KFU, and press 1, and then enter, and then 1 and then enter. This should reboot the kindle EVEN if it says its offline in KFU.
If that doesnt work, turn off the kindle, and as soon as you turn it back on, press 1 enter 1 enter in KFU.
Both these methods worked for me... but my KFU still hangs every time it enters fastbootmode!
jinhypen said:
I have read to a nausea thread after thread about fixing my bricked Kindle, unfortunately I cannot post in the development section since I am a big NOOB. I'm sure most have heard this a million times, and have read about it a million times but have I still have not a clue how to go about it.
If anyone can help it would be greatly appreciated.
So story is downloaded KFU, installed drivers via KFU, plugged in Kindle, started option 2(ROOT w/ SU), it chugged away snagged at install FFFing, so I thought okay let me unplug and re do it, but now it is stuck at KF logo white/orange which many of you say is in fastboot mode. I cannot get the computer to recognize when connected, usually you hear a audible tone when connecting via usb, but nothing. Have tried reinstalling drivers again but they show they have already been installed. People say unistall but I cannot find the device to uninstall the drivers!! I have tried the unbrick util, but KF does not show nor on KFU. Thus I think Soupkit would be the same if it cannot see that KF is connected.
Another q, is even if I get it unbricked and use KFU will it still hang at FFF again...is it just dependent on computer or something, I don't understand why it works for some and not for others(causing them to use linux instead of windows?)
Please help me
Click to expand...
Click to collapse
first of all lets get this straight. KFU did not (what you call bricking) brick it. you did by taking on the challenge.
second does device manager show up with anything when you plug it in?
goldflame09 said:
first of all lets get this straight. KFU did not (what you call bricking) brick it. you did by taking on the challenge.
second does device manager show up with anything when you plug it in?
Click to expand...
Click to collapse
Thanks for the replies guys, I tried the first solution of using KFU and option 1, however it just hangs and just says waiting for device/device not found. Goldflame you are correct, I did it myself, no one forced me LOL. The device does not show up when I plug it in. If I power down(hold power down for 15secs, and then plug it in the KF logo comes back up but remains nonresponsive.) Seems the computer doesn't know its connected so the two cannot communicate. I've installed drivers so don't know what the problem is, tried different usb ports as well. I am also using a non factory micro cable, IDK if that matters or not read other people ordering factory ones to help them.
jinhypen said:
Thanks for the replies guys, I tried the first solution of using KFU and option 1, however it just hangs and just says waiting for device/device not found. Goldflame you are correct, I did it myself, no one forced me LOL. The device does not show up when I plug it in. If I power down(hold power down for 15secs, and then plug it in the KF logo comes back up but remains nonresponsive.) Seems the computer doesn't know its connected so the two cannot communicate. I've installed drivers so don't know what the problem is, tried different usb ports as well. I am also using a non factory micro cable, IDK if that matters or not read other people ordering factory ones to help them.
Click to expand...
Click to collapse
ok well this is different from my case where it showed up as an unknown device in device manager. reboot your computer without the kindl plugged in and let me know if anything different happens when you plug in your kindle
goldflame09 said:
ok well this is different from my case where it showed up as an unknown device in device manager. reboot your computer without the kindl plugged in and let me know if anything different happens when you plug in your kindle
Click to expand...
Click to collapse
Yes rebooted still reacts the same way. any other ideas? tia.
jinhypen said:
Yes rebooted still reacts the same way. any other ideas? tia.
Click to expand...
Click to collapse
I have no guarantee that it will work but try to delete your .android folder.
Its located in c:/users/your user name/.android
Then plug in your kindle, open kfu and choose option 2 even if it says device offline
Sent from my Kindle Fire running CM10.1/SGT7
goldflame09 said:
I have no guarantee that it will work but try to delete your .android folder.
Its located in c:/users/your user name/.android
Then plug in your kindle, open kfu and choose option 2 even if it says device offline
Sent from my Kindle Fire running CM10.1/SGT7
Click to expand...
Click to collapse
TY you for being so responsive goldflame, but I have already done that as well...I researched quite bit before posting this..as I didn't wanna be "that" person. Still nothing works does anyone have anymore solutions for me?

Categories

Resources