yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] Mike02z:
Excellent. I guess I should update to 14.4. 14.3 seems to be working fine for me.
[Essential Phone Guides, News, & Discussion] aer0zer0:
You can also flash some of the 14.5 builds too, they work as well
[Essential Phone Guides, News, & Discussion] superior888:
Can anyone with root on stock rom install Kernel Auditor from play store and see if we can adjust the kernel speed or set another gouvernor? Wanna see if we can get this little less laggy. In Lineage the smoothness is insane good.
[Essential Phone Guides, News, & Discussion] JoshuaUB78:
I'm actually running stuck rooted, using Kernel Auditor. You can adjust cpu speeds, the number of cores available for hot plugging. Not many governor options other than standard Android. Have mine on Interactive with noop for I/O.

Anyway, since I haven't run Lineage I don't have a comparison.

---------- Post added at 03:43 PM ---------- Previous post was at 03:36 PM ----------

I haven't had any negative battery issue; rooted stock latest November update.
[Essential Phone Guides, News, & Discussion] scottfreeze:
Not strictly root-related, but there doesn't seem to be a dedicated TWRP thread.

Is there a working, Oreo-compatible build of TWRP floating around? I installed the Oreo beta, but now I would like to restore a TWRP backup I made on NMJ32F. None of the TWRP builds I can find can see the internal storage, nor do they even prompt for the encryption pin.
[Essential Phone Guides, News, & Discussion] nrage23:
There is no TWRP build that supports the Oreo firmware. You would have to flash back to a Nougat firmware then restore your backup.
[Essential Phone Guides, News, & Discussion] nibblur:
thanks. I was able to get root on oreo.
[Essential Phone Guides, News, & Discussion] Mike02z:
Not really accurate. The latest TWRP can be booted with Oreo, it's just touch does not work. You can still sideload with TWRP. That is how I got root in Oreo.
[Essential Phone Guides, News, & Discussion] IC_Blood:
Were you guys on Oreo?
[Essential Phone Guides, News, & Discussion] treIII:
Anybody having problems with phone waking or any apps locking up? Since rooting with magisk 14.3 I've had some of these issues which didn't exist before root. Also this was my root procedure. I flashed magisk Oreo boot.img with fastboot. Then installed magisk manager. I have root just some problems as described above. Phone app seems to lock up often
[Essential Phone Guides, News, & Discussion] treIII:
What can I do to uninstall magisk? My phone is having a lot of problems. Will a factory reset remove magisk?
[Essential Phone Guides, News, & Discussion] kirschdog1:
Is there instructions on how to do this anywhere?
[Essential Phone Guides, News, & Discussion] mrcooter:
Negative. Uninstall from within the app or just start fresh with factory images if you need to. I've had root on Nougat and now Oreo without any issues.
[Essential Phone Guides, News, & Discussion] treIII:
I just removed it from the magisk manager and all seems fine now. I think that what I did wrong was try to install Xposed on Oreo and that may have caused the problem. If my phone keeps performing normally I'll know. I'll report back. Thanks
[Essential Phone Guides, News, & Discussion] Warmice23:
I update to Oreo. This no root yet is there?
[Essential Phone Guides, News, & Discussion] kboya:
Flash Magisk 16 and update internally to 17 (which is working perfectly for me)
[Essential Phone Guides, News, & Discussion] najoor:
Safetynet check returns invalid response in magisk and I can't make Google pay work. If that normal?

I'm on stock Android pie:

Magisk: 16.0

Magisk manager: 5.8.3

Google pay: 2.27.209520801
[Essential Phone Guides, News, & Discussion] sash11:
Just patch stock boot.img with Magisk application and flash patched_boot.img from fastboot. You should get your root back)
[Essential Phone Guides, News, & Discussion] Hero2457:
Patching the boot image via the application is giving me an error.
[Essential Phone Guides, News, & Discussion] kboya:
It works for me. Have you enabled Magisk hide?
[Essential Phone Guides, News, & Discussion] droidian5:
Magisx manager 5.9.1 is out along with Magisx 17.1 and is working great!
[Essential Phone Guides, News, & Discussion] Darkside1984:
Just flash by TWRP in this order: magisk uninstaller, stock boot and magisk 16.0 zip.

Now I'm fine with 16.0 until they fix new version...
[Essential Phone Guides, News, & Discussion] sash11:
What's wrong with 17.1 ?
[Essential Phone Guides, News, & Discussion] droidian5:
17.1 fixed the issues with bootloop when upgrading from 16!
[Essential Phone Guides, News, & Discussion] nababatigyza:
Thanks a lot, I followed your steps, but flashed Magisk 17.1 . Worked like a charm :good:
[Essential Phone Guides, News, & Discussion] najoor:
Thanks for your response. I unrooted, flashed elementalX kernel, and re-rooted with magisk 17.1 and magisk manager 5.9.1 and now the safetynet check passes and Google pay works. I didn't have to enable any hide option or anything like that. If I have to guess, it was rerooting with 17.1 that fixed it.
[Essential Phone Guides, News, & Discussion] ultrasuper:
So there's no way to update Magisk to 17.1 using **only** the phone; We have to use a computer, correct?
[Essential Phone Guides, News, & Discussion] resaik:
Hi

Where i can find patched boot on my phone please?

And does i have to put him on adb fastboot on my computer too?

Thanks
[Essential Phone Guides, News, & Discussion] sash11:
If you are rooted already, update using direct (recommended) method through Magisk app. If you are trying to root a stock Android, no way around a PC.

---------- Post added at 11:25 PM ---------- Previous post was at 11:21 PM ----------

What are you trying to do with patched boot image? You can patch a stock boot.img to get a patched_boot.img. If you are trying to root your phone, than yes, patched_boot.img needs to be in the same folder with your fastboot executable. Or you have to specify full path to it while flashing with fastboot.
[Essential Phone Guides, News, & Discussion] resaik:
Yes i want to root .i did it but i had to factory reset .

but now when i install magisk on twrp (i tried with 16.0 16.6 16.7 17 17.1) when i reboot magisk is not installed on my phone .!

I past many hours to try but i don t find how can i do .for this i would try this method with patched boot.img
[Essential Phone Guides, News, & Discussion] lynnux:
To install using patched boot.img method:

Download and install latest MagiskManager apk

Give storage permission to MM app, this is important. It may not ask you for it.

Open MM app, hit install

It will ask you to choose method, choose patch boot image method

It will tell you where patched_boot.img is placed in your file system, probably downloads

Connect to computer, transfer patched_boot.img to computer

Fastboot flash (in bootloader) patched_boot.img to phone, reboot

This info is available elsewhere, the more places the better.
[Essential Phone Guides, News, & Discussion] Darkside1984:
Yeah! :laugh:
[Essential Phone Guides, News, & Discussion] resaik:
Instala

Installation failed i use mm 5.9.1 apk ?

I don t know what is wrong.i really need root .

I had factory reset again is the same .
[Essential Phone Guides, News, & Discussion] lynnux:
At what step is it failing? Is there an error message?
[Essential Phone Guides, News, & Discussion] resaik:
Downloading zip

100%

Extracting files

! Installation failed
[Essential Phone Guides, News, & Discussion] lynnux:
Is this in MM app? Did you give storage permissions to app?
[Essential Phone Guides, News, & Discussion] resaik:
Yes of course.
[Essential Phone Guides, News, & Discussion] lynnux:
I'm stumped (don't have any idea what's going wrong).
[Essential Phone Guides, News, & Discussion] resaik:
Thanks to help .i will reflash stoxk firmware something is going wrong i have to fix it !
[Essential Phone Guides, News, & Discussion] sash11:
If you did not see Magisk application after you rooted the phone it does not mean phone is not rooted) Just install Magisk.apk latest version 5.9.1 manually and check if you have root.
[Essential Phone Guides, News, & Discussion] NaterTots:
If you showed the steps you are taking to get root it would help others that are trying to help trouble shoot this for you.
[Essential Phone Guides, News, & Discussion] NLBeev:
[MENTION=4229539]resaik[/MENTION]

When your PH-1 is running stock and a pc with working adb/fastboot is available....

Try the guide in the OP. ( Flashing TWRP first )
[Essential Phone Guides, News, & Discussion] resaik:
Yes adb fastboot work fine
[Essential Phone Guides, News, & Discussion] Darkside1984:
I've installed the Ainur Sauron Magisk module and now I'm in bootloop. I need to unistall it by TWRP but it's encrypted. Any way to solve it without doing factory reset? Thanks!
[Essential Phone Guides, News, & Discussion] aer0zer0:
Flash the stock boot.img in fastboot

Boot back into OS and disable fingerprints and stuff

flash twrp in fastboot

The rest is cut and dry, just delete magisk.img in adb folder, then reroot in twrp
[Essential Phone Guides, News, & Discussion] mobileman88:
There's a new twrp which supports P. Hopefully one which works for PH1 soon. https://plus.google.com/+DeesTroy/posts/TE259QesfyT
[Essential Phone Guides, News, & Discussion] resaik:
I don t know why but i had a problem with the rom.because i reinstall a pie image to re install

The phone like at the begining.and it was very easy to root it with the patched boot solution with magisk.

Anywere thanks for peoples who try to help me .

Ang long life to all essential phone and essential phone users :laugh:
[Essential Phone Guides, News, & Discussion] NLBeev:
Magisk 17.1 has a great option.

'Install to inactive Slot'

It seems to me that after an OTA we don't need a PC to reroot. [MENTION=4550123]bmg1001[/MENTION] do you agree?
[Essential Phone Guides, News, & Discussion] RandomPooka:
This is correct. It's how Magisk Manager used to work, so it's nice to see that feature make a return to the playing field.
[Essential Phone Guides, News, & Discussion] bmg1001:
Wouldn't the OTA not apply since you were rooted?
[Essential Phone Guides, News, & Discussion] Thebear j koss:
Installs to other slot.

Sent from my Essential Phone using Thebear Blue XDA Labs
[Essential Phone Guides, News, & Discussion] RandomPooka:
Correct, in regards to stock. But, it works for custom ROM OTA upgrades like AOSiP. I hear that LOS has a seamless updater setup now, too.
[Essential Phone Guides, News, & Discussion] NLBeev:
Active slot = rooted, other slot = stock.

I wonder when the OTA install script checks the 'active slot' for root?

Before or after copying the images to the non-rooted slot.
[Essential Phone Guides, News, & Discussion] Darkbandit14:
Delete, it fixed itself somehow
[Essential Phone Guides, News, & Discussion] jionny:
Sorry for the noob question but this is my first time using Magisk I am currently on 16.7 and got a update notification for 17.1 what are the steps to update this as I see a few options to install
[Essential Phone Guides, News, & Discussion] NLBeev:
The Magisk manager may download and flash the new version
[Essential Phone Guides, News, & Discussion] jionny:
so just click flash? nothing else?
[Essential Phone Guides, News, & Discussion] jionny:
Nevermind figured it out
[Essential Phone Guides, News, & Discussion] Darkside1984:
Two silly simple questions: Is it normal that TWRP (mata11) to appear cutted on the left of the screen? Any short-term possibility of installing custom recovery on our Essential natively?
[Essential Phone Guides, News, & Discussion] stinger4321:
Yep. It's been like that
[Essential Phone Guides, News, & Discussion] DoR3M3:
The TWRP Team from what I've been told, now owns an Essential, so we should see improvements soon... ;)

This isn't all that's bad, have you tried typing in the keyboard, like for renaming a backup... LOL

It's in sad shape at the moment, oh how I hope it will be fixed real soon.
[Essential Phone Guides, News, & Discussion] sash11:
We really do not need recovery that much. Rooting can be done without it now. Maybe backup is the only thing that is of benefit.
[Essential Phone Guides, News, & Discussion] bschmidy10:
Anyone update yet? Best steps to update and keep magisk root?
[Essential Phone Guides, News, & Discussion] gk1984:
It's not that hard. Download the Ota from Essential developer site, download the boot image from OP in this thread. Let Magisk patch the boot image and copy it to PC. Adb sideload the Ota, then boot the the bootloader and fastboot flash the patched boot image. You're done
[Essential Phone Guides, News, & Discussion] NLBeev:
I tried the system update. Didn't work with root, but I noticed that the security patches are only 81Mb.

EDIT

Seems to me 81Mb concerns a script.

The online OTA takes about 15 minutes to download and install.
[Essential Phone Guides, News, & Discussion] NaterTots:
So after I updated I tried to reroot by way of TWRP as I had been doing and with this lastest update I didn't have any touch screen ability while in TWRP.

And when I go to root with magisk manager, I get an error when it tries to patch the boot img. I'm using the lastest magisk apk.

Really weird
[Essential Phone Guides, News, & Discussion] LRiley:
same here no touch twrp
[Essential Phone Guides, News, & Discussion] robertbarber:
Its the same for me as well. Twrp seems to freeze after it loads. I do have access to adb commands so I can still flash the stock boot image after rebooting to bootloader so it can boot but not sure whats causing twrp to freeze
[Essential Phone Guides, News, & Discussion] LRiley:
I got magisk by having the stock boot image in storage. go to magisk and install it. then select patch boot image file and pick the stock boot image. it will create a patched boot image that you can take off the phone and put into your adb folder. Then fastboot flash the patched stock image to boot the restart. you will have root access
[Essential Phone Guides, News, & Discussion] robertbarber:
Just did that and have root back. Thanks for the advice
[Essential Phone Guides, News, & Discussion] NaterTots:
I tried that and I keep getting this.

Edit: I think I have a bad download of the boot.img

Nope, still happens with a new download.
[Essential Phone Guides, News, & Discussion] mobileman88:
I had the same issue too on one of the ph1s I have. Only way is to flash in twrp
[Essential Phone Guides, News, & Discussion] Lakino:
jionny, so how did you do it? Just like you originally asked, what are the exact steps to update?

What exactly did you do? I'm in the same boat and would appreciate a step by step instructions to update.

Thanks. :good:
[Essential Phone Guides, News, & Discussion] jionny:
just hit install the menu says recommended that is what you click
[Essential Phone Guides, News, & Discussion] LRiley:
Do you have magisk 17.1(newest)
[Essential Phone Guides, News, & Discussion] lynnux:
Last week I had a similar problem patching the boot image, kept getting the same message. I ended up getting the boot image from a different place (I believe from the fastboot download from Essential's website, can't remember for sure), and that worked. I'm still not sure if that's what finally solved it, or if was using a different port on computer, etc.
[Essential Phone Guides, News, & Discussion] mobileman88:
I have 3 PH1s.

2 of them let me patch boot images in MagiskManager or do direct flash. For the 3rd one, for the life of me, I could never get it to work. Always have to do the following to root :

- Diable PIN/pattern/fingerprint

- Boot to bootloader

- Flash twrp

- Boot to twrp

- Flash stock boot

- Flash magisk

- reoboot

Doing full return to stock still have the same issue for the 3rd. Go figure
[Essential Phone Guides, News, & Discussion] GospelNerd:
This is the behavior I was seeing as well. I clicked to download the Magisk zip instead so I could flash it in TWRP. But, when I did that, the app asked for file system permissions which I granted. Then, I just tried the Patch boot image option again, and this time it worked:victory:... duh.:cyclops: Although I didn't remember having to do that before.
[Essential Phone Guides, News, & Discussion] oceansoul:
latest TWRP does not have touch screen support on mine, but ota mouse solved that
[Essential Phone Guides, News, & Discussion] lynnux:
This triggered my memory of last week, and giving the Magisk Manager app storage permissions is indeed what got me past the 'installation failed' message.
[Essential Phone Guides, News, & Discussion] ultrasuper:
You mean OTG mouse..?
[Essential Phone Guides, News, & Discussion] socali:
I finally got Essential PH-1 with the September update and Magisk v17.1 to boot up!

After multiple trial and error cycles, I think what did the trick was uninstalling magisk manager, then I fastboot flash the magisk patched boot and then phone booted up.

I don't use TWRP, so here's what worked for me:

1) Magisk manager - create a patched boot image for the September boot

2) Magisk manager - do Uninstall -> Complete uninstall (if you already do not have magisk, then uninstall the manager app)

3) Install September OTA update (including a full boot after update)

4) Fastboot flash the patched boot

5) Install magisk manager again
[Essential Phone Guides, News, & Discussion] bmg1001:
Added a quick poll to the OP asking about TWRP touch and the update. The data should hopefully give us some insight as to why touch in TWRP works for some, and not for others.

EDIT: My theory is that the OTA updated some firmware stuff involving touch, while the fastboot images didn't. If you updated via fastboot, chances are you're touch wouldn't work in the system, but would work in TWRP. Likewise, if you updated via OTA, touch wouldn't work in TWRP, but would work in the system.
[Essential Phone Guides, News, & Discussion] ultrasuper:
Just to be clear, on a Stock rooted PIE (August 091), it's NOT possible to update to the Sep (036) security update *without* using a computer as the intermediary (via a sideload or whatever)...

This CANNOT be done using ONLY the phone, correct?
[Essential Phone Guides, News, & Discussion] NLBeev:
Because fastboot is needed.
[Essential Phone Guides, News, & Discussion] ultrasuper:
So no TWRP at all using this method. Correct?

*Answering my own question.

Followed [MENTION=3443130]gk1984[/MENTION] precisely. Worked perfectly. No TWRP utilized at all.
[Essential Phone Guides, News, & Discussion] NaterTots:
That fixed it for me. Thanks
[Essential Phone Guides, News, & Discussion] alexbuga:
Thanks. Fixed my issue too. No twrp yay!

I actually managed to run twrp from adb shell because I had no touch support. but there's no command for flashing the boot.img in that mode.

So this really helped me a lot.
[Essential Phone Guides, News, & Discussion] spotmark:
[MENTION=4550123]bmg1001[/MENTION] No option for me in the poll. Updated via TWRP. TWRP works.
[Essential Phone Guides, News, & Discussion] NLBeev:
September update online OTA

I've also tried a few things, to get the online OTA working.

Reflashing the current stockboot.img works, but the online OTA failed. Probably because I made changes to the system. (edit build.prop and installed layers)

Therefore I reflahsed the current boot en system images with fastboot and to both slots. After that the online OTA installed in about 15 minutes.

Reroot

I had to extract the new version of the boot.img (4.4.152) form the factory image of September, because rooting with the previous patched kernels failed.

Transferred the new boot.img to my PH-1 with Dropbox.

With magisk manager I created a new patched_boot.img and tranferred it to the PC .

I did not uninstall the magisk manager just to see what should happen.

Reroot worked with fastboot flash boot patched_boot.img
[Essential Phone Guides, News, & Discussion] sash11:
I've had to sideload OTA in order to get latest 036 build.

First I tried to just flash stock boot.img of 091 build to get back to stock so to speak without removing Magisk. OTA failed to apply. Then I flashed patched_boot.img back to regain root, uninstalled one module and removed Magisk from application. Phone rebooted and went into stock recovery with a robot, exclamation mark and No command message. I rebooted the phone and tried to apply the update. It failed again. My guess is something was messed up in the other slot that OTA was trying to install into.

I rebooted phone into stock recovery and sideloaded the OTA image. It applied to the other slot. So active slot changed from _b to _a for me. After sideloading OTA I booted into bootloader and applied previously patched boot.img for 036 build. Phone booted but I did not have root and Magisk application was not present. I installed Magisk.apk but still no root. So I rebooted and all went to normal. Root was present. Not sure why phone was not recognizing root after the first boot. My guess is because after the first boot Android does some finishing touches. So probably the way to do it is reboot into the OS after sideloading the OTA and let it finish the update. Then reboot into fastboot and flash patched_boot.img. While doing all these things I did not disable any protection. I have pin and finger print.
[Essential Phone Guides, News, & Discussion] NLBeev:
Yes. I got the online OTA working after flashing the current (091) boot and system images to both slots. For reroot we need to create a new patched_boot.img.

All apps including magisk manager and modules were kept. Except layers.
[Essential Phone Guides, News, & Discussion] techlogik:
patched_boot.img is 2MB is size after I try patching it. It is 20MB to start. Then, after flashing it...won't boot, bootloops back to bootloader. What a cluster. Seems like I'm going to try to sideload back to August Android P to get everything working, it is a complete mess, and now TWRP and touch screen doesn't work anymore.

Another issue I get is when I do a fastboot flash boot boot.img it can't flash and doesn't recognize the partition. I have to use fastboot flash boot_b boot.img and specify the parition. Tried everything, it won't reboot and as I said, my patched_boot.img is 2MB is size compared to the 20MB it normally is when I do the patch method through Magisk manager, transfer it over to the comptuer, and try the above.
[Essential Phone Guides, News, & Discussion] NLBeev:
You could start with the back-to-stock method.....see https://xdaforums.com/showthread.php?t=3701681
[Essential Phone Guides, News, & Discussion] techlogik:
Well, I happened to have a USB OTG cable...plugged my wireless mouse/keyboard adapter into it, then was able to Root the phone via TWRP with a mouse.

Couldn't get the kernel installed though, it doesn't understand how to move around in TWRP with the mouse using the AROMA installer. Only could exit the installer and just run the root.

Need an unattended Elemental installer method and no Aroma, just stock speeds and leave it at that like most to work around. Maybe try to flash via flashfire or Rash flash then reboot TWRP, and root again?
[Essential Phone Guides, News, & Discussion] NLBeev:
See the poll in the OP. Many have problems with twrp because there is no touch.

Untill the touch issue is solved, you better use alternative methods.
[Essential Phone Guides, News, & Discussion] jionny:
yes I am using 17.1
[Essential Phone Guides, News, & Discussion] ultrasuper:
My understanding is that when stock/rooted, one cannot take the OTA updates in the phone we get notifications about (attempting to do so will fail to update). I updated my stock/rooted 091 to 036 via sideload (steps on Essntial's website for developers) .

I'm confused about what the steps are one would utilize to update involving TWRP at all.

The poll up top has two paths:

Update via OTA

Update via Fastboot

Can someone post the steps to update an already rooted/stock install via these two methods (involving TWRP), which wouldn't result in the loss of any installed apps, Magisk or modules, and root. It is unclear to me.
[Essential Phone Guides, News, & Discussion] NLBeev:
Post #1856; how I got the online OTA working and rerooted my PH-1.