Pixel 8 Shiba issue to lockback the bootloader

/e/OS Devices Google
1

Hi community! I just bought a 2nd hand Pixel 8 to swiitch to e OS.I was quite sad because the web installer could’nt establish communication with the Pixel, even after I downgraded from A16 build to the last A15 build I found, using Android Flash Tool.

So I decided to follow these steps: Install /e/OS on a Google Pixel 8 - “shiba” using the A15 official build.
It worked smooth, and after using Git Bath to flash the image the phone did boot on Murena OS.

BUT now I cannot do the step “Locking the bootloader” because the phone is not recognized by my computer, when I use a cmd prompt “C:\platform-tool>fastboot devices” nothing appears, and I have a issue message when plugging the usb to the computer. I did activate in e OS option the USB debogging mode etc.

I think I could use some help!

Thanks, Celes

Edit:
In the USB menu of the phone, I cannot choose “use USB for… transfer file/MTP”, the menu is blocked on “No data transfer”. I imagine it can be linked to the issue

2

are you sure of the cable ?

have you tried using git-bash

please share photo

1 Like
3

Do you have a fastbboot drivers problem ? [Solved] Windows does not see my phone in Fastboot mode

You can only change this while a data cable is connected between device and PC.

1 Like
4

Thanks for the answers. Yes the cable OK is fine it’s the one from the pixel box, I used it to flash e OS before.

I did’nt try using GIT Bash for the fastboot prompts (not used to the “gramar” of git bash").

Here are the photos:

erreur windows
erreur windows580×340 11.3 KB

Sorry it’s in french.

Do you have a fastbboot drivers problem ? [Solved] Windows does not see my phone in Fastboot mode

With the phone in fastboot mode (using power + volume down), I can’t see the phone neither in the Device manager window. So I can’t fix possible driver issue

You can only change this while a data cable is connected between device and PC

Yes usually it works changing it when connected but here no, the options are in grey.

EDIT:
I had to reset USB-debugging authorizations and it worked smooth after that. Thanks for the help!

2 Likes