Official TWRP 3.2.3-0 for Essential PH-1

[rignfool]

Ya know... I know there are work arounds. There shouldn't have to be. The maintainer of TWRP for this phone could at the very least build one final version that fully supports the final release from Essential. Yes, I know it's all volunteer supported and there's no obligation... But our maintainer hasn't done anything with TWRP and this phone in 2 years. My Nexus 9 tablet that's 5 years old has a TWRP update last year to stay current with TWRP in general, not to address any device specific issues.

It'd be nice to have support from the maintainer, or someone else to step up and take over. I would if I knew anything about compiling anything.

Unfortunately that's the problem with the enthusiast crowd... When it's not fun... The work stops...

And well... When it's your baby that totally craps the bed... Then depression sets in

 

[Bofahad]

Heads up: if anyone has an error making a backup, just delete the folder /data/per_boot, then make a backup

Finally
you are AMAZING how you knowed that ??

 

[SykkNyzz]

Finally
you are AMAZING how you knowed that ??

It's usually in the last line of the log that shows what stops the backup from happening. (You can find the log under TWRP subFolder)

 

[Bofahad]

It's usually in the last line of the log that shows what stops the backup from happening. (You can find the log under TWRP subFolder)

 

[mizzike32]

trying to understand my error

Hello all. I recently decided that I want to put a custom rom on my essential phone which was stuck on the last official February image (PARTITION B).

just so that everyone understands me, I've read a lot of information on this particular thread and I do understand there are 2 partitions and that essential does it differently than google because of how the recovery is implemented.

like stated above i figured out I was on partition B with Feb. 2020 image.

I was in the process of flashing TWRP and then eventually trying out P.A. Quartz.

I use an 8 digit pin.

I was not rooted and have no intention to root even on the custom rom.

YES I unlocked the bootloader and had the proper essential drivers on windows.

I was following TWRP's instructions...(yes now i know its probably the last thing i should have done because of the age of this twrp image)

Everything was fine up until I got to the part of executing the command to flash the twrp image.

I got an error and the command didn't work.

I was able to easily execute the command to set partition A active or partition B active. no problem switching either or.

The problem was resetting back to B partition (I was trying to flash TWRP to partition A because B was in use with Feb. 2020)

After setting B active again when I tried to log back into stock android, I could no longer swipe up the app drawer and I could no longer get into settings. Android was acting all funny.

I restarted the phone and set the A partition active again....this time I decided to boot on this partition. Obviously this went nowhere and I ended up in the factory recovery screen. I either can factory reset the phone or go back at this point.

I decided to reset to factory. Turns out the image was from the Essential official August 2019 Android Pie image. I booted into it and have not done anything yet.

I'm hoping someone here has some friendly advice on what to do. I am aware of the difficulties of this older version of TWRP but I really want to use something other than stock essential images.

Please help and Thank You.

 

[rophiroth]

Slot are a p#$n in the arsh... I was in an unofficial Los17. 1, install the official and try to flash gapps and got a lot of problems... Those problems would never come up together... We screw with kernel... Still don't want to try having twrp on both slot like I've before.

I don't understand why slot can be useful...

 

[gavinfernandes2012]

Please help and Thank You.

Have you made sure the twrp image you downloaded isn't corrupted?

Also if you can, try using a USB 2.0 cable/port/adapter between your phone and your computer. For me, anything with USB 3.0 causes all Fastboot commands to fail most of the time.

Your case does seem odd though considering some Fastboot commands work.

 

[DAE1964]

Hello all. I recently decided that I want to put a custom rom on my essential phone which was stuck on the last official February image (PARTITION B).

just so that everyone understands me, I've read a lot of information on this particular thread and I do understand there are 2 partitions and that essential does it differently than google because of how the recovery is implemented.

like stated above i figured out I was on partition B with Feb. 2020 image.

I was in the process of flashing TWRP and then eventually trying out P.A. Quartz.

I use an 8 digit pin.

I was not rooted and have no intention to root even on the custom rom.

YES I unlocked the bootloader and had the proper essential drivers on windows.

I was following TWRP's instructions...(yes now i know its probably the last thing i should have done because of the age of this twrp image)

Everything was fine up until I got to the part of executing the command to flash the twrp image.

I got an error and the command didn't work.

I was able to easily execute the command to set partition A active or partition B active. no problem switching either or.

The problem was resetting back to B partition (I was trying to flash TWRP to partition A because B was in use with Feb. 2020)

After setting B active again when I tried to log back into stock android, I could no longer swipe up the app drawer and I could no longer get into settings. Android was acting all funny.

I restarted the phone and set the A partition active again....this time I decided to boot on this partition. Obviously this went nowhere and I ended up in the factory recovery screen. I either can factory reset the phone or go back at this point.

I decided to reset to factory. Turns out the image was from the Essential official August 2019 Android Pie image. I booted into it and have not done anything yet.

I'm hoping someone here has some friendly advice on what to do. I am aware of the difficulties of this older version of TWRP but I really want to use something other than stock essential images.

Please help and Thank You.

TWRP has problems with the February update. I would revert to the January or earlier build.

Here's some info that's a must read.

https://mata.readthedocs.io/en/latest/

Sent from my PH-1 using XDA Labs

 

[mizzike32]

TWRP has problems with the February update. I would revert to the January or earlier build.

Here's some info that's a must read.

https://mata.readthedocs.io/en/latest/

Sent from my PH-1 using XDA Labs

Thank you for the link!

The first custom rom that I was going to try out with the essential phone was paranoid android quartz.

Their instructions say that the january vendor-QQ1A.200105.088 AOSP image needs to be flashed on both slots.

after that...
."Instructions:
Download the latest build
Boot into bootloader and flash the January firmware and AOSP vendor using the script inside.
Boot the latest image of TWRP
Flash the latest build and TWRP installer
Reboot"

i really don't know what to do first.

Partition A currently has the August 2019 9 PIE build installed (working normally)

Partition B currently has the February 2020 Q 10 build installed (not working normally)

and to top it all off i don't need to remind anyone of the touchscreen issues between the august and september 2019 builds that I was reading about for hours yesterday.

---------- Post added at 01:50 PM ---------- Previous post was at 01:17 PM ----------

Have you made sure the twrp image you downloaded isn't corrupted?

Also if you can, try using a USB 2.0 cable/port/adapter between your phone and your computer. For me, anything with USB 3.0 causes all Fastboot commands to fail most of the time.

Your case does seem odd though considering some Fastboot commands work.

I checked the md5 and sha256 numbers and successfully verified that they match the image I downloaded.

Also I was not using USB 3 when doing the process.

I was using a usb A (Windows 10 computer usb 2.0 connector) to usb C (essential phone) cable to do the fastboot commands.

I'm wondering if my 8 digit pin code had something to do with it. IDK.

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

in regards to flashing and sideloading the essential ph-1 i just read this on the downloads page of the essential official website:

"Some users have reported issues when flashing or sideloading using a USB 2.0 cable. The cable included with PH-1 is USB 2.0 and is primarily intended for charging. If you're flashing or sideloading PH-1, we recommend using a high-quality, spec-compliant USB 3.0 (or higher) cable."

The cable I was using was purchased directly from google when i bought my nexus 6P USB A to USB-C.

The 2 windows machines I own have USB 3.0 ports but NO USB-C ports (Their from the 2011/2012 sandy bridge/ivy bridge era)

 

[DAE1964]

Thank you for the link!

The first custom rom that I was going to try out with the essential phone was paranoid android quartz.

Their instructions say that the january vendor-QQ1A.200105.088 AOSP image needs to be flashed on both slots.

after that...
."Instructions:
Download the latest build
Boot into bootloader and flash the January firmware and AOSP vendor using the script inside.
Boot the latest image of TWRP
Flash the latest build and TWRP installer
Reboot"

i really don't know what to do first.

Partition A currently has the August 2019 9 PIE build installed (working normally)

Partition B currently has the February 2020 Q 10 build installed (not working normally)

and to top it all off i don't need to remind anyone of the touchscreen issues between the august and september 2019 builds that I was reading about for hours yesterday.

---------- Post added at 01:50 PM ---------- Previous post was at 01:17 PM ----------



I checked the md5 and sha256 numbers and successfully verified that they match the image I downloaded.

Also I was not using USB 3 when doing the process.

I was using a usb A (Windows 10 computer usb 2.0 connector) to usb C (essential phone) cable to do the fastboot commands.

I'm wondering if my 8 digit pin code had something to do with it. IDK.

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

in regards to flashing and sideloading the essential ph-1 i just read this on the downloads page of the essential official website:

"Some users have reported issues when flashing or sideloading using a USB 2.0 cable. The cable included with PH-1 is USB 2.0 and is primarily intended for charging. If you're flashing or sideloading PH-1, we recommend using a high-quality, spec-compliant USB 3.0 (or higher) cable."

The cable I was using was purchased directly from google when i bought my nexus 6P USB A to USB-C.

The 2 windows machines I own have USB 3.0 ports but NO USB-C ports (Their from the 2011/2012 sandy bridge/ivy bridge era)

I also use the cable from my Nexus 6p without any problems.
I would flash January stock from Essential, then proceed with the custom ROM.
Completely removing the February build all together.

Sent from my PH-1 using XDA Labs

 

[gavinfernandes2012]

Thank you for the link!

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

in regards to flashing and sideloading the essential ph-1 i just read this on the downloads page of the essential official website:

"Some users have reported issues when flashing or sideloading using a USB 2.0 cable. The cable included with PH-1 is USB 2.0 and is primarily intended for charging. If you're flashing or sideloading PH-1, we recommend using a high-quality, spec-compliant USB 3.0 (or higher) cable."

The cable I was using was purchased directly from google when i bought my nexus 6P USB A to USB-C.

Yeah I don't know why that is on the website, but personally it's been the opposite with my ph1, tested with several devices cords and operating systems and the only discerning factor was tnat USB 2 worked and 3 didn't for me.

But yes as DAE1964 mentioned (and I completely forgot, oof) Feb stock has problems with TWRP.

Also if you'd like a starting point and Fastboot is working, use that and download the Fastboot image from essential and flash it to both slots and follow the paranoid android instructions from there.

If Fastboot is still giving you trouble, you could download the OTA and flash it from the stock recovery which should work (flash it twice, with a reboot in the middle so it's on both slots then)

Also if you need help with ADB commands just @ me or pm me and I'll reply here


Edit: also, your 8 digit pin might only cause problems if you can't access your internal storage from recovery, and if your zips are all on internal storage...
Using ADB sideload does sidestep this issue though

 

[mizzike32]

after a long day today after flashing the january images, I was able to "flash boot" into the opposite slot and instead of getting mad (like i did yesterday with touch not working in twrp) I just decided to use an otg adapter and use a mouse to interact with twrp. It's not ideal but it works.

i now have twrp in both slots.

now I have to figure out how to get Quartz properly flashed.....time to take a nap.

THANK YOU TO EVERYONE WHO REPLIED TO MY POSTS AND EVERYONE WHO HAD SUGGESTIONS AND RECOMMENDATIONS. I TRULY APPRECIATE IT.

 

[mizzike32]

i'm a boob

after a long day today after flashing the january images, I was able to "flash boot" into the opposite slot and instead of getting mad (like i did yesterday with touch not working in twrp) I just decided to use an otg adapter and use a mouse to interact with twrp. It's not ideal but it works.

i now have twrp in both slots.

now I have to figure out how to get Quartz properly flashed.....time to take a nap.

THANK YOU TO EVERYONE WHO REPLIED TO MY POSTS AND EVERYONE WHO HAD SUGGESTIONS AND RECOMMENDATIONS. I TRULY APPRECIATE IT.

all i had to do was restart back into recovery. twrp is working nice with touch now.

i never took that nap, i want to get this ish done!

 

[Darkside1984]

Having an error that I think is quite common but I expose it here in case someone has the solution:

Running Paranoid Android last compilation (over January stock) and official TWRP from this post (zip flashed). I can't get the backup to end. Close to 100% it always get 'createTarfork() process ended with ERROR: 255'.

Suggestions?

 

[temporarium]

Having an error that I think is quite common but I expose it here in case someone has the solution:

Running Paranoid Android last compilation (over January stock) and official TWRP from this post (zip flashed). I can't get the backup to end. Close to 100% it always get 'createTarfork() process ended with ERROR: 255'.

Suggestions?

Have a look here:
https://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462/post82030011

 

[Darkside1984]

Have a look here:
https://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462/post82030011

FYI, for me the cause of this error (although on an Essential Phone PH-1), is an empty /data/per_boot directory. Once deleted, the backup completes successfully. For some reason, it's always recreated, so I have to delete it prior to every backup.

It works. Thanks!! :fingers-crossed:

 

[JohnnyChim]

can I use the TWRP with stock rom?

My device wont boot after flashing TWRP 3.2.3.0

 

[mlock420]

can I use the TWRP with stock rom?

My device wont boot after flashing TWRP 3.2.3.0

You have to be on January ota stock rom February doesn't work with twrp

 

[JohnnyChim]

Still I am not able to flash TWRP. I am already in stock january build. After I flash the TWRP I press "go into recovery". My device only reboot into the fastboot. But I am able ot flash lineage official recovery normally.

Can anyone help me? I want to flash evolution x.

 

[SanoFeketeSK]

OK I FIGURED IT OUT, HOW TO GET TWRP TOUCH WORKING FOR EVERYONE

Explanation of issue:

I finally figured this out after thinking about it too long. I was wrong about some Essentials possibly having different touch screens/digitizers. If you don't want to give yourself a headache, just skip to the instructions below.

The reason it worked for some people, including myself, is we followed the directions and flashed TWRP.img to the non-active slot. The non-active slot for us had August still on it (including the August version of hyp and rpm) which is why touch worked in TWRP.img. Once the TWRP zip installer is used, however, TWRP is installed to the ramdisk of the current boot image, and therefore touch works with September when switching back to the active slot (TWRP.img is built with the boot image of August and hence requires August or older hyp and rpm partitions for touch to work with it, BUT the TWRP zip installer installs TWRP to the ramdisk of the current boot image (kernel), and therefore is compatible with any boot image -- it isn't built on a specific boot image to begin with -- it "injects" your boot image with TWRP and is compatible with any boot image: past, present, or future). So the following instructions will always work to install TWRP with working touch.

How to get touch working in TWRP:


a) Make sure you have September on the active slot (and latest rpm and hyp partitions if you messed with those) and have temporarily removed your lockscreen pattern/pin/password. Also make sure you have the stock boot image on your active slot (in case you had previously installed Magisk). Boot into fastboot.
b) Switch slots and flash twrp-3.2.3-0-mata.img to the non-active slot
c) Boot into twrp
d) Since touch doesn't work in TWRP, issue the following commands from your PC to install the TWRP installer since you can't do it by touching the screen:

adb shell twrp sideload

adb sideload twrp-installer-mata-3.2.3-0.zip

e) Exit back to bootloader after sideload is complete using command:

adb reboot bootloader

f) From bootloader, switch back to Active (September) Slot

Congratulations, you are done and have installed TWRP with working touch on to your active slot!
--When you boot into recovery, you will boot into TWRP and your touch will work.
--When you boot into Android, you can add your lockscreen pattern/pin/password back (and now since touch works in TWRP, you'll be able to enter it next time you boot to TWRP).
--If you wish to install Magisk, simply boot into TWRP and flash magisk.zip (Do NOT flash the stock boot image first or you will have erased all the hard work you just did properly installing TWRP).
--These instructions will need to be repeated everytime you update your boot image (kernel) because TWRP has been installed into your current boot image (kernel).

In case twrp-3.2.3-0-mata.img isn't updated by next month's update (October), save and reuse these instructions to install TWRP to October's boot image (kernel).


---------- Post added at 00:47 ---------- Previous post was at 00:46 ----------



If you have no lockscreen pin/pattern/password, but are encrypted, your password is default_password and TWRP (as well as Android) enters it for you automatically.

Hello I failed at installing new rom the touch zone didnt work anymore now I installed LineageOS for my zenfone 3 and gapps and the touch zone still not working. Could you help me please? What do you mean with Make sure you have September on the active slot Please?