I installed #Android12 on my #GooglePixel 3a yesterday and experienced some problems: 1) After installing the update, the lock screen crashes immediately after loading. So, as soon as I enter the SIM-PIN, the phone tries to reload the lock screen every few seconds
(1/n)
2) After some time of a flashing status and notifications bar, the phone reboots 3) After booting, step 1 and 2 repeat 4) The phone asks me to perform a hard reset (System couldn't be loaded)
(2/n)
5) I tried to install (adb sideload) the OTA image via ADB in recovery mode, but that didn't help (developers.google.com/android/ota)
(3/n)
6) I also tried to use rescue mode, but the online tool said that my build was too new (pixelrepair.withgoogle.com)
(4/n)
7) Finally, I performed a hard reset of my phone, which deleted all of my data
Luckily, I'm a #GoogleOne user, so my photos are safe (No, I'm not a Google fanboy, I just like the product)
(5/n)
8) I managed to recover my apps and settings from a recent (the morning of that day) online backup, which left me with a working Pixel 3a running Android 12 ...until I tried to use the lock screen for the first time
(6/n)
9) Repeat steps 1, 2, 3, 4, 7 and 8
Note: I also tried not using the backup, and the lock screen worked again, but that wasn't a solution, so I continued on my journey to get my phone to work again
(7/n)
10) In the end, I had to resort to reflashing the Android 11 factory image using the official website (flash.android.com/welcome)
Note: I also tried this with the Android 12 image, but I ran into the same issues as before
(8/n)
The website didn't work under Windows, by the way, because it couldn't find my phone after rebooting to fastboot (first reboot in the process).
So, I used Linux (Ubuntu 21.10 in my case) for step 10.
(9/n)
11) I also sideloaded the latest Android 11 security patch after reflashing (see step 5 for details) 12) I also disabled automatic updates in the developer options afterwards to prevent any additional data loss until a patch is released.
(10/n)
How does Twitter work again? I think those messages are supposed to be short, so let me quickly mention the official Google accounts in hope for some attention to my problem: @Google@GoogleDE
(11/11?)