[Q] Kindle fiire rooting fail - Kindle Fire Q&A, Help & Troubleshooting

SO recently i tried to root my kindle using one of the guides unfortunately i somehow messed up during it or something, but the problem i have now is whenever i turn my kindle on it has the yellow triangle with a fire logo in it and at the bottom it says "press power button for recovery". Simple enough only the second problem is i do not have TWRP or anything like that so pressing the power button literally does nothing. Unfortunately as well when i plug it into the USB it will identify that something is connected but it won't install it to the pc because it cant find some hardware or something. So i cant get it to start up or connect it to the pc and am desperately looking for a solution. Thanks to anyone who can help.

First off. Do you have a first gen kindle fire?
6.3.x or 10.x.x?
If you have a first gen,
Download this.
http://forum.xda-developers.com/showthread.php?t=2192818
Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer.
Does KFU find the device? If so, good. You will be taken to the main screen at that point I think.
Choose to install recovery (TWRP).
That should be it. Post here if there's any problems.
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

jma9454 said:
First off. Do you have a first gen kindle fire?
6.3.x or 10.x.x?
If you have a first gen,
Download this.
http://forum.xda-developers.com/showthread.php?t=2192818
Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer.
Does KFU find the device? If so, good. You will be taken to the main screen at that point I think.
Choose to install recovery (TWRP).
That should be it. Post here if there's any problems.
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.
Click to expand...
Click to collapse
Attached is a picture of what my kindle screen looks like. I tried resetting it, plugging it into the computer, etc. but this screen never changes. Also on my pc it doesn't recognize it as a kindle, it recognizes it as an unknown device. So I can't put any files onto my kindle at the moment because my PC keeps telling my me driver is not working or something. I attached files showing what my pc says as well. Also I apologize for the bad quality of the pictures i don't own a very nice camera at all so I apologize in advanced for that. The last 3 are readable the 1st one is basically just a yellow triangle with a fire symbol in the middle and it says "press power button for recovery" but nothing happens when i press the power button, and the 2 photo is a little bit blurry but all it says is:
Unknown Device
Device Type: Universal Serial Bus controllers
Manufacturers: (Standard USB Host Controller)
Location: Port_#0009.Hub_#0002
Device Status:
Windows has stopped this device because it has reported problems. (Code 43)

The "press power button for recovery" can be confusing if you don't know what's going on. That version of FireFireFire sits in fastboot mode for...I think...8 seconds before it will recognize the power button. You can repeatedly press the power button until the LED turns orange to see if that gets you into recovery. If not, you're probably looking at something like usbboot to replace your bootloader. You need to replace your bootloader anyway, but hopefully you'll be able to flash a new one in recovery instead.

soupmagnet said:
The "press power button for recovery" can be confusing if you don't know what's going on. That version of FireFireFire sits in fastboot mode for...I think...8 seconds before it will recognize the power button. You can repeatedly press the power button until the LED turns orange to see if that gets you into recovery. If not, you're probably looking at something like usbboot to replace your bootloader. You need to replace your bootloader anyway, but hopefully you'll be able to flash a new one in recovery instead.
Click to expand...
Click to collapse
Repeatedly pressed the power button for about 30 seconds with the same result, green light still, and no screen change. So it looks like its this usbboot, how would i go about doing this in order to replace my bootloader?

KindleFail said:
Repeatedly pressed the power button for about 30 seconds with the same result, green light still, and no screen change. So it looks like its this usbboot, how would i go about doing this in order to replace my bootloader?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1405052
http://forum.xda-developers.com/showthread.php?t=1430038&highlight=firekit
Since you will need Linux anyway, you might as well download and install SoupKit. It comes with Firekit and will probably make your life easier in the long run.

What guide did you use exactly? I can see if we can update that guide to use the latest FFF because that is a very old alpha version that has had many issues with the yellow triangle in the past. I'm surprised its still floating around here.
Sent from my One V using xda app-developers app

Stuck at boot logo
Hey all,
I'm not sure if this is the correct place to post but I didn't want to make a new topic and this seems to be in the area of what is wrong with my kindle... I tried the new KFU v0.9.9 on my first gen KF running 6.3.2. I have rooted it before (not on 6.3.2), but unrooted and restored to factory settings because I thought I was going to sell it. However, the plans fell through and I am keeping it so I wanted to re-root and all that jazz....
My question is, how do I get it boot past the boot logo? I used the KFU, but firstly when it prompts it says:
'findstr' is not recognized as an internal or external command, operable program or batch file.
So none of the commands pop up, however they are still there... For example, i followed:
"Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer."
And I can get to fastboot, but it says there is no device connected to my computer. If you need more details on the problem I'll be glad to give them to you. Hopefully someone checks this thread again
Thanks

What version of Windows do you have that doesn't have 'findstr'?
What do you see in your device manager while the device is plugged in?

soupmagnet said:
What version of Windows do you have that doesn't have 'findstr'?
What do you see in your device manager while the device is plugged in?
Click to expand...
Click to collapse
I'm running a 64 bit version of Windows 7 professional.
There's nothing in the device manager when I plug it in.

Related

Omap4430 usb device ???

Hi,
I just switched off my kindle using the power button then shutdown in Ice Cream Sandwich. My kindle now won't turn on and when plugging it in to the pc shows up as OMAP4430 and constantly connects and disconnects?
Please Help
If you hold down the power button for ~30 seconds to force it off, then press it again, do you get anything on the screen?
If not, then your partitioning or bootloaders got hosed. There might be something you can do with the USB debricker (w/o having to open it up). What were you doing before you rebooted?
Hi,
I am currently in the IRC trying to sort it out. (I have been told it is in bootloader mode and I need to install linux and try to connect to the serial console...).
I have tried hardresetting it and I dont get anything on the screen. Before I rebooted I copied some music and apps to the sdcard in Ice Cream Sandwich, then rebooted to go into recovery (However, after switching it off It didnt even start up again so I couldnt go into recovery).
Connecting it to PC shows up as an OMAP4430 USB Device, with no drivers which is constantly connecting and disconnecting from the pc.
You mentioned a USB debricker? Would this work in my situation? If I cant get it fixed with help from the guys in IRC.
Regards,
XperiaPlayer
You are in the cpu's USB boot mode. You need to send the cpu something to boot over usb or it will loop forever trying to find something to boot off flash.
Search the dev forum for "rekindle". I'd post a link if I could. Using those directions you should be able to boot TWRP over usb and get in over adb to figure out what happened. Because you're already in usb boot mode, you don't even have to open your Kindle. You will need Linux tho.
Sent from my GT-P7510 using xda premium
Thank you Its working now
heeeelp
pokey9000 said:
You are in the cpu's USB boot mode. You need to send the cpu something to boot over usb or it will loop forever trying to find something to boot off flash.
Search the dev forum for "rekindle". I'd post a link if I could. Using those directions you should be able to boot TWRP over usb and get in over adb to figure out what happened. Because you're already in usb boot mode, you don't even have to open your Kindle. You will need Linux tho.
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
hi i have the same problem as him. but do not know how they do it, really need help with this, please help me what to do.
Okay start by creating a live usb. When your device comes up as omapp44xx just run the script usb_fix_parts_and_install_fff_twrp and plug your device in while off when it says <waiting for omap44xx device> in the terminal. The script should run when your device boots up because it`s in this state. I don`t believe you will even need the short trick. Get a 4 gig usb flash drive.
Instructions:
1. Download this http://www.pendrivelinux.com universal USB installer
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of drop down in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
Use this iso I made Soupkit is already ran just use the above instructions http://db.tt/CR4OaQTF Firekit is an option of Soupkit. The usb might be a little slow to boot this is normal let me know how it goes. Good luck.
omap4430 please help
any other ideas? this is not working ... please help me guys
Whats not working? When you run the script and plug your powered off kindle in what does it do? Any other ideas this is not working isn`t terribly informative.
thank you for your answer. BUT
I did everything what you wrote in there. and everything was going, I downloaded, I have ubuntu in a flash. but I do not see that your last sentence. Sorry I do not get it, sorry. this
I do not see how I do it When you run the script and plug your powered off kindle
Side note this is not for use for anything but the Kindle Fire!! I feel really bad Bono now has a really hard bricked lg optimus 3d cube I think both of us learned a hard lesson wish I knew I was dealing with a phone.
Thepooch said:
Side note this is not for use for anything but the Kindle Fire!! I feel really bad Bono now has a really hard bricked lg optimus 3d cube I think both of us learned a hard lesson wish I knew I was dealing with a phone.
Click to expand...
Click to collapse
lol why would he post about his phone on a kindle page?:silly:
It's actually quite common for people to assume that a fix for an error can be universal, that often isn't the case unfortunately.
My tablet does not go to recovery mode
Hi I have a Samsung Galaxy tab 2 7 inches, I am having the same problem as the op, but I did not try to flash/root anything. I just arrived from a travel, and it look like when my tablet was on my bag the things near it pressed some weird combination of buttons, and now it does not turn on, nor my laptop recognize it. I just get a notification of omap4430 could not be installed.
So I understand that I need to turn-off my tablet before trying to enter the restore menu (power + volume up). But I dont know when my tablet is turned off, because I can not see a thing on the screen at all. I am trying to press the power button for 30 secs, and then I am trying to press the combination of button, but nothing happens. What I need to do? Do I keep trying doing the same??
thanks in advance.
Heavenly_King said:
Hi I have a Samsung Galaxy tab 2 7 inches, I am having the same problem as the op, but I did not try to flash/root anything. I just arrived from a travel, and it look like when my tablet was on my bag the things near it pressed some weird combination of buttons, and now it does not turn on, nor my laptop recognize it. I just get a notification of omap4430 could not be installed.
So I understand that I need to turn-off my tablet before trying to enter the restore menu (power + volume up). But I dont know when my tablet is turned off, because I can not see a thing on the screen at all. I am trying to press the power button for 30 secs, and then I am trying to press the combination of button, but nothing happens. What I need to do? Do I keep trying doing the same??
thanks in advance.
Click to expand...
Click to collapse
Your question would be best answered in the Samsung Galaxy Tab forums.
Confused
Thepooch said:
Okay start by creating a live usb. When your device comes up as omapp44xx just run the script usb_fix_parts_and_install_fff_twrp and plug your device in while off when it says <waiting for omap44xx device> in the terminal. The script should run when your device boots up because it`s in this state. I don`t believe you will even need the short trick. Get a 4 gig usb flash drive.
Instructions:
1. Download this universal USB installer
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of drop down in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
Use this iso I made Soupkit is already ran just use the above instructions Firekit is an option of Soupkit. The usb might be a little slow to boot this is normal let me know how it goes. Good luck.
Click to expand...
Click to collapse
Since there are no lights indicating whether the kindle is off or on how do I know when i connect the device and run the script with what i think is off ( not making the disconnect and connect sound in windows) the script runs but it stays at
"waiting for OMAP44xx device..."
when i connect it in what i believe is powered on it runs the scripts and this comes back
"waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
Fixing partitions...
< waiting for device >
"
and just sits there for a while. I get no response from the kindle and I have not opened to short it yet trying everything possible to not open it
What am I doing wrong. Thanks in advance
opporlando23 said:
Since there are no lights indicating whether the kindle is off or on how do I know when i connect the device and run the script with what i think is off ( not making the disconnect and connect sound in windows) the script runs but it stays at
"waiting for OMAP44xx device..."
when i connect it in what i believe is powered on it runs the scripts and this comes back
"waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
Fixing partitions...
< waiting for device >
"
and just sits there for a while. I get no response from the kindle and I have not opened to short it yet trying everything possible to not open it
What am I doing wrong. Thanks in advance
Click to expand...
Click to collapse
Is the battery dead? Could be most all power on issues are fixed by using the short trick. Considering the near unresponsive state you will need to open the back provided the device back light is not coming on. The fact that you are not getting LED indication does pose an indication that the battery could be completely dead. In which case the short trick will likely pull you through the final stages of the script. Always try charging via usb on your computer to see if you can manage to push some current to the battery and perform 2 min long press then press again for normal power on to verify it not something more near a SOD.
Good luck
THANKS
Thepooch said:
Is the battery dead? Could be most all power on issues are fixed by using the short trick. Considering the near unresponsive state you will need to open the back provided the device back light is not coming on. The fact that you are not getting LED indication does pose an indication that the battery could be completely dead. In which case the short trick will likely pull you through the final stages of the script. Always try charging via usb on your computer to see if you can manage to push some current to the battery and perform 2 min long press then press again for normal power on to verify it not something more near a SOD.
Good luck
Click to expand...
Click to collapse
Thank you for the quick reply! I had left the tablet charging all night via usb to the computer so im not sure if that helps in terms of the device having powered. The device back light is not coming on and I get not LED indication. Okay I tried the 2 min long press and again for normal power still no response from the tablet I uploaded a video to youtube tittled xda456 to show exactly what is happening or if you would be willing I can show you my screen via join.me/654-762-978 The post you showed about shorting the pin the name on the chips are different. MY kindle was a 2nd gen kindle running 10.4.6
Should I just proceed to opening the kindle and shorting the pins then?
opporlando23 said:
Thank you for the quick reply! I had left the tablet charging all night via usb to the computer so im not sure if that helps in terms of the device having powered. The device back light is not coming on and I get not LED indication. Okay I tried the 2 min long press and again for normal power still no response from the tablet I uploaded a video to youtube tittled xda456 to show exactly what is happening or if you would be willing I can show you my screen via join.me/654-762-978 The post you showed about shorting the pin the name on the chips are different. MY kindle was a 2nd gen kindle running 10.4.6
Should I just proceed to opening the kindle and shorting the pins then?
Click to expand...
Click to collapse
Oh noes!!! firekit is only for the fist gen. devices under no circumstances should it ever be used for a second gen device like the one you have that is likely permanently bricked.
Sigh RIP kindle.
Sent from my SGH-M919 using xda app-developers app

[Q] Is the yellow triangle a stock screen?

Is the yellow triangle ('press power for recovery options') a stock KF screen, or is the something that's been added by the KFU? Amazon said they would send a replacement, but I'm wondering if I'll have issues if they see it's been rooted...
Update 6.3.1 has left me on this screen, and as of yet I have not been able to get around it. The computer will only recognize it for about 5 seconds when it is plugged in, but then the LED on the KF goes Orange and it disconnects.
I'm looking at getting the factory cable.
Unfortunantly when I ran the KFU I did not install any other recovery options other than rooting the device. (Crossing over from the jailbreaking on the iPhones, you could get the device is recovery without any big deal and I assumed it was the same with the KF...oops)
Turn your Kindle off.
Turn your Kindle on.
As soon as you see the yellow triangle, hold the power button until it turns orange. This will boot your device into recovery.
While in recovery, look for an option to mount your sdcard.
When it is mounted, it will show up on your computer as an external drive.
From your computer, transfer the "Flash.zip" from this link: http://forum.xda-developers.com/showthread.php?p=25598837 ...to your sdcard.
Then use recovery to flash "Flash.zip" and reboot.
When it reboots, hold the power button until it turns orange again and use the selections at the bottom to change your bootmode. To scroll through the selections hold the power button for a second and release. When you have the right option selected, leave it alone for a few moments and it will select automatically. You may need to reboot.
Avidmtbiker said:
Is the yellow triangle ('press power for recovery options') a stock KF screen, or is the something that's been added by the KFU?
Click to expand...
Click to collapse
This is not the stock boot loader screen, it is an older version of FireFireFire.
soupmagnet said:
Turn your Kindle off.
Turn your Kindle on.
As soon as you see the yellow triangle, hold the power button until it turns orange. This will boot your device into recovery.
Click to expand...
Click to collapse
I've done this...
But there's no response from the KF, the screen doesn't change. The LED does go Orange, but it would anyway - even without pressing the button.
The computer is unable to recognize it at this point.
As of now it seems only to turn on whenever the USB cable is plugged in, I'm guessing the battery is dead.
Any more suggestions? I'm leary of sending it back in with modded software, I imagine they're smart enough to check that...
Ah, so you don't even have recovery installed. I guess I should have seen that in the OP...I'm such a noob <hangs head in shame>
OK the first thing you need to do is educate yourself a little bit about the Kindle Fire, the different bootmodes, and the difference between adb and fastboot:
http://forum.xda-developers.com/showthread.php?p=23747567
Then you need make sure your drivers are in good working order:
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
When you have a good foundation to work from, we'll get recovery installed and continue to fix any other problems you need help with.

KF stuck at Kindle Fire white/blue logo; tried a few ways including Linux

Hi All.
I’ve rooted my Kindle device successfully before (during v6.2 – have the driver installed from this and cable worked successfully )
Now with the 6.3.1, I used the KFU v0.9.6 to do it – option 2 ‘Install Permanent Root with Superuser’
Followed the instructions as per http://forum.xda-developers.com/showthread.php?t=1399889
- On my XP machine, it detected my Kindle initially but it stopped and my Kindle Fire was showing the stock welcome screen but kept on rebooting.
- Then I tried on a Win 7 machine and ran option 2 again – it did something and now my Kindle is stuck on the FFF screen (Kindle Fire logo in blue and white – v1.4a).
- Now when I run ‘ran.bat’, pc it shows ‘waiting for device’
- The FFF screen was blinking initially but now it’s permanently on.
- I can off my Kindle by pressing the on button for about 20 seconds and when I connect my Kindle in the off state to the pc, it turns on and remain on the FFF screen
1. Installing the driver
So I figured the above is due to the driver.
- However, the Kindle is not appearing in the Device Manager with a yellow ! – hence can’t manually install the drivers.
- Tried install_drivers.bat – it says ‘Google, Inc. (WinUSB)…..Install failed (Unsigned)’
​- I ensured that the ‘Driver Signing Options’ is set to ‘Ignore – Install the software and don’t ask for my approval’ and ‘Make this action the system default’.
- So next, I tried to force my XP to install the drivers (Kindle unplugged), by using ‘Add Hardware’ and installing drivers from c:\kfu\drivers –
​- Installed all 3 drivers – Android ADB Interface, Android Bootloader Interface & Android Composite ADB Interface.
​- Received this message at the end – ‘The software for this device is now installed, but may not work correctly. The device cannot start. (Code 10)’
​- But when I plugged in my Kindle and run KFU it still says ‘waiting for device’.
I tried the above steps with:-
- 3 XP machines and 1 Win 7, and
- on different USB ports (tried both USB 2.0 and 3.0)
- and tried using 4 different usb cables
- Same results ‘waiting for device’
- One exception though – for the Win 7 machine – when I ‘install_drivers.bat’, it says ‘Google, Inc. (WinUSB) ….Ready to use’ – but still shows ‘waiting for device’, when running KFU.
2. Delete old drivers
Followed this (http://forum.xda-developers.com/showthread.php?t=1459116) to uninstall the drivers (including the Microsoft support page).
- But XP and Win 7 still did not detect the Kindle in ‘Device Manager’
- Tried to force install the 3 drivers again and still ‘waiting for device’
Additionally tried to download the Google Usb driver from Android SDK - same issue - no yellow !
And tried to connect via 'c:\KindleAdb\adb devices' (learned from the previous root exercise) - no devices appears.
3. Kindle Fire Unbrick Utility
Tried this next - http://forum.xda-developers.com/showthread.php?t=1428428
Tried the many options available. When it is executed, its says ‘error’, despite saying Kindle unbricked at the end.
4. Firekit LiveUSB repair kit 1.1
Finally decided to use the Linux method (http://forum.xda-developers.com/showthread.php?t=1430038)
- Created a USB Ubuntu and ran the program but suprisingly still the same problem – stuck at ‘waiting for device’ (see snapshot attached).
So I’m a bit confused right now. From the above it seems to me that the Kindle is not talking to the PC.
- But if in Linux, it doesn’t work (which from what I read doesn’t require a driver?) then it could possibly be my cable.
- But the cable did work when I rooted in 6.2 and it also worked initially when I used KFU. And also, I tried with 4 different cables.
​- Am not sure if the cables are ‘factory cable’ – but it did work initially.
I’m stuck here. Any help/advice would be deeply appreciated. Thank you.
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Thank you kinfauns for your immediately reply.
kinfauns said:
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
Click to expand...
Click to collapse
Unfortunately this doesn't happen on my KF. The power button is bright green. And the bootlogo is persistent and remain bright on the display.
I've tried repeatedly pressing and releasing the power button but didn't work.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
Just bought a USB factory fastboot mode cable online .
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I tried this method but nothing changes - when I turn it back on, it goes back to the bootlogo. KFU still says <waiting for device>.
Also tried 'Temporary fastboot mode' - 'fastboot getvar product' - still <waiting for device>.
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Click to expand...
Click to collapse
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
ivanovicch said:
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
Click to expand...
Click to collapse
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Thepooch said:
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
I pressed power button for more than a minute - tried 2 ways:-
- with the KF on - it switches off and remains switched off.
- with the KF off - it switches on for a bit and then switches off and remains switched off.
I'll just give the factory cable a try when it arrives - will update here again. Hopefully I don't have to open up the case.
Thanks kinfauns and Thepooch.
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Click to expand...
Click to collapse
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Please help me My Kindle is stuck at black screen after Kindle Fire logo. I have Android Composite ADB Interface driver installed, but when I plugged my Kindle Fire to my PC, it detected as a USB Mass Storage, and won't connect as an Android device so I couldn't do anything with adb commands or KFU...
See it in my topic for more information: http://forum.xda-developers.com/showthread.php?p=30542544#post30542544
ivanovicch said:
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Click to expand...
Click to collapse
Dear All. My KF is ALIVE! Had to open my back case and do the short point trick - http://forum.xda-developers.com/showthread.php?t=1405052.
Worked like a charm.
Thanks pokey9000, kinfauns and mainly the Thepooch - thank you for guiding me through this.
your welcome I`m quite pleased its fixed myself
same issue not unable to solve
i have exact same issue but i am having a problem to fix it. i wonder if anyone can help me here. i am trying to short the test point but in device manager its shoing usb not recognized again and again. please guide me whats wrong i am doing. using windows 7 (64bit)
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
hasanalikhattak said:
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1254 using XDA Labs

[Q] Need help with rooted(?) possibly bricked kindle fire

Back story: I purchased a used Kindle Fire on Ebay about a week ago, not knowing that it had been rooted. I was looking for a standard Kindle fire for my son so he would stop using my tablet (lol) and the parental controls are better and more books and so on... none the less when I got it I noticed that it booted differently (I had a kindle fire prior) and it booted into Android. I have had problems with trying to be able to get my computer to recognize it. It looks for missing drivers and I have been all frustrated, but figured that we would just have to download off of it, well, we went on a trip this past weekend (11 hours) and my son wanted to watch a movie, turned it on and it wont boot past the yellow triangle now. I have tried a hard reboot, I have tried to turn it on and hold it and watch for the orange light to no avail. The light is either green or its powered off.
I don know what to do at this point? I cant hook it to my computer (wont even recognize as an F drive or mass media) and I cant boot past the orange triangle. Yes, I am a newb (apologies) but a very frustrated one if that counts?
Sadly I think the thing is bricked and I will take a $150 hit (ugh)
No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)
Yes, you would be correct in that I just want it stock, sure Android is great but my son is 4 and he just needs the basics for his books and angry birds lol. So, I attempted what you said, powered off all of the way and turned back on, as soon as I see the yellow triangle I hold the button and it wont turn orange, it will just power back off. I used to be able to touch the screen when the yellow triangle came up and it would take me into some menu (TWRP?) but it wont do that anymore either, its just remains either off or on the yellow triangle.
soupmagnet said:
No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)
Click to expand...
Click to collapse
Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.
I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
soupmagnet said:
Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.
Click to expand...
Click to collapse
Save yourself the trouble mail it to me I will fix it then you reimburse me the return postage or better yet I can show you how to fix it without even mailing it . 150 for a first gen kindle is pretty high you kinda already got taken.
[email protected] said:
I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
Click to expand...
Click to collapse
Pay attention to what I said previously...
soupmagnet said:
Extract the KFU and run the install_drivers.bat
Click to expand...
Click to collapse
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.
I think I am officially over this thing... I downloaded the drivers and went to plug in the kindle fire to the computer and now its just looping the triangle... it turns on for a second and then off and on and off and so on... UGHHHHHH....
soupmagnet said:
Pay attention to what I said previously...
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.
Click to expand...
Click to collapse
You let the battery die. I won't go into how it happened but to get it to charge, you need to...
With the device turned off, Plug the device into USB and hold the power button until it shuts off again. If you can get it to stay off, leave it plugged in for about half a day and turn it on again.

[Q] Fire Stuck on Boot Screen

I have a first generation kindle fire, and was attempting to root the device using the kindle fire utility. So far, I had installed FFF and TWRP, but the tutorial I was following was outdated and by the time I realized this I had installed both utilities multiple times. It was on about the third attempt that the device froze.
The device is currently stuck on the boot screen with the "fire" in blue. In the top right corner, it says "v1.4a". At the bottom of the screen, it says "Press power button for boot menu". Unfortunately, the power button doesn't do anything; It doesn't shut the kindle down, doesn't enter the boot menu, nothing. When I have the kindle plugged into my windows 7 (64 bit) pc, a notification pops up saying "USB device not recognised". Sure enough, in the device manager window it shows up as "unknown device".
I've been searching for hours trying to find the solution but nothing matches the same problem. Any help would be greatly appreciated.
Crowbar Offensive said:
I have a first generation kindle fire, and was attempting to root the device using the kindle fire utility. So far, I had installed FFF and TWRP, but the tutorial I was following was outdated and by the time I realized this I had installed both utilities multiple times. It was on about the third attempt that the device froze.
The device is currently stuck on the boot screen with the "fire" in blue. In the top right corner, it says "v1.4a". At the bottom of the screen, it says "Press power button for boot menu". Unfortunately, the power button doesn't do anything; It doesn't shut the kindle down, doesn't enter the boot menu, nothing. When I have the kindle plugged into my windows 7 (64 bit) pc, a notification pops up saying "USB device not recognised". Sure enough, in the device manager window it shows up as "unknown device".
I've been searching for hours trying to find the solution but nothing matches the same problem. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Very informative...kudos to you.
Make sure the device is completely powered down (hold power button until it shuts off) and power it up again. When you see the Kindle Fire logo, press and hold the power button, or tap it repeatedly, and hopefully the boot menu will appear at the bottom.
Let's see if that works and we'll go from there.
Bob
soupmagnet said:
Very informative...kudos to you.
Make sure the device is completely powered down (hold power button until it shuts off) and power it up again. When you see the Kindle Fire logo, press and hold the power button, or tap it repeatedly, and hopefully the boot menu will appear at the bottom.
Let's see if that works and we'll go from there.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------
I have exactly the same problem, with the same screen details. I tried your suggestion several times, with no response.
An old borrowed Windows 7 box got me nowhere - TWRP kept complaining that it couldn't connect, although I'd loaded adb. I quit when it started loading endless Explorer windows full of crapware and became unresponsive. I'm totally lost with Windows, anyway, so I just hit the wall switch to end to pain.
I'm running debian sid and I'm much happier with linux, after using it exclusively for well over ten years, although I'm an experienced user rather than an expert.
I've pried the back off my Kindle, but I'm afraid to touch the inside, except as a last resort. I downloaded SoupKit, but can't decompress it.
What's the best thing to try next?
Paleoflatus said:
----------------------------------------------------------------------------------------------------------
I have exactly the same problem, with the same screen details. I tried your suggestion several times, with no response.
An old borrowed Windows 7 box got me nowhere - TWRP kept complaining that it couldn't connect, although I'd loaded adb. I quit when it started loading endless Explorer windows full of crapware and became unresponsive. I'm totally lost with Windows, anyway, so I just hit the wall switch to end to pain.
I'm running debian sid and I'm much happier with linux, after using it exclusively for well over ten years, although I'm an experienced user rather than an expert.
I've pried the back off my Kindle, but I'm afraid to touch the inside, except as a last resort. I downloaded SoupKit, but can't decompress it.
What's the best thing to try next?
Click to expand...
Click to collapse
Are you unable to bring up the boot menu upon startup?
Bob
soupmagnet said:
Are you unable to bring up the boot menu upon startup?
Click to expand...
Click to collapse
First, thanks for the help you're generously offering.
No. The start button quickly raises the centred "kindle(white) fire(blue)", with "v1.4a" at the top right and "Press power button for boot menu" at the bottom. Neither my Debian sid box (file manager, or lsusb), nor a borrowed win7 box (file manager) recognises it. Repeated presses, or a few seconds of the power button at boot have no effect, but a very long press shuts it down.
I managed to detach the back without damage, but I'm reluctant to do the shorting trick at boot, if there's a better way. If all is lost, it's no further problem, as it was never much use, anyway, due to Amazon's geoblocking here in Australia. If I can't get cyanogenmod or equivalent on it, I'll just chuck it.
I'd prefer to fix it with my Linux box, if possible, as I've used nothing but Linux and Android for well over ten years.

Categories

Resources