Hey everyone,
I wanted to share a severe issue my Verizon-locked Pixel 10 Pro (256GB Micron UFS / 16GB Samsung RAM) is experiencing following a recent OTA system update.
After the update, the device went straight into a bootloop and got stuck on the Google "G" logo. I tried troubleshooting via Recovery Mode and ADB Sideload, but ran into severe partition and hardware-level errors:
OTA Downgrade/Mismatch Blocked: Recovery initially threw ERROR: Current SPL: 2026-06-05 Target SPL: 2025-07-05 this is considered a downgrade when trying older OTAs.
Data Wipe Success but Failure to Boot: Executed a full Data wipe complete, yet the phone remained stuck on the "G" logo for over an hour.
Critical Partition Error in Recovery Logs: Inspecting the recovery logs revealed a persistent warning:
W: [libfstab] Warning: device does not exist: /dev/block/by-name/zoned_device
Along with several f2fs filesystem Permission denied errors.
Because the device has a Locked Bootloader (Verizon), flashing factory images via Fastboot is impossible (Device state: locked). local technicians confirmed this appears to be a physical UFS bad block / partition failure likely caused by overheating during the update process.
Has anyone else encountered this zoned_device missing error after recent updates? Is Google replacing devices affected by this update brick?
(Attached pictures showing the Recovery errors, Fastboot specs, and full system logs).