Pixel 7 install issues

arldn

I got a brand-new Pixel 7 that I've tried several different ways to install GrapheneOS, but nothing seems to work. I've managed to get the bootloader unlocked, but that it. I've tried the following:

1) CLI install from Ubuntu - This unlocked the bootloader, but then when I tried running the flash-all.sh script, both the phone and the terminal I ran the script from didn't output anything for over an hour so I assume that it wasn't working.

2) Web install on Windows 10 using Brave - Windows saw the Pixel 7 when the Pixel was booted up into the factory Google boot image and then Windows installed the correct driver. Then when I booted into the bootloader and tried the "Download release" button (I skipped the bootloader unlock since it was already unlocked from above), I get a popup window in Brave saying "grapheneos.org wants to connect" and "No compatible devices found". Then in the main browser window it says "Error: Failed to execute 'requestDevice' on 'USB': No device selected."

3) Web install on Fedora using Brave - same result as #2.

4) Web install on Fedora using Chrome - same result as #2.

5) CLI install from Windows 10 - flash-all.bat output is stuck at "< waiting for any device>".

I've mainly used the USB-C -> USB-C cable that came with the Pixel but I've also tried using a different USB-A -> USB-C cable.

Any suggestions?

de0u

arldn For USB, are you plugging into a motherboard port on your PC, as opposed to a hub? Also note that on some PCs the front panel USB ports are indirect. Overall it sounds most like a connection problem. If you are running any of these OSs in virtualization that could be trouble.

de0u

arldn I have no idea what's going wrong. But I think it might be useful to pick one configuration and provide as much detail as humanly possible. For example, this description:

CLI install from Ubuntu - This unlocked the bootloader, but then when I tried running the flash-all.sh script, both the phone and the terminal I ran the script from didn't output anything for over an hour so I assume that it wasn't working.

...doesn't say what flash-all.sh had said before it got stuck. Posting a transcript of the complete flash-all.sh run might be illuminating. And starting the transcript "a little early" might help too -- I guess in this case it would be good to know that signify signed off on the download, because that is stellar verification that the image download actually succeeded without incident.

Maybe also report details of your machine configuration(s)? Which version of Ubuntu, which version of Fedora, how much RAM on the machine, how much free disk space?

arldn

None of the machines are VMs. I initially used a front USB port on the Windows machine, but I've also tried a rear port that's mounted on the motherboard. The Fedora machine is a laptop.

W1zardK1ng

In windows 10
USB debugging and try to run adb devices - it should detect your phone
then run adb reboot bootloader, later run fastboot devices - it should detect your phone

If any of this not detecting your phone, mostly you have issue with the driver software.
also you can try using a usb 2.0 port and cable.

https://developer.android.com/studio/run/win-usb
https://developer.android.com/studio/run/oem-usb#InstallingDriver

arldn

When the phone is at the bootloader:
adb devices prints "List of devices attached" and then nothing else.
adb reboot bootloader prints "error: no devices/emulators found"

However, if I boot to the factory Google Android, enable USB debugging on the phone and run adb devices -l I get the following:

PS C:\Users\ARLDN\Downloads\panther-factory-2023031500> adb devices -l
List of devices attached
2C031FDH200JRG device product:panther model:Pixel_7 device:panther transport_id:1
PS C:\Users\ARLDN\Downloads\panther-factory-2023031500>

So I don't think the problem is the USB cable.

W1zardK1ng

arldn
adb devices command works only when the phone is powered on, its detecting your phone so that's good.
when phone is in bootloader you need to run fastboot devices command to see if it detects the phone.
Even when you are in bootloader, it should detect your phone.
Try opening Device Manager in windows when you are in bootloader and see if there an device as Android with a warning symbol.
https://beebom.com/fastboot-not-detecting-device-windows-10/

It will be nice if you can join the official chat rooms on Matrix, so that you can troubleshoot things in real time.

de0u

W1zardK1ng https://beebom.com/fastboot-not-detecting-device-windows-10/

That page is potentially alarming, since it recommends downloading a Windows driver from a Google Drive folder apparently controlled by the author of that page. Naively I would expect to be directed to download something like that from either an official Google page or an official Microsoft page. I am not familiar enough with Windows security to know how concerning this might be, but it does seem odd!

arldn

...doesn't say what flash-all.sh had said before it got stuck.

It didn't print anything to the screen.

Maybe also report details of your machine configuration(s)? Which version of Ubuntu, which version of Fedora, how much RAM on the machine, how much free disk space?

Initially I tried my Windows 10 desktop (32 GB RAM), when that didn't work I tried my Fedora 37 laptop (16 GB RAM). Both have several hundred GB free disk space. When I saw that Fedora wasn't an officially supported OS, I tried an Ubuntu 22.04.2 LTS Live CD on the laptop, which is what ended up unlocking the bootloader. That's where I ran the flash-all.sh

I tried the chat room first, and one of the people there walked me through a bunch of troubleshooting steps, but nothing worked.

Try opening Device Manager in windows when you are in bootloader and see if there an device as Android with a warning symbol.

There was a Pixel 7 with a warning symbol. When I booted the phone to the stock Google Android, the warning symbol went away. I checked Windows Update and it had optional updates for "LeMobile - Other hardware - Android Bootloader Interface" and "LeMobile - Other hardware - Android Composite ADB interface", so I applied those. Now when the phone is at the bootloader, it shows up in Device Manager as an "Android Bootloader Interface", and now when the phone is booted it doesn't appear to show up in Device Manager at all.

arldn

Currently when the phone is at the bootloader, this is what I'm getting:

PS C:\Users\ARLDN\Downloads\platform-tools> fastboot devices
2C031FDH200JRG fastboot
PS C:\Users\ARLDN\Downloads\platform-tools> adb devices -l
List of devices attached

PS C:\Users\ARLDN\Downloads\platform-tools>

arldn

When the phone is booted with USB debugging enabled, this is what I'm getting:
PS C:\Users\ARLDN\Downloads\platform-tools> adb devices -l
List of devices attached
2C031FDH200JRG device product:panther model:Pixel_7 device:panther transport_id:8

PS C:\Users\ARLDN\Downloads\platform-tools> fastboot devices
PS C:\Users\ARLDN\Downloads\platform-tools>

arldn

!!!!

I think adding the LeMobile device updates fixed the issue. I was able to flash the image and the phone is currently booted into GrapheneOS.

biznfo

I am trying to install to a Pixel 7. I downloaded the panther release. Then I clicked Flash release. I got a message "Finding latest release..." and then it timed out "Error: Timeout of 10000 ms exceeded". Is there a way forward?

biznfo

biznfo I restarted the bootloader and flashed again. It is running now.

mballon

biznfo
Thank you this helped me also !

Jeanclaud

Same prob here, I tried to install Graph from a mac and my pixel 5 running graphene with the same resuIt (unrecognized device). I must ad that I have installed all my phones to Graphene since my old pixel 3 with absolutely no problem