yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] reverenddak:
I forgot about this method. It works great. Detailed instructions can be found here: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Skips the whole TWRP part, and thus skips a whole reboot. I also find that all my previous Magisk installs are reinstalled.

---------- Post added at 05:34 PM ---------- Previous post was at 05:28 PM ----------

Also occurred to me. Wouldn't the *patched_boot.img* be identical for all devices (assuming the same phone/build)? Essentially allowing folks to skip the process of patching the boot image, and going straight to flashing a shared image? Or are the unique identifiers, etc., that require you to patch then flash your own?
[Essential Phone Guides, News, & Discussion] mobileman88:
So no need to remove all my patterns /fingerprints if I use this method?

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

wow... this sounds much safer. i won't need to delete my patterns and fingerprints then

---------- Post added at 09:50 AM ---------- Previous post was at 09:49 AM ----------

This sounds like a much better way to get it rooted honestly
[Essential Phone Guides, News, & Discussion] reverenddak:
A working custom recovery would be the best. I have no clue if anyone is even trying. I know that it has something to do with A/B partitions, but they seemed to have solve it for Pixels, so... I dunno. Could also be that there are 1000 times more pixels out there than PH-1s.
[Essential Phone Guides, News, & Discussion] tech_head:
There is a working TWRP, but not for Oreo.

The Essential needs boot patched because there is no recovery. So until you have a release that isn't beta, why bother?
[Essential Phone Guides, News, & Discussion] thehappydinoa:
Ok so my phone is being really annoying. I sideloaded 8.1 today and when I got to root it, it gets stuck on boot. Help please.
[Essential Phone Guides, News, & Discussion] Genghis1227:
Nobody tried this? [emoji58]
[Essential Phone Guides, News, & Discussion] dayh8:
I've been trying but my update keeps failing.
[Essential Phone Guides, News, & Discussion] Genghis1227:
Are you able to at least get back into the OS?
[Essential Phone Guides, News, & Discussion] dayh8:
I'm trying to do it all in the OS like the guide suggests should be possible, but about 4/5 of the way through Step 1 of the install it says the update failed. I've tried it about ten times. Not sure what the issue is, but at least for this update that method is not viable.
[Essential Phone Guides, News, & Discussion] Genghis1227:
Did you do the restore images in magisk before you tried the OTA? That may cause it to fail because it doesn't recognize the patched boot.
[Essential Phone Guides, News, & Discussion] dayh8:
Yes, but I'm going to try again after a reboot.
[Essential Phone Guides, News, & Discussion] Genghis1227:
Let me know!
[Essential Phone Guides, News, & Discussion] dayh8:
Negative. Not happening.
[Essential Phone Guides, News, & Discussion] Genghis1227:
Ok I guess

1. Remove lock pattern

2. Load TWRP temporarily

3. Sideload OTA VIA TWRP

4. Install boot image

5. Flash magisk

6. Reboot into system
[Essential Phone Guides, News, & Discussion] return.of.octobot:
I'm a little hesitant to follow through with the in-app boot image patch. The patched output is nearly 1/3 the size of the stock image I fed into Magisk Manager (22MB vs. 64MB). This can't be normal.. can it? Is something wrong here or is Magisk Manager just compressing the **** out of the image?
[Essential Phone Guides, News, & Discussion] Genghis1227:
Ok so this is what I did:

1. Remove lock pattern

2. Load TWRP temporarily

3. Sideload OTA VIA TWRP - Get the full OTA version https://storage.googleapis.com/essential-static/PH1-OTA-OPM1.180104.010.zip - Should be about 1 GB

- In TWRP, basically just install like you would install a normal zip...took a while but be patient

4. Install boot image

5. Flash magisk - I didn't realize that there is a 15.4 version...get that one... I had issues with 15.3

- For some reason when I flashed magisk each time it said that it could not mount /system...not sure what that was all about but after installing 15.4 it worked. I had to do the UninstallMagisk zip and then try again with 15.4 btw.

6. Reboot into system

It took a while for the initial boot...walk away. Then I saw it boot into the OS and saw the notification that Android system was upgrading. :)
[Essential Phone Guides, News, & Discussion] tech_head:
Yes, that's normal.

Same sizes for me.

I didn't even bother looking at sizes because I could always go back.
[Essential Phone Guides, News, & Discussion] return.of.octobot:
True enough, thanks though, it's definitely reassuring to know that before taking the plunge regardless.
[Essential Phone Guides, News, & Discussion] reverenddak:
OTA worked for me, was rooted (Magisk) and Oreo Beta3.

Lost root, but everything else worked fine.

Decided to Root because I wanted the GCam via Magisk because I know it works. I'm going on a trip and want to compare cameras.

I went the way I shared earlier, skipping TWRP and just downloading the 8.1b1 boot image onto phone.

Used MagiskManager to patch the bootloader.

uploaded the patchedboot.img to cloud

downloaded to PC

boot ph-1 to fastboot

fastboot flash boot patchedboot img (not exact code)

reboot

everything working fine

re enabled Magisk hide

all my previous magisk modules were reinstalled automatically

didn't have to disable lockscreen

didn't have to wipe or reset

everything working like a normal update

only had to re root because I wanted to

---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------

agree, file was smaller. but installed fine. rooted and booted fine.. using my phone right now.
[Essential Phone Guides, News, & Discussion] scottfreeze:
I'm seeing the same thing. Originally took the OTA, but flashing the twrp img failed with the same error message you saw. Then sideloaded the 8.1 image from the Essential Developers site, tried again, same thing. Tried rooting by flashing the Magisk patched boot image, same max download size error when trying to flash.

Running "fastboot getvar all" returns

all:

finished. total time: -0.000s

Digging a little deeper, I found that trying to set the current slot manually with command "fastboot --set-active=_a" gives this output:

Warning: Device A/B support is outdated. Bootloader update required.

error: Device does not support slots

My bootloader version after updating to 8.1 is mata-8a1a76e. Can someone who successfully rooted confirm that this is the correct version? Does anyone have any suggestions what I should try next?

Edit: Success! Flashed the boot partition from the 8.1b1 system dump thread (https://xdaforums.com/ess...mj20d-t3701681), which flashed successfully, then immediately flashed the Magisk patched boot image that I had previously prepared according to the instructions in post #787 of this thread.
[Essential Phone Guides, News, & Discussion] Seamonkey79:
I have the same bootloader version showing
[Essential Phone Guides, News, & Discussion] thehappydinoa:
I tired all the methods

I tired all the methods mentioned above a none of them allow me to get passed the boot animation... I tried installing a pre-patched image, I tried magisk uninstall, I tried installing magisk normally through twrp with magisk zip. Nothing is working so far.

I also have the same bootloader version: mata-8a1a76e
[Essential Phone Guides, News, & Discussion] Genghis1227:
Going to have to give this a try next time. I'm unrooted for the time being.
[Essential Phone Guides, News, & Discussion] runderekrun:
Did you have to flash the stock boot image for 8.0 before taking the OTA?
[Essential Phone Guides, News, & Discussion] Seamonkey79:
I thought I'd made some progress. I tried a factory reset, which didn't help, and then a fastboot -w.

Fastboot -w returned:

wiping userdata...

Erase successful, but not automatically formatting.

Unable to get partition size

FAILED (remote: unknown command)

erasing 'userdata'...

FAILED (remote: Check device console.)

finished. total time: 0.004s

It did allow me to send a fastboot --set-active=_a:

Setting current slot to 'a'...

FAILED (remote: unknown command)

finished. total time: 0.003s

However, sending fastboot --set-active=_b:

Setting current slot to 'b'...

OKAY [ 0.165s]

finished. total time: 0.166s

Didn't change any other fastboot commands, though, and now --set-active=_a returns the bootloader needs update error again.
[Essential Phone Guides, News, & Discussion] NaterTots:
I was on Oreo Beta 3 with root.

I flashed the OB3 boot.img through twrp

Rebooted and took the OTA

Then followed everything reverenddak listed in his post and back up and running with root.

Thanks. It was easy peasy.
[Essential Phone Guides, News, & Discussion] reverenddak:
nope. the OTA automatically does it for you, it's why you lose root.
[Essential Phone Guides, News, & Discussion] MoistPicklez:
I had similar issues when I was using Minimal ADB v.1.4.3, tried every USB slot, all commands issued returned errors, however, I downgraded Minimal ADB to v.1.4.2 and all my commands were working again. Go figure. Maybe try that?
[Essential Phone Guides, News, & Discussion] Seamonkey79:
Good thought. I went ahead and 1.4.1, 1.4.2, 1.4.3, to no avail. I had initially used the set directly from Essential as well, so that's 4 adb/fastboot versions that haven't worked now :-\
[Essential Phone Guides, News, & Discussion] MoistPicklez:
****, and I'm guessing you tried all the USB ports available? Maybe try a reboot on both Comp and phone, get back to bootloader and give it another shot with a different USB port then before?

It took me a good hour to finally get 'fastboot -w' to wipe properly, then flashed the 8.1 Beta last night, not sure if Minimal ADB was to blame, could've just been the PC I was using.
[Essential Phone Guides, News, & Discussion] GospelNerd:
I can confirm, the Magisk patched boot.img was much smaller as [MENTION=6474612]return.of.octobot[/MENTION] reports. But, I didn't hesitate, and went ahead and flashed. All seems good so far.

Also, I followed [MENTION=4344712]reverenddak[/MENTION] 's steps except instead of uploading to cloud and downloading to PC, just use "adb pull /storage/emulated/0/MagiskManager/patched_boot.img" .. Same results for me. Magisk Modules re-installed, Magisk Hide settings all good. SafetyNet checks out. :good:
[Essential Phone Guides, News, & Discussion] Seamonkey79:
Tried a number of USB ports on my main system, none of them were any different. Went to my old desktop and tried using its USB2 ports (my new system is all 3/3.1) and it wouldn't even return an error for anything, just sat there like there wasn't really a device on the other end, though it showed fine for fastboot devices and ADB worked okay.
[Essential Phone Guides, News, & Discussion] vergilbt:
We all in the same boat?

Can't flash twrp after I did an update to beta 8.1

Seems like no solution to get root in this state?

Have we go back to beta3 8.0 and flash first twrp, then 8.1- image and at least Magisk and root stuff?
[Essential Phone Guides, News, & Discussion] runderekrun:
I tried the patched boot.img method and my phone wouldn't boot afterwards. What I am guessing is that it is still trying to load my xposed magisk module for 8.0 Oreo. Anyone know how to stop that from loading? I flashed stock boot.img so I am back up and going (not rooted).
[Essential Phone Guides, News, & Discussion] Seamonkey79:
We might be able to flash back to the latest 7.1, I'm downloading that right now. Thinking (hoping) flashing that and then updating to the beta will move it through.

Edit -

fastboot won't work still, so flashing back to 7.1 is a no-go. I downloaded the firmware from the LOS FAQ link on mega, but again, fastboot won't flash anything, it sits with a 'waiting for device' or the same too large error.

To be honest, while I would like to have root, at this point I'm concerned that when 8.1 final is released, I won't be able to take it because the bootloader is all messed up. I know the update app doesn't flash things the same way, but if the a/b partitions aren't working properly, what will happen when it tries to update the inactive partition with Final...
[Essential Phone Guides, News, & Discussion] NaterTots:
Why don't you just do root through magisk?

It worked really well and I think twrp will work as long as you remove your PIN and fingerprint to unlock beforehand in settings/security
[Essential Phone Guides, News, & Discussion] MoistPicklez:
Very odd with the fastboot troubles, after the PC I used sorted itself out, I had no problem flashing Beta 8.1, setup, flash TWRP, proper boot.img, and finally Magisk. However I did go through an hour or so of errors.
[Essential Phone Guides, News, & Discussion] runderekrun:
I fixed this by using mount-magisk.zip ( https://xdaforums.com/apps/magisk/collection-magisk-modules-t3445257 ) and going into TWRP and deleting xposed module.
[Essential Phone Guides, News, & Discussion] scottfreeze:
Got it working! Here's what worked for me. I flashed the boot partition from the 8.1b1 system dump thread (https://xdaforums.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681), which flashed successfully, then immediately flashed the Magisk patched boot image that I had previously prepared according to the instructions in post #787 of this thread.
[Essential Phone Guides, News, & Discussion] vergilbt:
Maybe I'm little bit blind, but which steps I have to go according root by Magisk?

EDIT: got it. post 787 was the trick!

thanks a lot to all in this community
[Essential Phone Guides, News, & Discussion] Seamonkey79:
Tried that. Mine still says download size not reported, then errors. Trying the flash-all right now, but it's saying that the A/B partitions are gunked up so it needs a bootloader update.
[Essential Phone Guides, News, & Discussion] scottfreeze:
Just in case it makes a difference, I used fastboot from the SDK platform tools found here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

I had previously been using the Minimal ADB and Fastboot tool, and there were definitely differences between them while I was troubleshooting this issue.
[Essential Phone Guides, News, & Discussion] thehappydinoa:
Ya so I tried all previous mentioned methods and I am able to boot into 8.1 but when I try to patch with magisk manager or with the zip it gets stuck in a boot loop...
[Essential Phone Guides, News, & Discussion] Seamonkey79:
Well, it seems the magical combination was a different computer with a different USB cable and the Google-sourced adb/fastboot files.

I tried a number of minimal with no luck, and even went through 4 USB cables. In the end the combination ended up being a USB3.1 port with the 2nd of two Anker USB3 USB-A to USB-C 3.3m cables.

---------- Post added at 05:16 PM ---------- Previous post was at 05:09 PM ----------

After spending almost 6 hours today trying different combinations of things, I would strongly suggest checking with a different, USB3, USB-A to USB-C cable in a USB3.1 port (USB3 might work, my combo was with a 3.1).
[Essential Phone Guides, News, & Discussion] cas239:
Any ideas why this won't work for me? Still getting stuck at an endless boot
[Essential Phone Guides, News, & Discussion] tech_head:
Have you been able to just get 8.1 installed and boot without root?
[Essential Phone Guides, News, & Discussion] cas239:
Yep. Sideloaded through ADB just fine. Everything booted and ran great. When I try to root with Magisk, it hangs when booting. When I sideloaded the stock boot image through ADB Fastboot, the phone boots up just fine
[Essential Phone Guides, News, & Discussion] jonzou:
would you help me with the detail steps please?

1. fastboot flash boot twrp.img

2. in twrp, flash boot.img

3. flash magisk.zip

4. flash Mount_magisk.zip

5. in twrp file manager, goto /magisk

what files should I delete or modify to bypass my old xpose modules?

thanks
[Essential Phone Guides, News, & Discussion] runderekrun:
Yeah so once you flash mount_magisk.zip in the file manager there will be folders in /magisk. Go into the folder of xposed or whatever module you think is keeping you from booting and hit the icon in the lower right and then on the next screen hit delete. They are clearly named.
[Essential Phone Guides, News, & Discussion] contagous:
Hmm i'm also boot looping after just doing the following:

1. fastboot flash boot twrp.img

2. in twrp, flash boot.img

3. flash magisk.zip

If i then reflash stock 8.1 boot it boots no problems, no magisks module are installed

Any ideas?

*Update*

I flashed the Magisk patched boot IMG and everything booted fine and its rooted. I would suggest this method for anyone that got stuck in a loop.
[Essential Phone Guides, News, & Discussion] jonzou:
turn out my problem was not xposed modules, my slot a is working, thank you for the help
[Essential Phone Guides, News, & Discussion] Ironjim4102:
Updated withe no issues. Re-rooted with. Magisk 15.4.

I have seen these issues before. One dumb little thing I forgot to do once was to check USB and file transfer. Then my pc recognized phone I fastboot.
[Essential Phone Guides, News, & Discussion] scottfreeze:
Question: In the early days of this device and this thread, it seemed like the TWRP port was being updated pretty regularly, and then those updates just stopped at v11. Is there a technical reason why no further updates are possible, or is it just that whoever was working on it found better things to do with their time?
[Essential Phone Guides, News, & Discussion] thehappydinoa:
Ya, that was my problem.

---------- Post added at 04:09 PM ---------- Previous post was at 04:08 PM ----------

Ya, I had the same question.
[Essential Phone Guides, News, & Discussion] paulr24:
I'm so confused right now. Here are the steps I have taken:

-removed Substratum theme, unrooted via Magisk, OTA updated to 8.1 Beta 1, booted up and everything was working for the past day

-installed TWRP, flashed OREO-8.1-B1.img, flashed Magisk 15.3, rebooted, got stuck in bootloop

-tried [MENTION=1736723]runderekrun[/MENTION]'s solution of using mount-magisk.zip and deleted all of my module folders from the /magisk folder (left all non-module folders intact)

-rebooted and it got as far as showing my wallpaper but then said "factory data reset... restarting" and took me to the black factory reset screen with tiny text that only allows the options of retry or factory reset

-I hit retry and the same thing happened

-went into TWRP and tried swapping between partitions A and B and rebooting (to be honest I don't 100% understand the partition stuff)

-eventually I was able to get to where the phone booted up but it's in the weirdest state right now. I can navigate around somewhat like normal except if I pull down the notification shade it only pulls down like the first level and not fully if that makes sense. Hitting the settings button in the notification shade does nothing, so I can only get to settings via the settings app in the app drawer. The "previous apps" button doesn't work at all, and neither does the home button so if I open an app and then want to go back to the home screen I need to hit the "back" button.

Anyone have any idea wtf happened here and how I can fix this? Thanks!
[Essential Phone Guides, News, & Discussion] morphius88:
This worked on the first try for me. No twrp but not really needed atm. Thank You
[Essential Phone Guides, News, & Discussion] tech_head:
Because to have TWRP for this phone you need to modify the boot image.

There is no separate recovery.

So there is a version that works on the released OS.

There is no version for the Beta versions of Oreo.
[Essential Phone Guides, News, & Discussion] runderekrun:
Damn dude. I think it's time to cut your losses and format /data.
[Essential Phone Guides, News, & Discussion] paulr24:
Yeah that's the direction I'm heading right now. I'm wondering if the weird behavior I experienced is similar to what I used to see happen sometimes where I'd get constant "system UI has stopped" notifications and would have to factory reset. Maybe changes in Oreo have made it so when the UI is royally screwed you can still actually navigate around to some extent? I don't know, but if that's the case it's not a bad thing since I was at least able to backup everything I wanted to before doing the factory reset.

Now I'm a little weary of flashing Magisk again since I don't think I really did anything wrong to cause the weird issues...
[Essential Phone Guides, News, & Discussion] manaox2:
I had this state happen to me on Nougat. I had to format data and reset to stock before starting over to fix it. My A and B slots didn't match up or something pretty much. Cool thing was for a little while I could reboot to TWRP recovery without having to flash it. Don't think it's an Oreo thing. Pretty sure not going to mount in TWRP and checking system before flashing magisk had something to do with it and then using the super bugged magisk that was out for a few months filled up my storage with logs and caused the system to get corrupted beyond a simple fix.
[Essential Phone Guides, News, & Discussion] jhill110:
There's an app in the play store called toast source. When you get a system UI has stopped you can use it to see which app is causing the issue.
[Essential Phone Guides, News, & Discussion] cas239:
Fyi to those who are having issues with bootloops after trying to root on 8.1, doing a factory reset worked for me. Rooted with the patched boot image and phone booted right up
[Essential Phone Guides, News, & Discussion] Genghis1227:
For anybody that it's wondering how to take the OTA with magisk here are the steps that I found that worked cleanly without the need to load TWRP.

Uninstall magisk mods

Uninstall magisk

Flash stock boot.img (fastboot flash boot boot.img)

Reboot (fastboot reboot)

Take OTA

Reboot

Download stock boot.img

Install magisk manager (if not installed)

Patch stock boot.img using magisk manager

Pull patched_boot.img to computer

Flash patched boot image in fastboot (fastboot flash boot patched_boot.img)

Reboot (fastboot reboot)

Check root and safetynet

Load magisk modules
[Essential Phone Guides, News, & Discussion] 12paq:
Not sure what you mean by "There is no version for the Beta versions of Oreo."

We have been using TWRP on all 4 Beta versions of Oreo. TWRP gets over written if you flash any form of a boot.img, but it's easy enough to fastboot flash it back on again.
[Essential Phone Guides, News, & Discussion] gk1984:
I haven't had any issues rooting with Magisk by fastbooting a patched boot image. But since TWRP can't decrypt the 8.1 beta, I'm concerned about Magisk Modules that can cause a bootloop. In the past, you could flash Magisk Mount and place an empty file titled remove (or delete) or titled disable in the root of the module to remove or disable the magisk module during boot. Is there another way to do this without TWRP or is a factory reset the only option?

I haven't encountered this yet, but I did have a scare with a module causing the phone to take longer than usual to boot. It got me thinking about this. What would I do?
[Essential Phone Guides, News, & Discussion] RawSlugs:
safetynet failed

im on oreo beta 8.1 i installed magisk and im still failling the safetynet test. what can i do to fix this?
[Essential Phone Guides, News, & Discussion] bmg1001:
The only thing TWRP can't decrypt is /sdcard. You can still use Magisk Mount and everything else normally. If you want to flash something, you can also simply use adb push to push the zip to something like /data/media/ and flash from there. You just can't flash or view files on /sdcard.

As for the patching the boot image method, I'll probably update the thread sometime this week. Usually patching the boot image caused problems in the past, with side effects like a broken SafetyNet, but now that it seems it is working fine, there isn't much of a need to go through the whole process I have in the OP now.
[Essential Phone Guides, News, & Discussion] shooterlgk:
Anybody have the latest lineage boot.IMG?