• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[RECOVERY][OFFICIAL] TWRP 3.5.2 [CEBU]

Search This thread

mistersmee

Senior Member
Jan 14, 2019
57
14
18
Kolhapur, India
Moto G9 Power
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.​

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 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
 
Last edited:
  • Like
Reactions: BTK19

mistersmee

Senior Member
Jan 14, 2019
57
14
18
Kolhapur, India
Moto G9 Power
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.
Code:
Blocking checks
- [X] Correct screen/recovery size
- [-] Working Touch, screen
       - [X] Focaltech touchscreen panel (confirmed working)
       - [X] Novatek touchscreen panel (confirmed working)
       - [ ] Other as of yet unknown panels (No panels from any other vendor other than Focaltech and Novatek have been reported, so idk)
- [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
- [!] 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.


Update:
With the updated image,
Code:
- [X] set brightness
works now.
 
Last edited:

mistersmee

Senior Member
Jan 14, 2019
57
14
18
Kolhapur, India
Moto G9 Power
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.
 
Last edited:

mistersmee

Senior Member
Jan 14, 2019
57
14
18
Kolhapur, India
Moto G9 Power
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.
 
Last edited:
  • Like
Reactions: BTK19

mistersmee

Senior Member
Jan 14, 2019
57
14
18
Kolhapur, India
Moto G9 Power
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.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    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.​

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