Related
I rooted my Kindle Fire about a month ago with KFU. Everything was fine until I turned it on one day and I got stuck at the Triangle screen. None of the reboot tricks work. The interesting thing which I think is what is stopping me from being able to successfully use other methods is that when I plug my Kindle Fire into my computer via usb, it connects, and then disconnects (the USB) about 2 seconds later. I've tried different ports, etc. Any help on this issue would be greatly appreciated. I've read over multiple things, but don't see a mention to the kindle being disconnected via usb so quickly, thus stopping me from being able to do anything.
Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?
soupmagnet said:
Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?
Click to expand...
Click to collapse
I've tried the rebooting the Kindle while trying to reset the kindle to booting "normally" within the KFU. I've tried holding down the power button on a reset, then pushing it again until it is orange, none seem to work. I'm confident I could get it to work again if the kindle did not disconnect from my computer so quickly. By this I mean I hear the "usb chime" when I plug it in, then within seconds the disconnect chime plays. During the brief few seconds it is connected, it shows up on my devices list, but obviously when the usb disconnect chime plays, it disappears off of the device list.
edit: I'm using windows 7 Ultimate.
Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.
ErikV55 said:
Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.
Click to expand...
Click to collapse
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.
kinfauns said:
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.
Click to expand...
Click to collapse
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.
ErikV55 said:
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.
Click to expand...
Click to collapse
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.
kinfauns said:
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.
Click to expand...
Click to collapse
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.
ErikV55 said:
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.
Click to expand...
Click to collapse
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?
kinfauns said:
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?
Click to expand...
Click to collapse
I've tried to reset the bootmode via the KFU method recommended in the guide posted here (normal, 4000 and trying to reset when it says waiting for device) The device pops up in the device manager as an "unknown device" which may be a problem with the version of the drivers im DLing. I'm using KFU version 0.9.6
When I first DLed them it seemed as if the drivers were installing correctly, when I plugged in the Kindle is said drivers were being installed but it failed because the device disconnected after the 2 seconds.
Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.
hunterhk said:
Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.
Click to expand...
Click to collapse
Thanks for your response, I will go through these and report back when I get back home from class.
ok, now I have my kindle being recognized by my computer as "android phone" with the sub of "android adb interface." If I have read the guide correctly that means it is in fastboot mode. However when I open kfu it says the kindle is offline.
If someone would be willing to help me out through Skype I would gladly appreciate it. I'm really at a lose as to what to do at this point.
and no stupidly I do not have FFF or TWRP loaded, since I first rooted it when I was a super noob. The usb driver seems like it should be able to work according the the Kindle fire beginners guide, but KFU does not recognize the kindle even though my computer does.
So, I tried searching for days on how to fix my problem.
A little while ago I rooted my Kindle Fire, and it was great. Then I did something. Not sure exactly what. But It ended up just doing nothing. When I boot up the Kindle it shows the blue and white Kindle Fire logo. Nothing else past that (unless I go to recovery.) Now, my computer doesnt recognize it anymore, even after doing most of the driver updates that people on here have said to do.
I need help, basically, getting it back to normal, so I can give rooting a try again. Now that I know what exactly I am dealing with, I can do this and not screw everything up.
First, the computer says the driver is installed, yet it doesnt recognize it.
Second, (before the driver mishap) KFU said it was connected but the adb was unknown.
Third, I have CWM and I tried to flash the normal Amazon update to bring it back, and it says"it cant open it (bad)".
Now, I would really like some help with this. I'm just at a complete lost.
Now should I put that into command prompt in the adb part? because it just says fastboot is not recognized.
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Now its just not connecting to the computer. I installed Android sdk and everything and its just not working. It says the driver is installed but there was an error because a problem had occurred. Any help? :crying:
As soon as you get tired messing with drivers you can move on to something that works http://forum.xda-developers.com/showthread.php?t=1850038
ManofFishFry said:
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Click to expand...
Click to collapse
I hope u r on windows PC..
first after u set up adb, make sure u install adb drivers that came with kindle fire utility with ur kindle fire unplugged..if u had plugged in kindle fire while doing that, go to device manager and uninstall that device and its driver software and start up from beginning..
keep kf unplugged and install driver..u dont get usb debugging option in stock kf rom..its enabled if u have installed the drivers properly..ur kindle fire appears as android phone in device manager if everything u hav done is correct..
then boot up ur kf..that blue and white kf logo is of firefirefire bootloader..i hope its v1.4a and u see it on right top of the screen..if its stuck there then open command prompt as administrator on ur pc..connect ur kf to pc..type in to cmd
Code:
fastboot devices
if u see something under list of devices attached that will be ur kindle fire(unless some other android device is connected in fastboot mode lol)
Because kindle fire, as far as i know, can only boot into 3 bootmodes(normal, recovery, fastboot) unless u have altered the partition table to install different roms and multiboot ur kindle fire..
if fastboot command is not recognized, try setting the path to where fastboot.exe is present in KFU folder
alternatively u can go to folder where fastboot.exe is located and right click while holding shift and selecting 'open command window here' and fastboot needs to firefirefire bootloader to be installed on ur kindle fire..
also u can try this..
JUST GO TO RECOVERY..twrp has always been a better recovery software than cwm based thing available for kindle fire at least for me..if u go to recovery, ur kf will definitely show up as an adb device..u can change the bootmode using this..just type in:
Code:
adb devices
if ur kf is seen as in recovery then type this in cmd
Code:
idme bootmode 4000
reboot
just report if this worked..
okay well, I deleted all the drivers and started from the beginning. Yet, after running the install_driver.bat I plugged my Kindle in and it still says device not recognized. Now, you how can get adb working? It is coming up as unknown device. Its just seeming like theres something wrong on the kindle part. But hey, what do I know. haha
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
But doesn't that require linux? I have windows 7. Is there something like that for windows?
Thepooch said:
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
This is what I get when I try to install the driver....
To run soupkit all you need is at least a 2 gig usb flash drive ubuntu 12.04 32 bit and universal usb creator. By the way your problem with the driver is you (or how you`re going about it), You would trip if I got on your computer and got it to work or could at least tell you why its not working. that`s why I suggested soupkit if you would of actually read the information I gave you, I wouldn`t have had to tell you twice and you would know that to use it it`s not required to be installed on your computer. But hey catch me online I can either help you fight through windows crappy drivers or help you set up soupkit I`m always game for a challenge When updating the driver you need to point it to the 32 bit version of the driver for instance on my computer it`s located here C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers. After it`s ran unplug and replug device if that doesn`t work power off and power on while connected this generally does the trick when windows finally catches on it will install android adb interface, this is the fastboot driver (if you`re stuck in fastboot). Then select option 1 in KFU for changing bootmodes, then option 1 for normal if it does nothing power off and power on while connected it should then detect the kindle and reset the bootmode to normal. Pm me later I will be online all evening and most every evening I will help you sort it out.
Josepho1997 said:
Whoops! Somehow my post was posted twice. I didn't even get to see your reply. Sorry!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
this is what I get when I try this... (btw im working with firefirefire. its got the blue and white kindle fire.)
Why don't you let me take a look?
Dark__king said:
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
Click to expand...
Click to collapse
Yes soupkit can fix mounting problems.
This is a very interesting issue with this Kindle windows detects it as unknown usb device, drivers are installed properly from what I can see. Ubuntu with soupkit ran on it fails to detect it in recovery or fastboot. multiple cables tried, lsusb doesn`t show the device connected. I really think this one the computer is the problem, because it`s the only unchanged variable.
Firekit may be the only option if Linux won't detect the device. Before doing that, make sure a USB 3.0 port isn't being used and try a fresh install of Linux to be safe. Otherwise, it seems putting it in USBboot is the only option for getting Linux to detect.
I'm not exactly sure what causes the unknown device error, but it almost always means there is something wrong with the bootloader, and it seems as though Windows might be the main culprit. Not sure why exactly, but it may be similar to the problem soulweeper51 had. Possibly a hardware issue involving the computer's USB port or the motherboard itself.
@ManoFishFry has doomlords cwm recovery and he flashed JB at first I thought it was an issue with cwm not being detected but the fact that it`s not detected in fastboot raised my eyebrows. The bootloader appears to be functional but I cannot rule out any minor state of being broken in another fashion when lsusb returns null. The computer doing the work had never been used prior to the incident so driver install didn`t take place till after the fact. The usb ports are all either 1.0 or 2.0 no 3.0 ports are being used. An alternate computer would be nice to rule out the computer itself @ManoFishFry only has a dinosour of an xp machine as alternate use of is not possible yet, not that it would even be possible to install drivers because of the typical unsigned driver failure of xp and booting ubuntu isn`t happening at the moment on this machine.
I'm willing to bet it is the bootloader.
Just USBboot and get it over with.
We did try usb boot once but it didn`t work will keep trying.
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
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
Please help me!
I rooted my girlfriend's Kindle a few days ago in order to install the Google Play store. Managed that just fine and installed a few apps. I then decided it would be a good idea to change the launcher and get shot of the carousel. I tried the next Launcher 3D and followed an online guide to install it. On rebooting the Kindle I got a constant pop up advising Next Launcher 3D had stopped working. It popped up continually every 1/2 second or so and I couldn't get rid of it,
Again I had a look online and found a guide to removing it using command prompt script via ADB. I went through the instructions correctly but it kept telling me the app didn't exist. Using the dir command showed the app though. Confused I tried again a couple of times. I then got a pop up on the device telling me another app.....something relating to Swype had stopped working. The Kindle rebooted itself and presented a screen with a red triangle and 'Kindle Fire System Recovery' giving me the options to either reboot or reset to factory defaults. I tried both of these options (perhaps foolishly) and had no success.
I was given some further advice from a very helpful poster on here to get KFFAide v100 and enter some fastboot commands. On entering the command 'fastboot -i 0x1949 getvar product', the script shows 'waiting for device'. Powering on the device at that point does nothing more than booting to the same screen with the red triangle. Windows does not acknowledge that the device is connected at all.
It would seem I was hasty in rooting the device. Having rooted several other Android devices I was clearly overconfident in my ability and now find myself at a loss. Is there any way at all for me to recover the device at this point? Or should I now file this under 'very expensive experience and education'?
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi Stunts513. Thank you for your reply. Have tried what you said above and Windows (8) just doesn't detect that the device has been connected. No pop up from system tray, nothing in file explorer and nothing, not even for a second in device manager.
Am at a loss for the moment. Will have to get hold of an Ubuntu CD and try that way. Am just praying it detects the Kindle. Didn't on my girlfriends laptop nor my PC so am mildly panicked just now.
OK, so I went through Linux Mint and installed the SoupKit and tried it that way. Same result. The device just isn't detected at all. Really starting to fear the worst here. The fact it's still powering on should give me some faith but i've tried all I can think of and everything advised and cannot proceed past this point.
Does anyone have any last gasp possibilities for me? Borderline desperate here now.... will try anything at this point.
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Did exactly that. Brought up the virtual terminal. Nothing.
Have tried everything now I think. Used different PCs. Different cables. Different OS. Tried bypassing getvar and just trying a manual command "fastboot -i 0x1949 flash recovery recovery.img". Nothing is getting any response from this device other than booting to the recovery screen.
Suspect I may be out of luck.
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah it is most definitely an 8.9 model. Am not sure what I have done to it but it is not being detected by any OS whatsoever. Have bitten the bullet and bought the Mrs a replacement. Expensive error on my part.
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Many apologies for the delay. i managed to get the Kindle up and running following your advice coupled with that on another thread. Although it wouldn't detect in either Windows 8 or Ubuntu, it did so on Windows XP. Don't imagine you can begin to explain that one any better than I can as it's entirely illogical......but there you go. From there it detected as a JEM device and I was able to run KFFA and do a complete restore.
I now have it the way I intended to have it in the first place. Changing the launcher was fruitless as I couldn't get the wallpaper fix to work but am fine with that. had a look at customising the icons on the carousel but boy does that look like more trouble than it's worth!! Lol.
I wont pretend I was going to send my Kindle off to you guys. In truth I would have sold it to recoup some of my losses and raise funds towards the replacement. I will however be making a donation to the team very shortly as a token of my appreciation.
Thank you very much for all your help. it is greatly appreciated.