yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] bmg1001:
Added a Magisk'd Boot Image for the new Oreo Beta. I have NOT tested it so if it borks your phone, you know what to do. For now, you're gonna have to use the old root method. The boot image DOES NOT have TWRP built-in. Happy rooting! :)

If you face an error while trying to flash Magisk, you may have to wipe your data with "fastboot -w" and then try again.
[Essential Phone Guides, News, & Discussion] billybong10:
Works great! Thanks [MENTION=4550123]bmg1001[/MENTION]
[Essential Phone Guides, News, & Discussion] Hung0702:
I'm on NMJ32F. Got TWRP up, though a few pixels on the right are obscured by a vertical black bar.

Had to install magisk through adb shell twrp sideload, but couldn't install xposed v88.2 sdk25 the same way. Won't install directly from TWRP either, and it returns "/system could not be mounted!"

I checked it under Mount, but then it still wouldn't mount. Suggestions?

EDIT: Installed Xposed from within the apk. Not sure about the error message from within TWRP tho, nor the the obscured portion of TWRP.
[Essential Phone Guides, News, & Discussion] garywojdan81:
I read that flashing the P ota file on top of the image file fixes the wifi issue.
[Essential Phone Guides, News, & Discussion] mobileman88:
so no full wipe required? cool
[Essential Phone Guides, News, & Discussion] brepeti:
hi, there's someone who's been succesfully rooted? (android P)
[Essential Phone Guides, News, & Discussion] aer0zer0:
Yea, same way as O, twrp------>stockboot------->magisk 16.4 beta
[Essential Phone Guides, News, & Discussion] brepeti:
maybe that was a problem, i tried it with 16.0 magisk, and the device can't boot, just show the essential logo.

i hope with 16.4 will work
[Essential Phone Guides, News, & Discussion] aer0zer0:
It will, I already did.
[Essential Phone Guides, News, & Discussion] ace2k8:
If all fails we can still downgrade with fastboot and ADB correct?
[Essential Phone Guides, News, & Discussion] aer0zer0:
Yep, use the BTS zips in the firmware thread
[Essential Phone Guides, News, & Discussion] zenmechanic:
Hoping someone here can assist me. I've read through this thread and can't seem to find another user attempting to do the same thing as me.

I'm on the sprint 7.1.1 build NMJ32F and security patch level from Nov 5th, of 2017. I'd like to update this to Oreo and keep root without wiping out my data. Is the correct path: patch the BTS boot.img on the installed build, then let the OTA apply plus patches, then fastboot back into TWRP and patch the boot and flash Magisk? Thanks for any assistance here.

NVM: figured it out. Let OTA upgrade happen, fastboot twrp, flash May boot image then magisk.
[Essential Phone Guides, News, & Discussion] rignfool:
Now there is a name I haven't seen in a long ass time..........

;)
[Essential Phone Guides, News, & Discussion] RandomPooka:
Like Obi-Wan?
[Essential Phone Guides, News, & Discussion] rignfool:
More...

Broken...
[Essential Phone Guides, News, & Discussion] nstirton:
Thanks for the great guide!

Just an FYI, having went round the houses for an hour finding out why I couldn't install TWRP, I used a different TWRP version than the OP links to and it worked just fine. Perhaps there's an updated version out there now?

Best, Neil
[Essential Phone Guides, News, & Discussion] indian84:
TWRP 11 is the latest..
[Essential Phone Guides, News, & Discussion] mobileman88:
Is there anyone working to get twrp to coexist with stock boot?
[Essential Phone Guides, News, & Discussion] indian84:
Nope
[Essential Phone Guides, News, & Discussion] mobileman88:
That's a little sad... I really miss having the ability to boot to twrp regularly and making a Nandroid.
[Essential Phone Guides, News, & Discussion] stinger4321:
i am unable root since May update. i tried flashing the patched boot image no go.. and tried the traditional twrp then may boot image then magisk.. system wont boot after restarting. i have to flash factory boot from fastboot to recover. ideas?

thanks
[Essential Phone Guides, News, & Discussion] bmg1001:
Which version of Magisk are you using?
[Essential Phone Guides, News, & Discussion] stinger4321:
16.3 thats what i was using since it came out
[Essential Phone Guides, News, & Discussion] bmg1001:
Try using v16.4
[Essential Phone Guides, News, & Discussion] stinger4321:
i saw that came our thought it was more for P.. will try it out
[Essential Phone Guides, News, & Discussion] TheZadok42:
After rooting my gmail and calendar apps keeps crashing (not even launching)

What can I do?
[Essential Phone Guides, News, & Discussion] Seraph08:
pre-patched Android P bootimage

https://androidfilehost.com/?fid=962339331458992492
[Essential Phone Guides, News, & Discussion] InkSlinger420:
Ya miss me?

Figured it was about that time to start showing my ugly mug again...
[Essential Phone Guides, News, & Discussion] ryan_c:
I've just updated to the may oreo release, can't get magisk installed. I've tried 16.0 and 16.4. 16.0 seems to install cleanly, but I get a boot loop. 16.4 fails to mount the /system partition.
[Essential Phone Guides, News, & Discussion] bmg1001:
Try mounting system manually within TWRP before flashing Magisk v16.4. Not sure why it wouldn't work.
[Essential Phone Guides, News, & Discussion] ryan_c:
Tried again, and it worked. I didn't follow the instructions correctly the first time. Will I be able to re-root after updating if I encrypt my phone?
[Essential Phone Guides, News, & Discussion] bmg1001:
Yeah, rerooting is all good and easy, encrypted or not.
[Essential Phone Guides, News, & Discussion] xslntx:
Thanks so much for this. 7.x and 8.x were no issue for me but P gave me a bootloop after magisk finished patching.
[Essential Phone Guides, News, & Discussion] mobileman88:
How did you patch this image? Trying to patch the DP2 (early may) boot.img results in error and so does trying to patch the boot.img from the one from a few days ago

However, patching 8.1 May image is successful.

Patching with latest MagiskManager and Magisk 16.4
[Essential Phone Guides, News, & Discussion] Deandre7452:
Did you get root yet on your DP2 because I got root on mines

Just by install Magisk 16.4.zip not boot.img
[Essential Phone Guides, News, & Discussion] mobileman88:
I normally root by patching the stock boot image using Magisk manager. Copying out the patched image then fleshing it in fastboot. No need to have twrp at all. However I can't seem to do it for all the P releases
[Essential Phone Guides, News, & Discussion] crixley:
worked just fine for me.
[Essential Phone Guides, News, & Discussion] gk1984:
I do this too. But this wasn't working for P. Had to do it via TWRP by flashing the Magisk zip.
[Essential Phone Guides, News, & Discussion] crixley:
Weird that it didn't work for you guys.
[Essential Phone Guides, News, & Discussion] Deandre7452:
Yea I had to flash Magisk 16.4 zip in twrp to can't patch boot.img either
[Essential Phone Guides, News, & Discussion] crixley:
I unzipped the fastboot zip and patched the boot.img that was in there
[Essential Phone Guides, News, & Discussion] mobileman88:
I took the boot.img from the BTS thread but kept getting error. Which fastboot zip are you using?
[Essential Phone Guides, News, & Discussion] crixley:
The android P one from the essential site
[Essential Phone Guides, News, & Discussion] mobileman88:
It keeps giving me access error when trying to download. The other Ota file works fine
[Essential Phone Guides, News, & Discussion] crixley:
Download the OTA then, that would have the boot.img as well
[Essential Phone Guides, News, & Discussion] LVA_:
Not able to get into recovery

My PH-1 was on Android 7 and rooted following this thread. To upgrade to 8.1, I restored the boot images in Magisk Manager and did the OTA (8.1 May) update. Went smooth, rebooted, and working 8.1 system.

Now, to root again...

1. Disabled the screen lock

2. Downloaded TWRP (twrp-mata_11.img) and the boot image (OREO-8.1-MAY.img) as per instructions

3. Rebooted into fastboot

4. sudo fastboot flash boot twrp-mata_11.img: success

5. Select "Reboot into recovery" from the bootloader... and nothing. Phone goes into poweroff. Once I start it again, I get into fastboot. Can't get into recovery, haven't got an Android to boot anymore either.

6. Rebooted into fastboot, flashed the boot image, powered off, restarted, all is well again. But, no root.

7. Tried again with twrp (steps 3-5). No go. Reboot into fastboot, flashed the boot image, powered off, restarted... hangs on the "loading" dancing dots. Crap.

8. Noticed that the phone was flashing to boot_a in the meantime. No idea why - did it detect TWRP failing, and decide to "fall back"? Anyway, fastboot set-active _b and flashing the boot image again results in a working but unrooted phone.

On previous phones I was able to do "fastboot boot twrp.img" and have an "in-mem" recovery, without actually having to reboot into it. I can't find anything like that anymore, and the PH-1 reports "FAILED (remote: unknown command)" when trying to boot the twrp image directly, so I guess that's off the table.

So... any ideas? I feel like I'm missing something here. I looked into sideloading but that requires a working recovery too.
[Essential Phone Guides, News, & Discussion] mobileman88:
This will require TWRP . I am trying to do it without TWRP

---------- Post added at 09:53 AM ---------- Previous post was at 09:52 AM ----------

doesn't... kept getting this error

---

mata:/sdcard/MagiskManager/logs $ cat install_log_20180531_094832.log

- Device platform: arm64-v8a

- Extracting files

- Boot image is signed with AVB 1.0

Bad system call

Failed!

! Installation failed

---

Happened to both P previews from early May and the one from last week. This is with 16.4 and MAgiskManager 5.7.0

---------- Post added at 09:53 AM ---------- Previous post was at 09:53 AM ----------

there's only a big patch.bin file, no boot image file in there.

---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------

there's only a big patch.bin file, no boot image file in there.
[Essential Phone Guides, News, & Discussion] bmg1001:
Seems like a problem for those on the P preview on the Pixel 2/2 XL too. Unfortunately, it seems like your only route would be to flash Magisk v16.4 via TWRP. Not sure why this issue occurs, or why it only seems to happen to a few people.
[Essential Phone Guides, News, & Discussion] mobileman88:
I found that I will be able to patch the DP2 image if I first boot with a pre-rooted DP1 image. The error simply does not happen.
[Essential Phone Guides, News, & Discussion] Itzamistry:
If I am currently on .166 stock Oreo. Can I root my device simply with adb sideload magisk.zip or do i need to flash the boot.img too. If so, do I flash it before or after sideloading magisk.zip and how? Thank you.
[Essential Phone Guides, News, & Discussion] LVA_:
Turns out that patching the boot image manually with Magisk Manager, transferring it to pc and flashing it properly to slot _b with fastboot, was all that's required. I still don't know what's the issue with flashing TWRP, but then again... this way is so much easier. Rooted phone again!
[Essential Phone Guides, News, & Discussion] n2locarz:
Hey guys, This is my first phone with two partitions so it's a learning curve. Everything is straight forward. I had no issues until I took the latest Oreo May update. I fastboot flashed (clean) to May Oreo build. After getting things setup I then attempted to root. Tried Magisk 16.0, 16.3 and 16.4. Even checked the "mount system" box since that was failing. I used the magisk manager to patch the boot image and have been playing with that. I was somehow able to get root but then I went to install a new hosts file via TWRP and now I lost root and I still have ads... ugh. Anyone have advice? Thanks
[Essential Phone Guides, News, & Discussion] mobileman88:
Did you reinstall stock boot image after going into twrp?
[Essential Phone Guides, News, & Discussion] n2locarz:
I can confirm without a doubt the Wifi issue is caused by applying the incorrect stockboot.img after installing Magisk. After I encountered this issue, the fix was this:

Go back Fastboot, re-flash TWRP, this time apply the correct boot.img and problem solved. When I tried it via fastboot, it wouldn't take. I'm sure it's because of the partitions and my lack of understanding them at this point.

Magisk 16.0 will root - build OPM1.180104.166 AFH (latest oreo 8.1 may)

If you need a copy of the patched boot.img, it's located here:

https://androidfilehost.com/?fid=962339331458991038

Sorry if this has been over before. The thread is quite large and needs to be split into O & P Rooting for specific
[Essential Phone Guides, News, & Discussion] bmg1001:
Uploaded the boot image for the new P beta. I changed the naming of the boot images a bit, but they have the last three numbers of the build number now. This new P beta released today is PPR1.180510

.022.
[Essential Phone Guides, News, & Discussion] djc924050462:
Rooting Failed about the new P beta 022.

i have tried 3 times ,all failed.

Every time when i flashed TWRP,then i was going to reboot phone ,it has showed me that system has broken.can not enter system.

But this method works well about DP2

is there any bug about flash TWRP into DP3?

and how can i fix it:)

---------- Post added at 07:34 AM ---------- Previous post was at 06:55 AM ----------

i have fixed it, i chose wrong partition before.:laugh:
[Essential Phone Guides, News, & Discussion] leandrohvlucas:
Sorry for bringing back from the hell... heheh

But just to clarify, if i'm rooted, i don't need to apply my current boot.img version and then apply the OTA... i just flash the latest BTS updated and after just flash the magisk patch? Using the no-wipe option there's no risk?

Sorry... just bought the Phone, it will arrive at next monday, but i'm already reading everything i can to not mess up with it... kkkk
[Essential Phone Guides, News, & Discussion] bmg1001:
Yup. Just flash the updated BTS and then Magisk. Shouldn't run into any weird issues updating that way.
[Essential Phone Guides, News, & Discussion] feligoni:
For some reason I'm not being able to get my phone rooted. I am on latest P beta. I follow all the steps, flash twrp, then boot image, then magisk 16.4 or 16.0(tried both). When i reboot back to System there's no magisk manager app installed. I install it manually but it tells me there's no Magisk installed.

Everything should be flashed on _b partition right?

Anyone experiencing the same? I'm clueless.
[Essential Phone Guides, News, & Discussion] bmg1001:
Can you elaborate what you mean by "everything should be flashed on _b partition"?
[Essential Phone Guides, News, & Discussion] feligoni:
We have A/B partitioning right? On twrp it says current slot: B. I assume when i flash the boot image and magisk they are being flashed on that slot right?

My question is if thats correct or should i change the slot to A and flash image and magisk on A slot. Which i dont remember doing for previous build of Android P.
[Essential Phone Guides, News, & Discussion] bmg1001:
Yeah, when flashing Magisk, you generally want to flash it to the partition where the ROM you want to root is on. I'm not sure why Magisk isn't working for you. All I can suggest is repeating the process (Flash TWRP, install stock boot image, flash Magisk), and then wait a few minutes while the Magisk app installs in the background upon boot. Also, I think Magisk v16.4 is the only one that works on P.
[Essential Phone Guides, News, & Discussion] feligoni:
Well, looks like the eight time was the one :P It seems to be working now after 8 tries. Thanks for your help!
[Essential Phone Guides, News, & Discussion] bmg1001:
June Security Update boot image is up. :good:
[Essential Phone Guides, News, & Discussion] SupaSimon:
Hi! It looks like I am stuck in FastBoot. When I try flashing any boot image, it tells me "remote: Error flashing partition." What should I try?
[Essential Phone Guides, News, & Discussion] bmg1001:
Try using a different USB port or different USB cables. Also, try rebooting the bootloader too. Don't know what causes this error exactly, but I usually solve it on my end by doing this.
[Essential Phone Guides, News, & Discussion] c19932:
I am currently on oreo 8.1 rooted with magisk. My question is, is there any way for me to do a system update without having to reinstalling all of my magisk module again?

My planned steps were (starting with my rooted 8.1): restore image in Magisk --> phone will be unrooted and all magisk modules will be uninstalled --> OTA update --> flashed the latest magisk patched boot img --> reinstall all magisk modules again =[

any way to keep the magisk modules settings?
[Essential Phone Guides, News, & Discussion] bmg1001:
You should be able to keep modules by: Flashing the BTS (back-to-stock) package for the update you're trying to install (I'm assuming June?), then either flash TWRP, install stock boot image, then flash Magisk, or fastboot flash a Magisk-patched boot image.

Just note that when using the back-to-stock, choose the "no wipe" variant. Also, the flash script might automatically reboot the device when done, so when you see that it is almost done flashing, hold the volume down button so it reboots back to fastboot.
[Essential Phone Guides, News, & Discussion] aer0zer0:
It'll reboot to bootloader
[Essential Phone Guides, News, & Discussion] c19932:
Thank you so much for your help. I really appreciate it. I have several questions if you don't mind. I've been out of the loop for a while .

1) Where can I find the BTS packages? I am assuming you are talking about the OTA packages that we can download from the official website? (https://www.essential.com/developer/current-builds)

2) before I flash the BTS package, do I need to uninstall magisk first?

thanks again
[Essential Phone Guides, News, & Discussion] NaterTots:
I think the BTS they are talking about is in the first post of this thread.

https://xdaforums.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

You'll want to make sure you select, "Don't wipe" if you don't want to wipe all the data on your phone.

---------- Post added at 07:16 AM ---------- Previous post was at 06:47 AM ----------

So, I keep getting an error when trying to get root on the latest P build.

I boot to bootloader

flash TWRP

boot to recovery

install the P Beta boot image into boot

then install Magisk 16.4 zip and it comes up with error 1 and fails when installing the zip.

Am I doing something wrong?

Thanks
[Essential Phone Guides, News, & Discussion] jmkarnai01:
Just make sure when flashing it is on the same slot you flashed p beta to. Also had the problem until I swapped slots.
[Essential Phone Guides, News, & Discussion] shaq1612:
I'm on the new June P update and magisk installs fine but I lose root a few seconds after boot. I've already done it 3 times with the same results using magisk 16.4.
[Essential Phone Guides, News, & Discussion] paulr24:
Same here.
[Essential Phone Guides, News, & Discussion] shaq1612:
so I've done it 6 times now all with that same results the only difference is the length of time it takes to lose root. I was able to stay rooted for a couple hours the last time. By the way flashing the magisk zip doesn't install magisk manager.
[Essential Phone Guides, News, & Discussion] Tautvydas:
Guys, a very noobish question, but I searched the thread and couldn't find it:

On 8.1 June, flashing magisk modules with twrp, requires only "fastboot flash boot twrp.img" command, and once in twrp, I just flash magisk modules, and that's it? No additional files to flash/etc.?

I know, that twrp doesn't remain, and I read somewhere that it's too unstable to keep it (again, sorry for my knowledge).

Just to be on the safe side, since if it would result in bootloop/etc, restoring device again with watch takes a lot of time.

Thanks!
[Essential Phone Guides, News, & Discussion] bmg1001:
While most modules flash fine via TWRP, unless specifically told to do it through TWRP, you should install modules through the Magisk Manager. If you were to reinstall TWRP through fastboot, you'd have to also reinstall the boot image and Magisk itself.
[Essential Phone Guides, News, & Discussion] Tautvydas:
Thing is, with 180611 build from kantjer (one of the latest) there are problems installing bigger size modules such as YTVanced and DIY GCAM MOD .

Example with Vanced, it installs, after reboot it appears on modules (though shows as "no info provided" on all graphs), but the app itself isn't present on app drawer. (prior I removed original YT and it's updates). Install log shows no errors, and I'm not knowledgeable to tell discrepancies from logcat or magisk debug log.

Then, if YTVanced is present, trying to install other modules from magisk just fails - installs with no errors, but after reboot it doesn't appear on modules list whatsoever.

Same thing with GCAM MOD.

Somehow bigger modules screw with whole modules part itself.

So I though about flashing modules directly from twrp, but since, as you've told, basically I'd have to reinstall magisk itself, just leaves me to wait for fixed magisk build.

Anyway, maybe you are using/have magisk build, which does not have these problems and could share it?

Thanks!
[Essential Phone Guides, News, & Discussion] bmg1001:
I've had similar issues myself on the June 3rd build too, actually. I think we'll just have to wait until the bugs are sorted out, unfortunately. YouTube Vanced works for me right now, though I'm not using GCAM or any other big modules, just fonts and stuff like that. Not sure what is causing it, or if it happens for other devices, though I'm sure it'll be sorted out relatively soon.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Go back to beta 16.4. I know your struggles.
[Essential Phone Guides, News, & Discussion] morphius88:
Hey guys,

I remember there was a way to flash an update while keeping root by patching the magisk file or something staying rooted. I cant seem to find it.

I think I might be using wrong search words. Can someone point me in the right direction?

Basically, Im on the 8.1 Beta with the february security patch still, but I would like to move up to the Out of Beta 8.1 (or Android P Beta) while staying rooted and not losing data.

Appreciate the help. Thank You
[Essential Phone Guides, News, & Discussion] bmg1001:
Flash the P preview using the back to stock zips found in the Development section here on XDA, using the no-wipe script, and then flash Magisk right away before booting into the system.
[Essential Phone Guides, News, & Discussion] morphius88:
I have substratum theme running, which I assume would not work on P until the theme supports it. So I think I will stay on 8.1. just dont want to be in 8.1 Beta anymore.
[Essential Phone Guides, News, & Discussion] bmg1001:
Depends on the theme. Most themes for system elements will not work on P, except for a select few that only change small things like the system accents. Themes for third party apps will work fine, though.
[Essential Phone Guides, News, & Discussion] morphius88:
Yea. Mostly system apps. Its a paid theme so I am sure they will eventually have support.

---------- Post added at 07:23 PM ---------- Previous post was at 06:31 PM ----------

Do i flash the stock 8.1 Beta boot image onto my phone, reboot, take the OTA and then Use magisk installer to install magisk, it should ask me to patch the boot image?

I can patch the image, save to the cloud/computer and then flash the patched boot image via fastboot and regain root?

Or am I missing something?
[Essential Phone Guides, News, & Discussion] mhajii210:
Android P beta 1 and root

Guys I'm having the same problem. I've already rebooted numerous times and at first I have root, but after some time it's lost until I reboot. Any solution to this???