[RECOVERY][3.3.1-0][Unofficial] TWRP recovery for ZTE Axon 10 Pro - ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other

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
/*
*
* 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.
*
*/
Note:
- Decryption with pin will not work if you fastboot boot the image (disable your pin , boot the image, flash the installer, and then reboot recovery)
- If you are on stock and not rooted, then you need to flash Magisk or your device will not boot after "Installation"
- If you are already rooted on stock or Custom ROM with Magisk, you may skip "Installation" and precede below
a.) Download the latest TWRP installer zip and Magisk zip
b.) Flash the TWRP installer as a local Magisk module (Install Magisk via TWRP afterward)
Installation:
1. Download android sdk tools here
2. Enter fastboot mode (You must follow the guide to unlock your bootloader first)
3. Run "fastboot boot recoveryimgfilename.img" (flash the installer for permanent installation and decryption)
a.) If you can't decrypt to access internal storage, you probably still have your pin or pattern enabled.
Tips:
If you already have TWRP flashed, you can only flash the new installer zip from TWRP (If you have Magisk installed don't forget to flash it again afterwards).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
Always use "system_image" and "vendor_image" instead of "system" and "vendor" when you are making a backup.
Download:
TWRP 3.3.1-0 Unofficial img and installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/C457/android_device_zte_pine/commits/twrp
https://github.com/C457/android_kernel_zte_sm8150
Donations:
Credits:
bigbiff
Dees-Troy
mauronofrio

Reserved in case something blows up

To answer one of the most anticipated questions, yes this will work on 5g models I'll make a guide in due time.

Hey unjistifieddev when will f2fs formatting be implemented? just wondering since right now its only formatting in ext4, also for some reason system backups will not restore it fails to format, so what i do is flash system image then restore data partition.

do you mean the system partition? the one formatted in ext4 is correct, data can be formatted f2fs and ext4

rafyvitto said:
Hey unjistifieddev when will f2fs formatting be implemented? just wondering since right now its only formatting in ext4, also for some reason system backups will not restore it fails to format, so what i do is flash system image then restore data partition.
Click to expand...
Click to collapse
F2fs formatting should work I'm not sure since I've been wiping my internal to make sure everything works. Also have you tried only backing up and restoring as system image and vendor image? Apparently you can't backup or restore system on these newer devices because system and vendor aren't mounted in fstab but by the kernel early before init runs fstab.
Sent from my ZTE A2020U Pro using Tapatalk

Chris axon 7 said:
do you mean the system partition? the one formatted in ext4 is correct, data can be formatted f2fs and ext4
Click to expand...
Click to collapse
Stock uses f2fs by default and does not mount data as ext4 at all. If it's formatting data in ext4 that's a problem, but I'm not sure that is. Both op7 and Zenfone 6 use f2fs by default and my trees for TWRP were based on them.
Sent from my ZTE A2020U Pro using Tapatalk

Unjustified Dev said:
F2fs formatting should work I'm not sure since I've been wiping my internal to make sure everything works. Also have you tried only backing up and restoring as system image and vendor image? Apparently you can't backup or restore system on these newer devices because system and vendor aren't mounted in fstab but by the kernel early before init runs fstab.
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
Good suggestion i will give that a shot thanks.

rafyvitto said:
Good suggestion i will give that a shot thanks.
Click to expand...
Click to collapse
Which model do you have?
Sent from my ZTE A2020U Pro using Tapatalk

Unjustified Dev said:
Which model do you have?
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
US model

rafyvitto said:
US model
Click to expand...
Click to collapse
I was looking for a G user I'm trying to make TWRP detect different models so it works on all variants. For now it's set to US props so we (I lol) can flash stock.
Sent from my ZTE A2020U Pro using Tapatalk

Unjustified Dev said:
I was looking for a G user I'm trying to make TWRP detect different models so it works on all variants. For now it's set to US props so we (I lol) can flash stock.
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
I see gotcha.

I have a G model ( zte a2020g 4g)

Chris axon 7 said:
Ich hab ein G model ( zte a2020g 4g)
Click to expand...
Click to collapse
cat /proc/vendor_imem/board_id
Sent from my ZTE A2020U Pro using Tapatalk

:/ $ su
:/ # cat /proc/vendor_imem/board_id
6
:/ #

Chris axon 7 said:
:/ $ su
:/ # cat /proc/vendor_imem/board_id
6
:/ #
Click to expand...
Click to collapse
Well that's what I expected same as US board thanks.
Sent from my ZTE A2020U Pro using Tapatalk

Hmm board 14 is much more challenging and POAD kills PINE every time!!
Cheers

Unjustified Dev said:
I was looking for a G user I'm trying to make TWRP detect different models so it works on all variants. For now it's set to US props so we (I lol) can flash stock.
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
Dear, And what is the problem of collecting TWRP for the EU, there it is necessary to change the encryption in boot, I do not see any problems in this

what do you mean ? twrp can decode. I have twrp on it and encrypted data with pin, if I go into twrp and enter my pin decrypts twrp normally without problemme
Sent from my ZTE A2020G Pro using XDA Labs

http://files.nwwn.com/~unjust/Axon 10 Pro/
404 not found
Edit
side goes again

Related

[RECOVERY] TWRP touch recovery

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.
CHANGELOG for 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Downloads:
Universal For All T6 Variants
Official - https://dl.twrp.me/t6univ
Installation:
Unlock your phone at www.htcdev.com
Boot phone into fastboot
Perform command fastboot flash recovery twrp-3.2.1-0-t6univ.img
Boot into HBOOT and select recovery
Root:
Download SuperSU http://download.chainfire.eu/supersu
Flash it in recovery
Copy backup to PC suing a PC:
adb shell
su
chmod -R 777 /data/media/TWRP
exit
Now you can copy your backup over
XDA:DevDB Information
TWRP, Tool/Utility for the HTC One Max
Contributors
Flyhalf205
Version Information
Status: Testing
Created 2013-10-26
Last Updated 2018-01-15
Great start @flyhalf
Sent from my HTC One using Tapatalk
Right now it is a 50/50 chance of it being pink and double.
It's not pink and double, however, it doesn't appear to be mounting any of the partitions. "Invalid block device" for all of them.
navalynt said:
It's not pink and double, however, it doesn't appear to be mounting any of the partitions. "Invalid block device" for all of them.
Click to expand...
Click to collapse
I'm shocked it isn't pink. I will fix it later this weekend then. But sounds like an easy fix then. Thanks for update
EDIT: I just uploaded a new copy. @navalynt ... Mounts should be fixed. Also if this does boot. Try turning off phone to see if offmode_charging_animation works Thank you
Damn, fly u everywhere. Lol.
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
---------- Post added at 11:04 AM ---------- Previous post was at 11:03 AM ----------
I cant wait to get my hands on the max!
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
I will try it later today. Since I got one MAX last week.
Sent from my HTC_One_max using xda premium
I put up a new link. Fixed the mounts I do believe so. Someone test it out please.
@zounduser In a crazy way I do end up in a lot of places ha.
Flyhalf205 said:
I put up a new link. Fixed the mounts I do believe so. Someone test it out please.
@zounduser In a crazy way I do end up in a lot of places ha.
Click to expand...
Click to collapse
Backup and restore working in latest version.
So does mounts and adb sideload.
Sent from my C6806 using XDA Premium 4 mobile app
Can anyone confirm root works ? Tried the other thread and I've unlocked boot loader Nd instAlle clockwork which I can confirm works, but installing the root zip dosent give me root
garyfl said:
Can anyone confirm root works ? Tried the other thread and I've unlocked boot loader Nd instAlle clockwork which I can confirm works, but installing the root zip dosent give me root
Click to expand...
Click to collapse
Go flash http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Flyhalf205 said:
Go flash http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Click to expand...
Click to collapse
Still dosent work, I still cannot change pixel density or install viper4android
garyfl said:
Still dosent work, I still cannot change pixel density or install viper4android
Click to expand...
Click to collapse
Any changes you make inside the ROM and reboot it will be reverted because of system has write protection on stock kernel.
Flyhalf205 said:
Any changes you make inside the ROM and reboot it will be reverted because of system has write protection on stock kernel.
Click to expand...
Click to collapse
So wait to flash a custom Rom essentially ?
garyfl said:
So wait to flash a custom Rom essentially ?
Click to expand...
Click to collapse
You can boot into recovery and flash things and it will stick. You can edit the build.prop for the density in recovery. You'll have to pull then push and fix permission on it. Reboot and sucess.
Sorry I don't understand, my knowledge is very limited up to this point.
garyfl said:
Sorry I don't understand, my knowledge is very limited up to this point.
Click to expand...
Click to collapse
Do you have a custom recovery?
Sent from my Nexus 4 using XDA Premium 4 mobile app
jschur1 said:
Do you have a custom recovery?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep one max unlocked boot loader Nd custom recovery
Flyhalf205 said:
I'm shocked it isn't pink. I will fix it later this weekend then. But sounds like an easy fix then. Thanks for update
EDIT: I just uploaded a new copy. @navalynt ... Mounts should be fixed. Also if this does boot. Try turning off phone to see if offmode_charging_animation works Thank you
Click to expand...
Click to collapse
Charging animation shows up when the phone is off.
Any work on getting the recovery working on the sprint model? T6whl

[Recovery] TWRP 3.1.1 for Xperia X

Greetings!
I'd like to present a TWRP recovery for the single-sim Xperia X. This release works on Xperia X F5121 and F5122
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
NEEDS TESTING
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-suzu-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
[TWRP] TWRP 3.1.0 for Xperia X
Old OP below:
Team Win Recovery Project 3.1.0​
REQUIREMENT:
- Unlocked bootloader
FEATURES:
- MTP support
- USB OTG storage support
- Covers most partitions for nandroid backups
- ADB root
- Full SELinux support
- Support for partition decryption
Download: Dropbox
Installation via the bootloader (Platform-tools (adb & fastboot))
Code:
fastboot flash recovery recovery.img
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Special thanks kistigun for testing recovery on the device.
Changelog: twrp.me
TWRP was going on OmniRom 7.1 sources and XperiaDeveloper.
SOURCEs: Suzu; loire; Common.
Nice work! Finally no more decryption problems on the X!
Working well, thanks!
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)? When I've tried the phone boots normally instead.
baddesthad said:
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)?
Click to expand...
Click to collapse
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed. If I don't find how to fix that button will be removed.
samavar89 said:
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed.
Click to expand...
Click to collapse
Good to know, thanks for clarifying
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Oel said:
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Click to expand...
Click to collapse
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
Ah...
Ok, Thanks!
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
robby.pgn said:
No, don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
Click to expand...
Click to collapse
This problem is strange, please provide a log recovery.
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Kianush said:
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Click to expand...
Click to collapse
In Your kernel there is support for DM-Verity and Sony RIC?
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
robby.pgn said:
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
Click to expand...
Click to collapse
Kianush said:
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
Click to expand...
Click to collapse
use this tool/guide to make a rooted kernel(and edit DM-Verity and Sony RIC): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
grayleshy said:
Team Win Recovery Project 3.1.0​
Click to expand...
Click to collapse
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Thanks
robby.pgn said:
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup.
Click to expand...
Click to collapse
This problem is almost resolved, just need to test, but I don't have time to compile recovery. In the test version recovery without decryption, problem solved.
juliompinheiro said:
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Click to expand...
Click to collapse
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
grayleshy said:
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
Click to expand...
Click to collapse
For whatever reason I'm not able to boot into TWRP like I should be. I've used the poison version of TWRP before so I know what to do, and yet the phone will just boot normally despite holding volume down and power when off.
I know that TWRP is installed though as I am able to boot to it if I first boot to the bootloader using a USB cable but that is very cumbersome to do though.
grayleshy said:
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
Click to expand...
Click to collapse
Clearly for the image available at your dropbox there are some libraries dependency errors, not only for the 'busybox', but also for other binaries that are in /sbin.
I do not know why this issue is only happening on my device since you said you can't reproduce this error. If there is anything I can do to help solve this strange behavior, count on me. I am an advanced linux user, but not too familiar with android specifics.
On latest 333 ROM for UK so that fingerprint scanner works on my Xperia X F5121.
I also modified by kernel/boot so that TWRP doesn't brick (actually boot loop) the device like it did the first time. After using these awesome instructions flashing TWRP recovery from here didn't kill the device any longer: https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I was able to take an early nandroid backup before a bunch of Titanium restores, etc. Now I get stuck at "Backing up data" step and it literally doesn't move to the next file. Attaching an image of where I get stuck. FYI, I do use password encryption on the backup and I did disable MD5 creation... still just stuck.
Next tests are to:
see if the stall is on the same exact file number
try no encryption
do a check disk (fsck) type of repair just in case I have corruption --- on my brand new device
Any suggestions greatly appreciated!
UPDATED:
I only back up Boot, System & Data (the default)
On second attempt it stopped at file 18869 of 22065 --- so it does jump and not consistently stop at a certain file.

TWRP 3.2.3-0 available

Was this already known ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
raystef66 said:
Was this already know ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Ey buddy I need your help , magisk keep forgetting my rooted apps ... I forgot whats the command I have to run on terminal emulator can you please help me !
luisaet82 said:
Ey buddy I need your help , magisk keep forgetting my rooted apps ... I forgot whats the command I have to run on terminal emulator can you please help me !
Click to expand...
Click to collapse
if it's this what you're referring too...
In terminal :
Code:
su
reboot disemmcwp
or adb :
adb shell reboot disemmcwp
raystef66 said:
if it's this what you're referring too...
In terminal :
or adb :
adb shell reboot disemmcwp
Click to expand...
Click to collapse
The first one ... Thank you so much .. great night
So its about twrp and first reaction is off topic...why you dont pm him?!!
Predatorhaze said:
So its about twrp and first reaction is off topic...why you dont pm him?!!
Click to expand...
Click to collapse
Big deal...that's called helping someone out you know.
You could have pm me or him too you know
And really? All those exclamation marks too? I suggest to ease down (and I know you already a bit longer then yesterday...) your comments are from time to time most inappropriate. I leave it with that
Can i flash the latest version when i have the treble recovery from nfound?
@BaamAlex the version 3.2.3.0 has as far as I could see that on my axon 7 no treble support
Chris axon 7 said:
@BaamAlex the version 3.2.3.0 has as far as I could see that on my axon 7 no treble support
Click to expand...
Click to collapse
Have you installed this here?
Yes
raystef66 said:
Was this already known ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Wow. This completely flew past me (and probably most of the xda community lol). Gonna check it out later. Thanks for telling us
Was this the same release that Nfound said was using older sources than his custom release?
This version boots as it should even with a fully loaded f2fs data partition. Finally the f2fs bug in TWRP has been solved!!!!!
Oki said:
This version boots as it should even with a fully loaded f2fs data partition. Finally the f2fs bug in TWRP has been solved!!!!!
Click to expand...
Click to collapse
Can we use that TWRP on treble? It will be better if we format all partitions to f2fs?
Aviver said:
Can we use that TWRP on treble? It will be better if we format all partitions to f2fs?
Click to expand...
Click to collapse
This TWRP works perfectly with treble roms. The main limitation is the inability to wipe, format, backup and restore the vendor partition using the menu system. You can always use the terminal to manage all that. For integrated vendor management, your only option so far is TWRP 3.2.1-8 Treble.
F2FS is a filesystem aimed to ssd storage devices. It provides an efficient and elaborated write policy that takes advantage of the flash memory. Reads are not specially efficient, this is why ext4 is used for read only partitions and f2fs for read/write partitions. So, system and vendor are ext4 while data and cache should be f2fs.

TWRP Flame [Official]

[RECOVERY] TWRP 3.5.0-0 - TeamWin Recovery Project
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 , 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.
flame Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Please go to https://twrp.me to download the device image.
A11 Testing:
https://build.twrp.me/test/flame/twrp-3.6.0-0-test1-flame.img- updated for lineage-18.1 booting
Old info:
Hello, this is a test build for flame users (will work on coral crosshatch/blueline later). The image is pretty safe for backing up now.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
Not working: sideload and fastbootd
May FW Date https://build.twrp.me/test/flame/twrp-3.3.1-0-test1-flame.img
June FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test2-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test4-flame.img
- fix super partition restore
- fix persist partition restore
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test5-flame.img
- allow repacking of TWRP boot.img
- magisk currently doesn't work
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test6-flame.img
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test7-flame.img
- fix repacking TWRP with magisk
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test8-flame.img
- multiuser decryption support
- fastbootd support
3.5.0-0: Android 11 bringup
https://build.twrp.me/test/flame/twrp-3.5.0-0-test1-flame.img
https://build.twrp.me/test/flame/twrp-3.5.0-0-test2-flame.img
- Titan M Wipe working on Format Data
- Apex fixes for flattened directories
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a Coral/Flame TWRP base
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Touch Install Image
5. Select your boot.img from /sdcard
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
TWRP won't Boot?
Make sure you have a kernel that supports the R DTBO and LZMA ramdisk starting with test5 such as https://forum.xda-developers.com/pi...nel-kirisakuraq-1-0-0-pixel-4-xl-aka-t3992213
Is this just for flame? Or both coral and flame? Reason I ask is because the 2 devices have significant differences, and if it's just for flame, you'll want to throw it in the regular Pixel 4 subforum
This is for flame as described. I will work on coral next.
They share the same device tree btw.
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
bigbiff said:
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
Click to expand...
Click to collapse
Ah man lol got me all excited!
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Can confirm this works for flashing. Booted the image and then ADB pushed magisk and kernel and both flashed successfully!
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Great work to see, we are finally not tied to magisk for flashing things now
Mrcactuseater said:
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Click to expand...
Click to collapse
wont work to @my end
2WildFirE said:
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Click to expand...
Click to collapse
Can you paste logcat output too?
Please guys don't just say it doesn't work. I need recovery.log and logcat so I can debug issues.
2WildFirE said:
wont work to @my end
Click to expand...
Click to collapse
Can you please post recovery.log and logcat?
bigbiff said:
Can you please post recovery.log and logcat?
Click to expand...
Click to collapse
Yep
Is ADB logcat -l the correct one?
2WildFirE said:
Yep
Is ADB logcat -l the correct one?
Click to expand...
Click to collapse
I usually do in adb shell
logcat > /tmp/logcat.txt
Then adb pull /tmp/logcat.txt
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
2WildFirE said:
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
Click to expand...
Click to collapse
Can you tell me your android build version?
bigbiff said:
can you tell me your android build version?
Click to expand...
Click to collapse
qq3a.200605.001
just to thank you a lot bigbiff for putting so much work and efforts on this, you are great. hope you can sort this out, best luck!! (a p3 user) :fingers-crossed::good: sorry for the ot
2WildFirE said:
qq3a.200605.001
Click to expand...
Click to collapse
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
bigbiff said:
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
Click to expand...
Click to collapse
Thanks will try :good:
@bigbiff
yeah decryption works fine now
@bigbiff
Sorry for dump questions, but if I want to backup, is it enough to backup super and data partition?

[RECOVERY][OFFICIAL] TWRP 3.5.2 [CEBU]

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
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)
- [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.
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.
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.
I'm a little late but. Thank you very much
Unfocusedobsessiv said:
I'm a little late but. Thank you very much
Click to expand...
Click to collapse
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.
still waiting for twrp for android 11
bhavesh.kale.73 said:
still waiting for twrp for android 11
Click to expand...
Click to collapse
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.
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.
arkansawdave74 said:
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.
Click to expand...
Click to collapse
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.
mistersmee said:
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.
Click to expand...
Click to collapse
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.
arkansawdave74 said:
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.
Click to expand...
Click to collapse
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.
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.
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.
arkansawdave74 said:
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.
Click to expand...
Click to collapse
That's great to hear.
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.
mistersmee said:
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.
Click to expand...
Click to collapse
Is your new build official as well?
EDIT. Nevermind. I missed the last line.
arkansawdave74 said:
Is your new build official as well?
Click to expand...
Click to collapse
Yes, it is official.
Booting twrp-3.6.0_11-0-cebu.img boots ok TWRP but touch freezed, any idea?
sirjuncos said:
Booting twrp-3.6.0_11-0-cebu.img boots ok TWRP but touch freezed, any idea?
Click to expand...
Click to collapse
Try this image: https://build.twrp.me/twrp-3.6.0_11-0-cebu.img

Categories

Resources