I had a previously working Pixel 3XL, running Dirty Unicorns (flashed in December). I hadn't touched the bootloader / fastboot since then, but just a couple of days ago, I rebooted the phone and it refused to boot after that.

The issue is that fastboot cannot determine the locked status of the phone (Device-State: error!), and therefore behaves as if it's locked (and therefore cannot continue with AVB).

I was curious if something in the system / boot / userspace was able to corrupt the bootloader, or if it was simply a failing battery / emmc. It seems that other people have been struck with this issue, some of them with stock ROM. (I've tried the battery method. It didn't work for me)

(More details in the XDA post linked above. Also any data recovery help would be nice)

  • you mentioned EDL mode, where did you get google firehose programmer from?? – alecxs May 5 at 21:50
  • I didn't. I was asking if someone had the files for an EDL rescue. – Lightfire228 May 5 at 22:35
  • ah.. no no, google did not leak anything for it's devices for security reasons ;) – alecxs May 5 at 22:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.