Thermos4940
Hi, I'm a Fedora user too, but I used my work laptop with Windows 10 to install GOS on my Pixel 6a.
Theoretically Fedora should work, but I preferred to avoid potential problems since it is not officially supported in the prerequisites.

      treequell Do you happen to have another Android device nearby? You could try connecting that phone to your Pixel with a USB-C to USB-C cable and running the flashing tool from that.

      I tried, does not work.

      eautalus Hi, I'm a Fedora user too, but I used my work laptop with Windows 10 to install GOS on my Pixel 6a.

      I will try first on Ubuntu and then on Windows

          • [deleted]

          • Post #11
          • Edited

          Hey there, I totally hear you on the struggles of installing GrapheneOS from a Linux machine. I tried to do the same thing and ended up having to use my sister's Windows 10 laptop to make it work.

          I found out that it was a necessary step to boot my Pixel 6a into fastboot and so install the Android driver by checking for updates and so clicking optional updates on the Windows machine to get the android driver.

          After installing the Android driver on here laptop and rebooting it, everything went smoothly from here browser with the GrapheneOS web-ui installer.

          In any case, just wanted to chime in and say you're definitely not alone in your experience!

            • [deleted]

            • Post #13
            • Edited

            Equal2024 oh wops, well the same thing should work as the google web installer needs drivers installed.

                [deleted] For my part, I installed GrapheneOS on Arch Linux with Sway and had no difficulties. It seems OP was able to install GrapheneOS with no difficulties, either (though they have not said this, it is implied); it's the Google Web Flashing tool they're having issues with. If Google released their flashing tool under a free license, it would be easier for developers to investigate why the tool was not working, but alas.

                @Thermos4940 Though this is unlikely to be related to the issue you're facing, make sure you've removed the GrapheneOS key before using the flashing tool; text from GrapheneOS web installer:

                The GrapheneOS factory images flash a non-stock Android Verified Boot key which needs to be erased to fully revert back to a stock device state. Before flashing the stock factory images and before locking the bootloader, you should erase the custom Android Verified Boot key to untrust it

                If you're having trouble using Google's web flashing tool, the docs provide some assistance: https://source.android.com/docs/setup/build/flash

                Here's one thing you haven't tried yet:

                Caution: If you have Android Debug Bridge (adb) installed on your machine, stop the adb service with the command below before proceeding as the service interferes with the flashing process.

                adb kill-server

                If you can't get the flashing tool to detect your device properly to select the right image to flash, no matter what, Google also gives you the option to flash the images manually: https://developer.android.com/about/versions/13/download#flash

                    Thermos4940

                    Which browser did you use? There's this paragraph on the GrapheneOS guid:

                    Officially supported browsers for the web install method:
                    Chromium (outside Ubuntu, since they ship a broken Snap package without working WebUSB)
                    Vanadium (GrapheneOS)
                    Google Chrome
                    Microsoft Edge
                    Brave
                    You should avoid Flatpak and Snap versions of browsers, as they're known to cause issues during the installation process.

                    In case any of that applies to your situation you could try to download chromium or brave (https://github.com/brave/brave-browser/releases/tag/v1.51.114) directly.

                    I used Arch to install GOS, so in case you're in for distro hopping Arch would be a safe bet.

                        Phead OP mentions they tried these browsers in the top post:

                        Chrome and Chromium

                        Edit: Ah, I see you're referring to whether they've used the Flatpak or Snap versions of the browsers; my bad. This might be the case, as they've used Fedora and Ubuntu. In addition to this, using a containerized version of a browser is not a good idea anyway, because it replaces the much more robust browser sandbox these browsers are using with the Flatpak or Snap sandbox; see some discussion here:

                        [0] https://discussion.fedoraproject.org/t/is-it-a-good-idea-to-replace-the-default-firefox-with-the-flatpak-one/30370/30
                        [1] https://discussion.fedoraproject.org/t/is-it-a-good-idea-to-replace-the-default-firefox-with-the-flatpak-one/30370/34
                        [2] https://seirdy.one/notes/2022/06/12/flatpak-and-web-browsers/

                            Equal2024

                            True but it was not stated if it was installed from flatpak or snap. Don't know if chromium or chrome is available on flatpak, just wanted to make sure though.

                                Phead This is definitely worth mentioning because Ubuntu absolutely uses the Snap version for browsers by default. I don't think Fedora does this for Flatpak, but Fedora Silverblue plans to do this.

                                  7 days later

                                  Thank you all!

                                  Phead I used Arch to install GOS, so in case you're in for distro hopping Arch would be a safe bet.

                                  Yes, ArchLinux would have been worth a try too. I originally used this to install Graphene OS.

                                  Equal2024 Edit: Ah, I see you're referring to whether they've used the Flatpak or Snap versions of the browsers; my bad. This might be the case, as they've used Fedora and Ubuntu. In addition to this, using a containerized version of a browser is not a good idea anyway, because it replaces the much more robust browser sandbox these browsers are using with the Flatpak or Snap sandbox; see some discussion here:

                                  I used the Chrome browser as the browser. I installed Chrome directly and neither as a flat pack nor as a snap. But it still didn't work.

                                  Equal2024 Here's one thing you haven't tried yet:

                                  Caution: If you have Android Debug Bridge (adb) installed on your machine, stop the adb service with the command below before proceeding as the service interferes with the flashing process.

                                  adb kill-server

                                  adb was not running at the time I tried this from different Linux systems. I had checked that. But it still didn't work.

                                  My Solution:

                                  The only thing that worked was finally installing Windows 11 and doing the whole thing from Windows. It was a hassle to install the correct drivers, but I managed.

                                  Equal2024 @Thermos4940 Though this is unlikely to be related to the issue you're facing, make sure you've removed the GrapheneOS key before using the flashing tool; text from GrapheneOS web installer:

                                  The GrapheneOS factory images flash a non-stock Android Verified Boot key which needs to be erased to fully revert back to a stock device state. Before flashing the stock factory images and before locking the bootloader, you should erase the custom Android Verified Boot key to untrust it

                                  Having already flashed Stock Android I almost forgot to wipe the Graphene keys, but luckily I remembered that at the last moment so I could do it before locking the bootloader again.

                                            Thermos4940

                                            Glad you found a solution. Could you elaborate on what you had to do to make it work with Windows 11? Just in case there are other users with similar problems.

                                                Phead Yes, I followed the Android Flash Tool instructions. I then had to install device specific drivers. In particular, I have followed the following instructions:

                                                1. I have loaded the manufacturer-specific updates for my PC (according to the instructions).
                                                2. I installed Android Studio and installed the USB drivers within Android Studio (according to the instructions).

                                                This has resulted in me being able to start the process. However, I then had to install more drivers after my Pixel rebooted and lost connection to my PC. Unfortunately, I can't reconstruct exactly what that was, but I more or less followed the troubleshooting instructions on the screen. Sorry, it's been over a week now and I've been busy setting up my system in between.

                                                I hope this also helps others who are facing this problem.

                                                Thank you all for your great support!

                                                    Thermos4940

                                                    Thanks you! Always good to have some sort of a starting point when trying to troubleshoot a specific problem.

                                                      a year later

                                                      Thermos4940 This allows Android Flash Tool to connect and the process actually starts. But, as soon as the device reboots it loses the connection.

                                                      I also ran into this issue on Fedora. It seems that the Flash tool being able to work with the phone after it reboots into the bootloader is equivalent to fastboot devices working without sudo, which it doesn't by default.

                                                      Various places around the web point to 'udev rules' to fix similar issues. Fedora's android-tools package includes a set of udev rules in a doc folder, which you can symlink to /etc/udev/rules.d to make them take effect, but these rules only work for adb, they don't change anything for fastboot!

                                                      I followed these instructions to create a different kind of udev rule manually, plus a bit from this forum post to create a plugdev group and add my user to it. After rebooting my laptop, fastboot devices and the web flashing tool both worked.