yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] Thompson2x:
Yes I have, two Type C ports on my laptop just now. I do only have the cable that came with the phone at the moment, and I've read that can be an issue. I can try with a different cable and traditional USB ports when I get home in the morning if that may make a difference. As of right now, the screen has turned off and the LED flashes red when it's plugged in, but that's all that happens

**EDIT** It's charged enough now that it's back to sitting at the "Powered by Android" screen, but that's where it's stuck, and 'fastboot devices' doesn't detect it.
[Essential Phone Guides, News, & Discussion] RandomPooka:
Hold down "power" and "volume down" for like 10 seconds. You'll go straight to bootloader, where you can flash TWRP.

From there, flash the stock boot image, followed by magisk.
[Essential Phone Guides, News, & Discussion] nababatigyza:
Hello everyone,

I am getting below error, any ideas?

C:\Program Files (x86)\Essential\ADB>fastboot devices

XXXX fastboot

C:\Program Files (x86)\Essential\ADB>fastboot flash boot twrp.img

target reported max download size of 536870912 bytes

sending 'boot_a' (45048 KB)...

FAILED (data transfer failure (Too many links))

finished. total time: 0.202s

I am at the bootloader ( which is unlocked ) while I am trying this.

Thanks in advance!

Fixed: Changed the USB port and got it working....
[Essential Phone Guides, News, & Discussion] JudasD:
I had this problem once. I tried a different cable and the problem went away.

Hope this works for you.

JD
[Essential Phone Guides, News, & Discussion] Thompson2x:
Unfortunately, when I do this it shuts the phone off for a few seconds and then goes right back to the "Powered by Android" screen again
[Essential Phone Guides, News, & Discussion] RandomPooka:
Ok, and when you hold it as long as I suggested?

I've had it take upwards of 15 seconds to get there.
[Essential Phone Guides, News, & Discussion] Thompson2x:
I've been able to get into bootloader and then then Flash TWRP successfully and get into recovery mode. I have the Magiskv16 files and the April Oreo file from the OP. The video I was following then used these two commands:

adb shell twrp sideload

adb sideload magisk.zip

I used the correct name for the Magisk folder, but these steps obviously do not include the stock boot. What is the command I need to use for it? And do I just do that before the magisk sideload? Sorry for all the noob questions, this is my first time :eek:
[Essential Phone Guides, News, & Discussion] aer0zer0:
That video is OLD..... you don't need adb commands

Follow the op in this thread. You can actually use the touchscreen.....
[Essential Phone Guides, News, & Discussion] Thompson2x:
I get this error message when the zip attempts to install. I downloaded the zip again a couple times to no avail as well.
[Essential Phone Guides, News, & Discussion] RandomPooka:
Sorry I wasn't able to respond, but aer0zer0 is right. You're definitely taking unnecessary steps. I also don't see you flashing the boot image before Magisk, which is what you'll want to do when you do it in TWRP
[Essential Phone Guides, News, & Discussion] Thompson2x:
I believe I've been able to successfully flash the boot image--I downloaded the Oreo April file from the OP and went through the install in TWRP. It said it was completed. but when I then go to install the Magisk zip I get the error in my last post where it says it failed because if couldn't mount 'system.'
[Essential Phone Guides, News, & Discussion] aer0zer0:
What version twrp? Bfore flashing magisk, mount system, by going to mount button, and selecting system. If your still getting that error 1, its your version of twrp
[Essential Phone Guides, News, & Discussion] Thompson2x:
I believe it's the most current TWRP, it's from the link in the OP--3.2.1-0. Is that the most current? When I go to Mount, it doesn't let me select system.

When I install the boot image, I do I select Boot or System Image?
[Essential Phone Guides, News, & Discussion] RandomPooka:
You install the boot image to boot...
[Essential Phone Guides, News, & Discussion] Thompson2x:
Ok, that's what I did, and it still won't mount nor let me select the box for system in the mount menu. TWRP is the most current version as well, double checked that.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Is it twrp11.img?
[Essential Phone Guides, News, & Discussion] Thompson2x:
TWRP-mata_11.img

It'st the one in the OP
[Essential Phone Guides, News, & Discussion] Thompson2x:
Finally got it, reverted back to stock and started over completely. Everything seems to be ok now except WiFi doesn't work. I went back into TWRP and reflashed the boot.img and Magisk but that didn't fix it unfortunately.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Did you flash it to the right slot?
[Essential Phone Guides, News, & Discussion] Thompson2x:
That I do not know, there's nothing about slots in the OP. I just went in TWRP and hit install. Is there anything from Magisk that is supposed to get installed app-wise?
[Essential Phone Guides, News, & Discussion] Fed4Lyfe:
i flashed boot image to the boot partition and it worked. but I am also having the same problem with wifi not turning on.

---------- Post added at 07:15 PM ---------- Previous post was at 07:06 PM ----------

why doesn't OP say in the post which partition to install stock boot image? I don't mean to be a whinner but this step seems pretty important if you don't want to brick your phone.
[Essential Phone Guides, News, & Discussion] RandomPooka:
Where the f*** else would you install the boot image if boot partition is an option?
[Essential Phone Guides, News, & Discussion] rignfool:
WiFi not working means that you have TWRP still installed as your boot.img... or you have a firmware mismatch...

My instincts say you may have read the OP... But didn't understand it...

I also learned from your post that you skimmed/ignored the information about how to figure out which slot you are on... And how to make sure you're flashing to the correct slot...

Please go back and re-read the OP... Then ask questions... Then attempt to flash...
[Essential Phone Guides, News, & Discussion] madd_vybzz:
Can I get a link to download the stuff I need to root the PH1? Bootloader unlocked already
[Essential Phone Guides, News, & Discussion] rignfool:
No...

You have to go back and actually read the OP...
[Essential Phone Guides, News, & Discussion] madd_vybzz:
I did but it didn't have what I wanted
[Essential Phone Guides, News, & Discussion] rignfool:
Yes... It does... Hundreds of people have managed to do it already...

If you don't understand something... Ask a question... DO NOT ask for handouts or spoon feeding...
[Essential Phone Guides, News, & Discussion] madd_vybzz:
Does it matter what version of magisk I use when rooting the PH1?
[Essential Phone Guides, News, & Discussion] Archangel:
I dont think so I used version 16.0 and it worked fine and if it needs to update it will.
[Essential Phone Guides, News, & Discussion] madd_vybzz:
Is it ok if I Google it and download it
[Essential Phone Guides, News, & Discussion] Archangel:
I just went to the Magisk XDA site here and flashed it

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Essential Phone Guides, News, & Discussion] madd_vybzz:
I can't find a twrp that fits my Build number OPM1.180104.141 is The twrp NMJ32F safe to use?
[Essential Phone Guides, News, & Discussion] indian84:
Use TWRP 11..

Make sure to disable the secured lock screen before flashing TWRP..
[Essential Phone Guides, News, & Discussion] RandomPooka:
Re-read the OP, just to be safe.

If you're looking for a TWRP that fits your build number, you may have misunderstood it. You want a boot.img that matches your build number of 141 (April Oreo 8.1), so you are rooting with the right boot.img/kernel

The TWRP is the 11 version for Oreo, no matter which boot.img you need.

I recommend getting the 141 full back to stock file from the firmware thread, too. It's good to have the needed tools to fix a mistake, if you accidentally mess up.
[Essential Phone Guides, News, & Discussion] madd_vybzz:
I read the Op and I found 4 different twrp.img I'm not sure which one to use
[Essential Phone Guides, News, & Discussion] RandomPooka:
Don't root your phone.

You had 2 different people explicitly tell you which TWRP to use in the 2 posts prior to your last post, and you STILL can't figure it out?

You are 100 percent destined to break something if you can't follow along with that and nobody here will give a crap, because you are actively ignoring very specific directions on what you need and where to get it.

Don't root your phone.
[Essential Phone Guides, News, & Discussion] madd_vybzz:
Bootloader is already unlocked
[Essential Phone Guides, News, & Discussion] RandomPooka:
That's not what I said, nor did I mention it

I don't know what you read, but it wasn't what I wrote.
[Essential Phone Guides, News, & Discussion] madd_vybzz:
I got the twrp I needed, I started the rooting process and when I reboot in to recovery mode the screen comes up black with a no command message
[Essential Phone Guides, News, & Discussion] RandomPooka:
When booting to TWRP, you're using this command, correct?

fastboot flash boot twrp.img (using whatever the exact name of the twrp file is. It's not always identical, depending on who hosts it)

The 'flash' part there is important. We can't just 'fastboot boot'.

After that flash command, you select 'Reboot Recovery' with the volume buttons on your phone and press the power button to select it.
[Essential Phone Guides, News, & Discussion] rignfool:
Nah... You're still on stock recovery...
[Essential Phone Guides, News, & Discussion] madd_vybzz:
Yeah I'm still trying to root the PH-1
[Essential Phone Guides, News, & Discussion] rignfool:
Is English not your first language?
[Essential Phone Guides, News, & Discussion] madd_vybzz:
Yes it is

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

How do I close the bootloader
[Essential Phone Guides, News, & Discussion] Azeazezar:
On this phone, you don't.

Not unless you are At least 110% certain everything is as stock as it can be.

You risk turning your phone into a paperweight. My advice: leave it unlocked.

That said, here is the answer:

fastboot flashing lock
[Essential Phone Guides, News, & Discussion] bmg1001:
Added the boot image for the May Security Update :good:
[Essential Phone Guides, News, & Discussion] johncjenc:
Unlocked and rooted using Magisk here, to update to the May security update can we flash the May boot image in TWRP, or do we have to relock, flash stock and then apply the image.
[Essential Phone Guides, News, & Discussion] manr1mg:
Is that the boot image for OPM1.180104.166 ?
[Essential Phone Guides, News, & Discussion] bmg1001:
Yes
[Essential Phone Guides, News, & Discussion] bmg1001:
I think the way most people have updated on stock while running Magisk is to just flash the stock boot image for whatever build you are currently running. Once the stock boot image is installed, the OTA *should* apply correctly, afterwards you could patch the May boot image from Magisk Manager and then flash the resulting boot image in fastboot. I'm sure people have posted elsewhere in this thread the exact steps they took to update to a newer build, if you wanna look around.
[Essential Phone Guides, News, & Discussion] manr1mg:
Awesome thank you.
[Essential Phone Guides, News, & Discussion] avd:
Never had luck doing it this way. But will try again.
[Essential Phone Guides, News, & Discussion] bmg1001:
You could also just flash a "Back-to-Stock" zip of the build and patch the boot image while you're at it too. Always works 100%.

Just be careful as some BTS zips, like the newer ones by aer0zer0, are very likely to wipe your data. If you decide to go that route, I highly suggest editing the script (flash-all.bat) and deleting any line containing "fastboot -w" (sometimes, this may be in there twice!) so that your data isn't deleted. If the BTS zip has something like a "flash-all-nowipe", you can use that one just fine instead.
[Essential Phone Guides, News, & Discussion] avd:
Yep, bts is the only way that works for me.
[Essential Phone Guides, News, & Discussion] JudasD:
i flashed stock boot and system and still received an error on the OTA. :( will have to try BTS this time.

JD
[Essential Phone Guides, News, & Discussion] bmg1001:
The main idea is to just flash the back to stock for the build you want to update to. Just updated the OP with this actually. So if you're on the April update and rooted and you want to go to the May update, you can download and patch the boot image from the May update with the Magisk Manager, then copy the patched boot to your PC, flash the BTS (make sure to choose the no wipe flash-all script), flash the patched boot, then reboot.
[Essential Phone Guides, News, & Discussion] JudasD:
Your method was my next approach. My bandwidth is severely limited at the moment and i was trying to eliminated downloading a 1.3 gig image :) I wont get a chance to give this a try until tomorrow evening. Thank you for all of your help on this awesome device.

JD
[Essential Phone Guides, News, & Discussion] mobileman88:
The full image is always the best way to flash. I never had a problem with it all these years across multiple devices
[Essential Phone Guides, News, & Discussion] Chien35:
Alas, I forget to patch my boot image from previously rooted now I'm on latest May security patch after flash from sideload.

Any solution yet???
[Essential Phone Guides, News, & Discussion] InkSlinger420:
I got you

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

May update Magisk patched boot.img

fastboot flash it.
[Essential Phone Guides, News, & Discussion] harsh2193:
Just wanted to confirm one thing. Once I flash the BTS and have the patched magisk boot image, should I simply flash the magisk boot image (fastboot flash boot patched_boot.img)?

Nothing to do with the current-slot and no need to flash TWRP again to flash the magisk zip?
[Essential Phone Guides, News, & Discussion] bmg1001:
Yeah, just "fastboot flash boot patched_boot.img" should work.
[Essential Phone Guides, News, & Discussion] Skripka:
So long as the image is in the directory where ADB and Fastboot are
[Essential Phone Guides, News, & Discussion] InkSlinger420:
or if you have system wide adb in your path you can do it from wherever the file is...
[Essential Phone Guides, News, & Discussion] bmg1001:
Added the boot image for the P Developer Preview. I have not tested this myself as I don't currently have the P Beta installed, however, other people on the Discord have told me that rooting it is basically the same as rooting stock Oreo. You might need to reboot a few times, but it should work. Also, I'm not sure if the latest stable Magisk supports P yet, but the beta Magisk builds should, and I find that they are just as stable as the official releases...usually...

EDIT: Flashed P. Magisk v16.4 works perfectly using the regular ol' Oreo method.
[Essential Phone Guides, News, & Discussion] RandomPooka:
Whoa. We got a P preview? Slick
[Essential Phone Guides, News, & Discussion] JudasD:
yes we do. I just saw the news this morning, the PH-1 is one of the first phones to get it. very cool. :good:

JD
[Essential Phone Guides, News, & Discussion] JudasD:
Your method worked beautifully. Thanks again bmg.

JD
[Essential Phone Guides, News, & Discussion] prabs99:
Can we uninstall thru Magisk, and install OTA and reinstall using the patched boot image?
[Essential Phone Guides, News, & Discussion] bmg1001:
You can try. Uninstalling through Magisk might remove all your modules, and in the end, it might not even work properly. While this might work, I can't guarantee that it will for sure.
[Essential Phone Guides, News, & Discussion] prabs99:
I will go with the BTS route.
[Essential Phone Guides, News, & Discussion] blackice000:
I can confirm the Magisk uninstall, OTA, reinstall does not work. It's sad we cannot simply accept the OTA while rooted. So much for "open" phone development from the manufacturer.

Rick

BlackIce
[Essential Phone Guides, News, & Discussion] RandomPooka:
That's true of every device I've seen. Not sure why you're so upset about it with this one
[Essential Phone Guides, News, & Discussion] bogdi1988:
According to another thread post, Magisk 16.4 beta can root the P developer build
[Essential Phone Guides, News, & Discussion] mobileman88:
Anyone got the wifi not working issue when flashing the full image from Essential for P? How can I fix it without wiping my data?
[Essential Phone Guides, News, & Discussion] Archangel:
For some reason after a 3rd or so reboot root goes away and I have to do the process all over again,,,on the may update?
[Essential Phone Guides, News, & Discussion] kinglove1211:
I'm not used to it either,I had a pixel xl and didn't like how it was set up like that so I sold it.I guess I'll have to mess around with this one for awhile to get it figured out.

---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------

With magical you can do the button combo to get back into recovery but I haven't had any luck with reboot apps.If you have supersu I guess it overwrites the image and the phone just reboots normally,even from the fastboot menu.
[Essential Phone Guides, News, & Discussion] gokart2:
[/B]

This command is not universal between devices, and you will need to gather its pieces (/dev/block/platform/dw_mmc/by-name).

How?

- In your device, use any explorer that can get you to the device root (personally I use ES Explorer, by pressing on "/" on navigation bar).

- Go to "/dev/block/platform/" folder

- Here you will see some files and folders, we need to open folders and search for the folder called "by-name" inside one of them; in my situation it was "dw_mmc" folder which has the folder "by-name" inside it.

- At the end, my targeted piece info will be (/dev/block/platform/dw_mmc/by-name)

- Now open adb shell and put that command..

adb shell ls -al /dev/block/platform/[COLOR="Red"]dw_mmc[/COLOR]/by-name

This one will give you info about the dev block names WITH their familiar names (i.e, boot, recovery, system... etc)

/dev/block/********

You want the on that says boot.......

Get that address/partition.....then:

adb shell
su
dd if=/dev/block/mmcblk******* of=/sdcard/boot.img

That will dump it to the root of the sdcard. ~42mb my guess

https://xdaforums.com/showthread.php?t=2450045
[Essential Phone Guides, News, & Discussion] networx2002:
Worked!!! TY
[Essential Phone Guides, News, & Discussion] gokart2:
TENCHAR
[Essential Phone Guides, News, & Discussion] MinimalistChris:
Dialer APK Request

Hate to go a bit off-topic here, but figured that now people who have root, can do me a favor here...

I'm on Lineage OS now, but I forgot to grab the Essential Dialer APK before I switched over. Since that dialer is essentially the Google Dialer, I know it should work fine on Lineage. I'm just hesitant to grab it from APK Mirror because there are so many versions of it that I don't know which would even be compatible.

Thanks for any help! Love this community!!!
[Essential Phone Guides, News, & Discussion] ad78:
SuperSU will let you use android pay? Im happy with magisk as I tested a while ago in starbucks
[Essential Phone Guides, News, & Discussion] Milly7:
Get it from the play store
[Essential Phone Guides, News, & Discussion] gokart2:
Thanks!

Quick question via PM if you don't mind. I assume your flashing magisk then dumping the kernel instead of modifying the stock boot.img? Or are they just ramdisk mods?

And....what do you mean a few posts back about the TWRP modified boot.img?

Not likely. I don't use Android pay. I'm a bit old school. I like to build a majority of options from Xposed/magisk into my roms. Compile my own kernels, etc. Keeps me busy. And I learn more. Not saying Xposed/magisk isn't awesome, I just feel the less I use them the less issues I have? I still Xposed a bit, but haven't needed to use magisk.

Even though I currently don't have the phone (yet), I'd like to help a bit.

Been reading up on the a/b partition stuff, definitely interesting.

I took down my root process idea because I don't want anyone bricking or getting caught up. Typically I test then post. So if anyone wants to try to get a working SuperSU process, I have some ideas. But I need the SuperSU modified boot.img. The process of root with magisk will likely work.

After rooting via magisk, can you boot to TWRP recovery? Or is it like Pixels where you essentially (lol) only can temp boot to TWRP?
[Essential Phone Guides, News, & Discussion] bmg1001:
Remember, the recovery and kernel are now rolled into the same boot image. The first build of TWRP included a non-working kernel, so leaving it as the boot image would result in a non-working system. I used that early image to boot into TWRP, flash the stock boot image over it while still being booted in TWRP, then I flashed Magisk and dumped that boot image, so that no one else would have to do the same thing.

Now that the boot images I have on the new root method have TWRP inside them already, it's just a matter a flashing TWRP, flashing Magisk, and rebooting. Same as any other older device. The recovery is located in the ramdisk. I've been unpacking the boot images, adding TWRP, and repacking now. This should hopefully work for everyone.

The Pixel method of booting TWRP temporarily isn't working right now. The fastboot boot command doesn't work by itself on this device, I think we might need to specify an extra parameter for it when typing the command, but I don't know what it is yet. Still looking :/
[Essential Phone Guides, News, & Discussion] gokart2:
Wow, great idea with the TWRP ramdisk! So as long as it's in there it will boot to TWRP recovery....:good::good:

Wondering if maybe you need an Essential specific fastboot file? Awhile back Motorola devices needed a specific Motorola ADB to flash firmware?

---------- Post added at 11:28 AM ---------- Previous post was at 10:58 AM ----------

[MENTION=4550123]bmg1001[/MENTION]

Have you tried

fastboot oem ?

If you want to dump me the bootloader, I will dig into it today and try to get some oem commands out?
[Essential Phone Guides, News, & Discussion] gokart2:
I ran through the NMJ32F_back_to_stock.zip searching for keyword "oem" to find any "fastboot oem" commands and came up with nothing. But I also ran through to find keyword "fastboot" and found nothing. So my guess is they're another partition besides the ones included in the NMJ32F_back_to_stock.zip. Searched every file in there besides system, bluetooth, modem, and the flash-all's for obvious reasons.

Dump me these and I can check them if you want? :good:

apdp

box

bspdata

cdt

ddr

devinfo

dip

dpo

frp

fsc

fsg

ftmboot

ftmdata

ftmsys

keystore

limits

logbk

logfs

misc

msadp

nvcust

nvrf

persist

raw

sec

sti

storsec

toolsfv
[Essential Phone Guides, News, & Discussion] bmg1001:
I did the same earlier and also came up with no results. I have a feeling that I might find something in misc or bspdata. Once I get home I will try to extract all these, but I won't get home for another 4 hours or so.
[Essential Phone Guides, News, & Discussion] gokart2:
Gotchya! Was bored and figured I'd try to help a little. Good luck!:good:
[Essential Phone Guides, News, & Discussion] bmg1001:
I'm just worried that it'll require an extra parameter. I looked through XDA and found that some Nexus 4 users had to specify a parameter when using the command. They had to use "fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img" for example.
[Essential Phone Guides, News, & Discussion] okgnew:
Can we get root for public Oreo Beta, please?
[Essential Phone Guides, News, & Discussion] gokart2:
Interesting. How did they find the command? Assume it was a somewhere in the bootloader as well. Although kcal is a kernel parameter if I'm not mistaken?