yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] ultrasuper:
SO you have to unroot (basically re-install the stock boot image of version in use) , and have to remove Magisk too (thereby removing any installed modules as well).

The procedure(s) in the poll necessarily involve losing "things", and requires one to un-root before proceeding.. ?

Afterwards, you have to re-install a new copy of Magisk (rooting, like in the OP) and re-install (and config if necessary) any Magisk modules you were previously running.

?
[Essential Phone Guides, News, & Discussion] NLBeev:
Yes. Flashed stock boot and system images.

No; because the current boot.img AND system.img are reflashed.

Depends. Probably not. Afterwards you need to flash a patched_boot.image created with Magisk manager on your PH-1.

You need to prepare this (extracting the new boot.img from the PH1-factory zip)
[Essential Phone Guides, News, & Discussion] guliver365:
I am unable to use TWRP-mata- 11.img I reinstalled PH1-Images-PPR1.180905.036 download fast boot .img, ElementalX PX 3.08 and Magisk

So I flashed TWRP but when I reboot in recovery I cannot click or use the slider the screen digitizer is not responsive in TWRP, just stuck there until reflash PH1-Images-PPR1.180905.036, any Ideas?
[Essential Phone Guides, News, & Discussion] lynnux:
Here's what I did:

*Sideloaded new OTA file from Essential onto phone

*Boot into system, I was now unrooted

*Grabbed boot image for current build from op

*Used MM to patch new boot image via "Install"

*Moved new patched boot image to my Chromebook

*Rebooted into bootloader, fastboot flash new patched boot image

*Reboot phone. I was now rooted, lost nothing. MM remembered everything I'd given root permission to, all modules remained.

No twrp. No removing fingerprint/passwords. No loss of anything.
[Essential Phone Guides, News, & Discussion] Lakino:
Thanks lynnux for the step by step.

One question: did you or do you use EX Kernel? If one uses EX Kernel, what additional steps would one need to take to ensure a smooth and successful upgrade?
[Essential Phone Guides, News, & Discussion] bmg1001:
Unfortunately, if you're on the September Update, it seems the only way to make touch work in TWRP is to either attach a USB OTG mouse, which magically makes touch work for some reason, or to flash the old "hyp" and "rpm" partitions temporarily, which would also require you to flash the new ones again whenever you're done with TWRP so that you have touch in the system. You may also be able to use an older kernel for the August patch along with the old hyp and rpm partitions, but I don't suggest that to be honest, not that stuff will break, but I don't know what changes Essential made.

This also requires you to have done "fastboot flashing unlock_critical"

hyp and rpm images for the September update

hyp and rpm images from the August update

Slightly more detailed explanation could be found at this Reddit post.
[Essential Phone Guides, News, & Discussion] munchy_cool:
if our TWRP recovery flashed Magisk to both then this could have been avoided. I tried our current twrp and it only flashes Magisk 17.1 to active slot, but Magisk 17.1 has the capability to both slots.

If we can somehow get a new version of twrp, we can then flash twrp to inactive slot, change slot to inactive slot, boot into twrp, flash Magisk (which would root both slots), change slot to other slot and reboot.

This way, we dont even need stock boot.img :highfive:
[Essential Phone Guides, News, & Discussion] ultrasuper:
I did exactly the same except I did NOT reboot into the OS after the OTA sideload-- I simply rebooted directly into the bootloader and:

$ fastboot flash boot_a patched_boot.img

(I always check the active boot slot first and explicitly name it in the command. I don't know if it's necessary but it "feels" safer)

Perfect outcome. Note that I don't (at the moment) have *any* type of screen lock at all.
[Essential Phone Guides, News, & Discussion] MoistPicklez:
I wonder if Essential was aware that their updated partitions would fudge up our touchscreen in TWRP. Seems like an odd thing to update all of a sudden, especially when it borks stuff over.

I know there is a work around, but I'm not sure the average user wants to flash a bunch of random partitions and then have to reflash the up-to-date ones.

Wut ya doin' Ssential?!
[Essential Phone Guides, News, & Discussion] ultrasuper:
I don't understand. Aren't there respondents to your poll who say touch in TWRP did work for them? Wasn't that the point of your poll?

I posted a thread here here where I was looking for a way to verify with certitude if this had been done on ones' phone (there is a fastboot variable which can be queried for "unlock" but I don't know about "critical').

Do you know of a way to check?

---------- Post added at 06:50 PM ---------- Previous post was at 06:43 PM ----------

So to flash stock you rebooted into factory recovery and used sideload to get the system OTA zip file installed right? and then rebooted to fastboot to flash the stock (non-patched) boot image? (No use of Magisk here to "prep" for any of this correct?)

Why do you have to extract the boot.img from the full zip? Can you not get that image instead from the link in the OP here? And then patch that boot image? That's what I did.
[Essential Phone Guides, News, & Discussion] bmg1001:
Yes, but it is all dependent on how people updated, so it will work for some, and not others. That post was primarily intended for those who experienced touch not working.

If you updated via the official fastboot images, TWRP will still work, but you wouldn't have touch in the system, unless you also flashed a kernel for August or earlier.

The most interesting result however, is the amount of people who say they updated via fastboot and experience touch not working in TWRP. Since the fastboot images were missing the updated firmware, there wouldn't be any mismatch to cause this issue, unless they updated to the new firmware afterwards or reflashed the update via OTA.

Honestly, due to all of these issues, the best way to root the September update right now may be to just patch the boot image with the Magisk Manager and fastboot flash that, without ever having to use TWRP. I never put that patched boot image method up in the OP because I found it to be very buggy and inconsistent in the past, and even now with 17.1, it seemed some people still had weird issues here and there.
[Essential Phone Guides, News, & Discussion] lynnux:
I've been using EX, flashing it through ex kernel manager at the end of the procedure I gave. However, the Sep patch has created an issue where the touch screen stops working in certain cases, like after flashing custom ROMs or kernels. Twice I flashed EX after all the above, and touch screen wouldn't work, so I started over. I've seen a few people say they were able to flash EX successfully, I'm going to wait until that gets sorted out.
[Essential Phone Guides, News, & Discussion] Lakino:
lynnux, thanks for the clarification. Please report back and post when you get EX Kernel working -- i.e. kernel works with touch -- for Sept update. I'm holding off as well. In fact, I'm holding off updating to Sept build PPR1.180905.036, full stop. I'm waiting to see if Essential itself releases a hot fix to address these touch issues.

---------- Post added at 05:09 PM ---------- Previous post was at 05:06 PM ----------

bmg1001, do these no-touch issues affect non-rooted users who just update via OTA? I guess my question is: are only rooted users being affected by this or all users who update to PPR1.180905.036 affected? Is Essential going to address this no-touch issue immediately?
[Essential Phone Guides, News, & Discussion] guliver365:
the OTG mouse worked for me got root, but no cursor in the aroma installer of Elmental EX Kernel!

Update

I flashed elemental EX directly from the app issue resolved
[Essential Phone Guides, News, & Discussion] ultrasuper:
I am trying to wrap my head around all of this but for right now, based on what you know about this, if I want to use TWRP now on stock/rooted 036 (to make nandroids for example), will touch work for me?

My path was:

New phone (7.1.1) -> immediately took OTA (on the phone) to 9.0 (091) -> followed OP to root w Magisk 16.7 -> updated Magisk to 17.1 (via direct thru app) -> Grabbed 036 boot image from OP and patched it w/Magisk and copied to computer -> Sideloaded OTA (from Essential's www) -> rebooted directly to bootloader and "fastboot flash" patched boot image -> Reboot to rooted 091, nothing else changed.

You predict touch working on TWRP or do I get and OTG to connect a mouse?
[Essential Phone Guides, News, & Discussion] bmg1001:
Since you updated via OTA, TWRP touch will not work.
[Essential Phone Guides, News, & Discussion] Lakino:
I don't think you can make normal nandroid backups with TWRP on the Essential as you can with most other phones, due to the A/B partitions.
[Essential Phone Guides, News, & Discussion] ultrasuper:
Yes you can. [MENTION=9317968]jacksummers[/MENTION] has been successful at creating/restoring nandroids. See this post.
[Essential Phone Guides, News, & Discussion] socali:
I've been using this method of patched boot for the past few updates on 2 phones with no issues at all. In Magisk Manager I simply did Uninstall - "Restore images" or fastboot flash the original boot image, then did OTA update and then used Magisk to patch the new boot image and fastboot flash.

As I mentioned in my prior post here, this was the first time I ran into issues where I had to uninstall Magisk Manager itself as well. I suspect this had to do with the v16 - v17 bootloop issue mentioned in Magisk release notes.

----

Regarding touch screen issue - interestingly, at some point I fastboot flashed a mismatched boot image (I believe september boot on august slot) and I did not have touch when the phone booted up. I was worried that I messed up something, but then realized it's the wrong boot version. I'm guessing TWRP is expecting the old drivers or firmware and it's incompatible with the update one.
[Essential Phone Guides, News, & Discussion] NLBeev:
I think your guess is right. TWRP did not work AFTER I installed the OTA.

About OTA.

I did the online OTA, but didn't work, because only the current stock boot.img was flashed. I needed to flash the current system.img too. To undo changes in the system partition (substratum.layers; Hosts for ad blocking; tweaks in build.prop)
[Essential Phone Guides, News, & Discussion] NLBeev:
With the September OTA I did some experiments.

The online OTA will only install when boot.img and system.img are exactly stock. No substratum, Hosts Adblock, build.prop tweaks etc.
[Essential Phone Guides, News, & Discussion] Nburnes:
Well yeah, that's how it works. It won't flash if a single bit is changed on either /system or /vendor.

Even mounting it rw will cause block verification to fail.
[Essential Phone Guides, News, & Discussion] :
If u dont get touch in twrp, just switch to the opposite slot. It is more critical of mismatches now.so one must flash twrp to both slots, then switch to the other. I am running a gsi with the stock kernel from update 036
[Essential Phone Guides, News, & Discussion] NLBeev:
That's nice You're running ahead.[emoji41]

I'll try it. The latest OTA and reroot were done without twrpp. I think it is useful for nandroid backups.
[Essential Phone Guides, News, & Discussion] drumrjoe:
What did I do now?!?! I tried reverting back to stock and now have no touchscreen ability! Can't press the "let's go" blue button on screen... https://photos.app.goo.gl/n9SDssc5cv6KrmK59

Getting into panic mode... Please help. TIA
[Essential Phone Guides, News, & Discussion] sash11:
What did you flash to get back to stock? Try rebooting into fastboot and flashing the latest image for fastboot.
[Essential Phone Guides, News, & Discussion] Ryuk359:
I had the same issue when I updated to the new ElementalX kernel. You have a kernel mismatch. Try flashing the back to stock stuff in fastboot.
[Essential Phone Guides, News, & Discussion] :
No just flash the ota zip adb sideload out of stock recovery
[Essential Phone Guides, News, & Discussion] NLBeev:
After reroot, I did a second OTA with adb sideload. The OTA switched slots and booted with stock (no root).

With fastboot I could switch to the previous slot. Also working incl. root.

Probably the sideload OTA doesn't check both slots.
[Essential Phone Guides, News, & Discussion] Maxr1998:
Are you trying to install a module? It looks like the module template is outdated and doesn't support the new Magisk version.
[Essential Phone Guides, News, & Discussion] HACK3DANDR0ID:
Anyone having a problem with booting into TWRP and it just freezes on the TWRP start screen, forced to power device off.

Factory Image : PPR1 Sept 2018 patch

*edit*

Nevermind, I see im not the only 1
[Essential Phone Guides, News, & Discussion] techlogik:
The touch screen issue has been covered at various locations.

If you want your OS touch screen to work, seems like you need to Side load the OTA. Not the Fastboot version. The fastboot version caused mine to not work in the OS. But, if you sideload the OTA version, TWRP touch won't work.

Since I have a USB OTG cable, I just plugged it into the phone, booted TWRP, and could flash Magisk no problems then. Most people are thinking that there is some firmware snafu from Essential on the full ADB fastboot build compared to the OTA that are hosing the touch screen. But who knows.

I recommend sideloading the OTA version, you can use the stock recovery, or if you haven't upgraded already, boot TWRP with full version 9 P from August, select sideload, let it sideload, reboot, your touch screen in the OS works. TWRP touch will require a USB OTG cable for now as a work around.

A tip for the USB OTG, fastboot flash boot twrp.img, then unplug and put your USB OTG in, then select Recovery and reboot into that. I personally use a wireless mouse/keyboard, works fine.

Good luck!
[Essential Phone Guides, News, & Discussion] sash11:
That's the whole idea of A/B slot design - OTA is installed into the inactive slot to prevent possible faulty flashing. If update is successful, active slot changes, if not things stay the way they were. I really don't understand why anybody would use twrp now since flashing patched boot.img seems faster and easier. I had to sideload the OTA because normal installation would fail for me no matter what I tried. Then flashing patched_boot.img gives me root back. It's that simple.
[Essential Phone Guides, News, & Discussion] techlogik:
When I build a patched boot.img file through Magisk, it makes the file 2MB is size...when it is normally 20MB. Flash it through fastboot, never boots. So that method doesn't work for me.

Also, flashing a custom kernel, then rooting is easy. The A/B partition sounds great in theory..but execution with rooting/modding/custom kernels etc..have created a nightmare with all sorts of crazy workarounds.

Coming from a Pixel 2 XL...it isn't any better over there either.

Normal installation fails because you had a modified system/boot image...unless you flash stock ones...the OTA won't install. Hence, needing the sideload OTA which is the only method that worked for me without messing up my touchscreen in the OS. The full fastboot image my screen would never work in the OS.

So, next best work around, USB OTG cable with wireless mouse. Now I have Elemental installed through TWRP (took awhile to use the up/down/power keys to get around Aroma to install that), then Magisk with the mouse. Back to normal now. But a PITA.
[Essential Phone Guides, News, & Discussion] philsner:
Sorry for asking but by reading the last couple of pages I really want to play safe.

I reckon its a bad idea to root / use custom kernel on a fresh install of an unlocked stock pie (sept. update)

Because of the talking about custom/patched boot images I'm afraid ending up with an expensive paperweight.
[Essential Phone Guides, News, & Discussion] NLBeev:
It's not that bad. There are risks, but these are more or less the same for all smartphones.

There is some hassle with Adb and Fastboot. But there's a great guide in the OP and there's a Back-to-stock thread.
[Essential Phone Guides, News, & Discussion] philsner:
I tried the guide of course but always end up with a non-responsive twrp. While doing the research I kind of lost track what the work around would be as everyone did something different. At least it feels like it, that's why I asked.
[Essential Phone Guides, News, & Discussion] NLBeev:
That's right. There is trial and error.

a. Flashing the back-to-stock images is a solution to get the online OTA.

b. The idea of [MENTION=9317968]jacksummers[/MENTION] to flash TWRP to both slots.

c. Sideload the OTA with Adb.

Important is to prepare things on a PC.

After reading your posts I think you should start with back-to-stock and sideload the latest OTA. Forget TWRP for the moment.
[Essential Phone Guides, News, & Discussion] philsner:
I tried it that way but always end up wondering how to install the Boot.img before flashing Magisk on the active Partition. TWRP on the active partition still is unresponsive when flashing onto both partitions

What do you mean with OTA? I already am on the Sept. 5th update.
[Essential Phone Guides, News, & Discussion] NLBeev:
That were my trial.errors....

When you need the latest patched_boot.img to get root. I can upload it,
[Essential Phone Guides, News, & Discussion] philsner:
So is it "patched" when I flash twrp on the inactive partition, flash boot.img from op, installing magisk and extracting it like in the guide in op? Am I supposed to use that extracted one on the active partition and I'm rooted after that?
[Essential Phone Guides, News, & Discussion] NLBeev:
When the patched_boot.img is flashed you're rooted.

I did it with fastboot directly to the active slot.

EDIT link to patched_boot.img

https://www.androidfilehost.com/?fid=1322778262903999715
[Essential Phone Guides, News, & Discussion] philsner:
Yes please!

Edit:

I used the patched boot from another thread and it worked perfectly fine. Finally now rooted with EX kernel. Thanks for the help!
[Essential Phone Guides, News, & Discussion] sash11:
del
[Essential Phone Guides, News, & Discussion] NLBeev:
OK - success with your rooted PH-1. See you at the next update.
[Essential Phone Guides, News, & Discussion] Ryuk359:
You're the man! Worked like a charm.
[Essential Phone Guides, News, & Discussion] NLBeev:
Maybe next is something for your guide

Since version 17 of Magisk it's possible to:

A. restore the stock boot image on the current slot;

B. install Magisk on the inactive slot;

C. let M boot from the updated slot, (instead of the OTA).

That makes it possible to use the OTA over radio. Update without a PC and root kept.

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
[Essential Phone Guides, News, & Discussion] techlogik:
Get a otg usb and then use a wireless mouse plugged into it.

Copy the new boot.img to the SD card along with Magisk and ex kernel

Fastboot flash twrp

Before selecting boot recovery, plug your USB otg in, then boot recovery. You will have a working mouse.

Install stock boot.img

Install Ex kernel. Mouse will not work in Aroma. But you can use the up/down volume keys and power button as the select/enter function. It takes some trial and error, but you can use the buttons to get the kernel installed. Be patient and start with the up volume button, then power button, that normally advanced. Also a trick again to select you understand the risk with buttons.

After kernel, use mouse to install magisk 17 1.

Reboot system.

Of course use the Ota and sideload it first if TWRP doesn't have touch to start this. All works well with above method and profit.
[Essential Phone Guides, News, & Discussion] bmg1001:
The OTG Mouse idea was mainly that touch magically works when it detects a mouse, but this works too!
[Essential Phone Guides, News, & Discussion] bschmidy10:
How do I manually switch slots? Or choose which slot to boot?
[Essential Phone Guides, News, & Discussion] Thebear j koss:
Fastboot getvar current-slot

Fastboot set_active

If 1st command gives an a

After set_active put b or other

Check again Fastboot getvar current-slot after setting active the new slot.
[Essential Phone Guides, News, & Discussion] NLBeev:
Magisk switches to the opposite slot as described in my previous post.

For manually switching slots a PC is needed with working 'fastboot'. Boot phone to fastboot/bootloader mode. and use "fastboot --set-active=a" or "fastboot --set-active=b".
[Essential Phone Guides, News, & Discussion] DoR3M3:
Don't say We and speak for the majority, everyone's needs are different and TWRP is nice tool for whatever the need may be for someone.

There are a lot of good reasons to have TWRP.
[Essential Phone Guides, News, & Discussion] NLBeev:
Yes. We keep in 'touch' [emoji41]
[Essential Phone Guides, News, & Discussion] sash11:
It was a though and not a call to action. And don't tell me what to do) TWRP is not as critical as it used to be and is not required in order to root the phone. That said, there are other applications for it indeed.
[Essential Phone Guides, News, & Discussion] DoR3M3:
No one is telling anyone what to do, other then your usage of the word WE, as the authority on the subject matter, and again you bring it up now with "Critical"...

Please do tell what your defintion of critical is that you are speaking about?

TWRP is not just about rooting, it's used to perform many functions, I don't even think you understand... :eek:
[Essential Phone Guides, News, & Discussion] Hero2457:
Guys, I've run into a problem after rooting my phone on the September build. The touchscreen isn't working on boot up; I rooted via patching the boot image with magisk manager and using adb commands. Can anyone help me get my phone's screen to work?
[Essential Phone Guides, News, & Discussion] Thebear j koss:
Try the patched boot IMG from reddit. Link posed somewhere in here...

EDIT--https://xdaforums.com/essential-phone/how-to/september-update-t3838394/post77531677
[Essential Phone Guides, News, & Discussion] Hero2457:
EDIT--I should've read that thread before asking! Thanks for the help, I thought I had messed my phone up somehow
[Essential Phone Guides, News, & Discussion] sash11:
I think the majority of us who use twrp use it in order to gain root. So it was critical in that sense. But not anymore. Don't assume what I do or do not understand. That is not your area of expertise) I never claimed that twrp is just about rooting. On the contrary I aknowledged that there are other uses for it. Don't put words in my mouse. Lighten up and take it easy.
[Essential Phone Guides, News, & Discussion] DoR3M3:
Actually I'm very chill and couldn't be happier, I was just typing, with no hidden agenda, and certainly no words in anyone's mouth, and I'm as light as it comes, so take it easy too... ;)

The truth is, I was just trying to point out, that you were throwing words out there without elaborating...

I can't resist, you keep doing it again; I think the majority of us who use twrp... Don't think man... LOL Actually a lot of people use it for more then just rooting... Ok enough off topic...

It's all good!

PEACE :)

P.S. [MENTION=4278722]sash11[/MENTION] I edited the post over...
[Essential Phone Guides, News, & Discussion] sash11:
Cool. Now I did an assumption in my previous post that the majority uses twrp for the purpose of rooting. If that is so, than my usage of the pronoun We is fully justified) Would really be interesting to see a poll done on this.
[Essential Phone Guides, News, & Discussion] :
I use twrp only for backups.
[Essential Phone Guides, News, & Discussion] NLBeev:
For backup I use now the ADBsync scripts of osm0sis. To backup and later sync the SD card.

Updated the ADB stuff and added some commands to make it work with Wifi. I've also added the adb backup commands for app and system data.

EDIT

https://www.androidfilehost.com/?w=files&flid=282113

Using the app ADB WiFi of MetaCtrl
[Essential Phone Guides, News, & Discussion] :
Nice!
[Essential Phone Guides, News, & Discussion] ceelos218:
I'm interested in knowing how to backup ?