Related
Last night my phone went dead. When I plugged it in. I saw the Goggle words on the screen, like when the phone is booting up from being off power. this stayed on for several seconds, then it flashed off and nothing all night. The led light was flashing on and off for a bit, but nothing. I couldn't turn it on then.
Then this morning, I was able to hold the power button and then the Google showed up for a few seconds, then nothing. I have tried holding down the power button for 10 sec to no avail, holding the power and vol down, nothing. Is there any other way to reset this or is the battery or something else on it dead and it needs to be returned to Google. Any and all help is welcomed.
Right now I have it plugged into the google cord and plug, not seeing the led light.
Good news: You're not the only one this is happening to.
Bad News: Not really a good solution yet.
Android Authority is covering it. There's some discussion in their comments.
I tried going into recovery and factory reset/wipe cache and that did nothing. Apparently some people have had luck flashing an older release, but I wasn't able to get anywhere close to that. I ended up calling calling the Google Hardware Warranty Center and they're sending me a replacement.
If bootloader is unlocked, I will be able flash factory image to fix this?
I haven't rooted the phone. It is just the basic android. I'm on with Google support right now. They are going through all the things that I have already done.
I can't get to the bootloader. The phone is off / dead right now. Once it turned off last night, I haven't been able to get it to power up again.
Google wanted me to put it on their cord and charge for an hour to see if anything changed. Hoping it works. I have to travel this weekend, and he was saying it could take up to 7 business days to get a new phone.
No power after 2 1/2 hours on the google cord. Guess to get a replacement.
hope you have a backup phone to use.
I have an iphone 5 I use for Ipod. Would it be too much work to use this until I get the other one, or will it probably not have the right sim card?
I'm in the same boat too. Google sent me out a warranty replacement. Mine just crashed when making a call and it would no longer power on after that. The only thing it would show when plugged in to my computer was Qualcomm downloader for USB.
When I updated to Nougat, I now get the screen that says Firmware Update with a message telling me to keep it plugged in. It's been at 0% for a few hours. Rebooting the phone results in the same thing. Phone's not rooted or anything. Guess I have a brick now.
90s
Sent from my Nexus 7 using XDA-Developers mobile app
There are lots of reports that nexus5x die after the nougat update
I got it to boot up last night, and I was able to get it to recovery mode, then tried to reboot, but nothing else. I'm contacting Google again to get the warranty started.
Just ordered a replacement, bummer that it is a refurb, not new, but sometimes the refub units are tested more than new. Is there any way that I can ensure that the data on the phone won't wind up in the wrong hands after it is fixed by Google and sent out, or is it just a roll of the dice?
They said they were sending me a refurb but its was a brand new one. It came in a retail box. Wondering if they ran out of refurbs with all the people having issues.
So I have the refurb unit at home. It is asking to update to nougat. Are the software updates safe enough to put on the phone. Mine is just stock not rooted.
Can't wait. I've been limping by on the iPhone 5.
Sent from my iPhone using Tapatalk
Mine died, LG told me to send it to them for repair, but only have me a FedEx ground, would have liked more like Air delivery for faster processing
Been using my 5x for 18 months or so, standard Android 7.1, etc. Pulled it out of my pocket a couple hours ago and it is totally dead! Had about 75% battery when last used.
I'm unable to get any response out of it, no charging indicator, power + volume keys doesn't work. Just totally dead.
Any ideas? Will Google replace it for a fee? I'm on a trip for another few days and will really miss it -- hope I don't need it for something important.
Sent from my SM-T700 using Tapatalk
Same happened to me while ago. But still no luck with this. To fix I believe I need access to boot menu which I couldn't
Update: For some reason, I was able to get into the initial screen that you get by holding power and volume down. However, none of the three options work from there. All I get is a Google logo for several second and return to darkness.
Sent from my SM-T700 using Tapatalk
You can read about Nexus 5X bootloop on this forum. Its a hardware problem.
Sent from my Nexus 5X using Tapatalk
shut_down said:
You can read about Nexus 5X bootloop on this forum. Its a hardware problem.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Aargh! I was afraid that might be the problem.
Sent from my SM-T700 using Tapatalk
rochrunner said:
Aargh! I was afraid that might be the problem.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
my nexus 5x is going to die . i opdate it too android 8 and work with telegram . then it turn off and is not turn on . after 1 day when press power key the notification light is turn on. i cant go to recovery or downloaD mod . please help me
Mine did this exact thing and it was the bootloop problem, though it didn't bootloop. It acted like yours did.
Your best hope if you're going on a trip soon, is try the method that turns off the big cores. If you don't have an unlocked bootloader, try putting it in the freezer or an ice bath, and maybe it'll boot long enough to unlock the bootloader. Mine would get into recovery using that method so I could wipe the cache and adb the OTA. It also tried to boot longer, but never would boot.
All the phones act differently and you may get lucky.
Mine never booted until I used a hairdryer on the motherboard. But it immediately froze after booting. Then actually did start bootlooping. Only using a heatgun got it to boot where I could pull my data off of it. But it died relatively quickly. Then I got it to act normal for 9 hours after using a heatgun at higher temp. After that I could heatgun it again and get it to boot, but it would very quickly die again. The fix that turns off the big cores was not out then, so I don't know if it would have fixed it.
Voicebox said:
Mine did this exact thing and it was the bootloop problem, though it didn't bootloop. It acted like yours did.
Your best hope if you're going on a trip soon, is try the method that turns off the big cores. If you don't have an unlocked bootloader, try putting it in the freezer or an ice bath, and maybe it'll boot long enough to unlock the bootloader. Mine would get into recovery using that method so I could wipe the cache and adb the OTA. It also tried to boot longer, but never would boot.
All the phones act differently and you may get lucky.
Mine never booted until I used a hairdryer on the motherboard. But it immediately froze after booting. Then actually did start bootlooping. Only using a heatgun got it to boot where I could pull my data off of it. But it died relatively quickly. Then I got it to act normal for 9 hours after using a heatgun at higher temp. After that I could heatgun it again and get it to boot, but it would very quickly die again. The fix that turns off the big cores was not out then, so I don't know if it would have fixed it.
Click to expand...
Click to collapse
I was on a trip when it happened, but miraculously survived without access to Google Maps, SMS, FB, etc. Returning home, I was very impressed with Google support. I put in for a callback on my home phone, received a call in less than a minute, and they are replacing my phone (with a refurb) free as a "warranty extension" (phone about 18 mos. old). So I should be back in business in a couple days. In the meantime, I'm finding it kinda liberating to not have to be carrying the phone around, remembering to put it on the charger, etc.
rochrunner said:
I was on a trip when it happened, but miraculously survived without access to Google Maps, SMS, FB, etc. Returning home, I was very impressed with Google support. I put in for a callback on my home phone, received a call in less than a minute, and they are replacing my phone (with a refurb) free as a "warranty extension" (phone about 18 mos. old). So I should be back in business in a couple days. In the meantime, I'm finding it kinda liberating to not have to be carrying the phone around, remembering to put it on the charger, etc.
Click to expand...
Click to collapse
Yeah, they replaced mine at 14 or 15 months in. By then it was such an issue that the tech guy didn't even bother making me do all the troubleshooting steps before he said he was handing me off to the guy to set up the replacement.
Mine just did this to me. It's my second 5X and this time nearly 6 months elapsed before it died so I couldn't use the Amazon return process (my first one started bootlooping in less than 2 weeks).
Had the phone 100% charged, slipped it into my pocket, took it out during lunch and it refused to boot. Can't even get into recovery.
I'll put it into my freezer tonight to see if I can at least get it to boot long enough for me to retrieve a few photos that I hadn't backed up in the cloud.
I wonder if my frequent use of the phone as a car GPS contributed to this. My friend's 5X has not crapped out on him since he bought it in 2015...
Google Pixel, here I come!
Edit: Freezer worked, and in fact the phone is still alive, but I'm not cancelling my Pixel order regardless
machoman1337 said:
Mine just did this to me. It's my second 5X and this time nearly 6 months elapsed before it died so I couldn't use the Amazon return process (my first one started bootlooping in less than 2 weeks).
Had the phone 100% charged, slipped it into my pocket, took it out during lunch and it refused to boot. Can't even get into recovery.
I'll put it into my freezer tonight to see if I can at least get it to boot long enough for me to retrieve a few photos that I hadn't backed up in the cloud.
I wonder if my frequent use of the phone as a car GPS contributed to this. My friend's 5X has not crapped out on him since he bought it in 2015...
Google Pixel, here I come!
Edit: Freezer worked, and in fact the phone is still alive, but I'm not cancelling my Pixel order regardless
Click to expand...
Click to collapse
hi, i got the dead nexus5x too
How long you putted in the freezer?
After freezing event, phones works as usual? or it worked a few ours, than dead?
Thank you.
maltinbay said:
hi, i got the dead nexus5x too
How long you putted in the freezer?
After freezing event, phones works as usual? or it worked a few ours, than dead?
Thank you.
Click to expand...
Click to collapse
1 hour. It works as usual. Hasn't died since I took it out, but I'm not getting my hopes up.
hey guys - I'm troubleshooting this device for a lady friend - this exact thing just happened to her haha she's running all stock everything, I was able to get to the default bootloader/choose recovery etc screen but when I selected recovery, like you all, it just bootlooped a couple times, then played the entire boot animation, then died again...
if I do this freezer thing, can the wug's toolkit aid me in flashing some custom stuff to make it a little easier to mess around with? i.e. put on kernel adiutor and turn off the big cores like someone mentioned?? anyone know the thread where I could root purely from bootloader screen + computer? the toolkit seems to require normal access to the OS to function, right?
thanks in advance
machoman1337 said:
Mine just did this to me. It's my second 5X and this time nearly 6 months elapsed before it died so I couldn't use the Amazon return process (my first one started bootlooping in less than 2 weeks).
Had the phone 100% charged, slipped it into my pocket, took it out during lunch and it refused to boot. Can't even get into recovery.
I'll put it into my freezer tonight to see if I can at least get it to boot long enough for me to retrieve a few photos that I hadn't backed up in the cloud.
I wonder if my frequent use of the phone as a car GPS contributed to this. My friend's 5X has not crapped out on him since he bought it in 2015...
Google Pixel, here I come!
Edit: Freezer worked, and in fact the phone is still alive, but I'm not cancelling my Pixel order regardless
Click to expand...
Click to collapse
WTF!!!!!!! My ****ing dad's nexus died! WTFFFFFFFFFFFFFFFF!!!!! **** YOUR UGLY BODY!!!
purplepenguin said:
hey guys - I'm troubleshooting this device for a lady friend - this exact thing just happened to her haha she's running all stock everything, I was able to get to the default bootloader/choose recovery etc screen but when I selected recovery, like you all, it just bootlooped a couple times, then played the entire boot animation, then died again...
if I do this freezer thing, can the wug's toolkit aid me in flashing some custom stuff to make it a little easier to mess around with? i.e. put on kernel adiutor and turn off the big cores like someone mentioned?? anyone know the thread where I could root purely from bootloader screen + computer? the toolkit seems to require normal access to the OS to function, right?
thanks in advance
Click to expand...
Click to collapse
I believe you should be able to get the phone to stay alive long enough to do everything you mentioned, after a freezer treatment.
In my case, the phone has actually stayed alive continuously after the freezer treatment but I'm not getting my hopes up.
Alex Wood said:
WTF!!!!!!! My ****ing dad's nexus died! WTFFFFFFFFFFFFFFFF!!!!! **** YOUR UGLY BODY!!!
Click to expand...
Click to collapse
lolwut?
Same things happened to my phone...it was 50% charged and all of sudden... The phone went off...still trying to find out....
Just happened to me.
Phone died while in standby on my desk, black screen and no luck booting or anything. I was assuming the worst, it's been only 1 year since i bought it.
I dig out my screwdrivers kit, removed the back cover and disconnected the battery. After a few minutes i reconnected it and the phone was alive and kickin' again. No bootlop whatsoever.
Now it's working fine, i hope it keep doing that for long time. @machoman1337 yours is still fine or died again?
Thanks
.bucch said:
Just happened to me.
Phone died while in standby on my desk, black screen and no luck booting or anything. I was assuming the worst, it's been only 1 year since i bought it.
I dig out my screwdrivers kit, removed the back cover and disconnected the battery. After a few minutes i reconnected it and the phone was alive and kickin' again. No bootlop whatsoever.
Now it's working fine, i hope it keep doing that for long time. @machoman1337 yours is still fine or died again?
Thanks
Click to expand...
Click to collapse
I bought a Pixel so I haven't tested my 5X since my black-screen happened. It's still in my drawer.
machoman1337 said:
I bought a Pixel so I haven't tested my 5X since my black-screen happened. It's still in my drawer.
Click to expand...
Click to collapse
Oh, I see. Thanks anyway.
I'll see for myself.
there's a nexus 5x extinction in progress
there we'll be no nexus 5x alive in a while
having nothing but rubbish in your hand after 2-3 years is not a pleasure and this is a shame for lg
Hello
My Nexus 5x 16 GB (LG H791 ) got the bootloop, i need to fix my phone !
Soo yesterday was a very hot day.
I ran around a bit outside and took a lot of pictures. But it was very hot outside. Whenever I take pictures, HDR has to be rendered first, it consumes a lot of power and I can imagine that the Nexus 5x gets hot. When I put it in my pocket, it still worked. After I got it out again, the screen was completely black and it could not boot anymore. It was just black, nothing worked.
Later, I went home to look at the Nexus 5x.
I looked at whether it was possible to get into fastmode, dloadmode and recoverymode, but the screen remained black.
I've fixed other cell phones before, but with the Nexus 5x, I still have some little hopes.
I opened the nexus and cleaned it completely with 100% alcohol. Every corner and every connector.
After cleaning I switched it on again and suddenly it started again.
But it only showed the colorful google animation and it restarted after a short time and it repeated itself endlessly.
From there I noticed that it is the well-known bootloop problem.
I knew before that it will eventually come to this problem, so I unlocked my OEM (Bootloader) about 1 year ago :good: !
So I googled and there seem to be some fixes !?
First of all, I tried THIS and it didn't help
I tried also from this solution the TWRP recovery. Jeah i got in to the TWRP recovery and installed the EX4_10_5X.zip, but with some errors. The Nexus is still repeating... BUT!! The google logo animation was stuck, no animation!
Soo I googled more and more and saw a new solution!
THIS! So i did all 4 stepts expect step 1, because it's already unlocked.
JEAH! My Nexus 5x seems to be ok again ! After I set everything up, the Nexus 5x has frozen and crashed ! Man damn!! I was sooo happy..
Then i tried to flash the latest factory image from https://developers.google.com/android/images?hl=en#bullhead
I ran the "flash-all.bat", got no problems the first time, but the Nexus is still bootlooping :/
So i flashed it again with a factory image from 8.1.0 (OPM1.171019.011, Dec 2017).
But this time the Nexus has freezed and turned off!
It restarted by itself, but there was no Google logo anymore. It restarted each time after the message came that the Nexus is unlocked.
If I go into fast mode, it freezes after a short time, it is not possible to flash an image on it, because after a "fastboot reboot-bootloader" command, the Nexus just stops responding, so I have to disconnect the battery.
If I reconnect the battery immediately, the screen will still be black.
So I always have to wait 3 minutes until I can connect the battery again. This is exactly as with a USB-C cable.
I got one time a crash or greenscreen !
I saw a thread about (BLOD).
I downloaded the latest fix files. After i got really quick into the fastboot mode, i flashed this two things and jeah i got my google logo back, but it still freezes and it won't turn on, only if I reconnect the battery after some minutes.
Now my problems:
No Google logo (Rare)
It stays off after it freezes
It's hard and randomly that I get into the recovery mode with TWRP. If I make it, the nexus freezes again
I can not flash an image because the screen stays black every time I restart
I can't fix it, i need your help ! Pls
Community ? Can you help me ?
@MrClean24, I'd say goodbye: even if you succeed to make it run with sleeping cores, it's slow and wont be stable.
rp158 said:
@MrClean24, I'd say goodbye: even if you succeed to make it run with sleeping cores, it's slow and wont be stable.
Click to expand...
Click to collapse
Man damn, it don't wan't to give it up
@MrClean24, a new mainboard?
rp158 said:
@MrClean24, a new mainboard?
Click to expand...
Click to collapse
That was my first idea, but i don't wan't to use any money for this phone
If it can't be fixed, then i will buy a Pixel 3a phone.
@MrClean24, good idea (I'm not favouring bin generally, but you wont fix damaged hardware by software plasters durably)
Jeah its a hardware problem :/ I think mine can't be fixed anymore, but thanks
Join the club
My old n5x is death with that problem
My old Nexus 4 have the same problem too
2 Nexus deaths ??
in 2018 I bought a pixel 2 xl and is a great machine
manfio said:
Join the club
My old n5x is death with that problem
My old Nexus 4 have the same problem too
2 Nexus deaths ?
in 2018 I bought a pixel 2 xl and is a great machine
Click to expand...
Click to collapse
Can't wait 4 my pixel 3a
My Pixel XL just took a crap this morning. It was working as expected early on. A bit later I could not access the internet despite showing a pretty strong lte connection. I didn't think much of that because it's not unheard of for service to not reflect the indicator. I was listening to a podcast and it just died. Went into an endless boot loop. It has had a steady decline in how far it will boot. I once got into TWRP but it crashed shortly after and once got to the login screen, again, crashing before I could login. Now it doesn't get past the google screen.
I have tried flashing the stock image from the bootloader as well as trying to fastboot twrp and neither go well. The flashing "works" but doesn't boot. Fastboot doesn't give an error but the phone just bootloops.
As it sits the bootloader is unlocked (not sure it matters at all).
At this point I have already bought a new phone but am considering trying to fix it to have a backup if I can get an idea of where to start or what it would cost to send in.
Any advice or help would be appreciated.
This sounds really similar to what I had happen after a while with my first Pixel XL. I tried to document everything HERE.
Wiping dalvik cache through TWRP seemed to be a short term fix (daily), but even that eventually stopped working. I ended up being able to jump into an "open enrollment" period for adding insurance for the phone with Verizon and then was able to use their extended warranty system to get a replacement phone (which was confusing since they said it was not an insurance claim since it appeared to be a phone defect out of my control, so I'm not 100% sure I even needed the insurance? Your mileage may vary.) The replacement was a refurb but has worked perfectly ever since I got it. They still had them in stock at the time or else I'd have tried to push for a 2 (or maybe now push for a 3 or 3a?). Good luck!
just went through the same thing. research shows it was most likely a known motherboard issue. its out of warranty so i bought a used one on swappa for 80 bucks and then sold my non functioning one at an ecoATM for 30 bucks. so im only net -50.
tgumina said:
My Pixel XL just took a crap this morning. It was working as expected early on. A bit later I could not access the internet despite showing a pretty strong lte connection. I didn't think much of that because it's not unheard of for service to not reflect the indicator. I was listening to a podcast and it just died. Went into an endless boot loop. It has had a steady decline in how far it will boot. I once got into TWRP but it crashed shortly after and once got to the login screen, again, crashing before I could login. Now it doesn't get past the google screen.
I have tried flashing the stock image from the bootloader as well as trying to fastboot twrp and neither go well. The flashing "works" but doesn't boot. Fastboot doesn't give an error but the phone just bootloops.
As it sits the bootloader is unlocked (not sure it matters at all).
At this point I have already bought a new phone but am considering trying to fix it to have a backup if I can get an idea of where to start or what it would cost to send in.
Any advice or help would be appreciated.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/gsi/Pixel/Pixel-AB-11-20200909-ErfanGSI.img-0125.7z
↑extract and fastboot flash this
so I woke up this morning and the phone was off, i tried to turn it on with no luck. Plug in the original OEM charger and been getting stuck in bootloop.
tried to follow recovery mode but everytime i get to the "fastboot" screen and try to toogle the menu, the phone reset back to the "Google" logo....so now i can't even enter recovery mode to side load. have anyone run into this issue before? and what is the solution?
thanks
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
lpiratel said:
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
Click to expand...
Click to collapse
Are you BL locked or unlocked? If unlocked, you can at least try installing the factory image (with or without the -w) and see what it does.
sliding_billy said:
Are you BL locked or unlocked? If unlocked, you can at least try installing the factory image (with or without the -w) and see what it does.
Click to expand...
Click to collapse
unfortunately, BL is locked and I can't do anything that I know of on my end. Time to go back to my back up oneplus 3T
lpiratel said:
unfortunately, BL is locked and I can't do anything that I know of on my end. Time to go back to my back up oneplus 3T
Click to expand...
Click to collapse
Can you see the device in Fastboot with fastboot devices from a command prompt? Are you locked and not unlockable (Verizon) or just not unlocked? If just not unlocked you could try unlocking the BL (assuming you had at least toggled OEM Unlocking in developer settings)? I don't know if the command works on a locked BL (I suspect it doesn't, but it is worth a try), but fastboot reboot fastboot would get you to fastbootd where you can do ADB sideload.
sliding_billy said:
Can you see the device in Fastboot with fastboot devices from a command prompt? Are you locked and not unlockable (Verizon) or just not unlocked? If just not unlocked you could try unlocking the BL (assuming you had at least toggled OEM Unlocking in developer settings)? I don't know if the command works on a locked BL (I suspect it doesn't, but it is worth a try), but fastboot reboot fastboot would get you to fastbootd where you can do ADB sideload.
Click to expand...
Click to collapse
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
lpiratel said:
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
Click to expand...
Click to collapse
Suggestion: Call Google support
lpiratel said:
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
Click to expand...
Click to collapse
Homeboy76 said:
Suggestion: Call Google support
Click to expand...
Click to collapse
Same suggestion as Homeboy at this point. Sorry.
lpiratel said:
so I woke up this morning and the phone was off, i tried to turn it on with no luck. Plug in the original OEM charger and been getting stuck in bootloop.
tried to follow recovery mode but everytime i get to the "fastboot" screen and try to toogle the menu, the phone reset back to the "Google" logo....so now i can't even enter recovery mode to side load. have anyone run into this issue before? and what is the solution?
thanks
Click to expand...
Click to collapse
They will rma it, I had a similar issue on my pixel 2 (slot unbootable load error) and they shipped me once right away.
lpiratel said:
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
Click to expand...
Click to collapse
This just happened to me yesterday. Plugged my Pixel 3 XL in to the wall charger and it immediately went into a bootloop. Nothing would stop it as if it were a hardware issue. Tried to boot into recovery and fastboot but it would immediately bootloop again. Eventually after the battery died I was able to start it up and get it working again. My issue now is that I'm worried it will happen in the future. Didn't plan on upgrading but might have to move to the 4 XL as I use this phone for work.
holy crap - this happened to my wife's phone last week. We ended up getting a Pixel 3A XL for her.
She plugged in her 3XL at around 10% and it started boot looping. I couldnt' do anything with it. The only way I could try and keep it on is blasting it with a flipped can of CO2. I tried everything from factory reset to reflashing. Finally I gave up, and let it sit for a week. Started the phone, and it stayed on for 3 days and let the battery drain again to 10% - plugged the phone it and it started bootlooping again. I'm wondering if the battery just gave out. I wonder if we can see if there is some manufacturing correlation here, maybe all of our phones came from the same batch. I ended up buying in Nov 2018 for Black Friday sale.
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
hazeem96 said:
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
Click to expand...
Click to collapse
I'd simply try to get support for this, it looks like the next big flaw and is likely class action lawsuit material, assuming hardware failure can be proven - to which I have not a single doubt in my mind, from reading alone the reports a few red flags can be seen instantly!
From not being able to reach fastboot or get past Google logo it appears to be the UFS storage chip that went bad! However it also seems that there's a relation to the charging mechanism, potentially involving the battery itself..
I think we'll start to see more an more reports about this flaw the next month, I hope not but after all Google released to the public on hardware level alone I wouldn't be surprised either - don't get me wrong, I love their devices and most Nexus and Pixel in daily use, I wouldn't even consider switching to another brand as love those devices to much but after all the years I also know that Google doesn't always execute their plans well on hardware level! Their 'lemon count' is statistically higher than elsewhere!
Good luck everyone, I'm definitely keeping an eye on this thread and issue!
Sent from my Google Pixel 3 XL using XDA Labs
This *just* happened to me, too! Happened at 330pm EDT right before I had a meeting, so I had to quickly swap the sim into another phone. I'm also out of warranty, and the fact that there are a number of us reporting this same issue in a quick span of time leads me to think this is something on Google's end
Sam Nakamura said:
I'd simply try to get support for this, it looks like the next big flaw and is likely class action lawsuit material, assuming hardware failure can be proven - to which I have not a single doubt in my mind, from reading alone the reports a few red flags can be seen instantly!
From not being able to reach fastboot or get past Google logo it appears to be the UFS storage chip that went bad! However it also seems that there's a relation to the charging mechanism, potentially involving the battery itself..
I think we'll start to see more an more reports about this flaw the next month, I hope not but after all Google released to the public on hardware level alone I wouldn't be surprised either - don't get me wrong, I love their devices and most Nexus and Pixel in daily use, I wouldn't even consider switching to another brand as love those devices to much but after all the years I also know that Google doesn't always execute their plans well on hardware level! Their 'lemon count' is statistically higher than elsewhere!
Good luck everyone, I'm definitely keeping an eye on this thread and issue!
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Since my original reply to this post, it has happened a couple of more times on my phone. Both times I've noticed the phone gets extremely hot but as soon as the battery dies and the temperature cools for a while, the phone will power back on. My uneducated guess is that something in the processor or battery connection is causing the phone to overheat. Excuse the layman's terms lol.
I too have been a big fan of the Nexus and PIxel lineups over the years but my reason for upgrading to the newer model was always because my old phone had some sort of hardware defect. Galaxy Nexus microphone died, Nexus 6P wouldn't power on, OG PIxel bootlooped. Pixel 2 XL had screen issues. Pixel 3 XL, here we are now lol. Each one lasted me at least over a year and the software is unmatched in my opinion. I'm proud of how far they've come with software, hardware and camera. I just wish they'd put a little "oomph" in their quality control department.
Google doesn't help with bootloop
hazeem96 said:
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
Click to expand...
Click to collapse
----------------------------------------
I bought my Pixel 3 XL November 2018 from the Google Store.
The phone has been great, but the bootloop started happening with me 4-5 days ago. I had to buy a new phone (yes, I'm stuck in the modern world, unfortunately. i need a phone)
Recovery buttons get to a menu...and then back to the bootloop within 2 seconds, There was little time to press volume buttons etc and no response when I do so on this screen, other than the dead Android with it's hatch open.
But no matter what I do - it goes back to the bootloop within a few seconds.
I spoke w rep from Google for 40 minutes or so, I was polite. No help; he said he could not send me a new or renewed device. he suggested repair shops. Which....the shop told me they do not deal with bootloops, "probably a hardware issue", he said.
So...idea....use my credit card extended warranty! But....for this purchase, strangely...I used PayPal. ughhhh!
Disapointing. Not quite 2 years out of my Pixel, and I was hoping to capitalize on the resale / trade-in value. Not possible now, even a trade in requires a factory wipe.
I did think of using ADB / fastboot, but I do not have time to futz around right now.
You could try Google, but...if you are out of warranty, it is unlikely they will help. Did you buy it with a credit card w extended warranty?
good luck
this just happened to me google is saying that because the phone is out of warranty (by 8 months)
there is nothing they can do about it
at least I have the extended care