Database Users

[Resolved] Brinked Kindle Fire unable to Connect to PC

So I'm stuck on the FireFireFire logo (Fire Hazard Symbol) before I get to recovery. The KF will not go past this slash screen into normal boot, nor will it go into recovery when press the power button (light stays Amber and does nothing).
To make matters worse, when I plug it into my computer, the KF shows up then goes away within 10 seconds. It will pop up again in device manager and disappear again within 10 seconds. After that, I will not show as trying to connect and I have to turn the KF and retry.
I cannot use KF Utility because my KF will not stay active on my computer long enough to do it. I have yet to try it on another computer, but I don't think I have too many options left.
Oh, XDA-Developers, you're my only hope.
[Issue Resolved]
I reinstall the recovery by quickly using the KF Utility 9.1. It seems to have reinstalled and working well again. If anyone has similar issues as I had, try reinstalling recovery. Thanks!

Malhou said:
So I'm stuck on the FireFireFire logo (Fire Hazard Symbol) before I get to recovery. The KF will not go past this slash screen into normal boot, nor will it go into recovery when press the power button (light stays Amber and does nothing).
To make matters worse, when I plug it into my computer, the KF shows up then goes away within 10 seconds. It will pop up again in device manager and disappear again within 10 seconds. After that, I will not show as trying to connect and I have to turn the KF and retry.
I cannot use KF Utility because my KF will not stay active on my computer long enough to do it. I have yet to try it on another computer, but I don't think I have too many options left.
Oh, XDA-Developers, you're my only hope.
[Issue Resolved]
I reinstall the recovery by quickly using the KF Utility 9.1. It seems to have reinstalled and working well again. If anyone has similar issues as I had, try reinstalling recovery. Thanks!
Click to expand...
Click to collapse
Hi,
I got a problem very similar to yours. I tried to root my KF (obvioulsy I didn´t know what I was doing) and now I get the KF looping on load screen. It does not not get recognized by the computer and, if not connected to the usb or ac charger it won´t do anything (tried to press for 30 sec and nothing). When it´s connected it will only flashes the KF logo.
I also tried to connect to a different computer. The KF appears for few seconds on device manager and then vanishes again. Do not know what to do. I tried to download the KFU you mentions but that didn´t worked (unless I used the wrong option)
Do you have any suggestion? Thanks

andersonrel said:
Hi,
I got a problem very similar to yours. I tried to root my KF (obvioulsy I didn´t know what I was doing) and now I get the KF looping on load screen. It does not not get recognized by the computer and, if not connected to the usb or ac charger it won´t do anything (tried to press for 30 sec and nothing). When it´s connected it will only flashes the KF logo.
I also tried to connect to a different computer. The KF appears for few seconds on device manager and then vanishes again. Do not know what to do. I tried to download the KFU you mentions but that didn´t worked (unless I used the wrong option)
Do you have any suggestion? Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1623244

Kindle Fire TWRP Yellow Triangle bootloop

I rooted my kindle fire with the Kindle Fire Utility. Installed TWRP, and installed the rom - MIUI.us_blaze_4.0.3-2.2.3-alpha_0xD34D. After doing this, I reboot and I am stuck at the Yellow Triangle. If I push the power button to get into TWRP the power button turns orange and is still stuck at the yellow triangle . if I power off and on again , do nothing Windows detects the kindle for a few second and then it disappears and then is detected again and then disappears, so I cannot access the device through ADB ,
Any ideas or do I now have a paper weight instead of a kindle fire

Kindle fire Utility should work even without being recognized (well it did for me after turning on and off 3 times).
Does the device at least get's the firefirefire logo? If so, this is what I did
-Turn your kindle off by holding the power button down for at most 20 seconds.
-Plug kindle into your computer
-Run the unbrick utility
-Turn kindle on
-Wait for the Caution Sign with the fire logo (firefirefire logo)
-Choose first option on utility (Recovery Loop)
-Wait... (a max of 10 minutes)
This should work, if not, try to turn off your kindle on and off, and then try again.
==========================================
This is what worked for me (I've been tossing this around awhile now, and it even worked for two of my friends).
The link to the unbrick utility is: Here

Mine got stuck on the triangle as well and I thought I was screwed, but appears you are just stuck in fastboot.
What I did was use the KFU (vashypoo has made an awesome utility) and even though it didn't show as recognized when I opened the KFU, I was able to use Option 1 - Bootmode Menu, Then Option 1 - Normal.
My Fire restarted normally after that.
Give it a shot.
Check out this post: http://forum.xda-developers.com/showthread.php?t=1520826
Zane had to cycle a couple of times to get it to take.

Are there alternative download links for this utility....I keep downloading it from the site that this site provides and I keep getting viruses or incomplete downloading. I have been trying to unbrick my kindle for weeks and this seems like my last route...

Try this Linux solution. It was the only thing that worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038

Solution for This: I had the exact same problem
http://forum.xda-developers.com/show...02&postcount=4
I had the exact same problem and b63 posted this as a reply. My Kindle was stuck on yellow triangle and was not recognized by ADB. When I tried to boot into twrp the power button turned orange but stayed on the yellow triangle. The thread above is what I used, worked perfectly.
Good Luck!

Kindle Fire Bricked and Windows doesn't recognize it.
First off, thanks for all the development and help in getting the Unbricking utility and the KFU for all of us noobs. I have been searching threads for hours before I decided to post, and I can't find the answer. I rooted with KFU and have TWRP installed. I ran MIUI several months until I decided to try MIUI 4.0 after I flashed 4.0 it rebooted to the yellow triangle and the power turned orange. I ran the unbricking utility and now the light is green, but it won't go any further. When I first plug in the kindle windows recognizes it for a second and then it disappears from the device manager completely. I have updated the driver several times, tried the KFU to get it to boot (4000) and nothing works. if I turn off the kindle and turn it back on KFU and windows will recognize it for a second and reboot it, but then it gets stuck on yellow triangle and never goes anywhere. Then I don't see it in the device manager anymore, not even 'unknown device'.
I did forget and leave the Kindle plugged into the computer while it was flashing MIUI 4.0, I don't know if that would have killed it. I never got a chance to see 4.0 it's been bricked ever since.
Any help or ideas would be greatly appreciated. I'm sorry if this specific situation has been covered anywhere in the forums and I missed it.
Thanks

this should help you:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4

[Q] KF won't start, charge, or connect to PC

[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!

KF won't start, charge, or connect to PC
Absurd1 said:
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
Click to expand...
Click to collapse
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex

JohninLex said:
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
Click to expand...
Click to collapse
Well, like I said, I don't know much about any of this stuff, but here's what I can tell you:
I don't have FIREFIREFIRE. Not really sure what that is, but it's certainly never been on my Kindle.
What I did try doing was following those steps in Kindle Fire Utility anyway. I can get it to the point where it says:
ADB Status: Online
ADB Rooted: No
Boot Status Unknown
If from there I hit 5 (to "install latets TWRP recovery"), I get a whole bunch of
"The system cannot find the path specified." for each step it goes through, until finally it gets here:
"If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait..."
To reiterate again -- I don't know what any of this ADB stuff is, where to find it, etc.

We are in the same boat. Was messing around w/ someone's Bare Bones CM7, and as per instructions, clicked wipe SYSTEM, and since then my device has been with screen "on" but black; non response to power button weather plugged on AC adapter or USB. Will have to research the forums tomorrow (cant find search function now) and let you know if I find a fix and please do the same if you find something first.
Sincerely,
-RM
---------- Post added at 08:49 AM ---------- Previous post was at 08:37 AM ----------
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.

theartofbone said:
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
Click to expand...
Click to collapse
Nope, that's not doing anything for me. My kindle won't power on. All it does is display "Kindle Fire" for one second, then go dead.
Does anyone have ANY advice?

oundsde good
Try a different charger and plug into the wall for a little while.

_Justin said:
Try a different charger and plug into the wall for a little while.
Click to expand...
Click to collapse
Tried that. No luck.

Do you have a chat program, or google talk? I'll help you out.

_Justin said:
Do you have a chat program, or google talk? I'll help you out.
Click to expand...
Click to collapse
..........

My device has the same issue, it powers down as soon as I connect it to a PC or charger. The interesting thing, that it is charging, but the led is dark. When I take it off the charger the next day, it boots up and fully charged. (when I connect a cable again it shuts down immediately)
If you find out something I would be also interester. (I've also rooted before 6.2, than I've lost root, than after I while I've faced these issues)

Alright, unless any folks have any other advice, I'm gonna go ahead and contact Amazon for a return.

try to charge it with the wall charger for some hours - check the charger - should have ~1.8A - maybe the orange light is showing up after half an hour
try to power it off by holding pwr ~20sec to allow better charging - if you can't let it on the charger - try to power it off later (eg after an hour)
look here about charger spec and contact problems:
http://forum.xda-developers.com/showthread.php?p=23035482#post23035482
some had success with a factory cable:
http://forum.xda-developers.com/showthread.php?p=23034046#post23034046

Phone boots to blue screen

My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!

The same thing just happened to me! Someone please help us! IS there a solution to this?

dsljk2009 said:
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
Click to expand...
Click to collapse
colbyrainey said:
The same thing just happened to me! Someone please help us! IS there a solution to this?
Click to expand...
Click to collapse
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!

colbyrainey said:
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
Click to expand...
Click to collapse
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.

jocyrus said:
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
Click to expand...
Click to collapse
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.

audit13 said:
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
Click to expand...
Click to collapse
It didn't work. Any other suggestions? :|

jocyrus said:
It didn't work. Any other suggestions? :|
Click to expand...
Click to collapse
Don't know of any other methods because holding down the power button got the phone to turn off and allow me to get into download mode. From download mode, I was able to restore a stock 5.01 ROM to my phone via LG Mobile Support Tools.

LG G2 Bluescreen then no boot after disconnecting battery
Found my LG G2 with a completely blue screen. It would not turn off. Took it apart and disconnected the battery. Reconnected the battery and there was only a blank black screen and the phone would not boot. Zilch. Even with pressing the power button with the volume down to boot into recovery.....still zilch.
I sucessfully got my phone to work again using a hair dryer trick on an LG G3, which I found here.
1. I took the back off the phone, disconnected the battery, and removed the SIM card.
2. I then used a hairdryer on high heat and blew the heat over the uncovered areas for 10 minutes.
3. I let the phone from hot to warm, reconnected the battery and put it all back together with the SIM card replaced.
4. I booted into recovery and restored a TWRP backup, and my LG G2 is working like a champ again.

Nexus 7 dead until i connect it to a pc/laptop PLEASE HELP!

So my girlfriend was using her Google Nexus 7 2012 of 32gb only Wi-Fi triying to play the EA game "The Simpsons: Springfield" while the tablet was charging and when the game loaded it was running slowly till it frozen and then she tried to see all apps open with the 3rd button, she could pull down and see the notification drawer, then she push the 3rd button (that one on the right) but the tablet didn´t respond, instead it will just pull back the notification drawer, then the tablet started to show a notification in the middle of the screen that said "the system process is not responding" (We don´t have screenshots from this notification, that´s what she remember's and I am translating into English from the Spanish she saw) with 2 options, "wait" and "close", she pressed "close" and then it showed another notification saying "the user interface is not responding" (We don´t have screenshots from this notification, that´s what she remember's and I am translating into English from the Spanish she saw) with 2 options, "wait" and "close", she pressed "close" and I am pretty d#%n sure that it was in that moment when it got f$#%&d. Then she left it alone for like 10 minuts but it didn´t do anything, so she attempted to restart it by pressing "power + volume down" buttons together for 10 seconds and when she let the buttons go, that´s when she realized it was gone all wrong, what she saw was this "Android Robot with his belly opened with a lot of words on the down - left of the screen which ended up with look state - unlocked, it also had two arrows on the right-top of the screen, one pointing up and one pointing down, there was also on the top of the screen a red arrow with black background and inside that red arrow had written RECOVERY MODE" then she used the arrows on the right to move what was written on the red arrow, there was at least 3 options, she remember´s the first which was "RECOVERY MODE" and the second that was "POWER OFF" she is also pretty sure that it was a 3rd option but so far she doesn't remember. So she chosen power off with the power button and the tablet powered off automatically and she waited to see the tablet charging but it never appeared, later on, she tried to turn it on, it won't happen.
So now the tablet is totally dead and the only sign of life i have seen is that sound when i plug in the tablet into my pc or her laptop and press the power button, that sound that minds that a device has been mounted and the same sound when i unplug it from the pc or laptop. I have no idea of what should I do with her, my best hope is that I found a genius here patient enough to help me out with this peace of technology. :crying:

Connect to Nexus Root Kit and try to flash stock ROM. There is option for non bootable devices
Sent from my Nexus 4 using Tapatalk

Which Nexus Root Kit?
I only found here the Wugs Nexus Root Toolkit, I already installed the Wugs Nexus Root Toolkit v2.1.6 but I couldn't find the proper way to use it for a non bootable device.
Am I using the correct Nexus Root Kit?
If yes, please tell me: where can i find a step by step guide to solve the problem?
If nope, where can i find the correct Nexus Root Kit with a step by step guide?
Thank's so much in advance for your help, I already tried with the Wugs Nexus Root Toolkit v2.1.6 to flash stock ROM but as the tablet is dead, I couldn't boot it to bootloader, obviously I couldn't either turn the tablet on to allow usb debugging, for all matters, the toolkit need's adb connection to work, and I couldn't find the way to start an adb connection.

Make sure the tablet is not stuck in APX mode. To get out of this: connect the tablet for some time (at least for about 1 hour) to the charger then press for about >=20 sec the power button *only*. Release the button. If the tables was stuck in APX mode, now it should have exited that mode. Now you should be able to boot to bootloader / recovery / system. If this does not work, I suppose your tablet is bricked ...

Its correct NRT. First step is to download correct drivers and make sure it passes full driver test and adb and fastboot work. If that's the case then everything can be flashed (bootloader, recovery and ROM). Here is link to a manual process that shows steps but NRT does it automatically. Look at flashall script
http://www.laptopmag.com/articles/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Also try connecting to charger, keep it charging for 30 min or so and then try power button
Sent from my Nexus 4 using Tapatalk

Thank's!
Thank's to much for your glorious help!
I tried connecting to a charger about an hour and half and then power button, nothing happened, in approximately 24 housr from now I will follow the step by step guide to unbrick the tablet, thank's for the link, I hope it work's, I let you know later on.

If your device is really bricked, there is no change for reviving it, sorry.

Try installing just adb/fastboot (adb-setup-1.4.3.exe) from https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k After installing open cmd window as admin, go to c:\adb and see if "fastboot devices" returns anything. If yes, then download recovery TWRP image (twrp-3.0.2-0-grouper.img) to same folder and type "fastboot boot twrp-3.0.2-0-grouper.img". If recovery comes up then you have options to flash some ROM. To permanently install recovery "fastboot flash recovery twrp-3.0.2-0-grouper.img" Boot loader can be flashed in the same cmd window, If it worked then reboot into bootloader with fastboot.

Why is everyone giving him advice on unbricking when he can't even power on the tablet.
Yeah, you can use ADB to fix a tablet that won't power on so the computer can even load a driver for it. LOL
<sarcasm>
Look, the Nexus 7 has random charging issues especially when it gets drained down to zero battery.
I deal with it on mine sometimes.
Not saying this is your problem, but since you can't even power the device on, it's the first thing I'd look at.
Gotta pop the back cover and reseat the battery connector.
Then try charging again for a couple hours.
Ugh, I've got to do it to mine right now too.
For the third time since I've owned it.
---------- Post added at 12:12 PM ---------- Previous post was at 11:56 AM ----------
Yep, reseating the battery cable fixed it once again for me.
https://www.youtube.com/watch?v=x8u8xSnfCOA