yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] NLBeev:
Few minutes back. Flashed the back-to-stock img's just to see what happens.

I hope to find a method to unroot/update stock without a PC. But I did not found a PC-less method.

After flashing BTS and reboot: no root and the Ex kernel manager shows a short menu. No tools.

So flashing twrp-recovery from the internal memory is not possible.

Rooting again (thx to OP)

- PH-1: Press volume down + start -> bootloader mode.

- PH-1: Message that the device software can't be checked . . .

- PC: Command prompt: fastboot flash boot twrp-mata11.img

- PH-1: volume button -> reboot recovery -> start button.

- TWRP: install stockboot.img from internal memory.

TWRP did not have the system partition mounted, but the option Mount system partition read-only was already checked.

I did not change this, navigated to Magisk16.7.zip and flashed it.

After reboot my PH-1 was rooted.
[Essential Phone Guides, News, & Discussion] BaamAlex:
How should i understand that? Flash boot.img and then magisk.zip? First install the boot.img, back and then magisk.zip? Or install the boot.img, reboot to bootloader, then to recovery and last install the magisk.zip? Or can i install the magisk.zip via sideload via stock recovery?
[Essential Phone Guides, News, & Discussion] TT_Vert:
magisk always has to be last as it modifies the boot image to allow root. What I do. after flashing my rom. Flash into TWRP. Flash the boot image you use. Flash magisk to allow root of that boot image. I'm also dual booting which is nice while playing around. Just change the active slot and bob's your uncle.

Dave
[Essential Phone Guides, News, & Discussion] BaamAlex:
Change the slot? Sry im new here :D

I want to stay on android p. I want only root on this thing.
[Essential Phone Guides, News, & Discussion] TT_Vert:
You're only changing the active slot if you are dual booting which you are not. All you need to do is get your stock boot image and then flash it after flashing twrp. THEN flash magisk to modify boot image. This is assuming you've already unlocked the bootloader. A bit more annoying on these new phones but it's not hard.

Dave
[Essential Phone Guides, News, & Discussion] Bobbaloo:
That 'splains a lot. Thanks for clearing that up for me. I had that issue
[Essential Phone Guides, News, & Discussion] DoR3M3:
Slots don't change on Stock - Rom & Magisk Slot A

Slots change on Custom Roms - Rom Slot A Magisk Slot B

You do it any other way, you're going to boot loop...

Also I've learned, depending on what you are doing, like a RESTORE in TWRP, that after I restore a backup, then I reboot into the bootloader, then boot back in twrp and flash the boot.img and magisk. I've noticed if I restore, boot.img, magisk all at the same time, magisk fails...
[Essential Phone Guides, News, & Discussion] :
I make my backups in TWRP as follows:

Disable security, then,

Backup my current kernel in ex kernel mg(that way its already rooted and good to go as is,without having to reflash magisk after)

So....now,

I flash the twrp boot img either via fastboot or if I'm on the go via ex kernel mg.if u do it via ex kmg, u gotta NOT reboot, it doesn't reboot recovery but tries to boot up and can't cuz the kernel isn't a kernel but twrp.....but go to magisk and reboot recovery there or use a terminal app and jus do su, reboot recovery..or turn it off and go to bootloader manually.

Once i get into twrp, i flash as a boot.img my backup of my kernel i made in ex kernel mg before booting to twrp.

NOW, i make my backup of boot, system, and data in twrp.

When u restore, u already are restoring a pre rooted kernel, so u won't have to reroot

If u make the backup before flashing your kernel again it just saves twrp boot.img as boot and not the kernel. That's why u have been boot loopingg. If u follow this method, life will be much easier. Once u restore your backup, the phone will boot up and all is well. I make physical copies of my important internal stuff, and copy to my USB flash drive or laptop. I do this to test GSI system images or to test questionable mods.

---------- Post added at 12:57 AM ---------- Previous post was at 12:49 AM ----------

And no slots do change on stock. I promise. If u have a corrupted file on A for example and cannot boot without reset, it automatically changes to B and boots there. It's one of the reasons that google and oems made A/B partitioning. Along with seamless updates.
[Essential Phone Guides, News, & Discussion] DoR3M3:
[MENTION=9317968]jacksummers[/MENTION] of course slots might change, I meant, that if you flash Stock on Slot A, then boot into TWRP, you should still be on Slot A where you will then flash magisk to root.

If you are on a Custom Rom, boot into TWRP and flash the rom on Slot A, then boot back into the bootloader, then back to TWRP, you should now be on Slot B to flash Magisk, this is what I meant.

I've tested trying to stay on the same Slot A that I installed a custom rom to, and then flash magisk to the Slot A, TWRP will allow it, it works, but then if I start the phone, it just boot loops. I have never seen where you can install a custom rom and magisk to the same Slots. For me it's always worked, Custom Rom Slot A, Magisk Slot B. This is also the same way it works on a Xiaomi phone that I have with A/B partitions...

As far as the Kernel, are you talking about Custom or Stock?

Ahh so I did on Stock Oreo at first to test, Xposed/FakeGapps, and microG shows that nice big message at the top, Your ROM has no native support for signature.... But 'System spoofs signature' is checked, but the Signature Spoofing Checker says DISABLED...

I guess time to learn how to deodex this thing... ;)
[Essential Phone Guides, News, & Discussion] :
Either kernel type. I use both. Mainly stock
[Essential Phone Guides, News, & Discussion] EddiePR:
Help!

Touch not working on twrp on build

Any help, please? I follow all the steps.
[Essential Phone Guides, News, & Discussion] DoR3M3:
So you saying, you backup the Kernel in the ElementalX, then in TWRP flash in this order; kernel > boot < magisk, and good?
[Essential Phone Guides, News, & Discussion] :
No.not at all. The kernel u backup in EX is already rooted. U don't flash anything other than that kernel backup. Then make your nandroid backup. Boot, system, and data. If u do this b4 flashing the kernel backup, you aren't backing up anything but the twrp img and your system and data. Kernel and boot are the same thing. The only important note is that twrp img is flashed to the boot partition. See attached. You navigate to exkernel folder in twrp. Select the kernel u backed up. Hit install , flash as boot. Now... Go to backup. Check boot system and data. so whenever u need to make a backup or restore one, u won't have to Reflash a kernel/boot image and also have to reflash magisk. It's already a pre rooted backed up kernel, complete with the rest of your backup. What you're saying is adding unneeded extra steps
[Essential Phone Guides, News, & Discussion] :
Pic of ex-kernel manager backups.these are kernels that are already pre-rooted. After u flash magisk when u first root, the state is written into the image. So when we back it up in android, it stays rooted..ya follow?
[Essential Phone Guides, News, & Discussion] ultrasuper:
[MENTION=9317968]jacksummers[/MENTION]

This is the first I've heard of successful nandroids.

I assume you've already been successfully restoring various nandroids you've made of different stock and/or custom ROMs you've installed (essentially fully configured ROMs, apps/settings and all) .

Most have said restorinbg from nandroids hasn't worked (for unknown reasons)

I think this is great news. It deserves a separate outlined thread with whatever caveats/requisites you've discovered (i.e., all security disabled, etc.)
[Essential Phone Guides, News, & Discussion] :
Yeah it works fine. Stock or custom, coming from Oreo or pie. Or vice verse. As long as the bootloader has been updated and the baseband it works either upgrade or downgrade of the OS.

Only bug I have found is if there is any corruption, touch fails in twrp and one must factory reset or fastboot -w . I even found a work around if one fails to disable security. A clumsy hack around but I will detail it another time.suffice to say, keep an anykernel zip on your laptop, ie, ex kernel zip.oh and the only real oddity is if you are coming from a treble gsi, u have to restore your nandroid to both a and b. So if u do mess with gsi's after making a nandroid, be sure to copy it to your laptop before testing. Then copy back when ready to restore.
[Essential Phone Guides, News, & Discussion] PITTAR:
i followed the guide step by step but when reboot the phone nothing magisk someone have some hint?
[Essential Phone Guides, News, & Discussion] DoR3M3:
Custom Rom or Stock?
[Essential Phone Guides, News, & Discussion] PITTAR:
stock 9.0 pie
[Essential Phone Guides, News, & Discussion] DoR3M3:
Did you flash magisk on the same slot as the rom?

Also did you use Magisk 16.7?
[Essential Phone Guides, News, & Discussion] :
If have no touch in twrp, then u are experiencing some corrupt data. Factory reset, then do fastboot set_active other. Then factory reset that then start over with twrp. It's the only fix I have found
[Essential Phone Guides, News, & Discussion] drumrjoe:
ugh, requesting a little help.. on a new essential ph-1.. upgraded to android pie, no problem. unlocked bootloader with no problem.. got twrp up and running, no problem.. sideloaded magisk 16.7 no problem.. now phone was bootlooping a few times. Now just running through the boot animation with the 4 dots turning to many dots in circle and back again... please help... you're my only hope...;)

Update... got phone in recovery mode, but have no idea on how to get it re-started
[Essential Phone Guides, News, & Discussion] :
In recovery do a factory reset. After flashing twrp, U gotta flash the boot img first in twrp, then magisk then reboot .
[Essential Phone Guides, News, & Discussion] drumrjoe:
oops, meant bootloader mode.. not twrp.. tried going into recovery and get the green robot with red exclamation point..
[Essential Phone Guides, News, & Discussion] droidian5:
In bootloader mode, flash twrp, then flash just the IMG. That might get you back up. You might be able to switch slots and get it to boot too.
[Essential Phone Guides, News, & Discussion] TT_Vert:
did you do a data/cache wipe? You could also do a fastboot -w to wipe all.

Dave
[Essential Phone Guides, News, & Discussion] :
When u see the little android guy, hold power, and tap volume up.u will be in stock recovery.select factory reset.
[Essential Phone Guides, News, & Discussion] drumrjoe:
Thanks for all the help!! You guys are all the real RockStars!!! I was able to download and flash a stock ph-1 rom and got the thing back to life.. My bootloader is still unlocked so may try rooting again once I read through all the docs and youtube vids!
[Essential Phone Guides, News, & Discussion] torhonia:
Hey guys, one simple question is it possible to change it's IMEI number after it is rooted? Thanks a lot.
[Essential Phone Guides, News, & Discussion] NaterTots:
I think talking about that violates XDA rules.
[Essential Phone Guides, News, & Discussion] droidian5:
I know that's illegal
[Essential Phone Guides, News, & Discussion] torhonia:
Maybe a private message about it ?
[Essential Phone Guides, News, & Discussion] RandomPooka:
It's still illegal in a private message
[Essential Phone Guides, News, & Discussion] DoR3M3:
Oh LMAO! I was waiting for that... ;)

Yeah that's cause the Pooka gots your PM Hacked...
[Essential Phone Guides, News, & Discussion] drumrjoe:
ok, got everything back up and running.. upgraded to Pie 9.0...made sure I had the right boot image, twrp was working great.. did a an adb sideload of the boot image (pie-9.0-091.img) all good, then did a sideload of magisk-v16.7.zip, everything good.. did a reboot to recovery, all good, then did a restart in recovery... phone reboots and I get the circle animation going from 4 dots to the many dots circle... seems stuck on that? How long is that supposed to go for?
[Essential Phone Guides, News, & Discussion] kboya:
Why didn't you flash the boot.img and Magisk.zip in twrp then reboot?
[Essential Phone Guides, News, & Discussion] sash11:
Not that long. I would suggest patching boot.img in Magisk application and flashing patched boot.img from fastboot. No need to flash twrp and Magisk.zip with this method. To me it is cleaner and quicker imho
[Essential Phone Guides, News, & Discussion] drumrjoe:
Thank you for the quick reply... Not sure I understand patching boot.img in Magisk application... Is there a link or vid on how to do that?

Thanks in advance.
[Essential Phone Guides, News, & Discussion] NaterTots:
Why bother using TWRP if you're going to sideload everything?

Disable lock screen security including fingerprint

If you're using TWRP, go to the bootloader,

Fastboot flash TWRP,

Select install image

Install the boot.img that you put in your storage and matches the build you have installed,

Then change TWRP back to install zip

Flash Magisk 16.7

Reboot system and you're done.

Once you've installed the boot.img you can't go back to TWRP recovery without doing fastboot again.
[Essential Phone Guides, News, & Discussion] munchy_cool:
getting an error when flashing twrp.

can flash stock boot.img successfully?

using boot_b as my current slot is b and using just fastboot flash twrp.img is giving an error as well.

PS:- i have done both flashing unlock and unlock_critical.

on stock Pie and latest fastboot from google.

https://developer.android.com/studio/releases/platform-tools
[Essential Phone Guides, News, & Discussion] aer0zer0:
hmmm, i was gonna say did you append boot_b since your using the google platform tools and not essentials, but you are. is it possible you have a bad copy of twrp?

65DED4C1A4382F0474333AD9F045930B md5 of twrp11
[Essential Phone Guides, News, & Discussion] munchy_cool:
md5 looks good

65ded4c1a4382f0474333ad9f045930b

could be that I am on Mac and latest adb and fastboot might not be co-operating? I checked your other thread which recommends a specific version of adb and fastboot but it has only .exe files.
[Essential Phone Guides, News, & Discussion] aer0zer0:
essential only provides windows drivers. Can you bootcamp? i mean, it did flash stock boot.img, can you reboot to bootloader and run the command again? im havent owned a mbp in years

---------- Post added at 12:32 PM ---------- Previous post was at 12:24 PM ----------

buddy of mine suggested doing fastboot -vvv then your command to get the verbose output
[Essential Phone Guides, News, & Discussion] munchy_cool:
same issue on multiple tries.

here we go with logs

fastboot: verbose: sending command "getvar:has-slot:boot_b"
fastboot: verbose: received OKAY ""
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "0x20000000"
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'boot_b' (45048 KB)
fastboot: verbose: sending command "download:02bfe000"
fastboot: verbose: received DATA 02bfe000
fastboot: verbose: sending data (46129152 bytes)
fastboot: verbose: received OKAY ""
OKAY [ 0.205s]
Writing 'boot_b'
fastboot: verbose: sending command "flash:boot_b"
fastboot: verbose: received FAIL "Error flashing partition."
FAILED (remote: Error flashing partition.)
Finished. Total time: 0.525s

---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------

strange thing is , when it fails to flash the twrp file. sometimes it doesnt boot until you flash stock boot.img

---------- Post added at 01:11 PM ---------- Previous post was at 12:45 PM ----------

this is very strange. Same issue everywhere.

tried below

1. windows powershell - used both Google and Essential fastboot

2. windows command prompt - used both Google and Essential fastboot

3. Macbook - used only Google fastboot

can flash stock boot, but cannot flash twrp img. same error everywhere.

checked oem device-info as well

(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Device modem EFS unlocked: false
(bootloader) Charger screen enabled: true

Edit

this thing is a hot mess. tried going back to stock, didnt flash system. and got stuck. then i started getting the red message.

so i flashed the red fix boot.img and let it reboot 5-6 times. then i flashed stock boot.img to both slots and did a fastboot -w and rebooted. it didnt boot into android and bootlooped back into the red message. reboot then and it boos fine, but now i cannot get rid of the red message even after multiple tries.

this is the worst phone for modding on a mac.

cant even flash stock

Sending sparse 'system_b' 1/5 (524284 KB) OKAY [ 3.043s]
Writing sparse 'system_b' 1/5 FAILED (remote: Flash Write Failure)

Edit 2

stuck in a bootloop. cant flash system. any help will be appreciated.
[Essential Phone Guides, News, & Discussion] NaterTots:
I'm just spit balling here, but maybe try a different cable?

And don't use the cable essential supplied as they said it can brick devices when using it for adb and fastboot
[Essential Phone Guides, News, & Discussion] munchy_cool:
I dont have a type c port on my computer so am using a cable with which i have flashed below phones (using fastboot)

Pixel 2

Moto X4

Xiaomi Mi A2

tried changing the slot as well but that switched back to slot b after reaching max unsuccessful boots.

this phone is irritating none the less.

not sure what else to try.

---------- Post added at 03:12 PM ---------- Previous post was at 02:47 PM ----------

so i changed the slot to a.

flashed Essential's 8.1 image using fastboot on a mac, using the same cable i have been using and everything flashed fine and I booted into Android 8.1.

tried flashing Oreo to slot b, got an error on boot_b and system_b.

changed slot back to a, booted back into Oreo. downloading the update now and it should instal on slot b. let see how this goes.

---------- Post added at 03:54 PM ---------- Previous post was at 03:12 PM ----------

after updating to Android 9.0 Pie, it installed on slot b and now twrp img is being sent successfully. damn, what a pain.
[Essential Phone Guides, News, & Discussion] aer0zer0:
WTF, lol. Why did it hate B so much
[Essential Phone Guides, News, & Discussion] droidian5:
I think it hates the mac ;)
[Essential Phone Guides, News, & Discussion] munchy_cool:
lol

been a crazy day..i think somehow boot_b and system_b were not unlocked. and now they are (hopefully).

will try to root next week. on stock Pie right now.
[Essential Phone Guides, News, & Discussion] sruel3216:
Essential noob here. Decided to get in cuz they are so cheap at the moment. Came from Pixel 2 xl.

Anyways I been trying unlock my bootloader but having some trouble. Usb debugging check. Oem unlock check. Device is recognized by comp. I run adb to reboot to bootloader. But then at bootloader my device isn't recognized. I saw some other commands to try if device wasn't connecting in bootloader, but those didn't work either.

Any help would be great. Thanks

Edit: read in Reddit I need to try essential drives. I'll see if that works
[Essential Phone Guides, News, & Discussion] NLBeev:
You need a usb 3.0 compatible cable.

The essential cable is only for charging the battery.
[Essential Phone Guides, News, & Discussion] sruel3216:
I know. I was using a USBc to USBa. Installing the drivers from essential fixed it.

thanks

---------- Post added at 08:03 AM ---------- Previous post was at 07:22 AM ----------

What are the commands you do to swap. I think I'm getting the same issue as you. I do the flash boot twrp.img and it says failed no such partition
[Essential Phone Guides, News, & Discussion] NLBeev:
https://mata.readthedocs.io/en/latest/
[Essential Phone Guides, News, & Discussion] sruel3216:
im getting this issue exactly:

https://xdaforums.com/essential-phone/help/partition-t3733811/page2

what <filename>.img are they flashing for it to work? i tried flashing the boot.img but that didnt work.

thanks
[Essential Phone Guides, News, & Discussion] sash11:
Just updated Magisk to 17.0. No issues. SafetyNet check is fixed now.
[Essential Phone Guides, News, & Discussion] munchy_cool:
filename is either the twrp image or stock boot image.
[Essential Phone Guides, News, & Discussion] Darkside1984:
I haven't made it work. When I turned on the phone this morning I received updates from Magisk Manager and 17.0 zip but it seemed like the previous ones were no longer active.

When I've flashed boot image and Magisk 17.0 and restart the system, It remained in bootloop. I had to reflash the 16.0...

Any suggestion? I've last Oreo compilation (July).
[Essential Phone Guides, News, & Discussion] sash11:
Just install latest Magisk apk 5.9.0 from official thread https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Inside Magisk application in Settings change update channel to Beta. Download stock boot.img to your phone. In Magisk application click Install. Choose Install again. Then choose Patch Boot Image File. Magisk will patch your stock boot.img and save it to MagiskManager folder on your sdcard with a new name called patched_boot.img. Reboot into fastboot mode and flash patched_boot.img into the active boot partition. Reboot after that. Your phone should be rooted after this. Here is a video howto. Watch first three minutes)

https://www.youtube.com/watch?v=BF4_hnKgjFA
[Essential Phone Guides, News, & Discussion] NLBeev:
Assuming we are talking about flashing the stock boot image with fastboot in a command shell of a PC.

fastboot flash boot_<letter> <filename>.img

<letter> Is the active slot (a or b) where you want to flash.

<filename> needs to be replaced by the name of the boot image on your PC.

When the img is not in the directory where fastboot is; you need to add the path name before.

See the first post in thread

[GUIDE][Back-To-Stock]
[Essential Phone Guides, News, & Discussion] ceelos218:
Reboot to phone recovery or twrp?
[Essential Phone Guides, News, & Discussion] sash11:
Sorry, made a mistake. Reboot into fastboot, flash patched_boot.img from fastboot. After that just reboot into the OS. That should be it. Your phone's boot loader has to be unlocked of course prior to flashing)
[Essential Phone Guides, News, & Discussion] ceelos218:
Would it matter if I have finger print and lock screen? For future reference.
[Essential Phone Guides, News, & Discussion] sash11:
Remove any protection before rooting. You can re-enable after everything is done.
[Essential Phone Guides, News, & Discussion] nababatigyza:
Hi, I am having the exact same issue! How did you re-flash Magisk 16? I cannot boot, and the device is encrypted.
[Essential Phone Guides, News, & Discussion] lynnux:
I had the same problem with Magisk this morning as others. Updated to 17.0, got into bootloop. I could reboot into bootloader, but not recovery. I fastboot flashed stock boot.img, and phone rebooted w/o root. I think I'll wait before trying to install 17.0, can live without root for now.
[Essential Phone Guides, News, & Discussion] munchy_cool:
https://twitter.com/topjohnwu/status/1035895431656558592
[Essential Phone Guides, News, & Discussion] aer0zer0:
Did you have a pin on your phone when you took the OTA and flashed twrp? Crypto doesn't work on the released one. There is one twrp with working touch, but crypto is still broke.
[Essential Phone Guides, News, & Discussion] Mike02z:
TWRP never got past the screen asking if I wanted to modify the system. At that point I sideloaded Magisk 14.3. I then flashed the Oreo.img in the OP via fastboot and rebooted. I'm encrypted. I'll be happy to share screen shots.
[Essential Phone Guides, News, & Discussion] aer0zer0:
I couldn't mount data, so sideloading failed.when we got touch working, , I formatted data through twrp. Then I was able to sideload it. But It forced a factory reset
[Essential Phone Guides, News, & Discussion] Mike02z:
Not sure what's up. Here are some screen shots...
[Essential Phone Guides, News, & Discussion] aer0zer0:
Sure, all good here. I just got crypto errors