Google Support has screwed me over, any ideas or tips?

ArticularSpark · June 8, 2022

Hey everyone. So, I'm gonna try my best to keep it on the rails here, but I'm infuriated with Google's lack of support on this issue, and want to share/plead for help in the event someone might have tips.

TL;DR: I opted into the Android Beta 13 program on my daily driver, my Google Pixel 6 Pro, apps I need for my job as a network admin didn't work, so I rolled back. After getting Android 12 back (from an OTA update) the device is stuck in the bootloader, unable to even go into recovery, and Google Support won't help because there is a faint scratch on the screen from where my keys brushed against my phone once.

So, the TL;DR includes a lot, but to fill out more info:

- I'm a first-time network admin, and a lot of my accounts use MFA that was on the Google Authenticator instance on my Pixel 6 Pro. Absolutely stupid of me, I know, to use a daily driver as a Beta device, but I wanted to do what I could to aid the devs in gathering info to sooner roll out 13. I still think that opting to roll back to 12 shouldn't brick my device, and I'm wondering if it falls under the terms and conditions of joining the 13 beta program if I had opted out and was trying to roll back through the Google-approved facet.

- I've dabbled in Android ROM and Kernel development in the past, most prominently in the 5.0-6.0 days. I know my way around fastboot, advb, and recovery. This device isn't even recognized as fastboot, recovery, or adb with the enhanced Google ADB drivers.

- I have a log of the support chat, but I essentially was told the device couldn't be warrantied due to the light scratch on the screen. Even though that would have ZERO to do with how the operating system functions. It felt like what I was saying was more than what their script was equipped to handle.

Any thoughts? Any advice? Also, pease feel free to absolutely flame me for the dumb decision.

- ArticularSpark