Win 11. Pixel 5 with calyx. installer
I keep this here as troublehooting help if someone needs.
First i got stuck during a few steps. I was stuck with in the unlocking Bootloader Step with Pixel 5 and did two things afterwards it worked. not sure which one helped.
- when activating usb debugging i got a prompt, to always allow this computer (with a number ID). Here i ticked the box.
you can verify with .\adb devices: that should give you a number and “device” at the end (not “unauthorized” (download platform tools to do that) - when the phone was in fastboot, but nothing happened i went to win device manager and installed the Google USB drivers (which would not install, when the phone was just regularly connected)
https://developer.android.com/studio/run/win-usb?hl=de
OEM-USB-Treiber installieren | Android Studio | Android Developers
in the end i got all the way to the actual installation (after everything was downloaded). The phone was on the fastboot screen with bootloader unlocked, but the iode installer only gave me “waiting for any device” in the details.
same when i tried .\fastboot devices
Then i unplugged tried to start from the bootloader, got to some other screen, that asked me to go back to bootload or shutdown or a third option (the screen was called something with “D” at the end). that got me back to bootloader screen, where i could choose to relock bootloader or start.
somewhere along the way i got a warning, that the device is corrupted.
I tried start, now i’m stuck on the google logo and nothing happens i cant even switch it off
Then I got back to bootloader via holding start and volume down for a while and then keeping holding volume down. Then i downloaded and unzipped the fastboot files for my phone from ota / ota · GitLab.
Then I checked connection of the phone via adb. it was there. then i tried running flash-all.bat via rightclick and run as admin. that failed, then i ran it from shell and that worked. after shell arrived at “Press any key to exit” I had the option to relock the bootloader, (which i didnt for now) and then a few restart confirmations and it worked.
Pretty painful in the end compared to the installer, but it worked with help from ai.