yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] LoveScarGuitar:
Isn't one slot just for updates? So regardless, the ROM is only going to be installed on one slot. I don't think it matters which slot. Just whichever slot has the ROM, the opposite will be empty. I'm still trying to learn a/b partitioning, though.

As for the 'no touch' thing, I do know that you have to flash twrp on the opposite slot that you have the ROM. I don't think it matters which slot, but the slot that you originally install twrp on will have no touch. I only know this because I've installed twrp on the same slot as the ROM and had no touch. But I could be wrong.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ultrasuper:
No. A/B are independent boot/system partitions, but they both share ONE data partition. Either A or B could be active, while whichever is inactive will take an system/OS update, and upon reboot, will then *become* the active slot.

Touch not working had something to do with TWRP being built using August dependencies but your installed system has different ones on it (because you had already updated to September) AFAIK.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Since we have the TWRP A/B Retention Script of [MENTION=4544860]osm0sis[/MENTION] in a Magisk module . . . we may be lazy and it doesn't matter if we are right or wrong.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Exactly correct.

Touch not working has to do with the "temporary" TWRP.img due to the fact that it was built on the August kernel but in the September release, Essential updated the rpm and hyp partitions that had never been updated before that have to do with touch working, therefore if you have September installed, you need a kernel built for September for touch to work.

If you follow my directions in post #86, they say how you can install the TWRP installer zip (which will work with touch on any past, present, or future kernel) from TWRP.img using 2 adb commands in place of touch. And since we are now lucky enough to have a TWRP installer zip, we will always have a version of TWRP that can be installed and works.

[MENTION=6513322]LoveScarGuitar[/MENTION]:

Also at that link I have a detailed explanation of why touch worked for some with the temporary TWRP.img. It's not due simply from flashing it to the inactive slot. It's because the inactive slot still had the August release on it for many people. So when October comes out, people will have October on active and September on inactive slot and touch in TWRP.img won't work on either. But with those 2 adb commands in my post, you can still flash the twrp installer zip without touch working.

https://xdaforums.com/showpost.php?p=77597383&postcount=86

---------- Post added at 04:46 ---------- Previous post was at 04:39 ----------

I saw that module and got pretty excited, unfortunately I'm not sure if that module will work on the Essential. If you follow the link I posted, with Dees' TWRP installer zip, you will always have a working TWRP installed into your current boot image, even if touch doesn't work with the temporary TWRP.img that you use to flash it. Just be sure to redo the instructions after each monthly update.

If you try osm0sis' module when the October update comes out, please let us know the results.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Well edit 2 here.

Contacted osm0sis and send the log.

Something with Pie and changes is Magisk.

New version of the TWRP AB Retention script is now available in Magisk manager - Downloads.

Working great on my PH-1.
[Essential Phone ROMs, Kernels, Recoveries, & Other] guliver365:
I had TWRP working pretty good until II updated the. Phone to the OTA October Tru TWRP, now I lost it since the original boot image deleted it. Is there a way to have it installed permanently?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I have a patched twrp magisk stock boot for magisk up on my afh if you have any need
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
The October update doesn't install. Dunno if it's because of twp, magisk, or both.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Jz5678910:
Had the same problem, even when removing both it didn't work, so I just sideloaded the ota image from essential website and it worked like a dream.
[Essential Phone ROMs, Kernels, Recoveries, & Other] spotmark:
Just did my first update and root without having to get off my couch. Loving permanent TWRP. :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
in adb or fastboot?
[Essential Phone ROMs, Kernels, Recoveries, & Other] brqndon:
I have permanent TWRP and Magisk installed. What is the most convenient method to update to the October patch without losing root.

Thanks in advance!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Jz5678910:
I believe it's adb. I did it through essential stock recovery.

Edit: I followed the instructions on the webpage where you download said image.
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
yeah i meant recovery instead of adb. im trying it in twrp sideload, if that doesnt work, i might use the fastboot image and then reinstall twrp and magisk and all of that. i wish the ota would have worked.
[Essential Phone ROMs, Kernels, Recoveries, & Other] spotmark:
Download Oct. OTA from Essential site to your phone.

Boot into TWRP

Flash October update

Flash TWRP installer

Reboot

Boot into TWRP

Flash Magisk (I assume you already have it on your phone.)

Reboot
[Essential Phone ROMs, Kernels, Recoveries, & Other] brqndon:
Thanks so much. Will do the above steps. And hopefully I can do so without leaving my couch just like you did. Lol.
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
so i did the sideload. it worked, but theres twrp wasnt installed. so i tried to flash twrp and when i boot into it, theres no touch, no matter what i do.

---------- Post added at 11:43 PM ---------- Previous post was at 11:33 PM ----------

all sorted, i found a useful post -> https://xdaforums.com/showpost.php?p=77597383&postcount=86
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Follow my instructions here: https://xdaforums.com/showpost.php?p=77597383&postcount=86

Edit: Looks like you found them! Can everyone who has found them helpful please thank the post so it will move up higher and it will be more visible to more people? Keep getting asked the same question almost every day, literally. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] ultrasuper:
Preamble: I have NOT yet done the Oct update; so I'm still on Sep (Active part _a), with August Pie on _b

So in my (rather long and detailed) post #187, I say that when I boot into (now permanent) TWRP, and switch Active Slot to _b, and reboot, it boots (only) to the TWRP on _b.... But if your statement is accurate above, why doesn't TWRP have touch working in that instance of TWRP there?
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Because using that method, you are flashing the twrp.img to your inactive slot (as it's boot image where recovery is stored). Then applying the TWRP installer zip which injects both slots with twrp. But your inactive slot doesn't have the correct (stock) boot image on it anymore, it still has the non-touch working TWRP.img on it for it's boot image -- so all it can do is boot directly to TWRP with non-working touch (this is the reason you flash TWRP.img to your inactive slot to begin with, so you don't alter/corrupt the boot image of your active slot with the TWRP.img).

So if you want touch to work on both slots in TWRP and both slots to boot to Android, you would need to flash the correct stock boot.img to your inactive slot after you get touch working on your active slot and flash the TWRP installer zip again. However, I don't see any reason when this would be needed.

I hope that makes sense.

---------- Post added at 02:46 ---------- Previous post was at 02:13 ----------

Thanks!

Yes, once you have TWRP permanently installed just once, upgrading like this every month is by far the easiest way. Thanks vm for the info!!

Just one little tip to make things even simpler, no need to reboot between flashing TWRP installer and flashing Magisk. You can simply boot into TWRP, flash OTA, flash TWRP installer, flash Magisk. Bing, bang, boom! Done! When you flash the OTA zip in twrp, it installs to the same slot (it doesn't install to the other slot like when sideloading it from stock recovery). Of course it doesn't hurt either :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] yankeefan:
I am at a loss as what to do after searching threads. I sideloaded ota and now I cannot get any fastboot commands to work. I get nothing with adb devices but when I use 0x2e17 I get connection. I even tried to restore from a file downloaded from essential it does not go anywhere. Tried to see about installing TWRP can I do that. I have tried it on two different computers with multiple cables and ports. Every action I does comes back with failed any suggestions. I did do a factory reset and still no luck
[Essential Phone ROMs, Kernels, Recoveries, & Other] bmg1001:
Are you 100% certain that flashing the OTA zip in TWRP doesn't flash it to the opposite slot?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
I've flashed a few hours ago the official October OTA zip with TWRP (active slot). The built-in installer uses 2 steps. After step 2. The updated October version is in the opposite slot.

EDIT

That's why there are 2 official images: OTA and Fastboot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] bmg1001:
Yep, OTA flashed to opposite slot when I flashed via TWRP. Not sure how he got the OTA installed to the same slot....
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Depends how you flash it. If you flash it like any other regular zip by clicking install, it should flash to same slot.

If you use the adb sideload command to install it in TWRP (just as if installing from stock recovery), then it flashes to the opposite slot just like from stock recovery.

---------- Post added at 14:15 ---------- Previous post was at 14:01 ----------

Just FYI, that has nothing to do with why there are two ways to download and flash it (fastboot and OTA).

The OTA zip can be installed with the bootloader locked, and if you unzip it, there's not separate images for all the separate partitions inside of it -- just one big compressed file.

The fastboot zip requires the bootloader to be unlocked and allows the user to flash one or all partitions. To flash each partition requires a separate fastboot command. It also allows you to flash an older version on top of a newer version. It gives much more freedom to those who want or need it.

It's just a stock feature of how and why A/B exists that flashing an OTA flashes to the opposite slot, so in case the install craps out, you still have your previous system on the other slot to fall back to. A/B also allows actual over-the-air downloaded OTAs to be installed while still running Android since it's installing to the other slot. Before A/B, if you took an OTA update over-the-air, the phone had to reboot to recovery and take 5-10 minutes to install it, during which time you couldn't use your phone.

However, the OTA downloadable zip was meant to be installed using adb sideload. If you flash it like any other zip in twrp, it doesn't flip slots.
[Essential Phone ROMs, Kernels, Recoveries, & Other] bmg1001:
You sure about that too? It doesn't matter whether you sideload it or not. The OTA zip will install to the opposite slot regardless, just like every other ROM zip.
[Essential Phone ROMs, Kernels, Recoveries, & Other] izzyfanto:
Excuse my ignorance, what is the benefit to installing to the same slot? Won't the OTAs just ping pong installs back and forth between slots each month?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
On my PH-1 the OTA's play ping pong.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ultrasuper:
Let's see if I follow this. (Two points of confusion below)

Agree.

Is this not exactly the same as your previous line, except that it happens in BOTH slots? -- Flashing the TWRP.zip package to both slots (as each slots' boot image where recovery is stored)?

(1) Time out: This TWRP.img (the initial temporary one)

HAD working touch for me

. THEN I proceeded to install the TWRP.zip (permanent; installed to both slots now--- I assume

also

overwriting the "currently running", "temporary" TWRP.img I installed above).

Are you saying that the temporary, TWRP.img is NOT serving the same purpose as TWRP.zip (i.e., a BOOTABLE image)? My assumption is they both get flashed, as bootable images. I further assumed (as I just said in the previous line above) that once I flashed TWRP.zip, it overwrote TWPR.img in the inactive slot. So TWRP.zip exists on both slots now. One slot is active with a COMPLETE ROM/TWRP/Magisk, the other only has TWRP.zip now.

Is that correct?

(2) And when I switch to the inactive slot, TWRP comes up but touch doesn't work, why? Because I don't have the ROM (or kernel) there anymore with the requisite drivers for touch? (Maybe because initially installing TWPR.img as a sideloaded install overwrote the ROM image that was there?)
[Essential Phone ROMs, Kernels, Recoveries, & Other] TheBurgh:
This method worked like a charm.
[Essential Phone ROMs, Kernels, Recoveries, & Other] techlogik:
Wanted to post a big thanks again to the Dev and update to TWRP. Updating to the latest Ota was easy and smooth.

Appreciate the work you put into this.

---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------

Edited
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
What you described is for me the reason to sync both slots.

When the October update with twrp and root are working.

- flashed the official October OTA.zip (again) with twrp, to install a stock version in the opposite slot.

Still in twrp I reboot back to the active slot.

With Magisk manager I installed:

- module TWRP A/B Retention script.

- Magisk root to the opposite slot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] izzyfanto:
I've never heard of this, what does it do? Is it a Magisk mod?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Thebear j koss:
Yez
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
It's a script that can be flashed with Magisk manager. It patches the boot image in the opposite slot with TWRP that's in the active slot.

With Magisk manager it's now possible to install TWRP and Magisk-root to the opposite slot.

EDIT I've found it in thread of [MENTION=4544860]osm0sis[/MENTION].
[Essential Phone ROMs, Kernels, Recoveries, & Other] V0idst4r:
Thank you so much for finally making this official build! <insert extremely controversial informal bug report>
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Not to be a smartalec, but the old twrp11.img build of TWRP that we've had available for I think more than a year now could backup and restore full backups (boot, system, and data without data/media) perfectly fine. I did it quite a few times.

What it couldn't do, however, was be permanently installed, nor decrypt data if you had a lock screen pin/pattern/password set (maybe that was your issue), nor backup or restore the vendor partition, plus it was built from a much older version of TWRP (3.2.1 vs 3.2.3) so it lacked additional features and fixes, and finally, starting with the September update from Essential, the touchscreen would no longer work in it making it almost completely useless without an OTG mouse (all you could do was flash zip files using the adb sideload command without an OTG mouse).
[Essential Phone ROMs, Kernels, Recoveries, & Other] V0idst4r:
It would backup but couldn't restore data. It'd always fail with

createTarFork() process ended with ERROR: 255

.

Also it wouldn't be useless because you can backup and restore from adb in TWRP now too.

adb backup --twrp system boot data cache

and

adb restore

etc...
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
I used it to backup and restore as well.. i also used it to decrypt my entire phone..with the help of the no verity zip by zackptg and the format data option. Then, u did not have to disable security. It worked even with fingerprint.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Thanks, [MENTION=223132]Jack[/MENTION], for the backup (no pun intended lol). As I had said, I also had used it to backup and restore successfully many times. I'll never understand why when something doesn't work for one person, they always assume it must be the same for everyone else.

Edit: You have no idea how close I came to also decrypting. It was such a giant pain to have to remove lock screen pin/pattern/password, which in turn deletes all fingerprints, which then means every program has to be logged back into using a password after using that old TWRP and adding lockscreen and fingerprints back on. Thank goodness those days are over!

---------- Post added at 04:52 ---------- Previous post was at 04:48 ----------

I didn't realize that old version was new enough to do adb backup. But regular backup and restore (commonly still called a nandroid) worked fine here. Why it gave you an error, I have no idea.
[Essential Phone ROMs, Kernels, Recoveries, & Other] V0idst4r:
No need to be rude. It gave an error because it couldn't properly handle the permissions of a file I had. I didn't mean to give the impression that nobody could backup at all, I just tested it and it failed because of something in

/data/sytem_ce

Pretty sure it had something to do with multi-user/work profiles. Point is, it's fixed now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
I found the solution here: https://xdaforums.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976

I don't think it's ever needed with the new official TWRP, but if it is, now everyone will be aware of the fix.

"extractTarFork() error when restoring data from a TWRP backup

1. Reinstall the ROM from which the backup is based on.

2. Wipe your data. You can do this from the recovery or from fastboot using the command

Code:

fastboot -w

3. Boot into the ROM. When going through the initial setup, use the EXACT same security setup as the one from your backup. For example, if you used a Fingerprint + Password in the backed up ROM, use the exact same combo along with the exact same password as well. There is no need to set up anything else, like accounts.

4. Flash, install, and reboot into TWRP. You should now be able to restore the data backup without any issues."
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
hi, I installed as a guide to the twrp, but the touch does not work, how do I solve
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
https://xdaforums.com/showpost.php?p=77597383&postcount=86
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
Fastaboot devices = Ok

adb devices = not

PC Windows 10 64 bit

Driver essential installed = ok

Patch the october in the my telephone

How do I make my PC see the phone in adb ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
It should see it anytime you are in TWRP (not to mention when in Android). You've never used adb?

Check device manager and see if there's anything with an exclamation mark when phone is connected and in TWRP. Also try a different USB port.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I always used fastboot, in adb i can not, I do not se the phone. in device manager and all right.

I have to try plugging it in when the twrp and on the phone to see what it does in device manager.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
ok adb devices

write me the commands to run now in adb to complete installation of the twrp, consider that the file twrp-installer -mata-3.2.3-0.zip and on the dir sdcard
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I redid the procedure and does not go into revovery mode, only in fastbooot mode, which happened, even reactivating slot A, goes only in fastboot mode. Help help

after 10 minutes it is restarted regularly, what do I do?
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
If you followed all the steps in post #86, and have TWRP working with touch, all you need to do is flash magisk.zip.

If you flash that file, it's undoing and redoing all the work you just did. However, if you decide to still flash it, it would go to image boot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
It all works, but the red windows is left, useless work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
If you are talking about the red varity warning when the phone turns on, you accidentally tripped varity. It's pretty easy to fix.

First, you need to make a backup of your current boot.img:

Boot to fastboot and run the following command to determine your current slot:

fastboot getvar current-slot

It will say _a or _b. This is your current slot. Write this down. Don't lose it. Very important!

Now boot into TWRP.

From TWRP, run ONLY ONE of the following two commands

if your current slot is _a:

adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/

OR

if your current slot is _b:

adb shell dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/

The backup of your current boot image will be stored at /sdcard/boot.img. Copy it to your computer using the method of your choice. Make sure you have this file on your computer before going any further!!!

Then, go to bootloader and fastboot flash this file to boot http://gg.gg/ai7m1

fastboot flash boot boot.fix.red.img

Then restart the phone.

The phone will start booting, then stop and start again. This will continue to happen. Let it happen at least 2 or 3 times, then hold the volume down button to return to bootloader.

Now from bootloader, flash the boot image you had backed up to your computer at the beginning.

fastboot flash boot boot.img

That's it. You're done. Restart the phone and the red warning will be gone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
And this is the red window
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Sorry for the long quote of you both.

[MENTION=943156]nibera[/MENTION] what are/were you running?

[MENTION=2557531]starcms[/MENTION] he has asked in multiple threads, with us generally giving the same answer, wonder if it's possible the fix red boot doesn't work on P, if that's what he is on? I haven't managed to trip verity on P yet, so I haven't actually tested it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
It works on P; I've tried.

And honestly, it wouldn't matter what ROM he is on. The fix works at the bootloader level.

---------- Post added at 03:55 ---------- Previous post was at 03:54 ----------

I know what the red window is! And I just gave you very detailed instructions on how to fix it! Thanks for wasting my time if you aren't even going to follow them.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
Hello, meanwhile I apologize but the fault is only mine because I asked the same information on two threads, your time is not wasted and your information is useful for me and for the whole community, as soon as I return today I will do the same, you terro updated.

thanks and again sorry.

I apologize for the translation but I use google translator to communicate on this xda forum
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Lol, calm down killer. I know all that too :highfive:
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I just did a bit of confusion, and my fault.

sorry
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I have done the procedure you indicated and I am attaching the screen, I think it has not created any backup file of the boot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
He forgot one thing in his instructions.

That DD command requires a name at the end of the last slash.

Just type in boot.img or something, then it will work.