[RECOVERY][enchilada] TWRP 3.2.3-0 Touch Recovery [UNOFFICIAL]

[joemossjr]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.



DOWNLOAD: Fixed....

Things that are different from official build:
fixed wrong theme color in screenshots on OP6.
Add support for QCOM haptics vibrator. (fixed vibration)

BUGS:
mtp (causes kernel panics) (can add a test build if needed)
flashing aroma packages

If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

XDAevDB Information
[RECOVERY][enchilada] TWRP 3.2.3-0 Touch Recovery [UNOFFICIAL]


Contributors
Joemossjr
Dees_Troy
wuxianlin

@notsyncing on github for the fixes
Source Code: Github

ROM OS Version: 8.x Oreo

Version Information
Status: Testing

Created 2018-07-07
Last Updated 2018-08-01

Donation Link: Buy this man a beer

 

[Veestaai]

Thanks for this. Add the version that supports MTP. Will test and let you know!

 

[joemossjr]

It's definitely bugged lol but I'll add it tomorrow

 

[felonius]

Thank you very much!

 

[xXx]

It's definitely bugged lol but I'll add it tomorrow

I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.

So thanks very much to provide us with the very first working TWRP for the OP6.

Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?

 

[DocRambone]

Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.

 

[joemossjr]

I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.

So thanks very much to provide us with the very first working TWRP for the OP6.

Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?

I'll be getting logs tonight while flashing an aroma package to see what's needed lol I feel like it's something simple but we will see. Thanks for the support everyone I do this on my free time lol I'll post the mtp enabled here shortly

 

[joemossjr]

mtp has been added to the downloads folder and is specified in the name!

 

[joemossjr]

https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned

 

[xXx]

https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned

thanks, very much appreciated :highfive:

 

[lollyjay]

mtp has been added to the downloads folder and is specified in the name!

Yes I have tested it and can confirm it's working. Just make sure you unmount mtp and remount it before attaching the USB cable (thanks to @DocRambone for the tip)

 

[iElvis]

Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.

This works, thanks!

 

[mbr007]

It's not working for me both new versions. Boot looped.

Sent from my ONEPLUS A6003 using XDA-Developers Legacy app

 

[lollyjay]

It's not working for me both new versions. Boot looped.

Did you remember to flash magisk after reboot into twrp?

 

[joemossjr]

Did you remember to flash magisk after reboot into twrp?

Yeah you have to flash magisk if you already had it flashed before hand

 

[xXx]

mtp has been added to the downloads folder and is specified in the name!

I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?

 

[showgood163]

Can you add another mirror like androidfilehost please? Unable to access google drive...

 

[adiher]

I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?

Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?

 

[joemossjr]

Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?

I can make a new build that's higher

 

[jbm76]

https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned

Could this have anything to do with why aroma isn't working?

https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5

From the magisk 16.6 change log.



Note to ROM Developers
If you are embedding Magisk Zip into your ROM, and your ROM uses Aroma Installer, please be aware that on some devices (most likely Samsung devices), it is possible that the installation process of Magisk could break Aroma. Please test flashing your ROM zip before releasing to your users. If you found out you are the few unfortunate devices, unzip the Magisk zip, and do the following changes and re-zip the installer:

Code:

# Remove or comment out these 2 lines in META-INF/com/google/android/updater-script eval $BOOTSIGNER -verify < $BOOTIMAGE && BOOTSIGNED=true $BOOTSIGNED && ui_print "- Boot image is signed with AVB 1.0"

The reason why Aroma Installer breaks is unknown. Maybe consider letting the project that's abandoned for nearly 5 years go?