I'm still on invisiblek's LOS 15; what would be the best path to follow to move to LOS 16 nightlies? Can I just use the detailed instructions in the other discussion or do I need to return to stock first?
[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata)
- Thread starter invisiblek
- Start date
I'm still on invisiblek's LOS 15; what would be the best path to follow to move to LOS 16 nightlies? Can I just use the detailed instructions in the other discussion or do I need to return to stock first?
No need to revert to stock - perhaps this wouls even be a bad idea, as right now you have everything co figured for a custom ROM?
As said, I recall having no issues using the procedure from https://forum.xda-developers.com/showpost.php?p=70452245&postcount=2
See also my post from August in this thread.
Best of success!
Raoul
Last edited:
Missing commits
I have a couple of questions.
1. There used to be a LineageOS 16.0 thread for the Essential PH-1 in this forum. Where did it go? Did someone delete it by accident?
2. When I look at the list of "changes for all devices" at the LineageOS website, I see lots of commits for the PH-1. Here are a few examples.
However, when I look at the PH-1 builds page, none of these commits seem to show up in the build content. Why not?
I have a couple of questions.
1. There used to be a LineageOS 16.0 thread for the Essential PH-1 in this forum. Where did it go? Did someone delete it by accident?
2. When I look at the list of "changes for all devices" at the LineageOS website, I see lots of commits for the PH-1. Here are a few examples.
Code:
scsi: ufs: Add discard command support to ufs debugfs req. stats android_kernel_essential_msm8998
scsi: ufs: Adding io_stats to UFS debugfs android_kernel_essential_msm8998
blkdev: Refactoring block io latency histogram codes android_kernel_essential_msm8998
scsi: ufs: Add UFS slow I/O monitoring. android_kernel_essential_msm8998
scsi: ufs: Add discard command support to ufs debugfs req. stats android_kernel_essential_msm8998
scsi: ufs: Adding io_stats to UFS debugfs android_kernel_essential_msm8998
blkdev: Refactoring block io latency histogram codes android_kernel_essential_msm8998
scsi: ufs: Add UFS slow I/O monitoring. android_kernel_essential_msm8998
mata: Mount persist using Android firmware DT entry android_device_essential_mata
mata: Update to Dec 05 vendor security patch android_device_essential_mata
ASoC: wcd_cpe_core: Allow DSP to process after LSM message android_kernel_essential_msm8998However, when I look at the PH-1 builds page, none of these commits seem to show up in the build content. Why not?
Anybody? There was a new commit today:
Code:
mata: Switch to lazy WiFi HAL android_device_essential_mataBut when I look at the PH-1 builds page, it is not in the latest build nor in the list of changes for the next build.
Code:
Changes to be included in next build
Changes included in lineage-16.0-20200110-nightly-mata-signed.zip
Changes included in lineage-16.0-20200109-nightly-mata-signed.zip
Changes included in lineage-16.0-20200108-nightly-mata-signed.zip
Changes included in lineage-16.0-20200107-nightly-mata-signed.zip
media: Fix compiler warnings android_hardware_qcom_media
gps: msm8960: Fix compiler warnings android_hardware_qcom_gps
memtrack: Fix hal_api_version android_hardware_qcom_displayI don't know about the 16.0 thread either, but for the 2nd question, as I have seen those commits are for the lineageos 17.1 branch. You can check it out on github but I think that's the reason why you don't see them in the 16.0 changelog, as they are not included in these builds.
Thanks a lot, this makes perfect sense! It's good to know that 17.1 is under active development.
so in the era of essentials death... how goes lineage on this phone?
Did the stuff that Essential open sourced on Github as they closed the doors make it any easier to continue to update the OS for the Essential?
Just installed LOS 16 from their website, its working pretty well although it is Pie not Q, but so I am missing those gestures
Fluid navigation gestures on play store
But I'm still on stock rom so maybe it won't work on lineage. But I hope it does...
It does, already using it XPFluid navigation gestures on play store
But I'm still on stock rom so maybe it won't work on lineage. But I hope it does...
You can find detailed information at https://wiki.lineageos.org/devices/mata and https://wiki.lineageos.org/devices/mata/install (linked from the first page)
Correction to the guide @raoulbhatia sent links for, for ADB and Fastboot, download the Windows drivers from essential's site: https://essentialsupport1493251565....015490828-Windows-Drivers-for-Essential-Phone since these are generally recommended.
Yes, bootloader is unlocked. I have 2 questions
1. Do you use MindTheGapps or OpenGapps?
2. After having LOS, how do I root it with Magisk?
I tried to use patch image method in Magisk manager but after reboot the phone got stuck and couldn't get back in.
(I don't have touch in TWRP, so I can't use it to flash zip)
Thanks.
---------- Post added at 05:40 AM ---------- Previous post was at 05:34 AM ----------
Yes, I used the instruction from that LOS site, I could do sideload Rom in no issue, but still had problem with sideload Gapps.
Which one should I use, MindTheGapps or OpenGapps?
Anyone know if HDMI out works with LOS 16? I assume yes, but would hate to spend all that time flashing and be disappointed
DAE1964
Senior Member
After you install the Rom install the Twrp zip. Reboot to recovery, then install gapps. Good luck. I always use opengapps.
Sent from my PH-1 using XDA Labs
You can actually use twrp even if your touch doesn't work using adb, there's a guide for it somewhere on the xda forums if I'm not wrong. But you don't actually need twrp.
1. I use MindTheGapps. No real reason, it was recommended in the wiki and I didn't want to possibly have to troubleshoot any issues so I was playing it safe.
2. I connected my device to my laptop, rebooted to recovery, put on adb sideload from lineage OS recovery and then ran "adb sideload Downloads\magisk.zip" from powershell.
Note: DAE1964 's method should work as well, but for me twrp and magisk never seemed to play well together so I just use LOS's built in recovery
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)
