Database Users

[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

[Q] Brick fix?

Posted recently as my Nexus 7 seemed to be bricked. It seemed hopeless as it was a competition prize and i had no receipt of purchase and it seemed that the factory warranty had run out. nVidia the competition sponsor I guess bought a shed load of them and then handed them out later.
Anyhow, after seeing repeated demands that I use the original charger (which was a US charger and as such not compatible with 240V power in the UK) I finally decided to try it. I remembered that i had bought a transformer for a guitar effects pedal so I plugged that in and the charger into that and then the Nexus 7. Still no joy. However I decided to leave it connected and let it charge over night and the whole of the following day.
This evening I forlornly tried to boot the unit and HURRAH! I got the Google logo.
I waited for the animation to start for Android....
And I waited.....
And I waited a bit more....
Nothing. It seems stuck. I then powered it off by holding the power button and it turned off, only to immediately turn on and stop at the Google Logo. The only way to stop this was to get into fastboot mode (Power and volume down pressed) and cycling to power off and hitting power again to execute.
So I thought I could get somewhere.
However I cannot get it to go properly into recovery mode. I get the bootloaded screen where I can restart the bootloader (which does just that), power off (which also works correctly), Start (locks at Google Logo) or recovery mode (which also locks at the Google Logo)
I cannot get to the screen with the image of the Android with the red triangle and the exclamation mark.
The bootloaded screed says the following:
FASTBOOT MODE (red text)
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SERIAL NUMBER - 015d2d422357f20b
SIGNING - not defined yet
LOCK STATE - LOCKED
I have the SDK loaded and I cannot get the "Fastboot devices" to work. I previously sideloaded KitKat onto it so all the drivers are installed. I cannot get my PC to see that there is anything plugged in to the USB port. I think i need to get to this screen so that I can initiate a total system restore don't I?
Also the system heats up like an oven when it is locked at the Google logo.
I have repeatedly tried to get the drivers installed and have yet to get the PC to recognize the device. This is really wierd as I had used the adb to sideload KitKat onto the device.
Shortly after the sideload and a small 1.5Mb OTA update it went on the fritz. It would do absolutely nothing. After an extensive charge on the original 2A charger I can get it into Fastboot. However the fastboot sometimes freezes and I cannot get into Recovery Mode. Whenever I try to hit the power for recovery I get the Google logo and that's it. Have tried numerous presses of Vol-up and Power but no use.
It seems that there is something that the unit is trying to process and cannot get past that point. What can I do? I seem to be in driver hell. I am totally Stock. When the system was last operational USB Debugging was switched on. I don't care if I have to wipe it flat, I just want it working again.
Help please!!!!!!

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

RSD Lite Flash Failure?

So I pulled out my XT907 to test a new cable I have. The port on the phone has been damaged and it won't charge and won't be recognized by my PC. The port stopped working ages ago during a reset to stock using RSDlite. So when the device tries to boot, it goes straight to the fastboot screen and tells me there was a flash failure. This screen also tells you if you have a USB cable connected. Heres where I am confused. According to this screen, when I plug in a cable, the device registers it as being plugged in (or not plugged in), but the PC won't say anything. Since then I thought I also lost TWRP as a result of the flash failure. Today I found out I was very wrong. I got the device to boot to TWRP without issue, the red Motorola logo even appears at boot which hasn't happened since RSDlite failure. From there I went to the file manager and discovered the whole system is still there. So I am confused as to what is really happening here: 1) Either the USB port on the phone works or it doesn't, depending on what you believe (the phone or the PC) 2) If RSDlite did fail, as fastboot says, how would I even be able to boot to TWRP? 3) Given number 2, if the flash really did fail would it cause the device not to be recognized? 4) Also given number 2, the logo shouldn't even appear period. EDIT: 5) With the device powered off and I plug it into an outlet or my PC, it will power on into fastboot and also says USB connected.

So I decided to dig out the phone and play around with it. I can still get into TWRP so I managed to flash system and boot. Here's the weird part. I thought the phone wouldn't charge. I was wrong. It charges on almost every cable, but my PC will not recognize it in AP fastboot or TWRP. I had forgotten about the 3 button trick, volume up + volume down + power brought me to the recovery menu. I just let it sit there for the few seconds it stays and suddenly the red logo appeared...and the phone booted...normally. So it does charge, but adb or fastboot is a no go. Looks like if I keep this phone, I'll be flashing what I can or am able to with TWRP, on an external SD card if I can't download it to internal.
So it appears only the AP fastboot partition is damaged...every time It boots to it (if I didn't intentionally do it) it says "fastboot flash failure". So since I can't use RSD lite, what are my options?

So the only thing that was damaged was AP fastboot and anything beyond that, including 'charging mode' (thanks for that trick @sd_shadow though it didn't work). For a couple years I thought the clip inside the charging port on the phone was too badly damaged to take a charge or be recognized by my PC. So with intentions of fixing it myself, I put it in a drawer until such time. I knew there was some hope in salvaging it despite the 'flash failure' because every cable I tried, would only charge the phone so no PC means no RSD Lite. I was convinced TWRP would save me and I would find a way to flash everything I needed, but was only able to get as far as the boot.img and system.img. So last night I started to play around with the phone after having plugged it in and noticed the green light in the upper left corner turned on. I spent a few hours flashing and reading and flashing some more before I found another post by @sd_shadow referencing to three buttons, press and hold in this order: volume down, volume up and power. That got me to the stock Motorola recovery screen, which only hangs around for abut 10 seconds, so you have to be quick at selecting an option. I did not select an option, and much to my surprise the phone booted all the way and properly. And that was the only issue. I still had TWRP too. However anytime I needed to reboot, it would go straight to the AP fastboot screen. The 3 buttons bypassed that.
I looked inside the charging port on the phone as I had many times before, and noticed what looked like a piece of foil stuck inside of it. I tried to dig it out but I just managed to push it between the crack in the clip. I plugged it back into my PC and I was even more surprised when it made the familiar connect sound. So I assume that piece of foil was actually a pin, and I managed to seat it just right that the phone charges, is recognized by my PC and i was able to SUCCESSFULLY recover using RSD Lite. We're back in business

The system has been destroyed!

My brother's Mi9t turned off all of a sudden in middle of his push up training app. He couldn't turned it on. Once he load it through recovery and he chose restart option without wipe. His phone shown this error: The system has been destroyed!
His phone is locked. It doesn't turn on. It doesn't charge at all. If we leave his phone for hours when pressing power button only it's red Led turns on but phone won't charge or turn on. When it is in charge nothing works at all even red light color on top of the device.
We tried using pc to charge, or using 5V 2A charger but it doesn't help.
The worst problem is that because of Corona Virus epidemy in my country they have shuted down all Guarantee services till atleast next two week. They don't even answer the phone, just texted me to wait till end of quarantine.

Start phone in fastboot ( volume down and power).
Connect to pc and start adb on pc and type
fastboot continue
After that, phone will boot in system.
Add mi account in dev.options and apply for unlock.
Make backup, and wait for unlock time.
After you unlock bootloader, phone will boot again normaly.
Every time when you reboot phone( when you waiting for unlocking), you must start phone with adb command.
After unlocking BL, phone will start normaly every time.
If you want to use with locked BL, flash fastboot rom again.