Google has shared a temporary fix for owners of Google Pixel devices that were rendered unusable after installing the January 2024 Google Play system update.
As previously reported by BleepingComputer, after the January 2024 Google Play system updates came out, some owners of various Google Pixel models experienced internal storage access problems, the inability to open apps or the camera, or even take screenshots.
Google acknowledged the problem and told BleepingComputer that they were looking into the issues, and owners who hadn't applied the January 2024 Play system update were advised to hold off.
Today, Google shared a temporary and somewhat complicated fix on the Google Pixel support forums that could help impacted users restore their phones to normal working status.
"We are aware of a storage issue occurring on a small number of Pixel phones that have received the January Google Play system update, causing some devices to behave incorrectly," reads a post by a Google community manager on Pixel's support forums.
"If your device was impacted, you might notice multiple apps crashing, screenshots not saving, and external storage working inconsistently."
Although Google hasn't shared any details regarding the root cause of the issue, it stated it's more prevalent on Pixel devices with multiple user accounts.
The company says they are working on fixing the root cause of the system update issue and will provide further updates when they learn more.
A complicated fix
While Google is working on a fix that will be pushed out to all Pixel phones via an update, it has released a fairly complicated temporary solution that requires installation of the Android Platform Tools developer toolkit.
If you are comfortable using the command, then you can follow these steps to fix your Google Pixel device:
- Enable ‘Developer options’ within Settings on your Pixel phone by:
- Navigating to Settings > About phone > Build number
- Tapping the Build Number option seven times until you see the message ‘You are now a developer!’ This enables Developer options on your device
- Go to Settings > System > Developer options
- Under Developer options enable USB debugging
- Connect your Pixel phone to your computer via USB-C cable.
- If device shows “Charging this device via USB” -> tap for more options and set to “File Transfer”
- If device shows “Charging this device via USB” -> tap for more options and set to “File Transfer”
- Click here to download Android’s folder of Platform Tools to your computer, which includes the Android Debug Bridge (ADB) application.
- After unzipping the downloaded folder, open your terminal / command prompt.
- Within Terminal / Command prompt:
- Change your working directory to the platform-tools directory you just extracted the tools to.
- Type “./adb devices” (“adb devices” in Windows) and press the Enter key.
- If the result within Terminal lists your phone as “Unauthorized” – your Pixel phone is likely prompting you to allow USB debugging. Tap Allow and retry this step so that your phone is listed as “device” within Terminal.
- Input the following commands in your Terminal, pressing the Enter key after each line:
- “./adb uninstall com.google.android.media.swcodec”
- “./adb uninstall com.google.android.media”
- Disconnect your Pixel phone from your computer
- Restart your Pixel phone (your device might disconnect from network, this is OK)
- On Pixel 5a and earlier: Press your phone's Power button for about 30 seconds, or until your phone restarts
- On Pixel 6 and later, including Fold: Press and hold the Power and Volume up buttons at the same time until your phone restarts
- Return your phone and computer to their previous settings:
- Turn off USB debugging
- Go to Settings and scroll to the System section (on Android 8 and above, go to Settings > System)
- Tap Developer Options.
- Tap the button to toggle developer options Off. USB Debugging is included in Developer Options
- Stop adb:
- Type “./adb kill-server” in your Terminal window and press the Enter key. Exit the Terminal application.
- Turn off USB debugging
The above fix requires having a Windows, Linux, or macOS computer available and a certain level of comfort or familiarity working with developer tools, so it's certainly not ideal for everyone.
Rightfully, some users complained that the fix was far too complicated. Others underlined that Google was too late to share a fix, noting that many impacted users have performed a factory reset by now.
Those still on the November 2023 Play Services update would be better off postponing the installation of the latest update, especially if they use multiple user profiles.
If you're already impacted and need extra help resolving the issue, it is recommended that you ask your questions in Google's support forums.
Comments
smart4ss - 5 months ago
It's crazy really. The whole point of hiding the developer options is that most people should simply not tinker with them. I'm not sure what is the point of posting a picture of an anonymous comment from an unnamed website in the article. But yeah Google's developer workaround shouldn't be called a fix, and most consumers would probably make things worse. Encouraging them to try will likely create more frustration.
U_Swimf - 5 months ago
It isn't intended as a fix. It's a new wave of fresh recruits for future testing.
Imagine going to the mechanic. After you get your car serviced, you leave, pull into your destination and bam the service engine light pops up on the dashboard with a warning that says you need to go back to the dealership. You generally don't want to enable the hidden secret menu in the car that allows you to turn off the cars check engine light...
Later to learn that all those clicks, just made a binding legal contract intended to impose future policies and rules about your new relationship terms. Efffff that noise.
What's the point in all this remote management software, virtual OS, dynamic flash programming and javascript injection stuff if none of it can be used to do what it was meant for?
If you wanna test products because a trillion dollar company that in the past couple years haas laid of tens of thousands of workers (and still makes profit), consider filing a warranty claim instead as inconvenient as it may be. Better than new binding contract which i assume is why the menu is hidden and requires 7 clicks and various other instructions intended to seperate users from Beta testers
h_b_s - 5 months ago
Uh... "dev mode" isn't a secret and quite a few people enable it for reasons other than development. This isn't a "fix" most people are going to deploy on their own, but there's a lot of people out there that can use it if they haven't already done a factory reset. There's far more people out there in Android land that bypass Google's restrictions on apps and rooting than there would be for Apple. Not that this excuses Google's historical and ongoing consumer hostile & callous attitudes; if anything this makes it all the more obvious Google is in the "automated testing catches everything *we* care about" camp of dysfunctional & anti-social development houses.