yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Talking about me and those instructions I posted one page back? Happy to be of help!

---------- Post added at 15:24 ---------- Previous post was at 15:23 ----------

The hyp and rpm partitions to my knowledge had never been updated before the September release of Pie.

---------- Post added at 15:36 ---------- Previous post was at 15:24 ----------

See comments above in italics

---------- Post added at 15:43 ---------- Previous post was at 15:36 ----------

You are missing a step or flashing Magisk before flashing the TWRP installer zip.

You flash the TWRP.img once. It's just temporary. Then, before you flash the TWRP installer zip, make sure you have the stock boot image installed on your active slot. Then flash the TWRP installer zip, switch back to your active slot (if you had switched to the Inactive slot), and then lastly flash the Magisk zip.

Edit: Also after you flash the TWRP.img, you don't have to select boot into recovery. Just boot like normal and it'll boot into TWRP recovery. Did you try redownloading the new TWRP.img file? It sounds like yours is corrupted. Also, since you have September on both slots now, touch won't work when you first boot into TWRP. Use the instructions I posted on the previous page to be able to flash the TWRP installer zip when touch in TWRP isn't working.

---------- Post added at 15:51 ---------- Previous post was at 15:43 ----------

Yes,both slots can be rooted (or only one can be rooted since they each have their own boot image). The only thing that determines if a slot is rooted is if Magisk has been installed to it which installs to the ramdisk in the boot partition(kernel).

When you are booted to the slot that is rooted, open Magisk manager, choose install, and select install to inactive slot. Now they'll both be rooted.

But just to repeat, you definitely shouldn't be utilizing the slots as a way to run two different ROMs or really even two copies of the same Essential image/ROM. That's not what they are meant for because /data is shared between both slots. Just stay on the slot that has the latest Essential image installed (or the custom ROM you want to use installed)
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
thanks for following up!

i removed my previous reply because i figured out what the problem was.

*sigh*

when i had gone to the TWRP site to download the img file, and when i had clicked on the 'Download twrp-3.2.3-0-mata.img' link, nothing happened, then i right clicked on it and saved file as...and THAT was the file that i was flashing.

it was your suggestion of th efile being corrupt that got me to check the md5 on it, and that is when i saw it was wrong!

this time, i opened up a different browser and when i clicked on the 'Download twrp-3.2.3-0-mata.img' link, it downloaded just fine and the md5 matched.

i changed slots...i flashed the twrp.img...i rebooted...and it booted into TWRP!

it doesn't have touch, as you said it wouldn't, so i have to work on that (after i adb sideload twrp-installer-mata-3.2.3-0.zip, touch still didn't work and i couldn't cleanly exit to the bootloader, so i had to do a hard reboot which lost temp load of TWRP, i think)

anyway, it was my bad and i wanted to let you know that i figured out what the issue was with it rebooting into bootloader, and that your suggestion of a corrupt img file was what was the solution.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Glad I could help :)

After doing the previous command followed by adb sideload twrp-installer-mata-3.2.3-0.zip like in my instructions, you should now have permanent TWRP installed with working touch. Let me edit the instructions and add a line to reboot after the sideload is complete because touch will not start working immediately after the sideload. adb reboot bootloader. Forgot about that.

If you don't have working touch on TWRP when you choose to boot into recovery, it sounds like the sideload may not have completed. Did you redownload the TWRP zip also? Cause if you downloaded them both the same way the first time, I'll bet the zip file is corrupt also.

Regardless, it doesn't matter that you did a power button reset to exit TWRP, you'd still have the TWRP.img with no touch on your inactive slot and a working TWRP with touch on your active slot if the sideload was successful. So it really sounds like your TWRP zip is corrupt also.

Lastly, even when the sideload is successful, touch in TWRP won't start working immediately. At the very least, after the sideload, you would need to reboot to bootloader, change back to active slot, and then you'll have working touch when you load TWRP, like it says in my instructions.

Redownload the zip, then follow my instructions. I updated them to add the command to be able to reboot out of the "temp" TWRP with no touch.
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
profit!

yeah, i was rushed and i didn't think it though and didn't follow through, and i didn't grab the zip file, again. i should have thought of that right when i realized what had happened with the .img file.

hey, thanks for all your help!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] thirtythr33:
awesome bro thank you for the hard work!
[Essential Phone ROMs, Kernels, Recoveries, & Other] zestar_77:
So I have the september image, with the augest hyp and rpm files, and twrp installed.

Touch works, both in twrp and when booted to android.

However, what doesn't work when booted into android is WiFi. refuses to turn on.

So I went and uninstalled magisk, rebooted, problem not solved.

Then I went and flashed the september hyp and rpm files, and boot.img patched with magisk, rebooted and WiFi works.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Spaine Lilang:
Forgive me if I'm missing something here, but does this mean it will always be on a slot?:confused:
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Don't be flashing old parts of firmware (like hyp and rpm) or bad things will happen. If you are flashing using the fastboot method, flash all files in the package. Don't go back and flash older versions of some (like hyp or rpm). Follow my instructions 2 pages back on how to install the TWRP installer zip if touch is not working in the "temporary" TWRP.img. And the best way to update to the new version every month is with the OTA download.

---------- Post added at 22:24 ---------- Previous post was at 22:18 ----------

Will what always be on a slot? When you flash the TWRP installer zip, it flashes TWRP into the ramdisk of your boot partition (kernel). In other words it "injects" your kernel with TWRP so it will stay permanently installed (until your kernel is updated). When the October update comes out, it will come with a new, updated version of the kernel, so you'll have to install TWRP again using the TWRP installer zip and my instructions 2 pages back on how to install the installer zip when the touchscreen doesn't work with the "temporary" TWRP.img. Because when October comes out, no one should have August on their inactive slot (they should have September), so touch won't work for anyone in the "temporary" TWRP.img unless it is updated by the dev between now and then. But my instructions are basically just two extra adb commands. Very simple.

---------- Post added at 22:27 ---------- Previous post was at 22:24 ----------

No problem, glad you got it working!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
[MENTION=2557531]starcms[/MENTION] you and [MENTION=912474]Dees_Troy[/MENTION] are da real mvp's. Thank ya both kindly.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Koncrete:
Just wanted to post up some issues "I" had....

I've had 8 and 9 beta and full release. Never had an issue flashing any boot.img or version of magisk.

Had August release on here, tried flashing twrp it pushed then failed. Tried erasing the partition then flashing twrp, no dice. Tried flashing my patched boot, nope... Stock boot... Ain't happening... In a slight panic I tried Sept ota... 5min later I'm alive again but now unrooted...

Back to bootloader to flash twrp, HAH no twrp for you... Again it sent package but failed. No matter which slot was active so I flash the OTA again because now I can't boot...

So I download a couple of prepatched Sept boot imgs, one with magisk and one with twrp... Off to the batcave, and again stock, magisk patched, twrp+magisk patched, twrp by itself...

All send then failed... So I OTA again and start reading.... 45min later I'm at Best buy buying a "CHEAP" 20 usb a-c cable.

I get home...

adb reboot bootloader

Success

Fastboot flash boot twrp.img

Success

Fastboot reboot recover

Success

Twrp flash twrp

Success

Twrp flash magisk

Success

Whiskey tango foxtrot lollerskates

Same cable I've been using just all the sudden doesn't like me
[Essential Phone ROMs, Kernels, Recoveries, & Other] TheBurgh:
Curious to see if anyone has successfully backed up and restored through the official TWRP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] DroidBoy123:
Does full system backup and restore work on this? [MENTION=912474]Dees_Troy[/MENTION]
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Yes, tested here, works perfect.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Backups and restores work fine. Worked fine on old twrp too. Works with gsi's too
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
What did you come from before the restore? I tried to install LOS16 with no luck and then tried to restore my nandroid after a wipe also with no luck. I assume I can switch slots in TWRP and restore to either one? Not overly familiar with A/B slot phones just yet.

Another quick question. If I sideload while on slot A in twrp what slot does it install to? I would assume B, it would install into the opposite but I am not sure.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
I came from and restored to the official September release.

No, you can't restore to any slot and here's why. When you are restoring, you are only restoring /data (without /data/media, but that's not important right now), /system, /vendor, and boot (kernel). You aren't backing up or restoring the other parts of the firmware that can change each month (like hyp and rpm which caused so many issues this month in the September update). So you either need to restore to the slot you backed up from, or to be completely safe, install the fastboot download package from Essential's website that matches the version you are restoring to the slot you want to restore to (so all the parts of the firmware will definitely match and work with your backup) before you restore.

If you sideload the OTA download from Essential's website while on slot A, yes, it will install to slot B and vice-versa. If you sideload just a regular zip file from TWRP (instead of clicking install and flash), it will install to the current slot. Although some zips are specifically made to flash to both slots, like the TWRP installer zip.
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
Thanks man, greatly appreciate the info. I tried to flash Los 16 through TWRP and it messed things up. But I think try to adb/fastboot from my Mac laptop was my biggest problem, nothing seemed to work. Switched to windows and back up and running in 10 minutes, following your little guide.

I might try again and pay a little more attention to the slots.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
If you are flashing to another ROM (LOS 16), you need to wipe /system and /data in TWRP before. I don't know if you need to wipe /vendor also, it depends on the ROM. Read their instructions.

Lastly, you need to find out if the latest version of LOS 16 is built using the Setptember kernel and firmware, or if it's still being built from the August firmware. Because if it's still being built from the August firmware, you'll need to flash the August fastboot package from Essential's website before installing LOS 16 or the touchscreen and possibly other things like WiFi won't work in LOS 16.
[Essential Phone ROMs, Kernels, Recoveries, & Other] fredgar75:
Awesome! Thank you for this!
[Essential Phone ROMs, Kernels, Recoveries, & Other] dirtyreturn:
Hey XDA, is twrp supposed to be listed as the kernel source? Edit - when a/b partition are flashed? If so, has anyone experienced lock-ups with the UI?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Twrp is not listed.

Since my PH-1 is rooted I switch kernels with EX-manager. And boot in twrp-recovery with the app of Franco (simple reboot)

Maybe the kernels that work on my PH-1 are useful. Twrp and root are included. Stock boot Sept. update (4.4.152)

https://www.androidfilehost.com/?fid=1322778262904005331

Same but with ElementalX kernel ex308.

https://www.androidfilehost.com/?fid=1322778262904005332
[Essential Phone ROMs, Kernels, Recoveries, & Other] HACK3DANDR0ID:
Dam I missed a lot being sick for a week.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Not sure exactly what you are asking, but if you back up the boot partition in TWRP after installing twrp with the twrp installer zip, TWRP will be backed up as well. The TWRP installer zip "injects" your boot image (kernel) with TWRP, very similar to how Magisk installer zip " injects" your boot image with Magisk.

If you are installing both TWRP and Magisk, TWRP zip must be installed/flashed before Magisk or the device will continuously boot to TWRP.

---------- Post added at 14:16 ---------- Previous post was at 13:59 ----------

Make sure you read my instructions on page 9 in case the "temporary" TWRP.img doesn't have working touchscreen.

I highly recommend that everyone save a copy of those instructions. Because if the "temporary" twrp.img isn't updated to be based on the September (or newer) boot image/kernel, no one will have working touch in the "temporary" TWRP.img next month when October comes out​

because October will be on the active slot and September on the inactive slot. (August, which supports the old firmware with the old versions of hyp and rpm, will no longer be on the inactive slot so touch won't work for anyone in the "temp" TWRP.img, even those who had no issues with touch working this month).

But the touch not working in the "temp" TWRP.img is really no big deal. The only reason you use the "temp" TWRP.img is so you can flash the TWRP installer zip. And with the 2 commands in my post on page 9, you can flash the TWRP installer zip even with touch not working in the "temp" TWRP.img.
[Essential Phone ROMs, Kernels, Recoveries, & Other] dirtyreturn:
Yes, I was not clear enough. Is TWRP supposed to be listed under kernel in 'About Phone'?
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
No
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
According to the Essential TWRP GitHub page, [MENTION=912474]Dees_Troy[/MENTION] pushed a commit with a ton of fixes less than a day ago, including the "temp" TWRP.img using the September kernel (so touch will work on it) plus it looks like he's trying to get the screen centered, amongst a whole lot of other changes. He hasn't built updated versions on TWRP.me yet, probably doing testing and possibly other changes before we get an updated version. But he's definitely working on it! Thank DT!!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Delete
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
I never say to use the "fastboot boot" option. I say to flash the TWRP.img and then boot into TWRP. That's pretty clear. You are the only one confusing people by mentioning a command that doesn't work on the Essential.

Anyway, the key to the instructions are the two adb commands that let you install the TWRP installer zip without the touchscreen working in the "temporary" TWRP.img. The rest of the instructions are just an abbreviated version of the official instructions on twrp.me.

If they aren't good enough for you, then don't use them. They have helped countless people in this thread.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Wasn't my intention.... Post deleted
[Essential Phone ROMs, Kernels, Recoveries, & Other] schweigster:
I was able to flash recovery to the b slot (though I note "_b" did not work, I had to put just "b")

---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------

Per the instructions, I was able to flash recovery to slot b (though I note I had to specify "b" rather than "_b"), as this is not the main slot. I went into TWRP, changed back to slot a, and flash the TWRP zip, which was successful. When I try to reboot system, it just boots back into TWRP (also it takes a while on the TWRP splash screen before booting into TWRP; I don't know if this is normal for this phone). I had to reflash the regular ROM boot.img to reboot my system. This, of course, erases TWRP. Any ideas as to how I can get TWRP flashed while keeping the ability to boot normally?
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
Remove Magisk. Boot TWRP temp from an unrooted ROM. Once TWRP is installed you can flash Magisk from it like normal.
[Essential Phone ROMs, Kernels, Recoveries, & Other] schweigster:
Thank you! That worked! I should have realized I needed to start from a clean boot.img. Love this phone even more with a permanent TWRP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] YunolexDDP:
Uh..my build number is PPR1.180905.036 and the touch screen still cant work qwq
[Essential Phone ROMs, Kernels, Recoveries, & Other] demilenos:
I cant change slot. I use latest adb and latest OREO build. I sure device unlocked too.

"H:\Android\mata>fastboot --set-active=a

Setting current slot to 'a' FAILED (remote: 'unknown command')

Finished. Total time: 0.000s

H:\Android\mata>

H:\Android\mata>fastboot --set-active=a

fastboot: error: Device does not support slots"
[Essential Phone ROMs, Kernels, Recoveries, & Other] Thebear j koss:
Fastboot getvar current-slot

Fastboot set_active other
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
Cannot seem to paste into this from the XDA app.

Looks line you got your answer anyways. Your commands are incorrect.
[Essential Phone ROMs, Kernels, Recoveries, & Other] demilenos:
Very nice to see help but...

"H:\Android\mata>Fastboot getvar current-slot

current-slot:

Finished. Total time: 0.001s

H:\Android\mata>Fastboot set_active other

fastboot: error: Device does not support slots

H:\Android\mata>"

I changed to CtoC, AtoC stock cables but none work.

There is no problem in fastboot works before. I really have no idea...
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Unplug your phone...

Run the command...

Then plug your device in
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
On one of my computers I get those exact same messages. In my case the solution was to reboot into bootloader and try the command again. I discovered that I can only give one command in bootloader successfully, then I get messages just like that. So I give a command, it works, I reboot into bootloader and do the next command, etc.

Not saying this is your problem, but it's worth trying.
[Essential Phone ROMs, Kernels, Recoveries, & Other] demilenos:
thx so much dude! it works.

flashing is problem now. I cant pass writing stage.

ps. it bcuz wrong partition name. I fix now. nevermind.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
Your active slot is a. You have to put _a after the boot command, like this: fastboot flash boot_a twrp.img
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
I also found

fastboot set_active other

not to work.

Use:

fastboot getvar current-slot

Followed by:

fastboot set-active=_a

OR

fastboot set-active=_b

(It needs to be _a or _b, not simply a or b)

Same as for flashing:

fastboot flash boot_a twrp.img

OR

fastboot flash boot_b twrp.img

I'm pretty sure it depends on the version of fastboot installed on your PC. For the very newest version of fastboot from the Android SDK, you must use these commands.

Edit: A slightly older version of adb and fastboot, but possibly more customized for the Essential (I haven't tried it), is installed in your Program Files(x32)/Essential folder on your PC when you install the drivers from Essential's website. It is also automatically added to PATH. But it sounds like you got it working, so I wouldn't worry about it.

---------- Post added at 01:04 ---------- Previous post was at 01:04 ----------

Read my instructions, page 9, post 86.

https://xdaforums.com/showpost.php?p=77597383&postcount=86
[Essential Phone ROMs, Kernels, Recoveries, & Other] demilenos:
I agree that, I recently changed adb newest version. Seems now partition parameter need specify slot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Osmatic:
Damn i'm confused.

Received fresh new PH1 with 7.1.1 preinstalled on both slots. Downloaded the latest Android 9 Pie, Release 2 Fastboot archive.

Flashed it (based on *.bat file content to both slot A and slot B).

Installed the TWRP IMG through flashing it to slot B, got non-working touchscreen. Used Type-C to USB adapter with logitech mouse (works good in TWRP), installed TWRP ZIP which showed status "installing both slots A and B". Now when booting to slot A, TWRP touch is working, but none while slot B is active. What i'm doing wrong?

BTW, TWRP logo is shifted left - is it ok?
[Essential Phone ROMs, Kernels, Recoveries, & Other] ElfinJNoty:
There's a temp TWRP zip and a TWRPinstaller.zip you need to flash once from within booted temp TWRP. Then you should be golden
[Essential Phone ROMs, Kernels, Recoveries, & Other] YunolexDDP:
Uh I...have a new problem. I use "adb shell twrp install" to install twrp-installer-mata-3.2.3-0.zip and it seem to work...but later I flash the stockboot and flash magisk. Than I cant boot into the system. It reboot itself to the stock recovery when it finished booted. And told me cant start up the system and two options down below "try again" "factory reset"

Is my stockboot file is incorrect?
[Essential Phone ROMs, Kernels, Recoveries, & Other] thirtythr33:
just wanted to thank you for the hard work making this possible. I was wondering when I will need to reinstall twrp now that it is permanent? I'm running latest aosip w/stock kernel, will I be able to flash the next build and keep twrp?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Because you used the TWRP installer there was no need to flash the stock boot.img. You need to re-adb the twrp installer.

When the active slot has the September update you may try first to flash one of the patched boot images mentioned in post 120.