Google Pixel 8 - eOS Installation issue (Shiba)

Hi @ITSME,
Thank you for your response.
I have shared my feedback to improve the installation guide that might help you :slight_smile:
Here are my feedback : Google - Pixel 8 - shiba - Documentation Suggestions - #15 by Anonymous
Have a nice day

I found my way here after, making the same mistake as OP. The web installer made it a little to easy to jump in without me making all the necessary checks about A14 / A15. It is a phone I bought to replace my current working one so I’m not in a crunch to get it working, my question is the following. If I wait for the /e/OS-a15-official release will it work to install from the web installer with the Pixel 8 in the state it is now or will I have to do this Git-Bash stuff to get the device back to a state where the web installer can start from stock android?

Hi smc5199, maybe you can clarify what Android version your Pixel 8 is in at the moment? A15?
Also, what is the state of your device now? Blocked in FastBoot menu? Or can you start it normally on Android stock?
This would help to further assist you.
Regarding the possibility to install eOS A15 official with the eInstaller, I’m not sure maybe Piero will be able to answer here but the Git-Bash process is easier than it sounds, even without much understanding on how scripts works :wink:

I am not actually sure which version of Android the Pixel 8 was running. It was new to me from Swappa.com and I started to web flash it before ever realizing it was something I should know. I can’t tell now because it is in the state that OP described in the second paragraph and provided a picture for.

I cannot access RECOVERY MODE. Indeed, when I select Recovery Mode from the Fastboot menu, the phone displays a screen indicating that the ā€œbootloader is unlockedā€¦ā€ (See the photo below), then briefly shows the Google logo before rebooting continuously on this same screen (2 or 3 times). It then returns to the Fastboot menu.

I think that would be blocked in fastboot, I can’t start it normally to Android stock. That’s encouraging that Git-Bash is probably manageable if required.

@smc5199, welcome.

While you might have the same issue as OP … maybe your situation could be resolved (or made more clear) as [Solved] Windows does not see my phone in Fastboot mode ??

… but likely you will have to resolve the Android version issue … manual install puts one in control.

In this case, I would recommend installing Android Stock OS to know which version of Android (14,15,16) you currently have on your device.
You can do so with the Android web installer. I would recommend trying with flashing A14 first and see if you can proceed or if you have the anti roll-back message. If A14 works well and good otherwise try to flash A15 :slight_smile:
Then you can try to flash the related eOS firmware (A14 or A15).

Alternatively you can try the command line install (with Git-Bash) of the eOS A14 and eOS A15 and see which on works :slight_smile:

Good luck!

Thank you, was able to get it with the Android web installer. It’s on stock A15, A14 was rollback blocked.

For my next step, if I were to install eOS A15 with Git-Bash would I have to do it a second time when eOS A15 goes from a Community Build to an Official build? Or if I’m on the eOS A15 it will just be more frequent OTA updates once it moves to having official build status?

If you install the eOS A15 Community Build you’ll need to erase the data to switch to the eOS Official Build as mentioned by Piero here.
eOS Official Build should be released this week so better to wait and install it once available.

1 Like

Hi. I own a pixel 8 (shiba) with Google stock Android 15, security patch May 5, 2025.
Which means anti roll back is activated.
I would like to install /e/OS 3.2 Android 15 official.
I do fear one thing : bricking this (expensive) device.
Has someone managed to do so, starting from the May 5, 2025 update, with zero risk/problem, using the Linux script, preferably, or with the /e/OS online installer?
Thx.

I was on this one 15.0.0 (BP1A.250505.005.B1, mai 2025) and did the official update manually with the terminal without any problem.
It was (when I updated my phone) still using the 3.1.4 on the online installer.

I did the update manually from /e/OS 3.2 A15 community to /e/OS 3.2 A15 official without any issue.
Please note : it did erase all the data of the device !

via recovery or local update ?
or
via fastboot install script ?

via the command line and GitBash, device on fastboot mode

why it did erase all the data of the device !

I guess that was when I lock the bootloader after the install

1 Like

Is this the Linux script method found in the eOS archive/zip download?