Development [OFFICIAL]TWRP for the Motorola G30 (caprip)

[ThE_MarD]

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Introduction:

Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch-driven user interface, with 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.

Key Features:

Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage

In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.

We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open-source project.

Source Code:

GitHub - https://github.com/TeamWin/android_bootable_recovery

Gerrit Instance - http://gerrit.twrp.me

If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.


This is for UNOFFICIAL builds of TWRP for the Motorola G30 (caprip)

Device Config:

GitHub - TeamWin/android_device_motorola_caprip

Contribute to TeamWin/android_device_motorola_caprip development by creating an account on GitHub.

github.com

Official Downloads:

https://twrp.me/motorola/motorolamotog30.html

Test Downloads:

https://osdn.net/projects/twrp-for-caprip/releases/

Installation:

1. Backup everything important off of your device
2. Make sure your bootloader is unlocked
3. Download the recovery image (and optionally the TWRP installer zip) from above
4. Reboot into bootloader
5. Run this command (Change the .img to whatever the name of the file is you downloaded):
   

   fastboot boot twrp.img

6. (Optional instructions from this point on) Install TWRP installer zip
7. Reboot to recovery

Upgrade / Reinstall TWRP instructions

1. Download desired TWRP installer zip version
2. Reboot to recovery
3. Select Install
4. Tap on install and select the TWRP installer zip you downloaded from step one
5. Reboot to recovery and confirm that the updated version of TWRP is installed

Nandroid backup/restore

1. Have an available microSD Card or USB OTG drive
2. Backup boot, dtbo, system image, vendor image and data (optionally any other partitions you want a backup of) to your external storage device of choice
3. Once you wish to restore? Reboot to TWRP and format data (Wipe > "format data" button > type yes > keyboard checkbox)
4. Reboot to TWRP
5. Restore boot, dtbo, system image and vendor image
6. Reboot to system
7. Once it boots to the system without issues? Do not set any lockscreen security and reboot to TWRP
8. Restore data
9. Reboot to system
10. After it finishes boot? Your data and ROM will be restored but sometimes the UI might be incorrect, so reboot to the system again

For the TEST builds of TWRP? Please let me know if this works. If so? I will submit it to Gerrit for official updates.

Credits:

• mistersmee for his TWRP tree for the Motorola Moto G9 Power (cebu) that this caprip tree is based upon
• Samw662 for encouraging me to work on this and help out caprip owners since I don't own one plus testing these builds

 

[ThE_MarD]

Heyyo, initial public release is twrp-3.6.2_12-0_UNOFFICIAL-20220929-03-caprip which is based on TWRP 12.1 branch. Please test decryption on either A12 or A13 ROMs as I'm unsure if it is setup correctly or not.

Please report any bugs in this thread

 

[anuragnahata]

Hey, I cannot see my internal storage on this version of twrp. I am on android12 srtock rom

 

[ThE_MarD]

Heyyo @anuragnahata , can you please test this?

https://build.twrp.me/twrp-3.7.0_12-0-caprip.img

fastboot boot twrp-3.7.0_12-0-caprip.img

If you have any problems with this build too, then please submit logs either here or in PM. I've had other caprip owners say everything on that TWRP build works fine for them

 

[Leogami9009]

Touchscreen doesn't work. Maybe because my software channel is reteu?

 

[ThE_MarD]

Heyyo, TWRP 3.7.0_12 official is meow up on the TWRP website! Thanks to @Sammm77 for encouraging me to work on this for a device I don't even own and for helping test it out.

@Leogami9009 can you please provide logcat? Tbh I'm not even sure what are all the touchscreen drivers that caprip even uses but I did try to reference the kernel source code but maybe I missed one? Also, are you on the official build or a test build?

 

[Sammm77]

Heyyo, TWRP 3.7.0_12 official is meow up on the TWRP website! Thanks to @Sammm77 for encouraging me to work on this for a device I don't even own and for helping test it out.

@Leogami9009 can you please provide logcat? Tbh I'm not even sure what are all the touchscreen drivers that caprip even uses but I did try to reference the kernel source code but maybe I missed one? Also, are you on the official build or a test build?

For some people ek touch does not work, but for the vast majority it works perfectly. You have to wait 15 seconds when starting TWRP but after that it works fine. Excellent work friend.

 

[Sammm77]

Touchscreen doesn't work. Maybe because my software channel is reteu?

No, it's not because of your channel, surely the developer skipped a display driver. Maybe with time we will solve it, if you want to contribute send logcat and dmesg to the developer.

 

[ThE_MarD]

@Sammm77 if touchscreen doesn't work right away? Odds are it's just the touchscreen driver still initializing and maybe checking firmware and such. Focaltech for example is really known for having touchscreen issues as well on TWRP because of a long init period. Some touchscreens have a way to manually reset the kernel driver I think but I'm unsure if caprip has a method to do so.

My Asus Zenfone 5z (Z01R) has focaltech touchscreen and has issues with TWRP where sometimes it's intermittent that touchscreen works but it always works in the ROM since the ROM boot time is a lot longer than TWRP

 

[Leogami9009]

Ok, i let the phone to load the driver and it works, thank you all!

 

[Leogami9009]

Is it normal for this recovery to not be able to resize system/ not being able to enter on internal storage?

 

[Sammm77]

@Sammm77 if touchscreen doesn't work right away? Odds are it's just the touchscreen driver still initializing and maybe checking firmware and such. Focaltech for example is really known for having touchscreen issues as well on TWRP because of a long init period. Some touchscreens have a way to manually reset the kernel driver I think but I'm unsure if caprip has a method to do so.

My Asus Zenfone 5z (Z01R) has focaltech touchscreen and has issues with TWRP where sometimes it's intermittent that touchscreen works but it always works in the ROM since the ROM boot time is a lot longer than TWRP

No, it doesn't load right away, that would be great but it doesn't. You have to wait a few seconds. Do you think that can be solved?

 

[Sammm77]

Is it normal for this recovery to not be able to resize system/ not being able to enter on internal storage?

internal storage must be decrypted. Maybe later I'll make a tutorial on how to do that.

 

[ThE_MarD]

Heyyo, well it seems there's some communication breakdown as I was under the impression that decryption worked but I guess it doesn't lol oof.

Ok, can someone who is decrypted please try to decrypt and when it fails send me the recovery.log and logcat?

(No replies? Maybe decryption does actually work and there's some more miscommunication???)

 

[Leogami9009]

Sorry for the long waiting, but i forgot to get the logcat and recovery.txt. I tried today to get it, but i wasn't able to. it says that it was saved in data/media/ so i tried to get it with adb pull but it says "failed to stat remote object 'data/media/logcat.txt': Permission denied". But i think i should mention that i've installed twrp by flashing the .zip with termux (my phone was rooted with magisk and it had the magic flasher module). I installed it this way because the booted .img touchscreen didn't worked even if i let it some minutes for the driver to load. And when i've flashed the .zip with termux my device wasn't rooted anymore. So i can't use adb root. But when i flash the patched boot.img back, the recovery just disappears.
Sorry for bad english

 

[ThE_MarD]

@Leogami9009 hmm, maybe it's just because of the prebuilt kernel? Not too sure though tbh but I think there's kernel source code somewhere so I might see if that would help? From what I saw from Motorola's source code release there was only like, 2 drivers they used for touch

 

[Sammm77]

@Leogami9009 hmm, maybe it's just because of the prebuilt kernel? Not too sure though tbh but I think there's kernel source code somewhere so I might see if that would help? From what I saw from Motorola's source code release there was only like, 2 drivers they used for touch

That's why twrp doesn't work on ilitek screens, on this device.

 

[ThE_MarD]

@Leogami9009 I think I just realized you're trying to get some logcat.txt on the device, but you should be using a PC or something to get logcat like this:

Via Windows PowerShell:

adb logcat | Tee-Object logcat.log

Via Linux Terminal:

adb logcat | tee logcat.log

And whatever folder you are in when you run it will have that logcat.log

Also, which build of TWRP are you on?

Plus twrp-installer.zip is meant to be installed whilst in recovery and not while booted into the system. Installing TWRP does remove root so if you want to maintain that you must reinstall it after rebooting to recovery.

 

[Leogami9009]

Here is the logcat, i let it for 5 minutes:
I have twrp 3.7.0, i realized yestarday that if i root with twrp i can have both root and the recovery, and i tried to flash the zip with the twrp already installed ( nothing different)
Something intresting is that if i format data with twrp and reboot in recovery, it detects the internal storage (when i try to select the internal storage it says it has 15000mb or something like that), but after i set up the phone, it says 0mb. Maybe is something about the partition format? Idk, i can put a sd card to see if it gets detected or not.
Another thins is that when twrp starts it says "Unable to mount storage" and "Unable to mount /data/media/TWRP/.twrps" two times and when i try to manually select the Internal Storage and data partition and format those it says "Unable to mount 'data' (Invalid argument)" "Unable to wipe /data."

 

[jan6]

ahoy, the release version does not work on my phone, also EU, build S0RCS32.41-10-9-2
I mean, I fastboot boot twrp-3.whatever.img and it boots to that, but touchscreen doesn't work, and adb doesn't work, only thing I can do is turn screen on-off, lol, even after waiting several minutes

also the kernel sources are iirc like, on github, under various tags and branches