Database Users

kindle fire refuses to boot.

I installed cyanogen and TWRP on my fire a couple days ago. It was working fine but today i was playing a game boy emulator and it shut off on me. the battery was completely dead at the time (i was playing plugged into a wall, and it had been totally dead for about half an hour) so i figured i just bumped the cable or something, the problem is it won't charge. when i plug it in to a wall, PC, what have you. it boots to the fire logo and asks me to press power to enter recovery (as it should) but then it just turns off and shows the same screen. i left it alone for an hour and it was still doing this. when i try to power on without being plugged in absolutely nothing happens. I've tried my usb cord and two different chargers, all of which work with my phone perfectly.
i think this is a hardware issue(please tell me otherwise) which would suck because I'm pretty sure everything i did voided my warranty. any suggestions or am i just boned?

well i contacted customer support and they didn't seem to care at all about the root, they told me it was a battery issue and are sending me a new one. good news for anyone wondering if rooting voided warranties, it doesn't.

That's great to hear that Amazon isn't going to be a **** about it. It is one thing if someone screws it up because they rooted but a hardware issue is a hardware issue and it is a good sign that they are not looking to screw you merely because you happened to have rooted coincidentally to having gotten a dud unit.

this same thing happened to me it seems. I was playing a game and my KF died. so I charged it for awhile but now its in the same type of weird loop, just like yours. Even after successfully issuing commands to change the bootmode etc, which I can only do like 1% of the time since it keeps rebooting. Hope its not a hardware issue though

it is a hardware issue, at least thats what amazon said. i fixed mine yesterday though, plug it in wait for the loop BS to start and hold the power button until it stops completely, then wait about 20 seconds release and press the power button again. I've had to do this twice today too, so definitely get a new one sent out, but it works for now.

I wonder how friendly Amazon will be after replacing a few thousand of these because people are screwing them up???
Seriously haven't seen this many "help I bricked my device" threads ever in a forum.
Sent from my Rezound using Tapatalk

I hope you can change you KF they said thay you bought one change one if there any trouble with your KF

nrfitchett4 said:
I wonder how friendly Amazon will be after replacing a few thousand of these because people are screwing them up???
Seriously haven't seen this many "help I bricked my device" threads ever in a forum.
Sent from my Rezound using Tapatalk
Click to expand...
Click to collapse
There are a lot of "I bricked my device" threads but the vast majority are having driver issues or stuck in the wrong boot mode. Almost everyone I have seen posting with a problem gets it sorted out and has their Kindle Fire working again.
The OP here appears to have a genuine hardware problem, according to Amazon, and didn't "screw anything up".

[GUIDE] The 5 second bootloop! aka: Don't let your battery die!

Symptoms: The Kindle Fire starts booting normally, but then shuts off prematurely or reboots spontaneously before the device completes the startup process. In extreme cases, the bootlogo may not even appear on the display and only the power switch LED lights up before the device shuts off again.
Cause: The battery has been depleted to the point that not enough power gets delivered to the CPU. The CPU detects the low power condition and its safety features power off the device.
Solution: Use the stock 1.8 amp AC charger to recharge the battery. In most cases, this seems to be enough to get power to the CPU and battery that it will begin to charge again.
In some rare instances, not even the AC charger will be enough to charge the battery. Why? The Kindle Fire's hardware does not have the ability to charge its battery offline. The device needs to be up and running so the ramdisk can handle the battery charging operation and that requires the CPU to be powered up. If the battery cannot provide enough power to the CPU, it shuts off automatically and the boot process stops or restarts... a classic catch-22.
Devices without FireFireFire 1.4 (or later) will need to upgrade to that version. This bootloader stops the boot process for a low battery condition (less than 3%) and charges the battery to its specified minimum before continuing to boot.
If the device has an earlier version of FFF, use the temporary fastboot mode feature to fastboot flash the new version using fastboot. If the device is using the stock bootloader (white/orange "kindle fire" bootlogo), a factory cable is probably necessary to put the device into fastboot mode.
Although the preferred method of installing this bootloader is through TWRP, it is dangerous in this situation because TWRP could shut down without warning. Because of this potential for a premature TWRP shutdown and a bad flash as a result, fastboot must be used under these circumstances. The device can be powered entirely from the USB port while running the bootloader, so it's much safer in this regard. Be sure to check the MD5 sum of the distribution, extract the contents of the zip archive and find the binary inside the cache directory. Flash this file using fastboot.
Using an older version of FFF...
Code:
fastboot flash bootloader /path/to/u-boot.bin
fastboot reboot
With the stock bootloader...
Code:
fastboot -i 0x1949 flash bootloader /path/to/u-boot.bin
fastboot -i 0x1949 reboot
Note: In both cases above, the "/path/to/u-boot.bin" must be replaced with the actual path to the file's location.
After a reboot, the bootloader will automatically stop the boot process and begin charging. The backlight is normally off in battery charging mode to conserve power, but press and hold the power button for a few seconds and a battery charging notification will appear on the display.
Note: Currently, neither FFF 1.4 nor 1.4a will display a bootlogo before entering battery charging mode, so the device may appear to be bricked. Press and hold the power button for a few seconds to display the battery charging notice. In addition, these versions will only enter battery charging mode when hooked up to USB power and not the AC wall charger. The developer is aware of both situations and has indicated that he intends to implement fixes for these issues.
Credits
pokey9000 - For providing information about the Kindle Fire hardware
SBlood86 - For sharing his experiences and initial ideas for a fix
Hashcode - For fixing/implementing battery charging on the bootloader​

+1
Sent from my Amazon Kindle Fire using xda premium

My kindle fire is running Firefirefire 1.4a and when it boots normal mode it loads the Kindle Fire screen then restarts it's self. Trying to boot it in any other mode never boots it. The thing is charged but i cannot get it booting at all.

What if I do not have the stock charger?
I charge it using my PC?
Please help, I am lost without my kindle.

Kindle Fire Restarts on its own
A long while back, I rooted the kindle fire using the kindle fire utility .95. It worked fine for months. Then today, the device suddenly restarted and went into the "press power button to for recovery" page with the yellow triangle.
I can get it to go into the system for about 10 seconds but then it just restarts. To get in, I use the kindle fire utility and put it into normal boot mode. It goes in fine but then it restarts. I do have access to fastboot and i can get in. Battery power is near full so that wasn't the problem.
Anyways, after trying everything I found in the internet, i found the best solution was to use this thread:
[GUIDE] Kindle Fire For Beginners
Assuming you're already in fastboot mode, go down to post number 3 and start at step number 6. I got the u-boot.bin from this page Amazon Update
(you have to extract it). The twrp file I got from the kindle fire utility page.
The last step I did was step number 7 which was to reboot. Once I rebooted, it went into twrp recovery but said it couldn't access the memory or something of the sort. Then it did some sort of update and sort of took a long time to update. Then it restarted, paused for around 30+ seconds on the flashing kindle fire logo,and now its perfect.
Tip: To get into fastboot mode, the exact steps I took were:
1. Shut down Kindle completely.
2. From the kindle fire utility, select 1 and then select 1 again. It should come as waiting for device. After that plug in the kindle and let it do its things. Once the kindle fire logo pops up, keep on spamming 2 in the kindle fire utility to select fastboot mode till it lets you get in. You have to do it before it starts to shut down again.
After that, the fastboot things should be working and you can do the rest of the stuff starting from number 6.
I hope this helps some one.

JoshuaLintag said:
What if I do not have the stock charger?
I charge it using my PC?
Please help, I am lost without my kindle.
Click to expand...
Click to collapse
You need something with a higher charging output than a pc. The stock of charger puts out 1.8 amps, so you need a charger that is close to that. I know that some aftermarket iPad chargers are 2.1 amps so that may work if you can get one of those.
Sent from my Kindle Fire using xda premium

I am new to the Kindle Fire, as in I don't have one yet. But, this seems like kind of a big deal or does it only happen on rooted, customized Kindle Fires in which case Amazon probably doesn't care quite so much?
If this happens on a fully stock Fire when it goes dead I would imaging a ton of these being returned if something like this happened to gramps or someone less tech savvy...which I have a feeling is a huge number of Kindle Fire owners.

Evo_Shift said:
I am new to the Kindle Fire, as in I don't have one yet. But, this seems like kind of a big deal or does it only happen on rooted, customized Kindle Fires in which case Amazon probably doesn't care quite so much?
If this happens on a fully stock Fire when it goes dead I would imaging a ton of these being returned if something like this happened to gramps or someone less tech savvy...which I have a feeling is a huge number of Kindle Fire owners.
Click to expand...
Click to collapse
A new Kindle Fire purchased from Amazon comes with a stock wall charger. It does not come with a USB cable.

Evo_Shift said:
I am new to the Kindle Fire, as in I don't have one yet. But, this seems like kind of a big deal or does it only happen on rooted, customized Kindle Fires in which case Amazon probably doesn't care quite so much?
If this happens on a fully stock Fire when it goes dead I would imaging a ton of these being returned if something like this happened to gramps or someone less tech savvy...which I have a feeling is a huge number of Kindle Fire owners.
Click to expand...
Click to collapse
I think a more appropriate answer to your question can be found in the OP...
A couple of users have reported flashing back to the stock boot image to get out of this situation. The idea is that some ramdisks on custom ROMs may not be as efficient as stock when it comes to the battery charging software.
Click to expand...
Click to collapse

My Kindle starts up and turns off 2 seconds from turning it on.
ADB won't detect it also the KFU. help

JoshuaLintag said:
My Kindle starts up and turns off 2 seconds from turning it on.
ADB won't detect it also the KFU. help
Click to expand...
Click to collapse
This is a joke right? You're just toying with me, right? I mean, if you were serious then you wouldn't be very bright considering the answer to your problem is in the OP.
Oh, and also in this thread, WHERE I ALREADY TOLD YOU THE ANSWER!

soupmagnet said:
This is a joke right? You're just toying with me, right? I mean, if you were serious then you wouldn't be very bright considering the answer to your problem is in the OP.
Oh, and also in this thread, WHERE I ALREADY TOLD YOU THE ANSWER!
Click to expand...
Click to collapse
Maybe it's because you talked about your military background, but I get flashes of Full Metal Jacket during some of your "motivational teaching" posts...
You little scumbag!
I got your name!
I got your ass!
You will not laugh!
You will not cry!
You will learn by the numbers!
I will teach you!​
Anybody else?

kinfauns said:
Maybe it's because you talked about your military background, but I get flashes of Full Metal Jacket during some of your "motivational teaching" posts...
You little scumbag!
I got your name!
I got your ass!
You will not laugh!
You will not cry!
You will learn by the numbers!
I will teach you!​
Anybody else?
Click to expand...
Click to collapse
"Tough love" is better than no love at all.
Sent from my DROID BIONIC using Tapatalk

JoshuaLintag said:
My Kindle starts up and turns off 2 seconds from turning it on.
ADB won't detect it also the KFU. help
Click to expand...
Click to collapse
There will be times when I tell myself "Maybe you're being too hard on people".
Then I see stuff like this and snap out of it.

fzdolfan said:
"Tough love" is better than no love at all.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I'll go with that. Maybe he didn't appreciate my tongue in cheek effort at humor... or I'm dating myself by quoting a 25 year old movie.

kinfauns said:
I'll go with that. Maybe he didn't appreciate my tongue in cheek effort at humor... or I'm dating myself by quoting a 25 year old movie.
Click to expand...
Click to collapse
That's a great movie BTW. Although, my love/hate relation with it is due to my drill sergeants watching it before every cycle to get themselves "motivated"
Ah, good times

Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Here is a video of what happens
http://www.youtube.com/watch?v=5zYtNZkpy7Y

luishawk said:
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25400963
That link will take you to a thread that will explain what your problem is and how to fix it.

luishawk said:
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Here is a video of what happens
http://www.youtube.com/watch?v=5zYtNZkpy7Y
Click to expand...
Click to collapse
Well, I think we've reached a new low today. You post a question...
http://forum.xda-developers.com/showthread.php?t=1648813
... and I answer it by providing a link to a thread that not only tells you what the problem is, but also suggests possible fixes. Instead of actually trying the fix... one of which is as simple as plugging in your charger! You copy/paste the same post into a thread that already gives you the answer in the OP!
I don't like going negative in my posts, but stuff like this really makes me wonder why I take the time...

After 5s bootloop, now my kindle fire total battery die, can't use stock 1.8 amp AC charger or usb - pc, usb - iphone charger. It not show 5s bootloop now .
Any solution ?
I wish to read this topic earlier

[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] Nexus 10 stuck at bootloader screen, will not do anything else

I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.

razrus said:
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
Click to expand...
Click to collapse
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk

charesa39 said:
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.

razrus said:
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
Click to expand...
Click to collapse
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?

charesa39 said:
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
Click to expand...
Click to collapse
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.

razrus said:
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
Click to expand...
Click to collapse
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?

charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.

charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.

So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.

razrus said:
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
Click to expand...
Click to collapse
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.

charesa39 said:
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
Click to expand...
Click to collapse
Is it possible to flash even though it's not recognized by windows?

razrus said:
Is it possible to flash even though it's not recognized by windows?
Click to expand...
Click to collapse
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.

charesa39 said:
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
Click to expand...
Click to collapse
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.

razrus said:
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
Click to expand...
Click to collapse
That's great to hear. I'm glad it came back to life. :good: Although, I wouldn't suggest using a toolkit. In my experience from what I've seen around these forums, they tend to cause more harm than good. It's good if you understand everything that's going on, and they can prove useful for devices that have really complex unlocking and rooting procedures, but Nexus devices are so easy to unlock and flash manually. I always flash each image file manually so if something goes wrong, I know exactly where it went wrong and how to fix it. The Google Play issue you mentioned is a perfect example. Flashing manually also helped me learn the basics of Fastboot and ADB. So if you want to stay on stock 5.1, I would recommend reflashing the factory image manually. I always use this thread to help me out in case I forget something: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Although it's for the Nexus 6, it's the same procedure for the Nexus 5, Nexus 10, Nexus 7, etc. That's the real convenient thing about Nexus devices as well, as they are all pretty much flashed the same way. Should all be really simple since you already have the drivers set up from installing the toolkit. Good luck! And have fun with your newly revived N10.

Can't hardware boot into fastboot.

I think I'm bricked. My shield is stuck in a simple bootloop and should be considered a softbrick. I can't seem to get into fastboot. Forget adb, that's not responding, but I'm still getting the android boot logo. I've tried so many ways. Holding the button, mashing the bettenbetter, plugging at the brick, power at the console, just about everything. Anyone figure out how to get into fastboot with hardware? If so, please let me know or I'll be throwing this out. It just won't seem to respond to fastboot. Such a shame.
EDIT: Android figured it out somehow and just booted, but I'd still like to know how to get into fastboot for when I'm not so lucky next time. Or any other way to get into recovery.
EDIT 2: Thought I posted this in troubleshooting. My mobile data was lagging somethinf fearce. Sorry.

It can be tricky mate. The way I did it was to unplug the device and then put the power cable back it. As soon as you plug the power cable back in hold the power button down until the fastboot menu appears. It took me a few tries. Of course if you have adb working the easiest way is "adb reboot bootloader"

baileyjr said:
It can be tricky mate. The way I did it was to unplug the device and then put the power cable back it. As soon as you plug the power cable back in hold the power button down until the fastboot menu appears. It took me a few tries. Of course if you have adb working the easiest way is "adb reboot bootloader"
Click to expand...
Click to collapse
I have done it once before, but it didn't work the way that their confusing instructions said. I'll give that a shot though. When android just flat out won't boot enough to access ADB, it can be problematic.

kdb424 said:
I have done it once before, but it didn't work the way that their confusing instructions said. I'll give that a shot though. When android just flat out won't boot enough to access ADB, it can be problematic.
Click to expand...
Click to collapse
It certainly doesn't help that there isn't a physical button on the Sheild, so your not absolutely sure your pressing in the right place after re-inserting the power cable.

In my experience the whole button is sensitive, bit that's still a pain. I have no problems booting my phone to recovery or fastboot, but that's just nuts. Oh well. Hopefully teh learned something as I'm sure their techs are complaining too. It is a consumer device, so I guess I can't be too mad, but still, they expect us to reflash before an RMA when needed sometimes, and that's not fair to ask with thes device lol.

I have the same issue here. I was able to get in fastboot hardware wise a bunch of times before. Now I think the device is done. I've tried every combination. What's weird is I did get a flicker of the bootloader continuing once. What could have changed that the bootloader is not responding anymore? How did you get lucky, let it sit there loading for a day? I've tried to see if fastboot commands can reboot the bootloader when I plug it in timing it correctly. So frustrating.

Yesterday from many many trying times I did it only once and don't wanna go cross again and don't ask me how I don't know how and still don't know how. I did everything by "book/instructions" finally give up and just randomly (panicly ) pressing / holding finger on it, power on / off...and then somehow bootloader screen appear. That should be fix by Nvidia
Sent from my SM-G925K using XDA Free mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:49 AM ----------
I hope some developers out there will create some magic solution how enter easily in bootloader mode, like using micro sd ports some modded scripts or usb ports where in plugged in mode console entering bootloader mode or recovery etc.
Sent from my SM-G925K using XDA Free mobile app

Glad I'm not the only one having issues. I've been trying everything with no luck. I'll give it a few more tries and then It's going back. Following Nvidia's instructions is BS. There is obviously an issue going on here that needs to be fixed.

mow4cash said:
Glad I'm not the only one having issues. I've been trying everything with no luck. I'll give it a few more tries and then It's going back. Following Nvidia's instructions is BS. There is obviously an issue going on here that needs to be fixed.
Click to expand...
Click to collapse
It will definately go into fastboot, it's just a matter of timing. It's really tight. In the end I stopped following their directions and just tried a bunch of random stuff. I tried so much I don't know what worked, but doing what they said wasn't working for me.

kdb424 said:
It will definately go into fastboot, it's just a matter of timing. It's really tight. In the end I stopped following their directions and just tried a bunch of random stuff. I tried so much I don't know what worked, but doing what they said wasn't working for me.
Click to expand...
Click to collapse
Same here - finally haotic random pressing / unplugging and at the end done only once
Sent from my SM-G925K using XDA Free mobile app

Im also in the same boat
Just tried to flash stock 2.1 and Full android 2.1 and now the shield wont boot into anything
Im trying the hardware bootloader method but thats not working so far.........ive just unplugged everything, and giving it a while before i keep trying.........i suspect i might have to try rma......that'll be fun...........(im implying, that it wont)

Same here, mine is stuck on on screen and stating production fused , and couple of options like recovery kernel forced recovery, none works fallowed nvidia instructions , tried downloading SDKS And followed commands nothing working , as well tried holding power button , and unplugging and nothing works, I will try what you guys did and see maybe I get lucky somehow

I have a Shield TV power device but the screen is black and I can not go to the Hardw
I have a Shield TV power device but the screen is black and I can not go to the Hardware Bootloader Access:crying::crying::crying:

Same here - when I plug int he power the green light comes on for about half a second then goes off.
Quite infuriating really.

I get a screen that sasys "continue booting..." and then it loads normally do I need to let go once it says this or should I continue to hold?