Official TWRP 3.2.3-0 for Essential PH-1

[SykkNyzz]

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

 

[temporarium]

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

Thanks for acknowledging the source ?

 

[VoluntaryMan]

Read three posts before yours.

... 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.

 

[rophiroth]

Is there and even more updated version?

 

[rophiroth]

im pretty sure there is an updated twrp, someone have it? thanks

 

[gk1984]

im pretty sure there is an updated twrp, someone have it? thanks

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.

 

[shri_chanakya]

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.

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.

 

[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..)

 

[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.

 

[IronRoo]

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.

Think most people think this is unlikely to be updated.

 

[Bill720]

I got it working... kind of

Think most people think this is unlikely to be updated.

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)

 

[temporarium]

Or simply flash a custom ROM instead of the February stock

 

[Bill720]

No thanks

Or simply flash a custom ROM instead of the February stock

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?

 

[temporarium]

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?

How about EOL = no more security updates?

 

[gk1984]

How about EOL = no more security updates?

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.

 

[temporarium]

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.

That's just for Google services. The underlying system will be left as is. Anyway, custom ROMs aren't all bad ?

 

[Bill720]

"security updates" are overrated

How about EOL = no more security updates?

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.

 

[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.

 

[grzwolf]

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 NOVENDOR Feburary 2020 update
Just skip flashing the bootloader "fastboot flash abl_x abl.img" and TWRP / LOS17.1 are happy.

 

[gk1984]

Essential NOVENDOR Feburary 2020 update
Just skip flashing the bootloader "fastboot flash abl_x abl.img" and TWRP / LOS17.1 are happy.

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.