yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] starcms:
[MENTION=921457]munchy_cool[/MENTION]

Your post 2, the instructions in case touch is not working, needs a small correction.

After you use the adb commands to flash the TWRP installer zip and reboot to bootloader, if you immediately enter TWRP again as it says to do, touch still will not work because that slot still has TWRP.img as it's boot image which is still incompatible with touch working.

Touch won't begin working until the current slot is changed back to that noted in step 5.

So the instructions should be modified to say after the part about installing TWRP installer zip with adb command and rebooting to fastboot, instead of immediately re-entering TWRP, the fastboot change slot command (shown in step #8) should be used to change back to the slot noted in step 5. Then touch will work in the installed version of TWRP (and that's the end of the instructions except for mentioning Magisk) ;)

Lastly, since October is now out, pretty much everyone should either have October on both slots or October on the active slot and September on the inactive slot (depending on what method they used to upgrade). In either case, touch will not work in twrp.img, so in step 9 you should at the very least mention what to do if touch doesn't work (such as say see post 2). If I were you, I would go further and move the contents of post 2 directly there in post 1. Right now, it doesn't mention what to do if touch doesn't work until the very last sentence in post 1, and even there it mentions only one specific, pretty rare case when touch would not work. For everyone now following these instructions, touch will not work for them in TWRP.img.
[Essential Phone Guides, News, & Discussion] munchy_cool:
the instructions in post 2 do mention to change slot to that noted in step 5.
[Essential Phone Guides, News, & Discussion] starcms:
Yes, but they say to do it via the touchscreen in TWRP. If the touchscreen wasn't working in the inactive slot with TWRP.img, it still will not be working after flashing TWRP.zip (via the adb command). Therefore it is not possible to boot into TWRP, click reboot, and click to switch to the active slot as currently stated. The switch back to the original slot as stated in step 5 must be done using the fastboot command in step 8.

The instructions in post 2 end with "and go back into TWRP. Check if touch is working and then set your slot to one noted in step 5. " The touchscreen won't be working yet, not until the system is first switched back to the slot noted in step 5 using the fastboot command in step 8.

I hope I'm being clear and you understand where I'm coming from now. I'm just trying to help make the instructions 100% clear and correct. That one thing is the only little mistake, but it could throw people unfamiliar with the process for a loop.
[Essential Phone Guides, News, & Discussion] munchy_cool:
Thank You and Fixed.
[Essential Phone Guides, News, & Discussion] starcms:
No problem. But just to be absolutely clear, if touch was not working in the first place, it will definitely not be working there yet. It's an impossibility.

So the current, edited instructions of "and go back into TWRP. Check if touch is working and then set your slot to one noted in step 5.

If touch is not working use fastboot to change the slot. and then reboot into recovery. "

Would be much clearer as:

"to reboot to fastboot. Switch back to the slot noted in step 5 (of the first post) using the instructions in step 8 (of the first post). Then from fastboot you can choose Recovery Mode to boot into TWRP (where the touchscreen will now function) or choose Reboot System to boot into Android."

Also in step 9 of the first post (if you don't want to completely replace the current instructions with contents of post 2, since no one currently following these instructions with an up-to-date phone could possibly have touch working in TWRP.img) I would add the sentence saying "If the touchscreen doesn't function, skip to instructions in post 2 below" after "You should now boot to TWRP".

I'm not trying to be a smartalec, I just know how many dozens of questions I answered in the new official TWRP thread regarding just this one single issue. And you obviously put alot of effort into making these instructions, which I think is fantastic, but since touch not working in TWRP.img is basically a certainty at this point, the instructions should be just as clear on that point and not treat it as a side issue.

Anyway, if you choose to, all you have to do is copy and paste from this post to your instructions (I did the hard part for you :) ). In the interest of the Essential community, I hope you do, but I won't bother you any more about it either way. And no, you do not need to credit me, they are your instructions. Best regards!
[Essential Phone Guides, News, & Discussion] munchy_cool:
Thanks and done. :highfive:
[Essential Phone Guides, News, & Discussion] rignfool:
If you were feeling saucy... Since we all know how to really fix touch... Why not just put... In this thread... An updated TWRP.img that will work with the current partitioning...

It doesn't have to boot any ROM... Just as a TWRP transitioning device?
[Essential Phone Guides, News, & Discussion] starcms:
Stop stalking me on XDA and trying to insult me. It's wierd and kinda freaky (does it turn you on?), especially considering you don't even own an Essential. Now you are not going to crap all over this very helpful thread too, so as of now, you have been added to my ignore list. Last I ever hear from you, stalker.

I'm very sorry about this [MENTION=921457]munchy_cool[/MENTION]. And thanks for incorporating some of my suggestions! :highfive:
[Essential Phone Guides, News, & Discussion] rignfool:
Whoa princess... You ain't special...

I ain't stalking you... I've had an essential for over a year... Been here and discord... And reddit

EDIT : nah...

You're a damn troll... Taking something where people are genuinely worried about their devices... And screaming at them like this is child's play...

Oh... And prefacing with "Not trying to sound like a douche... But". Makes you sound like a douche...

I hope you read this...
[Essential Phone Guides, News, & Discussion] munchy_cool:
please take your trolling/hate/games to PMs please.

Thanks
[Essential Phone Guides, News, & Discussion] arthur_shug:
Touch not working

Hi there, i tried install twrp, but after touch is not working

what i do:

unlock bootloader

flash android 9

and then

fastboot getvar current-slot

say slot a

i use command fastboot flash boot_b twrp-mata.img then reboot recovery, touch is not working, now i put installer to device memory and use command adb shell twrp install /sdcard/

twrp-installer-mata-3.2.3-0.zip reboot to bootloader and reboot to recovery

Touch not working anything what i can do?
[Essential Phone Guides, News, & Discussion] rignfool:
Either flash a back to stock so that both a and b slots are on new firmware... Or... Flash TWRP to the current slot, then current boot.img, then the TWRP installer
[Essential Phone Guides, News, & Discussion] arthur_shug:
first step fastboot flash boot twrp.img

second fastboot flash boo boot.img?
[Essential Phone Guides, News, & Discussion] starcms:
Ignore what [MENTION=3290808]rignfool[/MENTION] said. It is completely false and incorrect. He clearly does not understand what causes touch to stop working during TWRP installation and therefore is clueless on how to fix it (basically like talking to someone at tech support who is reading from a script).

Anyway, it sounds like all you forgot to do was to switch back to your original slot, which sounds like it was slot a, at the very end. One very tiny, simple mistake, easily fixed with one fastboot command.

So assuming you haven't changed anything from the time you made your post, simply issue the following command from fastboot (assuming slot a was your active slot which sounds like it was)

If unfortunately you did flash anything else from the time you made your original post, you'll need to flash the stock original boot.img to slot a using fastboot and restart the instructions from the beginning (not forgetting the final step this time :) )

fastboot --set-active=a

If fastboot complains, use this command instead:

fastboot --set-active=_a

(It depends on the version of fastboot you have installed)

That should do it!

[MENTION=921457]munchy_cool[/MENTION], That last step is really easy to miss in the current instructions (if you are following the version for when touch doesn't work). Anyone currently following these instructions will have October or newer (or perhaps September) installed, meaning that touch will not work for anyone during the installation of TWRP. Maybe consider dropping the whole part relating to installing with touch working? Even if someone somehow still had August or older installed (and therefore touch would work during installation), the instructions for touch not working would still work just fine.
[Essential Phone Guides, News, & Discussion] munchy_cool:
Thank you for helping other peeps.

As for missing the last step, well it's mentioned there and if people dont read and miss it I cant do anything.

The instructions are pretty clear now if anyone takes the time to read. :highfive:
[Essential Phone Guides, News, & Discussion] rignfool:
Dude... Keep my name out of your mouth...

---------- Post added at 02:03 PM ---------- Previous post was at 01:50 PM ----------

Here... An October boot image with TWRP already injected...

Flash this, reboot to recovery, tell [MENTION=2557531]starcms[/MENTION] to shove his attitude, profit

https://drive.google.com/file/d/1TkdByZvhCQWCaoskOIHXLuTKb3EQfRww/view?usp=drivesdk
[Essential Phone Guides, News, & Discussion] TacoLoco:
Great guide, but I have the problem, that after flashing recovery img and boot into it (no touch - check) I cannot install recovery zip via adb (no devices/emulators found).. Can you help me please?

Edit:

Flashed the boot.img [MENTION=3290808]rignfool[/MENTION] posted above to slot b and now I got twrp in both slots, but in slot a touch still doesn't work.. Also flashed twrp zip afterwards but twrp in slot a remains without touch.. Is this correct? Or should I flash the boot.img (the one with twrp) also in slot a?
[Essential Phone Guides, News, & Discussion] munchy_cool:
if the boot.img is from october patch and you are on october patch then you can flash it on slot a as well.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Sounds like slot a doesn't have October firmware
[Essential Phone Guides, News, & Discussion] kakabobo:
how to flash oct firmware to both slot ?

using bts
[Essential Phone Guides, News, & Discussion] munchy_cool:
yes, bts flashes to both slots
[Essential Phone Guides, News, & Discussion] sonic0504:
Can twrp decrypt data again like in 7.1?
[Essential Phone Guides, News, & Discussion] munchy_cool:
thats a question for the twrp thread.
[Essential Phone Guides, News, & Discussion] xDark_:
For post 2 w/ no touch, doing "adb shell twrp install /sdcard/ twrp-installer-mata-3.2.3-0.zip" would give me a "failed to map file" error.

Removing the /sdcard/ portion (so just typing "adb shell twrp install twrp-installer-mata-3.2.3-0.zip") flashed successfully though.

Weird lol.
[Essential Phone Guides, News, & Discussion] Dream Lin:
I can't use fastboot --set -b

Why?i will tell you more about it if you reply me.

:(
[Essential Phone Guides, News, & Discussion] munchy_cool:
you need help and are trying to bait me into replying to you ..damn ..thats a first
[Essential Phone Guides, News, & Discussion] Dream Lin:
I am helpless.......that's not interesting,right?

OK,when i use fastboot --set -b,it tips me

fastboot:option requies an argument --b

so strange...so do you know what should i do now?
[Essential Phone Guides, News, & Discussion] loctuantran:
No such file or directory error even I put them the TWRP img file together in platform tool folder. I also copy the folder path to make sure that it's correct to but error still happens
[Essential Phone Guides, News, & Discussion] munchy_cool:
read point 8 again, and you will realize your command is incorrect.
[Essential Phone Guides, News, & Discussion] munchy_cool:
does path have spaces?

on windows do dir /p and in terminal ls -l to check the file name
[Essential Phone Guides, News, & Discussion] Dream Lin:
But i can use fastboot --set -a,when i use fastboot --set -b slot,it still current slot to a.
[Essential Phone Guides, News, & Discussion] ipdev:
So you confused me a little too.

The commands will change slightly depending on computer and version of fastboot.

Most command line utilities have a cheat sheet.

--? -? --h -h -help or --help

fastboot --help

fastboot -h

Just pay close attention to spaces, underscores and dashes.

syntax makes a difference.

For me:

Mac OSX 10.13.6

fastboot version 28.0.1-4986621

Installed as /opt/sdk/platform-tools/fastboot

$ fastboot getvar current-slot
current-slot: _b
Finished. Total time: 0.002s

$ fastboot set_active a
Setting current slot to 'a' OKAY [ 0.158s]
Finished. Total time: 0.160s

$ fastboot getvar current-slot
current-slot: _a
Finished. Total time: 0.003s

PS.

I don't remember having to ./fastboot on Mac.

Sure years ago, when I had platform-tools in root and was too lazy to put it in the path, I had to /platform-tools/fastboot

Why I thought that was easier :confused:
[Essential Phone Guides, News, & Discussion] Dream Lin:
Oh.......i forgot it,thanks your words.

The problem is i can't touch it.i will try to solve it,thanks.:)
[Essential Phone Guides, News, & Discussion] RUGGNATION:
Hi All,

Running into an issue where i was able to fastboot devices, get slot (B), then went to flash and it said: failed (remote: unknown command). Tried to launch recovery and now its gone, no twrp, no stock. Went back in to try and start over but fastboot devices just brings back a bunch of question marks now and getvar slot returns back a string of numbers and letters. Android still boots up fine but i dont currently have a recovery.

https://i.imgur.com/EnSp8jF.png

Anyone know a way to clear this up, start over, or see where i went wrong? TIA
[Essential Phone Guides, News, & Discussion] munchy_cool:
you still have stock recovery.

essential is a pain in the a$$ to flash, just try the command again and see if it works.

else try a different usb cable, different port or a different computer
[Essential Phone Guides, News, & Discussion] whitewarrior11:
Hello folks!

First of all, thanks for this guide :)

I managed to have a custom ROM running, but now, my recovery is back to stock and my custom ROM is not rooted :(

I followed the guide with these steps (roughly):

- Unlocked bootloader

- Copy TWRP zip and Magisk zip to SD card

- Reboot into bootloader

- Check fastboot (OK)

- Flash twrp on the other partition

- Set other partition as active

- Reboot into recovery (touch is not working so reboot into bootloader)

- Flash TWRP.zip to both partitions

- Reboot into recovery (touch is not working so reboot into bootloader)

- Set first partition as active

- Reboot into recovery (touch works!)

- Flash custom rom + magisk

- Reboot into system

Now my custom ROM is working (Lineage 16.0) but no more TWRP or Magisk root anymore.

What did I do wrong? :)

Thanks in advance for helping!
[Essential Phone Guides, News, & Discussion] munchy_cool:
flash custom rom + twrp zip

boot into android

reboot back into twrp, flash Magisk

reboot system

every time you flash a custom rom or kernel, you will loose twrp as recovery is part of boot.img (aka kernel) for ab devices.
[Essential Phone Guides, News, & Discussion] whitewarrior11:
Thnx :) I will try this asap!
[Essential Phone Guides, News, & Discussion] Kal84:
hello all hope u can help me i had a serious error n i did not see the partition if it was A or B and erase the system now the phone only starts in TWRP :(
[Essential Phone Guides, News, & Discussion] munchy_cool:
get current slot

and change it to opposite of what you get and then reboot
[Essential Phone Guides, News, & Discussion] chemical1der:
Recently bought and very much love my PH-1 but man is this an incredibly difficult phone to flash. Running Stock 9.0 with March security update.

1. I've unlocked my boot loader (unlock + critical_unlock)

2. Have proper ADB/Fastboot on two different PC's (with Essential drivers on both)

3. Followed munchy_cool's incredibly clear instructions

4. Used four different USB A to C cords on two separate Windows PC's

5. And I STILL cannot flash TWRP to slot b (I am currently on slot a) or flash a patched boot.img to root (with Magisk) stock.

Am I missing something obvious? Is the phone really this finicky with cords/adb and fastboot environments? I really want to keep my PH-1 but might jump to a OnePlus for ease of modding.

Thanks in advance for the help!
[Essential Phone Guides, News, & Discussion] swiftbones74:
This phone is actually pretty simple to mod when you get past the initial ab hump. Its going to be pretty much the same with a oneplus since that's an ab as well.

*Edit* The way I do it from stock (root) is to flash one of the all-in-one magisk-twrp-boot.img's to inactive slot. Something like fastboot set active other_ then fasboot flash boot magisk-twrp-boot.IMG and then repeat the first command again then I repeat the second command. There are other ways but I find this the most simple. This works like a charm if you have essential's drivers installed on your windows machine and run fastboot from the unzipped back-to-stock folder on your desktop or whatever directory its in. I highly recommend getting rid of random adb and fastboot installation's on your computer first. So just go to the bts forum download latest bts, unzip with 7-zip and get er done.
[Essential Phone Guides, News, & Discussion] chemical1der:
Thanks, [MENTION=8135223]swiftbones74[/MENTION]! I tried the all-in-one's as well. My problem is every time I try to write to the inactive slot (b in my case) I get an "error flashing partition" message. I have configured and reconfigured adb/fastboot innumerable times (along with other tips I've gathered from the threads). It's driving me cray cray. I am not sure if my b partition is somehow borked or perhaps the boot loader is the problem? regardless, it's a shame because I love this phone but can't remember the last time I ran anything plain stock.

Anyway, I will keep at it and appreciate your help.
[Essential Phone Guides, News, & Discussion] swiftbones74:
Hmm maybe [MENTION=5447216]aer0zer0[/MENTION] can come over from 6t land and give you a hand? He's kinda the master with this stuff IMO.
[Essential Phone Guides, News, & Discussion] munchy_cool:
its the phone ..I had major issues with Essential flashing stuff via fastboot.

one day it took me 8 hrs, and 3 computers to install factory firmware from fastboot, which is when i decided to day bye bye to mata.
[Essential Phone Guides, News, & Discussion] chemical1der:
Thanks [MENTION=921457]munchy_cool[/MENTION]. The irony for me is I sold my Pixel 2 precisely because I hated the A/B partition set up for modding. Yet here I am again.... At least it was easy to flash the partitions on that device. This has been a nightmare. Especially frustrating since I've been flashing custom ROMs since the Droid Incredible and have always been able to get myself out of trouble. I'm gonna try my work computer and purchase one more USB cable before giving up and moving on as well.

Edit: 8 months after putting my PH-1 in an office drawer I dug it out three days ago to try and resurrect it. Lo and behold, I was able to flash TWRP and get it back to stock! Not sure what was different this time around. Anyway, thanks again [MENTION=921457]munchy_cool[/MENTION].
[Essential Phone Guides, News, & Discussion] munchy_cool:
A/B is easy once you get the hang of it.

i have been flashing custom roms since 2009 as well and no phone has given me as much pain as Essential.

I used the same cable, and same computer to flash Pixel 2, Moto X4, moto g5 plus and it was only essential which had issues so it had to go ..
[Essential Phone Guides, News, & Discussion] tuanban:
why my phone after flash twrp successfully and boot into recovery report again: no commad
[Essential Phone Guides, News, & Discussion] spawnz01:
My Quick Guide

Thanks for the guide bro (still was hard to understand clearly). I banged my head against the phone and troubleshooted for about 6hrs each for two days. Literally read over 80 different posts/threads/sites and especially a bit challenging cause I've been using iPhone since iPhone 3GS. My only other foray into Android was a Moto G5+ and it was a breeze to work with lmao.

If anyone else ends up reading this, the key is to understand that we have 2 partitions to work with. Since we can't flash recovery directly like other phones, the goal is to flash the other partition's boot image, change active boot slot, then standard boot directly to the boot partition we just flashed, then from here install the zip via adb CLI (this will write both partition recoveries), then back to bootloader, set active boot slot back to A, standard boot--this time should go back into your ROM/OS normally. Now go back into recovery and this time it should be TWRP and let you touch stuff (back in A, remember when it wasn't before). From here go to Install -> pick your Open GApps and whatever else your heart desires.
[Essential Phone Guides, News, & Discussion] TheDude1998:
always go back to this thread when i forget the commands after an update thank you very much!
[Essential Phone Guides, News, & Discussion] hawklen:
Thanks for the guide, I got the no touch problem, did step 2, still didn't have touch. So back to bootloader, changed the slot to b (I originally changed it to a) and now touch works. Oh yeah, edit. On latest 2019 pie w/ july update.

Good work!
[Essential Phone Guides, News, & Discussion] ToppestOfDogs:
I have no touch in TWRP, and it gives me the error "Unable to locate zip file '/sdcard/ twrp-installer-mata-3.2.3-0.zip'." when I try post 2's fix even though I have that exact file on the internal storage.

Edit: Nevermind, it was the lockscreen I still had on.
[Essential Phone Guides, News, & Discussion] elonmusketgood:
Hi, I've been trying to use this tutorial, but when I try to reboot to recovery from the bootloader menu, it just goes back into the bootloader menu.

This is all of the outputs:

.../flash/other# fastboot --version
fastboot version 1:7.0.0+r33-1
.../flash/other# fastboot getvar current-slot
current-slot: _b
finished. total time: 0.001s
.../flash/other# fastboot flash boot_a twrp.img
target reported max download size of 536870912 bytes
sending 'boot_a' (6 KB)...
OKAY [ 0.088s]
writing 'boot_a'...
OKAY [ 0.027s]
finished. total time: 0.115s
.../flash/other# fastboot --set-active=_a
Setting current slot to '_a'...
OKAY [ 0.028s]
finished. total time: 0.028s

Using Debian 9, and fastboot from the debian repositories. I used flashall before this.
[Essential Phone Guides, News, & Discussion] kittygotwet:
anyone have a fix for flashing being stuck? i'm getting this issue and cant proceed.
[Essential Phone Guides, News, & Discussion] Slipknot8Wwe:
So I wanted to share something with everyone STILL having issues with the essential phone twrp... Let's make it simple k..

Download October's official build from here

https://www.essential.com/developer/current-builds

Now.. download this boot.img from here..

https://drive.google.com/file/d/1TkdByZvhCQWCaoskOIHXLuTKb3EQfRww/view

Next.. extract the OFFICIAL firmware and remove the boot.img that comes with it and replace it with the one that you downloaded..

Fastboot back to stock with the new boot.img once your at the last step (erase user data) don't flash it just fastboot reboot.

When your all booted up back to stock boot into bootloader then go to recovery and Wala! Working TWRP! Flash away! Remember to put the twrp installer on your phone for when flashing ROMs.
[Essential Phone Guides, News, & Discussion] rogosteve:
Does this TWRP allow for decryption? I can not get into TWRP when fingerprint/password is enabled.
[Essential Phone Guides, News, & Discussion] rignfool:
Not on 10