Does anyone have a clue as to why Gnome would give a claimInterface error when trying to flash a phone with GraphineOS? I would like to get this issue to the right people so it can be resolved.
I get the error on Garuda (Arch Linux) after the phone reboots during the flashing sequence the web installer uses. I think it is probably just before the the last step GrapheneOS has been flashed (“Flash release”). and just before The GrapheneOS factory images has been obtained (“Download realease”).
I’m not sure to understand. I don’t have the device, so difficult to see where the connection problem is.
It will automatically handle flashing the firmware, rebooting into the bootloader interface, flashing the core OS, rebooting into the userspace fastboot mode, flashing the rest of the OS and finally rebooting back into the bootloader interface.
Referring to this sequence (flashing factory images), there seem to be two times when the phone reboots. Where does the connection problem come from?
I think I run into the issue on the first reboot. The error claimInterface occurs on the flash step of the web install here: Web installer | Install | GrapheneOS
All the user does for the web install is basically go through and click the buttons on the webpage while the phones boot loader is unlocked. Since I haven’t looked at the code, I couldn’t say which reboot there is a problem. For me, testing with a Pixel 6a, the issue happens very quickly on the flash step linked above.
So what happens after unlocking the bootloader? Does the phone reboot? Is there a message on the phone when flashing? What are the messages on the site before the error?
After unlocking the bootloader the Pixel phone prompt to approve the unlock. That works as expected.
There is no message on the phone when flashing except for the normal bootloader interface screen.
There isn’t a message on the site before the error that I can remember. That is a good question. All I remember is the phone quickly reboots and then the claimInterface error is shown on the web install page.
Knowing exactly where the problem is in the process is necessary. Also, it might be good to have a web app that runs the relevant commands without flashing anything (i.e. without taking the risk of bricking the device) to see if this is reproducible with Pixel phones and any other smartphone.
I am awaiting a response from the GrapheneOS lead developer on the relevant issue.