yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] millicent:
Thank you so much, it worked!

I am quite embarrassed for not having thought of it. Actually I believed I already reinstalled magisk manager as well (was about to tell you so but then I was maybe I didn't) amongst some other steps I did such as reinstalled the latest magisk zip (in twrp) but since it works now I think i forgot the most obvious step!
[Essential Phone Guides, News, & Discussion] HACK3DANDR0ID:
Everyone STILL having TWRP Screen Touch issues?
[Essential Phone Guides, News, & Discussion] NLBeev:
No issues, flashed the all in one patched boot image of aer0zer0
[Essential Phone Guides, News, & Discussion] HACK3DANDR0ID:
I have tried (3) different members Patched_Boot.img and still unable to get TWRP Touch Screen to work at all...

*edit*

Tried another Patched_Boot.img file and now have TWRP Touch!
[Essential Phone Guides, News, & Discussion] freedm2993:
Oct OTA

Firstly apologies for the noob question.

1. I'm rooted and have perm TWRP.

To get the Oct OTA update:

1. I have to unroot (uninstall Magisk)

2. Flash stock recovery (using TWRP)

3. Take the Oct OTA

4. Life is good :)

Is the above steps correct...- just don't want to fu the phone - my life is fu'd up enough...cheers!
[Essential Phone Guides, News, & Discussion] lynnux:
Which one worked? Others may find this helpful.

Aer0zer0's is patched for the Oct update, with the new hyp and sym partitions, so that one should work (it did for me). Older patched versions may not work.
[Essential Phone Guides, News, & Discussion] NLBeev:
Several people including me had a failed OTA. I downloaded the official October OTA zip on my ph-1 and flashed it with TWRP. Reboot ..... root gone of course. Flashed from my PC with fastboot the all-in-one patched boot image of aer0zer0, to get root and TWRP again.

https://androidfilehost.com/?w=files&flid=283261
[Essential Phone Guides, News, & Discussion] sash11:
You cannot flash stock recovery. You mean stock boot.img? If you have permanent twrp on both slots, you have to remove it from the non active slot as Magisk uninstall will only deal with your active slot.

Flash stock boot.img into both slots. Active slot will take your current build, passive slot will take one build earlier. So if your current slot is on 036 build, your passive slot has 091 build.

After that take OTA. If it fails to install for any reason, just boot into stock recovery and sideload the full OTA image for October.

Alternative way is to do full unroot. Try to take OTA. If it fails, just sideload OTA from stock recovery)
[Essential Phone Guides, News, & Discussion] freedm2993:
Many thanks.

So:

1. Unistall Magisk ( from Magisk manager) = Full unroot.

2. Flash stock boot.img to both A and B (using TWRP) -.zip file from essential site

3. Take OTA.

If fail OTA fail:

Sideload OTA using stock recovery.

Please let me know if the above "seems" right - cheers + many thanks!
[Essential Phone Guides, News, & Discussion] HACK3DANDR0ID:
Your right, i should have included it. The Patched_Boot that was able to work for me without error can be found in the 1st post HERE
[Essential Phone Guides, News, & Discussion] aer0zer0:
you made last month easy with yours, thought i would reciprocate.

Also, i am on nightly ianmacd builds of magisk. which is why some people have problems with magisk manager. If it says "hay i need to update manager" and it fails, just uninstall and reinstall manager. Then you will be G2G. he uses different build sig, so it wont just autoupdate from TJW version.
[Essential Phone Guides, News, & Discussion] lynnux:
Thank you both for working on this and sharing your results freely. Some of us need to be spoon-fed, this a/b slot thing is confusing, not to speak of hyp/sym/twrp/no-touch. You're both good at explaining things clearly and simply, and your patched images work.
[Essential Phone Guides, News, & Discussion] NLBeev:
I admire your speed.
[Essential Phone Guides, News, & Discussion] sash11:
Just do full unroot and try to take OTA. If it fails to install, sideload full OTA image in stock recovery) That's the easiest way imho.
[Essential Phone Guides, News, & Discussion] kma_29:
Here, this one worked out:

1. Unroot,

2. uninstall Magisk

3. insanely nervous pause trying everything...

4. adb sideload OTA.zip

5. fastboot flash both slots oct_patched_twrp_magisk_stock.img

6. profit
​
[Essential Phone Guides, News, & Discussion] mobileman88:
Do you need to reboot before step 5?
[Essential Phone Guides, News, & Discussion] sash11:
In step 5 you are in stock recovery. After sideloading you have to reboot into system. So yes, you do.
[Essential Phone Guides, News, & Discussion] mobileman88:
What I meant is do I reboot after ota gets flashed? Can I flash the patched boot image right after ota then reboot?thanks.
[Essential Phone Guides, News, & Discussion] sash11:
There is an option in recovery to reboot into bootloader. So yes, you can reboot to bootloader and flash patched boot.img. But I would reboot into system first, let Android finish updating and make sure I'm on the latest patch build. Then reboot to bootloader and flash my boot.img.
[Essential Phone Guides, News, & Discussion] kma_29:
:D

I think i did, i had to be sure nothing is broken. It booted in unrooted pie.

and then: Shutdown. Volume down key, power key - bootloader.
[Essential Phone Guides, News, & Discussion] mobileman88:
Ok
[Essential Phone Guides, News, & Discussion] CamoGeko:
Anyone know why I am seeing this?

I'm unrooted on latest Oct OTA with unlocked bootloader, without TWRP.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Tools look old
[Essential Phone Guides, News, & Discussion] CamoGeko:
I'm using the recommended Tools from your thread. I've tried everything, even the latest Tools from Google.

When I try to flash a patched boot img I get this:
[Essential Phone Guides, News, & Discussion] aer0zer0:
Reboot to the bootloader once
[Essential Phone Guides, News, & Discussion] CamoGeko:
Tried that, will do again.

Btw have I got a dodgy cable or something??

Just spammed fastboot flashing unlock_critical and it worked after like 10 tries. What the hell is going on lol

I've been trying for like 2 hours. :eek:
[Essential Phone Guides, News, & Discussion] aer0zer0:
You might

It's port or cable this point
[Essential Phone Guides, News, & Discussion] CamoGeko:
This is me just now trying to flash a stock boot.img

The best case scenario, it sends the boot.img but then hangs until I force reboot-bootloader.

PS. I've tried all my USB ports now, I'm using a USB-C cable from my OnePlus 5. I even tried a different USB-C cable about an hour ago and it gave me the same results. I'm running out of ideas tbh.
[Essential Phone Guides, News, & Discussion] sash11:
Try specifying the active slot boot_a or boot_b whatever it is.
[Essential Phone Guides, News, & Discussion] CamoGeko:
Tried that already mate.
[Essential Phone Guides, News, & Discussion] NLBeev:
Check the PC. Windows device manager.

Is there an !-point when connected ?

Do you see the (composite)adb-driver?

Do you see changes when USB connect/disconnect?

Did you reboot the PC before connecting the phone?

Does windows 10 show a message when you connect?

Does 'adb' commands works and 'fasboot' commands not?

Reinstall the drivers that are already on your PC when you see a '!'
[Essential Phone Guides, News, & Discussion] CamoGeko:
Device shows up as Essential Phone Fastboot.

All ADB commands work fine, phone is always detected in Fastboot.

Don't have any '!' in device manager.
[Essential Phone Guides, News, & Discussion] CamoGeko:
My bootloader details below.

I'm really running out of things to try, maybe uninstall the Essential ADB/Fastboot drivers and try Google driver instead? All I want is Root + Magisk + EX Kernel. How hard can it be lol
[Essential Phone Guides, News, & Discussion] NLBeev:
That confirms the connection.

In device manager it must be listed under 'Portable Devices'

On the phone there must be a notification

'USB debugging connected'

Now the drivers. . .

Adb reboot bootloader. Phone reboots in Fastboot Mode. Following must happen in the device manager:

Under Portable Devices phone disappears.

New device shows up 'Android Phone'.

Click to show the driver mostly 'Android Composite ADB Interface'

When this all is OK your usb connection works, but maybe fasboot not.

Than choose another driver.

Right click - Update Driver Software - Browse my computer for driver software - Let me pick from a list . . .

Use one of the listed drivers. Named 'Android .... etc'

When still fastboot issues .... It's probably hardware. Clean the connectors.
[Essential Phone Guides, News, & Discussion] CamoGeko:
Thank you for the amazing suggestions and support mate.

I finally broke through the barrier! :laugh: :cowboy:

Apparently for some reason some of my fastboot commands wouldn't work at all (I would either get a FAILED error or target didn't report max-download-size error and it would just hang on SENDING), so instead of doing "fastboot flash boot boot.img" I had to do "fastboot flash boot_X boot.img" and specify the slot I want to flash (where the X is the slot).

Also, for some reason doing "fastboot getvar current_slot" would just return a null so that wasn't working either. I had to do "fastboot set_active X" (where the X is the slot) to change the slot to whichever one I wanted to flash.

Steps below are roughly the ones I had to take:

PS. My OP5 can be flashed using a 10 year old toaster and a shoe lace, why the hell Google has to make so difficult??
[Essential Phone Guides, News, & Discussion] aer0zer0:
Lol how many adb/fastboot paths do you have in environment variables?
[Essential Phone Guides, News, & Discussion] CamoGeko:
What does that matter?

I was running it straight from a folder with ADB/Fastboot in there.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Environment variables supercede where your using it
[Essential Phone Guides, News, & Discussion] CamoGeko:
I don't have any on the laptop I was using since it isn't mine.
[Essential Phone Guides, News, & Discussion] aer0zer0:
If the essential adb/fastboot binaries were working, no need for _a or _b
[Essential Phone Guides, News, & Discussion] CamoGeko:
How do you explain that certain things work and others dont?

Doesn't make sense to me.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Lol, the essential is funky in that regard to be honest.

But if your using minimal adb/fastboot it installs environment path, essential windows driver, also installs environment path. Googles zip doesn't. It can be confusing. Google's new one, if you don't specify _a or _b, you get a error where it cant find partition boot__a for instance. And it's formatted cleaner on the output. Some minimal fastboots work better than others, I like 1.42 for most everything. HTC has their own that reboots to ruu mode after error 90.

Glad you got it going though. My setup is just using essentials adb/fastboot only, and verifying I have no other adb/fastboot paths in environment. It works well.
[Essential Phone Guides, News, & Discussion] CamoGeko:
That is exactly what I am using though. Essential ADB/Fastboot (screenshot below).

I'm still struggling to comprehend how simple commands like "fastboot getvar current_slot" are returning a null, its like the partitions aren't being detected? :confused:

However I can still select one by typing "fastboot set active X", because "fastboot set_active other" doesn't work .... and I can also flash to a slot by specifying which one I want to flash to.
[Essential Phone Guides, News, & Discussion] galakanokis:
I will chime in quickly and say my fastboot commands all changed right after flashing the October update. I haven't touched anything ADB/fastboot wise on my computers (more than one) in over a week since I redid my environments and the previous commands without appending the _a/b worked just fine. I had been flashing some Lineage test builds so I was fastboot flashing boot twrp.img quite a bit. When I gave up on the LOS I flashed the Oct fastboot images, complete wipe and start over. When I went to install the temp twrp image it took me a while as I had to go with fastboot flash boot_a to get it to work and I have never done that before. Nothing changed, I hadn't even unplugged my phone. So my amatuer sluething says something has changed with the bootloader in the October update or I am crazy or drunk or possibly all three.
[Essential Phone Guides, News, & Discussion] NLBeev:
The platform tools on Essential's website are now version 2801.

Accidentally I noticed that 'other' will cause an error when using this (newer) fastboot.exe.
[Essential Phone Guides, News, & Discussion] aer0zer0:
lol, im still on the old ones, cause i dont wanna think about slots. But it makes more sense now. if they updated to the latest google binaries.

[MENTION=3301438]geko95gek[/MENTION] that probably explains everything then. But i posted me using the old version screens. Lol, crazy. Maybe ill update them now.

Edit: It appears the windows driver is still the same. the windows driver also contains a specific set of ADB/Fastboot, and writes an environment variable, in case anybosy was wondering
[Essential Phone Guides, News, & Discussion] CamoGeko:
Maybe so, I've never in my life seen that "A/B support is outdated" message before. It totally threw me!

Okay, what about the other commands like "fastboot getvar current_slot"? Surely that should work, instead of just returning null.

Yeah I was using Fastboot 39 and it just seems totally broken to me lol

Can you test the commands I mentioned and see if they work for you?
[Essential Phone Guides, News, & Discussion] aer0zer0:
fastboot set_active other i went from a to b, then ran fastboot getvar all
[Essential Phone Guides, News, & Discussion] CamoGeko:
Thanks! Hmm weird, that didin't work for me at all lol :eek:

It would just tell me that the device doesn't have slots lmfao, or FAILED :laugh:
[Essential Phone Guides, News, & Discussion] aer0zer0:
fastboot getvar current-slot just returns the slot its on
[Essential Phone Guides, News, & Discussion] CamoGeko:
For me it didin't, it was just blank. :eek:
[Essential Phone Guides, News, & Discussion] NLBeev:
At last we solved a fastboot issue . . . To be complete, the Windows drivers of Essential doesn't install on a pc with Win10 Enterprise LTSB
[Essential Phone Guides, News, & Discussion] sash11:
Interesting discovery. Is that why when my phone is in bootloader, PC never picks up the correct driver and I have to manually install it every time...

I might just have to switch to using Ubuntu which bypasses windows driver issue)
[Essential Phone Guides, News, & Discussion] NLBeev:
Probably yes. The Windows device manager shows an error '!' there's a connection, but not working. Manually (re)activating the existing driver is needed by starting the Windows management tools.

For me that's much easier than switching to Ubuntu.
[Essential Phone Guides, News, & Discussion] CamoGeko:
I succeeded by not using the Essential ADB/Fastboot drivers at all, ended up installing the Google drivers instead. It seems to show up correctly in Device Manager.

Once again Windows is part of the problem, not the solution.
[Essential Phone Guides, News, & Discussion] aer0zer0:
That's good news, just remember to append _a and _b to everything and you will be fine.
[Essential Phone Guides, News, & Discussion] CamoGeko:
Yeah I'll try haha, I've started a log of what I've flashed and which slot.

With this phone I feel like I'm overcoming another challenge of Android, it was becoming too easy to flash stuff on the OP5 lol ?
[Essential Phone Guides, News, & Discussion] mwahahaa:
Since upgrading from Oreo 8.1 to October Pie initially things seemed to work, but when flashing the all-in-one boot.img with magisk and twrp I bootlooped and had to sideload the update again. Now I can boot but wi-fi won't turn on, I can't change security settings or get access to developer options, there are no notifications in the status bar, the home button doesn't work and other weird things. I haven't been able to find anything by searching the thread so are there any ideas about what might have gone wrong and how to fix it?
[Essential Phone Guides, News, & Discussion] mobileman88:
Try flashing the stock boot img if it works. If it does. Flash the all-in-one again. If it doesn't work reset network settings. If it still doesn't. You will need to perform a factory reset
[Essential Phone Guides, News, & Discussion] mwahahaa:
You lose internal sd card with a factory reset on the PH-1 correct? My PC can't detect the phone's storage and I'm wondering if I will lose all my Titanium backups. Could the problem be something to do with the a/b slots? I got interrupted after flashing twrp and before flashing twrp installer because of being encrypted, and the problems seemed to start from there.
[Essential Phone Guides, News, & Discussion] mobileman88:
Copy backups out with adb first. Factory reset removes everything.
[Essential Phone Guides, News, & Discussion] NLBeev:
https://xdaforums.com/showthread.php?t=3701681

In that thread you'll find Back-to-stock zips. Before factory reset you could unzip the latest on your PC and flash your PH-1 to stock.
[Essential Phone Guides, News, & Discussion] iKrautDroid:
I understand that the "red verity warning" can be removed, but what about the "orange" one that appears on every boot? Is it permanent or is there some way around it?
[Essential Phone Guides, News, & Discussion] mwahahaa:
Thanks, I have adb pulled up my pictures and Titanium backups and will try this before the factory reset.
[Essential Phone Guides, News, & Discussion] hssxda:
I just sideloaded the Oct OTA and whenever I try rooting with TWRP and Sideloading the latest Magisk the WiFi does not work. When you go to Wifi and try to turn on it won't allow it. I have tried it twice and had to sideload the OTA back each time to get it working again but I am not rooted. Anyone else having this issue?

I was following the rooting process from here: https://www.the***********.com/root-essential-phone-ph-1-using-magisk/ and using Magisk 17.2
[Essential Phone Guides, News, & Discussion] NLBeev:
You may try a Back-to-stock flash as mentioned in the thread of [MENTION=5447216]aer0zer0[/MENTION] https://xdaforums.com/showthread.php?t=3701681

Unzip the latest version on a PC and flash you PH-1 to stock.

When WiFi is working again you may flash the all-in-one boot image to get TWRP and root. It's included in the zip.
[Essential Phone Guides, News, & Discussion] sash11:
Did you try without twrp just flashing patched_boot.img from fastboot? This should have worked flawlessly. Just make sure you flash the correct image build.
[Essential Phone Guides, News, & Discussion] tech_head:
As long as the BL is unlocked you will see the range warning.

There is no way to get around it that I have seen.
[Essential Phone Guides, News, & Discussion] hssxda:
Ended up doing it this way and it worked. Thanks!
[Essential Phone Guides, News, & Discussion] nibera:
Hello,

I too have the problem of the red screen at every reboot, I have the phone with unlocked bootlader and unlocked critical partition, and I'm stock, I also have the boot.fix.red file that I do not know how to use it, could help me, thanks
[Essential Phone Guides, News, & Discussion] TT_Vert:
I already explained above. Please read it and if you don't know how to install TWRP someone below my post linked how to do that also.

Dave
[Essential Phone Guides, News, & Discussion] mwahahaa:
I have searched but haven't found a solution to the issue of twrp not taking the password to decrypt, outside of doing a full wipe or removing the android password each time you go into recovery. Is there another, permanent method (e.g. installing a differnt twrp version) that will allow a password to be entered in this situation? If not I can live with removing the pin but it is a pain to have to keep setting up the fingerprint reader afterwards.
[Essential Phone Guides, News, & Discussion] TT_Vert:
You must disable all lock screen passwords before using twrp. So boot back using stock boot.img, disable pw and try again.

Dave
[Essential Phone Guides, News, & Discussion] mwahahaa:
Thanks, I know this method and everything works but I am wondering if there is a fix that allows the requested pw for twrp decrypt to work when booting to recovery, so that I don't have to disable the lockscreen pw each time.
[Essential Phone Guides, News, & Discussion] TT_Vert:
there isnot.
[Essential Phone Guides, News, & Discussion] NLBeev:
Are you sure? I've a working TWRP version 3.2.3.0. With a correct pin (4 numbers in my xase) the data is decrypted.

The only issue is that I've to touch the keyboard slowly and exact.

Especially the return key at the bottom. Sometimes a touch doesn't work. And I need to start over again.
[Essential Phone Guides, News, & Discussion] sash11:
I can also confirm that pin decryption is working just fine when permanent TWRP is installed
[Essential Phone Guides, News, & Discussion] NLBeev:
If you've a working October version you may flash the all-in-one boot.img of Aer0zer0 wich gives you TWRP 3.2.3.0 and root.

https://androidfilehost.com/?w=files&flid=283261
[Essential Phone Guides, News, & Discussion] mwahahaa:
Am I supposed to input my lockscreen PIN? Because when I use that it is denied. I have permanent, latest twrp that works fine when no lockscreen security is set.

EDIT: works when I change lockscreen security from PIN to password. TWRP wouldn't accept the 4-digit PIN.
[Essential Phone Guides, News, & Discussion] sash11:
You have to be very vigilant when pressing the numbers in twrp. Many a time it registers a wrong number, not the one you actually press.
[Essential Phone Guides, News, & Discussion] TT_Vert:
I know on previous TWRP versions w/ the PH1 you could not encrypt and they specifically said if you did you were screwed. Things may have changed w/ the baked in TWRP, i have no idea as I'm still 2 months behind the curve.

Dave
[Essential Phone Guides, News, & Discussion] NLBeev:
Now we have it all working with version 3.2.3.0.

https://twrp.me/essential/essentialph1.html
[Essential Phone Guides, News, & Discussion] CamoGeko:
I confirm that TWRP decryption works fine for me here.

Although when I first flashed it I had to reboot after booting into TWRP for it to work.

So I booted to recovery, then rebooted to TWRP again.
[Essential Phone Guides, News, & Discussion] Bobbaloo:
Yes! I thought it was me or better, my phone l
[Essential Phone Guides, News, & Discussion] gilbertoperezx1:
hi there

How can I flash this file? thanks in advance
[Essential Phone Guides, News, & Discussion] jamiejames:
Via fastboot from bootloader.

fastboot flash boot then file name.

Then start, profit.
[Essential Phone Guides, News, & Discussion] CamoGeko:
Sometimes you have to specify which slot you want to flash to by using fastboot flash boot_X boot.img (where X is replaced by a or b).

I had to do this personally as the generic flash command wouldn't work for me.
[Essential Phone Guides, News, & Discussion] jamiejames:
I didn't have to I think because I always flash the factory image that flashes both slots.

Good to know I will remember that. Thanks for the info.
[Essential Phone Guides, News, & Discussion] NLBeev:
The 'all-in-one' boot image can be flashed the same way as a boot.img.

In TWRP when available or with fastboot.

Fastboot flash boot <name>
[Essential Phone Guides, News, & Discussion] gilbertoperezx1:
I have successfully flashed the file thanks
[Essential Phone Guides, News, & Discussion] gilbertoperezx1:
Hi people do.you if it is safe to install some.modules from.magisk? I want to try the one for the xbox one s comtroller to play games on my phone. Thanks for your time
[Essential Phone Guides, News, & Discussion] aer0zer0:
Well.....you did root now, you are using magisk......#trusttheprocess