Hi all,
I tried to flash iodéOS on a stock Pixel 7 phone but the process has failed. It was up to date with Android 16, and it was bought in the UK, if it matters.
I used the automatic installer on Windows. It stopped working at the point when the phone was rebooted into userspace fastboot (fastbootd). The USB completely stops working on any PC/OS/cable.
I have have confirmed:
In bootloader (white Fastboot Mode) Windows sees Android Bootloader Interface, “fastboot devices” in CMD works and returns the serial of the phone.
In recovery or fastbootd no new device appears in Device Manager (Windows), Linux also sees nothing on USB, “fastboot devices” returns nothing on all machines.
I tried multiple cables (including the original), multiple USB ports and hosts (Windows PC, Linux PC, Surface Go).
If none of those environments see anything at all when the phone switches to recovery/fastbootd, then the USB stack in those modes is effectively dead from the PC’s point of view. That’s not something I can fix with drivers or commands. Hence the installer just hangs at the “waiting for the device” part.
Luckily enough I could restore the stock firmware, so at least the phone isn’t bricked.
What has likely happened is that the iodé installer flashed a bootloader / firmware combo that didn’t fully match the rest of the device’s firmware state.
In that mismatched state, userspace fastboot (fastbootd) and/or recovery couldn’t bring up the USB correctly, so the phone vanished from all computers in those modes.
Do you have any suggestion? I’d appreciate some help.
Thank you!
Update:
I could flash the rom manually. I used Linux as I read that usb driver issues are not really a thing there. Running the flash-all.sh was a success. This time when the phone booted into the userspace fastboot mode, the PC could still mount it. I have no clue why it dropped connection using the installer though. But to be fair I only ever used the Windows installer, as I’m new to Linux and haven’t figured out tgz files yet. But I confirmed on Linux that in that broken state it wasn’t visible in any OS.
Now my next question would be whether it’s safe to lock the bootloader or not yet?
I read it that if I had a recent system version that would increase the anti-rollback counter or whatever, and if the new rom is older, then at the time of locking the bootloader, I could still brick it?
A few days ago, I flashed a Pixel 7A from Android 16 (in accordance with LineageOS recommendations) to Iodé 7 and locked the bootloader, but left it open in the developer options - OEM unlock.
Yeah, the guy had similar connectivity issues during fastbootd mode. But they still could see a device popping up in Device Manager and update the driver, whilst in my case there was none and the 'fastboot devices` command didn’t return anything on any host. The manual install did get through though.