yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] mobileman88:
Do try turning on "Core Only mode in Settings" and "MagiskHide".
[Essential Phone Guides, News, & Discussion] freshlysqueezed:
Reinstall magisk from within magisk manager (direct instal). Then reboot
[Essential Phone Guides, News, & Discussion] tech_head:
THIS!

I'm having no issues with eh latest Magisk (16) and the latest manager.
[Essential Phone Guides, News, & Discussion] desarea708:
I'm a little confused. I have a fresh install of 8.1 how do I obtain root from here? Tried the way in the first post and got stuck in a boot loop.
[Essential Phone Guides, News, & Discussion] Ironjim4102:
Did you flash 8.1 stock boot and use the 15.4 magisk? Just checking.
[Essential Phone Guides, News, & Discussion] desarea708:
I used 8.1 stock boot and 15.3 magisk
[Essential Phone Guides, News, & Discussion] Ironjim4102:
Use 15.4 or 16 that should work
[Essential Phone Guides, News, & Discussion] Einril:
Personally I've tried everything: 15.3, 15.4 and 16, each time testing the 2 methods (TWRP without screenlock and patched boot img). It ended up in bootloops everytime. Sometimes it manages to boot, but I get no Wifi and the phone freezes and reboots after 20 seconds.

Could somebody who managed to root successfully post their patched boot img? I'm guessing it should be the exact same for everybody.
[Essential Phone Guides, News, & Discussion] mobileman88:
The rooted images are specific to each individual device it seems.
[Essential Phone Guides, News, & Discussion] Einril:
Oh, strange. I've never heard of a boot image that would be specific to each individual device. Do you know why that would be? An identical hardware with an identical software should not have any trouble booting from the same boot image, unless it's somehow impacted by a unique device parameter, but I can't imagine why. I'm not an expert on Magisk, so maybe I'm missing something.
[Essential Phone Guides, News, & Discussion] mobileman88:
The encryption keys for one plus device ID etc are part of the modified boot image. At least that is what it seems to me when rooting a custom kernel and mucking with its patching process in its install scripts which Magisk does something like it too.
[Essential Phone Guides, News, & Discussion] Einril:
Oh yeah I forgot about encryption. That makes sense then. Thanks!
[Essential Phone Guides, News, & Discussion] mobileman88:
No worries. Actually it is not that hard to use Magisk manager to patch the boot image in your phone then transfer it to your pc for flashing in fastboot
[Essential Phone Guides, News, & Discussion] Einril:
I know. I had no issue with all previous betas, but I just can't seem to root this one without bootloops.
[Essential Phone Guides, News, & Discussion] NaterTots:
Maybe list exactly what you are doing and we could help you more that way
[Essential Phone Guides, News, & Discussion] Einril:
Sure. As explained a couple posts above, I tried 3 different versions of Magisk (15.3, 15.4 and 16), each one with the two methods:

Patch stock OREO_8.1_B1 boot image with MagiskManager

Adb pull the patched boot image

Flash the patched boot image with fastboot

or

Remove all screenlock (fingerprint and pattern)

Flash twrp boot image with fastboot

Reboot into twrp

Flash stock OREO_8.1_B1 boot image

Flash the Magisk installer zip

Each time I ended up with my phone freezing during the boot animation, and rebooting endlessly. I was able to recover it easily by reflashing the stock boot image.
[Essential Phone Guides, News, & Discussion] NaterTots:
What OS are you currently on? Is it a Sprint phone?

I am on 8.1 beta and followed the post from when 8.1 was released with 15.3 and had no issues.

I was on 8.0 beta 3 rooted,

I flashed twrp

Flashed the beta 3 boot img

Took the OTA

And then followed what was listed by reverenddak in post #818 or thereabouts.

Very strange if you're doing that and it's not working.

Maybe try a factory reset and then try again?
[Essential Phone Guides, News, & Discussion] Einril:
I'm on the 8.1 beta 1 and it's an unlocked phone (bought from Amazon).

I guess I'm gonna have to factory reset yeah, I wanted to avoid that as I have a couple of apps (bank and work) that don't survive a Titanium backup restore.

Thanks anyway!
[Essential Phone Guides, News, & Discussion] tech_head:
Try a different cable/USB port.

The process should work.

A reset won't help.
[Essential Phone Guides, News, & Discussion] thehappydinoa:
Ya so I actually had some problems with the OREO-8.1-B1.img provided from this page.
[Essential Phone Guides, News, & Discussion] Einril:
Thank you! I used the patched boot image directly from your git, and it worked. I'm now rooted and everything's working perfectly!
[Essential Phone Guides, News, & Discussion] mobileman88:
When I have had such issues, usually I will flash the Magisk Uninstaller, proceeded by flashing stock boot image to see if it all works ok.

After that, then flash the patched boot. I have never had a bootloop after that with the steps above.
[Essential Phone Guides, News, & Discussion] Alaric323:
Has anyone had any issues installing magisk modules on the 8.1 beta? Keep getting magisk_merge.img mounting failed issues. In the past this has been a kernel issue, but I don't see anyone else having this problem yet.
[Essential Phone Guides, News, & Discussion] mobileman88:
Not at all. But I am only using gcam
[Essential Phone Guides, News, & Discussion] rignfool:
Did you install Xposed...

I had this issue... I blamed selinux and it went away when I removed Xposed...
[Essential Phone Guides, News, & Discussion] Alaric323:
I have not. I was under the impression that Xposed was still in Alpha phase. Trying to install Viper myself (particularly ahrion and zackptg5's revision). Actual error code is as such:

Magisk : mount /dev/block/loop1->/dev/tmp/magisk_img failed with 22: Invalid argument

...shame it doesn't go into more detail about what arguments it uses.
[Essential Phone Guides, News, & Discussion] rignfool:
Hmm...

Maybe try a version that is more specific... Those unity installers could have an issue that your device isn't compatible with... And since the devs don't have it... They may not have seen the error...

Or you could submit logs to them and see what they say...

[MENTION=6037748]Zackptg5[/MENTION] is pretty good about suggestions and bug squashing
[Essential Phone Guides, News, & Discussion] Zackptg5:
Next release will have sepolicy fix for essential phone. Could you post the log on the v4a thread? Try uninstalling and reinstalling magisk cause that error isn't mod specific (it uses the regular magisk util_functions like any other magisk module)
[Essential Phone Guides, News, & Discussion] Alaric323:
The same module worked during Oreo Beta 2. This isn't an issue with this specific module; all modules I'm attempting to install have this issue. I've unrooted and rerooted, and the problem persists.

Wonder if it's connected to my inability to install BusyBox.

I would attempt to flash Viper in TWRP, but we don't have a persistent version of it yet for Oreo, nor does it have access to the system partitions...
[Essential Phone Guides, News, & Discussion] Alaric323:
Attached is the error that appears when attempting to install the plugin. (This is an older plugin version, the latest is 1.5.2, but the error is still identical.)

Install Log:

- Copying zip to temp directory
- Installing ViPER4Android_FX-v1.5.1.zip

Unzipping files...
Archive: /data/user/0/com.mt9K.tu.sQzM2TkU/cache/install.zip
inflating: .gitattributes
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: README.md
inflating: common/install.sh
inflating: common/keycheck
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
inflating: common/uninstall.sh
inflating: common/unityfiles/addon.sh
inflating: common/unityfiles/modid.sh
inflating: common/unityfiles/util_functions.sh
inflating: config.sh
inflating: custom/Old/ViPER4AndroidFX.apk
inflating: custom/Old/libv4a_fx_jb_X86.so
inflating: custom/Old/libv4a_fx_jb_arm.so
inflating: custom/ViPER4AndroidFXMaterial.apk
inflating: custom/libv4a_fx_jb_X86.so
inflating: custom/libv4a_fx_jb_arm.so
inflating: module.prop
inflating: system/app/ViPER4AndroidFX/ViPER4AndroidFX.apk
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA

*******************************************
* ViPER4Android FX *
*******************************************
* v1.5.1 *
* by ahrion, zackptg5 *
*******************************************

- Mounting /data, /cache
- Magisk install detected
- A/B partition detected, current slot: _a
- Mounting /system, /vendor
- Device skip_initramfs detected
- Creating /data/adb/magisk_merge.img with size 64M
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
- Mounting /data/adb/magisk_merge.img to /dev/tmp/magisk_img
! /data/adb/magisk_merge.img mount failed...
Failed!
! Installation failed

Magisk Log:

06-09 13:25:51.217 622 696 I Magisk : * Starting MagiskHide
06-09 13:25:51.217 622 696 I Magisk : hide_utils: Hiding sensitive props
06-09 13:25:51.217 622 696 I Magisk : hide_list: [com.google.android.gms.unstable]
06-09 13:25:51.231 622 696 I Magisk : hide_list: [com.aniplex.fategrandorder.en]
06-09 13:25:51.242 622 696 I Magisk : proc_monitor: init ns=mnt:[4026531840]
03-01 21:57:20.244 622 1173 I Magisk : ** late_start service mode running
03-01 21:57:20.244 622 1173 I Magisk : * Running service.d scripts
03-01 21:57:20.244 622 1173 I Magisk : * Running module service scripts
03-01 21:57:20.690 622 696 I Magisk : proc_monitor: zygote ns=mnt:[4026533873] zygote64 ns=mnt:[4026533897]
03-01 22:05:50.508 4212 4212 E Magisk : read failed with 104: Connection reset by peer
03-01 22:05:50.512 4212 4212 W Magisk : su: request rejected (10285->0)
03-01 22:06:50.289 6049 6049 I Magisk : Create /data/adb/magisk_merge.img with size 64M
03-01 22:06:50.505 6051 6051 E Magisk : mount /dev/block/loop1->/dev/tmp/magisk_img failed with 22: Invalid argument
[Essential Phone Guides, News, & Discussion] jAm-0:
Could somebody please post the modified boot.img for the latest Lineage 15.1 for me? or is it device dependent
[Essential Phone Guides, News, & Discussion] convolution:
Hi, how do we install the stock boot image? is the command fastboot flash system system.img?

Also, for me to understand the steps:

Step 1 is to get a custom recovery, TWRP.

Step 2 -> ????? Why do we need to flash the stock image again?

Step 3: Install magisk via TWRP? Flash the .zip file right?

Thanks for helping me out.
[Essential Phone Guides, News, & Discussion] spotmark:
The command is fastboot flash boot boot.img

The reason you need to flash it is because TWRP is also installed as boot.
[Essential Phone Guides, News, & Discussion] convolution:
I think I destroyed my phone. Recovery is corrupt. I can't boot into android either. But my phone can still do fastboot and is recognized in fastboot.

What now?
[Essential Phone Guides, News, & Discussion] spotmark:
See if you can still install TWRP. If so, just boot into TWRP and reflash the ROM.
[Essential Phone Guides, News, & Discussion] convolution:
So I managed to get twrp working...

Where do I get the stock image file? EDIT: I found em... but I can't find NMK24B

I'm assuming the stock image would be in zip form. I'd drag the zip image file as well as magisk into the phone, get twrp up, flash the image.zip and magisk.zip, and i'm good to go?

I tried downloading the image.zip file from essential website, and it's a no go.
[Essential Phone Guides, News, & Discussion] spotmark:
It's all written down for you in the first post of this thread.
[Essential Phone Guides, News, & Discussion] convolution:
Thanks.

Does anyone know if I do OTA updates, will I lose root/twrp?

Thanks.
[Essential Phone Guides, News, & Discussion] spotmark:
You won't be able to take OTAs if you're rooted. As I stated, TWRP is installed as a boot image, so you lose it as soon as you flash a new ROM or root your phone.
[Essential Phone Guides, News, & Discussion] jAm-0:
I cant get the boot.img to show up in twrp but the magisk zip shows up fine.

Do I flash the boot image in fastboot?
[Essential Phone Guides, News, & Discussion] Ironjim4102:
Bottom right where it says install zip. Tick that and it will.say Install image. Then tick again and you can install your zip
[Essential Phone Guides, News, & Discussion] jAm-0:
Thanks for that, must have missed it!

Well I'm impatient and incompetent so I flashed the boot.img via fastboot and sent the phone into bootloops. Managed to get into recovery and flash Lineage again so at least my phone is up and running. Question, did the lineage revert the boot.img back or do I still have the patched 8.1b img? Thanks!
[Essential Phone Guides, News, & Discussion] Ironjim4102:
Ya it did. Just have to flash your boot.img Everytime. Then flash say kernel then Magisk. If you flash rom reboot first set up etc. Then fastboot TWRP again flash boot.img for that ROM then kernel or whatever then Magisk.
[Essential Phone Guides, News, & Discussion] jAm-0:
Roger that! Thanks for the help.

Quick question, do we have a patched boot.img for the latest lineage? I tried to extract myself without much luck.

EDIT: Well now its hard bricked, no fastboot, no recovery just stuck on the splash screen.

My own fault for not knowing enough about the dual partition system to mess around with
[Essential Phone Guides, News, & Discussion] Ironjim4102:
I'm not sure. I'm sure someone in here does though.
[Essential Phone Guides, News, & Discussion] jAm-0:
I've asked around without much luck. Ill keep searching
[Essential Phone Guides, News, & Discussion] Arju:
my recommendation is for you to use this boot image (patch it to get magisk). https://xdaforums.com/essential-phone/development/kernel-lineageos-15-1-upstream-builds-t3754202

This kernel is basically stock lineageOS kernel with upstream fixes. Have a read through the first post of that thread and you'll understand a bit more.
[Essential Phone Guides, News, & Discussion] jAm-0:
Right now im in the process of restoring the system image.

From there flash twrp > lineage

Then I flash his custom kernel boot img

Use Magisk manager to patch his img and flash that to boot

Or can I flash the patched boot.img initially?

WILL THIS WORK LOL its been a two day task (granted im pretty novice, Im still figuring out how this dual partition works.

PS Will I need to fastboot -w at all during this process, I'm still learning when thats necessary

Well my bootloader or w/e must be corrupt because no matter what I do it only works maybe 1/50 times. No recovery or nothing. I've even flashed the stock images via fastboot about 20 times WHEN I CAN EVEN GET INTO FASTBOOT.

I have no idea what the problem is, maybe I'll look for a bootloader and flash that, I'm out of knowledge/patients

Thanks again
[Essential Phone Guides, News, & Discussion] Arju:
- restore system image. Boot into system.

after that you could go into the bootloader menu on phone and hook it up to your computer and just to be safe type in fastboot -w at this point.

Use this installation instruction here (taken from the AOSiP thread):

boot into fastboot

fastboot flash boot twrp-mata_11.img

boot twrp

wipe system/data/cache

flash rom

- boot into system

- Go into the magisk thread (google it) and download the magisk apk and install it.

- Go into the thread I shared with you and download the latest boot image found there and follow the instructions on that thread on how to patch it with magisk.

- send the patched boot image to your computer.

- fastboot flash the patched boot image.

- Now you should have magisk up and running.

Make sure you have all the files you need before hand to make it all easier.
[Essential Phone Guides, News, & Discussion] jAm-0:
Thanks again for all you're help, but my issue arises before I even have a chance to do any of this. The bootloader barely allows me to get anything done; bootloops, barely can get into recovery, difficult to even boot into the phone.

And know the factory images/twrp are failing to flash on the partitions, I have no idea whats happening

So my question is should I try to flash a different bootloader to maybe help with these issues

Also Im unsure what you mean about the bootloader menu in phone
[Essential Phone Guides, News, & Discussion] Arju:
This is how you get into the bootloader menu: https://www.androidexplained.com/essential-phone-fastboot-mode/

Once there you can use the fastboot commands on computer. after you fastboot flash twrp you should use the volume keys on the phone to toggle until you get to recovery. when it says recovery on the top instead of start then press the power button.

Have you restored system image prior to getting here?
[Essential Phone Guides, News, & Discussion] jAm-0:
I am capable of doing everything I need to do to get magisk running on LOS. My only problem is the bootloader isn't allowing me to get anything done. It wont boot into recovery, it wont power the phone down and it will only bootloop. I've restored the factory images via the system dumb back to stock thread.

Fastboot is all I'm able to gain access to, and know its failing to flash to the boot partitions. I think I have a faulty device.

Im getting this issue while flashing

FAILED (remote: Error flashing partition.)
[Essential Phone Guides, News, & Discussion] mobileman88:
You will need to unlock flashing in fastboot. Do note this action will do a full wipe of your device
[Essential Phone Guides, News, & Discussion] jAm-0:
My phone is already unlocked
[Essential Phone Guides, News, & Discussion] Arju:
Try this.

Go into bootloader and start up fastboot on your computer.

Type in: fastboot -i 0x2e17 devices

tell me now what happens on the computer screen. Is your computer able top recognize a fastboot device?

Edit: (sorry iforgot the letter s in devices. try the above fastboot command and let me know if your computer recognizes you device.)
[Essential Phone Guides, News, & Discussion] jAm-0:
I will as soon as it turns on. I think I hard bricked it for good this time. :(
[Essential Phone Guides, News, & Discussion] Arju:
Crossing my fingers you didn't . Just tag me after you tried that command. If nothing happens then try fastboot devices -i 0x2e17

If either one of those works then we're on right track. If not then your bootloader might be toast. Your phone ain't bricked until you can't turn it on so just take a deep breath and relax ;)
[Essential Phone Guides, News, & Discussion] jAm-0:
I cant turn it on
[Essential Phone Guides, News, & Discussion] Arju:
Dang... What happens when you plug it into to the charger? could it be that the battery is drained?
[Essential Phone Guides, News, & Discussion] jAm-0:
Nothing at all, not even led

Super bummed, saved up for that phone and had it maybe a week. Well ya live an learn i guess,
[Essential Phone Guides, News, & Discussion] Arju:
Sorry to hear. I'll ask around in the Essential discord chat where a lot of xda members hang around. Maybe someone there knows what to do. I'm out of ideas at this point. Can only help if you manage to get into bootloader mode.

try step 2 and 3: https://thedroidguy.com/2017/09/essential-ph-1-wont-turn-troubleshooting-guide-1075935 to see if it turns on.
[Essential Phone Guides, News, & Discussion] jAm-0:
Hey man I appreciate all your help really!

But this phone is done, just going to have to live with my mistakes
[Essential Phone Guides, News, & Discussion] NaterTots:
What USB cable were you using to connect to your PC?
[Essential Phone Guides, News, & Discussion] jAm-0:
standard samsung usb c cable
[Essential Phone Guides, News, & Discussion] Arju:
Do you know your battery level prior to death?... plug it into the charger and let it stay for an hour or so and then test the multi key combinations to see if it wakes up. Could be that it drained itself.
[Essential Phone Guides, News, & Discussion] robertbarber:
I am wondering if each build of CandyROM, which is the ROM i am using, has the boot.img available for download for each build done how much can I shorten the list thats in the first post for rooting the phone. All I would need to do from reading this thread, and please let me know if I am wrong, is go through the steps to install the ROM and do initial setup. Make sure the lockscreen lock is set to none and then go back and flash twrp and the boot image and then magisk and reboot. For those who want to check out CandyROM you can find the builds for the Essential phone here https://download.bbqdroid.org/

Update: was able to flash the boot.img from where the ROM is and Magisk in TWRP and it worked just fine for me. Now I am rooted.
[Essential Phone Guides, News, & Discussion] dchurch85:
Not sure what's going on, but I can't get root to stick.

I am on the 8.1 beta. I downloaded the stock file for it, rebooted to bootloader, flashed twrp, in TWRP I flashed the stock file, then magisk. Once I reboot, root checker and magisk manager show not rooted.

I'm just trying to get the google camera ported over. If there is an easier way to do this, let me know. I downloaded magisk manager from their website and used the most current magisk file from their app.

Also, where do I get the magisk camera modules? Thanks in advance
[Essential Phone Guides, News, & Discussion] Airgio:
i've got the first beta build of Oreo 8.1. If i root my Essential, can I receive new OTA build updates?
[Essential Phone Guides, News, & Discussion] NaterTots:
Not directly. You'll have to flash the stock boot image for the build you are on before taking the OTA.
[Essential Phone Guides, News, & Discussion] bmg1001:
Sometimes, Magisk will not install after the first reboot, but it should by the second. If it still doesn't work, try patching the stock boot image using the Magisk Manager and then flashing the patched boot image from within fastboot. Also, the magisk camera modules are available in the Themes and Mods section for this device here: https://xdaforums.com/essential-phone/themes/magisk-based-gcam-port-ar-sticker-t3730837/page66
[Essential Phone Guides, News, & Discussion] dchurch85:
Awesome got it working, thank you.

Anyway you hide root now? My corporate email won't sync now that I'm rooted.
[Essential Phone Guides, News, & Discussion] tech_head:
What application?

Magisk should be able to hide from anything.
[Essential Phone Guides, News, & Discussion] dchurch85:
That's what I thought, but it isn't.

The 2 apps are container and boxer
[Essential Phone Guides, News, & Discussion] dchurch85:
I went into the magisk settings and selected to hide magisk, when I log in to those apps it still says compromised and can't be used...
[Essential Phone Guides, News, & Discussion] noob5ever:
Apologies if this is a dumb question (username is relevant) but do I need to perform the "critical" bootloader unlock to achieve root via this method?

In preparation for rooting, I unlocked the "standard" bootloader last night, wiped phone etc, then reinstalled everything thinking I probably wouldn't need to perform another wipe before I got root + titanium backup running. From what I've read, the "critical" unlock wipes the phone as well.

thanks
[Essential Phone Guides, News, & Discussion] bmg1001:
For root, you don't need to unlock critical, though you probably should anyway, in the rare case that you may have to flash a back-to-stock zip. Also, yeah, the critical unlock wipes the phone as well.
[Essential Phone Guides, News, & Discussion] noob5ever:
Thank you for the reply, looks like I'll wipe 'er again and start over, better safe than sorry!

And huge props for this guide bmg1001 :good:
[Essential Phone Guides, News, & Discussion] tech_head:
Have you manually hide them, tried core only mode and hide magisk manager?
[Essential Phone Guides, News, & Discussion] dchurch85:
Boom! I didn't hide those apps, just clicked the hide magisk from detection setting. Working now. Thank you!
[Essential Phone Guides, News, & Discussion] crixley:
How is this ROM? Any bugs?