I tried to attach a photo of the Fastboot screen, cant do it at the moment.

so:

(this is all in the lower 1/3 of the screen)

Red triangle on top with a black exclamation mark in it.
(then)

Product revision: husky MP1.0 B1
Bootloader version: ripcurrent-14.5-12100691
Baseband version: g5300i-240308-240517-B-11857457
Secure boot: PRODUCTION
NOS production: yes
DRAM: 12GB Samsung LPDDR5
UFS: 256GB Kioxia
Device state: unlocked (in red text)
Boot slot: a
Enter reason: reboot bootloader
UART: disabled

    Sart Then its not possible to install GOS, apologies. If its unlocked/not a carrier version you can connect it to a wifi network and see if that works, but otherwise you cannot install GOS. We cannot help you install GOS until this is done, and if its a carrier version that prevents OEM unlocking, we cannot help you at all.

    • Sart replied to this.

      splattergames
      no phone not new and I will put a sim in the phone and connect to my laptop to check the internet. At the moment I have 2 phones connected to my laptop (no home internet), 1 phone (Samsung s8) is set up as a 'hotspot' my other phone is the target phone (Pixel 8 Pro).

      Sart okay, it seems like the bootloader is unlocked already. Have you tried the next step in the install (flashing)?
      Edit: disconnect other devices, that may interfere with the flashing process! The Pixel should be the only phone connected via USB to your host machine during flashing.

      • Sart replied to this.

        Sart

        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 (with Brave Shields disabled, since it caps storage usage at a low value to avoid fingerprinting available storage)

        Sart Did you download the udev rules and followed the rest of the instructions on the page? (assuming you are on Linux)

        Yeah I was just about to say that. To make sure nothing else is interfering with the WebInstaller, make sure to quit all other tabs, close all other programs (especially those that might also be talking to udev like RGB software or similar) and make sure that adb isn't interfering. You may run adb kill-server in the terminal to make sure.

        • Sart replied to this.

          I must sign-off now,
          THANK YOU EVERYONE,
          can we pick this up again tomorrow?

          Sart check if anything on your system is using that port. You can run sudo lsof -i :5037 and post the output (if any).
          Edit: probably nevermind; that indicates that adb server is not running in the first place...

          • Sart replied to this.

            Must go for now.

            Sart yeah. That's normal (see my edit). If you want to continue tomorrow, we can make a cut here.

            raccoondad

            hi, my phone was bought brand new from 'Giffgaff' the phone was in the unlocked state, phone is 2 months old now, 'Google' gave me the bootloader unlock command 2 days ago, so I assume everything is legit.