yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] VoluntaryMan:
... I'm not asking for that.

I'm asking for the new TWRP codebase for previous OSes.

Our TWRP build works on Android 10 at the moment anyway (just not the Feb build) and using an old version of their codebase.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
Is there and even more updated version?
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
im pretty sure there is an updated twrp, someone have it? thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Most current TWRP is on official TWRP website, but still lacks support for decrypting and touch if you're using any current update. It's still neglected.
[Essential Phone ROMs, Kernels, Recoveries, & Other] shri_chanakya:
I downloaded TWRP from official site and used that. You need to ensure you are flashing on both the a and b partition for touch to work. Please read the twrp flashing post.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rophiroth:
And all twrp versions have the screen buggy? Here I found the updated version I was talking about, touch without losing the other slot stuff:

https://drive.google.com/folderview?id=161SEe74nYxXIBfg3OPlYEUz_D2IAguCf

While installing twrp in both slot my los16 dont boot anymore :'c

But I run into a recently different problem now... I move a mock app to system with luckypatcher and then my system dont boot anymore... Lockscreen was password protected and decreypting is failing to read my password. Any way to fix this without factory reset and lose all data? :'c (I dont undestand why this cause system cant boot..)

---------- Post added at 04:08 PM ---------- Previous post was at 04:08 PM ----------

And all twrp versions have the screen buggy? Here I found the updated version I was talking about, touch without losing the other slot stuff:

https://drive.google.com/folderview?id=161SEe74nYxXIBfg3OPlYEUz_D2IAguCf

While installing twrp in both slot my los16 dont boot anymore :'c

But I run into a recently different problem now... I move a mock app to system with luckypatcher and then my system dont boot anymore... Lockscreen was password protected and decreypting is failing to read my password. Any way to fix this without factory reset and lose all data? :'c (I dont undestand why this cause system cant boot..)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bill720:
So close!

Any word on getting TWRP updated or working with the Febuary 2020 stock Rom release? We're so close! Once it's working, we'll be done with pesky updates for this phone forever and then they never have to worry about it again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IronRoo:
Think most people think this is unlikely to be updated.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bill720:
I got it working... kind of

That's too bad, given the importance of this final software update. At any rate, I worked on this for a few hours yesterday and found what I consider to be a viable solution by taking advantage of the ever-irritating "slots" function.

Basically, with the January 2020 Rom (stock, rooted, and EdXposed) on both slots, I used TWRP to install the PH1-OTA-QQ1A.200105.032.zip to one of the slots. I booted the phone and verified that it had received the Febuary Rom (032) on that slot and was still running the January (007) on the other. I used Fastboot to apply the FebRoot.img image to the slot that I had upgraded to 032 and restarted.

With that done, and after verifying that everything was working as expected, I now had one slot with a fully rooted/working 007 and, most importantly, one with a fully rooted/working 032 (Febuary 2020). To have some access to TWRP, I installed the same old "Dec_boot_patched_TWRP.img" on the slot with the old January (007) Rom that I wouldn't be using anymore. That slot now has only TWRP. When I need to use it, I just flip over to slot A, do whatever needs to be done in Twrp, switch back to slot B, and boot normally.

While this is a bit annoying, the only times I ever should need to use TWRP anymore will be for emergency recovery purposes (in case of broken Magisk/EdXposed module updates) and for doing backups. The 30 extra seconds that I'll have to spend (maybe 2-3 times per year) are worth it in exchange for not having to dismiss the ever-irritating update nags ever few days. Even if Twrp never gets updated, I'm happy with leaving it as-is, since this setup is essentially 100% functional.

For anyone who might be playing along at home, here are some of the most useful commands, all compiled into one place, in no particular order:

adb reboot fastboot

adb reboot recovery

adb shell getprop ro.boot.slot_suffix (this one tells you what slot you're currently on, after booting up, or from within TWRP)

fastboot getvar current-slot

fastboot --set-active=a

fastboot --set-active=b

fastboot reboot recovery

fastboot flash boot_b FebRoot.img (or, alternatively fastboot flash boot_a FebRoot.img)
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Or simply flash a custom ROM instead of the February stock
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bill720:
No thanks

I've had my fill of custom Roms for one lifetime. Apart from lack of proper display calibration, there aren't any glaring omissions in the stock Rom that I can think of. How about you?
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
How about EOL = no more security updates?
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
I know it's not the same, but we still get security updates via Play Store. Go to Android Settings, then Security and you'll see it. Tap it to update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
That's just for Google services. The underlying system will be left as is. Anyway, custom ROMs aren't all bad ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bill720:
"security updates" are overrated

It's been my experience that the best security is common sense. I don't worry about it and don't have any plans to start unless some kind of actual and exploitable security problem is found.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
Can someone who has actually tried to run TWRP on Feb. update produce and share a TWRP log in the issue I filed?

https://github.com/TeamWin/android_bootable_recovery/issues/14

I haven't actually flashed any custom ROMs and have no need for TWRP, but I'm planning to flash either LOS 17.1 when it's released or Paranoid Android shortly in hopes it addresses some bugs Google/Essential has ignored. It would be nice to have a current version of TWRP, as many here have expressed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] grzwolf:
Essential NOVENDOR Feburary 2020 update

Just skip flashing the bootloader "fastboot flash abl_x abl.img" and TWRP / LOS17.1 are happy.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
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
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bofahad:
Finally :)

you are AMAZING how you knowed that ??
[Essential Phone ROMs, Kernels, Recoveries, & Other] SykkNyzz:
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)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bofahad:
:svetius:
[Essential Phone ROMs, Kernels, Recoveries, & Other] 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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 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...
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] DAE1964:
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/
[Essential Phone ROMs, Kernels, Recoveries, & Other] mizzike32:
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)
[Essential Phone ROMs, Kernels, Recoveries, & Other] DAE1964:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gavinfernandes2012:
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
[Essential Phone ROMs, Kernels, Recoveries, & Other] 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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mizzike32:
i'm a boob

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!
[Essential Phone ROMs, Kernels, Recoveries, & Other] 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?
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Have a look here:

https://xdaforums.com/nexus-6/help/e-createtarfork-process-error255-t3302462/post82030011
[Essential Phone ROMs, Kernels, Recoveries, & Other] Darkside1984:
It works. Thanks!! :fingers-crossed:
[Essential Phone ROMs, Kernels, Recoveries, & Other] JohnnyChim:
can I use the TWRP with stock rom?

My device wont boot after flashing TWRP 3.2.3.0
[Essential Phone ROMs, Kernels, Recoveries, & Other] mlock420:
You have to be on January ota stock rom February doesn't work with twrp
[Essential Phone ROMs, Kernels, Recoveries, & Other] 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. :(
[Essential Phone ROMs, Kernels, Recoveries, & Other] SanoFeketeSK:
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?
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Are we going to see TWRP 3.4 for Essential?
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
He's still alive, isn't he?

Can someone drag him back in? :laugh:
[Essential Phone ROMs, Kernels, Recoveries, & Other] blair.sadewitz:
You could take over as maintainer if you'd like, gk1984.

Is there functionality that you're missing?
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] blair.sadewitz:
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:rolleyes: 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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Talnoy:
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!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Nifter:
help touchscreen not working even in stock roms until i use mouse!!!!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] nijohnson:
Use the adb shell commands. I think they're identifed in the Essential Root Guide #2
[Essential Phone ROMs, Kernels, Recoveries, & Other] OliverBell:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] OliverBell:
Thank you, [MENTION=3443130]gk1984[/MENTION]! I was able to get LOS 17.1 installed with their own recovery. TWRP will have to wait :(
[Essential Phone ROMs, Kernels, Recoveries, & Other] dankovac1999:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gk1984:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hamal985:
Hello, can someone help me?

When I try installing twrp it pops up this error:

Desktop/TWRP_Boot_Jan.img

ERROR: usb_read failed with status e00002ed

ERROR: usb_write failed with status e00002ed

ERROR: usb_write failed with status e000404f

ERROR: usb_write failed with status e000404f

ERROR: usb_write failed with status e000404f

ERROR: usb_write failed with status e000404f

Warning: skip copying tool_b image avb footer (tool_b partition size: 0, tool_b image size: 67108864).

Sending 'tool_b' (65536 KB) ERROR: usb_write failed with status e000404f

FAILED (Write to device failed (No such file or directory))

fastboot: error: Command failed

Thank you
[Essential Phone ROMs, Kernels, Recoveries, & Other] dirtyreturn:
Hi there XDA! Um, i m experiencing a bit of difficulty here with getting twrp to stick, granted only one attempt was made. I followed the instructions from our twrp device page to what I believe to be a 'T' . TWRP did not stick. Though, after going through the instructions provided, I flashed an update to a ROM, a boot.img, then magisk, and tapped reboot to system.

I figured out what slot I was on, then switched over to the opposite slot as active, used fastboot flash boot twrp.img, booted to recovery, switched back to the original slot, flashed the twrp.zip through twrp, and then did the above ^.

Does twrp not stick when flashing other boot.imgs?
[Essential Phone ROMs, Kernels, Recoveries, & Other] techlogik:
Well, now I got no touch screen again after and issue with trying to get substratum theme working. Sideloaded the OTA and no twrp touch again. Tried also the full fastboot version, then no touch in OS.

Back to the drawing board.