Help needed installing ROM on Pixel 2 XL

If someone can help me to get /e/ on my Pixel 2 XL. After flashing and rebooting it just stop in bootloader. Whatever I do will not boot. Here is my steps, please let me know if I did something wrong.

  1. Flash latest factory 8.1 image
  2. Boot in TWRP and clean cache, system and format data
  3. Reboot in TWRP, adb push latest /e/ rom and flash
  4. Adb push and flash TWRP zip, clear cache and reboot system

After that it will just stop in bootloader again. I did try with same steps some older versions of /e/ for Pixel 2 XL but it is exactly the same. I don’t really know what is wrong here. On my old Oneplus X I did not have any of this and I was so happy with it but here on Pixel 2 XL it’s just refuse to work…

Update:
I did try with different versions of TWRP and also with older versions of factory images (like 8.0).
At one point I get /e/ boot animation but after a minute will just restart. Loading did never finish.

Also I did try with sideload but that give me same results. Sometimes TWRP is showing a message like there is no OS are you sure you like to reboot?..

I would like to know exactly version of factory image I need to use before flashing /e/ and best TWRP version to flash with.

Hi @rhunault please can someone help @emilius install /e/ on hi Pixel 2 XL

Hi @emilius if you reboot at this point what happens?

@emilius you can reboot if TWRP shows you this message. It happens sometimes that it does not detect the system installed. Please tell us if it works after reboot.

Thank you for help @rhunault and @Manoj
After reboot the system will not boot.It will go back to bootloader. Sometimes I get /e/ boot animation but after about 2 minutes will restart again in bootloader.

I am not sure what factory image I should have before I flash /e/. I did tray with 8.0, 8.1 and 9.0. Is there specific version I should have?

Prefer installing a 8.1 factory image, as /e/ Oreo is based on this version.

Yes, that is how I did it first time. After flash it will just show boot animation and after 2 minutes will reboot to bootloader. This is the order how I did it

  • flash latest 8.1 factory image on A and B slots and let it boot once
  • fastboot boot TWRP, clean cache, system and format data
  • sideload e
  • sideload TWRP
  • reboot system

That procedure should work on any rom installation, it is 100% clean install but it is not working with e rom. I am wondering if anyone else with Pixel 2 XL have this problem?

I did another try with latest e form 05/07 and it is still the same. The phone will start booting, e animation is happening for about 2 minutes and then the phone just restarts to recovery. What else I can try?

The procedure seems good. Only thing strange: what do you mean exactly by sideload TWRP?

That is flashing TWRP (adb sideload twrp-pixel2-installer-taimen-3.3.0-0.zip)
First time I have to boot to TWRP (fastboot boot twrp-3.3.0-0-taimen.img) and then flash it from TWRP (adb sideload twrp-pixel2-installer-taimen-3.3.0-0.zip) but I did it with sildeload avoiding copying (push).

A/B devices have to boot to TWRP first and then flash. That part is also wrong in “how to flash” procedure for taimen. Flashing recovery from fastboot is for older devices I think. That is how I flash TWRP on my OnePlus X.

Hi @emilius and @rhunault , I have had the same difficulties getting e os to boot on the taimen and wanted to contribute a bit more of what I have tried. I have used every build listed:

  • e-0.5-o-201905129807-dev-taimen.zip ( does not progress past boot logo )
  • e-0.5-o-201905109628-dev-taimen.zip ( does not progress past boot logo )
  • e-0.5-o-201905079429-dev-taimen.zip ( does not progress past boot logo )
  • e-0.5-o-201905069220-dev-taimen.zip ( stops at boot animation, then reboots after several minutes )
  • e-0.5-o-201905049014-dev-taimen.zip ( stops at boot animation, then reboots after several minutes )

In addition to clean installs from both 8.0 and 8.1 factory images, I also tried flashing the successive e os builds on top of the previous to see if there would be any change, without any luck. It seems like there is some trouble with the device images that are causing the same problems that @emilius and I are having with installation.

@anon64684597 so I am not the only one. Good to know. I am wondering how is this community builds getting tested? Is there something we don’t know?

@Manoj @rhunault @barczakmark I have tested latest e-0.6-o-2019051710440-dev-taimen.zip and it is still the same. Not possible to boot, bad flash.

Hi,

We are sorry for problem you are facing of. Could you please raised an issue here?

I did that long time ago, that is the first place I posted this issue here.

Did anyone manage to this working? I’m faced with the same issue. TWRP flashes the ZIP just fine, but says there’s no OS installed and a reboot just goes back to the bootloader.

@Manoj @rhunault this issue is still there. To bad, I was really looking forward to this ROM. I end up flashing COSP ROM with NanoDroid. More or less same thing :wink:

I am having similar issues with /e/ on my Pixel 2. I tried to install /e/, got the boot logo for about 10 minutes, and the phone rebooted into recovery. I reinstalled the e 0.7 .zip file and again got the /e/ boot logo for about 15 minutes. The device rebooted and gave me a prompt with a LineageOS logo stating “Can’t load Android system” and “your data may be corrupt” and asking me to factory data reset the device.

I reset the device from the prompt. The phone then rebooted, gave the /e/ logo for about two minutes, and rebooted again into the LineageOS recovery screen I previously mentioned.

Are you by any chance downgrading your phone - or was it on Pie OS earlier. We have seen such bootloop issues on most devices when we try to downgrade the OS.

I was on the Android 10 beta, but installed the current stock Android Pie ROM before trying to install /e/.

I followed the steps listed in this XDA post, just replacing the LineageOS ROM with the /e/ ROM I built.

Edit: As an experiment, I tried installing the LineageOS ROM in the XDA post I linked above and it successfully booted. It seems like there is some issue in the /e/ ROM specifically.