Gee, I didn't have a chance to root it or anything. I just got my Turbo 2 on Monday from Moto-Maker, got it all set up like I wanted, was checking FB, and the app froze. I closed it out, and opened it up again, and it froze again. So I shut the phone down thinking I would restart it, but after it turned off, it wouldn't start again. Tried holding the power button for 10 seconds, tried booting into recovery, tried charging, tried hooking it up to a computer. Nothing. Black screen, dead, never turned back on, not even a recharging indicator. I'm bummed.
I've already started the exchange process with Moto, but I thought I would post here as a heads up in case it becomes a problem with this model. I've had bricked phones before, but never after 5 days.
Just sounds like you got a defective phone, hopefully your replacement is fine. You're not gonna get a chance to root the next one anytime soon, these phones haven't been rooted yet.
Root will come. It always does. I hadn't even thought about it. I usually run stock for at least a few months so I can figure out what I want to change.
Root doesn't always come, not any more.... There are a number of phones that have never received a proper root. Some have temporary root, some have nothing.
Never buy a phone for what it MIGHT do in the future...
Sent from my XT1585 using Tapatalk
Oh yeah. I got that. I'm not concerned about having root. The point I made was that I hadn't done anything to the phone to brick it. This phone will get root. Just like last year's Turbo did...eventually. Verizon makes it difficult, but eventually someone figured it out. But the T2 is some decent hardware, so someone will eventually decide to do it. Probably have to pay for it, though.
amateurhack said:
Oh yeah. I got that. I'm not concerned about having root. The point I made was that I hadn't done anything to the phone to brick it. This phone will get root. Just like last year's Turbo did...eventually. Verizon makes it difficult, but eventually someone figured it out. But the T2 is some decent hardware, so someone will eventually decide to do it. Probably have to pay for it, though.
Click to expand...
Click to collapse
Same thing just happened to mine - only 4 days out of the return period! I'm so pissed. I plugged it into the turbocharger to charge overnight, and when I woke up in the morning I realized my alarm never went off. Phone won't respond when plugged into a charger, PC, power button, or holding any combination of keys to hard reset.
sweendiggler said:
Same thing just happened to mine - only 4 days out of the return period! I'm so pissed. I plugged it into the turbocharger to charge overnight, and when I woke up in the morning I realized my alarm never went off. Phone won't respond when plugged into a charger, PC, power button, or holding any combination of keys to hard reset.
Click to expand...
Click to collapse
Update, Verizon replaced it with a brand new phone despite being of my return period. The manager said they can, at their discretion, perform a new-for-new exchange up to 30 days and mine was obviously DOA. He said he had never seen one of these die like this, and it's usually one of their better phones. I have my fingers crossed that this one works out OK.
I had to order my replacement from Moto Maker. I've had it for two weeks with no issues.
Related
Like the title says... woke up to the HTC boot screen and it wont boot past it. I bought it on Nov. 18th so it has been 34 days and ATT will not replace it in store because it is 4 days past the return date. Warranty will cover it, but this is frustrating right before the holidays. BAck to the old Tilt2 I guess.
Watch out and always sync your pics and such to your zune software!
Woke up this morning, once again with a dead Surround. This was my replacement device that warranty covered from December. Another one is on the way from ATT, but I was wondering if there is some lemon law where I can get my money back or something? If my phone is going to keep dying every few months I don't want it.
kdj67f said:
Woke up this morning, once again with a dead Surround. This was my replacement device that warranty covered from December. Another one is on the way from ATT, but I was wondering if there is some lemon law where I can get my money back or something? If my phone is going to keep dying every few months I don't want it.
Click to expand...
Click to collapse
in texas theres a lemon law but i dont know if you have one
The rep on the warranty line said after 2 or more FRU's they will negotiate a replacement device. Which is fine, as I may be negotiating for a different phone if this one dies.
Was it plugged in when it died?
Sent from my Desire HD using XDA App
The first one died unplugged, moments after I woke up and shut my alarm off and unplugged it. The second one was plugged in and the bright white screen woke me up in the middle of the night. Both of them acted funny before they self-bricked, like forgetting my IE favorites and deleting some apps randomly.
I had this same problem. Replaced under warranty and so far I haven't had that same issue. I did have a different issue though, where it didn't read the whole memory properly as referenced in this thread:
http://forum.xda-developers.com/showthread.php?t=916865
I'm worried this device is prone to failures, as I've now had two devices acting up. I'm trying to get AT&T to give me a different device, but they said I can only do same device exchanges under warranty.
vel0city1 said:
I had this same problem. Replaced under warranty and so far I haven't had that same issue. I did have a different issue though, where it didn't read the whole memory properly as referenced in this thread:
http://forum.xda-developers.com/showthread.php?t=916865
I'm worried this device is prone to failures, as I've now had two devices acting up. I'm trying to get AT&T to give me a different device, but they said I can only do same device exchanges under warranty.
Click to expand...
Click to collapse
They do in fact have a policy for device replacement for multiple FRU's. Meaning, if you are like me, and have already replaced two under warranty (meaning you are using your third device) if you have problems with the third they can negotiate an alternative device if it is still under warranty. Call the warranty exchange number over and over until you get someone who is knowledgeable and is willing to work with you. And keep calling with every complaint so they have it on file!
Good to know. I guess I'll just go and exchange it now and hope the next one either lasts forever or calls it quits ASAP. Warranty is running short these days :\
The warranty is one year from original purchase date or 90 days from activating the replacement device, whichever is longer.
My Surround also wouldnt boot up. happened last week. It was on my desk and not in use. I watched as it said goodbye and shut off. Battery drained and turned off, no big deal as I tend to let that happen before plugging it in for the night.. Only this time it wouldnt get past the white HTC screen. I did the whole volume button reset thing and still nothing. Ended up talking with HTC and getting it shipped to Texas to get it looked at. next day it was in the mail back home. Should be here in the next day or so.
Im curious to see if the paperwork will let me in on what happened. Although I sort of doubt it.
Awesome! I was under the impression it was just 90 days.
Talking about HTC Surround acting funny?
Well, mine likes too.
1. I used my phone as a alarm clock. Every night I connect it to the wall charger and leave it turned on resting on the night table. The next day guess what, I woke up late. The phone never sounded the alarm, in fact it won't make any sound at all. Have to reset it to return it to normal.
2. There have been a couple of times where I have not received calls in hours. When I press the power button to check the status, the phones goes throughout the complete power up sequence. But the phone was already powered on the last time I checked a couple hours ago and the battery is full. Its like it powered off by itself at anytime without warning!
3. Try to use the phone while charging and you'll notice touch screen response gets a a little jittery. But I found a "cure" for that. Hold your phone in away that your fingers make physical contact with the metal frame around the display. This will minimize the jittering effect on the touch screen.
4. Camera autofocus needs prescription lens. My HTC Surround digital camera have a hard time trying to focus on objects more than 15 feet away. It gives focus confirmation but the pictures always look blurry.
Those are some of the bugs I found in my HTC Surround purchased from AT&T last November. I'm sure they are not the only ones!
Those are known bugs, but seemingly have no correlation between devices randomly dying or not. My first surround had all those bugs and died, my second one showed little signs of any of those bugs and died anyways. Hoping my third one dies within warranty so I can get a new phone :/
This has happened once before, but just for a small amount of time to to the heat (I believe). The phone has been off for over and hour and refuses to turn on whether I hold down the volume button, don't hold down the volume button, or push the battery in at the exact time as I'm doing the other one or two. The splash screen flashed for half a second and immediately went back off when I plugged my evo charger, the usb part, into my portable ipod charger, so I believe this means there is still help available! Last time this happened, which was months ago, it seemed as if it just needed to cool down a bit, and my reading on the internet confirmed that the phones shut off when their batteries reach too high of temperatures. So what I did was wrap the phone and the battery, separately, in a large wash cloth and let them sit it the fridge for a little while. No luck, I'm running out of ideas (and I realize a ziplock bag may have been better but who cares). A few days ago I installed cm7gginggerbread7 (wimax) over cm7gingerbread2, but have not had any issues up until now and everything has run perfectly as well as smoothly. Is there any way I can turn my brick into a phone? Perhaps there's a way to adb something even though the phone wont boot (im a noob). I'm just pissed cuz I finally got every little thing exactly the way I wanted it, and now I'm stuck with a paperweight :/ I thank you for all your help, brave knights
It just suddenly shut off and won't turn back on?
And you weren't messing with anything?
If so, sounds like it's a hardware or battery issue.
Can you try a different battery?
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
sitlet said:
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
Click to expand...
Click to collapse
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
matt2053 said:
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
Click to expand...
Click to collapse
If they can't get it to power on then it really doesn't matter if it's rooted or not because they won't be able to find out.
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Raillery said:
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Click to expand...
Click to collapse
If this occurred while you were NOT changing anything with the radio partition or recovery partition then it's not a brick issue.
Sounds like you have a hardware issue.
Take it to the store.
If you smash it you will be paying $100 to asurion for a replacement as Sprint changed the TEP again.
Just wondering was your battery completely dead before this happened. I have read some people here and other places have said that if the battery completely dies that it won't charge unless you put it on a actual battery charger made for it. Does the charge light come on when you plug it in? Also, like my friend before me said, take it to Sprint. Ask them if they have a battery you could try. If it doesn't work it will eliminate the battery being the issue. If it won't boot they will replace it. They won't be able to tell if it is rooted because it won't boot. If you were flashing a radio and didn't let it finish or the battery died during the process, you are bricked.
Does the charge light flash when plugged in?
Sent from my PC36100 using Tapatalk
The light doesnt change
clean off the battery contacts
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
vespix said:
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
Click to expand...
Click to collapse
Take the original battery to sprint. Tell them the story and get a replacement, ask for some free accessory since you've helped them isolate a reliability issue.
LOL
There are two known issues with the Evo to be aware of. The first is the charging bug. If the Evo shuts off due to low battery level there is the possibility that the charging circuit fails to recognize the dead battery as even being there and will not charge. The workaround is to charge the dead battery in another compatible phone or use an external battery charger. This is supposed to be fixed in the next update but we'll see.
The second is the thermal sensor bug. The thermal cut off starts to trigger at lower and lower temps til even freezing the phone won't work. I thought the local service center was joking til I actually saw it reproduced. This is a hardware issue and the only fix is a replacement phone.
The first issue is intermittent but knowledgeable service centers are aware of this and will either charge the dead battery or swap out with a charged one.
The second issue is reproducible but can take some time to do so depending on how far off the sensor is. Again, knowledgeable service centers are aware of this and will want to reproduce it before ordering a replacement.
Not sure what technical thong is happening, but I do know I panicked when it happened to me, bit it turns out if you try to charge EVO from a USB port while its in the recovery mode it will eventually drain and **** off. I forgot I was on recovery mode and came back to what you described. After doing the swap with my GF's EVO and realizing my battery was fine, I remembered how I had left the phone in the first place and Googled it to confirm that will cause the dead EVO scare.
Sent from a corrective lens wearing eskimo translating Turkish smoke signals viewed over a streaming webcam at 640x480 resolution via a U.S. Robotics 14.4 Hayes compatible modem.
This has happened to me twice, but since I was on the extended battery from sprint, I would just pop my stock battery in and it powered up fine. Each time I just brought my battery in to sprint and they replaced it. Also, when it happened to me the charging light wasn't turning on or anything.
Sent from my PC36100 using XDA Premium App
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
cjh6386 said:
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
Click to expand...
Click to collapse
Blinking charge light means that the battery v has dropped below the required v to turn on the phone. I see 4-5 Evo's a day like this as well as the charge bug.
I actually got it booting again somehow. Now, it consistently turns on, will boot to the bootloader, but recovery doesnt work and it wont boot into the phone. It does search for pc36 image though... i might try that.
I just sit here and shake my head on a daily basis when I see people talk about problems and inevitably, and I'm not saying this is applicable in this case, but they say in their post they were using ROM or Kernel Manager.....
Just a story here, I RMAed my TF about a week and a half ago for like 8 dead pixels (just bought it at the end of August) and just got it back today. Went to go nvflash it so I could have root back, etc etc., and when it booted up (came back at 91%) I noticed it wasn't charging. I tried flashing a custom kernel, still not charging. Thought that was weird, so tried nvflashing again, except nvflashing wouldn't work. Thing was, the nvflash had had some trouble the first time, because I was doing it on my husband's computer (mine like, exploded yesterday, some ArchLinux update did NOT like me) and it kept saying "could not connect to any USB devices." I didn't think much of it when it finally worked because he said his had done that before, but in retrospect, must have been related to the charging problem.
Anyway, at this point I was pretty crabby, because I don't really understand how I RMAed my perfectly functioning TF (with slightly defective screen) and I now have a completely non-functioning TF with a perfect screen. (I guess they fixed the problem?) WTF were they even messing with the USB port for anyway? Anyway, I never was able to nvflash it back to stock, except I did manage to get it to work finally by holding the USB cable at its base next to the TF carefully (and before anyone says it's the cable, tried several, it is not) but then it interrupted halfway through and would not restart, and I'm pretty sure the tablet is a brick. Could someone correct me if I'm wrong - is there a way to restart the nvflash process if it has been interrupted partway through?
Either way, just thought I'd share this nightmare. I'm still pretty irritated with Asus, which is saying something, because I've always been kind of an Asus fangirl.
you did not mention if is still not charging . If so could be the small switch inside. Search for not charging as there are several threads on opening TF and finding switch. If bat gets too low can effect flashing.
The battery was at about 88% when I flashed - now the TF won't do anything at all, including start the nvflash process over again. Terminal just throws an error and says something about not being able to restart because end point was not reached. (Not by the computer) I'm pretty sure it had nothing to do with having enough charge, it just won't connect properly.
Like I said though, doesn't matter much now, because the TF won't do anything. Won't go into APX mode or boot. I assume this is because the nvflash process interrupted halfway through. It won't let me restart it - get the error I mentioned. I assume I'm screwed, but was wondering if anyone knew a way to get it going again. I thought it was pretty impossible to brick a TF (like a Droid X) but I've never seen an nvflash (or an SBF) interrupted halfway through.
Edit: and yeah I have no idea if it'd charge like this or not, but somehow I doubt it Firmware = poof.
Sent from my DROIDX using Tapatalk
do you know which RMA facility it was shipped too? ive heard horror stories about the texas facility. just curious oh and i hope you get it fixed
I have a ASUS G73 notebook that I had to RMA like a year ago for screen problems. It went to some place in Indiana. When I got it back it had an LCD with a deep gouge in it as if someone had taken a knife to it. So yeah who knows what the deal is with the companies ASUS outsources repair to.
Was indeed Texas. Gave them a call and the guy was like "Derp we think something might be wrong with the battery" and had me try turning it on, blah blah. Am shipping it back tomorrow. I don't feel particularly bad, since it wasn't my screwup, and it's not like I was a dumbass and was like I WILL FLASH AT 3% BATTERY LOLZ. There's clearly something messed up somehow with the connectors.
Anyway, I hope that it gets resolved soon. Being without it really sucks for school. I'm sure its just going to get there and they're not going to be able to turn it on either, no matter what they try. Makes me wish I would have just stuck with the dead pixels though, because I suppose if they do replace it, I'll end up with a B9O. :/
Edit: Thanks for commiserating with me anyway, guys - helps me feel a little better!
Sent from my DROIDX using Tapatalk
My coworker and I both had to RMA the dock to the TX facility and both docks came back with problems. I sent it back there yet another time but his was sent to CA. The turnaround time was amazing but the quality... not so much. It's on its way back to me though and tomorrow I'll know what they did this time.
uploder said:
do you know which RMA facility it was shipped too? ive heard horror stories about the texas facility. just curious oh and i hope you get it fixed
Click to expand...
Click to collapse
Literally just got it an hour ago, installed my old apps and it now is turning off randomly. Sometimes when it's in my pocket, other times when it's sitting on my desk. Makes no sense, google'd and found nothing of any help really.
I've battery pulled tons of times, and sometimes I have to pull two to three times before the damn phone will even power on.
Plugged it in just now, it will show it's fast charging... try to turn it on and it won't turn on.
Taking it back for replacement or maybe a new battery. Just checking if anyone else has this problem.
Just an update: It was a complete dud from the factory.
So after taking it back to the VZW store I agreed to see if ti was just the battery, get home and go to look at the phone. Dead.
Got a brand new one and it's fine now.
halffrozen said:
Just an update: It was a complete dud from the factory.
So after taking it back to the VZW store I agreed to see if ti was just the battery, get home and go to look at the phone. Dead.
Got a brand new one and it's fine now.
Click to expand...
Click to collapse
Lucky they exchanged 1 to 1. That must have been an unpleasant and frustrating experience...
psycovirus said:
Lucky they exchanged 1 to 1. That must have been an unpleasant and frustrating experience...
Click to expand...
Click to collapse
I'm a business customer, they better make me happy. lol
It was saddening that I got one of the only phones(from my searching) to ever have these problems.. but everyone makes duds...
My Nexus 6P decided to become completely unresponsive and turn off whilst on around 30% of battery yesterday.
Since, I've attempted to long press the power button, try to put the phone into boot mode by holding the volume down rocker (and tried it pressing up just in case) and power, alas no response.
Plugging the phone into the power socket returns no response also, no battery/charging animation and no red LED from the notification light.
Has anyone else had this problem/has a solution?
Thanks,
Ravi
Try leaving it connected to the charger for several hours and trying again. If that doesn't work then file a warranty claim. Had you modified it in any way recently?
I tried to do so for a few hours, but worried it was due to an overheating issue but will try for longer today, thank you! As for any modifications I've refrained from rooting or doing anything to the out the box model, the worrying issue is that I get no response from charging the device, makes me think that it's a hardware issue. Thanks for your reply!
sorry for the necro post, but the same issue happened to my wife's phone today. It was at 87% charge and plugged in when it happened. It powered off while she was watching a video and is now completely unresponsive. Did your phone "revive" or did you have to file a warranty claim?
Thanks
Zzan said:
sorry for the necro post, but the same issue happened to my wife's phone today. It was at 87% charge and plugged in when it happened. It powered off while she was watching a video and is now completely unresponsive. Did your phone "revive" or did you have to file a warranty claim?
Thanks
Click to expand...
Click to collapse
Mine recently powered off due to overheating. I left it for an hour or so and then plugged it in, and after a few minutes connected to the power supply it deigned to power up.
I was about to do a post about the cause of the overheating when I found this thread.
The same thing happened to me about a week ago. I have had no luck reviving the phone. I purchased it used a few months ago, so neither Huawei nor Google will accept it for repair, and I cannot find any third party who can repair the 6P. I now have a costly paperweight.
If anyone has a solution, I would love to hear it.
Zzan said:
sorry for the necro post, but the same issue happened to my wife's phone today. It was at 87% charge and plugged in when it happened. It powered off while she was watching a video and is now completely unresponsive. Did your phone "revive" or did you have to file a warranty claim?
Thanks
Click to expand...
Click to collapse
Hey,
It went a day without being able to be turned on, went for a shower and my girlfriend shouted saying that the phone turned on. Literally was a matter of leaving it plugged in and not attempting to do anything with it. No idea what the fault was to begin with and it hasn't happened since, sorry I can't be of much help with this but that's my experience with this issue!
EDIT: As knirirr it very well could be overheating and it's the only reasonable solution I can think of where nothing else is evident, at least in my experience.
My wife's phone powered back on after a few hours. She did say it was not hot or even warm when it shut down. I don't know what the catalyst for it coming back on was. It was completely unresponsive but after seeing posts elsewhere with other nexus devices having a similar issue and people said hold down the power button for up to 10 minutes and it will come on. I didn't believe that this would work and figured that something else was actually the trigger, but when I did it the phone powered up at about three and a half minutes and has been working fine since.
Thanks for all the replies.
charlie.s said:
The same thing happened to me about a week ago. I have had no luck reviving the phone. I purchased it used a few months ago, so neither Huawei nor Google will accept it for repair, and I cannot find any third party who can repair the 6P. I now have a costly paperweight.
If anyone has a solution, I would love to hear it.
Click to expand...
Click to collapse
Did you purchase it directly or third party? I purchased through Google and even after 5 months they accepted it for return.
Sent from my Nexus 6P using XDA-Developers mobile app
dratsablive said:
Did you purchase it directly or third party? I purchased through Google and even after 5 months they accepted it for return.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I purchased it on Ebay from a third party