You can choose to dirty flash if you wish, but the best and easiest way to update is to use the built in updater that works similar to an OTA on stock
So... I have a Pixel 3a and accidentally loaded the ROM here for the 3a XL. This has caused some issues, the most pressing of which is that the device doesn't show up to ADB unless it's in Rescue Mode.
I can't even check anything because the touch screen reads all wrong (doubtless because it's the wrong damn phone). I'm trying to get back to stock just to even be able to use it again, but with ADB not recognizing it I'm not sure what to do.
Any advice? Obviously I need to be more careful in the future.
Perhaps a stupid question but.... i downloaded the fastboot images for the rom and for gapps but don't see anywhere the fastboot commands to use for each img file. Can someone provide or link me to the commands to fastboot the rom files and gapps files, like by line
I am having issues installing the ROM. I flashed the last Q stock and went through the steps in post 2. No problems installing the boot image but when I reboot to recovery and go to the adb sideload, when I try to sideload the ROM, I get the error messages on the phone "E:footer is wrong E:Signature verification failed E:error: 21. I also tried flashing the March Q stock and went through the same steps and still get the same error messages. I am at a loss. Any suggestions?
Thanks for the reply. I performed the checksum on the ROM before trying to install and they matched. From what I read online, the errors I received is because the ROM file isn't signed and will not install. I have put upgrading on hold until I get more info here.
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
adb reboot bootloader fastboot flash boot /path/to/boot.img
fastboot reboot recovery adb sideload /path/to/rom.zip
Yea, I'd wait a little bit for the new update. New builds should be up soon, the build system finally works for bonito and coral, I'll be flashing a new build later today to test and see if anything is broken and if all is good then officials should be good to go.
Not currently. I'm waiting for major changes in rom source to settle down a bit so clean flashes aren't needed each update as often. I'll most likely release the next build with the April patch with a bunch of fixes. Hopefully within the week of its release.