Help: Pixel completely dead after the earpiece issues being fixed for almost one year - Google Pixel Questions & Answers

On a business trip in Dubai, the phone suddenly turns it off.
Now I am posting in the airport.
No response, cant turn on. tried whatever I can do.
can charge, but no flash sign.
connected to my laptop, no response
adb check ending up no devices.
Please someone help me figure this out.
Damn google, I have no backup phone, and use the phone to take pictures.
Will never use google phone again,

Are you able to boot into bootloader? Did you previously have USB debugging turned on?

can't boot into bootloader? and USB debugging enabled.
post-mortem said:
Are you able to boot into bootloader? Did you previously have USB debugging turned on?
Click to expand...
Click to collapse

Does fastboot devices find anything?

I don't think so. I tried adb devices, find nothing.
confirmed with a local engineer. the so called storage chip on the mainboard was broken. will try to find someone to replace it, then come here to update.
Damn google.
post-mortem said:
Does fastboot devices find anything?
Click to expand...
Click to collapse

bush911 said:
Damn google.
Click to expand...
Click to collapse
I guess you should blame HTC.

Related

USB port broken, unable to flash boot.bin

My phone died and requires me to flash boot.img in order to bring it back to Android. To my surprise, I couldn't get it to go, and after some testing it seems my USB port is having an issue where it won't connect data, but will charge. Both of my computers with seperate USB cords are stating that the USB device has malfunctioned. Does anyone know of a good solution? I know there are the pogo pins on the back, but I don't know if there is anything that connects to them or if they transfer data. Is my only option at this point looking for someone to do a USB port repair for me? Any ideas would be very welcomed. Thanks!
Not sure exactly what your problem is? Boot.bin? What exactly is that?
RollTribe said:
Not sure exactly what your problem is? Boot.bin? What exactly is that?
Click to expand...
Click to collapse
Probably boot.img
Sent from my HTC One XL using xda premium
serotoninzero said:
My phone died and requires me to flash boot.img in order to bring it back to Android.
Click to expand...
Click to collapse
Where is it now if not Android? There are only certain instances that the computer will recognize it. Try a different computer as well (fresh install of HTC drivers).
chris948 said:
Where is it now if not Android? There are only certain instances that the computer will recognize it. Try a different computer as well (fresh install of HTC drivers).
Click to expand...
Click to collapse
Sitting at the bootloader as well as TeamWin recovery usb mount. Both times comes up as USB device not recognized.
serotoninzero said:
Sitting at the bootloader as well as TeamWin recovery usb mount. Both times comes up as USB device not recognized.
Click to expand...
Click to collapse
You are trying to go into fastboot, right, and not just regular bootloader.

[Q] Cannot detect Nexus 5 except fastboot

So I've tried absolutely everything, new drivers, flash batch all newest firmware.. different computers, restarting computer..
whatever I do I cannot manage to get any computer to detect my Nexus 5 via adb or mounted storage.. the only thing that is detected is fastboot..?
any ideas??
Maybe it's a driver problem on your system. Did you try another computer?
What does device manager show? An unknown device connected? An acer device connected?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
What does device manager show? An unknown device connected? An acer device connected?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
nothing, nothing detected at all. but the USB port on the phone works fine because fastboot is working fine..
any idea's anybody? I've tired several computer with different windows versions.
This phone is absolutely undetectable by USB/ADB. It charges perfectly fine and fastboot works flawlessly...
You have an issue with the Nexus 5's driver and your adb driver, but not your fastboot driver.
Try uninstalling/reinstalling the drivers and use the 15-second adb/driver installer, if that doesn't work then try the universal naked driver.
Elluel said:
You have an issue with the Nexus 5's driver and your adb driver, but not your fastboot driver.
Try uninstalling/reinstalling the drivers and use the 15-second adb/driver installer, if that doesn't work then try the universal naked driver.
Click to expand...
Click to collapse
tried both, this phone isn't detected by any computer at all when it's switched on, zero. It doesn't show up as android, or acer or anything, there is no driver able to be installed because the phone isn't even detected by the computer unless I put it in fastboot mode.
omg, first the first time it just got magically detected in TWRP as ADB composite device. This is completely un-explainable, it's been days this was achievable..
restarted phone, impossible to detect again....
THE_KINGDOM said:
tried both, this phone isn't detected by any computer at all when it's switched on, zero. It doesn't show up as android, or acer or anything, there is no driver able to be installed because the phone isn't even detected by the computer unless I put it in fastboot mode.
Click to expand...
Click to collapse
You can still install/uninstall a driver if the device is not plugged in/detected as unknown device.
Have you tried manually reinstalling the driver?
Elluel said:
You can still install/uninstall a driver if the device is not plugged in/detected as unknown device.
Have you tried manually reinstalling the driver?
Click to expand...
Click to collapse
it's not detected at all thats what I'm trying to explain, it's not an unknown device, it's never detected at all
THE_KINGDOM said:
it's not detected at all thats what I'm trying to explain, it's not an unknown device, it's never detected at all
Click to expand...
Click to collapse
If you are certain it is an issue with the device and not your drivers, try booting up a Linux distro (Ubuntu will do) in a VM or directly off a USB stick, as it requires no driver installation in Linux to access the internal storage via USB.
Elluel said:
If you are certain it is an issue with the device and not your drivers, try booting up a Linux distro (Ubuntu will do) in a VM or directly off a USB stick, as it requires no driver installation in Linux to access the internal storage via USB.
Click to expand...
Click to collapse
it's strange because for the first time a few moments ago i was able to see the device in adb mode via TWRP, as soon as I restarted the phone it's impossible again, I've tried 20+ times since then.
only thing i can get repeatedly with no issues at all is the bootloader interface/fastboot
tried with linux, ubuntu. no connection.. But I already knew it wasn't drivers.. device isn't detected at all.. it's not like it's allocating the wrong drivers.. it's not even registering a usb device was connected to the PC unless in bootloader/fastboot.
Sounds like an issue with your usb cable or the phone side adapter. Have you tried ADB through a wireless connection?
[RANT ON]
I have already addressed your issue in this thread http://forum.xda-developers.com/google-nexus-5/help/diagnosing-usb-driver-adb-issues-windows-t2514396/post59570828#post59570828 and yet without so much as even a single reply or simple thank you for taking my time and telling you in detail how it is, you found it necessary to create a new thread? Are you hoping for a magic bullet?
What's even worse in my world. You offered not a single thank you to anyone here in this tread that completely wasted their valuable time trying to help you after you already have your answers.
I realize I am relatively new member here at XDA. But I've been lurking here for over 5 years. Forgive me but this guy is why I have been reluctant to join and help until recently. He is the reason I will not waste much more of my time attempting to help others. [RANT OFF]
I will try to calm now.
Thanks for listening and I don't care if you are offended.
THE_KINGDOM said:
my situation is quite different from yours. There is no ability to "adb reboot" my device because the device is completely undetectable by USB.
I've now only managed to see the device twice in adb mode and that was completely random while in TWRP recovery, and I didn't need to turn on ADB sideload to make it visible either.. other than these two times I've tried well over 100-150 times, this phone is absolutely undetectable by USB/Computer unless in the bootloader.
Click to expand...
Click to collapse
joegestes said:
If you are able to detect the device in bootloader "fastboot devices" but still can't ABD devices in android with USB debug enabled or in recovery and/or you experience intermittent ABD detection. After looking through OP and post #322 you are absolutely certain that it is not a driver issue, you are likely looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB devices.
Click to expand...
Click to collapse
joegestes said:
Also be sure to try a new high quality USB data cable. (not a cheep charging cable)
Click to expand...
Click to collapse
joegestes said:
[RANT ON]
I have already addressed your issue in this thread http://forum.xda-developers.com/goo...es-windows-t2514396/post59570828#post59570828 and yet without so much as even a single reply or simple thank you for taking my time and telling you in detail how it is, you found it necessary to create a new thread? Are you hoping for a magic bullet?
What's even worse in my world. You offered not a single thank you to anyone here in this tread that completely wasted their valuable time trying to help you after you already have your answers.
I realize I am relatively new member here at XDA. But I've been lurking here for over 5 years. Forgive me but this guy is why I have been reluctant to join and help until recently. He is the reason I will not waste much more of my time attempting to help others. [RANT OFF]
I will try to calm now.
Thanks for listening and I don't care if you are offended.
Click to expand...
Click to collapse
Wow man you need to cut the estrogen pills out. This is borderline extremely weird...
You gave me one potential plausible scenario and this thread was created days before my activity on that other thread. And my first comment u quoted was a reply to somebody else lolol...
Also, I have no charging issues whatsoever with this phone... therefore charging port may not be an issue at all. But at this point I don't deny that chances are it's an extremely rare hardware issue, rare.. Hence why I'm trying to explore potential software issues/fixes before hand.
And actually I'm very generous with the "thank you" I dish out to users on XDA, unfortunately I most people seem to think its a driver issue because thats the common issue.. But im trying to relay to people that my phone is not detected at all, zero recognition of a USB attached device. EXCEPT when in fastboot.. Which makes no sense... If it was a broken port then why does fastboot work????
THE_KINGDOM said:
If it was a broken port then why does fastboot work????
Click to expand...
Click to collapse
Because it could be a single broken connector in the port, it could be a bad internal connector, it could be a motherboard issue, etc.
THE_KINGDOM said:
Wow man you need to cut the estrogen pills out. This is borderline extremely weird...
Click to expand...
Click to collapse
Resorting to childish insults when you are called out is weird for a Man and IMO cowardly.
It is also why you should consider taking you own sage advice.
THE_KINGDOM said:
You gave me one potential plausible scenario
Click to expand...
Click to collapse
Actually, I gave you virtually all plausible scenarios.
THE_KINGDOM said:
this thread was created days before my activity on that other thread.
Click to expand...
Click to collapse
Correct. You did not create a new thread afterwards. You first created a new thread and then posted the same issue in a separate thread.
My mistake.
But still you are here, after you already have your answers, never bothering to thank anyone.
THE_KINGDOM said:
I don't deny that chances are it's an extremely rare hardware issue
Click to expand...
Click to collapse
Good, but IMO, it's not that rare on N5.
THE_KINGDOM said:
And actually I'm very generous with the "thank you" I dish out.
Click to expand...
Click to collapse
I,ll give you the same answer I give most people I encounter who are likely in denial.
Your Right! :good:
I haven't seen this mentioned, just making sure you have turned on usb debugging in the developer options otherwise adb won't work.
Sent from my Nexus 5 using Tapatalk

Stuck in bootloader ? Or device recognition problem ?

Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
donkeydances said:
Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Click to expand...
Click to collapse
Flash latest factory image (either 8.1 or DPx/P/9.0).
mrorange2108 said:
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
Click to expand...
Click to collapse
I'm trying that. Thank you !
xFirefly93 said:
Flash latest factory image (either 8.1 or DPx/P/9.0).
Click to expand...
Click to collapse
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
donkeydances said:
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
Click to expand...
Click to collapse
Have you tried with the Fastboot protocol?
xFirefly93 said:
Have you tried with the Fastboot protocol?
Click to expand...
Click to collapse
Like I said, I can't get my phone to be recognized by my computer so no Fastboot protocol. I am not sure why it doesn't get recognized though.

Pixel 2 Hard Brick

Hello, I'm having a Pixel 2 '' dead '' after an OTA update, now it does not start the boot even, on the computer it recognizes as Qualcomm QDLoader 9008, I need a huge help
Do you have unlocked bootloader? Does it recognized as Qualcomm loader in fastboot too?
hunfatal said:
Do you have unlocked bootloader? Does it recognized as Qualcomm loader in fastboot too?
Click to expand...
Click to collapse
the owner of the device said he had active usb debugging, unlocked bootloader he thinks he has. The cell phone does not connect, only the sound when I connect to the computer, would not have blankflash files for it?
Same problem with me after update
elawady.2014 said:
Same problem with me after update
Click to expand...
Click to collapse
Like us, several others gave the same problem, and still no solution
If you have locked bootloader then it's probably an RMA.
For unlocked bootloader check this:
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
hunfatal said:
If you have locked bootloader then it's probably an RMA.
For unlocked bootloader check this:
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
Click to expand...
Click to collapse
What is RMA ?
elawady.2014 said:
What is RMA ?
Click to expand...
Click to collapse
Return to repair / warranty.
My phone is also bricked after the update. Phone was stock.
Had a few instances when the screen would become garbled then phone would reboot, sometimes bootloop a few times.
Last time it did it and never came back on.
Had 70% charge, was on FB messenger and phone won't respond to anything now. Tried a few chargers, etc. Will try to start diagnosing tomorrow if I have a chance.
Sounds like there is no fix for this: https://forum.xda-developers.com/pixel-xl/help/help-pixel-xl-hs-usb-qdloader-9008-mode-t3574278
Tools not available to public for repair of this. Guess I will see if I can find a new motherboard for mine, or new phone. :crying:

Security update wrecked my phone.

So I got an OTA Security update on my Moto One 5g Ace, and as of right now I can't get any data to transfer USB? Ive tried factory reset uninstalled and reinstalled drivers I know the port is working because I can charge it. But when I connect to any computer I tried 3 different one's. None of them see it or even know it's there. Any ideas how I might be able to fix this?
KeRbYRoK said:
So I got an OTA Security update on my Moto One 5g Ace, and as of right now I can't get any data to transfer USB? Ive tried factory reset uninstalled and reinstalled drivers I know the port is working because I can charge it. But when I connect to any computer I tried 3 different one's. None of them see it or even know it's there. Any ideas how I might be able to fix this?
Click to expand...
Click to collapse
Search in settings "USB" and choose data transfer.
ATBG said:
Search in settings "USB" and choose data transfer.
Click to expand...
Click to collapse
That's the first thing I tried, you know how when plug something into the computer it notifies the device it doesn't make a chime the computer doesn't even realize it's been plugged in. My Moto g pure and Moto g supra are still visible so I know it's not Cables and what not.
KeRbYRoK said:
That's the first thing I tried, you know how when plug something into the computer it notifies the device it doesn't make a chime the computer doesn't even realize it's been plugged in. My Moto g pure and Moto g supra are still visible so I know it's not Cables and what not.
Click to expand...
Click to collapse
Did you re-plug it?
KeRbYRoK said:
That's the first thing I tried, you know how when plug something into the computer it notifies the device it doesn't make a chime the computer doesn't even realize it's been plugged in. My Moto g pure and Moto g supra are still visible so I know it's not Cables and what not.
Click to expand...
Click to collapse
Maybe there is videos that can help.
Even using Linux it doesn't show up, i keep checking the cord different devices on different computers to make sure, even the phone thinks its on a data cable but it still doesn't show up doesn't respond to adb or fastboot commands.
KeRbYRoK said:
Even using Linux it doesn't show up, i keep checking the cord different devices on different computers to make sure, even the phone thinks its on a data cable but it still doesn't show up doesn't respond to adb or fastboot commands.
Click to expand...
Click to collapse
I guess custom ROM is the only way.
ATBG said:
I guess custom ROM is the only way.
Click to expand...
Click to collapse
How can I flash it? It's not recognized by anything?
KeRbYRoK said:
How can I flash it? It's not recognized by anything?
Click to expand...
Click to collapse
Can you unlock the bootloader and flash TWRP?
ATBG said:
Can you unlock the bootloader and flash TWRP?
Click to expand...
Click to collapse
It doesn't connect to the computer. It's all good Amazon said it's covered. So im looking for another one.
KeRbYRoK said:
It doesn't connect to the computer. It's all good Amazon said it's covered. So im looking for another one.
Click to expand...
Click to collapse
Okay, good luck.

Categories

Resources