Database Develop

[TWRP][64 bit][3.2.1_r12][UNOFFICIAL]Moto Z2 Play[Albus]

TWRP 3.2.1_r12 Moto Z2 Play (albus)​
{
"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"
}
TWRP changelog : Here
Working/Bugs : Need to press power button two times for touch to work
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :Here
Tree : Here
XDA:DevDB Information
TWRP-ALBUS, Tool/Utility for the Moto Z2 Play
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2018-01-03
Last Updated 2018-02-03

I've been using this today to set up my phone fresh. I created a backup, installed stock twrp flashable rom, installed magisk, and magisk module zips all just fine.
Thanks for this.

Trying to set up my new Moto Z2 Play today.
I just unlocked the bootloader, so I'm good there. I wanted to install Magisk and leave it mostly stock. If I was going to just "fastboot boot twrp.img'' (instead of flashing) can I use this TWRP or should I just follow the instructions and use the TWRP version in this other thread?
Is this version more functional?
Would I be able to make a backup if I boot the TWRP instead of flashing?
Can I use the SD Card/internal storage with this version or do I have to still use the OTG cable and a flash drive to hold the DM Verity and Magisk ZIPs?

Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx

JRapsky said:
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
Click to expand...
Click to collapse
my experience is, you have to flash TWRP.
I don't think it has the necessary read/write permissions to do a full backup otherwise.

3.1.2_r18 version released. Check download link in OP

hi guys.
I successed to twrp temporary boot.
Successed to full backup (with all check).
Is it safe for permanent flash twrp right now?
p/s: After backup success, I reboot my phone and check TWRP folder but nothing here
so why?

fastboot boot twrp-xxxx.img
freeze at teamwin logo
O flash twrp and its ok

rodacoregio said:
fastboot boot twrp-xxxx.img
freeze at teamwin logo
Click to expand...
Click to collapse
Twrp temporary boot works fine for me.
Some guys said install it can fix your problem.

I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
But Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?

Mark2014 said:
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Click to expand...
Click to collapse
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.

kewlzter said:
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
Click to expand...
Click to collapse
It show me No command when i reboot to recovery mode by command
adb reboot recovery
was I wrong somethings ?
OS's still boot fine.

Mark2014 said:
It show me No command when i reboot to recovery mode.
was I wrong somethings ?
Click to expand...
Click to collapse
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.

kewlzter said:
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
Click to expand...
Click to collapse
tks. it works.
I trying format Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM copied in SD card?

Mark2014 said:
tks. it works.
I trying flash Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM in SD card?
Click to expand...
Click to collapse
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.

kewlzter said:
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
Click to expand...
Click to collapse
Tks. I did a full backup .
tks again.
I will try now.

I make a full backup, so can I restore that backup file after LineageOS?

This works when go command fastboot boot .... ?

I'm having an issue... I've successfully flashed r18, but it cannot seem to mount the data partition. It fails to mount (just hangs for a moment when you check the box next to data), fails to wipe (Could not mount/data and unable to find crypto footer... Failed to mount '/data' (Invalid argument)).
Never mind... I just tried it a 3rd time and it worked. Not sure what's going on there.
**OK** Now, I've flashed the Unofficial LOS and OpenGapps from the thread by OP, following all instructions, and the phone boots to recovery every time I try to boot to system...

Recent success, z2 Play XT1710-06
Just to add to the success stories: A newly-purchased Moto z2 Play, variant XT1710-06 dual SIM, Android 7.1.1, RETLA release channel, build NPSS26.118-19-1-6. My object was to install root only, not (at this time) do any custom ROM flashes.
With this in mind: I used TWRP-3.2.1-0(Albus) after doing the initial bootloader unlock. Quirks noted during install was that I needed to repeat the 'fastboot flash recovery' option 3-4 times to get TWRP to stay put in the 'recovery' partition. Also, as an experiment, I tried renaming the TWRP image to 'recovery.img' (which seems to help).
Once TWRP was in place, I downloaded and installed the most current Magisk (v16). It worked perfectly, the first time, no issues at all (and it even knew to install its management app on its own). Despite my initial leanings, I chose not to try SuperSU due mainly to the developer changes at Chainfire HD (original developer retired, product bought up by some unnamed Chinese group).
Now I get to reinstall all my apps... (sigh). Such is the price of getting the phone we Really Want...
I hope this makes life easier for others.
Keep the peace(es).

Treble Guide [ H3213 ]

Hi, I found out how Treble Roms finally works
all at your own risk
{
"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"
}
New Firmware
OK guys let's start ..... we need
1 . Sony Xperia Xa2 ultra [ H3213 ] Testet with Europe Germany or use XperiFirm to Download the Latest Pie Update
2 . Firmware
3 . Newflasher
4. Twrp for Discovery
5 . Treble Rom 64a/b
6 . Gapps pack
7 . Fastboot
Thats all
Let us begin !!!!
1 . Ok first boot the Xperia xa2 ultra in Factory mode (Connect with Usb 2.0 power and Volume -)
2 . Download the Firmware , unzip and flash with Newflasher ( in linux sudo ./newflasher.x64 )
3 . Boot in Twrp Recovery (fastboot boot twrp-3.2.3-1-discovery.img )
4 . wipe all ... system , art ,cache
5 . Download a Treble rom i have testet with Viper Os and Havoc , Bootleggers
6 . flash the Treble GSI ( fastboot flash system_a Treble_Gsi_image .img )
7 . Boot into Twrp Recovery set Bootslot A
8 . Go to wipe and select -> Advanced -> select the -> system partition and -> Select Resize ->swipe and done
9 . Go to install and install the OpenGapps Pack when its Done ....wipe all Factory Reset ......and Reboot .....Done ...... its Booting in your Treble Rom
what works ..... almost everything
workaround for Messages on Boot which is not that bad
Message on each boot: "Android System: There's an internal problem with your device. Contact your manufacturer for details" or "Vendor mismatch" error message before unlocking:
A. In a root file manager, backup both \vendor\build.prop and \system\build.prop files.
B. Open \vendor\build.prop original file with a root text editor. Copy the line with ro.build.fingerprint variable.
C. Open \system\build.prop original file with a root text editor. Find the line with ro.build.fingerprint variable and paste the copied vendor variable over the system one (replace).
D. Save the \vendor\build.prop file.
E. Reboot.
Thanx and Greetz
@phhusson
@IgorEisberg for XperiaFirm
@Sony
if you like it expresses the thanks button

First

tried liquidremix ab-boots up in boot animation then boot loop goes back again restarts boot process. Maybe because I could not see resize option in the advanced wipe system partition (459mb were extra but could not see any option to reclaim that space)
EDIT trying again with havoc but with twrp 3-3 (do see the resize option now EDIT3 did not see resize option as had kept system read only on first attempt-duh!)
EDIT2 followed all steps including the last factory reset in twrp-bootloop (goes to android bootanimation and returns back to boot)
would imagine have to swipe to allow modifications in twrp opening screen
anyway tried now both havoc and liquid os both run into boot loops
could you detail any missing (or taken for granted) intermediate steps? like the swipe to allow modifications..do you format (not just wipe) data too? (or wipe internal storage-though I tried those) thanks!

appreciate your assistance thanks please see my earlier message on bootloops and any possible missing steps

mac231us said:
tried liquidremix ab-boots up in boot animation then boot loop goes back again restarts boot process. Maybe because I could not see resize option in the advanced wipe system partition (459mb were extra but could not see any option to reclaim that space)
EDIT trying again with havoc but with twrp 3-3 (do see the resize option now EDIT3 did not see resize option as had kept system read only on first attempt-duh!)
EDIT2 followed all steps including the last factory reset in twrp-bootloop (goes to android bootanimation and returns back to boot)
would imagine have to swipe to allow modifications in twrp opening screen
anyway tried now both havoc and liquid os both run into boot loops
could you detail any missing (or taken for granted) intermediate steps? like the swipe to allow modifications..do you format (not just wipe) data too? (or wipe internal storage-though I tried those) thanks!
Click to expand...
Click to collapse
what did you have for a model with me, everything worked out right away
I deleted system a before I flashed the rom
I can read the steps again
1 . flashing the firmware via Newflasher
2 . Boot into Twrp and wipe all Data system cache etc
3 . Boot into Fastboot modus and fastboot erase system_a
4 . flash the Treble GSI ( fastboot flash system_a Treble_Gsi_image .img )
5 . Boot into Twrp and allow all ........set Bootslot A and go to wipe -> advanced -> check system and press filesystem .....and -> resize
6 . Go to install and install the OpenGapps Pack when its Done ....wipe all Factory Reset ......and Reboot .....Done ...... its Booting in your Treble Rom

noobstyle1337 said:
what did you have for a model with me, everything worked out right away
I deleted system a before I flashed the rom
I can read the steps again
1 . flashing the firmware via Newflasher
2 . Boot into Twrp and wipe all Data system cache etc
3 . Boot into Fastboot modus and fastboot erase system_a
4 . flash the Treble GSI ( fastboot flash system_a Treble_Gsi_image .img )
5 . Boot into Twrp and allow all ........set Bootslot A and go to wipe -> advanced -> check system and press filesystem .....and -> resize
6 . Go to install and install the OpenGapps Pack when its Done ....wipe all Factory Reset ......and Reboot .....Done ...... its Booting in your Treble Rom
Click to expand...
Click to collapse
so no format data (after swipe to allow modifications) and no wipe internal storage (as in wipe all as you had "etc" for wipe all)
thanks please confirm will try again (have xa2 ultra h3213 bootloader unlocked)

mac231us said:
so no format data (after swipe to allow modifications) and no wipe internal storage (as in wipe all as you had "etc" for wipe all)
thanks please confirm will try again (have xa2 ultra h3213 bootloader unlocked)
Click to expand...
Click to collapse
yes no data format and all wipe ......wipe storage ,system ,data ,cache art dalvic then in fastboot mode fastboot erase system_a and then fastboot flash system_a system.img

noobstyle1337 said:
yes no data format and all wipe ......wipe storage ,system ,data ,cache art dalvic then in fastboot mode fastboot erase system_a and then fastboot flash system_a system.img
Click to expand...
Click to collapse
thanks...maddening that it is not working (for me). Will keep trying. Used havoc (a), havoc (a/b), liquid (a), liquid (a/b). Get to boot animation then back to the boot (unlocked bootloader screen).

What is this?
Is this some kind of root method for stock?
Or is it like Lineage, a new Android operating system altogether?

[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

General [SHARED] [ROM] MiuiMiX Rom 13.0.4.0 Redmi Note 10 Pro [sweet] 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"
}
Stable MiuiMiX Rom for the Xiaomi Redmi Note 10 Pro [sweet]
MiuiMiX is a custom build Rom based on xiaomi.eu and china beta firmware.
Created to give you the best experience while maintaining a smooth os and long battery life.
MiuiMiX comes prerooted and Magisk is installed right out of the box, it´s even more debloated without missing important apps. All Roms from us are beeing globalized.
You can check out all features on our site or supportchannels.
All known Miui Bugs
If you find any other bug, please report them to us!
Pre-requisites:
Unlocked bootloader
Custom recovery (See the recommended recoveries)
Read the FAQ
Clean Flash (If you are coming from another ROM or you are changing between stable and weekly builds):
Boot into your custom recovery
Wipe system and vendor (highly recommended when coming from non-MIUI rom)
Format Data (the one with "YES", isn't the same as a wipe data)
Reboot into recovery
Copy the ROM zip into your internal storage or to your SD card
Flash the ROM. (Gapps and Magisk are built-in. Firmware and vendor are inside all zip files)
Wipe dalvik/art cache and cache
Reboot system and enjoy! (First boot may take up to 5-10 min.)
Updating coming from a previous version of the rom (Dirty flash, only stable over stable or weekly over weekly. Never weekly over stable or vice versa.):
It is recommended to deactivate ALL magisk modules before updating
Reboot into recovery
Flash lastest MiuiMiX build
Wipe dalvik/art cache and cache
Reboot system
DOWNLOAD Link

Pertamax

Flash via fastboot or recovery? The file name is fastboot but in instructions flashing via recovery

"see recommended recoveries" - where ?
"see FAQ" - where ?

magisk does not work

[email protected] said:
Flash via fastboot or recovery? The file name is fastboot but in instructions flashing via recovery
Click to expand...
Click to collapse
is fastboot

do gestures work with 3rd party launchers?

Ashle said:
magisk does not work
Click to expand...
Click to collapse
24 or higher is needed(support a12)

Which recovery have to use?

@Murad Ali Perhaps it would be a good idea to correct the first post? The installation steps do not apply to this ROM at all, since it's a fastboot ROM...
@prashant.palange None. As mentioned above, it is a fastboot ROM. It's installed via fastboot (so needs PC) and includes two batch files for installation. If coming from a stable MiuiMix ROM version, you can use the "update" one, if from weekly (or if you want to do a clean install anyway), then use the "install with data format" one, but bear in mind this one (quite obviously) formats your data partition INCLUDING internal storage, so backup everything you want to keep beforehand.

Case_ said:
@Murad Ali Perhaps it would be a good idea to correct the first post? The installation steps do not apply to this ROM at all, since it's a fastboot ROM...
@prashant.palange None. As mentioned above, it is a fastboot ROM. It's installed via fastboot (so needs PC) and includes two batch files for installation. If coming from a stable MiuiMix ROM version, you can use the "update" one, if from weekly (or if you want to do a clean install anyway), then use the "install with data format" one, but bear in mind this one (quite obviously) formats your data partition INCLUDING internal storage, so backup everything you want to keep beforehand.
Click to expand...
Click to collapse
good but this is not fastboot file. regular zip.

@Murad Ali The link in your post leads to the fastboot install .zip archive you get from official MiuiMix sources (it's literally the same link). It even says "fastboot" right there in the archive filename. It is not a ROM that installs via recovery, because there is no fully working recovery for Android 12. You unpack the zip on a PC and install the ROM via fastboot (which is even included in the archive, along with the installation batch files, so the installation is as straightforward as possible).
I'm frankly kinda surprised you seem to have no idea what you have linked here (and made a thread for).

Case_ said:
@Murad Ali The link in your post leads to the fastboot install .zip archive you get from official MiuiMix sources (it's literally the same link). It even says "fastboot" right there in the archive filename. It is not a ROM that installs via recovery, because there is no fully working recovery for Android 12. You unpack the zip on a PC and install the ROM via fastboot (which is even included in the archive, along with the installation batch files, so the installation is as straightforward as possible).
I'm frankly kinda surprised you seem to have no idea what you have linked here (and made a thread for).
Click to expand...
Click to collapse
sorry i am not a developer. I liked and shared the rom, if there is a mistake it will be corrected. Also, the link says it's a fastboot rom.

@Murad Ali Well, like I already said, there's indeed a mistake, in that basically the entire first post with all the info on how to flash the ROM is wrong. Pretty much none of what is mentioned there applies, it's all meant for a recovery ROM update, whereas this one is a fasboot ROM update.
Here's what the second part of the first post should look like (for example - feel free to use it if you want):
Pre-requisities:
Unlocked bootloader
PC with unpacked contents of the .zip archive you've downloaded, including folder structure (important)
Custom recovery is not needed for this ROM! You will not be using it at all! At the time of this writing, there is no fully working Android 12 custom recovery, none of them can decrypt an encrypted data partition. If you have custom recovery currently installed on your phone, it will however not be affected by the ROM install/update procedure (but it will still not be able to decrypt an encrypted data partition).
Clean Flash (If you are installing from scratch, coming from another ROM or you are changing between stable and weekly builds):
Backup all the data from your phone you don't want to lose, including the internal storage (photos, messages e.g.) The install process will do a complete wipe of your data including your internal storage! (External SD should be fine.)
Boot your phone into fastboot (bootloader) mode
Connect the phone to PC (make sure you have the correct drivers installed for fastboot mode)
Run the "fastboot_first_install_with_data_format" script/batch for your platform (windows/linux/macos).
The ROM will now be flashed to the phone automatically and then a factory reset of your phone will be done.
You are done. Your phone should now reboot into your new ROM. (First boot may take up to 5-10 min.)
Updating coming from a previous version of the rom (This includes coming from a MIUI 12/A11 stable version of the MiuiMix ROM. Dirty flash, only stable over stable or weekly over weekly. Never weekly over stable or vice versa.):
(Optional) Backup all the data from your phone you don't want to lose, including the internal storage (photos, messages e.g.) - This is not required for update, you should not lose anything, but it's a good safe practice anyway.
Boot your phone into fastboot (bootloader) mode
Connect the phone to PC (make sure you have the correct drivers installed for fastboot mode)
Run the "fastboot_update_rom" script/batch for your platform (windows/linux/macos).
The ROM will now be updated on your phone automatically.
You are done. Your phone should now reboot into your updated ROM. (First boot may take up to 5-10 min.)
It is recommended to deactivate ALL magisk modules before updating.
DOWNLOAD Link

Hello friends, I really apreciate this ROM but I have a problem... not only with this ROM, but with all Xiaomi ROMs...
I'm a tester, I like to test a lot of aplications, ROMs, anything. Of course, I need a system backup in case something goes wrong... But I cannot backup in custom recovery (TWRP or OrangeFox) because Data partition cannot be mounted, it shows "0 MB"...
I tried everything found on google but nothing works... the same 0 MB data partition... I even tried this in fastboot:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
but powershell or cmd shows "--disable-verity unrecognized option"
Please, can anybody help me? Thank you.

Hellera said:
Hello friends, I really apreciate this ROM but I have a problem... not only with this ROM, but with all Xiaomi ROMs...
I'm a tester, I like to test a lot of aplications, ROMs, anything. Of course, I need a system backup in case something goes wrong... But I cannot backup in custom recovery (TWRP or OrangeFox) because Data partition cannot be mounted, it shows "0 MB"...
I tried everything found on google but nothing works... the same 0 MB data partition... I even tried this in fastboot:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
but powershell or cmd shows "--disable-verity unrecognized option"
Please, can anybody help me? Thank you.
Click to expand...
Click to collapse
In twrp and ofox it's not possible.
You have to be encrypted to do that in Recovery with android A12 , I think also in A11.
But I'll think you can do it if booted and rooted with alphabackup

Laptapper said:
In twrp and ofox it's not possible.
You have to be encrypted to do that in Recovery with android A12 , I think also in A11.
But I'll think you can do it if booted and rooted with alphabackup
Click to expand...
Click to collapse
Thank you @Laptapper, I tried a custom ROM, crDroid with A12 and it works... I can backup/restore everything... with MIUI ROMs doesn't work.

@Hellera Those ROMs likely don't use encrypted data partition (which is a security risk). If you disable any screen locks you might have in your MIUI ROM, you should be able to see and use the data partition just fine (I did that with TWRP 3.6 and MiuiMix 13.0.2). However, whether or not you will be able to correctly backup and (more importantly) restore a ROM like that to a working state in case you need to has to be tested more.
Also once you set up a screen lock again, the data partition gets encrypted again.

Case_ said:
@Hellera Those ROMs likely don't use encrypted data partition (which is a security risk). If you disable any screen locks you might have in your MIUI ROM, you should be able to see and use the data partition just fine (I did that with TWRP 3.6 and MiuiMix 13.0.2). However, whether or not you will be able to correctly backup and (more importantly) restore a ROM like that to a working state in case you need to has to be tested more.
Also once you set up a screen lock again, the data partition gets encrypted again.
Click to expand...
Click to collapse
@Case_ I never use any screen locks and I'm on MiuiMix 13.0.2, twrp and ofox doesn't see data partition, 0 MB... I think is about the android version 12... with version 12.5.7 android 11 I had not such problems... Is frustrating...

@Hellera Well, like I said, for me disabling fingerprint and PIN worked on MiuiMix 13.0.2. I guess there are more reasons why the data partition might stay encrypted even if you disable any screen locks.

Development [RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2021 Galaxy Tab A8 10.5 [SM-X200]

{
"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"
}
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
Downloads:
twrp_3.7.0_12-2_X200XXS1CWA3.tar.md5
twrp_3.7.0_12-2_X200XXS1CWA3.img
Change Log:
v3.7.0_12-2 (2023-02-28):
Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
v3.7.0_12-1 (2023-01-22):
Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).
v3.7.0_12-0 (2023-01-01):
Fixed issue with MTP sometimes not starting until state is toggled in the Mount panel.
Switched to TWRP 3.7.0 release built from new AOSP-12.1 branch.
Updated to X200XXS1BVJ1 (Android 12) OEM stock kernel (Oct 2022 Security Update).
v3.7.0_11-1 (2022-10-24):
Adjusted dynamic partition size and removed redundant backup image.
v3.7.0_11-0 (2022-10-09):
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
Updated to X200XXU1BVI6 (Android 12) OEM stock kernel.
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.

Additional Notes:
Ian's Multidisabler script has an issue on this device preventing it from disabling stock recovery auto-restoration. I'm hoping that a fix is forthcoming.
If you root this device with Magisk, be sure to patch only the boot.img file. Patching the AP tarball will generate a blank vbmeta.img, which this device's bootloader doesn't like for some reason.

Works on LTE version sm-x505 ??
Also which is better tab A7 or tab A8 ??

works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.

Magendanz said:
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
MTP doesn't start until you disable and reenable in the Mount panel
Downloads:
twrp_3.6.2_11-0_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-0_X200XXU1AVG1.img
Change Log:
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Click to expand...
Click to collapse
I am so delighted to see that there is major development for this device.
This will open the door for future custom ROMs.
Thank you Magendanz for your effort in bringing this to us.

I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol

Tony Ronaldo Matute said:
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Click to expand...
Click to collapse
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.

Magendanz said:
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Click to expand...
Click to collapse
I had tried different ways also but I give up, the only thing that I can think now is try to use the "reboot to bootloader" feature in TWRP. But well, this processor is going me crazy.

Magendanz said:
Reserved
Click to expand...
Click to collapse
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.

zfk110 said:
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
Click to expand...
Click to collapse
No, you should patch the boot.img using the Magisk app, then flash it using TWRP or pack in a tarball and use Odin. Don't patch the whole AP, as Magisk will substitute a blank vbmeta.img that the bootloader on this device doesn't like.

Rularick5 said:
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Click to expand...
Click to collapse
Was just going to try this method but I'm on AVC1...I'm assuming I need to be on AVG1?

As long as the binary number is the same, im assuming dont quote me, you should be able to flash avg1 then magisk then twrp. Just update to the latest firmware.

I figured that's what I had to do but was trying to avoid that....just rooted a week ago and had no idea about AVG1.
So if I want to upgrade to AVG1 or any other firmware in the future I have to do the whole process again of patching boot.img, flashing through Odin, factory reset and setting up everything again? There's no way to upgrade and retain root?

Not unless you can recieve ota while rooted.

New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.

Magendanz said:
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Click to expand...
Click to collapse
Any news for GSI?

Tony Ronaldo Matute said:
Any news for GSI?
Click to expand...
Click to collapse
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.

Magendanz said:
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Click to expand...
Click to collapse
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?

Tony Ronaldo Matute said:
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Click to expand...
Click to collapse
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.

Magendanz said:
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Click to expand...
Click to collapse
So, first you can try this disabler:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
as well, you can try to use this fastbootd command:
[Solved] VBmeta Flashing and Disable Verity Verification Command Problem
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img. Most of the time the below command does not work and causes bootloop, when Installing Custom recovery. So i...
forum.xda-developers.com