• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata)

Search This thread

invisiblek

Recognized Developer
Feb 24, 2010
1,584
5,896
Minnesota
www.invisiblek.org
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.

It should go without saying, but do not lock your bootloader with this installed. You must be 100% stock, I'd suggest on both slots, in order to re-lock your bootloader. Doing otherwise will likely lead to a brick that Essential really shouldn't warranty.

Code:
#include <std_disclaimer.h>

/*
 * Your warranty is now void.
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

Unofficial LineageOS Builds
Essential PH-1 (mata): https://updater.invisiblek.org/mata

Google apps
Google apps (opengapps nano) are baked in to these builds. This is due to the A/B partition layout and complications backing up/restoring gapps between builds. This is not ideal, and is the major road block to getting this device in to official status with Lineage. At this time I do not plan to release non-gapps builds. Users who require this will have to build their own.

Source
Device | Kernel
Here's a local_manifest for those who want to build at home.

Prerequisites
  • Unlocked bootloader
  • OPM1.180104.092 firmware - even if you were on this build, you should flash this firmware package to ensure the firmware is on BOTH slots.
  • Fastboot and ADB set up (use your google-fu to figure this out)

Installation
This device is different than what most people are familiar with due to the A/B partition layout. If you're familiar with Pixel devices, then you already know what this means. This thread isn't really designed to explain how it all works, that should be handled somewhere else. Instead, I'll assume you can either follow directions or do some research on your own. Additionally I have a discord set up where there are several people who may be able to help if you run in to a snag.

The initial install should go rather smooth, and future updates can be taken through the built-in Lineage updater app (yes, the are the seamless updates you may have heard about). Due to A/B, the recovery's ramdisk is actually on the boot.img partition (the rom's ramdisk is on the system partition now). What this means is once you flash the rom, it essentially (lol) replaces the TWRP that you have installed. This shouldn't be a problem since with the seamless updates, you shouldn't have to ever go into recovery. If you find yourself needing recovery, you'll have to re-flash TWRP to get there.

Phew, now some instructions.

  • See the prerequisites. You really do need these or things aren't going to work for you.
  • Boot into bootloader mode and wipe data with:
    Code:
    fastboot -w
  • Download twrp (mirror) and flash it with this command:
    Code:
    fastboot flash boot twrp-mata_11.img
    (no, this isn't a typo, you are flashing twrp to the boot partition)
  • While still in bootloader mode, use vol down to select "Recovery mode" and hit the power button. This should boot you in to TWRP. Enter your previous lock screen password or pin (if it asks) to decrypt your data partition.
  • Put the device in sideload mode with:
    Code:
    adb shell twrp sideload
  • Install the zip via adb sideload with:
    Code:
    adb sideload <zip name here>
  • When finished, reboot.
  • Profit!

The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

XDA:DevDB Information
[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata), ROM for the Essential Phone

Contributors
invisiblek
Source Code: [url]https://github.com/LineageOS[/URL]

ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x

Version Information
Status: Testing

Created 2017-11-12
Last Updated 2017-11-11
 
Last edited:

invisiblek

Recognized Developer
Feb 24, 2010
1,584
5,896
Minnesota
www.invisiblek.org
  • Q: What is broken?
    A: Nothing I'm aware of
  • Q: Can I use the stock Essential camera app?
    A: Yes
  • Q: Does the 360 cam work?
    A: No.
  • Q: Is this rooted?
    A: No. You're on your own for that.
  • Q: Does this pass SafetyNet?
    A: Yes. Android pay, Pokemon Go, etc work fine. If you root, depending on your root method, you may lose this ability. But the ROM itself does pass SafetyNet.
  • 2017-11-20 FAQ rollup: https://forum.xda-developers.com/showpost.php?p=74580036&postcount=189
  • FAQ site with some more info (be gentle with the terrible, or should i say complete lack of, css)
 
Last edited:
T

TheF|ipSide

Guest
"Why no work" bug reports incoming in 5,4,3,2,1....
EDIT: @invisiblek if you need this post for anything, let me know.
 
Last edited:

mrcooter

Senior Member
First time with an A/B device, so everytime you update with a new build to the updater site it will prompt us and begin updating in the background? Don't have to be specific with the process itself but I was just curious as I'd like to stay up to date as possible if I start the custom ROM endeavor since it's still early on in development. Thanks!
 

CaptainElwood

Senior Member
Jan 6, 2012
137
35
Thanks OP!
Got it up and running, seems pretty solid for the first build. The initial setup wizard hung at the last step for me but after a reboot it worked.

Oh, and the night mode works great!

^TWRP link worked for me about 30 mins ago

Update: I have installed most all of my apps and have been playing around setting up the phone for the last ~30mins....no stutters, no mistouches, everything is working great. LTE+ on VZW works, as well as Verizon messaging app. The phone apk has the option for vvm, haven't tested. Overall I can't believe how well this runs...ROM development has come a long way from the initial releases I'm used to on non nexus devices.
 
Last edited:

strictlyphat

Senior Member
Jan 19, 2008
929
184
Thanks OP!
Got it up and running, seems pretty solid for the first build. The initial setup wizard hung at the last step for me but after a reboot it worked.

Oh, and the night mode works great!

^TWRP link worked for me about 30 mins ago

Update: I have installed most all of my apps and have been playing around setting up the phone for the last ~30mins....no stutters, no mistouches, everything is working great. LTE+ on VZW works, as well as Verizon messaging app. The phone apk has the option for vvm, haven't tested. Overall I can't believe how well this runs...ROM development has come a long way from the initial releases I'm used to on non nexus devices.

Same feelings here. I really hope vvm works. Will test tomorrow... The ROM already kept me up tik now 3:09am

---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------

Also on vzw don't see LTE + though.
 

omvir

Senior Member
Apr 28, 2011
1,229
528
Has installing lineage fixed the low signal strength problem for those people that have been experiencing it?

Sent from my ONEPLUS A5000 using Tapatalk
 

tclaybor

Member
May 30, 2017
12
7
Works great! Found a wifi bug

Following the instructions posted, wifi stops working after flashing twrp and rebooting back into LOS. I flashed addonsu-14.1-arm64-signed.zip to enable App access to root. It worked, but wifi is broken on reboot. It turns itself off immediately after turning on.

Replication steps:
1. Follow steps in OP.
2. Reboot to bootloader (adb reboot-bootloader)
3. Flash twrp_mata-6.img (fastboot flash boot twrp.img)
4. adb push addonsu-14.1-arm64.zip /sdcard/
5. Install .zip in TWRP
6. Reboot

Anybody else getting this issue? The only way I've been able to fix it is to re-flash LOS.

EDIT: Thanks to @bmg1001, this issue is resolved (for me at least) by using this build of TWRP... Sorry, I can't post links yet! Can someone link this please?

https:// drive.google. com/file/d/1Pp9Hep-EEGNHLl6I_ob7ugihpKfrAcWm/view?usp=sharing

Note that flashing this TWRP build will allow you to reboot to recovery at any time without having to reflash TWRP, as mentioned in the OP.
 
Last edited:

tclaybor

Member
May 30, 2017
12
7
Has installing lineage fixed the low signal strength problem for those people that have been experiencing it?

Sent from my ONEPLUS A5000 using Tapatalk

My signal strength improved from 2 bars to 3 bars at home, but I'm not sure if the reception has improved or just the number of bars displayed at certain signal strengths..
 

makbomb

Senior Member
Feb 23, 2014
118
39
New York City
TWRP DL link not working

Following the instructions posted, wifi stops working after flashing twrp and rebooting back into LOS. I flashed addonsu-14.1-arm64-signed.zip to enable App access to root. It worked, but wifi is broken on reboot. It turns itself off immediately after turning on.

Replication steps:
1. Follow steps in OP.
2. Reboot to bootloader (adb reboot-bootloader)
3. Flash twrp_mata-6.img (fastboot flash boot twrp.img)
4. adb push addonsu-14.1-arm64.zip /sdcard/
5. Install .zip in TWRP
6. Reboot

Anybody else getting this issue? The only way I've been able to fix it is to re-flash LOS.

EDIT: Thanks to @bmg1001, this issue is resolved (for me at least) by using this build of TWRP... Sorry, I can't post links yet! Can someone link this please?

https:// drive.google. com/file/d/1Pp9Hep-EEGNHLl6I_ob7ugihpKfrAcWm/view?usp=sharing

Note that flashing this TWRP build will allow you to reboot to recovery at any time without having to reflash TWRP, as mentioned in the OP.

Good Morning!

The URL for TWRP isn't working for me. I copy pasted it in chrome address bar. Could someone please kindly help? I'm drooling to get started! :D
 

strictlyphat

Senior Member
Jan 19, 2008
929
184
Good Morning!

The URL for TWRP isn't working for me. I copy pasted it in chrome address bar. Could someone please kindly help? I'm drooling to get started! :D
Go to the rooting guide and it's in there. Use the mirror

---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------

One thing I noticed is cell service is much weaker so far. In this same spot if my bedroom used to go from 99 to 103 dbm. Now it's at a118. Will monitor and report.

Shows 0 bars of service. Used to be 2-3
 
  • Like
Reactions: makbomb

strictlyphat

Senior Member
Jan 19, 2008
929
184
Thanks, but it sounds like @tclaybor is using a different version, provided to him by @bmg1001 , since you'll see he was trying to link a google drive to that version?
The one in bmg1001 thread worked. But have to click mirror.

---------- Post added at 02:54 PM ---------- Previous post was at 02:54 PM ----------

If u do get it installed let me know about signal. Mine taking big hit.
 
  • Like
Reactions: makbomb

Top Liked Posts

  • There are no posts matching your filters.
  • 109
    LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.

    It should go without saying, but do not lock your bootloader with this installed. You must be 100% stock, I'd suggest on both slots, in order to re-lock your bootloader. Doing otherwise will likely lead to a brick that Essential really shouldn't warranty.

    Code:
    #include <std_disclaimer.h>
    
    /*
     * Your warranty is now void.
     *
     * We are not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at us for messing up your device, we will laugh at you.
     *
     */

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

    Unofficial LineageOS Builds
    Essential PH-1 (mata): https://updater.invisiblek.org/mata

    Google apps
    Google apps (opengapps nano) are baked in to these builds. This is due to the A/B partition layout and complications backing up/restoring gapps between builds. This is not ideal, and is the major road block to getting this device in to official status with Lineage. At this time I do not plan to release non-gapps builds. Users who require this will have to build their own.

    Source
    Device | Kernel
    Here's a local_manifest for those who want to build at home.

    Prerequisites
    • Unlocked bootloader
    • OPM1.180104.092 firmware - even if you were on this build, you should flash this firmware package to ensure the firmware is on BOTH slots.
    • Fastboot and ADB set up (use your google-fu to figure this out)

    Installation
    This device is different than what most people are familiar with due to the A/B partition layout. If you're familiar with Pixel devices, then you already know what this means. This thread isn't really designed to explain how it all works, that should be handled somewhere else. Instead, I'll assume you can either follow directions or do some research on your own. Additionally I have a discord set up where there are several people who may be able to help if you run in to a snag.

    The initial install should go rather smooth, and future updates can be taken through the built-in Lineage updater app (yes, the are the seamless updates you may have heard about). Due to A/B, the recovery's ramdisk is actually on the boot.img partition (the rom's ramdisk is on the system partition now). What this means is once you flash the rom, it essentially (lol) replaces the TWRP that you have installed. This shouldn't be a problem since with the seamless updates, you shouldn't have to ever go into recovery. If you find yourself needing recovery, you'll have to re-flash TWRP to get there.

    Phew, now some instructions.

    • See the prerequisites. You really do need these or things aren't going to work for you.
    • Boot into bootloader mode and wipe data with:
      Code:
      fastboot -w
    • Download twrp (mirror) and flash it with this command:
      Code:
      fastboot flash boot twrp-mata_11.img
      (no, this isn't a typo, you are flashing twrp to the boot partition)
    • While still in bootloader mode, use vol down to select "Recovery mode" and hit the power button. This should boot you in to TWRP. Enter your previous lock screen password or pin (if it asks) to decrypt your data partition.
    • Put the device in sideload mode with:
      Code:
      adb shell twrp sideload
    • Install the zip via adb sideload with:
      Code:
      adb sideload <zip name here>
    • When finished, reboot.
    • Profit!

    The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

    XDA:DevDB Information
    [ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata), ROM for the Essential Phone

    Contributors
    invisiblek
    Source Code: [url]https://github.com/LineageOS[/URL]

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 4.x

    Version Information
    Status: Testing

    Created 2017-11-12
    Last Updated 2017-11-11
    29
    • Q: What is broken?
      A: Nothing I'm aware of
    • Q: Can I use the stock Essential camera app?
      A: Yes
    • Q: Does the 360 cam work?
      A: No.
    • Q: Is this rooted?
      A: No. You're on your own for that.
    • Q: Does this pass SafetyNet?
      A: Yes. Android pay, Pokemon Go, etc work fine. If you root, depending on your root method, you may lose this ability. But the ROM itself does pass SafetyNet.
    • 2017-11-20 FAQ rollup: https://forum.xda-developers.com/showpost.php?p=74580036&postcount=189
    • FAQ site with some more info (be gentle with the terrible, or should i say complete lack of, css)
    28
    Here's a bunch of answers to a bunch of questions and things I've seen asked about. I'll link this in post 2 so it can be found again easily.

    Halp! My wifi doesn't work!
    Why: This is due to the boot.img being replaced either by flashing TWRP again or some root methods. In fact, it's not even that the boot.img is replaced, but the kernel inside it has been replaced. The problem here is that the kernel you have flashed is checking the wifi module when it tries to load it and determining that it wasn't built alongside this kernel. This patch must be included in order for the kernel to ignore this check.
    Solution: Re-flash the ROM and don't flash any other stuff afterward. Do this to make sure wifi works initially. After that try flashing your mods and see what causes it to break.

    How do I wipe cache/dalvik cache?
    Answer: You don't. Don't worry about this. You don't have to do it. I promise.

    Halp again! My fingerprint reader isn't working!
    Why: Your firmware is not the same version as the blobs included with the rom. Fingerprint reader uses some lower level firmware than what's included with the rom. Make sure you have the same firmware as mentioned in the OP. Firmware available here. You can just download and flash the appropriate "Firmware Package", you don't need a "Full Dump" for this unless you intend to go all the way back to the stock ROM.

    Is there a changelog?
    Answer: No, because I'm a lazy piece of sh!t. You're better off looking at the github history. I realize not everyone understands what a lot of it means, but that's a good excuse to learn something ;)

    Sup with this not getting official LineageOS support?
    Answer: Just a quick response to this. If I felt this ROM was in a state to give it official status at Lineage, I could turn that on at any point. I won't though, due to the A/B layout and retaining gapps/root/etc (addon.d/backuptool) between rom flashes. I touch on this in the OP too, there's just no really great solution for this right now. The same reason my Pixel builds never went official: official Lineage builds can't, and never will, include gapps. My current best solution would be to roll a supported gapps package that would work with the A/B stuff that I had worked on earlier this year. Opengapps won't work with this without a bunch of hackery to their installation scripts. The biggest problem with all this is if you flashed an update that didn't have gapps over one that did, and forgot to re-flash the gapps zip on top of it, android will get super pissed at you. Rebooting to recovery in this state and flashing gapps after having booted without them wont fix it. Its messy and will cause a lot of problems for users. That's the real reason I haven't made a push for official Lineage on Pixel or PH-1. Rest assured, I've been with the CM/Lineage team for many years (if you didn't know this already). This going to get about as close to official builds as you can get without actually being official.

    More stuff:
    - Double tap to wake is not going to happen here. If people want to roll their own kernels/ROMs with this functionality, that's on them. The hacks to enable this on devices that don't support it at a touchscreen firmware level are detrimental to battery life.
    - I'm not kanging oneplus 3teabag whatever device's drivers. If someone wants to roll their own kernel or ROM with stuff like that, have at it.
    - lineage-15.0 is in the works
    - 360 cam still doesn't work. Got closer with some proxy debugging, but haven't nailed it down yet.
    - Built in updater still needs some work. If it appears to hang, it's probably still installing or finished (it does all this in the background) but somewhere along the line stopped updating the notification. I need to track this down still.
    13
    Here are the steps I developed to install LOS and then correctly root it with Magisk.
    I just tried it with the latest 1130 build and it worked perfectly.

    NO NO NO
    Don't ever give out `dd` commands. You will brick people because people have fat fingers and will mistype. At the very least use by-name partitions and not numeric partition numbers. (I've removed the comment, this is a really bad thing to do)

    If you need magisk, flash this after flashing your rom: https://download.invisiblek.org/magisk_14.3_invisiblekhax.zip
    That zip will flash magisk to the opposite slot you're booted to. So you shouldn't have to deal with this reflashing twrp and swapping slots business.
    11
    How to Successfully Install LOS over Stock

    Is LOS 1205 compatible with firmware NMJ51B?
    Thats a good question has anybody confirmed this?

    Yes, LOS 1205 is working perfectly fine when flashing over either NMJ32F or NMJ51B.
    It is very important to back up all your data and then wipe the phone with fastboot before installing LOS when coming from stock. I believe that most of the weird issues people are reporting here after installing LOS is because they did not wipe the phone first.
    Another set of issues is when people try to flash twrp after installing LOS in order to root or flash other things. Since the new A/B system does not have recovery partition like before, flashing TWRP again messes up the kernel!

    Here are the steps for getting phone with stock rom (NMJ32F or NMJ51B) to LOS 1205:
    1) Backup all your data, including documents, photos, downloads etc.
    2) Wipe phone This is important!:
    Code:
    fastboot -w
    3) Flash twrp:
    Code:
    fastboot flash boot twrp-mata_6.img
    4) Flash LOS 1205 zip from within twrp (copy zip to phone and install)
    5) If you want root, from twrp go to Reboot -> Bootloader, then flash the rooted boot image:
    Code:
    fastboot flash boot boot-LOS1205-magisk1437.img
    6) Boot system as normal

    Notes:
    * Rooted boot image: boot-LOS1205-magisk143.zip UNZIP before flashing
    * You will not have TWRP after this process. Installing TWRP again could break LOS.
    * If rooted, you will need to get Magisk Manager apk from magisk thread and install as a regular app (no flashing)