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

Search This thread

smalltownbird

Senior Member
Jan 27, 2010
411
64
I haven't made any phone calls yet so I can't attest to call quality. I can say that the touch issues on the factory build are gone on this rom. That proves to me that the touch issues on the edges are a software problem. The phone is much smoother on this rom. Makes the phone usable.
 
  • Like
Reactions: co.ag.2005

makbomb

Senior Member
Feb 23, 2014
118
39
New York City
Seems that I no longer am able to boot into TWRP after having flashed Lineage (been using it on device successfully since yesterday), and I did use the twrp-mata_6_NMJ32F that @bmg1001 provided. Thanks.

---------- Post added at 04:02 PM ---------- Previous post was at 03:43 PM ----------

@invisiblek I PM-ed you a log re: people I call can barely hear me. I'm on T-MOBILE NYC. Thank you so much.

Just realized that I was running the 11/10 build, so I wonder if it's been fixed since. I will definitely flash the most current this evening, although TWRP seems to be gone. Also, is dirty flash OK? Thanks.
 

ruvort

Senior Member
Aug 4, 2010
1,542
405
Seems that I no longer am able to boot into TWRP after having flashed Lineage (been using it on device successfully since yesterday), and I did use the twrp-mata_6_NMJ32F that @bmg1001 provided. Thanks.

---------- Post added at 04:02 PM ---------- Previous post was at 03:43 PM ----------



Just realized that I was running the 11/10 build, so I wonder if it's been fixed since. I will definitely flash the most current this evening, although TWRP seems to be gone. Also, is dirty flash OK? Thanks.
This is because recovery now resides in the boot.img. Installing Lineage overwrites your boot.img with the Lineage recovery.

Sent from my LG-VS980 using Tapatalk
 
  • Like
Reactions: makbomb

masterchief_2001

Senior Member
Feb 11, 2009
102
15
Fulda
@invisiblek How long does it take to update the ROM with the updater app? I've downloaded the 11.13 build and it is installing now through the updater app,but I've startedupdating almost 1 hour ago. Any advices?
 

12paq

Senior Member
Seems that I no longer am able to boot into TWRP after having flashed Lineage (been using it on device successfully since yesterday), and I did use the twrp-mata_6_NMJ32F that @bmg1001 provided. Thanks.

---------- Post added at 04:02 PM ---------- Previous post was at 03:43 PM ----------



Just realized that I was running the 11/10 build, so I wonder if it's been fixed since. I will definitely flash the most current this evening, although TWRP seems to be gone. Also, is dirty flash OK? Thanks.

None of the TWRP versions I have tried stick around. The op pretty much explains why this is. The user who posted that he had a version that survives is likely misunderstanding or accidently misstating.
 
  • Like
Reactions: makbomb

mrcooter

Senior Member
None of the TWRP versions I have tried stick around. The op pretty much explains why this is. The user who posted that he had a version that survives is likely misunderstanding or accidently misstating.
Think it could be due to the A/B partitions? Only reason I say that is I installed the 11/12 build. Everything was fine. Did the initial setup and did advanced reboot from the OS into recovery. It put me in stock recovery but was slightly offset to the left like with our current TWRP. From there, rebooted to bootloader, chose reboot to recovery. It then booted to twrp. Then, chose reboot system from TWRP menu and somehow lost lineage. It was the stock boot animation and constant force closes when it booted. Nothing was pushed or flashed during this time either. Wiped data and stock booted and had to set everything up again but I never flashed back to stock..

Figured I would wait a few releases and try again but the only thing I can think of that would cause this would be the A/B partition and one over wrote the other, or lineage did not replace both partitions during the install?
 
Last edited:
  • Like
Reactions: makbomb

makbomb

Senior Member
Feb 23, 2014
118
39
New York City
Think it could be due to the A/B partitions? Only reason I say that is I installed the 11/12 build. Everything was fine. Did the initial setup and did advanced reboot from the OS into recovery. It put me in stock recovery but was slightly offset to the left like with our current TWRP. From there, rebooted to bootloader, chose reboot to recovery. It then booted to twrp. Then, chose reboot system from TWRP menu and somehow lost lineage. It was the stock boot animation and constant force closes when it booted. Nothing was pushed or flashed during this time either. Wiped data and stock booted and had to set everything up again but I never flashed back to stock..

Figured I would wait a few releases and try again but the only thing I can think of that would cause this would be the A/B partition and one over wrote the other, or lineage did not replace both partitions during the install?
@mrcooter I had the exact same experience, but I fDRed and after setup, downloaded today's LOS build and flashed, because I still had TWRP
 
Last edited:
  • Like
Reactions: 12paq

12paq

Senior Member
Think it could be due to the A/B partitions? Only reason I say that is I installed the 11/12 build. Everything was fine. Did the initial setup and did advanced reboot from the OS into recovery. It put me in stock recovery but was slightly offset to the left like with our current TWRP. From there, rebooted to bootloader, chose reboot to recovery. It then booted to twrp. Then, chose reboot system from TWRP menu and somehow lost lineage. It was the stock boot animation and constant force closes when it booted. Nothing was pushed or flashed during this time either. Wiped data and stock booted and had to set everything up again but I never flashed back to stock..

...


Yes the op clearly states the A/B issues and the location of recovery as to reasons why.

Like you and the other guy I reflashed TWRP and after running a backup, it It messed LOS up with the exact symptoms you mentioned and then eventually through TWRP my device got completely wiped. No biggie, I have all backed up to my PC. It's very early on in this build and I find it fun.

Also, as recommended by the op, us users might want to keep this dev thread clean and read/post/lurk over on the Discord channel. Especially if we're not posting logs.
 
Last edited:

xxBrun0xx

Senior Member
Jan 1, 2012
2,261
703
CT
Samsung Galaxy Z Fold2
This is probably a stupid question, but if twrp doesn't stick after flashing, if you don't flash Magisk immediately after flashing rom, are you not going to be able to root, or can you flash through lineage recovery?

Can't wait to give this a go! Thanks very much!
 

anandlal

Senior Member
Mar 22, 2011
344
81
Denver
Xiaomi Mi 9
Samsung Galaxy S21
@invisiblek How long does it take to update the ROM with the updater app? I've downloaded the 11.13 build and it is installing now through the updater app,but I've startedupdating almost 1 hour ago. Any advices?

Mine was stuck on Preparing First boot @8% for an hour. I decided to reboot the phone and start again.

This worked. It went through the complete process.

I was upgrading from 1112 to 1113.
 
  • Like
Reactions: masterchief_2001

hondajohn88

Senior Member
Jul 30, 2013
563
626
Upland
This is probably a stupid question, but if twrp doesn't stick after flashing, if you don't flash Magisk immediately after flashing rom, are you not going to be able to root, or can you flash through lineage recovery?

Can't wait to give this a go! Thanks very much!

After installing the Rom, you should be able to go into bootloader, flash twrp to the boot partition, boot twrp & flash magisk, then boot back into the Rom.
The process is described in another thread in discussions I think.
 
  • Like
Reactions: CRasH180

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)