Install /e/OS on a Google Pixel 2 - “walleye”
The instructions in this guide will assist you to install /e/OS on your walleye. Please read through the instructions at least once before actually following them, so as to avoid any problems later.
It is important that you know that downgrading Smartphones on OS versions greater than the /e/OS OS version you plan to install, can cause instability or at worst brick some devices. We recommend that you check your current OS version, before attempting the installation.
It is advisable to flash your device only if you know what you are doing and are ok taking the associated risk. All /e/OS builds are provided as best effort, without any guarantee. The /e/OS project and its project members deny any and all responsibility about the consequences of using /e/OS software and or /e/OS services.
Requirements
- If required take a backup of all important data from your phone on an external storage device before proceeding.
- Do not take a backup on the same device as some of these actions will format the device and delete the backup.
- Ensure your phone is charged more than 50%
- Check that
adb
andfastboot
are enabled on your PC. If not you can find the setup instructions here - Download all the files and images mentioned in the download section below before starting the installation
-
Make sure you have a working data cable to connect your device to the PC. There are cables which are only for charging and do not transfer data.
- Enable USB debugging on your device. You can find the instructions here
- Make sure that your model is listed in the Smartphone Selector. Check the model supported. Where available, information on the model supported should show as a pop-up when you hover the cursor on the Device name. The model number supported should be the exact same.
- Boot your device with the stock OS at least once and check every functionality.
Please share your experience , suggest tips or changes to this install guide documentation by visiting the Pixel 2 specific topic on our community forum.
To report issues in /e/OS please refer this guide
Downloads for walleye
-
/e/OS build : T community
To understand the difference between /e/OS builds check this guide
Unlocking the bootloader
-
Enable OEM unlock in the Developer options under device Settings, if present.
-
Connect your device to your PC via USB.
- On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
- Con il dispositivo spento
- premi Volume Giù + Accensione
- Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
Tip: If you seeno permissions fastboot
while on Linux or macOS, try runningfastboot
as root. -
Now type the following command to unlock the bootloader:
fastboot flashing unlock
-
If the device doesn’t automatically reboot, reboot it. It should now be unlocked.
- Since the device resets completely, you will need to re-enable USB debugging to continue.
Temporarily Booting a custom recovery using fastboot
-
Before proceeding ensure you have downloaded the custom recovery from the link given in the Download section above
-
Connect your device to your PC via USB.
- On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
- Con il dispositivo spento
- premi Volume Giù + Accensione
- Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
- If you see
no permissions fastboot
while on Linux or macOS, try running fastboot as root - Some devices have buggy USB support while in bootloader mode. If fastboot hangs with no output when using commands such as
fastboot getvar
.. ,fastboot boot
…,fastboot flash
… try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub
- If you see
-
Flash a recovery image onto your device by typing
fastboot flash boot recoveryfilename.img
Sostituisci
recoveryfilename
con il nome file dell’immagine della recovery che hai scaricato nella sezione precedente - Now reboot into recovery to verify the installation:
- Con il dispositivo spento
- premi Volume Giù + Accensione e scegli Modalità Recovery.
Steps to install /e/OS from recovery
Advanced
» Enable adb
Format the device
On /e/OS Recovery main screen:
- Select
Factory reset
- Select
Format data / Factory reset
option - Next screen will display a warning that this action cannot be undone
- Select
Format data
to proceed orCancel
if you want to go back -
If you selected
Format data
, the format process will completeTip: You will see text in small font on the lower left side of the screen mentioning format progressThe small font text would be similar to this
Wiping data Formatting/data Formatting/cache Data wipe complete
- Display will now return to the Factory Reset screen
Install /e/OS
In /e/OS recovery main screen:
- Select
Apply Update
and in next screenApply update from adb
-
In the next screen, the device is now in sideload mode
Note at this point the Cancel option is highlighted that does not mean you have canceled the action. The device is in adb sideload mode.
-
On your PC type begin adb sideload. Type the below command in a console
adb sideload downloaded_file_name.zip
Replace downloaded_file_name.zip with the name of the /e/OS file you downloaded in the previous section
- Press
enter
key on the keyboard to start the sideloading The screen will show the progress percentage…This might pause at 47% - Give it some time
- The PC console will now display
Total xfer: 1.00x
- The phone screen will now display some text with a message similar to
Script succeeded result was [1.000000]
This means that the install was successful.
Reboot the device
In /e/OS recovery main screen:
- Select
Reboot system now
The reboot process may take 5 - 10 minutes
To find some troubleshooting tips… click here
adb
- Getting a
Total xFer ':' 0.01x
message - Try to upload the /e/OS to internal storage and retry to install adb ':' sideload connection failed ':' insufficient permissions for device
error - Try to execute the commandsadb kill-server
andadb start-server
and retry- Running
adb shell twrp install /sdcard/</e/OS zip package>
raise non-existent directory error - Try to check solution here - Getting an
insufficient permissions
error - Try the solution given here - When running "adb devices" in bash a device is shown as "unauthorized" - Try the solution given here
TWRP
- Errors while running TWRP version 3.4.x.x or above - Try downloading and using a previous TWRP version.. below 3.4.x.x
- In TWRP if this error shows up
failed to mount /preload
- Try in TWRPwipe
screen in advanced menu selectpreload
andswipe to wipe
/cache/recovery/xxx -> no such file or directory
error while flashing a ROM - On PC runadb shell
in the console now create a folder called recovery for e.g. here the devicecode name is violet "violet :/cache# mkdir recovery"
Connectivity
- Trying to troubleshoot mobile connectivity issues - Read this guide
Still need help to complete the installation ?
Check out this document: An install Guide for the walleye
Please share your experience , suggest tips or changes to this install guide documentation by visiting the Pixel 2 specific topic on our community forum.
To report issues in /e/OS please refer this guide
This documentation “Installa /e/OS su un Google Pixel 2 - “walleye”” is a derivative of “install LineageOS on walleye” by The LineageOS Project, used under CC BY.