yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I wrote this above.

"When you enter "adb version" (without quotes), what do you get?"
[Essential Phone ROMs, Kernels, Recoveries, & Other] mcdull:
Is this rom able to use the USB-C to HDMI adaptor, i.e. Alt-Mode ? Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Yes, it works fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, it's time for Android 14!

My first LineageOS 21 build is available. Based on the latest LineageOS sources, including January's security patches.

The charging issue should be fixed - paging @LMUJT , please confirm, if you try this build.

LineageOS 21 builds for mata (both mine and Nolen's) are currently affected by a purely visual bug that causes an exclamation mark to be shown on the mobile network signal icon. Mobile data and VoLTE are actually working fine. I'm currently working to fix this issue.

Dirty updates from my LineageOS 20 builds are possible via recovery (remember to reflash Gapps! They must be reflashed after a major release upgrade), but afterwards, I recommend you:

install GrapheneOS's Apps store (which was preinstalled in my LineageOS 20 builds);

reboot;

uninstall it.

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

I had to drop support for all the interesting GrapheneOS features for this LineageOS 21 cycle, because they were too disruptive and difficult to maintain.

Any question, just ask!

Cheers :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Thank you for your continued support for this device!

Will next month's release eliminate the need for the leftover cleanup?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Nope, that will always be required.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LMUJT:
Thank you very much. You are awesome.

I will try a dirty flash and report afterwards. Should i flash the Lineage 21 recovery first?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
It's not needed.

If you are using Gapps, remember to reboot to recovery after flashing the ROM, so that the slots are switched and the new Gapps are installed in the correct slot :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] LMUJT:
The deed is done. My Dirty Flash is up and running perfectly. Thank you very much. Testing the charging issue will take a couple of days.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
This is not a topic for this thread, but I'll try. I flashed your new rom, but when trying to boot, the device would only boot to bootloader. I've had some similar troubles with this device since I first got it from eBay 4+ years ago. But I've always been able to get out of it.

But now, I'm unable to fastboot flash any partition. It shows:

FAILED (remote: Error flashing partition.) I can successfully do fastboot --set-active=_x (where x=a or b), but fastboot getvar current_slot shows no slot, i.e. current_slot: has nothing after it. So something really is corrupted.

I don't see any threads/posts that refer to an "empty" slot like this. I do see threads that talk about some kind of EDL mode to possibly repair, but I've never done anything like that. Do you have any idea of how to "reformat" partitions to get them back to being flashable?

Again, apologies for messing up your thread. I was ready for your new rom!

EDIT: I do have another Essential, but I have Lineage 20 nightly on there, just for comparison when things went wrong. So I can move to that device, but I sure don't want to screw both up!

EDIT2: Gosh, I'm nuts. I had this issue before but didn't remember. Yes, something is corrupt, but not with the device. The laptop needed to be restarted! Now I can see the slot with the fastboot getvar command. And I can flash everything.

@Tomoms, I'm hoping you didn't see this until this EDIT so that you wasted no time thinking about it.

EDIT3: Well, that good news was premature. The current slot issue and inability to flash keeps happening (trying to put recovery on other slot...getting ready for TWRP), and restarting the laptop no longer fixes it. So it's baffling. But as I've said, this device has had issues forever, so maybe it's on its last legs.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
This does indeed sound very strange. I've had similar issues lately, when using a certain version of fastboot. Maybe that plays a role in the problems you are facing too. I'll check and tell you which fastboot version is good for me. Still, it's strange that only one of your PH-1s is having issues. By the way, since I remember that you pointed out some differences between two bootloader versions and the way they interact with TWRP, you should know that starting from the LineageOS 21 cycle, my builds now ship with the full firmware included (radio/bootloader partitions are overwritten), just like official Lineage has always done.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
You mentioned a specific recovery in post 286. I have some notes that said it had a "change slot" option (or something like that) as one of the Advanced options. I could have missed it, but is that in this recovery? If not, can I just flash that one (to boot partition) on top of the already installed new rom.

Oh! Did you use the latest bootloader which was 032 or the older one that works for me which is 007? Somehow the 032 bootloader does not like it that boot that has been combined with TWRP. So booting to either system or recovery always erroneously come up in the bootloader.

Not knowing that was the issue, somehow I must have screwed something up when trying to reflash stuff. That has completely messed up slot a, but I was able to use slot b. Unfortunately, with a getting errors when flashed in fastboot, I can't do TWRP! It requires both slots. I won't try to explain any of that, you may already know what I'm talking about.

So I'm going to flash your new release on my other Essential. I think that will go better! I will just have to flash the 007 abl.img that works for me after flashing yours, assuming you are flashing 032. That would have caused the same problem as this first one, but it has never had the same problems with general flash issues... having to keep rebooting multiple times. Hard to describe it all, but it has been a mess from the beginning. I just made it work. The other one is more solid.

It is strange that no one else has this bootloader issue. I guess people aren't trying to use TWRP. I may give up on it in the near future because of these issues.

By the way, is the boot.image that shows on GitHub the same as what is in your zip? I thought I had extracted it and compared quite a while ago and they weren't the same. Maybe that's just because of the way it gets extracted.

Thanks as always for your great work!
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I keep messing my posts up. That last one ended up being included with my prior post. I was asking about different recoveries that might have different Advanced options, like change slot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I am shipping the same bootloader official Lineage ships (I guess it is 032).

The fastboot version that works for me is 31.0.2-7242960.

In the first post, I linked a boot image stored on Mega as the suggested recovery to use to install my ROM. Can you flash that one in the b slot of the quirky PH-1, and then try to use it to flash the ROM to the a slot? That boot image supports switching slots manually, but I remind you that Lineage recovery automatically installs Lineage builds to the inactive slot and then sets a flag to reboot into that slot on the next power cycle.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
This is a busy day for me, so I won't get to your request right away. But I'll say a couple of things.

I edited the post that said "Unfortunately, with b getting errors when flashed in fastboot, I can't do...". It should have said "with a getting errors". I think you probably understood that anyway.

I do understand about inactive slot and subsequent reboot and have been counting on that.

Are you thinking that the A slot will be "fixed" by the Mega recovery on B, as you suggested? If not, I can't use TWRP on that device. I can try later, but I'm not sure that I'm understanding exactly what this will prove.

I have installed with TWRP on the "good" Essential. But due to the abl issue, I had to extract and fastboot flash boot, system, vendor. I did all of that on A, yet B was the one that can boot to system and TWRP. On A, booting TWRP just hangs. That may be due to decryption. I may have mentioned before that I use a disable encryption module so that TWRP backup/restore of data work. Yet TWRP works for A. I know, this is all quite confusing. I really did have it working pretty well though until this abl issue. I guess there's no simple way for me to delete it from the file. It would be easier than how I flashed the 3 partitions. Maybe you are saying that your suggestion will help with all of this....but I'm not sure.

EDIT: I wonder what changes to the bootloader were made to cause my problem. Fixing that would obviously help me! But I have no idea how difficult it will be for you to figure that out. If I learn how to flash the 007 file "at the right time", that would help. But I messed up some steps today and don't have time right now to find the best way.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I haven't had time to do much yet. But it's not good! Now I get the error when flashing from either slot. So I'm unable to get your Mega boot installed. I tried that flash many times with no luck, then it started displaying a "red warning message". I don't know the exact words because it's no longer displaying. Maybe it was "Your device is corrupt and can no longer be trusted". It looped doing that for a while.

It took many reboots to get into the bootloader since it started looping with those 2 balls on the screen over and over. It's back to showing an empty current_slot. I think I can only get into the bootloader if I unplug the cable.

I did some reading about a possible fix for the red warning, but since it's not occurring now, that may not make sense. I read something that said it would be flashed to the inactive slot...but I don't know which one that is!

So I'll keep trying, but I don't know if this is salvageable. But I won't give up yet! Let me know if you think I should flash the red warning fix. I'm not sure where the "right one" is. Or which slot I would flash it to.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I am having a hard time understanding and keeping track of all the attempts you made. This issue is really weird. Both my latest 20 builds and my first 21 build have got a fix for the "verity red" screen built in the kernel, so I'm not sure why you're seeing that. I suggest that you try to flash the full stock 007 firmware, if you somehow manage to get fastboot to work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I completely understand why you're having a hard time. I am too, and I'm here looking at it all! I will say some possibly final words about that "bad" device that happened today. Then I'll move on to the "good" one.

Here are the "bad" device final words:

After not being able to flash to either slot for a long time early yesterday and again last night, I turned if off overnight. This morning, I held down/power for many seconds, and bootloader came up. I flashed your current boot (probably to b, but current_slot still is empty). No error during flash! In fastboot, I hit down button to go to recovery, it gave red warning, I hit power, it went to recovery, I told it to boot to system...and it did! I did fastboot to try to flash your Mega boot as you wanted, but now it got an error....many times. So I powered off, setting it aside until who knows what. Maybe it needs to rest!

Okay, on to the "good" device. I flashed the Mega boot. But it doesn't have any "change slot" option in Advanced. The size is identical to the one from the payload.bin in your rom. It says the same stuff at the top, i.e. Version 21.0 (20240110). I know I'm missing something! But I downloaded it again, same thing. By the way, Mega asks if I want to download that .img as a .zip instead. Now and then, I have thought it might be more convenient to have an image as a zip, so should I try that instead? I'll probably go ahead without getting your answer.

From this point on, I'll mostly be working with this "good" device. I'm going to try to get TWRP on it, but it's a bit of a pain because of the abl.img issue. If there's anything you need me to test, let me know. I'll be glad to try the Mega boot if you can help me find it! (If the .zip changes to a different version with "change slot", I'll let you know).

Oh, another by the way, about the abl.img issue. Here is a link to where someone mentioned that 007 works for TWRP and 032 does not. The next to last official release was Jan 2020 007, and the last was Feb 2020 032. There are other xda threads that talk about Chrome freeze issue, and that was another reason to use a different release that has a modem.img that fixes that. I really don't have insight into what lineage devs decided on what to end up with.

Latest Android 10 - unsupported/Unknown format from Magisk

Hi, New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material...

xdaforums.com

And another reference to the TWRP issue.

[ROM][10.0][MATA][OFFICIAL] Evolution X 4.3 [05/05/2020]

Evolution X 4.3 for the Essential PH-1 [mata] Living, Breaking, Keep Evolving. Evolution X is a flashable Custom ROM to bring a true Pixel feel to your Android Device at first glance, with many additional configurations at your disposal. We...

xdaforums.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
You are right. I forgot to fork the recovery's soruce code repo before the last resync I did before building the 20240110 build, and as a consequence the resync has cleared the patch that introduces the "Switch slot" functionality in the recovery. I'll restore it permanently in the next build.

Downloading the img file as a zip would change nothing - you'd simply have to unzip it before flashing it, so it doesn't make a lot of sense in my opinion.

BTW, instead of the only old and buggy TWRP build that exists for the PH-1, you might want to try a more modern and polished OrangeFox recovery (based on TWRP) build: https://yzu.moe/android/mata/recoveries/

This build comes from a developer known as "electimon", he is a skilled and trustworthy person (he also authored many commits in the new rebased kernel we're going to ship in official LineageOS 21 in the future).

Maybe it plays well with the 032 abl.img?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks! Can you possibly put the recovery on Mega (or anywhere) so that I can try it? No big deal if you want to wait for the next build.

I know I read about OrangeFox a while ago, but I didn't think it worked with this phone. I will gladly look into it, but I'm really used to TWRP for many years. The main reason I want it is for backups, but there are other good features. I'll have to see whether OrangeFox supports those.

EDIT: OrangeFox site doesn't show this phone. Maybe they are getting ready for it? Otherwise, I wonder why he gave you those commits.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
This probably isn't interesting to you. But maybe it gives a hint as to what changed in the bootloader abl.img to screw up TWRP.

Official TWRP 3.2.3-0 for Essential PH-1

I bought an Essential during one of Amazon's sales and I have finally produced a working, official TWRP for the device. I tested it on Essential's 9.0 official firmware with August security patches. Touch works and TWRP is able to decrypt your...

xdaforums.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Wait, didn't you see the link I've included in my previous post? You can download an Orange Fox build for the PH-1 from there. It most likely supports backups. In general, it is based on TWRP, so it has got all features of TWRP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I did see the link. But I went to their site to read more about it. That said that there were only 4 supported brands. Asus, Nothing, Samsung, Xiaomi. They also had "other devices" listed that were not supported, so maybe they were at one time. Anyway, Essential wasn't in that list either. So I just assumed that it was something in the works, but maybe not ready to be used.

I wonder how you knew this existed. Maybe electimon contacted you. Googling for both Essential Phone and Orangefox recovery revealed nothing. But I'll look at it soon. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I wasn't aware of its existence either, a user sent it to me not long ago :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Some good news, but plenty of bad! I'm trying OrangeFox, but having trouble. I know this isn't something you have tried or are interested in. So just ignore if you don't feel like thinking about this. I do like OrangeFox features and structure.

The good news is that after I first install your rom (i.e. no attempt to do add-ons yet), I don't have the problem where only bootloader comes up when trying to reboot recovery. So I guess 032 abl.img is good and I don't need to replace it with the 007 version!

But I have plenty of "slot confusion". OrangeFox wiki info in https://wiki.orangefox.tech/en/guides/flashing has a section on A/B devices.

I won't copy it all here, but here is a very confusing part, actually just the 2nd paragraph.

"With respect to flashing ROMs, Flashing a ROM will, in almost all cases, (except for one or two OnePlus A/B devices that also have a recovery partition) automatically replace the recovery with the ROM's own recovery. This behaviour cannot be changed. It happens because the recovery in A/B devices is part of the boot partition.

So, unless the maintainer of the ROM that you are about to flash has embedded OrangeFox within the ROM itself (and has announced this fact), you must, immediately after flashing a ROM (including an OTA update), flash the OrangeFox zip again, then change slots (only if the ROM's zip installer does not automatically do this), then reboot OrangeFox, before doing anything else. If you do not follow these steps, then you can expect problems (including the installed OrangeFox having been overwritten by the ROM installation)."

Here's what happens for me. I have OrangeFox flashed on B. When I install your rom, it does install on A as expected (it tells me that it's putting it there). When that completes, it says to reboot recovery to switch to the updated slot. So I tell it to reboot recovery, and it does reboot to your recovery on A. I can use your recovery to adb sideload Gapps and Magisk. But it won't boot to system. So I tried only doing the rom install without add-ons, hoping that I could boot to system. But no! I would think this should work, since I'm not trying to worry about more complication with slots and installing more zips.

A crazy attempt now, I tried going back to B and doing those add-ons with OrangeFox. It still won't boot system. (It did flash them on A, as desired).

So THEN I tried to understand that paragraph about flashing OrangeFox again. But I probably misinterpreted it... I couldn't get it to boot system after that.

I wonder if you can rewrite that 2nd paragraph for me, inserting slot A or slot B in the right places. You would base that on having OrangeFox on B, installing rom to A.

Again, I understand if you don't want to do this.

EDIT: When I say it won't boot system, it just comes up with a screen (sorry, I don't know what it's called) which has a solid white ball on the left and a black ball enclosed in a white square on the right....and it does that over and over. That pattern stays on the screen for maybe 10? seconds each time.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I clearly do not embed OrangeFox in my builds. So assuming you are now in OrangeFox (manually flashed to boot_b using fastboot) and you flashed my ROM (which was flashed into the A slot, because ROM zips are always installed to the inactive slot), you must flash the OrangeFox zip immediately (i.e. without rebooting to recovery). I've analysed the zip and it looks like it injects OrangeFox's recovery ramdisk in both slots' boot partition. Injecting it in the active slot is useless (the active slot, i.e. B, at this moment contains the OrangeFox you flashed with fastboot), the only useful operation to perform is to inject it in the inactive slot's boot partition (which contains my ROM's bootimage, i.e. stuff needed to boot Android, plus Lineage Recovery).

At this point, the inactive slot A has got OrangeFox in its boot partition. During the flashing process of my ROM, a flag was set to switch slots on reboot, so you can either reboot to system (if you want a clean system, without any other addon), or reboot to recovery, which will load the copy of OrangeFox injected by the zip in the boot_a partition.

You wrote: "A crazy attempt now, I tried going back to B and doing those add-ons with OrangeFox. It still won't boot system. (It did flash them on A, as desired)."

This is very strange. Only ROM zips are programmed to be flashed inside the inactive slot. If you are sure these addons were flashed from slot B into A, it must be that more advanced recoveries such as OrangeFox have got some functionality or setting that allows flashing any zip into an arbitrary slot.

Just to rule out any custom recovery/addon quirk, can you just flash my bootimage to either slot (e.g. B), and use it to perform a Factory reset + ROM flash (ROM will go to slot A), and then reboot to system (it'll reboot automatically to slot A), without flashing Gapps nor Magisk?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
@LMUJT when you are sure my LineageOS 21 build isn't affected by the charging issue, please flash this kernel on top of it and check if charging still works fine (it is ok for me): https://mega.nz/file/MtdTjRgZ#xziZGIKNTjM1LByjp72GErspiX2sSKrjIi9o7Oep6Sg
[Essential Phone ROMs, Kernels, Recoveries, & Other] just4me12:
Hi,

everything went fine for dirty flash for me. Now i`m waiting for a update of minimal microg. Thank you very much!!!! The charging problem is solved for me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LMUJT:
My Phone charged perfectly the last two days, so i installed the kernel. It is charging for now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
What do you mean with "i`m waiting for a update of minimal microg"?

Please try the new kernel I've posted, and let me know if charging is still ok.