Ok, thanks, I'll try it this weekend.
---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------
Thanks for your instruction, I'll give it a try.
[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata)
- Thread starter invisiblek
- Start date
Ok, thanks, I'll try it this weekend.
---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------
Thanks for your instruction, I'll give it a try.
Just a warning....I have similar problem....check this out
https://www.reddit.com/r/essential/comments/f6h1sq/los_16_new_install_bluetooth_crashes_and_wifi/
What do you mean that? lineage.org mark it as an official buid... is that possible without active mainteiner?
Thanks
YupWhat do you mean that? lineage.org mark it as an official buid... is that possible without active mainteiner?
Thanks
https://www.reddit.com/r/LineageOS/...geos_device_info_list_of_devices_with_active/
PH-1 is on this list of devices with at least 3 maintainers. They seem to frequent reddit, and not xda. I'm optimistic that our phone will get decent support on Lineage going forward. But then, I'm an optimist :laugh:
PH-1 is on this list of devices with at least 3 maintainers. They seem to frequent reddit, and not xda. I'm optimistic that our phone will get decent support on Lineage going forward. But then, I'm an optimist :laugh:
Yeah... Active...
Rashaad's mata is in a drawer...
Ethan's is probably under a pile of other devices ...
And Paul says he's retired...
Thanks for clarification.
How do you like LOS on this phone? How stable is it? Can it be daily drive?
Thanks again.
I like it pretty well, personally. While it is a step down from Q for sure, I did miss some things about Pie (like how ambient display shows only that simple black screen with time, notification icons, and battery instead of jumping straight to the lockscreen - I'm still bitter about this one). LineageOS itself seems close enough to stock for me for my purposes as well, so I have no issues with it. as always, YMMV, but I haven't had any crashing issues or random reboots so far. seems stable enough for daily driver material.
I'm fairly certain (but not 100% sure yet) that the reason we reboot after flashing a ROM (but before gapps/etc.) is because the recovery environment flashes to the old/inactive slot until it's rebooted. rebooting causes the active slot to boot, and then when recovery gets spun up, it's pointing at the slot we just flashed (the active one).
Last edited:
One more question....Did you root your phone?I like it pretty well, personally. While it is a step down from Q for sure, I did miss some things about Pie (like how ambient display shows only that simple black screen with time, notification icons, and battery instead of jumping straight to the lockscreen - I'm still bitter about this one). LineageOS itself seems close enough to stock for me for my purposes as well, so I have no issues with it. as always, YMMV, but I haven't had any crashing issues or random reboots so far. seems stable enough for daily driver material.
I'm fairly certain (but not 100% sure yet) that the reason we reboot after flashing a ROM (but before gapps/etc.) is because the recovery environment flashes to the old/inactive slot until it's rebooted. rebooting causes the active slot to boot, and then when recovery gets spun up, it's pointing at the slot we just flashed (the active one).
If so, how do you flash Magisk? Because with TWRP, after flash Magisk, I couldn't boot back to the system.
I think TWRP and Magisk don't agree with each other on our phone for some reason, don't know why. I haven't tested them on LOS, but I know this to be true on stock. There was this guy on reddit, I think u/halotechnology was his username, that used to post patches stock images with both twrp and magisk, don't know how he did it.
Right now I just flash magisk using the stock LOS recovery, and addon.d and the LOS updater takes care of updates fine most of the time.
I flash magisk from sideload, to flash from twrp Ive read that you must change slot or flash twrp on both slots.
Pd: stock version seems pretty well, only a few LOS functions are better. Restore wasn't as good as stock (maybe Android q feature?)
Pd: I got a weird audio bug with whatsapp playing from close speaker.
Pd: stock version seems pretty well, only a few LOS functions are better. Restore wasn't as good as stock (maybe Android q feature?)
Pd: I got a weird audio bug with whatsapp playing from close speaker.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
109LineageOS 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:
(no, this isn't a typo, you are flashing twrp to the boot partition)Code:fastboot flash boot twrp-mata_11.img - 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-1129- 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)
28Here'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.
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.
Answer: You don't. Don't worry about this. You don't have to do it. I promise.
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.
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
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
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.11How to Successfully Install LOS over Stock
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!:3) Flash twrp:Code:fastboot -w4) Flash LOS 1205 zip from within twrp (copy zip to phone and install)Code:fastboot flash boot twrp-mata_6.img
5) If you want root, from twrp go to Reboot -> Bootloader, then flash the rooted boot image:6) Boot system as normalCode:fastboot flash boot boot-LOS1205-magisk1437.img
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)
