Google Pixel smartphone owners report problems after installing the January 2024 Google Play system update, being unable to access their devices internal storage, open the camera, take screenshots, or even open apps.
The issue is being reported by owners of numerous Pixel models, including the Google Pixel 5, 6, 6a, 7, 7a, 8, and 8 Pro, suggesting that it isn't confined to a particular hardware architecture.
The root cause is unknown but is likely a software issue with the January 2024 Play system update that Google hasn't pinpointed or fixed yet.
Most proposed solutions coming from affected users don't address the problem, with some reporting solving it by performing a factory reset, in which case, all data is lost.
However, these recommendations are coming from impacted Google Pixel owners rather than Google themselves, who simply acknowledged they are aware of and looking into the issue.
"I wonder why this is not something that's getting blown up forcing Google for a fix. Spending so much money on a phone just to be made unusable by an update is very aggravating," an affected owner posted in Google's Pixel Phone support forums.
Google Play system updates are separate from the monthly security patches, both accessible via Settings > Security & privacy > System & updates.
Google introduced Play system updates in Android 10 as a way to deliver crucial security updates and system component enhancements and protections in devices not running the latest patch level and those that have reached the end of support by the OEM.
They are served directly by Google, bypassing the OEM update channels, and are effective in keeping older Android versions compatible with modern apps and Google services, and also relatively safe.
In the case of Pixels, it appears that Google performed a staged roll-out of the January 2024 Play system updates, so not every Pixel owner has received the problematic update yet.
If you are still on an older update (last was November 1, 2023), it is recommended to stay on it and postpone applying the January 2024 update until the situation clears up.
BleepingComputer has contacted Google for a comment on the reported problems and their plans to address them, and a member of the firm's press team has sent us the following:
We are aware of this issue, and are looking into it. - Google
Same thing happened a few months back
Although the nature of the current problem has not been confirmed yet, memory bugs introduced by a Play system update previously rendered Pixel devices completely unusable in October 2023.
Google eventually addressed the media storage access and repeated rebooting problems by releasing an update on November 7, 2023. However, by then, many users had already resorted to performing a factory reset, losing their data as a result.
The recurrence of this type of issue in such a short timeframe is quite concerning for Pixel device users, who cannot use the features of their phones.
The situation undermines the trust in Google's quality assurance processes and raises concerns about the rigor of the tech giant's validation and testing protocols before deploying a system update.
Update 1/25 - Added Google's response
Comments
wackoinWaco - 3 months ago
I have an 8 Pro AND the January 5 update. What's different you ask??
I have GrapheneOS installed. Could that be the only difference?
Inquiring minds want to know.
Regoat - 3 months ago
<p>Funny because I'm reading this on pixel 8 pro. Several people with the problem have the whole world where the device is sold, so how does it affect trust?</p>
AngryOxide - 3 months ago
I own a Pixel 6 with GrapheneOS and no problems here.
rhasce - 3 months ago
Same here, I bet ya they were trying to release a kill switch for older models. I also run GrapheneOS and my phone got the same update, of course not from Google, my phone is perfectly fine, clearly it is something google trying, is why I run de-googled software, it is way better. Pixel 5a here
zeroroots369 - 3 months ago
"Same here, I bet ya they were trying to release a kill switch for older models. I also run GrapheneOS and my phone got the same update, of course not from Google, my phone is perfectly fine, clearly it is something google trying, is why I run de-googled software, it is way better. Pixel 5a here"
#winner I 2nd...
goggomobil - 3 months ago
My Fitbit Charge 5 bricked because of a forced update. Google offered a 30% off coupon on a new unit....even though it was still in warranty.
Good luck, Pixel owners!
SVS24 - 3 months ago
Interesting. I had the pixel issue a few months ago and at the beginning of Jan while I was away from my children. I couldn't fix it so purchased a new pixel thinking my phone was out of warranty and dying and at the very same time my Fitbit charge 5 kicked it in as well so purchased a new one of those. Not knowing how to fix it I literally purchased both a new pixel and a Fitbit charge . I'm pretty cheesed right now because in total that $2000 for something that shouldn't have happened.
Regoat - 3 months ago
I have my 6th model of pixel phone and And I've never had any major problems so good luck for you
Tvnutt - 3 months ago
Wow! This sucks! I have a 6A and luckily now issues like this and I feel for the people affected . I did do a system update last month and, for some odd reasons reason, the VM icon won't disappear after I delete the VM. I have to restart the phone. No big deal but it is annoying.
greg18 - 3 months ago
No problems here on my Pixel 7 that is running stock Android 14 Beta firmware.
midnightwolf - 3 months ago
Funny this gets coverage but the Samsung S22 Ultra issue on AT&T that still has no fix from November has no coverage. Tons of people are without their phones since the November update. The issue is no network connectivity and AT&T blames Samsung and Samsung blames AT&T but both recognize the issue.
The funny part is that the updates shows up as November 1, 2023. Just like these phones.
ibuddy66 - 3 months ago
You should submit this as a complaint to the FCC about device functionality. They need to be held accountable. https://consumercomplaints.fcc.gov/hc/en-us/articles/360001201223
Go to the FCCs phone complaint section and select equipment
wackoinWaco - 3 months ago
Thx for the link. It might come in handy some day.
zeroroots369 - 3 months ago
I thought everyone got these models because they're the best for De Googling and installing custom Rooms? Like the old Jelly Bombed galaxy notes... Just me?
ibuddy66 - 3 months ago
I've been raising alarms on Google's update practices for years to deaf ears. Google effectively has no "Stable Channel". They have betas and more betas wearing a stable channel name tag. Their stable releases not just Android wise but even over to Chrome OS and other products are about as stable as a dead guy on a roller coaster. It's a terrible way to run a business. Imagine any other appliance or item that had this sort of treatment. Sorry the fridge doors fell off because the bolts were buggy. Maybe next month we will fix it. Next Month?!?! Yup. Say bye to your food! It's this type of disguised beta mentality that erodes customer trust. Betas should be betas. Stable releases should be stable.
Lividmonkey - 3 months ago
The irony is that I'm reading this on a stock Pixel 6 Pro and sent it to my wife on her stock Pixel 8 Pro. I fear Pixels are still quite operational.
moabpeggy - 3 months ago
I had this just happen on my Pixel 6. I got mad and started my phone to restart. I then restarted my phone and had the can't open apps issue but I could go to settings. So I went to the security update, clicked, and forced a recheck to see if there were any updates in hopes this might kick the system to be usable before I went through the process of factory reset, and BAM, that simple step made my phone usable again.
Google still needs to fix this. See if this works for you.
Anonymously - 2 months ago
unfortunately I have a Google Pixel 6a having troubles with the Google Play system not updating it stuck on Nov 1, 2023. I have factory reset nothing works. I had the same issue with my pixel tablet I did get that update but my phone won't. they do need to get a fix.