Google acknowledges that the Pixel phone system update is faulty and has provided a temporary soluti

Mondo Technology Updated on 2024-02-02

Recently, Google's latest update to the Play system has brought ** annoyance to Pixel mobile phone users. Many users complain on social ** that problems such as the app cannot be launched normally, the files cannot be accessed, and the screenshots cannot be saved after the update are frequent. The most effective solution at the moment seems to be a factory reset, but this is not only frustrating for users, but can also lead to irreplaceable data loss for users who don't back up** and files in a timely manner.

Google has now confirmed the issue in its community forum, noting that the issue is most common on Pixel phones with "multiple user accounts or work profiles." According to the community manager, the team is working to fix this system update issue.

However, while you wait for an official fix, you can try a new workaround if you want to fix the problem with your phone immediately and (importantly) don't want to lose any data. All you need is a Windows, macOS, or Linux computer, a USB-C cable, and a few developer tools that are willing to run.

First, you'll need to turn on developer options on your Pixel phone. The first step is to find the "build number" of your phone, find it through the search bar in the settings and tap it 7 times in a row. As the number of clicks increases, you'll see a pop-up that says, "You're x steps away from becoming a developer." When you tap it one last time, you'll be asked for your password, and you'll be in developer mode.

Developer options are now enabled in your settings. Search and go to the "Developer Options" menu, scroll down and turn on "USB Debugging". Next, prepare your computer and USB-C cable.

Connect your phone to your computer with a cable and make sure that File Transfer is enabled. If your phone says "Charge via USB", tap on it and select "File Transfer".

Next, visit the Android SDK platform tool official website and ** the folder that matches your computer's operating system (Windows, Linux, or Mac). When the extraction is complete, open the folder. Now, get ready for the technical challenge and open your computer's Command Prompt (Windows and Linux) or Terminal (Mac).

In the Command Prompt or Terminal, you first need to change the current directory to the extracted SDK Platform Tools folder. Enter "cd" after the current line and add a space to the end of the line, then drag and drop the extracted folder to the Command Prompt Terminal window, which will automatically populate the file path after "cd". Press enter, and you've successfully changed your working directory.

Next, type "adb devices" (or "for Macs.").adb devices"), and then press enter. You should be able to see a list of devices; If it says "Unauthorized" next to your Pixel phone, you need to authorize USB debugging on your phone. After allowing USB debugging, re-enter "ADB Devices" (".) is required for Mac systemsadb devices") and press enter, if the status changes to "device", you can proceed to the next step.

Finally, enter the following two commands one by one in the Command Prompt terminal and press Enter. The first one is "adb uninstall com.."google.android.media.swcodec", and the second is "adb uninstall com.".google.android.media.(For Mac systems, add ". ./”)。

At this point, most of the coding work is complete. Now disconnect your pixel phone from your computer and restart your phone. For Pixel 5a and earlier, press and hold the power button until your phone restarts; For Pixel 6 and later, press and hold the power button and volume up button at the same time until you restart.

After restarting, your phone should be back to working properly. If it's still not resolved, you may need to contact the Pixel support team. In the last step, close the Command Prompt terminal on your computer and type "adb kill-server" (for Mac, you need to enter ".).adb kill-server") and hit enter, then close the window. On your phone, go to Developer Options in Settings and turn off the Developer Options switch located at the top of the menu.

After this series of steps, the problem should be resolved.

post by tech

Related Pages