yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] Surge1223:
What's the patch process consist of? What is the patch doing that allows for these images to utilize the touch drivers? Is there a post that explains, how and why the patches were implemented anywhere?
[Essential Phone Guides, News, & Discussion] vincentallen2:
I'm on Q beta 6 right now. If I were to extract the boot.img from the beta factory files, patch it with magisk, and then flash the patched boot.img to my PH-1 through fastboot, would the data on my PH-1 reset or would I keep all the current data on the phone?

I'm attempting to root without flashing TWRP so I won't have to deal with the extra steps when I want to accept an OTA update.
[Essential Phone Guides, News, & Discussion] rignfool:
You won't lose data...

But... If you do it this way... You will not be able to easily revert to the stock boot.img within the manager... And therefore will need either your PC or something like Franco Kernel Manager to flash the stock boot image to be able to take the updates ...

Either way... You will have to flash the stock kernel to take the update
[Essential Phone Guides, News, & Discussion] vincentallen2:
Thank you for the reply, I ended up patching and flashing a beta 6 boot.img last night. For some reason I had in my head that the boot.img was the same as the system.img, and vice-versa haha.

My only complaint so far is that now the wallpaper resets temporarily after reboots.

But back to your suggestion, flashing the kernel the way that I did will still allow OTA updates, correct? I think it's a lot faster and easier to allow the phone to take the OTA and just download and flash the kernel later since it's a smaller file
[Essential Phone Guides, News, & Discussion] rignfool:
It will only allow OTA updates if you revert to the actual stock kernel... Not the magisk patched one...

And because of the way you installed it... You cannot use the uninstall images button in magisk manager... You will have to manually reflash the stock image...

On another note ...

I will not take the OTA using the updater for stock... No fall back if it fails
[Essential Phone Guides, News, & Discussion] ktmom:
[MENTION=1884668]vincentallen2[/MENTION]

Are you adverse to just flash the OTA in TWRP once a month adding the TWRP zip to the queue, then reboot to TWRP and reflash Magisk? It takes me little time to update each month.
[Essential Phone Guides, News, & Discussion] avd:
If I flash Magisk on the latest Q, it either keeps booting into twrp or hangs on the bootanimation. Anyone know where to find pre flagged not images?
[Essential Phone Guides, News, & Discussion] ktmom:
I don't know why you quoted that post.

Going to Q, with SAR (system as root), you'll have to use the Magisk Canary channel. Read the Magisk help thread for the details.
[Essential Phone Guides, News, & Discussion] avd:
I don't know why I quoted that either. I was trying with Ianmcd version.

Thanks for the hint.
[Essential Phone Guides, News, & Discussion] n2locarz:
Hey guys, haven't been keeping up in awhile. Great to see the user base still going strong. Have a new PH-1 that I'm moving to Q. Had to downgrade and flash the modem since it was a Sprint version. Updated to Q 122. This root guide doesn't seem to have the latest updates. Is there a stock TWRP Magisk Boot image available? I found Daze's google share with a Q122 boot images. He has Qroot_twrp.img. Found the link a few pages back:

https://drive.google.com/drive/folders/1-NaLsOVz6eSmtTU5elTAy1h6vGOwEWyk

Anyone know if it works? Same procedure as before? Also should I apply Magisk 19.3 an older version? Thanks guys
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
Was anyone here able to properly install TWRP on Android 10 and then flash Magisk 19.4 for root?
[Essential Phone Guides, News, & Discussion] avd:
TWRP: no problem. Magisk, all different flavors, no joy.
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
Surprised. Pixel 3 XL running Android 10 has problems with TWRP, but can be easily rooted with Magisk. Essential isn't much different, since it runs the stock firmware, and also doesn't have complications like those in Samsung Galaxy.

So, everybody here are already tried Magisk 19.3 stable, Magisk 19.4 beta, and canary builds too?
[Essential Phone Guides, News, & Discussion] n2locarz:
I'm running 10 and haven't successfully rooted yet. Others have but didn't say which version
[Essential Phone Guides, News, & Discussion] ktmom:
Magisk 19.4+ should work. You should patch the boot.img with the most recent Magisk Manager, then Fastboot flash the patched boot.img to the current slot. When you patch the boot.img, make sure, in MM -> advanced -> preserve forced encryption and preserve dm-verity are checked.
[Essential Phone Guides, News, & Discussion] kt-Froggy:
Magisk Canary builds work just fine. I am not using TWRP, but patching the boot image with Magisk works with no problems. Safety net check passes, GPay works with root.
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
What about TWRP? Does it work fine on Android 10 with decryption?
[Essential Phone Guides, News, & Discussion] kt-Froggy:
No idea, sorry. I am not using TWRP.
[Essential Phone Guides, News, & Discussion] freshlysqueezed:
I'm using twrp on Android 10 with decryption.
[Essential Phone Guides, News, & Discussion] hssxda:
Do you have any issue with setting PIN or Fingerprint? My stock works fine and then i successfully root with Magisk Canary builds and I lose the ability to set a PIN or fingerprint. Only option is "None" or Swipe" for screen lock.
[Essential Phone Guides, News, & Discussion] rignfool:
TWRP doesn't deal with encryption on 10
[Essential Phone Guides, News, & Discussion] samep:
Android 10 may be confusing fingerprint use? I'm running Android 10, latest 148 patch with Magisk 19.4 beta (no TWRP) but don't see fingerprint as an option.

But fingerprint does unlock the screen.

My fingerprint came over from Magisk 19.3 OTA patching from Pie to Android 10. Magisk 19.3 gave me some odd problems with eventual inability to launch apps at some point that was more frequent with Nova launcher compared to stock launcher. I also noticed I couldn't unzip modules to install with MM coming out of deep sleep.

After the patch with Magisk 19.4 beta, I still had the deep sleep unzip issue but installing the FDE.AI module made that go away, it seems. I have had a couple of SystemUI reboots with Magisk 19.4 beta though. One of those was right after going back to Nova launcher. Those issues were early. I think it's more stable now.

I've mentioned these issues in one of those early Android 10 threads for Essential. I'm also giving the detailed account with Magisk for the benefit of those asking or commenting lack of such methods or experience. I did not try Canary though. https://xdaforums.com/showthread.php?p=80373583
[Essential Phone Guides, News, & Discussion] kt-Froggy:
My options for the unlock are None, Swipe, Pattern, PIN, and Password (PIN is what I am using). Fingerprint is not listed as an option for the screen unlock, but I believe it's not supposed to be there by design - it's in a separate "Fingerprint" section under Security settings. FP works perfectly for the unlock.

My security setup has not been changed from Pie - I did the upgrade to 10 with the PIN and FP in place.
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
How?

[MENTION=3290808]rignfool[/MENTION] Someone else mentions otherwise.
[Essential Phone Guides, News, & Discussion] rignfool:
TWRP will work fine for F2FS... Or what I would assume is "decryption"

If you attempt to use TWRP on ext4 it will not decrypt and say the password is wrong
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
Oh. Got it!

So, for the time being, can we simply install TWRP and then use it to sideload and install the Magisk Canary version via ADB?
[Essential Phone Guides, News, & Discussion] rignfool:
I don't know...

I turn off any lockscreen security before flashing and booting TWRP when I'm on ext4...

And when on custom just switch to F2FS
[Essential Phone Guides, News, & Discussion] Bobbaloo:
Did you try to do a fingerprint search in settings? I've had that before on pie, occasionally. The option wouldn't be in the list but appeared in a search.
[Essential Phone Guides, News, & Discussion] samep:
Search finds it. Yes. But it's actually found in security, just below unlock. Same place (search or opening security).

I think that's just the way it is? Fingerprint won't unlock after a reboot. Users are forced to their default method. Mine is pattern. Fingerprint unlock works afterwards for non boot unlocks.
[Essential Phone Guides, News, & Discussion] kt-Froggy:
Yes, I responded about the FP unlock just a few posts above. It's a separate setting under Security. FP never worked for the initial unlock after boot, including the older Android versions. First unlock after boot must use the configured unlock method. It's also true for other devices I know - for example, my S7 on Oreo is doing the same.
[Essential Phone Guides, News, & Discussion] rignfool:
You do not want biometrics being part of your encryption key
[Essential Phone Guides, News, & Discussion] samep:
Makes sense. Thanks guys.
[Essential Phone Guides, News, & Discussion] Bobbaloo:
Wow. Essential? Other versions of Android? I never had that problem. I had others, yes but not that. Stock or rom?
[Essential Phone Guides, News, & Discussion] samep:
I haven't been paying attention but it makes sense as others answered my question. See screenshot; FP is below unlock as a separate security option. Works as I described earlier.

It's stock Android 10, Essential PH-1, October security patch with Magisk 19.4 beta as root. As I've said before, I OTA updated to Android 10 using the Magisk OTA method. It was Magisk 19.3 stable at the time but I had issues. Most are resolved with Magisk 19.4 beta. I used Magisk 19.4 beta to OTA update the October security patch (restored stock image, OTA update and patched per Magisk OTA method before reboot).

The scripts in the FDE.AI module installed with MM seems to be helping with other issues I was having with battery drain and SystemUI reboots. Android 10 seems to be stable with Magisk.
[Essential Phone Guides, News, & Discussion] kt-Froggy:
If you are talking about fingerprint not unlocking after reboot, every device with the FP sensor that I have seen works like that, on all stock versions of Android (can't say about custom ROMs, but pretty sure it's the same).
[Essential Phone Guides, News, & Discussion] CamoGeko:
I agree to some extent... stable maybe yes but far from being good to battery life. Also some compatibility for certain themes is still in infancy stages.

I know that, to many people (including me) making Android look like whatever they want is more important than being on the latest version number. Especially since there's barely any positive improvements with Android 10.
[Essential Phone Guides, News, & Discussion] samep:
I agree. I posted not long ago in one of these threads that battery life hasn't been the same for me since early Nougat (before Google services started draining the battery). Hasn't been the same since.

I was using a Google play services limiting script module in Magisk with little difference. But just switched to another module: FDE.AI This module also updated last night (the reason for the reboot in the battery usage screenshot). The new module seems to work better than the older one I used so long. Got rid of the other module. See screenshot; this is the best I've seen since Nougat that I can recall. FDE.AI is a script optimizer so only one is recommended. This optimizer is over stock Android 10 with original enforcing kernel. I did have another SystemUI quick reboot yesterday; I think that makes 3 for me since Magisk 19.4 beta upgrade. Nougat and Pie were much stabler for Magisk, for me. I skipped Android Oreo; lazy.

Nearly 4 hours screentime since charge to go with that battery use screenshot.
[Essential Phone Guides, News, & Discussion] Bobbaloo:
I just realized, with my Essential I was still in the habit of deleting fingerprint before booting recovery. I guess that's why. lol Forgot for a minute. With this OP7, not a prob at all
[Essential Phone Guides, News, & Discussion] brqndon:
Anyone having problems sending SMS over WiFi + airplane mode on while on Android 10? I receive texts fine but cannot send out. I get a message saying that airplane mode is on and thus cannot be sent. Weird.
[Essential Phone Guides, News, & Discussion] Bulldog1177:
Ok so I just bought my Essential phone and am currently on August 2019 security patch. Coming from my S7 Edge where root wasn't possible I am interested in rooting my phone and flashing a custom rom to obtain hotspot tethering. Bootloader has been unlocked but I'm lost as to what boot IMG I should use to get twrp and begin my customization journey. Any help is appreciated.
[Essential Phone Guides, News, & Discussion] ktmom:
If you stay on Pie, then Fastboot boot the TWRP img found in the TWRP thread. If on A10, TWRP isn't updated yet (not for any device).

While you can install TWRP on Pie, there is the possibility of instability with both TWRP and Magisk modifying the boot.img.

Start your journey with the PH-1 by understanding the material in https://mata.readthedocs.io/en/latest/ and read this thread. Custom ROM installation instructions will be in the custom ROM thread.
[Essential Phone Guides, News, & Discussion] CamoGeko:
If you leave your PH1 decrypted you'll never have any issues with TWRP.

Just a tip for everyone here...
[Essential Phone Guides, News, & Discussion] BaamAlex:
I want to buy this phone. But i don't need a custom rom on it. Stock Firmware is fine for me on this thing. Can i root it on android 10? What do i have to do when magisk prompts an update? How do i update it?
[Essential Phone Guides, News, & Discussion] DAE1964:
Read the post 2 above yours.
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
On Android 10, could I just disable fingerprint along with PIN and then boot TWRP. Will it then be able to decrypt the /data partition (internal storage)?
[Essential Phone Guides, News, & Discussion] allenjthomsen:
Yes Q10 is rootable. Magisk has a feature where you can flash latest update in phone and reboot.

All you do is click update next to where it says what needs updated in magisk and click install and then it will give you 3 option one being direct install to the devices slot you press that it will flash it then you press reboot and your phone will reboot and magisk will be updated.
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
::bump:: Anyone?
[Essential Phone Guides, News, & Discussion] ktmom:
Try it and find out. What's the worst that can happen? I would Fastboot boot TWRP though.
[Essential Phone Guides, News, & Discussion] rignfool:
You didn't believe me when I said you could?
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
Hey, I am sorry to overlook your helpful comment. I just tried it and it works! Thanks for it. :highfive:
[Essential Phone Guides, News, & Discussion] avd:
Yes. I could modify the data partition from twrp, but it looks like twrp is not compatible with A10 anymore
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
Only the decryption part with lockscreen security set, am I right?
[Essential Phone Guides, News, & Discussion] avd:
It won't boot if twrp is flashed.
[Essential Phone Guides, News, & Discussion] RawSlugs:
Twrp img only boots to twrp, need to install stock boot and flash twrp zip from other slot
[Essential Phone Guides, News, & Discussion] DJBhardwaj:
Thanks for the tip! Seems like after upgrading to 10, I will have to stick with Magisk-only root without TWRP for now. Thanks!
[Essential Phone Guides, News, & Discussion] avd:
You have a rooted partition working with October TWRP?
[Essential Phone Guides, News, & Discussion] rignfool:
Lemme guess... You forgot to boot before flashing Magisk?

It seems if essential changes anything in vendor or firmware .. and you don't boot system first... You bootloop on stock
[Essential Phone Guides, News, & Discussion] avd:
I'll try it now.
[Essential Phone Guides, News, & Discussion] rocketrazr1999:
just remove screenlock in Android to unlock TWRP

---------- Post added at 06:17 PM ---------- Previous post was at 06:12 PM ----------

yup, removing PIN will automatically remove fingerprints and then TWRP will not have any lock or be encrypted
[Essential Phone Guides, News, & Discussion] Edgehead123:
backup fails error 255

has anyone encountered error 255 when making a twrp backup? I get it even when I try to make a back up immediately after flashing a stock image. xda won't let me upload the log :'(

-edit: I figured out how to delete in TWRP, I have successfully done a backup... sorry for spamming
[Essential Phone Guides, News, & Discussion] OMGrant:
All the pre-patched images are gone and I can't get magisk installed at all.
[Essential Phone Guides, News, & Discussion] ipdev:
What rom are you using?

Please give a link to the rom.

Easier to pach and test if I have a link. ;)

Cheers. :cowboy:

Edit:

Dug out my PH-1.

Mine is on Feb 2020, AOSP GSI (SDK29)
[Essential Phone Guides, News, & Discussion] kt-Froggy:
You can just install Magisk app, patch the boot.img yourself and flash it. Check my old post with the steps to root PH-1 with Magisk (it refers to a specific Essential build, but you just take the boot.img from whatever ROM you have, it doesn't matter):

https://xdaforums.com/t/latest-andr...nown-format-from-magisk.4072429/post-82112593
[Essential Phone Guides, News, & Discussion] Darkside1984:
Does anyone know of a website that still hosts prepatched (root/twrp) boot images? It would be so useful.... :unsure:
[Essential Phone Guides, News, & Discussion] sd_shadow:
Why? Just use Magisk
[Essential Phone Guides, News, & Discussion] Darkside1984:
I can't flash TWRP by bootloader method.
[Essential Phone Guides, News, & Discussion] ipdev:
It has been awhile since I flashed mine. 🙂

If I remember correctly, I patched the new boot image with TWRP and then Magisk.

It is a big of a pain in the butt. 🙃

I was looking though some of my older posts trying to find one to point you to but, they all seemed to only note the part a user was having problems with.

As for TWRP.

I basically follow the instructions from TWRP.

Essential PH-1 - [twrp.me] - [WebSite] - Link

Example:

If you install the new boot image to slot 'a'.

Install TWRP to slot 'b'.

Then switch to slot 'b' and reboot.

Once in twrp, install the TWRP installer, to patch both slots.

Since slot 'b' is TWRP only, and slot 'a' is now a TWRP patched boot image..

I would use dd to dump the TWRP patched boot image, then pull it to your computer.

Reboot into bootloader and flash the TWRP patched boot image to both slots.

Double check to make sure you are back on slot 'a' and reboot into system (rom).

Then open the Magisk app and use the install 'patch file' option.

Select the TWRP patched boot image you dumped and continue.

When done, pull the now Magisk and TWRP patched boot image to your computer.

Reboot into bootloader and then flash the now Magisk and TWRP patched boot image to the active slot.

Might have to flash it to both slots??​

Reboot into system (rom).

---

To check active slot using adb.

adb shell getprop | grep slot

Using dd to dump boot partitions.

adb shell dd if=/dev/block/sde11 of=/sdcard/PH1-boot_a.img
adb shell dd if=/dev/block/sde28 of=/sdcard/PH1-boot_b.img

Fastboot commands.

fastboot getvar current-slot
fastboot set_active a
fastboot set_active b
fastboot flash boot_a NameOfFile.img
fastboot flash boot_b NameOfFile.img

fastboot --set-active=a
fastboot --set-active=b

Fastboot commands have changed with fastboot updates.

Not sure if newer fastboot options work with PH-1.

fastboot --slot all flash boot NameOfFile.img
fastboot --slot other flash boot NameOfFile.img

---

For some reason I think I had touch issues every now and then booting into the TWRP only image.

If you run into a no-touch issue..

TeamWin - [twrp.me] - [WebSite] - TWRP Commandline Guide

Example using adb.

Start TWRP sideload on the device.

adb shell twrp sideload

Using the TWRP installer to install a file on the device.

adb shell twrp install /path/to/file.zip

Cheers. :cowboy:

Edit:

PS.

When I refer to pull/push I am refering to adb pull and adb push.
[Essential Phone Guides, News, & Discussion] ultrasuper:
I lost root from stock PIE a while ago by accidentally taking one of the OTA updates. (Not sure why it worked tbh cuz I thought OTA updates wouldn't work when stock rooted/magisk/twrp 🤷‍♂️

Right after that I just decided to go to the end with the stock OTA updates, Android 10 and (the final) Feb 2020 security update.

Now I'd like to get root back. Hopefully without losing my data at all.

Magisk Manager is still there (Magisk 17.1, Manager 7.5.1, TWRP 3.2.3 was where it was before), and when I open that, the only menu option is Settings.. nothing to patch or anything else (like Magisk Hide, etc). There's also an update button for MM, and and Install button for Magisk itself.

Can I safely get root back through MM? Maybe by updating it, and letting it direct install Magisk? Or will it not work in my state?

Do I need to break out the Linux and use adb or fastboot? Steps I can follow would be greatly appreciated.
[Essential Phone Guides, News, & Discussion] MarSOnEarth:
Have you done anything since?
[Essential Phone Guides, News, & Discussion] ultrasuper:
Not as of yet. I need to make sure I get some important stuff off of it before I attempt anything. Also trying to search back posts to about the time of the last security update to see what others encountered
[Essential Phone Guides, News, & Discussion] MarSOnEarth:
Since you are on the OEM ROM, grab that from https://essential-images.netlify.app/ and pull the boot.img from the zipfile. Then, put that boot.img on sdcard and patch it with Magisk (the "install" button in top right). Done.
[Essential Phone Guides, News, & Discussion] ultrasuper:
My Magisk looks like this:

There's only "Settings" in the menu. IIRC, there used to be a menu option to "patch" the boot.img. ?

(the "Advanced" dropdown menu has "Preserve force encryption" checked, "Preserve AVB 2.0/dm-verity" checked, and "Recovery mode" unchecked)

Is MM supposed to "detect" boot.img in /downloads or something? and present the option to patch? without updating MagiskManager OR installing Magisk as seen in the screencap (which is a much newer vers than I had on the phone and I'd be a little concerned about compatibility issues)?

It's been a long time I can't recall how the process exactly flowed.
[Essential Phone Guides, News, & Discussion] MarSOnEarth:
I have not used Magisk Manager (MM) (I usually just sideload Magisk itself) but you said that you have Magisk (17.1 is old!), so why not use that.

But, so what happens when you click on Install in MM? It should ask you for the patching method -- you'd choose 'from file" and navigate to the boot.img. If yes, then that should do it.
[Essential Phone Guides, News, & Discussion] Meerk4ty:
Guys I have a problem and hope you can help me, I have Mata with QQ1A.200105.007, Jan 2020 rom installed.

I have already:

Installed device drivers;

Recognized phone in device manager;

Unlocked bootloader;

Unlocked critical flashing.

When I try to change partition from A to B - I am getting some weird errors in my CMD like:

Device does not support slots

Command failed

Unknown command

Failed to identify current slot

I just want to flash boot.img and install LineageOS then.

I have already tried 4 different cables and 3 different USB ports.