I'm trying to do a web install with windows 11 on google chrome. While trying to obtain factory images and clicking download release I get an error saying--- Error: undefined

I've tried on edge and when I click unlock bootloader or download release I get this error
Error: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface.

On firefox ( I know not supported) the options are all greyed out.
Not sure how to post an image of my phone, but here are its details in fastboot mode

Product revision: bluejay MP1.0
Bootloader version :Bluejay -1.2-9894665
Do I need to show baseband and serial number??
Secure boot: PRODUCTION
NOS production: yes
Device state: Unlocked (in red)
Boot slow: a
Enter Reason: reboot bootloader
UART: disabled

    S-Pi Error: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface.

    That means that you have another service or program on your PC interfering with the USB connection. Close everything apart from the web installer, and this Forum, and try again.

      S-Pi Do you have the right drivers installed? You need the correct drivers for your phone, and you also need platform tools.

        I have the same with the web install method. After trying to download release with its blue button, I get in red: Error: undefined. Is repeatable, but stops at different downloaded bytes.
        Also, when trying the cli method it stops after trying to flash the first slot, then the phone doesn't react on any further fastboot command except fastboot devices. Knobs are pretty much stuck at this point, the only key combination to save one's butt is holding Rescue and vol up at the same time for about 10 seconds or so, then it boots into stock Android but with an unlocked bootloader...
        Could flash it back with stock Android yesterday, now there's a new one, still trying after failing with GrapheneOS again on this device... (bluejay)

        • de0u replied to this.

          wjl Also, when trying the cli method it stops after trying to flash the first slot, then the phone doesn't react on any further fastboot command except fastboot devices.

          That sounds like it might be a USB cable/port problem. What kind of cable are you using, and where is it plugged in?

          • wjl replied to this.
          • wjl likes this.

              de0u That sounds like it might be a USB cable/port problem. What kind of cable are you using, and where is it plugged in?

              The original cable (USB-C to USB-A) which came with the device, and I tried two different USB-A ports on the front of my machine (the back is hard to reach, that's where keyboard, mouse, and audio interface are used). Normal data transfer or charging works nicely with those front ports (I've built the machine myself, should be good).
              OS: tried with both Arch and Debian Bookworm, could also try with Windows if that had to be, but I don't know much about Windows anymore...

                  wjl I tried two different USB-A ports on the front of my machine (the back is hard to reach, that's where keyboard, mouse, and audio interface are used).

                  Use the USB ports on the back of your machine. The ones on the front usually aren't suitable for flashing GrapheneOS.

                  • wjl replied to this.
                  • wjl likes this.

                      treequell Use the USB ports on the back of your machine. The ones on the front usually aren't suitable for flashing GrapheneOS.

                      Hm, I don't know if I have any free in the back, can look for that tomorrow. The front ones are 2 x USB 3.2 Gen 1 Ports, the back ones 4 x USB 3.2 Gen 2 ports so yes these are a bit speedier. MB is https://rog.asus.com/motherboards/rog-strix/rog-strix-b550-i-gaming-model/ in a mini-ITX case (Cooler Master NR200)
                      Edit: one of the the front ports is currently charging the Pixel 3a, while the 6a is on the wall socket charger, updating stock Android while I type... bugs me that the boot loader is still open...

                      • de0u replied to this.

                          2nd edit: just checked, started into fastboot again, and then it's like this:

                          wjl@handa-6:~$ fastboot devices
                          29011JEGR15311 fastboot
                          wjl@handa-6:~$ fastboot flashing get_unlock_ability
                          < waiting for any device >
                          ^C
                          wjl@handa-6:~$

                          And no matter which fastboot command from the .sh script I try manually, it's always that answer - guess that is the reason that the web installers (both Graphene's and also Google's) also get stuck at this point... tried factory reset yesterday, didn't help. No idea at which point the Android web installer then worked, and why (I was still on platform tools 33 on Debian yesterday, now it's 34.0.4)... anyway, it's after midnight here, so thanks for now and good night...

                          wjl Hm, I don't know if I have any free in the back, can look for that tomorrow. The front ones are 2 x USB 3.2 Gen 1 Ports, the back ones 4 x USB 3.2 Gen 2 ports so yes these are a bit speedier.

                          The reason why the installation directions say to use the direct-to-motherboard ports instead of the extended ports is because the extended ports result in flashing failures much more often (even though they work ok for charging and for low-speed/occasional data transfer). So it's genuinely worthwhile to try this step (and all the steps) exactly the way that the directions indicate.

                            • [deleted]

                            • Post #12

                            wjl Please follow the installation guide on the GrapheneOS website. It explains not to do exactly what you're doing i.e. using the USB ports on the front of your machine...

                              I have only a USB Type C port free on the back of my machine; however I can still try to temporarily unplug my monitor's USB cable from one of the USB A ports.
                              That doesn't however solve the problem with the unsuccessful downloads from the web installer. Still repeatedly getting:
                              ![https://cdn.cupoftea.social/media_attachments/files/110/853/015/259/828/586/original/96ee8cd68657c046.png](https://)
                              no matter if I try from Debian or Arch, no matter if I try Chromium or the original Google Chrome browser without any extensions...
                              To my limited knowledge that should have nothing to do with any USB cabling and/or port, or does it?
                              Anyway, thanks all...

                                wjl I recommend that you use the USB-C port on the back of your device, and the factory USB-C to USB-C cable from Google, if you have it.

                                wjl ![[https://cdn.cupoftea.social/media_attachments/files/110/853/015/259/828/586/original/96ee8cd68657c046.png](https://cdn.cupoftea.social/media_attachments/files/110/853/015/259/828/586/original/96ee8cd68657c046.png)](https://)

                                This error is most likely caused by your USB connection dropping.

                                Make sure also that you have at least 32GB free storage space on your PC.

                                • wjl replied to this.

                                      treequell I just did, temporarily disconnected my audio interface to do so. No difference.

                                      treequell This error is most likely caused by your USB connection dropping.

                                      I thought so too in the beginning - but as it can be repeated with GrapheneOS (haven't tried others on this 6a) I think somehow it corrupts the first phone slot after flashing it, and then stops. I've tried that twice now, the rescue mode then booted stock Android from slot B which saved me.

                                      treequell Make sure also that you have at least 32GB free storage space on your PC.

                                      On my /home I have 32.5GiB/256GiB, on my /bigdisk (still rotating platters) it's 1.99TiB/3.58TiB. That's the occupied/total bits...

                                      I could flash it back to stock with Google's web installer, and that option also locked my bootloader again - now it's on the August patch of Android 13, which I'll keep for now.

                                      But thanks for the help everyone. I still think GrapheneOS is golden, although on the 3a I now changed to DivestOS (easily and without any problems installed from my front USB btw) as suggested. That's a good option for devices not covered here anymore indeed, so thanks for that tip as well.

                                              • [deleted]

                                              • Post #16

                                              wjl easily and without any problems installed from my front USB btw

                                              Okay? I've had zero issues installing GrapheneOS on numerous Pixels devices over the years.

                                              • wjl replied to this.
                                              • wjl likes this.

                                                  wjl I thought so too in the beginning - but as it can be repeated with GrapheneOS (haven't tried others on this 6a) I think somehow it corrupts the first phone slot after flashing it, and then stops. I've tried that twice now, the rescue mode then booted stock Android from slot B which saved me.

                                                  That's incorrect. The GrapheneOS web installer is not doing that. There are no such issues with web installer. The installation is failing because you have not configured something correctly.

                                                  The process used to flash other OSes is not the same as flashing GrapheneOS, so being able to flash one OS is not indicative either way.

                                                  If you're still struggling with your PC, I suggest that you use another device to flash GrapheneOS. I would recommend running the web installer in Chrome on a device running Android or MacOS. Your Pixel 3a phone might work as an installer.

                                                  • wjl replied to this.
                                                  • wjl likes this.

                                                      [deleted] I've had zero issues

                                                      That may well be. I also had zero issues installing all kinds of third party operating systems on numerous Nexus and Pixel devices over the years, and GrapheneOS installed nicely (via cli) on the Pixel 3a. So I guess it must me my bluejay device which behaves somehow strange.

                                                      treequell There are no such issues with web installer.

                                                      Of course not - that was what I saw using the cli installer, the flash-all.sh script stopped after flashing the first slot, so from there on (after rebooting the device) I tried those lines one by one myself, just with copy & paste from the script to the command line.

                                                      treequell If you're still struggling with your PC

                                                      I don't think that I'm stuggling with my PC. I'm retired by now, but before that I helped the Debian project a bit, was a system administrator in healthcare IT, and also with IBM for several years in technical support. I think I know my way around computers, except that I don't like Windows or Mac much (have been on Linux for over 20 years, also tried some BSDs and supported Solaris before that).

                                                      But no bad feelings, again I thank you all, and it's all good. For the moment I'll stay on stock Google Android (as do my wife and daughter anyway), and on the 3a Graphene was awesome, but DivestOS is also nice.

                                                      Thanks all.