Database Develop

[TWRP][3.0][RECOVERY] TWRP 3.0.3-0 TeamWin Recovery Project ZUK Z2

TeamWin is proud to present TWRP 3.0.3-0 for the ZUK Z2!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 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
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
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 cache & dalvik, 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/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
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.
Device Config: https://github.com/TeamWin/android_device_zuk_z2
Kernel: https://github.com/TeamWin/android_kernel_zuk_z2
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
https://dl.twrp.me/z2/
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers

Thanks, it working on Z2 and Z2pro ? (same almost hardware)

tikilou said:
Thanks, it working on Z2 and Z2pro ? (same almost hardware)
Click to expand...
Click to collapse
Only Z2 not pro

Just reporting decryption of device doesn't work. Error 'unable to decrypt /data', just as with other TWRP versions. Device is Z2 Z2131.

SenK9 said:
Just reporting decryption of device doesn't work. Error 'unable to decrypt /data', just as with other TWRP versions. Device is Z2 Z2131.
Click to expand...
Click to collapse
So you have the same problem on the other TWRP?

mauronofrio said:
So you have the same problem on the other TWRP?
Click to expand...
Click to collapse
I have tried three TWRPs:
1) This one from OP (official TWRP 3.0.3.0)
MD5 - f80527e6a30c3b863163612879e1ecdc
2) Chinese/EN TWRP (3.0.2.0) from http://zukfans.eu/community/threads...2-zuk-z2-plus-z2131-z2132-only.291/#post-3719
MD5 - eaee35ae037de181655cca8ecdc9ad7d
3) International TWRP (3.0.2.0) from http://zukfans.eu/community/threads...2-zuk-z2-plus-z2131-z2132-only.291/#post-3715
MD5 - 5490ed18eef5409621e59c50c6548c94
All are unable to decrypt encrypted device with same error. I had this issue with one of my previous phone (I think Oneplus One) and it was something in TWRP since a later version fixed it.
On this page, it refers to some config when building TWRP:
https://forum.xda-developers.com/showthread.php?t=1943625
Code:
length= -- usually used to reserve empty space at the end of the /data partition for storing the decryption key when Android's full device encryption is present, not setting this may lead to the inability to encrypt the device
canencryptbackup= -- 1 or 0 to enable/disable, makes TWRP encrypt the backup of this partition if the user chooses encryption (only applies to tar backups, not images)
userdataencryptbackup= -- 1 or 0 to enable/disable, makes TWRP encrypt only the userdata portion of this partition, certain subfuldes like /data/app would not be encrypted to save time
Could this be related somehow? Is there any other info which you need?
EDIT: I will try the other EDL button TWRP and see if that works
---------- Post added at 09:25 AM ---------- Previous post was at 09:16 AM ----------
I have tried the 4th TWRP (EDL Button one) from your other thread, still no good. I have posted the error log below from TWRP. It also has gibberish characters, which I will post a photo in the other thread. Anyway here is the decryption error:
/tmp/recovery.log:
Code:
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Is encrypted, do decrypt page first
I:Switching packages (TWRP)
I:Set page: 'decrypt'
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
crypt_ftr->fs_size = 113540519
Using scrypt with keymaster for cryptfs KDF
Invalid hex string
Failed to convert passwd from hex, using passwd instead
could not find any keystore module
Failed to init keymaster
Signing failed
kdf failed
failure decrypting master key
Failed to decrypt master key
mount:
Code:
rootfs on / type rootfs (rw,seclabel,size=1825024k,nr_inodes=456256)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1897396k,nr_inodes=474349,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=1897396k,nr_inodes=474349)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p39 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
blkid:
Code:
/dev/block/mmcblk0p46: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p40: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p39: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p34: UUID="00BC-614E" TYPE="vfat"
/dev/block/mmcblk0p24: LABEL="dsp" UUID="af32c008-2a39-7e5b-a5dc-201456d93103" TYPE="ext4"
/dev/block/mmcblk0p23: UUID="00BC-614E" TYPE="vfat"
/dev/block/mmcblk0p16: LABEL="system" UUID="da594c53-9beb-f85c-85c5-cedf76546f7a" TYPE="ext4"

SenK9 said:
I have tried three TWRPs:
1) This one from OP (official TWRP 3.0.3.0)
MD5 - f80527e6a30c3b863163612879e1ecdc
2) Chinese/EN TWRP (3.0.2.0) from http://zukfans.eu/community/threads...2-zuk-z2-plus-z2131-z2132-only.291/#post-3719
MD5 - eaee35ae037de181655cca8ecdc9ad7d
3) International TWRP (3.0.2.0) from http://zukfans.eu/community/threads...2-zuk-z2-plus-z2131-z2132-only.291/#post-3715
MD5 - 5490ed18eef5409621e59c50c6548c94
All are unable to decrypt encrypted device with same error. I had this issue with one of my previous phone (I think Oneplus One) and it was something in TWRP since a later version fixed it.
On this page, it refers to some config when building TWRP:
https://forum.xda-developers.com/showthread.php?t=1943625
Code:
length= -- usually used to reserve empty space at the end of the /data partition for storing the decryption key when Android's full device encryption is present, not setting this may lead to the inability to encrypt the device
canencryptbackup= -- 1 or 0 to enable/disable, makes TWRP encrypt the backup of this partition if the user chooses encryption (only applies to tar backups, not images)
userdataencryptbackup= -- 1 or 0 to enable/disable, makes TWRP encrypt only the userdata portion of this partition, certain subfuldes like /data/app would not be encrypted to save time
Could this be related somehow? Is there any other info which you need?
EDIT: I will try the other EDL button TWRP and see if that works
Click to expand...
Click to collapse
I need of a tester, Do you want to test it?

Yes I can test it. I will PM you my contact

For those with encrypted devices, try using Fedor's TWRP 3.0.2 - it is able to successfully decrypt the device. No other TWRP can decrypt it that I know of, so this is a good workaround, it can be downloaded here - https://yadi.sk/d/JWaxwHrj34c6RJ

Hi dev,
Do we have f2fs support as well?
Thanks

rajputrajat said:
Hi dev,
Do we have f2fs support as well?
Thanks
Click to expand...
Click to collapse
For F2FS, people are reporting Fedor's 3.0.3 TWRP supports it, download link:
https://mega.nz/#F!1oxGmSaZ!jN5FyyrmXApd2miBpftfqg

Hello. I am coming from Sony Xperia Z1.
Regarding: TWRP decryption. TWRP does not support decryption for most of Qualcomm's devices. The reason is you have to modify device tree so that qucomm's blobs responsible for encryption/decryption are embedded into recovery image, as they can't be pulled by TWRP from system, because of hardware based encryption. I have compiled TWRP for Sony Xperia Z1-Z3 and they all are able to decrypt data partition. I am working on my Jaguar N rom for Zuk Z2, as I got the device just today. I will be posting a working TWRP as soon as I can.
Also, a question: How to flash TWRP via fastboot? On Sony devices you do fastboot flash recovery recovery.img. It is probably different on Zuk2. Thanks in advance...

fastboot -i 0x2b4c flash recovery recovery.img

There is a updated TWRP 3.1 rolling out: https://dl.twrp.me/z2/twrp-3.1.0-0-z2.img.html
Changelog: https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/

Hi, what is the correct and latest TWRP for the Z2 Pro? This seems to be only for Z2?

[RECOVERY][UNOFFICIAL] PitchBlack Recovery v3.0 [monet]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[SIZE="3"]*
* Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*
*[/SIZE]
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: Mi 10 Lite 5G (monet)
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device Tree: https://github.com/spakkkk/device_xiaomi_monet_recovery
Device Tree Maintainers: spakkkk & masemoel
Kernel: Stock Prebuilt
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Working
Decryption
You can flash Magisk, Roms, Kernels, Firmwares, etc.
Format and Wipe
Not tested
Backups
To Be Fixed Soon
Vibration
Link to dowload - 03102020 Version
SourceForge
Beers and Coffees
masemoel he deserves!
I want to thanks to masemoel, for the great help and time he wasted with me to make this PBRP work!

Great well done man!!!

I'm glad we could get this project working, and stable!! This couldn't have been possible without you ?
Sent from my Redmi K30 5G using XDA Labs

The twrp for me works very fine!!!
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
spakkkk said:
Code:
[SIZE="3"]*
* Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*
*[/SIZE]
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: Mi 10 Lite 5G (monet)
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device Tree: https://github.com/spakkkk/device_xiaomi_monet_recovery
Device Tree Maintainers: spakkkk & masemoel
Kernel: Stock Prebuilt
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Working
Decryption
You can flash Magisk, Roms, Kernels, Firmwares, etc.
Format and Wipe
Not tested
Backups
To Be Fixed Soon
Vibration
Link to dowload
Google Drive
I want to thanks to masemoel, for the great help and time he wasted with me to make this PBRP work!
Note to the XDA Mods - Please move the topic to the correct section please, i cant create thread there.
Click to expand...
Click to collapse
You have to put your paypal account because you de serve at least a couple of beer

great job

Thanks a lot. I Need It

Noice. Now let's wait for custom ROMs :laugh:

What about if OTA received? Will it break OTA or OTA will destroy this recovery?

gunar74 said:
What about if OTA received? Will it break OTA or OTA will destroy this recovery?
Click to expand...
Click to collapse
Don't know, i didn't receive any OTA :/

new version
PBPR updates
03102020

Link down

angus6969 said:
Link down
Click to expand...
Click to collapse
fixed bro!

spakkkk said:
fixed bro!
Click to expand...
Click to collapse
Download OK. :good:
Thank you.

Faced issues while installing Migrate GPE 3.1.1 based backups.
Is/was anyone successful in flashing Migrate GPE based backups?
Tested TWRPs:
PitchBlack Recovery v3.0 - 03102020
TWRP 3.4.0-14 Unofficial by mauronofrio
Used ROMs:
miui_MONETEEAGlobal_V12.0.2.0.QJIEUXM_12bc504f22_10.0
xiaomi.eu_multi_MI10LITE5G_V12.0.1.0.QJIMIXM_v12-10
Here is some log output:
Code:
---------------------------------
Migrate-GPE Flash package
Version 3.1.1 - release
---------------------------------
*** Extras ***
---------------------------------
minzip: Extracted 3 file(s)
Mounting partition...
about to run program [/tmp/mount_script.sh] with 3 args
DEBUG:: --- making config dir (/tmp/manualConfigs) if does not exist ---
Debug:: SAR device!
DEBUG:: --- fstab ---
/dev/block/dm-0 /system_root ext4 ro 0 0
/dev/block/dm-2 /vendor ext4 ro 0 0
/dev/block/dm-1 /product ext4 ro 0 0
/dev/block/dm-3 /odm ext4 ro 0 0
/dev/block/sda18 /metadata ext4 rw 0 0
/dev/block/sda34 /data f2fs rw 0 0
/dev/block/sda30 /cache ext4 rw 0 0
/dev/block/sde48 /firmware vfat rw 0 0
/dev/block/sda23 /persist ext4 rw 0 0
/dev/block/sda32 /cust ext4 rw 0 0
/usb_otg vfat rw 0 0
DEBUG:: --- end of fstab ---
Debug:: mount /system_root
Debug:: Directly internal toybox/busybox
Debug:: mount /data
Debug:: Directly internal toybox/busybox
mount: '/dev/block/sda34'->'/data': Device or resource busy
Debug:: Creating Test file
matches was 2 on <</dev/block/sda34 /data>>
script aborted: Mount failed data! Exiting...
Mount failed data! Exiting...
Updater process ended with ERROR: 7
An assert failed. Please check the output above for more details.
Updating partition details...
I:Data backup size is 3277MB, free: 98337MB.
...done
Error installing zip file '/sdcard/Migrate/Backup_2020.10.21_23.45.24/Extras.zip'
Updating partition details...
I:Data backup size is 3277MB, free: 98337MB.
...done

raupe said:
Faced issues while installing Migrate GPE 3.1.1 based backups.
Is/was anyone successful in flashing Migrate GPE based backups?
Tested TWRPs:
PitchBlack Recovery v3.0 - 03102020
TWRP 3.4.0-14 Unofficial by mauronofrio
Used ROMs:
miui_MONETEEAGlobal_V12.0.2.0.QJIEUXM_12bc504f22_10.0
xiaomi.eu_multi_MI10LITE5G_V12.0.1.0.QJIMIXM_v12-10
Here is some log output:
Click to expand...
Click to collapse
It's PBRP fault, and they're working hard to fix it.
Meanwhile, you can try making various small backups instead of one big backup (for example, if you hace 20, select 10 the first time, and take later backup of the other 10).
That's what I'm doing now ?

gunar74 said:
What about if OTA received? Will it break OTA or OTA will destroy this recovery?
Click to expand...
Click to collapse
I don't really think it would.. I received last week an update (using another recovery but the concept should be the same) and it was complaining about wrong fingerprint. In this recovery the fingerprint (as it should probably be) is customized to a value like Xiaomi/omni_monet/monet:16.1.0/QQ3A.200805.001/spak10031816:eng/test-keys, while the expected one is the one from the official recovery.
Now, either the developer accepts to change the fingerprint to enable OTAs, or who wants to have them out of the box can patch this recovery (without rebuilding from source, I assume here you have a basic knowledge of linux/unix systems):
Download Android Image Kitchen (here);
Unzip it and put the recovery image in the same folder;
Run
Code:
unpackimg.sh
to extract the image (from here on you may need to run commands with sudo);
Edit the file
Code:
ramdisk/default.prop
and look for the word fingerprint, wherever you find a value that looks like the previous (under the properties ro.*.build.fingerprint), replace it with something like
Code:
Xiaomi/monet_eea/monet:10/QKQ1.191222.002/V12.0.2.0.QJIEUXM:user/release-keys
(that's MIUI global, it shouldn't really matter what you put as long as it matches with the incoming update and in case it still complains you can check the recovery log and you'll see what are the allowed fingerprints);
Repack the recovery with
Code:
repack.sh
try it with
Code:
fastboot boot recovery image-new.img
and flash image-new.img as usual if it works;
[I didn't try this procedure on this specific recovery (although I did on a TWRP on which this is mostly based) and I don't take any responsibility for whatever may happen to your device]

Hi, i have installed PB and everything is ok, and now for something i dont know it enter in bootloop and i cant even acess my internal storage because it dont ask the pattern in the begining of the PB. Can anyone help me?

i had your same problem, i solved with otg and reflash the rom, unfortunately you have to do a full wipe

Unfortunately, my phone looks dead. I used PB recovery. xiaomi.eu_multi_MI10LITE5G_V12.0.2.0.QJIMIXM_v12-10 Rom was installed, everything was fine. Magisk 20.4 also.
An OTA update has arrived: xiaomi.eu_multi_MI10LITE5G_V12.1.1.0.RJIMIXM_v12-11
I started and then rebooted after installation: no picture, no sound, full KO.
I tried factory restore, previous nandroid save restore, rebooted the previous ROM, no result: back to TWRP after booting. I tried Stock ROM with MIFlash but it doesn't install with "anti rollback error" error.
Help!

After Format data flash V12.1.1.0.RJIMXM again, after 10 minute booted, but can't activate, can't open WiFi setting!

[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M31

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
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 features included in this recovery before flashing it!
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.
Kernel Features:
latest kernel source release
disabled security stuff/knox/proca/logging/audit/useless features
Recovery Features:
TWRP 3.5.2, Android 10
Built in 64-bit mode
Super partition support
Added custom super binary to help with managing super partitions ( more on that in post #3 )
Native rw mount dynamic partitions
Native GSI flashing
Native dynamic partitions resize/wipe/backup/restore
Working MTP and ADB only!
How to install?
Spoiler: ODIN(Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
Downloads:
TWRP-3.5.2-m31-v1.0
Encryption Disabler
TWRP_Bootlogo_patcher
Sources:
Device Tree: https://github.com/soulr344/android_device_samsung_m31
Kernel Source: https://github.com/soulr344/android_kernel_samsung_m21nsxx/tree/prebuilt
TWRP Source: https://github.com/soulr344/android_bootable_recovery/commits/android-10.0
Credits:
TeamWin, corsicanu, ananjaser1211, jesec, epicX67, exynos-nigg, testers and anyone else who made this possible.

Changelog:
v1.0
Initial Release
More in github release page
MISC LINKS
Telegram Channel
Telegram Group
TeamWin Official Website

FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed encryption disabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: I can't flash anything with TWRP. Internal Storage has some random folders with weird name.
A: Format Data and flash encryption disabler.

Info about custom super partition helper binary. (Irrelevant because of native logical partitions but yeah, its present)
It's meant to help with managing partitions inside the super partition itself. It has some functions built in like mount, unmount, flash and format. Here is a brief rundown on what each of them do.
Partitions that are supported are:
system, system_root, vendor, odm, product
Click to expand...
Click to collapse
Please note that system_root is an alias of system and umount is an alias of unmount.
All of these commands are runnable through TWRP Terminal ONLY!
Code:
super mount partition
This will mount partition in rw mode in mountpoint in fstab.
Code:
super unmount[or umount] partition
This command will unmount given partition and make it read only.
Code:
super format partition
This command will format given partition as ext4 inside super partition.
Code:
super flash partition /path/to/image.img
Flashes image.img to partition.
You can also flash GSI (Generic System Image) using this command. Simply run:
Code:
super flash system /path/to/gsi.img
For Custom ROM Developers:
You can use this as an alternative to mount/format/unmount partitions that are inside super partition normally.
Code:
run_program("/sbin/super", "format", "system"); # formats system
run_program("/sbin/super", "mount", "system"); # mounts system as rw
run_program("/sbin/super", "unmount", "system"); # unmounts system and makes it ro

Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.

Karen3443 said:
Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.
Click to expand...
Click to collapse
nope, you havent bricked. start by flashing stock rom again, the flash twrp, AND BE SURE to flash encryption disabler and format data. thats all and it should boot. if you skip encryption dissabler, then the stock recovery will auto restore itself(which seems your case)

if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.

Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.

drcarlox said:
if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.
Click to expand...
Click to collapse
yes, you'll lose your data. so, backup anthing important

Ahamadmusa said:
Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.
Click to expand...
Click to collapse
tap tag on the github page of bootlogo patcher and download the latest version

soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
Thanks, it worked. Now waiting for custom rom.

soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
i'm getting 404 page not found error,can you provide link?

kogkita said:
i'm getting 404 page not found error,can you provide link?
Click to expand...
Click to collapse
ok found it by searching through google,thx buddy.

M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install

If any custom rom comes for m31 in future,is there any possibility to decrease cpu and gpu voltage offsets?(custom kernel support ?)

dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache

zrekkab said:
dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache
Click to expand...
Click to collapse
it might be a mistake here(states android 10),but on telegram page it was mentioned android 11 only,try upgrading to 11 and flash,all modules perfectly worked for me.

ensonahmet said:
M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install
Click to expand...
Click to collapse
htt ps :/ /github. com/corsicanu /TWRP_Bootlogo_patcher /releases/tag/ v1.3 ,remove the spaces and download this 1.3v file

Thanks
Now build v2

I solved the solution by installing the Indian version of SM-M315F INU M315F XXU2BUC1

Development [RECOVERY] [11] [star/mars] [OFFICIAL] 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.
Hello, this is TWRP, for Mi 11 Pro/Ultra
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_star
https://github.com/TeamWin/android_device_xiaomi_mars
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download:
star: https://twrp.me/xiaomi/xiaomimi11ultra.html
mars: https://twrp.me/xiaomi/xiaomimi11pro.html

Wow
Finally, official TWRP for our device, thanks alot to dev

when i flash it ,i can`t mount my /data
my device is mi 11 star

347111268 said:
when i flash it ,i can`t mount my /data
my device is mi 11 star
Click to expand...
Click to collapse
Are you on android 12?

Nebrassy said:
Are you on android 12?
Click to expand...
Click to collapse
yes

347111268 said:
when i flash it ,i can`t mount my /data
my device is mi 11 star
Click to expand...
Click to collapse
on android 11 the same......

Edlar said:
on android 11 the same......
Click to expand...
Click to collapse
Send logs
adb pull /tmp/recovery.log
adb logcat > logcat.txt

Nebrassy said:
Send logs
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Click to expand...
Click to collapse
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you

jiyuugataki said:
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you
Click to expand...
Click to collapse
did you try if its connected by typing fastboot devices?

jiyuugataki said:
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you
Click to expand...
Click to collapse
Try going to mount menu, disable mtp and enable it, then check id adb is recognized

Nebrassy said:
Try going to mount menu, disable mtp and enable it, then check id adb is recognized
Click to expand...
Click to collapse
Worked, here are the logs
Thx !
Edit : That's strange, when i try to attach files, they upload and then disappear when i save
so, recovery :
recovery.log - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
logcat part1 : https://pastebin.com/ZPenY56E
part 2 : https://pastebin.com/6MYkJs5R

marcel112 said:
did you try if its connected by typing fastboot devices?
Click to expand...
Click to collapse
Tried and no problem
But, solved, thank you nonetheless

Hello everyone, I can't access to my data in TWRP completely because I want to flash magisk; any solution?

datadelrey said:
Hello everyone, I can't access to my data in TWRP completely because I want to flash magisk; any solution?
Click to expand...
Click to collapse
did you remove password or pin?

Great news!
I am wondering if there is a roadmap when TWRP will be available for A12?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Everything is fine, a log file appeared after I backed up the boot, I hope it's useful

please make a clear tutorial on how to fix the unable to mount/data
i removed the pin and password before fastboot boot twrp.img, go to advanced flash current twrp, and when i restart the device it goes to fastboot again.

Nebrassy said:
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Click to expand...
Click to collapse
How to update if we are currently use a different TWRP? I mean not "official".

Mi 11 Ultra / star
Using EU 12.5.20 and twrp 3.5.1
Update to 3.6.0 via Install Zip in 3.5.1
Reflash EU rom after update twrp and booted normally now.
Working fine. Thank you.

@hacker738 and now check, which version of TWRP is installed
if 3.6.0 then I'll really congratulate you

[ROM][13][wayne][Kernel 4.19][UNOFFICIAL]LineageOS 20.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* 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 features included in this ROM
* before flashing it! 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.
*/
Working:​- Wifi
- Sound
- USB tethering
- RIL
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- Camera
- GPS
- Fingerprint
- Dac(usb audio)
Flash guide:​Before you start...​- Be sure your partitions size is original, this is **IMPORTANT**, or you may brick your device.
- You need to backup your data, your data partition will be formatted.
Preparations​- Android Debug Tools
- Dynamic Partition Supported Recovery. Download
- super_empty.img Download
- Connet your device to PC
Then...​1. Flash Dynamic Partition Supported Recovery into your device
Bash:
fastboot flash recovery <RECOVERY_PATH>
2. Flash super_empty.img into your device
Bash:
fastboot wipe-super <super_empty_PATH>
3. Reboot to recovery
Bash:
fastboot reboot recovery
4. Format your data partiton in recovery
5. Install Dynamic Partition ROMS into your device by:
Apply update—>Apply from ADB
Now, be sure your device is connected to your PC, and run
Bash:
adb sideload <ROM_PATH>
6. Reboot and enjoy
Picture​
Download:​Release
If you want to give me some money to support my work, please contact telegram @xiaoleGun
Source Code:​device
vendor
kernel
ROM OS Version: Android 13
ROM Kernel: Linux 4.19.271

Compared with A2, the A13 ROM of mi6x is very small. I can see this newly developed version, and I feel that my 6x can survive again. Thank you very much

xiaoleGun said:
View attachment 5823351
Code:
/*
* 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 features included in this ROM
* before flashing it! 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.
*/
Working:​- Wifi
- Sound
- USB tethering
- RIL
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- Camera
- GPS
- Fingerprint
- Dac(usb audio)
Flash guide:​Before you start...​- Be sure your partitions size is original, this is **IMPORTANT**, or you may brick your device.
- You need to backup your data, your data partition will be formatted.
Preparations​- Android Debug Tools
- Dynamic Partition Supported Recovery. Download
- super_empty.img Download
- Connet your device to PC
Then...​1. Flash Dynamic Partition Supported Recovery into your device
Bash:
fastboot flash recovery <RECOVERY_PATH>
2. Flash super_empty.img into your device
Bash:
fastboot wipe-super <super_empty_PATH>
3. Reboot to recovery
Bash:
fastboot reboot recovery
4. Format your data partiton in recovery
5. Install Dynamic Partition ROMS into your device by:
Apply update—>Apply from ADB
Now, be sure your device is connected to your PC, and run
Bash:
adb sideload <ROM_PATH>
6. Reboot and enjoy
Picture​View attachment 5823361View attachment 5823365
Download:​Release
If you want to give me some money to support my work, please contact telegram @xiaoleGun
Source Code:​device
vendor
kernel
ROM OS Version: Android 13
ROM Kernel: Linux 4.19.271
Click to expand...
Click to collapse
I follow the installation steps, but the result cannot be installed smoothly. Is there any way to solve it, thank you

mouse723 said:
I follow the installation steps, but the result cannot be installed smoothly. Is there any way to solve it, thank youView attachment 5828119
Click to expand...
Click to collapse
You can try this recovery.img

xiaoleGun said:
- Be sure your partitions size is original, this is **IMPORTANT**, or you may brick your device.
Click to expand...
Click to collapse
How to know if it is? because mine was originaly a Mi A2 that i converted into a Mi 6X like a long time ago (back when guides to do so were fairly new) but haven't had issues flashing any rom on it so

demonoidmaster said:
How to know if it is? because mine was originaly a Mi A2 that i converted into a Mi 6X like a long time ago (back when guides to do so were fairly new) but haven't had issues flashing any rom on it so
Click to expand...
Click to collapse
The size of the system partition is 3221225472 bytes

xiaoleGun said:
The size of the system partition is 3221225472 bytes
Click to expand...
Click to collapse
Had your previous 19.1 build installed but tried flashing this one and it's giving me a liblp error about geometry magic signature being invalid
(Haven't flashed the super wipe zip yet because I wanted to know your opinion about my device type before doing that as mine isn't a oem Wayne model but rather a mi a2 converted into a Wayne model)

demonoidmaster said:
Had your previous 19.1 build installed but tried flashing this one and it's giving me a liblp error about geometry magic signature being invalid
Click to expand...
Click to collapse
try this recovery.img

xiaoleGun said:
try this recovery.img
Click to expand...
Click to collapse
what about their same recovery under the v11 tag ? it's newer than v10.1
EDIT: flashed their v11 recovery and rebooted to fasboot for super-wipe zip flash, then flashed xiaomi firmware in recov, wiped data.cache.metadata tried flashing but still gave dynamic partition error so i just did a quick reboot to recov first to make sure and tried again and sure enough it flashed fine, about to reboot to OS now, gonna edit again if booted
EDIT2: booted, just gotta restart to recov to flash nikgapps

xiaoleGun said:
try this recovery.img
Click to expand...
Click to collapse
trying to flash nikgapps (v13 for android 13) but it keeps failing with error /sideload/package.zip (status1) and i just don't know what else to do, can't even try litegapps++ microg either because it fails with that error too

demonoidmaster said:
trying to flash nikgapps (v13 for android 13) but it keeps failing with error /sideload/package.zip (status1) and i just don't know what else to do, can't even try litegapps++ microg either because it fails with that error too
Click to expand...
Click to collapse
Use magisk module, because we use erofs

xiaoleGun said:
Use magisk module, because we use erofs
Click to expand...
Click to collapse
is there no way to remount as read-write (on my other phone i mount then do mount -o remount,rw /product or such to remount as read-write when needed) ? i don't want magisk on this phone because i'm setting it up to give to someone so i don't want to have it use gapps as a module, besides i don't think nikgapps supports installing as module

demonoidmaster said:
is there no way to remount as read-write (on my other phone i mount then do mount -o remount,rw /product or such to remount as read-write when needed) ? i don't want magisk on this phone because i'm setting it up to give to someone so i don't want to have it use gapps as a module, besides i don't think nikgapps supports installing as module
Click to expand...
Click to collapse
You can repackage the system image

xiaoleGun said:
You can repackage the system image
Click to expand...
Click to collapse
this is honestly getting overly complicated for just trying to set up a basic rom...
just tried flashin magisk but nada doesn't work gives error 127, i'm switching back to a rom that works

hi xiaole cant use gboard on this rom..

Working flawlessly with MicroG and some Magisk modules.
Im very happy with this rom.

cant use wifi, cant use gapps, cant start setup wizard even if the gapps package had setup in it. Camera not work, a lot of bugs for me.

MI 6X released in 2018, can use android 13 smoothly, and no lag, no heat, stable and no self-reboot, all functions look normal so far(The camera app will black out, use Opencamera instead). Very exciting ROM. Looking forward to seeing the double tap to wake feature in the next version.

I can't install MindTheGapps, help! On the Recovery console:
Code:
Low resource device detected, removing large extras
Not enough space for Gapps! Aborting
Cleaning up files
Unmounting partitions
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed wtih status 1.
Installation aborted.
I have tried the following MindTheGapps:
MindTheGapps-13.0.0-arm64-20230408_162909.zip
MindTheGapps-13.0.0-arm64-20230323.zip
MindTheGapps-13.0.0-arm64-20221025_100653.zip
Then I tried NikGapps:
NikGapps-core-arm64-13-20230418-signed.zip
NikGapps-basic-arm64-13-20230418-signed.zip
But both gave errors:
Code:
...
Installing update...
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1.
Installation aborted.
Please help, thank you!

i have problem :/