yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] morphius88:
Credit to tech_head from post# 787 and the OP of this thread. For anyone that missed it or wanted to see if that method still works, it does.

This allows you to skip twrp and lets you keep all your magisk modules and keep all your data.

Not sure if it matters, but remove substratum themes before doing any of this, reapply after all steps are finished.

I have done it with security/fingerprints on and substratum themes applied and it still worked without data loss or other issues, but as a precaution might as well disable both.

1) download the stock boot image file for the whatever version of android you have currently have here <- Credit to bmg1001

2) put it in you adb folder and open a cmd window from that folder (ctrl+shift and right click then select cmd window)

3) Connect device, type "adb devices" in the cmd window to make sure the device is there

4) type "adb reboot bootloader"

5) type "fastboot flash boot <path to the boot image you downloaded earlier>"

6) type "fastboot reboot", your phone should reboot and no longer have root

7) take the OTA update

8) download the boot image for the current version you updated to from same link above and transfer it to your phone if needed

9) on your phone open magisk manager or magisk installer , it should ask you install magisk then select patch boot image

10) transfer that patched boot image to your computer (you can put it the adb folder if you'd like)

11) with phone connect to pc, type in the cmd window from before "adb reboot bootload" then "fastboot flash boot <path to the patched boot image>"

12) this should flash the "rooted" boot image, type "fastboot reboot", your phone will reboot and should now be rooted.

Your magisk modules should still be there and all your data should be good.
[Essential Phone Guides, News, & Discussion] RandomPooka:
Bonus points for not having to disable security for this, too. It's definitely the most effective way in my opinion.
[Essential Phone Guides, News, & Discussion] dirtyreturn:
Hi, I just received my essential yesterday and I'm not sure just what to do to unlock the bootloader. My device , when in fastboot gets a no permission check use rules notification after any fastboot command.

It is recognized when booted into Android using adb.

Has there been any instances you can recall where, even when oem unlock is enabled that fastboot commands don't work?
[Essential Phone Guides, News, & Discussion] NaterTots:
Nope not that I recall.

It sounds like you have an issues with your UDEV rules.

It is also possible it's the cable your using. You don't want to use the cable that essential provides as it is known to brick devices.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Did you install essentials phone drivers?
[Essential Phone Guides, News, & Discussion] dirtyreturn:
What are UDEV rules?? The cable I used is the data transfer cable from the Nexus 6p -- adb commands work like they should.. I do have some other type c cables around.. And thanks for the heads up with the provided cable

Are the essentials phone drivers required when running Ubuntu?
[Essential Phone Guides, News, & Discussion] IH8TouchWiz:
You don't need drivers if you're using Ubuntu, just make sure you have a working adb and fastboot environment and use this link to set up udev rules: https://github.com/invisiblek/udevrules .
[Essential Phone Guides, News, & Discussion] shaq1612:
any solution yet?
[Essential Phone Guides, News, & Discussion] aer0zer0:
What are you doing? Trying to run P beta and root?
[Essential Phone Guides, News, & Discussion] mobileman88:
I have had issue rooting the P beta. I tried to run Magisk 16.4 using Magisk Manager to perform a root of the device. I pointed Magisk Manager to the P B1's boot image file, but all I kept getting is the following in the screen that pops up after 16.4 is downloaded :

===

Flashing

- Device platform: arm64-v8a

- Extracting files

- Boot image is signed with AVB 1.0

failed:

! Installation failed

===
[Essential Phone Guides, News, & Discussion] aer0zer0:
Ok.

Flash twrp from fastboot

In twrp, flash the stock boot.img (you need to get rid of twrp)

Optional *flash custom kernel* EX or the one from discord

Flash magisk 16.4 beta

Reboot
[Essential Phone Guides, News, & Discussion] mobileman88:
Thanks for the quick reply. Previously for rooting 8 and 8.1,i could boot into stock kernel, install Magisk manager and patch a copy of the boot image which I copied in. 9 requires twrp?
[Essential Phone Guides, News, & Discussion] mhajii210:
Android P beta 1 and root

The problem is I lose root after some time and I have to reboot to get it back. I flashed twrp via fastboot, flashed boot image, then flashed Magisk 16.4. Anyone successful in getting root to stick on Android P beta 1???
[Essential Phone Guides, News, & Discussion] NaterTots:
I'm on build .022 and have no problem with root.

I did have to install magisk via twrp though as going through the magisk app wouldn't work.

So I did twrp, boot.img, magisk 16.4 then rebooted.

It's been a week now with no issues
[Essential Phone Guides, News, & Discussion] aer0zer0:
[MENTION=4482304]NaterTots[/MENTION] and I seem to be just fine without issue.

So to recap

1. Flash twrp in bootloader

2. Boot to twrp

3. Copy stock boot image over to phone.

4. Flash stock boot.image in twrp (this will overwrite twrp, because your phone WONT boot with twrp on it)

5. (OPTIONAL) if you want a custom kernel (EX or the one from discord group) flash it in twrp.

6. Flash magisk in twrp (I'm using 16.4 beta ATM, but there are custom builds that work too)

7. reboot

If you don't have magisk manager after reboot. Get the manager out of the /common folder inside the magisk zip you flashed.

Good luck.
[Essential Phone Guides, News, & Discussion] tech_head:
No issues.

I installed via twrp.

I'm running the P-Beta with ElementalX kernel and Magisk 16.4.
[Essential Phone Guides, News, & Discussion] aer0zer0:
It really just can't be any simpler to root this phone.
[Essential Phone Guides, News, & Discussion] ceelos218:
Can someone root my phone through TeamViewer? I can PayPal 5$
[Essential Phone Guides, News, & Discussion] aer0zer0:
It's gotta be rooted on device. What are you having problems with?
[Essential Phone Guides, News, & Discussion] ceelos218:
I'm just nervous I'll brick it. I'm coming from a 2014 Droid Maxx so everything is fairly new to me.
[Essential Phone Guides, News, & Discussion] aer0zer0:
I had a x pure, you will be fine. It's actually quite similar. The a/b thing is different, but it's actually better imo. So, what os/month patch you on?
[Essential Phone Guides, News, & Discussion] ceelos218:
I'm already bootloader unlocked and I'm on latest P beta 2 June patch. Yes the more I try to understand a/b the more confused I get. I believe I was having issues flashing twrp .. I got some error.
[Essential Phone Guides, News, & Discussion] mobileman88:
It's not that difficult. Let me know if you need some handholding.

---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------

Sent you a pm
[Essential Phone Guides, News, & Discussion] aer0zer0:
Ok, this is where the only confusion with this really comes in.

There is no recovery image, it is built into the boot image (kernel). TWRP that is available won't boot this phone, but it will give you a way to flash a working boot.img WHILE in TWRP (mind blowing).

Do you have working fastboot? If you do "fastboot devices" do you return your s/n in command prompt.
[Essential Phone Guides, News, & Discussion] NaterTots:
Did you also unlock Critical? That'll be needed along with the bootloader.
[Essential Phone Guides, News, & Discussion] ceelos218:
I kindly want to thank this user for helping me out through TeamViewer.. ? appreciate the help. I'm rooted fine now
[Essential Phone Guides, News, & Discussion] mongofrye:
i unlocked the bootloader. when i tried to install twrp in fastboot is when i ran into my first issue. it kept coming back with "failed remote no such partition". i ended up designating slot a. i followed all the other instructionsn for the 8.1 stock and magisk. one time it just kept looping and finally opening fastboot. i had to reinstall the stock oreo image and it finally booted back up.... but no root or magisk installed on the phone. use to do root back int he day on my other android phones but having a heck of a time here. any advice?
[Essential Phone Guides, News, & Discussion] aer0zer0:
Was it easy?
[Essential Phone Guides, News, & Discussion] shaq1612:
yeah I'm on the June update and I've done the root process about 8 times now but after a couple minutes I lose root for some reason. Once it lasted long enough for me to setup sixaxis and get my controller working but I lost it while the controller was connected.
[Essential Phone Guides, News, & Discussion] aer0zer0:
How are you doing root?
[Essential Phone Guides, News, & Discussion] crixley:
I'm curious myself. I see these posts a lot and I've never had a single issue.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Yep, kinda wanna know now
[Essential Phone Guides, News, & Discussion] shaq1612:
I flash twrp, boot into twrp, flash the stock boot img, then I flash the magisk zip same as I've always done for root. This update is the first time I've experienced this.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Are you using Xposed or anything else? Which version of magisk?
[Essential Phone Guides, News, & Discussion] stryver:
Coming from another device it would be useful to note that recovery is located and must be flashed to the 'boot' partition, not the 'recovery' partition. Because there is no such 'recovery' partition on this device, it is likely the reason you get errors when trying to load twrp.

[MENTION=1801480]mongofrye[/MENTION] meant to quote you too
[Essential Phone Guides, News, & Discussion] shaq1612:
no Xposed modules or anything and I'm using the magisk beta zip I think it's 16.4
[Essential Phone Guides, News, & Discussion] aer0zer0:
Can you start fresh?
[Essential Phone Guides, News, & Discussion] shaq1612:
start fresh as in factory reset?
[Essential Phone Guides, News, & Discussion] aer0zer0:
or flash the images from the BTS thread, which is what im doing.
[Essential Phone Guides, News, & Discussion] mobileman88:
What are the commands you use to make the BTS dumps? Do you mind sharing? Thanks
[Essential Phone Guides, News, & Discussion] aer0zer0:
put twrp on opposite slot of images you want, boot into twrp, make those files into bats.

Essential posts their fastboots and OTA's now on their website, doing this is "generally" moot. but its good to know.

Thats how i make the BTS files now.
[Essential Phone Guides, News, & Discussion] mobileman88:
Thanks. This can help make data dumps too I would think
[Essential Phone Guides, News, & Discussion] mobileman88:
Thanks mate.

Do you do the commands above in TWRP? I get access denied when I tried to perform them in adb since a default adb shell does not have root perms to dump out partitions.

Would like to also dump out the data partitions.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Correct, needs to be done in twrp
[Essential Phone Guides, News, & Discussion] mobileman88:
what about dumping out data, can i do it for the data partition the same way too? or is it not recommended?
[Essential Phone Guides, News, & Discussion] aer0zer0:
I suppose you could
[Essential Phone Guides, News, & Discussion] TotalChris:
Why can't I patch the images given? I'm using the latest P Beta. Magisk manager keeps telling me that the patch failed... I'm not trying to flash the boot image via Magisk manager, so it shouldn't be root issues... Just patch it so I can flash via adb. Is there a pre-patched image you have that I can flash? I've been trying this for awhile now.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Patching via magisk doesn't work. Easiest way is to do via twrp.
[Essential Phone Guides, News, & Discussion] TotalChris:
I can't do that. My phone refuses to unencrypt itself. Tapping the encryption entry in settings on my phone doesn't do anything, and even with all screen locks off, twrp asks for a password. I've tried every passcode I've ever used. I gots nothing
[Essential Phone Guides, News, & Discussion] aer0zer0:
Did you disable finger prints?
[Essential Phone Guides, News, & Discussion] TotalChris:
Yes
[Essential Phone Guides, News, & Discussion] aer0zer0:
that makes no sense. no fingerprints, no swipe, no pin and it still says encrypted in twrp?

---------- Post added at 07:18 PM ---------- Previous post was at 07:17 PM ----------

Are you usimg the latest TWRP? v11?
[Essential Phone Guides, News, & Discussion] mobileman88:
As sdcard is already mounted for backing up of the other partitions. Can I save it elsewhere? Data is about 15GB.
[Essential Phone Guides, News, & Discussion] RandomPooka:
Probably a good idea. I think internal SD is mounted under /data/media which means it would be dumping itself to itself, wouldn't it?

Recursively filling your storage up in the process, possibly. Being glitchy AF at the least.
[Essential Phone Guides, News, & Discussion] mobileman88:
is there any adb command to dump data straight out to the PC instead? Previously what I do when I had persistent working twrp recovery is to run nandroids with TWRP but with the current AB partitioning, it's no longer possible as recovery is part of the boot image. Unless I can automate the injection of TWRP into stock boot.img which could help I guess. (if someone could point me to the steps, i can possibly cobble together a shell script to do so)
[Essential Phone Guides, News, & Discussion] kfhughes:
I had to do something similar; you can do a recursive pull:

adb pull /sdcard
[Essential Phone Guides, News, & Discussion] mobileman88:
Thanks. Pulling /sdcard over adb is significantly slower than file transfer operations over windows explorer. Is there buffer or cache settings that can speed it up? My main objective is to get something like a nandroid which can restore to another phone of the same make/model in case it's lost/damaged etc. Right now I am doing backups with Titanium Backup twice a week and syncing it to Gdrive coupled with SMSBackup+Restore and Whatsapp backups. But nothing beats a quick nandroid restore which I used to be able to do on my Nexus 6P
[Essential Phone Guides, News, & Discussion] COCODRILO45:
good afternoon guys i just got essential phone today sprint version i unlocked the bootloader now im trying to root i could successfully boot to twrp and i flash stock boot image 234 then i flash magisk 16.4 everything seems find until the end ends with error failed to mount system (devices or resources busy) any tips on what could i be doin wrong thanks in advance guys
[Essential Phone Guides, News, & Discussion] aer0zer0:
Prior to flashing magisk, mount system in twrp. That will get rid of that error. Although it really shouldn't matter. Are you not getting magisk manager when rebooting? If so, grab the apk from inside the magisk zip, it's in the common folder. Install it and you should be g2g.
[Essential Phone Guides, News, & Discussion] surya17:
Guys, Mine was rooted on June update. To update to the July version, I Flashed the Stock boot.img and rebooted to remove the root. Still can't update via OTA. Can anyone please help?
[Essential Phone Guides, News, & Discussion] NaterTots:
I've been sideloading the current version I'm on rather than just flashing the boot.img. then I go and reroot without an issue
[Essential Phone Guides, News, & Discussion] surya17:
But won't it wipe all the data?
[Essential Phone Guides, News, & Discussion] NaterTots:
No. It doesn't wipe data if you sideload the builds from essential.

You could also use the Back To Stock builds but just choose the no wipe option.
[Essential Phone Guides, News, & Discussion] jesus359:
Hello, I was rooted in the beginning but then I just factory reseted it through the build that Essential provided on their website. Now I am trying to root again with this method but it keeps telling me that the /system is not mounted once I get to flashing Magisk at the end. The error it gives me is "Failed to mount '/system' (Invalid argument)

I tried to go into Mount on TWRP and press system but it wont let me do it. In the begining I did add the option to mount the /system when it asks you to swype, so it was not read only, I did this twice and it still gives me the error. I tried googling how to mount system either on the terminal through TWRP or through a flashboot\adb command but I could not find anything. Any help please?
[Essential Phone Guides, News, & Discussion] spotmark:
Be sure to disable any passwords or security before you use TWRP.
[Essential Phone Guides, News, & Discussion] jesus359:
I did. It seems like it would only let me enable it if I switch slots but then that's it. Since it has been factory reset multiple times and I know its going to factory reset again, I have not put any passwords on the phone. Does the swipe to unlock count as password/security? Now when I think I rooted it correctly just sends me to a bootloop, I just flashed the factory images from Essential and left it for now. Not sure what Im doing wrong.
[Essential Phone Guides, News, & Discussion] harsh2193:
I unfortunately forgot to patch the stock boot image for the new P beta (Beta 2 launched in July) before updating. Can someone please upload the patched boot image so I can flash it with adb?

Link to the stock boot image: https://drive.google.com/open?id=1ug46gJCR02_oh7-ubrsvGGRSbMwvFoSl (taken from OP)
[Essential Phone Guides, News, & Discussion] noidman123:
Maybe someone here can help, I'm on the newest P build, magisk/root doesn't seem to stick for me. I updated from 8.1 stable builds via adb using the OTA from the Essential website. I'm using the latest P-BETA-2-030 boot img from the op and Magisk 16. I boot into bootloader, fastboot flash -i 0x2e17 boot twrp-mata_11.img, boot into twrp, flash the stock boot, then magisk, and it says it works but when i reboot into system i can see magisk manager but it keeps asking me to install/update it. Any ideas? Thanks in advance.

Edit: forgot to mention I was rooted when i did the OTA through adb, I didn't wipe anything beforehand if that helps

Edit 2: Fixed it lol, if anyone else is running across this issue, make sure you mount /system in twrp before you flash magisk
[Essential Phone Guides, News, & Discussion] hkjr:
How's it running? Are you using Subs?
[Essential Phone Guides, News, & Discussion] noidman123:
Everything seems to be running fine, no real bugs or performance issues, root is sticking and all my modules are working. I haven't tried substratum yet though. Will try in a few
[Essential Phone Guides, News, & Discussion] aer0zer0:
When mounting system, also remember to uncheck "mount system r/w"
[Essential Phone Guides, News, & Discussion] hkjr:
all i needed to know lol. goal is to sideload P this weekend.
[Essential Phone Guides, News, & Discussion] noidman123:
Honestly it was worth it. Gestures take some getting used to but you can disable them. The built in notch support in P changes how notifications show at the top, there's a built in night/dark mode (although it's not system wide yet) etc. I haven't found any real negatives lol.
[Essential Phone Guides, News, & Discussion] ceelos218:
Careful with sais Oreo theme.. don't use the transparent or you'll bootloop. Swift dark is only good for downloaded apps.
[Essential Phone Guides, News, & Discussion] LieutenantCommanderData:
tried this but at step 7 (get the OTA) I get: Couldn't update installation problem also tried both slots (step 5)

any tips how to troubleshoot?
[Essential Phone Guides, News, & Discussion] RandomPooka:
When you install magisk using the manager, are you using the option to patch a boot image file? It sounds like you're trying to patch the boot partition of the device on one or both slots, and not patch the boot image dump that you copied to the phone in the previous step. It should prompt you asking for which file you want to patch if you've selected the right option (It's the second option down when you select "Install", and is labeled "Patch Boot Image File")
[Essential Phone Guides, News, & Discussion] LieutenantCommanderData:
I'm not at that stage as I'm not getting the OTA. (At step 7) so after flash stock boot I can confirm that I lost root but looks like I'm not stock enough to get OTA.
[Essential Phone Guides, News, & Discussion] RandomPooka:
Oh, sorry. I was looking at step 9 and not 7. My mistake.
[Essential Phone Guides, News, & Discussion] AndrewX85:
Essential ph-1 demo version

Hi,

My ph-1 i bought from ebay. I contacted essential costomer services and was advised that the ph-1 I bought is unlocked demo sprint version. They confirmed that there is no difference in the retail phone hardware to demo phone hardware. Although I will not get support or update from essential.

Can you advise how i update my phone if I am not able to download updates.

P.S. I can download updates, however it won't install. I also noted that the phone attempts to download file 8.1.0 and my phone already running 8.1.0.:crying:
[Essential Phone Guides, News, & Discussion] shaq1612:
So I'm on the July update now and I still have the same problem,root doesn't stick, it lasted one reboot, granted some superuser permissions then was gone again. Guess I'll have to do without root till this is figured out.
[Essential Phone Guides, News, & Discussion] mobileman88:
What are you using to root?
[Essential Phone Guides, News, & Discussion] srb7215:
Are you using the newest magisk? There was an update to 16.6 because 16.4 has some issues of not sticking. I never ran into it but could be your problem.
[Essential Phone Guides, News, & Discussion] morphius88:
Did you figure this out or still stuck without root?

Did you disable any substratum themes (if you had any).

Its possible at step 5, you did not flash the stock boot image. Check if you still have root ( I usually use a root checker app from the appstore)

Ive done that method 3 times without a single hiccup.
[Essential Phone Guides, News, & Discussion] LieutenantCommanderData:
I end up using the BTS with No wipe and re-rooted see here: https://xdaforums.com/essential-phone/how-to/guide-how-to-patch-update-rooted-t3813496.

I'm pretty sure I did step 5 correct as I lost root.

Also no substratum, pretty much stock beside the root for AdBlock

I was on April so maybe that played a role here.
[Essential Phone Guides, News, & Discussion] aer0zer0:
shouldnt have been a issue. PM me if you like, ill try and help you out
[Essential Phone Guides, News, & Discussion] morphius88:
Yep, should not have made any difference being on April. Last one I did I was coming from February straight to June Update.
[Essential Phone Guides, News, & Discussion] LieutenantCommanderData:
Really appreciate your help. I'm good as the BTS worked for me. Will try again with August patch and report back.
[Essential Phone Guides, News, & Discussion] shaq1612:
I'll try the 16.6 update. 16.4 worked fine for me up until these last two updates.
[Essential Phone Guides, News, & Discussion] aer0zer0:
good deal. did you do anything different? or did it just work this go-around
[Essential Phone Guides, News, & Discussion] mobileman88:
Yo mate, one thing I noticed when dumping is that the files I generated is much bigger than what you have. For example, my boot image dumped for A or B are both 64MB instead of yours which are 20+mb. Am I doing something wrong?
[Essential Phone Guides, News, & Discussion] aer0zer0:
your images are raw, mine are sparse. its all the same in the end.
[Essential Phone Guides, News, & Discussion] mobileman88:
How can I create a sparse image in this case? Thanks
[Essential Phone Guides, News, & Discussion] aer0zer0:
why? im mean you cant really from your own dumps. but its fine. just think of it as 1:1 dump of a hard drive with all the 0's included. its why your is bigger.
[Essential Phone Guides, News, & Discussion] mobileman88:
More to reduce the storage required and also time required to flash if it's smaller thats all
[Essential Phone Guides, News, & Discussion] kuyzz:
im a retard im stuck in boot screen.... HELP