Related
While I was listening to Soundcloud the phone rebooted and now its in a bootloop.
Just great! Can't start the phone.
borisb said:
While I was listening to Soundcloud the phone rebooted and now its in a bootloop.
Just great! Can't start the phone.
Click to expand...
Click to collapse
you know i really dislike recommending this but you may have to do a factory reset of the device :
1- Fully Turn off your Device
2- When is completely off : PRESS AND HOLD VOLUME UP + POWER till you see the Recovery Screen
3- With the volume buttons navigate to WIPE / FACTORY RESET and PRESS POWER Button.
4- Reset System.
hope that helps. good luck
DrakenFX said:
you know i really dislike recommending this but you may have to do a factory reset of the device :
1- Fully Turn off your Device
2- When is completely off : PRESS AND HOLD VOLUME UP + POWER till you see the Recovery Screen
3- With the volume buttons navigate to WIPE / FACTORY RESET and PRESS POWER Button.
4- Reset System.
hope that helps. good luck
Click to expand...
Click to collapse
If I need to do that I am returning the phone.
Issues like that will return and I will lose my data all the time.
Suddenly the note 7 does not look so expansive.
borisb said:
If I need to do that I am returning the phone.
Issues like that will return and I will lose my data all the time.
Suddenly the note 7 does not look so expansive.
Click to expand...
Click to collapse
understandable but believe it or not, sometimes after doing the first Factory Reset fixes a lot of current issues when you boot the device for first time or after OTA's or Big Update...
just give it a try and if still having issues just do what's best for you
I got no update yet.
I reset to factory defaults and cleaned the cache. Nothing happened.
Removed the SIM and the SD and did it again.
Still bootlooping.
I knew this phone is too good to be true.
Now I have to return it.
Talked to ZTE.
The phone cannot be replaced cause they dont have anything to replace it with.
You never had to return a Samsung or LG? I have.
Any phone you get can have its issues. I know your frustrated but just get a replacement or return it and move on.
You can ask for suggestions and try them but bashing the device because you possibly got a bad one doesn't help you at all. And it probably didn't make you feel any better either.
borisb said:
I got no update yet.
I reset to factory defaults and cleaned the cache. Nothing happened.
Removed the SIM and the SD and did it again.
Still bootlooping.
I knew this phone is too good to be true.
Now I have to return it.
Click to expand...
Click to collapse
Probably bad emmc block and it can't recover from it. You would have to re-flash factory image to bypass it if corruption is in one of the critical partitions
tolymatev said:
You never had to return a Samsung or LG? I have.
Any phone you get can have its issues. I know your frustrated but just get a replacement or return it and move on.
You can ask for suggestions and try them but bashing the device because you possibly got a bad one doesn't help you at all. And it probably didn't make you feel any better either.
Click to expand...
Click to collapse
I did have an issue with the note 5 and it was replaced at AT&T. But ZTE have no replacements.
Here is a snippet of the conversation.
Boris Ba: So if I do an RMA
Boris Ba: how long will it take?
John P.: The wait would be until we get in additional supplies which would 9/9.
Boris Ba: and ZTE thinks its a normal retail behavior?
John P.: It is not. The demand for the device has been greater than initially anticipated. This is definitely not the norm.
Boris Ba: This sucks. I will not buy this phone for the second time.
Boris Ba: And I need to spend energy to send the phone back.
John P.: I completely understand your decision given the circumstances.
peramikic said:
Probably bad emmc block and it can't recover from it. You would have to re-flash factory image to bypass it if corruption is in one of the critical partitions
Click to expand...
Click to collapse
Can you link the instructions?
borisb said:
I got no update yet.
I reset to factory defaults and cleaned the cache. Nothing happened.
Removed the SIM and the SD and did it again.
Still bootlooping.
I knew this phone is too good to be true.
Now I have to return it.
Click to expand...
Click to collapse
which Software version were you????
try flashing B18_to_B20 patch of you were in B18 this update may fix your issue
and i meant flashing over Stock recovery
peramikic said:
Probably bad emmc block and it can't recover from it. You would have to re-flash factory image to bypass it if corruption is in one of the critical partitions
Click to expand...
Click to collapse
I was thinking the same thing. If ZTE would just release a full system image, software-related issues like these could be fixed by the end user by reflashing through recovery, no need to RMA...
borisb said:
Can you link the instructions?
Click to expand...
Click to collapse
Unfortunately we don't have such an image for the US model, only for China and Global(Eu) which is also a ZTA blunder considering they relesased BL unlock. Quite a few problems are solvable with it, but ZTE has not released one yet. Probably what drained their initial RMA stock, if they had proper one one to begin with.
Sorry to get your hopes up...
DrakenX is correct.
First thing I do when I get a new phone is a hard reset. This will insure you get a proper install of the OS compared to the OS being installed on a 100 phones at once all hooked to a data rack and drawling from the same image.
All phones are initially installed this way the same with proprietary crap computers like Dell, HP, Sony and all the rest. If there is any type of power glitch or lag in the data stream it can affect your original out of the box install. So in short ALWAYS hard reset a new phone for peace of mind.
peramikic said:
Unfortunately we don't have such an image for the US model, only for China and Global(Eu) which is also a ZTA blunder considering they relesased BL unlock. Quite a few problems are solvable with it, but ZTE has not released one yet. Probably what drained their initial RMA stock, if they had proper one one to begin with.
Sorry to get your hopes up...
Click to expand...
Click to collapse
Eh.
Too bad. Well I got a refund from newegg so no worries.
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
the.root said:
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
Click to expand...
Click to collapse
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
BIGSAMDA1ST said:
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
Click to expand...
Click to collapse
Thanks. I came across that. I tried flashing MMB29P as well as several other factory images without success. My problem now it seems no matter what I flash I cannot get back into recovery anymore. Even if it's stock or if it's TWRP (any version - including 3.0.2.0 as they suggest), so I don't really get passed step 4-5 in that guide. I guess she only had so many reads left in her, sigh.
WEIRD @ warranty link. It says from my S/N that it's valid until 2017-02-17. I don't know how, I purchased it 2015-10-22, it shipped 2015-11-24, and I got it 2015-11-30. Unsure how/why that would've gotten extended until February. I'm concerned they'll get it back then deny it once they figure that out, or figure out it's been unlocked/flashed. When I first got the phone i had issues with it charging, I narrowed it down to the USB C->C cable being faulty, and contacted Huawei. They absolutely refused to replace just the cable. Said I had to ship the whole phone back and it'd take AT LEAST 3-4 weeks to get it back. I argued with several people on the phone there (their support 100% refuses to give you their name or transfer to their supervisors btw), and finally asked google support to pull some strings and get in contact with someone there to replace a simple freaking cable - no one cared at all - spent several hours trying and got nowhere. I'm /done with Huawei. I think my best bet is to probably find out how well that American Express extended warranty claim works, I've never actually had to use it before. IDK what I'll do after that. Sad this is a common problem with these phones exactly one year out, so even if I wanted to buy a used one on eBay I'd risk the same thing shortly thereafter.
I'll keep the phone powered off for a while and try some more flashing later see if I can get back into recovery to try the rest of his steps in that article. It's not looking promising anymore.
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
BIGSAMDA1ST said:
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
Click to expand...
Click to collapse
Hmm interesting. Maybe their US support has improved since last year. So it was brand new not refurbished? Did you get the full retail box set? I bought mine directly through Huawei, so I would like to think that they would have accurate warranty data, but perhaps not. I will consider RMA'ing it to them if it's really a new one. It's either that or a 550$ refund from my credit card company. I haven't tried fastboot lock yet, will do that when I give up on all else lol (and need to return it), but hopefully that will work if the rest of the emmc is hosed.
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
BIGSAMDA1ST said:
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
Click to expand...
Click to collapse
Just called them. They won't accept it back without a proof of purchase. I have to send in the proof of purchase before they'll approve the RMA and then I get the shipping label/information. And "they can't look it up by S/N, doesn't matter if the website says it's in warranty". LOL. Sounds about right from what I remember of their support. They say their website is inaccurate, and cant ever verify/lookup that I bought the product directly from them. Maybe I'll try back tomorrow to see if someone else will help but it's unlikely from the sounds of it. She did say this is very common problem however, knew all about it.
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
BIGSAMDA1ST said:
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
Click to expand...
Click to collapse
Yeah I played dumb and all, didn't help. She didn't ask me any real questions she was convinced of the problem just from my description. She also said it's 12 months from the date I purchased it and not when I received it in the mail (so since they took 5-6 weeks to get it to me - preorder madness - I don't get that time back in the warranty) lol. Not like it matters now, just to further comment on how crappy their support/warranty is (in my experience).
I'll follow up if I have any more luck unbricking the device or warrantying it for that matter.
Good luck on either with the warranty or bringing it back to life.
I also have problems such as your support Huawei says four weeks of waiting
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
the.root said:
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
Click to expand...
Click to collapse
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
BIGSAMDA1ST said:
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
Click to expand...
Click to collapse
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
the.root said:
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
Click to expand...
Click to collapse
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
BIGSAMDA1ST said:
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
Click to expand...
Click to collapse
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
the.root said:
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
Click to expand...
Click to collapse
Exactly.. That's why I'm still keeping mine and hoping it doesn't decide to go on the fritz again.
Got a used 6P 128 meg for christmas. Did OTA to 7.1.1 then unlocked bootloader, installed latest TWRP and rooted. Installed Pure Nexus 7.1.1 , Dynamic GAPPS and Flash Kernel on Christmas day. Been running great for 5 days then out of nowhere it started bootlooping at the GOOGLE screen. After establishing that I could not get anywhere with recovery but still reported device through fastboot I downloaded the latest factory image and flashed that with no change. At this point I am out of ideas. Any thoughts on grabbing a MM or 7.0 image? Actually any ideas are certainly welcome! Happy New Years everybody... LOL
CyberpodS2 said:
Got a used 6P 128 meg for christmas. Did OTA to 7.1.1 then unlocked bootloader, installed latest TWRP and rooted. Installed Pure Nexus 7.1.1 , Dynamic GAPPS and Flash Kernel on Christmas day. Been running great for 5 days then out of nowhere it started bootlooping at the GOOGLE screen. After establishing that I could not get anywhere with recovery but still reported device through fastboot I downloaded the latest factory image and flashed that with no change. At this point I am out of ideas. Any thoughts on grabbing a MM or 7.0 image? Actually any ideas are certainly welcome! Happy New Years everybody... LOL
Click to expand...
Click to collapse
Did you flash the entire factory image using flash-all.bat like Google suggests or do something more complicated where you flashed the factory image in pieces?
Actually I tried both ways. I did all the pieces separately but the data then formatted the data then then tried the flash-all.bat Starting to get worried for the first time since rooting my Samsung Moment on Froyo.
A couple of people with boot loop issues claimed that flashing 6.0.1 fixed their problem. If you are desperate it might be worth a try.
Bootloop?problem hardware https://www.google.it/amp/www.digitaltrends.com/mobile/google-nexus-6p-bootlooping/amp/
I was able to get Huawei to RMA it even though its out of warranty
Downloading 6.0.1 and then contacting Huawei are on the agenda then. I'll keep folks updated... Thanks guys.
EDIT: 6.0.1 flashed with no change. Still have fastboot access but any other option besides barcodes just reboots. Will start looking into RMA.
EDIT TWO: Huawei is blaming GOOGLE but they agreed to RMA. Looks like one is popping up every few day on here so how many are really happening??
Just happened to me. RMA on the way. I love playing with android but pixel and 6p having to many problems . I may go another OEM on android. Or hang myself and get an iphone .
How does the RMA process work with Huawei? Do they cross ship?
RMA?ok my problem RMA i'm be month later, no phone available and having to wait another day to get reimbursement phone, never buy more hauwei
i took a picture with my flashlight on last night and got kicked into a boot loop then it just died completely. when i plug it in no light goes on in the corner or anything. i did wake up to it stuck on the google screen put the second i pressed the power button it shut off again. I just got this phone back a week ago from getting the battery replaced now this happens. Weird thing is when i checked my warranty status for the battery replacement it said i was up 1/26/17. Now when i check it says im under warranty until 4/3/17. not complaining about adding on warranty time but i just found that odd
I dropped by phone 3 feet in a case on Sunday. the screen popped out about the width of length of a credit card on the button side. I snapped it back in. It worked until yesterday. My alarm when off to wake me up. It would not turn off and the vibrator was at least 100%, louder than normal. I held power to restart and it boot looped. I flashed 3 different factory images and no joy. I did 6.0.0 the very first image, and the last two January images. I suspect that this issue is a mechanical/electrical issue where the phone is not receiving enough amps/volts to complete the boot, since the bootloader and recover use much less power they still work. By mechanical i mean battery damaged or connections damaged/degraded. kind of like when you corrode the poles on your car battery. With in mind I got the phone in august 2016. week 1 I dumped a glass of water on the phone. Maybe corrosion on the battery terminals. Just a thought.
Good morning all,
my 6p looks completely dead. I've installed the latest Android O factory image from the Google Developer site, flashed it and was running withot issues until today.
I was about to write a comment on Facebook, and then the phone freezed. After seeing how the phone was not recoverying, I tried a hard reset by long-pressing the power and both the volume keys. Then, the phone got a black screen, didn't vibrate, and now looks totally dead.
It's not charging or responding in any way, no matter how I press it. I'm quite confident the phone was over 50% when this issue occurred.
I don't really know what coul've caused this, but on my side, the preview was flashed cleanly with a complete factory reset, and I've only restored media files, without rooting.
Any ideas as to what should I do?
Do you get anything showing up on a computer when you plug it in?
jmaclean62 said:
Do you get anything showing up on a computer when you plug it in?
Click to expand...
Click to collapse
Hi jmaclean, nothing, not even in Windows Device Manager...
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Zwitterion said:
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Click to expand...
Click to collapse
Yes a bad choice I would say - as an owner of a Nexus 6P device currently awaiting repair (thank god I'm in warranty) - I can tell you this device is plagued with issues that only become apparent as soon as your warranty is approaching expiry.
I love the phone, the design and build quality aesthetically speaking but would never be buying from Huawei again. The device is plagued with poor design that people believe leads to the CPU failing for some odd reason causing the dreaded bootloop issue.
My phone died literally in front of me and never worked again. I've contacted Huawei to get some clarification if this is an inherent fault as thousands are complaining about it and they just plain deny it and maintain if the warranty expires your out of luck. Apparently fixing the bootloop requires a motherboard change which in itself costs over $200 apparently. May as well get another phone for that as even the replacement component will eventually fail!
Sounds like a power issue. Maybe there's an open at the power switch or bad battery connector or battery. It most likely is nothing to do with Android oh it's just a coincidence. If you would have not even flashed Android O it would have still done this
seems like you will need to open up your nexus and unplug the battery, and then put everything together and try
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
paracha3 said:
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
Click to expand...
Click to collapse
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
murphyjasonc said:
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
Click to expand...
Click to collapse
Yes I was able to apply that and got it to work. Thanks
My nexus 6p suddenly won't start, I've had my phone since May 2016 so more than a year now.
I've flashed a custom ROM onto it, I'm sure this isn't a software issue because it's been running fine since I bought it (and flashed it) and I followed all the instructions correctly.
I've read through this thread and tried the solutions there, hold the power button for longer than usual (a few minutes), hold the volume down button and power together, hold the volume down button then charge it, now hold the power button. I tried all 3 solutions which worked for many in that thread, but not me.
This all started 2 days ago, with no changes software-wise and using the same configuration as when I first flashed it, I opened the app HERE Maps and then my phone froze, totally stuck and unresponsive, restarting was no good, I had to go into TWRP and wipe the cache and dalvik cache, and it booted fine.
Today, same thing, I opened up HERE Maps and it got stuck again, I now notice that it takes longer than usual to start up via the power button, and wiping the cache and dalvik cache does not work anymore, it stucks on boot.
Now, my phone is not able to start at all. I think this is a hardware-related issue.
So quick recap:
1. Opened HERE Maps and gets frozen
2. Wiping cache and dalvik cache no longer works, stuck on boot.
3. Phone not able to start at all.
I am out of warranty period-wise, but I also custom it, so obviously my warranty is out the window. I need some insight from you guys here at XDA before I buy another costly phone.
someRandomSamaritan said:
...Now, my phone is not able to start at all. I think this is a hardware-related issue...
Click to expand...
Click to collapse
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
v12xke said:
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
Click to expand...
Click to collapse
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Can you access recovery or bootloader mode?
If within warranty, contact google/Huawei depending on where you purchased the phone from.
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Is it recognized at all when you plug a data cable to your PC? Your phone may be stuck in Qualcomm's EDL mode. Search.
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
Click to expand...
Click to collapse
This is a possible option..I'll try that tomorrow when it's morning
Anything else I could try? I think the most obvious methods are not available for me with this kinda situation
someRandomSamaritan said:
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
Click to expand...
Click to collapse
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
v12xke said:
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
Click to expand...
Click to collapse
Okay, this is helpful, you guys seems to think it is in EDL mode (which I haven't heard of until now), I'll try this and hopefully a driver loads or something
EDIT: nope, no drivers are loading, doesn't seem to be anything new in device manager, no device plug in sound, how sure are you that I'm in EDL mode?
It did work a few times yesterday (being able to boot into TWRP and wiping cache and dalvik cache), but now I'm not so lucky, it doesn't work anymore. I don't believe my phone is completely dead for some reason, I still do believe it can be saved. Hopefully I'm right :|
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
someRandomSamaritan said:
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
Click to expand...
Click to collapse
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2. They have project treble.
Your issue is different than most others. Most n6p with issues are bootlooping devices.
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
BadBoy2K7 said:
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
Click to expand...
Click to collapse
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2.
Click to expand...
Click to collapse
Pixel 2 is some expensive thing, out of my budget
someRandomSamaritan said:
Pixel 2 is some expensive thing, out of my budget
Click to expand...
Click to collapse
Then you should look for alternatives. Perhaps OnePlus 5T, etc.
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
someRandomSamaritan said:
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
Click to expand...
Click to collapse
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
I was facing bootlooping problem with my Nexus 6P and bootloader was locked so was unable to flash ROM by any mean.
So I tried following few threads and did "fastboot continue" and my device is not showing any sign of power since then. When connected to PC then no USB connection is there.
Is there any suggestions that can solve issue?
someRandomSamaritan said:
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
Click to expand...
Click to collapse
No. Unfortunately this happened to me last month and ive had the phone for almost 2 years now. Its sad because others are having the same issue and I think the hardware is faulty
I just called up a local phone repair and they said from their experience of repairing nexus 6p phones, most (if not all) of them had dead motherboards. The technician told me to get a new model of a phone and skip the 6p as it is a poorly built phone.
I consider saving up for a pixel..
NoobInToto said:
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
Click to expand...
Click to collapse
Ive heard of people baking motherboard on Nexus 5x and many other phones to reflow the solder.