yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] sga999:
It has been a long time since I installed the Essential drivers and minimal ADB and fastboot. But they do work for me. I wonder if you have some older versions.

The original Essential site is no longer there. But I think XDA threads do point to some other places for the drivers. But the minimal ADB and fastboot is more recent than that. Sorry, I'm not being very clear! But it sounds like your fastboot must not be the right one. You should not get errors when trying to flash the boot image.

Maybe the drivers are here?

Essential-PH1-WindowsDrivers.exe | by sd_shadow for PH-1

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

For minimal ADB and fastboot, this seems to say the latest is 1.4.3. I have something earlier installed, so you may not have to have the absolute latest.

Download Minimal ADB and Fastboot Tool (all versions)

Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.

androidmtk.com
[Essential Phone Guides, News, & Discussion] sga999:
Edit: I'm confused. How did you get the QQ1A... rom installed? You had to have the proper fastboot then.
[Essential Phone Guides, News, & Discussion] Meerk4ty:
Device arrived with this version, tried everything you offered but nothing helped.
[Essential Phone Guides, News, & Discussion] sd_shadow:
Other fastboot commands work?

fastboot devices
fastboot reboot bootloader
fastboot getvar all
[Essential Phone Guides, News, & Discussion] Meerk4ty:
yes.

as I wrote I have already unlocked bootloader by command
[Essential Phone Guides, News, & Discussion] xterminater07:
Can someone help me with root issue? I got magisk to be recognized and it starts it's install until the end and it said cannot mount /system . Im running on nougat latest 32F.
[Essential Phone Guides, News, & Discussion] xterminater07:
I noticed that too! I just checked with root checker and it is rooted! OP should update the post to say to push twrp after unlocking bootloader you might have to try fastboot -i 0x2e17 flash boot twrp.img , then install the magisk 14.3 and ignore the error. Check root with root checker and it should work flawlessly.
[Essential Phone Guides, News, & Discussion] e1to:
Anyone???

Running lineage.. 7.1.2

Everything else working incredibly.. but really need WiFi working!
[Essential Phone Guides, News, & Discussion] qbanlinxx:
Have you reflashed the rom?
[Essential Phone Guides, News, & Discussion] Ascertion:
Does anyone know how to Magisk root LineageOS or AOSPA? Each time I flash Magisk, it returns an Error code 1. I think it comes down to an encryption issue but even formatting the device while still in recovery yields the error.

Anyone got the magic instructions?
[Essential Phone Guides, News, & Discussion] Sithben24:
After flashing "flashboot flash boot twrp.img," it says "sending to boot_b." When rebooting to recovery, it returns to the No Command screen with the Essential recovery.

If I try "fastboot boot recovery twrp.img," I get "cannot load 'recovery': No such file or directory." Any ideas here?

I'm on the Oreo Beta with unlocked bootloader.
[Essential Phone Guides, News, & Discussion] socali:
For Oreo, the OP lists a boot image that already has magisk:

https://drive.google.com/file/d/1r-x8TuNNZuZVDE7Fhu7tAHnBw92gMO-E/view?usp=drivesdk

Do "fastboot flash boot oreomagisk.img" and then reboot the phone normally.

You'll now be rooted. Now install magisk manager APK and you're good.
[Essential Phone Guides, News, & Discussion] Sithben24:
That worked perfectly. I was going a step too far. Thanks.
[Essential Phone Guides, News, & Discussion] aboood17:
does rooting affect the performance of the device?
[Essential Phone Guides, News, & Discussion] avd:
It shouldn't but it can. Magisk 14.5 was flakey.
[Essential Phone Guides, News, & Discussion] StephenMilone:
Anyone on the latest magisk 14.5 beta beware...I found mine was writing a huge log file /data/magisk_debug.log to the point where it took up my 90gb of free space and only discovered when i opened my messages app it told me i had no free space to receive texts. My only solution at this time was to unroot.

on stock 7.1, latest OTA
[Essential Phone Guides, News, & Discussion] socali:
Yep. I reported that a few days ago. It's also draining the battery and slowing down charge.

My solution is to use v14.3 - works perfectly fine.
[Essential Phone Guides, News, & Discussion] xterminater07:
If I return to stock using essential's instruction, do I need to unroot first, and how? or do I just follow their instruction to return to stock?
[Essential Phone Guides, News, & Discussion] socali:
Simply flashing stock image from their website is all you need to unroot and go back to stock.
[Essential Phone Guides, News, & Discussion] xterminater07:
Well apparently it won't flash! I did fastboot -i 0x2e17 devices and it picked up the device, but if I do normal fastboot devices it said waiting for devices. I tried to edit the flashall.bat file to include fastboot -i 0x2e17 flash yada yada but it wont work.

edit... weird... ran it again it worked!
[Essential Phone Guides, News, & Discussion] avd:
if you are using linux you need to run fastboot as root (or configure it correctly)
[Essential Phone Guides, News, & Discussion] nelson0521:
I cannot use wifi after I root via magisk. How do I fix it ?
[Essential Phone Guides, News, & Discussion] Sithben24:
I'm having the same issue so I'm kinda stuck on the Oreo Beta (which is mostly fine, but still). ADB works fine, and "fastboot -i 0x2e17" makes fastboot recognize the device, but flashboot alone doesn't recognize it.

Did you just run the flashall.bat file after running "fastboot -i 0x2e17"?

Thanks.
[Essential Phone Guides, News, & Discussion] xterminater07:
yea, i booted to the bootloader screen, and just hit flashall.bat. But I made sure all those files are in my adb folder. The latest platform ones.
[Essential Phone Guides, News, & Discussion] vergilbt:
First I want to say thanks for this thread and your work bringing root (for Oreo) to us.

Got it successfull on my device by these tutorial. But only one noob question from my side:

Is it normal that TWRP is gone after flashing recovery+magisk+boot-image?

When I want flash any zip in recovery by sideload (like Google_Lens_enabler_zip) do I have to go all these steps again? meaning flash recovery+[zip]+boot-image?

Thx
[Essential Phone Guides, News, & Discussion] aer0zer0:
TWRP is contained in boot image, once u flash the modified boot image, it's gone. Best bet is to do all your flashing at once
[Essential Phone Guides, News, & Discussion] Hung0702:
Is this a normal sized cache? Anyone know why magisk logs are so big? Or is this just a weird thing that Android/DiskUsage does when looking at cache?

EDIT: weird, the image didn't attach. [IMG="Here it is on Imgur"]https://i.imgur.com/gNN8H2Q.png[/IMG].
[Essential Phone Guides, News, & Discussion] vergilbt:
Thanks.

Than I'm right that I have to flash recovery first and modified boot image afterwards everytime I want to flash a new zip?
[Essential Phone Guides, News, & Discussion] brqndon:
Edit: Deleted.
[Essential Phone Guides, News, & Discussion] Ascertion:
This is a bug with v14.5. try flashing back to v14.3.
[Essential Phone Guides, News, & Discussion] blackice000:
I will be receiving my new PH-1 Monday and am going to stay with Nougat for the time being. Is there a method to have unlocked bootloader/root/some kind of recovery with the ability to receive OTA?

Thank you!

Rick

BlacIce000
[Essential Phone Guides, News, & Discussion] itsmekeoni:
A couple of things:

1) Thank you for the guide, it was helpful.

2) TWRP never booted for me, it would just have a blank screen like the device was off when trying to boot into recovery and at one point I had a hard time trying to start my phone. I ended up flashing the modded bootloader just to have root with Magisk and it worked after that.

3) Can we lock the bootloader again after root? I hate having that screen that pops up saying it is unlocked, it just takes that much longer to reboot.

Thanks again!
[Essential Phone Guides, News, & Discussion] reverenddak:
You can, but it will wipe your phone of any data. So if you Unlock Bootloader, Flash OS, Root, and then relock, before you use the device, it should be a non-issue.

I stand corrected. Apparently NOT if rooted and/or with custom recovery.
[Essential Phone Guides, News, & Discussion] largeselection:
Not sure if anyone else has had this problem. I was able to update to the oreo beta sideloading as per the instructions. For whatever reason, after updating to oreo, now my adb reboot commands don't work. So I was on nougat, plugged in my phone, was able to adb reboot recovery, then was able to adb sideload no problem. Now my computer recognizes the phone, I allow USB debugging and authorize the computer. I can see the phone in adb devices. The problem is when I use adb reboot bootloader or adb reboot recovery it just restarts the phone as normal and skips bootloader or recovery. I tried going into bootloader using the hardware keys, but then my phone didn't recognize the phone in fastboot devices. Any ideas? It seems to just be related to this after I apply the oreo update. I had another essential phone (thanks to the F+F code) and it did the same thing (recognized and worked fine adb rebooting into whatever on nougat and then not working once oreo was applied). I found this out because I was trying to root using the "old method"
[Essential Phone Guides, News, & Discussion] johnminator:
Anything new with the new UPDATE?
[Essential Phone Guides, News, & Discussion] bmg1001:
I won't be able to attempt making a TWRP'd boot image for the new update until later today, maybe, but for now, y'all should be able to flash the latest TWRP, flash the stock boot image for the OTA from within TWRP, and then flash the Magisk zip.

Stock Boot Image for NMJ51B: https://download.invisiblek.org/mata/boot_NMJ51B_stock.img

EDIT: Alright, I made a TWRP'd boot image for NMJ51B. Since I am not running stock,

I HAVE NOT TESTED

this boot image fully. It looks like Essential changed a few small things, but hopefully everything works fine! If the boot image doesn't work out for you, flash the original boot image linked above. If it works or if it doesn't, please let me know.
[Essential Phone Guides, News, & Discussion] tagline27:
This is incorrect, do not follow this advice unless you want to end up with a brick. It's only safe to relock your bootloader if you're on stock OS + recovery and unrooted.
[Essential Phone Guides, News, & Discussion] manaox2:
Flashing the stock image as boot in TWRP didn't work to update. I assumed boot based on the name. Should I have checked boot and system or just system instead? Maybe I should just wait.
[Essential Phone Guides, News, & Discussion] socali:
Here's the stock boot NMJ51B rooted with magisk v14.37:

boot-NMJ51B-magisk143.zip

Flash this only after you're updated to NMJ51B in order to get root again. UNZIP and use:

fastboot flash boot boot-NMJ51B-magisk1437.img
[Essential Phone Guides, News, & Discussion] manaox2:
I unrooted by doing the complete uninstall in magisk manager. Installing the update is still failing within the OS. I can try flashing the boot stock image in TWRP again, my main problem lies in updating to NMJ51B in the first place.
[Essential Phone Guides, News, & Discussion] socali:
Oh, I misunderstood. If you're on older stock and trying to get the OTA for NMJ51B, then flash the correct stock boot image for the version you're on right now (NOT 51B), and then try to get the OTA update.

No need to flash twrp - you can use: "fastboot flash boot" for that.
[Essential Phone Guides, News, & Discussion] manaox2:
Out of curiosity, is there another way possibly than going completely back to stock to update and get root all while keeping my data intact?

Nevermind. Messed up and got in a boot loop, than tried to restore backup from TWRP. After restoring backup, rebooted system and.... semi bricked now it seems. Don't get the bootloader unlocked message anymore, just the Essential logo and Powered by Android message. Unbricked by holding volume down after hard power off and then pushing twrp again... Man, I don't trust TWRP backups much now.
[Essential Phone Guides, News, & Discussion] avd:
[MENTION=1946444]socali[/MENTION] does this image also include TWRP recovery?

general question, so the boot image also contains the recovery?

i can't believe i've reverted into a noob with this phone...
[Essential Phone Guides, News, & Discussion] socali:
Oh wow. I'm not exactly sure what you did, but TWRP doesn't normally messes up with the bootloader..

Try holding the power button for a while until the phone is completely off, then turn on with volume down pressed + power. This should get you back to bootloader where you could use the factory images to recover everything using fastboot.

Edit: I just noticed your edit saying you managed to unbrick it.

---------- Post added at 07:51 PM ---------- Previous post was at 07:46 PM ----------

No, this image has is only rooted stock with no TWRP in it.

This phone is using the new A/B system which is a bit different than prior phones, so it's a confusing if you've been flashing phones beforehand. There is no longer recovery partition by itself, the recovery is now bundled inside the boot image.
[Essential Phone Guides, News, & Discussion] manaox2:
Yep, exactly what I did. Now I'm just going back to stock for sure. Getting a LOT of "FAILED: (remote: Flashing is not allowed for Critical Partitions)" messages here running the return to stock script in the bootloader.
[Essential Phone Guides, News, & Discussion] socali:
That's fine, since you did not unlock critical partitions, you couldn't have messed them up to begin with. I hope :)
[Essential Phone Guides, News, & Discussion] avd:
appreciate you helping two people at once. I'm on rooted "F" with TWRP on a sprint phone. Can I:

1) remove majik using the manager APK

2) flash BOOT from the stock F image using fastboot in bootloader

3) then I reboot into stock recovery and ADB sideload the B image

4) then reboot to bootloder and flash TWRP

5) reboot into TWRP then flash twrp.zip 14.3

6) then boot into system?
[Essential Phone Guides, News, & Discussion] manaox2:
And... finally after script finished to return to 32f stock, I see the circle on the lower half of the screen with colors swirling and "Erasing" written underneath. Yep. It's factory reset now. That's a bunch of time and settings down the drain. Terrible really, but I bet that update works now. I really miss when you could just flash an updated rooted image and keep your data and be done with it.

Battery too low to install update. I'll finish this later, getting hangry.
[Essential Phone Guides, News, & Discussion] Eric_Sheill:
Feel the save exact way!!

I've had to reset and start from scratch twice from stock, plus the first setup and once from LOS after missing swipes on keyboard rendering it unusable. Now my my phone won't take the B update and I'm going to pass trying in fear of having to wipe AGAIN!
[Essential Phone Guides, News, & Discussion] socali:
Yes, I think you can skip step 1 since step 2 will unroot it.

Also, between steps 3 and 4 I'd boot system and make sure the B update completes.

Step 5 I'm guessing you meant magisk..

Between 5 and 6 you'll have to check at bootloader if you're on the right slot, since TWRP tends to flip those sometimes.

Now, if you just want rooted update, you can simplify this a bit by avoiding the twrp part:

1) Flash stock F boot from fastboot

2) ADB sideload B update from stock recovery

3) Reboot system and let B update complete

4) Flash the rooted B boot image from fastboot

5) Boot into system
[Essential Phone Guides, News, & Discussion] avd:
I'll try and report.

Big thank you.

-----

started ADB server as sudo

mounted system

fails at step 1 -- error applying update 20 errorcode kDownloadStateInitializationError

I'm going to wait for an official firmware image and flash the whole thing.
[Essential Phone Guides, News, & Discussion] manaox2:
I had the update install, decided to restore backup without boot partition and then flash the 32f modified image again after to go back. Forgot to mount system first on the first restore which likely led to the odd issues.
[Essential Phone Guides, News, & Discussion] IC_Blood:
Did you guys manage to install any modules? I thought it was because of Oreo but after reverting everything to Nougat I still have the same issue! Do we need TWRP to make modules work? Because I only have Magisk now! What about you guys?
[Essential Phone Guides, News, & Discussion] jake5253:
Finally got mine updated with magisk boot image!!

Poweruser hint: unzip the damn boot image before you flash a zip to boot

:facepalm:

Thanks everyone!
[Essential Phone Guides, News, & Discussion] manaox2:
Did you manage to keep data intact?
[Essential Phone Guides, News, & Discussion] jake5253:
Not a snowball's chance...

I reverted to stock 32F boot.img, sideloaded update, and then proceeded to flash the 51B boot.zip to boot. Repeated this process two more times before I realized what I was doing wrong. At that point I assumed I screwed everything up, so I went ahead and screwed everything up by wiping userdata and reverting all the way back to clean-slate stock 32F.

Its okay. I didn't have anything better to do with my night
[Essential Phone Guides, News, & Discussion] avd:
unlocking critical_partitions wiped the phone.... ****
[Essential Phone Guides, News, & Discussion] jake5253:
I haven't unlocked critical. So far I've seen no adverse effects?
[Essential Phone Guides, News, & Discussion] GryphKid44:
How long did it take to flash the stock 32F boot.img? I'm at around 15 minutes and its just sitting there.
[Essential Phone Guides, News, & Discussion] jake5253:
Boot image is less than 100mb, should take a few seconds at most. Try a different USB cable, different USB port, restart your PC, or verify file integrity?
[Essential Phone Guides, News, & Discussion] scottfreeze:
I'm getting the same thing. Do you know what caused this? Were you able to find a fix?
[Essential Phone Guides, News, & Discussion] Ascertion:
I only used iytb module. I ended up just manually placing it under /system/app and it worked for me.
[Essential Phone Guides, News, & Discussion] avd:
The official firmware didn't require this.

---------- Post added at 01:09 PM ---------- Previous post was at 01:07 PM ----------

I gave up and flashed the unofficial images found in the firmware dump thread.

I have two issues:

Unlock-critical wiped my phone

I'm failing safety net with the unlocked bootloaders.
[Essential Phone Guides, News, & Discussion] jake5253:
I have seen this previously when trying to sideload.

I don't remember how I fixed it but I would say make sure you've restored the stock 32F boot image and that you're sideloading thru stock recovery, not in TWRP. If you have flashed twrp again, restore stock boot image and try again.

I haven't found a reason to unlock critical yet, so I have not unlocked it. Ever.

And safetynet is passing for me... Android Pay loads up (I haven't actually made a purchase but it loads and shows my cards, etc.)

And magisk reports green success marks on both safety net items.
[Essential Phone Guides, News, & Discussion] avd:
Ugh ugh ugh

Magisk hide was unchecked.
[Essential Phone Guides, News, & Discussion] blackice000:
Magisk Error?

I reflashed an older Magisk 14.3 because my logs were filling too quickly. Now the only Magisk error i see is:

Magisk : bind failed with 98: Address already in use

Any idea what that is? What is at port 98?

Thanks,

Rick
[Essential Phone Guides, News, & Discussion] adtamez:
It's happening the same to me. How were you able to make your cell phone boot again? I followed the same steps but I am stock on the boot animation.
[Essential Phone Guides, News, & Discussion] Croak:
Folks, just remember to use the matching TWRP for your build, or you'll run into problems, especially with radios (that includes GPS).
[Essential Phone Guides, News, & Discussion] kirschdog1:
I followed this to t and have root but no magisk modules will install? Any ideas?
[Essential Phone Guides, News, & Discussion] kirschdog1:
Here are some screenshots.
[Essential Phone Guides, News, & Discussion] kirschdog1:
:eek:
[Essential Phone Guides, News, & Discussion] IH8TouchWiz:
1. Before throwing three posts on this thread asking about your issue, at least have logs of this weird behavior which you can post alongside this bug report?

2. You probably have a better chance figuring this out if you ask in the Magisk thread than you do here.
[Essential Phone Guides, News, & Discussion] kirschdog1:
Thanks I think.......only reason i posted here is because this is specific for meta devices and I don't know this is a thread for rooting which I'm pretty sure the only way to achieve root is by using magisk. I guess that is silly logic though.
[Essential Phone Guides, News, & Discussion] dialfonzo:
THANKS ...!!!

I've just tested this and it work.

As explained, i ran into problems in TWRP:

1. The touch was not working for me so i used an OTG cable and a mouse

2. I had errors in the Shell so i did the bootloader "fastboot -w" and started over again

All working with Magisk

:)
[Essential Phone Guides, News, & Discussion] M@XLOL:
disregard....
[Essential Phone Guides, News, & Discussion] nicoseb:
Thank you for this guide.

I rooted last week with Oreo and it "worked"; but my phone keeps crashing and get stuck on the start screen (flying dots and circle)... Everytime I have to force restart the phone.

Some apps keep crashing in the background too and stuff like that. The first couple of days the camera app was completely unusable but then it started working.

Anyway, I played around yesterday, and I now have magisk manager with a couple of modules and BusyBox, and it seemed more stable but the crashes are back this morning.

I have not really found anyone in these threads having the same issue... Just one person due to navbars and how they fixed it with ADB.

Anyone with some smart advice?

I imaging un rooting would fix it...

I did have the Oreo update prior to rooting and did not experience any of these issues.

Thanks
[Essential Phone Guides, News, & Discussion] 1Krima:
I have been really stable on Oreo beta 1 with Magisk 14.3 and all of a sudden , I'm getting random reboots. Sometimes it gets stuck and I have to force restart. I have no idea what changed. I have no modules installed, only substratum LockClean theme.
[Essential Phone Guides, News, & Discussion] nicoseb:
[MENTION=5349835]1Krima[/MENTION] thanks, at least I am not alone! haha
[Essential Phone Guides, News, & Discussion] EdwardLThompson:
I need help finding the modified boot image for build NMJ51B
[Essential Phone Guides, News, & Discussion] socali:
Modified with TWRP? Here - https://drive.google.com/drive/folders/1CXkDC0iDJpDKxk4fWZYovFoxxtRdFrb7

Modified with Magisk? Here (unzip first) - https://www.androidfilehost.com/?fid=962021903579496761
[Essential Phone Guides, News, & Discussion] EdwardLThompson:
Thank you very much for your help. I'm a bit rusty on rooting as I have not done it since my Nexus 5. LOL.
[Essential Phone Guides, News, & Discussion] socali:
Welcome! :) Essential phone is a bit different since it's using the new A/B system.

You can either follow OP's instructions with Magisk v14.3 (do not use 14.5, it's currently broken), or get the rooted image above - unzip it and use fastboot:

fastboot flash boot boot-NMJ51B-magisk1437.img

Then reboot the phone and install Magisk Manager apk.
[Essential Phone Guides, News, & Discussion] EdwardLThompson:
I made the mistake of upgrading to Oreo and now I cannot access recovery. Maybe I should get some sleep before I brick my device. LMAO! Any chance someone has a link to TWRP for the Oreo build? I tried searching with no luck.
[Essential Phone Guides, News, & Discussion] IH8TouchWiz:
Here: https://androidfilehost.com/?fid=817906626617948231 . All credit goes to [MENTION=2385005]invisiblek[/MENTION] for the Oreo TWRP.