yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] jhhoffma:
I'm having an issue installing TWRP on my PH-1 with December update.

More accurately, I can install TWRP and use it fine. However, regardless of using DazeOne's TWRP/root img or flashing TWRP directly as in this post, I can't boot to system afterward. It just keeps rebooting to recovery/TWRP.

I've also tried doing October's BTS image and using DazeOne's TWRP/root img from there, but WiFI doesn't work afterward.

Any ideas on how to fix the first problem. I've tried the TWRP>Reboot>System commands, bootloader button presses, as well as adb commands to no avail!
[Essential Phone Guides, News, & Discussion] Tiggam:
Okay I'm on PH1-OTA-QP1A.191005.014 (Nov) and cannot get TWRP to work with touch after flashing via fastboot, nor can I figure out how to properly flash Magisk without a bootloop. Any help is appreciated.
[Essential Phone Guides, News, & Discussion] MrStee97:
unfortunately for me, adb refused to find the twrp installer zip so that i could fix touch. HOWEVER, thanks to adb sideloading integrated into twrp, i sideloaded the installer and it went through fine, after which i followed the remaining steps as directed with no more issues! thanks for all the help!!!

---------- Post added at 10:17 PM ---------- Previous post was at 10:17 PM ----------

see my post i just made, im on the latest update that just rolled out
[Essential Phone Guides, News, & Discussion] GoldLink24:
Android Q

This is a quick update for anyone on android Q.

1. Follow the instructions given in this post. The only caveat is that the TWRP linked no longer has touch capability on newer roms. Use this patched TWRP "htt://androidfilehost.com/?fid=11410963190603870371" (copy the main part of the URL. New user Restrictions)

2. Use the same twrp.zip linked and flash to both partitions (The screen will shift further to the left. It doesn't affect functionality though)

3. I got Magisk working after completing the installation of TWRP and setting up my rom. Simply download the Magisk apk from their website. Open it and select the option to download zip only. Simply boot back into TWRP and flash. You're done :D

Hope this helps:good:
[Essential Phone Guides, News, & Discussion] thk_ms:
Can' The see partitions,...

Hello everybody,

I bought an used Essential ph1 and I had unlocked it and put an actual LineageOS 16 on it.

Now I want to root it by using this tutorial.

I became stopped by the step of flash the twrp.zip witch should be on the phone.

I can't see the System Partition on my Desktop-PC 8Linux) and I can't see the Data-partition by TWRP. So I can't choose the twrp-zip to flash.

Can somebody help me?

Thank's, thk_ms
[Essential Phone Guides, News, & Discussion] The Jack of Clubs:
Man, I forgot how terrible this method is and how much TWRP needs an update. I started out the day by messing up flashing the OTA by forgetting to flash the twrp installer after. I reboot and google pay complains that its wiping my cards. I have to get twrp reinstalled, but the img doesnt have working touch so I cant put in my pattern so it cant decrypt. I have to boot back up (so many fastboot commands...) and turn off my lockscreen, which deletes my fingerprints. >_< Running twrp installer just causes it to reboot into the bootloader. I dont know why.

Anybody have a Feb 2020 boot.img with twrp installed that I can flash? Its the only thing I can think will work at the moment.
[Essential Phone Guides, News, & Discussion] tguadagno:
PLEASE PLEASE PLEASE!....i am in the same boat!
[Essential Phone Guides, News, & Discussion] ipdev:
I can not get the default TWRP image to boot or a TWRP patched boot image (QQ1A.200105.032) to boot.

Magisk patched boot images will boot.

Not sure of you setup/configuration but, if you know what version is installed on which slot it will help.

Sorry all, this is going to turn into a long post. :o

To get you up and running:

Both January and February builds will boot from the February boot image. So you can flash the stock boot image from Feb. to both slots and you will boot into system (rom).

fastboot flash boot_a boot.img and fastboot flash boot_b boot.img

To determine what slot you are on, can change slightly using fastboot but, adb should be the same. Hopefully the device booted into system (rom), you can use a terminal app or adb to find out what you need to know.

getprop ro.boot.slot_suffix

getprop ro.build.version.security_patch

Using adb, I'm going to cheat and use grep to shorten the commands.

adb shell getprop | grep slot and adb shell getprop | grep patch

adb shell getprop | grep slot
[ro.boot.slot_suffix]: [_a]

adb shell getprop | grep patch
[ro.build.version.security_patch]: [2020-01-05]
[ro.vendor.build.security_patch]: []

-- Quick reboot to bootloader and set_active b --

adb shell getprop | grep slot
[ro.boot.slot_suffix]: [_b]
adb shell getprop | grep patch
[ro.build.version.security_patch]: [2020-02-05]
[ro.vendor.build.security_patch]: [2020-02-05]

Odd. I'm curious about the vendor update now ?

Truncate.

(Left for reference.)

So, I'm running January on slot a and February on slot b.

I can still boot into (TWRP) recovery on a patched January image on slot a but, not on February slot b. I tested this earlier before I tested booting January with February's boot.img

Truncate.

Left for reference. Using dd to dump partitions is documented elsewhere.

adb shell dd if=/dev/block/sde11 of=/sdcard/PH1-boot_a.img
adb shell dd if=/dev/block/sde28 of=/sdcard/PH1-boot_b.img

It's late for me, hopefully it helps you guys out.

I use adb and fastboot from.

SDK Platform Tools developer.android - Link

Truncate.

Left for reference.

For me the fastboot commands are

fastboot getvar current-slot
fastboot set_active a
fastboot set_active b
fastboot flash boot_a NameOfFile.img
fastboot flash boot_b NameOfFile.img

I uploaded the current set of file I use here.

PH-1 MediaFire - Link

I'll add the stock factory images later.

All credit to those who own them.

Note:

I use this device for testing and learning.

Not a daily use, mostly testing with custom roms and configurations.

Cheers all. :cowboy:
[Essential Phone Guides, News, & Discussion] mesh66:
Hi there

I have a problem that I cannot install twrp.

I have unlocked the boot loader and have tried the commands: fastboot devices -check!

fastboot getvar current-slot after calling the command several times I get this message: current-slot: _b

Then: fastboot flash boot_a twrp-mata.img - that does not work the cursor remains standing.

What am I doing wrong???

I also tried this, after the command: fastboot getvar current-slot this: fastboot --set-active = _a -check

Then I entered the following command: fastboot flash boot twrp-mata.img

Then the following message appears:

target didn't report max-download-size

sending 'boot' (48712 KB) ...

FAILED (remote: Requested download size is more than max allowed

)

finished. total time: 0.003s

Whats going on here???
[Essential Phone Guides, News, & Discussion] chanh2018:
If you have Feb update then TWRP doesn't work well with it.

Roll back to Jan
[Essential Phone Guides, News, & Discussion] sga999:
I'm not sure if this will help. But I have two of these essential phones, both from eBay, so they had been used, but seemingly in okay condition. I had some problems with the first one failing doing fastboot commands now and then. But generally, it worked pretty well. But with the second one, I had quite a tough time! I did get your error about max download size now and then. I'm pretty sure that rebooting my computer somehow fixed that.

However, the more major problem was that flashing an image file failed lots! And there was not a meaningful error message given. "Smaller" image files would work, but larger ones would not. It turned out that I had to hold down power and volume down for maybe 20 seconds, and it would go into fastboot mode.. again. Then the fastboot command to flash a larger file would work. You are probably not going to encounter this problem. I think the second phone just must be a defective device. But once I get everything flashed, it seems to be working well. Very strange.
[Essential Phone Guides, News, & Discussion] rignfool:
Just keep beating on it ...

And reboot the phone and the computer...

Effin Mata is a finiky pain in the butt
[Essential Phone Guides, News, & Discussion] yuanbq:
I am trying to install TWRP on my Essential phone and encounter this weird issue:

My system is running on slot B, so I flash recovery img file to slot A and successfully get into recovery.

Then I install TWRP zip file in recovery and successfully install it on both slots.

After that, I reboot to slot b and try to get into recovery again, but it just stuck in fastboot.

Switch to slot A, get into recovery, reboot to slot B from recovery, stuck in fastboot, again.

I try to flash recovery img file directly to slot B, still stuck in fastboot.

So now I end up with a working recovery on slot A with NO system, and NO recovery in slot B with my system on it which I was stuck in fastboot.

I ran through a lot of tutorials and done a ton of searching, didn't find a solution to my problem.

Please help!
[Essential Phone Guides, News, & Discussion] chanh2018:
Lots of ppl with Feb update have similar problem.

Go back to Jan and you will be ok.
[Essential Phone Guides, News, & Discussion] yuanbq:
Thanks for your reply! But what is ppl and how can I get back to Jan. :crying: Sorry this is my first time using TWRP.
[Essential Phone Guides, News, & Discussion] lynnux:
ppl = people

One simple way to get back to Jan that might work - download Jan OTA (zip) from Essential website, transfer to phone, and flash zip in twrp.

Yes, twrp isn't behaving well in Feb update.
[Essential Phone Guides, News, & Discussion] yuanbq:
I try Jan OTA and it works！Thank you！

---------- Post added at 04:01 PM ---------- Previous post was at 04:00 PM ----------

I try Jan OTA and it works！Thank you！
[Essential Phone Guides, News, & Discussion] garfnodie:
I flashed back to Jan OTA, followed all instructions all the way to installing Magisk, I still don't have touch in TWRP though. I can live without touch though so long as I can do what I need using ABD while booted into TWRP, I just want to make sure that I should still be able to flash Lineage now.

edit: so upon further investigation, I have no touch anywhere, not in TWRP, not in Android, nowhere. I just want to get everything back to bone stock and start over, not sure how to do that though.
[Essential Phone Guides, News, & Discussion] chanh2018:
TWRP without touch is known issue.

To install Lineage OS, you should follow instruction from Lineage OS (using sideload)

here's the link....https://wiki.lineageos.org/devices/mata/install
[Essential Phone Guides, News, & Discussion] seungbaekm:
Works! Thanks!

My PH1 had the lastest Stock firmware (Feb 2020). I tried to fix the TWRP touch issue, but nothing worked.

Replaced the boot.img file and roll back to Oct stock, and then boot into recovery. TWRP still exist and touch works!

Thanks.
[Essential Phone Guides, News, & Discussion] thk_ms:
Hello everybody,

I'm now able to execute the working list of page 1. i think, I do no mistake in order of the workinglist. But after installing the magisrk.zip and rebooting into LineageOS the operating system starts until I can unlock the screen by wipe. After wiping into the LineageOS-Screen the phone gets in a loop with the statement "Smartphone is starting..."

I'm at a loss - whats the mistake?

Thanks a lot, thk_ms
[Essential Phone Guides, News, & Discussion] chanh2018:
If you still need help how to install LineageOS, please post your question in Lineage OS subject (I just got my phone install LOS successfully)

This place is for TWRP installation and Root
[Essential Phone Guides, News, & Discussion] thk_ms:
hello und good morning,

no, I installed LOS sucessfully. The phone is unlocked too. I have the discribed problem in the root-process. After installing the magisk.zip via TWRP the LOS is in loop, correspondending my describltion, above.

Thanks, thk_ms
[Essential Phone Guides, News, & Discussion] thk_ms:
Hello again,

maybe I need first a basic-information. In this thread I read in many post ablout the "december-recovery" or the "januar-recovery". It means new versions of twrp? To Download twrp I only know this side: https://eu.dl.twrp.me/mata/

Whats going wrong to me and can this detail be a solution for me?

many Thanks, thk_ms
[Essential Phone Guides, News, & Discussion] chanh2018:
I downloaded TWRP files at the same site you have.

And here's what I did:

1. Backup data and flash the phone back to stock Pie level (because LineageOS 16 is Pie)

2. Enable USB Debugger (in Development Options)

3. Download and copy these files to internal storage (Download folder in phone) : LineageOS rom .zip, Gapps .zip, TWRP .zip (this is installer file not boot image file), and Magisk .zip

4. Download TWRP .img (boot image file) to your PC

5. Connect your phone to PC and reboot to bootloader (adb reboot bootloader)

6. User fastboot to flash TWRP .img file (fastboot -i 0x2e17 flash boot TWRP.img)

7. Goto TWRP Recovery mode (at this time you have not touch, you need OTG dongle and USB mouse to operate)

8. In TWRP Recovery, wipe System, Data, and Dalvik (do not wipe internal storage, you files are in there)

9. Install LineageOS ROM

10. Install TWRP installer (.zip file)

11. Reboot back to TWRP Recovery (important step - and now you should have touch in TWRP)

12. Install Gapps.zip (if you like to have Gapps)

13. Reboot the phone and it should be boot normal

14. Now put the phone back to TWRP Recovery mode and flash Magisk.zip

15. Reboot and check Magisk manager is fully operated.

I successfully did my phone this way. And I hope you'll get the same.

Good luck.
[Essential Phone Guides, News, & Discussion] thk_ms:
Hello,

thank you for your replay. I understand, that your main massega is, that you start from a the stock-ROM and you doesn't change the a/b slot, right?

I will try. :)

Thanks, thk_ms
[Essential Phone Guides, News, & Discussion] Osama12340:
I am having the no touch problem, and am trying to follow the steps in the comments. I get the message: "Failed to map file '/sdcard/'"
[Essential Phone Guides, News, & Discussion] chanh2018:
After which step did you get that error message?

And I hope you didn't forget to copy all those zip file to your phone before process or you didn't wipe internal storage.
[Essential Phone Guides, News, & Discussion] Osama12340:
It was the step of flashing the zip file while on TWRP recovery but no working touch. I had files moved over before starting. I tried to flash TWRP img to both a and b, but it only boots on b. Also letting it do a normal boot always brings it to TWRP and I can't access the internal storage to see anything
[Essential Phone Guides, News, & Discussion] chanh2018:
No, you shouldn't flash TWRP img to a and b, the command (flash -i 0x2e17 flash boot TWRP.img) will taking care what slot itself

I had the problem with flash to a and b before. If you want, let re-try and see, just do exactly the sequence that I posted.

Also, to confirm, we're talking about Essential Ph-1 phone here, right? if you have different phone, then I'm not quite sure it works.
[Essential Phone Guides, News, & Discussion] Osama12340:
Yes it is the essential PH1. the phone no longer seems to want to co operate with fastboot commands even though it is showing up as a fastboot device. adb commands once in twrp recovery seem to work, but it cant find any files I put on it. Twrp touch isnt working so i tried to follow the steps in the first comment, which is where I am running into the problem. I also tried to flash an oem update back onto it, but it isnt flashing either as the fastboot commands get stuck forever
[Essential Phone Guides, News, & Discussion] chanh2018:
My recommendation is you go back to stock Pie.

If boot loader is still unlocked, and "fastboot devices -i 0x2e17" shows phone connects to computer, then you can download stock Pie from Essential official site and issue command "flashall" in command prompt.

(I used to edit flashall.bat and add "fastboot -w" at very beginning to wipe everything)

Hope you can recover the fastboot function and then restart the whole process again.
[Essential Phone Guides, News, & Discussion] thk_ms:
hello, hello,

with your instruction i was able to root my essential ph1. *great*

Only the original-TWRP-version didn't run with the OTR an USB-mouse. I helped myself at this step with another twrp-version (with touch). It works!

Many, many thanks, thk_ms
[Essential Phone Guides, News, & Discussion] atrixgca:
Stuck on fastboot flashing of twrp img.

Hey gang,

I'm having trouble once I submit the "fastboot flash boot_a twrp-mata.img" command. I'm getting a "Sending 'boot_a'" message but then it just hangs (I've waited for more than 10 min with no result). I've attached my log here. Can someone please help? Thanks!
[Essential Phone Guides, News, & Discussion] chanh2018:
Try this version of adb

https://xdaforums.com/showthread.php?t=2588979
[Essential Phone Guides, News, & Discussion] Osama12340:
Sorry this is a bit late, but i needed android 10 to install the rom I wanted, which includes the touch problem. The solution i found was this:

While on the twrp screen, in fastboot and adb shell, enter: adb shell twrp sideload

then, have the twrp recovery zip file in the adb folder and enter: adb sideload twrp-installer-mata-3.2.3-0.zip

After, use: adb reboot bootloader

on bootloader screen, type: fastboot --set-active=slot

("slot" being the one you are not on.)

Then go back into recovery mode, where twrp should have working touch and then flash the twrp zip again in the phone with the touch now working

I hope this helps
[Essential Phone Guides, News, & Discussion] Edgehead123:
"This is a quick update for anyone on android Q.

1. Follow the instructions given in this post. The only caveat is that the TWRP linked no longer has touch capability on newer roms. Use this patched TWRP "htt://androidfilehost.com/?fid=11410963190603870371" (copy the main part of the URL. New user Restrictions)

2. Use the same twrp.zip linked and flash to both partitions (The screen will shift further to the left. It doesn't affect functionality though)

3. I got Magisk working after completing the installation of TWRP and setting up my rom. Simply download the Magisk apk from their website. Open it and select the option to download zip only. Simply boot back into TWRP and flash. You're done

Hope this helps"

this + original instructions got TWRP touch working for me.

i seemed to install the TWRP.zip successfully using the touchscreen

if i follow the instructions and switch back into my original slot, then restarting to system brings me twrp

if I disobey and do not switch back, then restarting to system brings me to the fastboot menu

*sobs
[Essential Phone Guides, News, & Discussion] Edgehead123:
I tried with January 2020 android 10 stock image. (fastboot)

I used the official twrp image and .zip from the official XDA page

Even though command prompt says the image successfully installs, and even thought I can switch to the slot the image installed on: when I press power to boot into recovery, I am brought back to the boot loader menu.
[Essential Phone Guides, News, & Discussion] Edgehead123:
So I do not know what happened in my second scenario. But I was able to succeed with my first scenario after reading 3 more guides and finding out that unlocking critical partitions was an additional step. Downloaded the most recent Magisk.zip and everything went smoothly. Sorry for the multi posting. Thanks to all the post authors and the people who make this software :)
[Essential Phone Guides, News, & Discussion] Bill720:
Solution yet?

At this point, do we have a straightforward way for folks with the January release to install the February stock rom (QQ1A.200105.032) and keep Twrp, root, and edXposed? If not, is there a way to get rid of the irritating update nags? I've already tried disabling notifications and using the ad-blocker, but the messages still appear.
[Essential Phone Guides, News, & Discussion] qnc:
Pulled out my PH-1 again after a long hiatus. I know how to use ADB and fastboot and have been using them for a long time.

I'm on the Essential February release .

I fastboot flashed the updated software and rebooted the phone into the system.

I went back to bootloader and flashed the Patched Boot Feb image.

My problems are

#1 for slot a the image flashed and i can reboot to TWRP, but it will not boot in to the system.

#2 for slot b i flash the same image, but it will only boot to the bootloader it will not boot to recovery.

any help would be appreciated.
[Essential Phone Guides, News, & Discussion] chanh2018:
If you're in Feb release, TWRP doesn't work

You have to downgrade to Jan level
[Essential Phone Guides, News, & Discussion] tguadagno:
All, it is possible to stay on the Feb release and get this installed. purchase a $5 usbA-usbC like this

https://www.amazon.com/gp/product/B07KR45LJW/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

when you get to the point where the screen is unresponsive to touch, plug a usb mouse in using this adapter.. you will be able to complete the process using the mouse.

I have done several this way and it works great.
[Essential Phone Guides, News, & Discussion] qnc:
Thanks tried that and was able to boot in to TWRP on both slots, with patched jan boot.

I tried flashing Statix magisk and got stuck on the boot logo. will re-install jan with patched boot and run stock while i figure this out.

I just sold my nexus 6 and that was so easy compared to this.

I just realized that i used the wrong magisk version. I used 18.1.

Now on stock jan android 10 with version 20 magisk. going to take a rest and try to flash a rom later.
[Essential Phone Guides, News, & Discussion] No-New-Phone:
uable to mount data in twrp

Hi guys,

coming from latest original Feb Android 10 Rom, I followed the instructions (including the downgrade, wipe etc), installed twrp on both slots, did a reboot of the recovery, and flashed lineageos 17.1 successfully. All good.

Now I'd like to install magisk on top, but when I reboot to recovery, I cannot decrypt my data partition. It is secured only with PIN. When twrp boots up and asks for decryption password, and I enter the PIN, I get the message "wrong password". I can start TWRP then, but without access to the data partition, I would have to sideload magisk.zip, and before that I'd like to know why the hack this is happening and whether I did something wrong? Any Ideas how to get out of this? Reinstallation needed? Maybe LineageOS 17.1-Problem? I didn't change slots after installing lineageos ever again, could this cause Problems?

I appreciate your comments on this matter.
[Essential Phone Guides, News, & Discussion] chanh2018:
Did you try without lock screen password?

Remove finger print id and password, and try again.
[Essential Phone Guides, News, & Discussion] No-New-Phone:
Yes, that did the trick. Stupid me.
[Essential Phone Guides, News, & Discussion] LukeSeesThrough:
I have followed the instructions and when I use the Volume keys to boot into recovery it just takes me back to the Bootloader screen and using Volume Up + Power does the same. Has anyone else had this issue?
[Essential Phone Guides, News, & Discussion] chanh2018:
What rom are you using? If you're in Feb, then no work, must roll back to Jan
[Essential Phone Guides, News, & Discussion] mlock420:
So I have to roll back to Jan to get a b slots working? Because I can't get adb commands to work...I recently bought this off eBay and I did unlock bootloader critical
[Essential Phone Guides, News, & Discussion] chanh2018:
Don't worry about slot, flashing process will take care itself. Just make sure you're in Jan stock rom before doing anything.

About adb, use the fastboot package from Essential
[Essential Phone Guides, News, & Discussion] mlock420:
Hey I've tried downloading essential adb but the file doesn't exist anymore... And what's the most updated guide.... I'm coming from a OnePlus a/b slots which I can actually say is way easier because adb is really not needed most of the time...