web installer from graphene: invalid command update-super:super:wipe

hexagonal-lattice

Installing to a pixel-tablet via pixel6 w/ graphene, vandium, as on ubuntu22.04 I could not get brave past the first step (unlocking bootloader - (Failed to execute 'open' on 'USBDevice': Access denied) despite having the udev rules with correct vendorId, and the rest of the instructions as best I can tell (and and a host reboot).

Using my graphene pixel, install seems to proceed fine through perhaps 3 or 4 auto reboots in the installer. Note that each auto-reboot I'm required to re-connect the web app / _webusb manually, in case that's odd (I don't remember doing that on a previous desktop).

Eventually the pixel-tablet seems to try to boot (I see Google spash screen), and then drops back to a menu that's not fastboot. Options are continue booting, proceed to bootloader, enter recovery. Clicking "enter bootloader" gets me back to fastboot, where the web installer can now re-connect - but after re-connecting this error is displayed:

Error: Bootloader replied with FAIL: Invalid command update-super:super:wipe

Next steps? Thank you.

hexagonal-lattice

FWIW, on ubuntu22.04 (which failed as above to connect at all), the steps beyond the directions I've followed are basically here: https://discuss.grapheneos.org/d/710-cant-unlock-bootloader-access-denied/15, but as SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev". My user is already in plugdev, but I did reboot after that step. My desktop error didn't seem related, but I did try echo 0 | sudo tee /sys/bus/usb/drivers_autoprobe before rebooting (I assume that one is not persisted across boots). So it would seem highly unlikely I broke something on the desktop before trying from Vandium.

also a separate question: now the device is in boot loop. I'm hesitant to leave it at a static screen until I get a reply, but fastboot option to shut down doesn't seem to keep it shut down. How can I force the device off / or is it safe to leave it in the boot loop it's in now (it boots to the white background google logo, then goes black and reboots, presumably because the install's just not finished).

hexagonal-lattice

The device is stuck in a boot-loop now, but I have resisted trying to re-start the whole install due to concern I could make things worse -

If it's safe to re-start the install I am fine doing that, please just let me know if there are any risks of bricking here I need to be extra careful around.

hexagonal-lattice

Hoping someone can weigh in at least on whether I can start over, or if I risk a soft-brick of the device.

other8026

hexagonal-lattice I don't think anyone here wants to tell you to just start over in case it does get bricked. It does sound, to me at least, that you probably don't have any other options but to try again.

Try a different device to flash from or different cable for the next attempt. Make sure you're following the directions on the website to the letter.

Searching through the Matrix room quickly, I saw others with the same error were trying with browsers installed with snap or flatpak. You can't use those. That or check your udev rules again.

hexagonal-lattice

other8026
Thank you for your reply. It's always possible I made some mistake, but I followed the directions pretty carefully. Chromium has a snap caveot but brave does not, despite only being available on ubuntu from snap.

That's another question, though, which I submitted here: https://discuss.grapheneos.org/d/8431-conflicting-web-install-instructions-what-browser-for-ubuntu. These are the only two devices I have at the moment, but since brave didn't work for me, I'm hoping someone can point me in the right direction there.

Thank you.

hexagonal-lattice

I un-installed the default brave and re-installed via apt their private repo. Tried twice, hung at _{writing boot}, which was odd given that's the ~_3rd-ish step of the install, and after several boots. This was using a known-good cable and direct port that is typically used for a thunderbolt monitor.

I noticed the fastboot menu was responsive but no actions did anything (even shutdown). I held volume+power for about a minute, and the device finally shut down. starting it again, 3rd attempt, install worked. Whew.

This is my _5th device installing Graphene, and the first one to see issues. No insight, unfortunately, into the source of the problem.

yore

hexagonal-lattice The only possibility I can think of is using a web browser from Snap which is known to cause issues.