Official TWRP 3.2.3-0 for Essential PH-1

[chanh2018]

Are we going to see TWRP 3.4 for Essential?

 

[gk1984]

Are we going to see TWRP 3.4 for Essential?

If we haven't seen an update in 2 years, I think not. Our "maintainer" seems to have felt generous to put put 1 build or so and forget we exist.

 

[chanh2018]

If we haven't seen an update in 2 years, I think not. Our "maintainer" seems to have felt generous to put put 1 build or so and forget we exist.

He's still alive, isn't he?
Can someone drag him back in? :laugh:

 

[blair.sadewitz]

You could take over as maintainer if you'd like, gk1984.

Is there functionality that you're missing?

 

[gk1984]

You could take over as maintainer if you'd like, gk1984.

Is there functionality that you're missing?

I don't know the first thing about it but believe me, I considered it. I looked into what's required and I just don't have the setup to do it, yet alone the knowledge.

But yes, it's missing compatibility with current builds, missing decryption, and touch doesn't always work.

Let's not pretend this is normal for TWRP to behave this way. This is the first phone (and I've been rooting since Android Cupcake) that has a broken 3rd party recovery.

 

[blair.sadewitz]

I don't know the first thing about it but believe me, I considered it. I looked into what's required and I just don't have the setup to do it, yet alone the knowledge.

Yeah. Indeed, neither do I.

But yes, it's missing compatibility with current builds, missing decryption, and touch doesn't always work.

I know (see below):

Let's not pretend this is normal for TWRP to behave this way. This is the first phone (and I've been rooting since Android Cupcake) that has a broken 3rd party recovery.

Did I say that it wasn't broken? No. What I'm saying is that it is an all volunteer effort. (See below)

"If we haven't seen an update in 2 years, I think not. Our "maintainer" seems to have felt generous to put put 1 build or so and forget we exist."

He's probably busy with, umm, life., though he is under no obligation to do anything that he doesn't want to do. If you want someone to do the work, find a way to pay them. Organize crowdfunding. Do something. Indeed, he was generous; he ported it in the first place.

Have you investigated what is blocking the upgrade? Of course you didn't. Your time was better spent complaining and sniping at a volunteer. Maybe he no longer has the phone! Maybe he doesn't feel like it--who knows! Here's a hint: TWRP will build. However, something changed in 3.3 that requires a modest amount of work in order to coexist with magisk. Maybe you should ask the community what needs to be done in order to make it to work. Perhaps you could organize crowdfunding? I don't think it would be too difficult for someone who knows what they're doing.

I fail to grasp how you could snipe at people whose only mistake was, apparently, getting the thing to work in the first place and signing their name to it.

Perhaps the first thing you should do is join the developer's telegram group and ask what's blocking the upgrade. Someone already built 3.3.3.0, but not too many people use it, and there's a reason.

 

[Talnoy]

Can anyone maybe lend me a hand? I've followed this guide to the letter but for some reason the factory recovery will not leave slot b (the active android booting slot).

I've wiped everything more times than I can count, repushed files back and forth probably a thousand times and I can get into TWRP on slot A but for the life of me this zip file that was provided simply will not install TWRP on slot B which is my booting slot. I've tried to reinstall android, and now I'm going to attempt to get back to stock again.

Any help would be nice.

 

[chanh2018]

Can anyone maybe lend me a hand? I've followed this guide to the letter but for some reason the factory recovery will not leave slot b (the active android booting slot).

I've wiped everything more times than I can count, repushed files back and forth probably a thousand times and I can get into TWRP on slot A but for the life of me this zip file that was provided simply will not install TWRP on slot B which is my booting slot. I've tried to reinstall android, and now I'm going to attempt to get back to stock again.

Any help would be nice.

I hope you're not in Feb stock rom because TWRP will not work in this version.
You must back to Jan version in order to use TWRP.

 

[Talnoy]

I hope you're not in Feb stock rom because TWRP will not work in this version.
You must back to Jan version in order to use TWRP.

YES! I think you've got me on the right track - I found this 'Back to stock' package and got it running in the OS again: QP1A.190711.148-BACK-TO-STOCK.zip

I believe this is an October firmware if I'm not mistaken. If this is correct, I could then try to run the installation for TWRP again and it should be successful?

Finger's crossed!

 

[Nifter]

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.

help touchscreen not working even in stock roms until i use mouse!!!!!

 

[nijohnson]

Use the adb shell commands. I think they're identifed in the Essential Root Guide #2

 

[OliverBell]

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.

Was there any solution to this? I am also stuck in this process loop. I have tried January and September official builds but no luck booting back into them after installing TWRP into both slots.

 

[gk1984]

Was there any solution to this? I am also stuck in this process loop. I have tried January and September official builds but no luck booting back into them after installing TWRP into both slots.

If you flashed LOS 17.1, it has its own recovery and it doesn't support TWRP either. Your only choice is to flash stock firmware on one slot with TWRP and LOS on the other or don't use LOS.

 

[OliverBell]

If you flashed LOS 17.1, it has its own recovery and it doesn't support TWRP either. Your only choice is to flash stock firmware on one slot with TWRP and LOS on the other or don't use LOS.

Thank you, @gk1984! I was able to get LOS 17.1 installed with their own recovery. TWRP will have to wait

 

[dankovac1999]

If you flashed LOS 17.1, it has its own recovery and it doesn't support TWRP either. Your only choice is to flash stock firmware on one slot with TWRP and LOS on the other or don't use LOS.

So TWRP cant be flashed, when LOS (in my case 18.1 already) is present in the phone? I was trying to flash it with no luck. It always reboots to fastboot. This phone is messing with me.

 

[dankovac1999]

If you flashed LOS 17.1, it has its own recovery and it doesn't support TWRP either. Your only choice is to flash stock firmware on one slot with TWRP and LOS on the other or don't use LOS.

So TWRP cant be flashed, when LOS (in my case 18.1 already) is present in the phone? I was trying to flash it with no luck. It always reboots to fastboot. This phone is messing with me.

 

[gk1984]

So TWRP cant be flashed, when LOS (in my case 18.1 already) is present in the phone? I was trying to flash it with no luck. It always reboots to fastboot. This phone is messing with me.

I've long switched from Essential but what I remember is yes, because TWRP hasn't been updated to work with the new partition setup and firmware (which LOS is basing from), you can't use TWRP.