[RECOVERY][OFFICIAL] TWRP 3.5.2 [CEBU]

[mistersmee]

This build is now official.

Check out https://twrp.me/motorola/motorolamotog9power.html

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

#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 recovery
* 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.
*
*/

XDA:DevDB Information
TWRP, Tool/Utility for the Motorola G9 Power

Contributors
mistersmee

Source Code:
Device tree: https://github.com/teamwin/android_device_motorola_cebu
Kernel sources: Prebuilt (for now) [Note: Thanks @fddm, for your patched kernel!]
https://github.com/mistersmee/kernel_motorola_sm6115

TWRP sources: https://github.com/TeamWin/android_bootable_recovery

Telegram group: https://t.me/g9power (English language)

Version Information
Status: Stable
Created 20-05-2021

 

[mistersmee]

This is the list of things that need to work, as per TWRP's FAQs.
I will update as I find stuff that works, and as you guys tell me what works.

Blocking checks
- [X] Correct screen/recovery size
- [-] Working Touch, screen
       - [X] Focaltech touchscreen panel (confirmed working)
       - [X] Novatek touchscreen panel (confirmed working)
       - [X] Chipone touchscreen panel (confirmed working)
- [X] Backup to internal/microSD
- [X] Restore from internal/microSD
- [X] reboot to system
- [X] ADB



Medium checks
- [X] update.zip sideload
- [X] UI colors (red/blue inversions)
- [X] Screen goes off and on
- [X] F2FS/EXT4 Support, exFAT/NTFS where supported
- [X] all important partitions listed in mount/backup lists
- [X] backup/restore to/from external (USB-OTG) storage (not supported by the device)
- [X] backup/restore to/from adb (https://gerrit.omnirom.org/#/c/15943/)
- [X] decrypt /data
- [X] Correct date


Minor checks
- [X] MTP export
- [X] reboot to bootloader
- [X] reboot to recovery
- [X] poweroff
- [X] battery level
- [X] temperature
- [X] encrypted backups
- [X] input devices via USB (USB-OTG) - keyboard, mouse and disks (not supported by the device)
- [X] USB mass storage export
- [X] set brightness
- [X] vibrate
- [X] screenshot
- [X] partition SD card

If it isn't filled, it means it hasn't been checked yet. 'X' denotes that it is working. '!' denotes that it is not working.

 

[mistersmee]

Note: As I mentioned in the initial post, I'm using the prebuilt kernel for now, although the kernel sources have been released. For the long-term, using the prebuilt kernel is not ideal. I have been working on the kernel sources, but as of this writing, I have been unable to get them to boot. If any of you have experience working with Android kernels, please let me know, PM me, etc.

The kernel repo I'm working on is here: https://github.com/mistersmee/kernel_motorola_sm4250

PRs are always welcome.


Edit: Nevermind, I got them to boot.

 

[mistersmee]

A few notes on the image:

1. Yes, VBMeta shows 0MB in TWRP. It is intentional, nothing is wrong with the build, or your phone.
VBMeta as a partition, is only a few bytes in size, 65536 bytes, which is 65 KB, which is 0.06 MB, to be exact. TWRP displays sizes in MB, and probably rounds those decimals up, hence a size this small registers as 0. However, it is still an important partition, and it is in the stock fstab, so it cannot be left out.

2. The above point applies for "Prodpersist" as well. Although it is not as small as VBMeta, it is still just a few KBs in size, Again, it is in the stock fstab, so it cannot be left out.

Another probable explanation as to why Prodpersist shows up as 0MB, is that it is actually related to the /product partition. Due to the way Android 10, and dynamic partitions work, basically, the /system, /product, and /vendor have been subsumed under one big "super", which is incidentally read-only. Those individual partitions can only be mounted if the super partition as a whole is mounted, and TWRP does not mount that partition while booting, hence why it probably shows up as 0MB.

In any case, Prodpersist is actually not *that* important, so it doesn't *really* matter anyways.

3. As I said in the last paragraph above, Android 10 changed the way the /system partition works. Because of this, most modifications that in earlier Android versions we could do in TWRP, think flashable zips that change your boot animation, or anything that modified the system partition, will not work.

The only way to do those kinds of mods is through Magisk.

4. Yes, the image is 64MB in size. But, the stock recovery image is also 64MB.
The reason as to why it is 64MB, is because AVB support is enabled. AVB is, of course, Android Verified Boot, which allows GSI support, which should theoretically mean support for flashing GSI images in this TWRP build.
Without AVB support, the image is around 20MB, which is the more "normal" size of TWRP images of the past.

 

[Unfocusedobsessiv]

I'm a little late but. Thank you very much

 

[mistersmee]

I'm a little late but. Thank you very much

You're welcome!

Also as a general note to everybody:

If you updated to Android 11 and find that TWRP is not working for you i.e. it doesn't boot, nothing is wrong with your phone/you didn't mess anything up.

The build isn't working due to the Android 11 update, but I'm currently working on it.

 

[bhavesh.kale.73]

still waiting for twrp for android 11

 

[mistersmee]

still waiting for twrp for android 11

No ETA except to say I'm working on it. It depends on external factors, i.e Motorola releasing the updated kernel sources which they haven't done as of this writing.

 

[arkansawdave74]

Hello everyone. I've never had any luck restoring twrp backups of stock on encrypted A/B phones. Does anyone know if that's possible nowadays? I'm still on 10 too because of a Real Racing 3 bug that prevents it from loading in 11.

And a big thank you to you, @mistersmee . Your twrp is the reason I chose this phone.

 

[mistersmee]

Hello everyone. I've never had any luck restoring twrp backups of stock on encrypted A/B phones. Does anyone know if that's possible nowadays? I'm still on 10 too because of a Real Racing 3 bug that prevents it from loading in 11.

And a big thank you to you, @mistersmee . Your twrp is the reason I chose this phone.

You're welcome! And yeah, I had no problem backing up and restoring /data on cebu, so not sure what's going wrong for you.

 

[arkansawdave74]

You're welcome! And yeah, I had no problem backing up and restoring /data on cebu, so not sure what's going wrong for you.

Actually, I haven't tried in a couple years...Not since the G7 Power (Ocean). We had a terrible time trying to restore stock backups on that phone. I haven't even looked at the partition list in the backup section of your TWRP, but I'm about to. What partitions besides /data did you backup and restore successfully, if you don't mind my asking.

 

[mistersmee]

Actually, I haven't tried in a couple years...Not since the G7 Power (Ocean). We had a terrible time trying to restore stock backups on that phone. I haven't even looked at the partition list in the backup section of your TWRP, but I'm about to. What partitions besides /data did you backup and restore successfully, if you don't mind my asking.

Just about every partition that is available to backup/restore. Though frankly, backing up any partition other than /data is a waste of time and space, we don't actively modify them, and they are available in the stock firmware file if you manage to mess them up anyway.

 

[arkansawdave74]

Oh my gosh why didn't I think of that before.

The Moto G7 Power was the first a / B phone any of any of us had had back then. We tried and tried and tried many different ways to restore a backup but we never thought of that, which is surprising, but we were trying to make a complete backup that you could restore all from TWRP like in the old days. System, Boot, and data.

Anyway, I went to flash Resurrection Remix Q GSI and made it back up of stock first just /data. Restored just fine after the GSI failed to boot. You really made my Android experience so much better.

Thank You.

 

[arkansawdave74]

Hey guys. Just wanted to mention that I'm trying Android 11 Official GSI Customs coming off a stock 10 and TWRP still boots fine while running the 11s.

 

[mistersmee]

Hey guys. Just wanted to mention that I'm trying Android 11 Official GSI Customs coming off a stock 10 and TWRP still boots fine while running the 11s.

That's great to hear.

 

[mistersmee]

New release

TWRP 3.6.0_11

This build supports the Android 11 stock ROM. Unknown if it is backwards compatible with stock Android 10. Until confirmed that it is backwards compatible, people running 10 for whatever reason should stick to the 3.5.2 image, or update to 11 and run 3.6.0.

Everything is confirmed working. Download links are on the TWRP website, as always.

 

[arkansawdave74]

Is your new build official as well?
New release

TWRP 3.6.0_11

This build supports the Android 11 stock ROM. Unknown if it is backwards compatible with stock Android 10. Until confirmed that it is backwards compatible, people running 10 for whatever reason should stick to the 3.5.2 image, or update to 11 and run 3.6.0.

Everything is confirmed working. Download links are on the TWRP website, as always.

Is your new build official as well?

EDIT. Nevermind. I missed the last line.

 

[mistersmee]

Is your new build official as well?

Yes, it is official.

 

[sirjuncos]

Booting twrp-3.6.0_11-0-cebu.img boots ok TWRP but touch freezed, any idea?

 

[mistersmee]

Booting twrp-3.6.0_11-0-cebu.img boots ok TWRP but touch freezed, any idea?

Try this image: https://build.twrp.me/twrp-3.6.0_11-0-cebu.img