yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I haven't done much, but I wanted to give you a brief response. Thanks for your great explanation. You are so clear and helpful. Before moving on to OrangeFox, I had already done what you suggested. That is, I had not only gotten your rom up without add-ons but also with. If I had not already done that, I would never have moved on to OrangeFox. With "TWRP difficulties", I sure thought your OrangeFox suggestion was worth a try. And it still is!

When their instructions said to flash OrangeFox again, that's where I got confused and tried multiple ways...with none of them successfully booting system. So we'll ignore what kind of missteps I may have had and do exactly what you said. I'll get to it "soon". (But lots of football coming up).

One thing to mention. Because of TWRP, I had been installing a ForceEncrypt Disabler after Magisk. OrangeFox had a box to check that may do that for me without having to install that, and I had checked that. I'm hoping that was not the cause of some of my issues. I think I had installed your rom with OrangeFox, didn't do any add-ons, tried to boot system, and it failed (as did several other tries, with and without add-ons). But I'll have to try OrangeFox again and see what happens.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
No luck. I think I was very precise. I'm pretty sure that I did this way yesterday, among several tries. All is well with your recovery, either with or without add-ons, while for OrangeFox, neither way works, i.e. can't boot system.

You probably aren't interested in trying this since it has to be an OrangeFox problem. I don't know how to proceed from here. It's really too bad because I do like OrangeFox interface and options. And how I believe there's no abl.img problem like with TWRP . I wonder if the person who gave you the files has tried it recently.

EDIT: I tried with and without that disabler of forceencrypt setting, and it made no difference.

EDIT2: I wasn't clear. If I don't do the 2nd install of OrangeFox, I CAN change slot to A ( maybe unnec) and boot system. But somehow that "inject" messes things up.

I goofed and flashed incorrectly. This was in my attempt to flash boot,system,vendor instead of the rom.zip way (I haven't gotten that to work yet). See the mistake first when flashing system erroneously to boot, then see "error" when flashing boot which seems to not hurt anything. (I mean, I can still go back to OrangeFox flashing rom.zip and booting system). I searched some, but I can't find a way to fix that avb footer. Do you know how?

C:\Users\sandylg\Downloads\Essential\Lineage>fastboot flash boot_a output\system.img

Sending sparse 'boot_a' 1/4 (517064 KB) OKAY [ 12.618s]

Writing 'boot_a' FAILED (remote: 'Image is too large for the partition')

fastboot: error: Command failed

C:\Users\sandylg\Downloads\Essential\Lineage>fastboot flash boot_a boot_tom_lin14.img

Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 32022528).

Sending 'boot_a' (31272 KB) OKAY [ 0.844s]

Writing 'boot_a' OKAY [ 0.187s]

Finished. Total time: 1.031s
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I'll do a separate post rather than making that one longer!

I think this is proof that it's that subsequent OrangeFox install that screws things up. I have gotten system up on A when I did not to the 2nd OrangeFox install. Then if I switch to B, OrangeFox install again on B, I can boot to recovery on A, so OrangeFox did get injected there. But it wont boot system. Then if I flash your boot.img on A., it will boot system.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
It definitely is. Unfortunately these custom recoveries often rely on some kind of hack to install themselves permanently (not to mention the hacks needed to disable encryption), and this might not play well with the non-System As Root setup that is now enforced starting with Android 14. It can obviously be fixed, but I don't know how and I've decided to keep away from custom recoveries after experiencing how messy dealing with them can get.
[Essential Phone ROMs, Kernels, Recoveries, & Other] just4me12:
I flashed the new kernel. As far as i can tell everything in regard of charging works for me.

In the past i flashed microG via "FriendlyNeighborhoodShane's" MinMicroG. I saw you recommended to install microG as a magisk module but i have no magisk running on my device at the moment as i don't want to mess with the boot img. I tried MinMicroG but it doesn't work. I also haven't found any information in the official MicroG Repo to support Android 14 at the moment. I used to have MicroG running with PlayStore (as i have a few purchased apps).
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
MinMicroG is kinda unmaintained and in general it is not well suited for modern Android versions. That's why I do not recommend it anymore. Android 14 is definitely supported by MicroG. I use it. If you don't want Magisk, you could install MicroG manually by pushing the appropriate files to /system, but it wouldn't survive OTA updates...
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Important info for everyone

Since a couple of months, Google has been banning the spoofed build signatures custom ROMs use in order to pass Play Integrity. As a workaround, the devs of the Evolution-X ROM moved the implementation of the values to spoof to a small dedicated system app, to allow quickly replacing them with valid ones without having to wait for a full OTA update. I too adopted this approach in my builds.

Today, Google has invalidated the signature my first LineageOS 21 build was using, so head to the second post in the thread to learn how to pass Play Integrity again - it's as easy as installing an apk file. You will need to do this whenever you see that you cannot pass Play Integrity anymore - provided that I have pushed a new apk that works around the failure (I'll try to keep an eye on this situation and be as quick as possible). You'll find all future apks in the Mega folder I've linked in the second post.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
installed the pif_20240115.apk update, rebooted, and Device_Integrity and Basic_Integrity PASS. Strong_Integrity does not, never did, but Device and Basic are what is needed to use Wallet (tap-to-pay)... Wallet and the financial apps i use are working correctly. :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] just4me12:
Okay, i messed with the boot.img and followed your advice from the 2nd post (should have done that earlier).

Now everything works smooth and just how things shall be :) .

I also installed pif_20240115.apk and this also works fine for me.

Thank you sooo much. Happy to stick with this device.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks, I appreciate your attempts to get me a recovery other than TWRP that would do backup/restore. I'll still play with it a little, just to learn more about it.

I assume that you don't know a way to get rid of that error I get when flashing boot. It must have been caused by my invalid flash.

Thanks also for the Play Integrity info.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I think you won't be happy to hear about the TWRP topic from me again! But I had so many problems in the last week with the "bad" Essential that I wasn't trying to Install TWRP there. Then I was trying to get OrangeFox to work, and when that didn't work, today I have gone back to installing TWRP on the good one.

(By the way,I finally had to give up on the bad one. It could flash once out of every 30 or more tries, never worked twice in a row. The "good" Essential never has a problem at all. I have an old laptop that has USB 2.0 ports, while the one I have been using for the last couple of years does not. Flashing certainly does better on those ports, i.e. it might flash 10 times in a row!, then goes bad and stays bad until powering off or who knows what. But it has been a little unreliable from the beginning and now has finally bit the dust).

So...with the bad one and OrangeFox out of the way, I'm trying to get TWRP on the good one. It appears to have the same problem that OrangeFox did. I mean, it won't boot system. (This is different with TWRP...always boots to TWRP recovery instead, while with OrangeFox, it looped). Then I flashed your recovery back into boot and it comes up! So it seems like both OrangeFox and TWRP have the same problem after they inject into your ramdisk. You mentioned something about these recoveries not playing well with Android 14 .

I think you were saying it isn't something you want to look at. But since it happens for both TWRP and OrangeFox, I thought I'd mention it. I was hoping that I could go back to my usual TWRP, but now I will have to worry about the abl.img problem. That's actually pretty minor. I just have to flash the 007 one after your zip is installed. Even if I flash individual partitions for boot, system, vendor, leaving out all those bundled images, I still won't be able to use TWRP.

Is there anything I could do to help you see what this "bad inject" is causing? I understand if you really don't want to go any further with this. But I have really liked TWRP backup/restore....I get tired of having to fix widgets, and it helped me not have to do that. And if I'm trying multiple roms and want to switch back and forth, it's so easy. I was liking OrangeFox capabilities also.

I haven't tried your PIF apk yet since I haven't gotten this up yet.

My choices right now are bringing it up without TWRP or OrangeFox...OR going back to Android 13. I might want to try OrangeFox with that! Too bad that I only have one good Essential now.

I'd still like to have your boot that has the switch slot option. Let me know if/when you can put that on Mega. Maybe you said that won't be until your next release.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
The fact is that the recoveries must be adapted to the Android 14 ramdisk layout. There's nothing I can do on the ROM's side. My ROM implements the ramdisk layout changes needed to boot 14.

I gave a quick look at OrangeFox's zip to see if there was anything obvious I could do to make it work on 14. I produced these two alternate zips; if you're lucky, one of them will work for you:

42.35 MB file on MEGA

mega.nz

42.35 MB file on MEGA

mega.nz

If they don't, I'm afraid you're on your own.

I will provide a bootimage with a recovery capable of switching slots as part of the next build.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I didn't get either to work. I tried both several times. I think I must be doing something wrong because I'm trying the simplest possible steps. I install OFox on B, install the zip (goes to A), reinstall OFox on B, boot to Ofox recovery, now also on A. I don't install any add-ons. Reboot system. Sometimes it boots to bootloader, other times recovery, other times it loops.

A very strange thing happens with the original OFox AND your two. At various times when I think I should hear the dings indicating I can see internal memory, if I wait 2-4 minutes, it does finally occur and I can see it. This weirdness really makes me think it has to be me doing something wrong.

So I'll give up. But I really thank you for your efforts. I'm pretty sure I've never had anyone else on XDA be so willing to help. You are also very precise and clear...some are not. Many thanks for everything. I'll either use your 14 "as-is" or continue using your 13 with TWRP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LMUJT:
Charged again for the second time. The new Kernel has not brought back the charging issue.

Though i have experienced some stuttering while scrolling in Kiwi Browser which was not there before.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I've released a new update with some additional optimizations and improvements, plus support for the 3-finger swipe to screenshot gesture and an inbuilt app to read and export logs directly from the phone (check the changelog in the first post).

I might have messed something up on the OTA updater's side, please let me know if you are able to download the new update or not.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LMUJT:
I can see and download the OTA update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
@temporarium, I tried to send you a PM so that I don't clutter this thread with any more backup/restore questions. But I was restricted from sending to you. I'm looking for a way to backup/restore data.

I think you may be the only one other than myself in this thread using TWRP. I think you had been successful with Lineage 20. Me too. But I'm unable to use either TWRP or OrangeFox with Lineage 21. Have you made an attempt? If so, have you had any success?

I googled for other possibilities, and I see posts online (mostly stackoverflow, not XDA) about using dd or adb pull for userdata. But it's confusing, and I'm not sure if either of those are worth trying.

I know I can use dd command to create boot, system, and Vendor output and then dd them back in with no problem. But it's the data that I want. The output would be very big, and it's not clear where I can put it. Here's one article, and it describes a Windows way (I have Windows 10). Again...confusing! @Tomoms, please comment if you know about possibilities for backup/restore data since recoveries seem to be out of the question.

https://stackoverflow.com/questions/29442630/copy-full-disk-image-from-android-to-computer
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
@Tomoms, you said this about the new rom.

"This is needed to clear some leftover state related to that app which is now missing from my 21 builds."

I'm wondering what the effects are if I forget to do those steps about the Graphene apk.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
No, I use the lineage recovery now and OTA.

I backup using Swift backup and sync that to my server with Syncthing. If anything goes bad (which it hasn't with this ROM), I can get those apps back.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Yep, using dd is not feasible because you'd need roughly 100 GBs of space to store the partition image. It could be doable if you plug an external hard drive to your PH-1 via the Type C port though, keeping in mind that the drive should of course not use the FAT32 file system (ideally it should use ext4).

The ADB pull way seems interesting. If ran from within Lineage recovery (which cannot mount the data partition), it should result in an image of the (encrypted) data partition being stored directly on the computer.

Then you'd need to find a way to restore this image (again from within Lineage recovery, as the data partition must not be mountedd), which is not easy since you only have one interface but you need to send the device both data and commands...

If you do not perform the steps about the GrapheneOS app store, you will probably end up having a process crashing every few seconds/minutes in the background, with a potentially noticeable negative impact on performance and battery life.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks. I have used Swift backup for apps and wallpapers, but I get tired of fixing my widgets. A few allow you to save/restore data from them with a file, but most do not. I haven't found any other way to get them restored without TWRP backup/restore. (Or OrangeFox, if I could get that to work}. A complete backup and restore method has always been so convenient.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I haven't done much yet with your new rom. I have not seen any process crashes or anything like you mentioned. Maybe it will take more time than I have given it.

Various articles did have plenty of info about ways to do the backup. I didn't understand them well. But I didn't see much about the restore. You mentioned that it might not be easy. I will probably abandon this, but I thought it was worth asking you and @temporarium. (By the way, my data is decrypted because I use a ForceEncrypt Disabler zip (deprecated), necessary to make TWRP work well for data. I install it after Gapps and Magisk. I think there is a newer better version that someone else developed, but I never tried it).

[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]

Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...

xdaforums.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Confirming dirty flash from your LOS20 via adb sideload in LOS recovery went well. It asked to reboot to recovery and slot was changed, and Magisk sideload there 👍🏻

Only a couple of observations (could be this particular setup): I had to re-enable navbar buttons (somehow gesture navigation was set after the upgrade), and I had to disable battery saver - somehow that got enabled though battery power was adequate.

Also, the mentioned "glitch" was there.

Otherwise, all seems ok. Thanks again!
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I know this will sound absolutely nuts. But here goes. "For fun", I decided to power on the "broken" PH-1 which had been turned off for more than a week. It came up in bootloader, as expected. That's how it always came up after I was unable to fastboot flash anything because of errors. I had learned that it did better on USB 3.0 ports than 2.0. But even that failed after working a few times.

I flashed your boot image...it worked, so I did it again, expecting failure, but it worked. So I booted to recovery, worked. Then to system, worked! I used it for maybe an hour late last night, then turned it off.

Today I powered it on again, it booted to system. Everything is good. I'm not going to flash anything because I'm afraid that will mess it up!

I understand that overheating can be a problem. But when I was having those flashing errors, I turned it off. let it sit for a day or two. I'm not knowledgeable about hardware, but I see no reason why this longer length of time could have helped it work.

Anyway, I doubt that anyone can shed any light on this. It will inevitably fail again if I start to flash. It has had problems for over 4 years, ever since I got it on eBay. But I was always able to get past them until a few weeks ago.

EDIT: I may try to put Lineage 20 on there and leave it there forever. And I have your new Lineage 21 on the other "sturdier" one.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I think gesture navigation is enabled by default by a patch I have implemented in my LineageOS 21 tree. Power saving mode being on sounds like a random glitch of your setup.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
The "random glitch" could have been my father 😂

Anyway, both easily fixed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
@Tomoms, I don't know if you are following the play Integrity thread.. which is now over 500 pages! So I thought I'd tell you this one tidbit that osm0sis has figured out.

Many people, including me, are failing device integrity. It has to do with the string that is in the fingerprint. He has given a list over there of ones that are failing. - lineage- is one of them. So he gave instructions for how we could patch the boot.Img to change it to something else.

But his suggestion is that people report this to the developer and have them change it in subsequent releases. Your lineage 21 release is good, but your lineage 20 is not. I also have lineage 18 on a Leeco phone, and it also has that string. I don't know who maintains that one. But if you are going to release any more of lineage 20, I thought I would point this out.

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
-lineage is a suffix that is appended to the kernel version, i.e. it is part of the kernel version string. I've been changing that suffix to -Tom for years, but you are right! I apparently forgot to change it when I switched to the new rebased kernel in my LineageOS 20 builds. 21 is fine. I will not release any new LineageOS 20 build, but no worries! I can provide a new flashable kernel for my 20 builds that replaces that suffix, this is easy to do. Stay tuned and you'll see it here tomorrow.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I'm assuming that you don't know anything about how to get this done for the lineage 18 version on my Leeco le pro 3. I do see that it is still being maintained (010124 Nightly), but I don't know who to contact.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
For the Settings icon in your latest 21 ROM, the label shows as 'There is a problem loading the licenses'. If I look at its App info, it is called 'Third-party licenses' instead of 'Settings'.

I have no idea how I could cause this! Sometimes I do use a Shortcut Maker app, but I haven't done that with your new ROM yet. Even if I did, I can't imagine this result. No big deal, I'm just wanting to know if you see it too.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
You need to replace the kernel in the bootimage with a kernel compiled without the suffix. Your best bet would be to contact your LineageOS maintainer(s) and ask them to drop the suffix from the kernel configuration file, but I can see that one of the LePro3 maintainer has been inactive for almost 3 years, while the other one for even longer. I'm afraid your chances of success are quite low, unless you decide to build your own kernel without the suffix.

This is a random glitch that happens every now and then on Android 13 and newer. My next build will implement a workaround that should probably address it. In the meanwhile, running

adb root
adb shell rm -rf /data/system/package_cache
adb shell rm -rf /data/resource-cache
adb reboot

should address it. You can alternatively delete those two directories using a root file manager. Reboot immediately afterwards.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks for the "Settings fix". I deleted both folders. It helped for Total Launcher (my favorite) and Microsoft Launcher, but not Trebuchet, the built-in one. I only use the first two to compare when something goes wrong, like now. I look forward to your next build and am not concerned.

About the Lineage 18 kernel for Leeco, I was using a ROM on XDA by Mosimchah, but as you said, he has not been around. I also have his AICP release Android 11 on a 2nd Leeco. Unfortunately, there aren't good choices for that device since it's maybe 7 years old. I have loved it, so it's too bad.

I do see an update for today for Lineage 18.1 nightly on download.lineageos.org. And another site, lineageoslog.com, shows that release with a change log... it says "Bump security string to 2024-01-05" as one of the changes included. So someone is making changes, but I don't see how to contact them. I think you're saying that only a Leeco developer would be able to fix this string in the kernel. Sorry that I don't know enough about all of this...is the security string elsewhere?

I did a quick look at your info on unpackbootimg, etc. (and a few other people's similar files). But I'm not good at that setup so I gave up. So your change for PH-1 will be great, and I guess I'll give up trying to get the string fixed on the Leeco.