Database Users

Bricked KF no longer working or being recognized.

Hi!
A couple of months ago i bricked my brother kindle fire, I can't remember exactly what firmware etc I had to used on it, since i'm not a KF user myself. He came to me the other day saying that his kindle was no longer working any more.
Now this time, I have no idea what is wrong with it, the rom used had like a logo with a yellow triangle and fire sign in the middle.
The problem:
The KF is no longer recognized by the computer, I can't seem to get in via adb,
tried hard reset too...
The kindle periodically once plugged in turn on with the yellow triangle and fire logo from the rom and then turn black like it's off every second or so.
Is there a fix to my problem? and how?
Thank-you greatly in advance to all your help at hand.

it's probably stuck in fastboot. there's should be a thread in the development forum about how to fix it. I think you have to reinstall the drivers for an adv device.
sorry it's brief,have to go sleep and get ready for work.
Sent from my Kindle Fire using Tapatalk

dead battery - the kf is constantly rebooting, does nothing if pluggend out - right ?
would suggest to charge it with the wall charger for some hours - best over night
if you use a replacement charger take care it is strong enough - has to have ~2A or it will not work

Kindle Fire NEVER ROOTED OR TAMPERED WITH in boot loop!

Ok so I have been reading around and most of what I found about my specific problem (boot loop with never putting any custom restore or root or ANYTHING on it) was pretty much was useless. I am not a complete beginner I have put custom mods on many of my devices, defy, atrix, dell streak, ect, and I have used ADB among other things (not that I am a pro at it mind you!)
I realize theres a thread up for this here
http://forum.xda-developers.com/showthread.php?t=1356257
but I want to know if this will work or is for people WHO HAVE NEVER DONE ANY MODIFICATIONS TO THEIR KINDLE FIRE
If it is then I will give it a shot.
What happened is (to my knowledge) my daughter was playing with it, and the next morning, it was boot looping, and quickly. So when I turn it on, it shows kindle fire then goes black, then repeats or once in a while will make it to the slide to unlock but 2-3 seconds after goes black and continues the bootloop
ANY HELP GREATLY APPRECIATED!

I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?

AustinFire said:
I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?
Click to expand...
Click to collapse
Why would I even try to fix it if I had a warrant? .... thanks anyways...
so ive downloaded the drivers and its basically not working, and the method for deleting the drivers (the one some idiot posted at least) will only work IF THE DEVICE STAY CONNECTED... Which it obviously isnt... and the 3-4 seconds of it saying KINDLE FIRE isnt long enough for me to find it in the device manager... by the time that updates its already rebooting...
so please anybody.... i dont understand why it would be so difficult.... I JUST NEED A RECOVERY I DONT NEED ANY OF MY STUFF

I have tried running ADB shell it says device not found....

If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app

Ixthusdan said:
If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I would agree with you but i had installed some apps prior that seemed to make it glitchy and slow, and my daughter probably just triggered something (she is 3 and just constantly opens and taps things, i caught her in settings before) ... im pretty positive its software, especially since I read a few people with the same exact symptoms of mine... (it shows logo then reboots repeatedly, but sometimes makes it to the slide screen for like 4 seconds then it goes back to boot loop) Im sure I could fix it but I need help with getting my ADB in order or im screwed xD

I have also read several places that my problem could be fixed with a factory cable...

Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium

Dead Battery
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244

JimCo06 said:
Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I have tried all of that, many times in fact. I also think its odd that it got stuck in a bootloop but from what ive read stock KF do that sometimes and its usually as simple as changing the way it boots which is why I think the factory cable is what I really need...

kinfauns said:
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244
Click to expand...
Click to collapse
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...

Untraumatized said:
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...
Click to expand...
Click to collapse
You don't know whether or not your fastboot drivers are working because you must first put the device into fastboot mode to see if Windows will load the appropriate drivers.
Your problem is that on a stock device unable to boot into the system, 2 out of the 4 possible ways of putting the KF into fastboot mode are unavailable to you. The remaining options are to use a factory cable or to crack the case open to get access to the motherboard.
http://forum.xda-developers.com/showthread.php?t=1668159
There's another thread on the forums here about someone who disconnected the battery and hardwired it to a charger, but that seems like a really bad idea to me. A factory cable is your best/safest first step to getting out of your situation.

[Q] Is it possible to retrieve files from N7 whilst dead/bricked?

Hi all
Apologies at coming on here and immediately asking for help, but....
I've had my Nexus 7 since July and have been very happy until NOW!
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
I've tried all the methods of long push of buttons/multiple buttons/etc but to no avail.
I can bring up the factory restore option so I know I can get it working again, but....
I have an exam in a week which foolishly had work stored for on my n7 without back up (yes fool) so....
Please is there anyway to retrieve my files via PC etc before factory resetting
All help genuinely appreciated
Mark

rooted vs unrooted (or unlocked bootloader even if not rooted) makes a huge difference in the answer.
Please state which.

Sorry about that
Not rooted.
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark

pleading said:
Sorry about that
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark
Click to expand...
Click to collapse
I believe you are SOL in that case. Sorry.

Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Sent from my Nexus 7 using xda app-developers app

bigbop said:
Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Click to expand...
Click to collapse
pleading mentions the battery, but then says "stalls" - not "shuts down", which is what you might expect if the battery was drained:
pleading said:
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
Click to expand...
Click to collapse
But, bigbop could be correct if pleading meant "low battery shutdown"
One other very long shot - assuming that that the device is hung - is to see if either adb or MTP are available. Normally that happens very late in the boot & I have to imagine that he has already tried that though.

Hi again guys
Firstly thanks for not giving up on my situation!
Bad explanation by me I guess....
The battery went flat/dead (my bad)
Plugged in to charge and screen lit up again but showing the 'powering off' script
Left over night on charge, wouldn't switch on again next morning
Left on charge all day still no joy but if I try switching on whilst plugged in I first get the Google name, then the Google X but then gets 'hung' (probably a better description than freezes etc as it still pulsates the colours)
Only way to get out of this is to keep power button pressed which switches n7 off and starts the cycle again
If during the recycle I keep the volume down pressed then it accesses the option screen to recover/reboot etc
Hope this helps, and again thanks (desperate to recover course work)
Mark

Hi again
Update...
Battery is showing full now
But still same 'hung' situation
Regarding the 'ADB'
I can get to the 'apply update from ADB' option
And if I choose it states.... 'now send the package you want to apply to the device with "adb sideload <filename>"'
As always thanks for any help or suggestions
Mark

Mark,
It sounds to me like what you are describing is ADB in the stock recovery, not a ADB when the regular operating system is running. (Is that right?)
Unfortunately, the stock recovery is only good for 2 things: applying an OTA update, and doing a factory reset. Even if your tablet needed an OTA update (and it probably doesn't if it is up to date), it probably wouldn't fix the looping/wedged phenomenon: usually that is caused by stuff in the userdata partition.
Doing the stock recovery factory reset might cure the wedged/looping problem - but only if it wipes all the data from your tablet. (Including the /sdcard area too).
The only hope I held out was if your tablet was reachable via a ADB or MTP with the wedged operating system sitting there looping. Usually those facilities start up quite late in the boot sequence, however so probably you don't have that.
Sorry. I think you are still SOL when it come to retrieving files.

Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all

pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
I had same sort of problem N7 went flat tried to charge but would not power on
Took back panel off and disconnected battery for 10 mins reconnected battery and put back on charge
it then booted up as normal

pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
Uhhh ... what?
The OP was about a tablet that you couldn't get into because
[a] it had a correctable soft-fault
you didn't want to exercise an available soft-fault recovery method because of a desire to reclaim user files not backed up
... and so far as we know the soft-fault recovery mechanism still is available to you.
How did that morph into "this is the end"?
You need to re-do your homework, perform a factory reset, and move on with your life.
You have used either software or hardware in the past haven't you? That thing isn't a toaster or a waffle-iron! No backups of important stuff? Come on!
OK, well then. Pack it up and send it to me with the charger and I'll pay for the shipping - UPS ground.

Doesn't the Nexus have a safe-boot mode?
Sent from my Nexus 7 using xda app-developers app

bigbop said:
Doesn't the Nexus have a safe-boot mode?
Click to expand...
Click to collapse
Just tried right now - held the Vol-down button down continuously from about 2 secs after the Google B&W splash screen appeared until the lock screen appeared. That worked. (Stock 4.2.2)
"Safe mode" appears in the lower left corner. I had access to all the market apps (that I tried), but did not see a toast notification from StickMount after the boot - suggesting that safe mode only inhibits apps from starting on boot.
I suppose this could work (although the OP's deadline has probably come and gone) for bypassing a hung boot - but only if the hang is due to a market app that normally starts on boot.

[Q] Phone refuses to boot - sometimes.

I've run into a problem with my S4. I'm rooted, and running Hyperdrive 15.
My phone refuses to boot quite often. Sometimes it will boot up perfectly fine and run for a day - day and a half, or it'll lockup and then refuse to boot up again, OR it will just not boot at all. My power button seems to be unresponsive, and the only way that I can get some action out of the phone is by reseating the battery in the well.
What I think it is, could be 1 of a few things, or a combination of them - i'm not sure.
Scenario 1: While playing with the Hyperdrive tweaks, my phone was hung after running the Zipalign tool for over 20 minutes and I had to pull the battery.
Scenario 2: I'm deployed on a ship currently, and I have my phone in a high-salt enviornment and I'm afraid that there might be salt corrosion inside of the power switch or the USB connection - shorting it out. I took my phone apart tonight and cleaned both items with isopropyl alcohol ( the switch itself on the main board ) but that didn't seem to produce any new results.
Scenario 3: I was recently rooting a Kindle Fire HD 7" for a friend out here, and I was dumb and didn't realize that I was pushing boot loader files that were designed for the Kindle Fire and not for my Galaxy S4. I have since tried to enter recovery, but with little avail. Download mode is also out.
A description of what my phone does when I reseat the battery: My phone will vibrate, the Galaxy S4 logo will show for 1.5 to 2 seconds ( same for download mode ) and if I hold the appropriate button, ' Recovery Booting.... ' will display as well. At that point, my phone will shutoff and the power button will become unresponsive.
If anyone can give me a bit of guidance on how to proceed to repairing my phone, I'd be super grateful.

Scenario 3: I was recently rooting a Kindle Fire HD 7" for a friend out here, and I was dumb and didn't realize that I was pushing boot loader files that were designed for the Kindle Fire and not for my Galaxy S4. I have since tried to enter recovery, but with little avail. Download mode is also out.
This sounds like the most plausible reason.
You will need something like JTAG to really fix it.

Lennyz1988, thanks for the quick reply. Internet out here is slow at best, and sometimes unusable.
As far as your JTAG option, I believe that would work, except that I dont have access to that kind of hardware right now. Sending my phone out at this point entails a month of transit time on each side of the turnaround time required for someone to re-flash my phone, and I wholly believe that I can do this.
As an update to my phone, it will not charge the battery anymore. I'll use someone elses phone to charge my battery soon. If anyone can give me a direction to go as far as how to completely reflash my phone IF it turns on, i'd be grateful beyond belief. I dont want to believe that if I can get it to start up again, that it is a total brick and completely useless - if it turns on again, i need someway to push new boot loader files to it. Really hoping someone can help.
Thanks again in advance.

Fire HD8 7th gen (Douglas) boot loop

i was asked to fix this tablet after i gave it as a gift to someone years ago. it looks like they were using a non-standard charger for a while. the complaint was that the battery wouldn't charge. when i tried charging it, it went into a boot loop. i figured the battery was dead so I purchased a new one on ebay and installed it but it did not fix the issue.
the loop is basically the white amazon logo staying on for about 15 seconds then rebooting. i can not enter recovery mode. i can also not get my mac, pc, linux computer to recognize the kindle. i tried using adb to detect it with no luck. i even tried the non-shorting debrick procedure with no luck.
at this point i kind of just want to solve the mystery. i'm also in for $15 for the new battery so it would be nice to have a working tablet for a while. my guess is that it's in this loop because it thinks the battery is bad and that it can't charge it safely. if that were the case, can i reset that? is there anyway to watch the pre-load procedure via a usb port? is there anything i can do to manually reset it if I open the case? does anyone have any ideas? ty in advance.

eudaxia said:
i was asked to fix this tablet after i gave it as a gift to someone years ago. it looks like they were using a non-standard charger for a while. the complaint was that the battery wouldn't charge. when i tried charging it, it went into a boot loop. i figured the battery was dead so I purchased a new one on ebay and installed it but it did not fix the issue.
the loop is basically the white amazon logo staying on for about 15 seconds then rebooting. i can not enter recovery mode. i can also not get my mac, pc, linux computer to recognize the kindle. i tried using adb to detect it with no luck. i even tried the non-shorting debrick procedure with no luck.
at this point i kind of just want to solve the mystery. i'm also in for $15 for the new battery so it would be nice to have a working tablet for a while. my guess is that it's in this loop because it thinks the battery is bad and that it can't charge it safely. if that were the case, can i reset that? is there anyway to watch the pre-load procedure via a usb port? is there anything i can do to manually reset it if I open the case? does anyone have any ideas? ty in advance.
Click to expand...
Click to collapse
I think that motherboard is bad and your Fire tablet caused a boot loop.