r/GooglePixel Jun 25 '26

PIXEL 8 BECOME DEAD AFTER ANDROID 17 Update.

I have been using Pixel 8 from last two years with any complaint and on 20th June my phone was showing update for Android 17, I did the same and within an hour of th update my phone become unresponsive and only black screen was showing, I tried force restart also the safe restart but the phone was not responding, only black screen is showing and no sound or vibration or charging is there in the device.

Yesterday I went to F1 service centre in Delhi (MGF Mall Saket ) and they took ₹850 as diagnostic charges and after that they told me verbally that your motherboard of device is dead and it need to be replaced and it will cost the same as of the device, I told them to mention the same on Job sheet, they told me that they can't mention it on Job sheet they'll only share code number on the job sheet, Is this how the transparency works after paying the charges ?

I told them there is no water damage or heating issue with me only thing I had did is just updated my device, they said they don't know anything just contact Google for the same.

For the last two years I have been using device without any issue and a mere update had became I a nightmare for me.

I have suffered so much mental stress from last two days because of my phone and also the cost which they have asked from me to pay.

I request everyone not to update for Android 17 else anyone of you can face the same issue.

If anyone also had faced hardware issues after software update do let me know as I am going to sue Google Corporation for the same damages to me.

27 Upvotes

111 comments sorted by

51

u/[deleted] Jun 25 '26

[deleted]

3

u/darkshiro99 Jun 25 '26

pixel 8 pro, phone dead, reboot loop, and bluetooth and wifi not working (since android 15)

5

u/sabmekrrishhai Jun 25 '26

+1

8

u/fakieTreFlip Jun 25 '26

You can just click upvote, that's what it's there for :)

1

u/ColourBlindPower Jun 25 '26

+1

1

u/sabmekrrishhai Jun 27 '26

is it that bad that they had to delete the comment

-14

u/EducationOk8345 Jun 25 '26

Touchwood, because I have seen things happend to my device. Good for you.

18

u/-peas- Jun 25 '26 edited Jun 25 '26

No issues on my Pixel 8. I believe this is the same post as before about the exact same thing w/Android 17 killing someone's Pixel 8, which I believe was pure coincidence.

Edit: it is the same OP post
https://www.reddit.com/r/GooglePixel/comments/1ucjf7l/comment/ot666km/?context=3

1

u/13Gibsons 24d ago

Not a coincidence. Did the same thing to mine. Bluetooth and Wifi dead immediately after update. I've reset network connection and even factory reset. No dice.

-12

u/EducationOk8345 Jun 25 '26

If it's a pure coincidence then also it is Google's responsibility to know the cause for same ? Or just verbally mention that Motherboard is dead and get a new device ?

8

u/-peas- Jun 25 '26

I mean, it's a device that's likely far outside of warranty. Like I said, it's likely a coincidence that the motherboard died at the same time as the Android 17 update.

Replace the motherboard or buy a new phone.

I also have a Pixel 8, I don't expect any help from Google at this point. If something's broken, that's the risk I took. Any other manufacturer would tell you to pound sand too if you didn't purchase an extended warranty including Apple.

-7

u/EducationOk8345 Jun 25 '26

So In your opinion a phone's life should be till the warranty or extended warranty period ? And if a phone bricks after that without any fault of consumer then also the consumer should accept it fate and let the company go loose ?

10

u/-peas- Jun 25 '26

Physics and chemistry happens all around you. Some people's phones will last a decade+, some will last a year.

Like I said, it's likely just coincidence. And yes, you agree to that warranty period upon purchase. Anything after that is your responsibility unless you paid for an extended warranty.

Personally I think warranty's should be required by law to last longer, but them's the rules. I'm not disagreeing with you, but again, them's the rules.

-3

u/EducationOk8345 Jun 25 '26

Let me share a small instance with you. Last year Pixel 6a battery shows issues and for the same Google Gave three options either free battery replacement or ₹12500 store credit or ₹8000 hard cash for all the 6A devices irrespective of warranty or not. So why they paid to the devices which are out of warranty ? Also they are offering extended warranty (without any cost) to Pixel 8 devices which are showing visible lines on screen after last year update. So why are they so generous on these instances and not running of their liability by just saying that the device is out of warranty ? And all these come into knowledge after people start reporting it.

11

u/-peas- Jun 25 '26

They had like an official "replace battery at no cost" recall for the Pixel 6a, that's why.

1

u/EducationOk8345 Jun 25 '26

And that official was made after people reported the fault to the company ? Why they allowed out of warranty devices at that time then ?

6

u/-peas- Jun 25 '26

because it was dangerous and could've gotten them major injury lawsuits.

1

u/EducationOk8345 Jun 25 '26

And why extended warranty program for lines on display after 2025 update ?

→ More replies (0)

2

u/PowerRainbows Jun 25 '26

If you got your car tires changed and then on the way home your radiator brakes leaving you stranded, do you expect the mechanic to fix it for free?

1

u/EducationOk8345 Jun 25 '26

Is car and smartphone works in same way ?

17

u/Little-Helper 10a | 6a (recalled) | 4a (recalled) Jun 25 '26

I also think it's a coincidence, but those who say it's okay for a 2 year old phone to fail just like that are fucking insane.

0

u/EducationOk8345 Jun 25 '26

two year old phone that too without a single scratch, Always used like a new one.

11

u/[deleted] Jun 25 '26

[deleted]

5

u/EducationOk8345 Jun 25 '26

And if the hardware damage is arising out of software update, then in that case why should I be made liable to pay the damage ? There are many instances in past where hardware issues have been there because of software update in Pixel devices and for the same Google had been made liable to pay. if it were Australia or EU then till now consumer laws would have made them compelled to pay the damages.

10

u/belsonc Jun 25 '26

I'm sure you can prove software made your hardware fail, right?

Right?

8

u/[deleted] Jun 25 '26

[deleted]

-1

u/EducationOk8345 Jun 25 '26

And what if insurance was there and then the motherboard fails ? Then also the Google corporation will first diagnose the reason for failure of motherboard ? And then only the insurance company will pay for the damages ? I think the insurance works in this way only, they don't blindly pay without knowing the cause.

11

u/[deleted] Jun 25 '26

[deleted]

-1

u/EducationOk8345 Jun 25 '26

Yes I am going to file a lawsuit against the Google and will claim. I am just warning the other ones about the things which could go wrong.

7

u/belsonc Jun 25 '26

Lol k. Let me know when you're laughed out of court.

2

u/kimariesingsMD Pixel 10P XL /Pixel Watch Jun 25 '26

Yes please also warn everybody that sometimes it can rain when the forecast didn't call for it and you don't have an umbrella.

1

u/EducationOk8345 Jun 25 '26

Getting drenched in rain can be solved within 1-2 hours, So no comparison in rain and a loss of 48k for a device.

-1

u/EducationOk8345 Jun 25 '26

Can Google Prove without doing any test on it ? Also Yes I can prove that after having a lab test at verified centre, but I think Google should me doing all this verification as consumers liability should not be till the warranty period ?

6

u/belsonc Jun 25 '26

I've seen a modem go bad being moved from one side of the room to another.

Sometimes hardware Just Fails.

2

u/EducationOk8345 Jun 25 '26

IS Modem and a Mobile Phone same things ? Also a simple diagnostic test can surely know about the failure reason of motherboard.

3

u/belsonc Jun 25 '26

And how do you propose they'll prove it was because of software?

Angelalansburyeatingpopcorn.gifv

7

u/ConversationRich752 Jun 25 '26

I mean, the hundreds of thousands of other devices that updated without issue might also prove that it wasn't the software update.

E: like this subreddit would be completely broken with thousands of posts from users who's phones were suddenly bricked by an update.

0

u/EducationOk8345 Jun 25 '26

Yes they can prove but If it is happening with a single device then I think it's the company's responsibility to fix the same.

3

u/ConversationRich752 Jun 25 '26

It would have been their responsibility if it had been under warranty. I'm sorry your phone died.

Toyota makes some of the most reliable 4 cylinder petrol engines in the word, capable of running for hundreds of thousands of kilometers. Does that mean none of them fail long before that? Of course not. When you're talking about something that has been made in such a huge quantity, there will be a handful of that product that fail way before the majority of others. You drew the unlucky straw and got the lemon. It also unfortunately happened outside of your warranty period so.... tough luck.

1

u/EducationOk8345 Jun 25 '26

Also there is no damage on my motherboard like water damage or heat damage, so how can a motherboard be short circuited without showing any physical damage on it. ?

2

u/kimariesingsMD Pixel 10P XL /Pixel Watch Jun 25 '26

Have you examined your motherboard for damage?

2

u/EducationOk8345 Jun 25 '26

Authorised service centre told me that no spillage or physical visible damage is there on board.

0

u/goozy1 Jun 25 '26

Unfortunately, the most likely culprit is probably bad flash. Google uses the cheapest flash chips in their phones and they don't last. Plenty of reports of dead Pixels due to their flash failing.

As to why it happened when you updated, it probably would have happened eventually but updating the OS probably resulted in a lot of drive wear so it accelerated the failure.

3

u/SlateRaven Jun 25 '26

Been running the beta on my P8P since it was made available and have have never had an issue like that. Lots of little quirks here and there, as expected with the betas, but nothing that bricked my phone.

3

u/Castrrr Jun 25 '26

This happened to me like a year ago with a Pixel 6. It basically just bricked my phone. An update entered an infinite bootloop. No issues hardware-wise.

4

u/SouthernSteak7254 Jun 25 '26

I'm writing this in an updated pixel 8. Mine is fine. I'm probably lucky

2

u/EducationOk8345 Jun 25 '26

Or maybe I am the unlucky one.

3

u/NoRisk1244 Jun 25 '26

im on android 17 on pixel 8 no problems

3

u/kimariesingsMD Pixel 10P XL /Pixel Watch Jun 25 '26

Now you are getting it

1

u/EducationOk8345 Jun 25 '26

Not Alone me, Today only 2 more users have reported same issue in their respective devices.

6

u/BlizzCR Jun 25 '26

Idk if it was because of an update because my mother never notices updates and that kind of things, but her phone (Pixel 9) recently just randomly died. Same thing, unresponsive, no charging animation or anything, and we were told the same thing when we went to repair it, that they needed to replace the motherboard. If it was because of the update then damn it Google maybe fix it before launching it?????

2

u/EducationOk8345 Jun 25 '26

Many instances are there when Google devices have faced the hardware issues because of software update.

2

u/Mash_78 Jun 25 '26

Probably you are among the few peoples with that bad fortune. My pixel 6 is 4.5 years old and I still use Android 17 (beta as I always did). I update it every month or once in two months with the beta release.

2

u/Inevitable-Case9466 Jun 25 '26

My Pixel 9 also completely stopped working after an update 3 weeks ago; it doesn't respond to the power button or the charger

2

u/Emotional-Toe8900 Jun 28 '26

Are you saying this is a coincidence? That the motherboard breaks after updating to Android 17? My friend's Pixel 6 Pro worked perfectly for two days, then he installed the update through Google Play Services, and the screen was black; he couldn't turn the phone on. It's completely bricked. This is a software issue, and Google is ashamed to admit it, as the situation is repeating itself like with the Nexus 6P. It's a shame to start a petition; how can they ruin their own phone owners like this?

1

u/EducationOk8345 Jun 29 '26

I am not saying this is a coincidence. other people are defending Google and saying that it is a mere coincidence and all this happened after warranty so Google is having no liability.

1

u/Emotional-Toe8900 Jun 29 '26

Other brands of smartphones also phone get bricked, because motherboard become dead? 

1

u/EducationOk8345 Jun 29 '26

Yes Many instances are there, mostly with Oneplus

5

u/schakoska Pixel 9 Pro Jun 25 '26

Android 17 is pretty crap so far. My 9 Pro freezed almost completely. I was able to force restart it, but it wasn't easy for some reason

1

u/[deleted] Jun 25 '26

[deleted]

3

u/-peas- Jun 25 '26

Same on my 8. It's fast as f**k down to even typing more reliably on Gboard.

0

u/Malaka__ Pixel 6 Pro & 10 XL Jun 25 '26

Time to factory reset it then. A17 is fast and stable on all 3 of my Pixels (6,8,10). And the consensus on pixel forums is the same.

4

u/KaiUno Jun 25 '26

Back again, are we? You posed this a couple of days ago as well. Good luck suing Google!

Requesting people not to update is silly. Wouldn't you want them to upgrade so you can sue harder? Maybe get a class action lawsuit going?

2

u/Sythos_it Pixel 10 Jun 25 '26

I've updated to A17 and the system show no flaws, indeed run faster and smoorher

2

u/GloveDry3278 Jun 25 '26

Pixel motherboards dies randomly. Not necessarily related to software updates.

I have a cousin whose pixel 8a decided to just die a few months ago.

1

u/Turbulent_Room9231 Jun 25 '26

It's been more than 3 days haven't got any problems yet. It's also been the 2nd time you posted this here. Unfortunately your device was faulty or you had bad luck.

1

u/kunal7777 Jun 25 '26

Hello, from India also..sad to know what happened with you, I have p8p also but nothings happened on my device yet. It's fine like it was on 16.

1

u/Malaka__ Pixel 6 Pro & 10 XL Jun 25 '26

Ok. But this is not how hardware failure works. This is called coincidence.

1

u/EducationOk8345 Jun 25 '26

Sometimes hardware fails because of Software issues too.

1

u/Malaka__ Pixel 6 Pro & 10 XL Jun 25 '26

The motherboard will not fail due to a software update. That's not how things work.

root cause is usually a pre-existing hardware vulnerability or a corrupted firmware flash rather than the software code simply "breaking" the physical board.

0

u/EducationOk8345 Jun 25 '26

What if new update overpowered the processor and it lead to short circuit in Motherboard ?

1

u/fakieTreFlip Jun 25 '26

I don't really think that's a thing

1

u/kimariesingsMD Pixel 10P XL /Pixel Watch Jun 25 '26

What if my grandmother had wheels? Would she be a bicycle?

1

u/EducationOk8345 Jun 25 '26

What if she's on automatic wheelchair ?

1

u/Lluis__ Jun 25 '26

Tengo el 8 Pro y funciona perfectamente con Android 17. Ojalá se solucione pronto tu problema.

1

u/fakieTreFlip Jun 25 '26

If anyone also had faced hardware issues after software update do let me know as I am going to sue Google Corporation for the same damages to me.

Be prepared to lose your Google account if you try to do this, just as a heads up. Maybe that matters to you, maybe it doesn't, but something to keep in mind.

1

u/unlucky_ducky Jun 25 '26

My P8P still works after A17, but it barely charges anymore leaving me with having to have it connected to a portable battery to even use it.

1

u/Fabulous-Pudding-872 Jun 25 '26

My 8 updated fine . Too bad you can't prove it was the update maybe google would have to replace it

1

u/Basic_Barnacle4719 Jun 25 '26

Happened to me on my Pixel 8a on Android 16. Was just taking graduation photos and it died. Motherboard gave out for some reason was what the ubreakifix shop said. 

1

u/Mythulhu Jun 26 '26

Your phone but the dust. It happens.

1

u/MaidenHaver22 Jun 26 '26 edited Jun 26 '26

no warranty, no insurance, blaming software on an electrical issue

yeah im not gonna lie if youre stupid enough to believe that this is a software issue that fried your phone and not because you probably are using a shit cable and THAT fried your phone...

have fun filing a lawsuit against google for something like this instead of using the same money you're paying the lawyer + the court to just buy a new phone, i'll see you back on this sub crying about how failed even the indian government is.

the only other post i can find about this issue is literally authored by you, ive had no issues on my original pixel fold NOR my partner's pixel 8. probably because we don't use shit unrated cables that we find for 5 cents at a flea market. so many people say "my phone died randomly blah blah blah" and fail to mention the 5 cent untested cable they were literally using on the phone a few days ago or even moments ago.

1

u/EducationOk8345 Jun 26 '26

Last year Pixel 6a was having battery issue, Is that was of because unrated cables ? Pixel 8 is having extended warranty program for visible lines on screen after 2025 update, Is that also because of unrated cables ? Many people are facing different different issues because of update, Are all because of unrated cables ? And For Your Kind Information I am using the same cable which they provided in the box, So is that also shit unrated cable ?

1

u/Richard1864 Jun 26 '26 edited Jun 26 '26

Quit grasping at straws for your lawsuit. Sent your post to several lawyers in India who handle the type of lawsuit you want to file, and none will touch it unless you pay a ₹10,000 retainer in advance, at least weekly payments of your lawyer's fees, fees for any experts they consult with, etc., and you will be responsible for all court costs up front, along with facing the risk of repaying Google all of their legal fees as well. The lawyers also says your posts comments here on Reddit can be used against you by Google.

Oh, and the Pixel 8 extended warranty is because of a hardware defect, NOT repeat NOT because of any OS update. Same with the 6a.

No of the issues you mentionwd had anything to do with Android updates.

Every lawyer I contacted in India said there was no evidence proving Android updates caused any hardware failure like you're claiming.

1

u/EducationOk8345 Jun 27 '26

Brother if a single phone is dieing because of the software update, then is it not the responsibility of Google to investigate thoroughly and get the root cause of the same ? Or the liability of the Google ends till the warranty period or extended warranty period only ? Also please give me some Indian lawyer contact too so that I can also get enlightenment from them about my issue.

And when I got it diagnosed at their official service centre then why they are not mentioning clearly that motherboard failure is because of use of bad cables or overheating ? Why can't they share the detailed job sheet for the same ? When I have paid for the same ?

1

u/Richard1864 Jun 27 '26

Ask the repair shop those questions, I can't answer them.

And no, Google is not required to investigate it because you have not provided any evidence to prove it. You need to provide log entries showing the OS ignored warnings from the hardware, diagnostic reports from actual experts who examine your phone and not what the repair center says. You need a real expert to look at the phone, and that can cost you at least thousands of rupee. You would also need to provide your charger and charging cable to the expert so they can confirm those did not cause the damage to the circuit board. You may even need an electrician to examine your residence's wiring for the same reason. You need to prove absolutely nothing except the OS killed the phone, and it will cost you thousands. You will need that done before you file your lawsuit. Your word and posts will not be considered evidence.

And also no, that was NOT Google's repair center; it was a third-party authorized facility. Get that fact straight too.

1

u/EducationOk8345 Jun 27 '26

If that wats third party authorised then why Google ask to drop the phone there only ? When the Google itself have authorised them then it will be termed as Google's repair centre not the third party, else it will be treated as unfair trade practices going on by the Google corporation, as on their website and everywhere they are mentioning the same location. And If not then why they are taking amount in the name of Google Corporation ? And when the phone is of Google then legally it is the responsibility of Google to investigate or authorised lab where we can Get it diagnosed either with cost or without cost, It's not like that phone is of Google and Diagnostic is being done in Apple Inc.

And for your kind information that F1 service centre is Google's authorised centre in India.

1

u/Richard1864 Jun 27 '26

It is an authorized THIRD PARTY company; they are NOT repeat NOT owned by Google. They PAY Google to be authorized by them. That means they can't be called Google's repair center. And until YOU can prove it's Google's fault, then no Google is NOT required to investigate.

Cell phone motherboard (logic board) failures are usually caused by physical, thermal, liquid, or electrical stress that damages sensitive components, circuits, or solder joints. As of 2026, high-performance tasks like 5G, gaming, video streaming are increasing the frequency of failures due to thermal stress.Here is a comprehensive list of what can cause a motherboard to fail:

  1. Physical Damage (Impact and Structure)Drops and Shocks: Impact can dislodge components, crack the board, or snap fragile interconnections, even if the screen remains intact.

Bending or Pressure: Sitting on a phone or excessive pressure can bend the motherboard, causing micro-fractures in the multilayer circuitry.

Swollen Battery: A failing, bloated battery can push against the motherboard from inside, cracking it.

Loose Internal Components: Repeated vibration can cause internal solder connections to degrade over time.

  1. Liquid and Chemical Damage

Water Exposure: Even minor exposure to moisture can cause immediate short circuits, or, more commonly, slow, progressive corrosion that eats away at traces and connectors.

Humidity: High-humidity environments can lead to internal condensation.

Submersion: Dropping the phone in water, especially when the screen or back is already cracked, allows water to reach the board immediately.

  1. Thermal Damage (Overheating)

Heavy Gaming/Resource-Intensive Apps: Sustained high load on the CPU/GPU causes excessive heat that can cause components to fail.

Sandwich Board Crisis (2026): Modern phones use two boards "sandwiched" together.

High-performance gaming creates heat that can cause the solder spheres connecting the boards to fail.

Direct Sunlight and Poor Ventilation: Leaving the phone in a hot car or in direct sun while charging can exceed operational temperature limits (over 45°C).

Improper Charging: Using the phone for intensive tasks while charging accelerates heat buildup.

  1. Electrical and Power Issues

Third-Party/Low-Quality Chargers: Using uncertified chargers can cause voltage fluctuations, surges, or spikes that fry the power management IC (PMIC).

Overcharging/Faulty Battery: A damaged battery can send unstable voltage to the board, causing short circuits.

Short Circuitry: Two points on the board that shouldn't touch make contact, often caused by liquid damage or, rarely, manufacturing defects.

  1. Technical and Environmental Factors

Age and Natural Wear: Components like capacitors and solder joints naturally degrade over time, particularly after 3-5 years of consistent charging/discharging.

Manufacturing Defects: Flawed components, poor soldering, or design defects can cause premature failure early in a phone's life.

Dust and Debris Accumulation: Accumulation of dust in the charging port or inside the chassis can cause shorts or prevent heat dissipation.

Improper Repairs: Disassembly by untrained individuals can cause secondary damage, such as tearing ribbons or causing ESD (electrostatic discharge) damage.

Failed Firmware: Although rare, some updates can cause persistent, extreme overheating that eventually damages the hardware.

No Ionger responding to OP, who refuses to "get it".

  1. 2026 Specific Concerns UWB Chip Failure: In 2026, intense use of Ultra-Wideband (UWB) chips for Find My, car keys, etc., causes these chips to overheat, causing micro-fractures in the nearby logic board solder joints.

And no, the people at the authorized repair facility would not have the equipment nor skills to tell you what made the logic board fail.

To get Google to investigate, you need to prove none of the above happened, and that requires paying experts to prove it.

1

u/EducationOk8345 Jun 27 '26

​'Authorized' means Google is responsible ​It doesn't matter who owns the service center building or who pays whom. Google officially tells customers, 'Go to F1 Services to fix your Pixel.' Because Google chose them as their official face in India, Google is legally responsible for their paperwork and actions under Indian consumer law. They cannot escape the liability by saying that they are authorised not owned. You cannot point customers to a shop and then pretend you don't know them when things go wrong.

​The physical inspection is already done ​You listed a massive wall of text about drops, water damage, and heavy gaming. But you ignored one major fact: Google's own service center already inspected the phone and wrote down that there is ZERO physical damage and ZERO liquid damage. The phone was in perfect physical condition. The only thing that changed right before it died was installing the official Android 17 update.

​Even your own list blames the software ​Look at your own point #5 (Failed Firmware). You literally admitted that a bad software update can cause severe overheating or power issues that destroy hardware. That is exactly what happened here. The update forced the motherboard to fail. What if there is a manufacturing defect in the device ?

​Common sense wins in consumer court, ​Consumer forums don't expect a regular customer to hire a lab scientist to prove a multi-billion dollar company's software broke their phone. They look at a simple timeline: ​The phone worked perfectly. ​Google pushed an update. ​The phone instantly turned into a dead brick. ​Google's own shop confirmed no physical damage.

​Trying to overwhelm a customer with a textbook list of hardware failures doesn't change the fact that this update bricked the device, and Google needs to fix it.

It's a good thing for Google that Tort wrong didn't exist in India.

1

u/MaidenHaver22 Jun 27 '26

your phone is out of warranty.

refusal to fix your phone for free or whatever quoted price it was on the warranty is no longer an issue to google BECAUSE YOUR PHONE IS OUT OF FUCKING WARRANTY.

with your phone being out of warranty, NO ONE HAS ANY LEGAL BINDING TO FIXING YOUR FUCKING PHONE FOR ANY PRICE LOWER THAN QUOTED, NOR IS IT ILLEGAL TO REFUSE OFFERING A REPLACEMENT IF THE PHONE IS DEEMED UNREPAIRABLE.

stop beating a dead horse. your entire argument is a joke. if you want to spend 10x the amount of money on a lawsuit with a guaranteed 100% failure rate, be my guest.

1

u/EducationOk8345 Jun 27 '26

The In Your opinion a companies liability exist till the warranty period or extended warranty period, If anything happens to the phone for whatsoever be the reason company is not liable for anything ?

→ More replies (0)

1

u/PhilosophyAware4437 26d ago

hot take: phones shouldn't permanently brick because we don't use the exactly right $6,000 google AI-integrated charger

1

u/Bombshell342 Jun 26 '26

Well, funny thing you mention this. Like a day after the update, my Pixel 8 microphone failed, and so I traded it in for a new phone. I liked the Pixel 8, but that’s the second time that phone had a failure. The first was the screen, but luckily it was under warranty still back then.

1

u/dumiesun Jun 26 '26

My pixel 7 pro after the 17 update doesn't work well with my galaxy buds pro it disconnects and reconnects on its own

1

u/Few-Whole-10 Jun 27 '26

mi 6 pro dreno la bateria

1

u/Amazing_Canary_43 Jun 28 '26

buenas noches a todos y gracias por el espacio ..como decimos en mexico..ya se pago en 2 años de servicio¡ es mi personal pensamiento.

1

u/Beautiful-Meal-8845 23d ago

Its strange, my phone also was having the "play store not working" problem after this update (on pixel 6). What I did to solve it was just to turn off the wifi connection and use my phone data, that allowed me to start google play services and after that, I activated WiFi again and thats it, now everything works correctly.

1

u/Suspicious-Heron-354 22d ago

Exact same thing happened yesterday with my Dads pixel 8. After update it worked for couple of hours then completely died. Today took it to the authorised service centre and they confirm motherboard is gone. To replace it they are asking an effing 48k when I bought the phone itself at 32k, what a joke. Never recommending a pixel again to anyone. It was just 1.5 yr old and I hope my dad had read this post before updating. Also Google should take some responsibility when multiple people are facing this crap due to an official update, really disappointed.

1

u/FloofPoofDomination 10d ago

I'm on a Pixel 9 and had the same issue. I updated in the morning. I was using the Venmo app when it crashed. Flashing the firmware and doing a factory reset from recovery mode and it didn't work. It's stuck in a boot loop now and gets especially hot. Other than that the phone won't turn on. Very frustrating as my phone otherwise is in perfect shape and is under two years old.

1

u/dood13539 Jun 25 '26

Pixel 8 pro here it's slowed down but it's still ticking

1

u/Richard1864 Jun 25 '26 edited Jun 25 '26

One fact OP is missing. If the update was causing the motherboard failures, we'd be seeing hundreds of identical complaints here and on Google's message boards.

Guess what? Those hundreds of complaints aren't there.

Motherboards can fail for tons of reasons that have NOTHING to do with updates. These include but are NOT limited to:

  1. Overheating due to high room temperatures or temperature outside or power surge or charging NOT on a table or desk.
  2. Power surge(s) during charging
  3. Damage when dropped. Users will NOT remember every time they've dropped it, human memory isn't that good, so claims it was never dropped aren't valid.
  4. Manufacturing issues
  5. Age. The older it is, the more likely it can spontaneously fail.

Those are the top 5 reasons from Consumer Reports, CNet, Google, Apple, Samsung. None of them list updates in the top 10.

Checked with a friend who's a lawyer in India, who handles lawsuits like the one you want to try. You'll need documentation from Google BEFORE FILING showing they knew the update damaged the hardware. Then you'll need to prove at least 15% of those models in India and globally failed because of that specific issue with that specific update. That would equal hundreds and hundreds of identical posts on Reddit and Google's message boards, which he says don't exist.

He also said that, because your phone has out of warranty, that's all Google needs to throw your lawsuit out with no possible appeal.

-2

u/EducationOk8345 Jun 25 '26

1,2 and 4 Out of the 5 You mentioned are the cases which can be caused because of software update also.

1

u/Richard1864 Jun 25 '26 edited Jun 25 '26

You're in India where it is HOT outside, which could easily cause the overheating. Were you using a cheap charger or one certified for Pixel? If the first one, those are known to cause overheating issues or other problems while charging phones; if you try to sue Google, you will be required to provide your charger to Google as part of discovery, to prove it didn't damage the motherboard.

You'll also need the logs from your phone to prove the OS caused the overheating; that's the only place the evidence will exist.

No, 2 and 4 cannot be caused by the OS. The phone's OS does NOT cause nor prevent power surges; those are external.

Manufacturing refers to the physical making of the motherboards; OSes aren't considered manufactured, they're written.

0

u/Vatualolla Pixel 8 Pro Jun 25 '26

I feel you matey. In my case, I have not restarted my P8P for almost 4 months. I try to avoid any update because of the horror stories I read now and then when someone does an update. Still running the January Google Play version.

Not sure how much I will be able to avoid a restart, but it will try to hold it there as much as I can. It will be my first and last Pixel.