Pixel XL turned into a brick?

[bounddyy]

1. This phone's been babied no damage.
2. Never rooted or any kind of tweaking, only basic usage.

Now it gets stuck on boot and even if I try to hard reset once I tap the button to get into recovery it just flashes the Google start up logo. I can never get to the "no command" part. Besides that it does nothing but turn on stay stuck on boot (Google logo).

 

[ferydaboss]

same here :/ any updates?

 

[godkingofcanada]

its not a brick. if this issue is affecting several people, someone at xda will figure it out, or google themselves will notice and fix it. I contacted google about it and let them know that ive seen several users reporting the same issue. i'm also trying different things on my end, but without being able to sideload zips or get into twrp its difficult. I cant even tell if the memory is encrypted or not. and fastboot has no diagnostic tool for me to run a hardware test, however I cant see all of our devices working fine one day and randomly breaking the next...

---------- Post added at 05:10 AM ---------- Previous post was at 05:09 AM ----------

it seems the last update or two did something and flashing different boots and stock images is not overwriting whatever is wrong, almost as if it was an update to something that can't be rolled back. if thats the case we will need another update that corrects the issue, since we can't manually reverse it.

 

[ferydaboss]

its not a brick. if this issue is affecting several people, someone at xda will figure it out, or google themselves will notice and fix it. I contacted google about it and let them know that ive seen several users reporting the same issue. i'm also trying different things on my end, but without being able to sideload zips or get into twrp its difficult. I cant even tell if the memory is encrypted or not. and fastboot has no diagnostic tool for me to run a hardware test, however I cant see all of our devices working fine one day and randomly breaking the next...

---------- Post added at 05:10 AM ---------- Previous post was at 05:09 AM ----------

it seems the last update or two did something and flashing different boots and stock images is not overwriting whatever is wrong, almost as if it was an update to something that can't be rolled back. if thats the case we will need another update that corrects the issue, since we can't manually reverse it.

so... Google knows about the issue, ok. But how will that help, to a whaetver person like me, that has NO google shops to RMA, or bring them to fix it to?

Are you saying that they will patch an OTA, so that we can sideload it? i can enter recovery mode, after letting the phone stay in Power Off mode a few hours. Tried resetting multiple times.

 

[C4rb0nf00tpr1nts]

I have a similar situation.
Pixel XL on charge, went out for 10 minutes, came back, pick up phone, power button unresponsive...
I did have all the preps for rooting (OEM unlock turned on, developer mode enabled, USB debug etc...) because I was going to try some custom ROMs.
"fastboot oem unlock" returns "FAILED (remote: 'oem unlock is not allowed')"
My whole life is in that damn expensive paperweight... I am in serious trouble (medical reasons, daily notes stored on phone) if i can't even simply recover user data.
Any ideas? anyone? help... please

 

[godkingofcanada]

I'm on the phone with google software development

 

[godkingofcanada]

No luck. Toasted or repair. They said the mobo

 

[ylapas]

Sorry to hear that. Just curious - how old the device was, maybe you have a manufacturing date? Have you used the genuine USB C PD charger, or used third party chargers? Just don't understand how motherboard dies so frequently for first gen.

 

[CapoJoel]

Mine died this morning when I went to check the weather. An update had apparently installed overnight, nothing else was out of the ordinary. It froze and I hard powered it off. I haven't had any signs of life since. It is listed as "Qualcomm-HS-USB QDLoader 9008" when I try to plug it into my computer (no access, just listed as a connected device.) Mine was a 128gb variant, carrier unlocked, never rooted/etc., only used with official charger & usb cable. I don't have the mfg date unfortunately.

I hope any of that info can prove useful, even if just to help establish a scope of the affected devices.

 

[jaytv]

I have a similar situation.
Pixel XL on charge, went out for 10 minutes, came back, pick up phone, power button unresponsive...
I did have all the preps for rooting (OEM unlock turned on, developer mode enabled, USB debug etc...) because I was going to try some custom ROMs.
"fastboot oem unlock" returns "FAILED (remote: 'oem unlock is not allowed')"
My whole life is in that damn expensive paperweight... I am in serious trouble (medical reasons, daily notes stored on phone) if i can't even simply recover user data.
Any ideas? anyone? help... please

Did you try the more current "fastboot flashing unlock" command? That is the correct one.

The problem is that will erase your user data partition.

Hopefully your notes were taken in Google Keep? If so, you can read them on any computer you can sign into with your Goodle account.

 

[C4rb0nf00tpr1nts]

Did you try the more current "fastboot flashing unlock" command? That is the correct one.

The problem is that will erase your user data partition.

Hopefully your notes were taken in Google Keep? If so, you can read them on any computer you can sign into with your Goodle account.

Sure did. Tried everything. Nothing will connect to the phone - only things that return a successful response are some of the fastboot commands (getvar all, device).
And due to having friends and colleagues that kept telling me to turn off all the "big brother" type of backup options I have nothing.
I can categorically state that I have nothing to hide from all the officious types that would be watching my every key stroke or phone entry and I will be turning on every backup or recovery option in future, whether or not I go back to the fragile device of a Google phone is to be decided if I myself decide to push on from this point at all...