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".
Related
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.
Well, I'm at a loss. Last night, I fell asleep reading a book on my N7. When I woke up this morning, I put it on my nightstand and went about my day. I came home tonight and it wouldn't boot up. I stuck it on the charger for about 30-50 minutes and went to boot it up and noticed not even the battery symbol would show up when I hit the power button while connected to the charger. This is with the factory charger. I tried multiple other chargers, nothing. I had Slim Bean Beta on it before this happened. It gave me no issues before today. I'm leaving it on the charger overnight, but I'm doubtful. Any ideas? I'm sick to my stomach over this. This is the first tablet I've ever bought and it was great up until today. I know it's just a material item, but I paid money for it only a year ago and expect to get more out of it. If anyone has thoughts or a way to get this thing going again, I'd greatly appreciate it. I'm pretty sure I'm out of my warranty period. Thanks guys.
t1.8matt said:
Well, I'm at a loss. Last night, I fell asleep reading a book on my N7. When I woke up this morning, I put it on my nightstand and went about my day. I came home tonight and it wouldn't boot up. I stuck it on the charger for about 30-50 minutes and went to boot it up and noticed not even the battery symbol would show up when I hit the power button while connected to the charger. This is with the factory charger. I tried multiple other chargers, nothing. I had Slim Bean Beta on it before this happened. It gave me no issues before today. I'm leaving it on the charger overnight, but I'm doubtful. Any ideas? I'm sick to my stomach over this. This is the first tablet I've ever bought and it was great up until today. I know it's just a material item, but I paid money for it only a year ago and expect to get more out of it. If anyone has thoughts or a way to get this thing going again, I'd greatly appreciate it. I'm pretty sure I'm out of my warranty period. Thanks guys.
Click to expand...
Click to collapse
Have you tried pressing and holding the power button for 20-30 seconds to force a reboot? Occasionally they freak out and lock up and need a forced reboot.
yeah, tried that. I'm following google's instructions to charge it over night and do the power hold to see if it starts up tomorrow. if not, i dunno. i'm not going to buy another N7, not with all the problems they've been having, even the Gen.2. I can't afford anything else, so I'll just have to wait and see tomorrow. It's just a bummer. I had nothing but problems with an Asus TF-101 my grandparents gave me to use for a little, and now this. Asus doesn't seem to have their stuff together when it comes to quality control on tablets. My Asus Ultrabook is great, but these tablets are a different story.
Was it set to never turn off the backlight when reading? It's probable you are suffering from the battery bug that is posted in numerous spots.
Sent from my Nexus 7(2012) that has zero issues.
t1.8matt said:
Well, I'm at a loss. Last night, I fell asleep reading a book on my N7. When I woke up this morning, I put it on my nightstand and went about my day. I came home tonight and it wouldn't boot up. I stuck it on the charger for about 30-50 minutes and went to boot it up and noticed not even the battery symbol would show up when I hit the power button while connected to the charger. This is with the factory charger. I tried multiple other chargers, nothing. I had Slim Bean Beta on it before this happened. It gave me no issues before today. I'm leaving it on the charger overnight, but I'm doubtful. Any ideas? I'm sick to my stomach over this. This is the first tablet I've ever bought and it was great up until today. I know it's just a material item, but I paid money for it only a year ago and expect to get more out of it. If anyone has thoughts or a way to get this thing going again, I'd greatly appreciate it. I'm pretty sure I'm out of my warranty period. Thanks guys.
Click to expand...
Click to collapse
Try connecting it to your PC, if the computer shows APX Mode in Device Manager then I can help you out with it.
Just contacted Google and Asus, will be returned for RMA. Still covered under warranty since it was purchased in January, I luckily just found the receipt. I'm wondering if I should have just taken it back to Gamestop where I purchased it from instead of going through Asus.
t1.8matt said:
Just contacted Google and Asus, will be returned for RMA. Still covered under warranty since it was purchased in January, I luckily just found the receipt. I'm wondering if I should have just taken it back to Gamestop where I purchased it from instead of going through Asus.
Click to expand...
Click to collapse
The Sero 7 Pro by Hisense is totally up to par with this N7, plus it has a back cam, a micro sd slot for storage expansion, and only for $129.00 at Walmart. Maybe some devs can manage to port the N7 roms over.
Jorghe1025 said:
Try connecting it to your PC, if the computer shows APX Mode in Device Manager then I can help you out with it.
Click to expand...
Click to collapse
I'm gonna give that a try in a bit and let you know. I was gonna take it apart to see if the battery connection came loose but since I'm probably gonna return it I'm not going to do that in case I damage the backing taking apart.
is asus gonna give me a load of crap if they get it to boot and see that the bootloader is unlocked and running a different rom?
i plugged it into my computer and it recognizes it as an unknown device. no apx or anything else, just unknown. windows makes the sound that something got plugged in but i can't really find it.
got it, it's in APX mode
t1.8matt said:
i plugged it into my computer and it recognizes it as an unknown device. no apx or anything else, just unknown. windows makes the sound that something got plugged in but i can't really find it.
Click to expand...
Click to collapse
Try to google "Nexus 7 ADB APX Drivers", install them and try again.
It did happen to me the first time
---------- Post added at 04:20 PM ---------- Previous post was at 04:07 PM ----------
t1.8matt said:
got it, it's in APX mode
Click to expand...
Click to collapse
OK, follow carefully,
*Connect it to your PC
*Press and hold the power button while connected for about 15 to 30 secs.
*the bootloader will appear
*restore to stock using the Nexus 7 Root Toolkit
If failed wait 20 to 30 minutes WITH the N7 plugged in to your PC, disconnect it, reconnect it and try again.
That did save me from a $210 Brick.
Jorghe1025 said:
Try to google "Nexus 7 ADB APX Drivers", install them and try again.
It did happen to me the first time
---------- Post added at 04:20 PM ---------- Previous post was at 04:07 PM ----------
OK, follow carefully,
*Connect it to your PC
*Press and hold the power button while connected for about 15 to 30 secs.
*the bootloader will appear
*restore to stock using the Nexus 7 Root Toolkit
If failed wait 20 to 30 minutes WITH the N7 plugged in to your PC, disconnect it, reconnect it and try again.
That did save me from a $210 Brick.
Click to expand...
Click to collapse
I'll try it in a bit and let you know. If it doesn't work I just hope Asus doesn't give me a hard time about it being modified.
Buh Bye Warranty
Yes.. The warranty will be voided due to rooting the N7. Follow the instructions from everyone here and they will help you get it working. If the computer is recognizing their is hope.. Repeat this Mantra 'Help me XDA, you're my only hope'
Stop getting into a tizzy and dont give up so easy...lol
Be patient, calm, and logical and this will easily get fixed.
No tizzy here, I'm not through until I've exhausted all possibilities. Thanks guys.
no bootloader after following instructions. tried with power button and power button with volume keys.
Just want to give an update. Asus fixed my tablet and i should have it Monday. Won't know for sure how it is until it gets here but I'm pretty pleased with their service.
Oh, and I never received an email or phone call that they couldn't fix it because of being modded so that must be a positive sign.
t1.8matt said:
Oh, and I never received an email or phone call that they couldn't fix it because of being modded so that must be a positive sign.
Click to expand...
Click to collapse
Usually hardware faults are covered even on modified software.
Sent from my Nexus 7 using xda app-developers app
I'm hoping they include a reason as to why it quit working but i doubt they will.
I rooted my nexus 4 a few weeks ago, and now I'm just getting a blinking red light on my device. I left it on charge and when I got back there was nothing.
I tried all the different troubleshooting options such as plugging it in while holding the button down etc...
Everything I've read leads me to believe this is an unrelated battery fault. But now I have to RMA the device! Does anyone have any prior experience with this and warranty/root? It won't boot or show as a device or anything so I can't exactly remove the traces of root...
mindgrenade said:
I rooted my nexus 4 a few weeks ago, and now I'm just getting a blinking red light on my device. I left it on charge and when I got back there was nothing.
I tried all the different troubleshooting options such as plugging it in while holding the button down etc...
Everything I've read leads me to believe this is an unrelated battery fault. But now I have to RMA the device! Does anyone have any prior experience with this and warranty/root? It won't boot or show as a device or anything so I can't exactly remove the traces of root...
Click to expand...
Click to collapse
Looks like you might be hitting this issue. Sounds like it is a pretty known issue. If I were you I would try rma first. If it's refused try the method described in the thread.
fredericve said:
Looks like you might be hitting this issue. Sounds like it is a pretty known issue. If I were you I would try rma first. If it's refused try the method described in the thread.
Click to expand...
Click to collapse
I did have a quick look at that when troubleshooting. Funnily enough, literally 15 minutes after I get the email that the replacements been shipped, I had it plugged into my PC with the Nexus 7 cable, and it spontaneously boots up :\ now to see what's going to happen with the replacement?!
Hi everybody,
What Happened:
My phone has suddenly become totally unresponsive. I have been using it most of the day, it was sitting at around 70% the time that it happened, but it is now a totally black screen. I had just taken it out of my pocket and it was suddenly like this.
The only idea I could come up with as to why this happened is that I charged it off of a JBL Charge 2 last night. I'm not sure if that may have messed with the battery, but I do find it odd that it's totally unresponsive while plugged in.
I was running android 7.1.1 DP2, with the ElementalX kernel 4.0 I believe. I was also rooted with SuperSU. What's really odd is that I hadn't done anything new recently besides install uTorrent and VLC media player. Otherwise, my routine has not changed one bit. Up to when the phone actually died, I hadn't even used either of these new apps the entire day.
What I've Tried:
I have tried plugging it in via AC, via USB, I've tried booting into recovery or fastboot, but there is zero response from the phone. No indicators on the screen, no LED blinks, no vibrations, nothing.
What I'll Try:
If anyone has any experience with this happening, I could use some advice. Otherwise I'm just going to wait it out, consider an RMA I guess. However, my device did have the bootloader unlocked and was rooted, so.... I hope it comes back by itself.
My advice is to keep it plugged in, or see if there is a response on the computer perhaps on fastboot, upon using the bootloader keys. I haven't had this, just a few suggestions. Good luck!
PS: A RMA will probably be needed, there are much more experienced people around here. Sure you may get replies later.
Good luck?problem all nexus 6p!!! Lg responds repay helps, hawuei what to do? problem arises with nogaut not be our fault, how to fix this? My phone now in service but to be fair this? warranty and having to wait ..
Hi all,
Hopefully this wasnt covered before- I used the search function and it didnt return any results, at least not for my specific scenario.
I've had this 6p for about 18-20 months roughly. Been my best phone by far, and I've been very happy with it(normally i replace my phones every 8-12 mos because I need the latest and greatest lol).
About six months ago I threw PureNexus on there with I believe Flash kernel. Worked flawlessly, and I've been really happy with it.
About a week ago, it powered off on its own but i had it in my back pocket so I just assumed it was an accidental reboot. However, this morning, I woke up, threw it on the charger for about 30 minutes, got to about 60%, and unplugged it. While I was using the browser, it froze up for a minute then shut down. No bueno. Cannot get it to power back on. No power light while charging. I did what others have had luck with, holding power, and/or power/down for several minutes, still nothing.
I reached out to Project Fi, and they want a 500 dollar hold to send me out a refurb replacement. I know they release the funds in approximately 12 days but we had a recent death in the family and I just cannot afford to have 500 bucks locked up, especially right now. Spoke w a supervisor, apologized, but said nothing they can do.
On a whim, I plugged it into the pc, and it DOES detect it but its the dreaded QHSUSB_BULK under 'other devices'. So that tells me its at least got power, but, I'm unsure if just trying to use adb(i havent in a while, not since i did the initial rom install but im sure i can find instructions) to attempt to throw the base image back on there, will work, or which direction to go.
I found this but I dont think its for my specific phone but thought maybe there was a set of instructions for this particular phone similar to these:
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I have seen several reports of this error happening when flashing the wrong rom, or using the wrong image, but never just all of a sudden when its been running like a champ.
any thoughts? thanks in advance.
Nexus 6p is plagued with issues like shutting down at certain percentages and the dreaded bootloop of death. You could get in contact with Google heard even people out of warranty having success. Could also have a shop replace the battery in some cases that fixed the shutdowns.
If it doesnt boot up at all I can't help you. If you can get to bootloader, flash stock image, un-root, re-lock your phone. see if it boots. I had to do all this, this morning. Phone would just shut off at 80%, reset and hang at the google sign. I could only get to into the main system with a hard reset every time. then it would reset and lock up. So i reverted it to stock and we will see how it goes. So far its been 6 hrs and no random resets and its in full use.
Yea, the problem is, I cant. Its not even a boot loop. Just looks like its dead. Held the power button down for roughly 10 minutes out of desperation.
The odd thing is, if i plug it into my pc it shows how i mentioned in my initial post. So it must have juice even though the power light/etc isnt on and it doesnt show charging.
Last hope I think i have is to run it out of battery leaving it on the table, then hope somehow when i plug it into charge, that resets it somehow since it was dead, and maybe clears whatever the issue is. Very odd considering it was working fine until this.
Your phone is stuck in the EDL mode when its detected as QHSUSB__BULK. There are solution for this but i dont know if this solution is combined with data loss or not and i try to find that out recently. I also still dont know how to fix that with linux.
Here two howtos:
https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838