[recovery]Unofficial TWRP for G9 PLUS (ODESSA)

Mar 15, 2017
41
122
53
santiago
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.

Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- sdcard
- Decryption works
- Otg works
- Flash Rom works (no tested)
- F2FS support
- Fastboot boot command support
- Fastbootd

Not working:
- other , you tell me


Download:

(stableR.21)
(stableV1)
(betar 18)


To Flash the TWRP:
Code:
fastboot flash recovery_a twrp.img
Code:
fastboot flash recovery_b twrp.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp.img
or
Code:
fastboot oem reboot-recovery
Reccomended ADB and Fastboot binaries:

Adb and Fastboot Installer


Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/Moto-tree-folders

COFFE:
https://www.paypal.com/paypalme/sebastian3567
 
Last edited:
Mar 15, 2017
41
122
53
santiago
Reserved

changenlog: (betar builds (betar is beta for me XD ))

stable r.21
fix touch for ft8756 display
improve partitions
fix backups and rework dt

reduce 67mb to 35mb recovery

stable r1 (final betar )

- fix Decryption

betar 18 ()
- fix sdcard
- Decryption don't works (break for now)

betar 17 (private)
- private build

betar 16
- update source code to TWRP 3.5.0_10 (build with OMNI/AOSP 10)


betar 15
: build fastbootD (install work c:)

touch work in nova display

no work touch report you display
adb shell
ls /sys/class/touchscreen
and send me you display name
telegram https://t.me/seba_3567
 
Last edited:

ReneZeiss

Senior Member
Jun 5, 2017
51
12
8
Thank you Sebastian for your efforts.
I tried this TWRP by "fastboot boot recovery.img" without flashing it.
Because I'm rooted I checked my sys/class/touchscreen to see if I had a novatek screen.
NVT-ts
Novatek_ts
Thanks for confirming that this was the correct screen Sebastian!
 
Mar 15, 2017
41
122
53
santiago
Thank you Sebastian for your efforts.
I tried this TWRP by "fastboot boot recovery.img" without flashing it.
Because I'm rooted I checked my sys/class/touchscreen to see if I had a novatek screen.
NVT-ts
Novatek_ts
Thanks for confirming that this was the correct screen Sebastian!
test in NVT-ts (work) (use fastboot boot recovery.img for test you display )
 

Luanthom

New member
Feb 5, 2019
1
0
1
Hi Sebastian,

I also have a new Moto G9 Plus and the touchscreen is ft8756. I've tried various TWRP images with the same result; unable to enter anything on the touchscreen.

I understand from the posts that you are still working on this touchscreen.
 

MindArchr

Senior Member
May 7, 2011
76
20
38
35
Los Angeles, CA
I have searched Google and the forums and cannot find a feasible answer. I am unable to create a full backup on internal or external storage due to the error seen in the screenshot (it gets stuck in the same position with the same error on both storages). Can someone point me in the right direction or assist me in rectifying the issue? Thanks in advance.
IMG_20210119_194030.jpg
 

hampik

Member
Jan 5, 2014
10
8
23
Have new g9 plus and after recovery flash end up in bootloop TWRP can't control because touch screen not working.... 200€ bye bye.....

Waiting for new Odessa file
 

MindArchr

Senior Member
May 7, 2011
76
20
38
35
Los Angeles, CA
Have new g9 plus and after recovery flash end up in bootloop TWRP can't control because touch screen not working.... 200€ bye bye.....

Waiting for new Odessa file
turn the phone off, boot into fastboot, and flash the stock image (you'll have to search for how to flash stock image on this phone), and see if that will fix the issue