Device not detected at factory images download stage on 9a

56565633

Hi,
I am attempting to install grapheneos on to a new Pixel 9a with web installer from a Samsung fold4 with Brave browser, shields down. Fold4 and 9a software up to date.
Successfully enabled OEM unlocking. Unlock bootloader was succesful.
But while obtaining factory images with download release, an 'error - undefined' appeared midway through the download. I attempted six times. Same error.
Thee OEM unlocking toggle is greyed out and inaccessible.
Now, when I reattempt downloading factory images, no device is detected to download on to. Grrr.
Any suggestions gratefully accepted.
Thanks.

akc3n

56565633 as per the prerequisites, https://grapheneos.org/install/web#prerequisites

You need a computer for running the web installer with at least 2GB of free memory available and 32GB of free storage space

Does your Samsung fold4 meet these requirements?

GrapheneOS

56565633 It sounds like you either don't have enough free disk space or the browser is still in a mode where it's not allowing using a lot of disk space. The error you're seeing is caused by the browser removing the file once it gets too large for the available space it's allowing the site to use. It's hard for us to work around it right now but we could improve the error message.

DeletedUser370

56565633 You already made a thread about this: https://discuss.grapheneos.org/d/22541-factory-images-not-downloading-on-pixel-9a

I think it would've been helpful for the people replying if you had provided the info on available storage space in this duplicate thread as well.

I suggest you try flashing from another supported browser. Make sure to not use incognito mode.

DeletedUser288

56565633 Any suggestions gratefully accepted.

Use Chrome instead of Brave.

thure

It would probably be helpful to add some more information like how you connect your phone with the laptop/computer (what kind of USB port and cable) and the operating system you're using.

You're probably using the documentation from the website. What was your last working step you did?

56565633

GrapheneOS
My last action is when I attempt to download factory images, it says "No compatible devices found". And the following appears: "Error: Failed to execute 'requestDevice' on 'USB': No device selected."
On the 9a, the OEM unlocking toggle remains greyed out and it says "Bootloader is already unlocked".
I am using the brand new usb cable that came with the pixel tablet two months ago.
It’s the same error on Brave, Chrome, and Vanadium.

I've used 84GB of the Fold's 256GB. So there is 172GB available.

Would a factory reset on the 9a return the OEM toggle back to original settings?

akc3n

56565633 it says "No compatible devices found". And the following appears: "Error: Failed to execute 'requestDevice' on 'USB': No device selected."

This indicates that your Chromium based browsers cannot detect your device in the correct mode and typically happens because it hasn't been authorized for USB communication. Please check the site settings to verify that you haven't disabled/rejected the site permissions.
You can manually tap the site settings icon in the navigation bar or by visiting the link below. Try plugging it again (and make sure that you plug it in while your phone is unlocked):
chrome://settings/content/siteDetails?site=https%3A%2F%2Fgrapheneos.org and verifying that the USB Devices option is set to 'Allow'.
Additionally, confirm that chrome://flags/#enable-webusb-device-detection is not disabled.

It’s the same error on Brave, Chrome, and Vanadium.

56565633

Hi akc3n,
Firstly, thanks. Secondly, I am waaay out of my depth but doing my best.

When I go to chrome/ flags, this message is highlighted ;
Automatic detection of WebUSB-compatible devices
When enabled, the user will be notified when a device which advertises support for WebUSB is connected. Disable if problems with USB devices are observed when the browser is running. – Mac, Windows, Linux, ChromeOS
#enable-webusb-device-detection
And to the side: "Not available on your platform".

In site settings/ permissions /USB/ Pixel 9a is listed, in a 'ask before allowing'
But under site settings/content/ I have no 'sitedetails'.

The 9a seems permanently unlocked in greyed out mode.

After doing that, tried plugging in, but same result.

The mystery to me is that downloading GrapheneOS on to my Pixel tablet using same cable/phone worked perfectly.

56565633

Thanks to all who helped. Problem resolved. I did a factory reset, stared from scratch, following the consise, step-by-step video guide by Side of Burritos. Good to be back in Graphene-land.

helix

Doesn't work for me either. When I click the button, a download message flashes shortly but the request fails with Error 400.

Copied request as cURL fails aswell:

curl 'https://releases.grapheneos.org/tegu-stable' \
  -H 'sec-ch-ua-platform: "Linux"' \
  -H 'Referer;' \
  -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36' \
  -H 'sec-ch-ua: "Chromium";v="139", "Not;A=Brand";v="99"' \
  -H 'sec-ch-ua-mobile: ?0' ;
curl 'https://releases.grapheneos.org/tegu-install-2025081400.zip' \
  -H 'accept: */*' \
  -H 'accept-language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7' \
  -H 'if-range: "689de7f0-5ee8113b"' \
  -H 'origin: https://grapheneos.org' \
  -H 'priority: u=1, i' \
  -H 'range: bytes=105258-105258' \
  -H 'sec-ch-ua: "Chromium";v="139", "Not;A=Brand";v="99"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Linux"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: same-site' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36' ;
curl 'https://releases.grapheneos.org/tegu-install-2025081400.zip' \
  -H 'accept: */*' \
  -H 'accept-language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7' \
  -H 'if-range: "689de7f0-5ee8113b"' \
  -H 'origin: https://grapheneos.org' \
  -H 'priority: u=1, i' \
  -H 'range: bytes=105258-105258' \
  -H 'sec-ch-ua: "Chromium";v="139", "Not;A=Brand";v="99"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Linux"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: same-site' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36'

a simple curl https://releases.grapheneos.org/tegu-install-2025081400.zip -O works fine and it verifies fine aswell:

ssh-keygen -Y verify -f allowed_signers -I contact@grapheneos.org -n "factory images" -s tegu-install-2025081400.zip.sig < tegu-install-2025081400.zip
Good "factory images" signature for contact@grapheneos.org with ED25519 key SHA256:AhgHif0mei+9aNyKLfMZBh2yptHdw/aN7Tlh/j2eFwM

de0u

helix Doesn't work for me either.

This thread was about installing from a phone. Are you installing from a phone? If not, a new thread might be best.

helix Copied request as cURL fails as well [...]

What's the failure?