Database Info

[RECOVERY][enchilada] Unofficial TWRP 3.2.1-3 for OnePlus 6 by wuxianlin

Entire credit goes to @wuxianlin; I've just mirrored and organised stuffs.
Downloads:
Baidu
AFH mirror
Fixed variant by @joemossjr & @charlieb620
Sources:
https://github.com/wuxianlin/android_device_oneplus_enchilada
http://wuxianlin.com/
Screenshots:
https://m.weibo.cn/status/4243215098108813
Instructions:
Download required files from Downloads section.
Unlock the bootloader.
Reboot to bootloader.
Boot into TWRP: fastboot boot recovery-xx.img
Change Partition slot using TWRP: [Reboot => Change_Slot]
(for example, if you're in slot A, change it to slot B and vice versa)
Flash twp-installer zip.
Flash Magisk (use latest) for root access (optional).
Success!

Reserved for future.

Sweet, will give it a shot! Thanks!
Sent from my [device_name] using XDA-Developers Legacy app

Nice

Can't you just do fasboot flash recovery nameofrecovery.img?

JazzieBoi said:
Can't you just do fasboot flash recovery nameofrecovery.img?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76626087&postcount=127

Nice
Sent from my ONEPLUS A6000 using Tapatalk

akaHardison said:
Finally,TWRP is ready.
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Finally? Dude the phone has been out like 3 days in the US and less than 2 weeks I believe anywhere else.
Get some patience maybe.

Is this still a temporary recovery or does this method make TWRP your permanent recovery?

Eric214 said:
Is this still a temporary recovery or does this method make TWRP your permanent recovery?
Click to expand...
Click to collapse
You need to flash TWRP-installer in TWRP, if you want permanent recovery.

Thaaank you very much!

Titokhan said:
Download required files from Downloads section.
Boot into TWRP: fastboot boot recovery-xx.img
Click to expand...
Click to collapse
Which files are required? There are a bunch of different files on that Baidu page.
Which image file should be booted to?

Displax said:
You need to flash TWRP-installer in TWRP, if you want permanent recovery.
Click to expand...
Click to collapse
where can I get twrp-installer from?

Displax said:
You need to flash TWRP-installer in TWRP, if you want permanent recovery.
Click to expand...
Click to collapse
so will making twrp permanent remove the a/b partition? that means i can't flash a/b compatible roms?

@nathanchance... I miss you
Enviado desde mi ONEPLUS A6003 mediante Tapatalk

There is really a lot of files in there. Which img should I boot into for the twrp?

There is a textfile in chinese (i assume) which I let go through google translate:
textfile
Maybe this will give some new information:
Code:
One plus six use ab partition, bring a lot of inconvenience to the brush, temporarily suggest less toss
One, unlock BootLoader (pay attention to backup data)
1. Developer Options Open OEM Unlock
2. Enter the fastboot mode: adb reboot bootloader
3. Unlock: fastboot oem unlock
The mobile phone prompts whether to unlock, the volume key selects Yes, the power button confirms
4 wait to boot
Second, brush into the specific boot
1. The disk boot folder has many types of boot
Introduction:
Official boot: the official original boot, recovery mode for the official recovery
Twrp boot: After brushing into recovery mode becomes twrp
Boot-with-magisk: automatically install migisk after brushing, recovery mode is official recovery, need to install magisk apk
Twrp boot-with-magisk: automatically install migisk after brushing, recovery mode is twrp, need to install magisk apk
name:
For example, boot-180513-h2os.img is based on the hydrogen OS 180513 version, be sure to match the use
Other files are similarly named
2. Brushing method
Enter the fastboot mode: adb reboot bootloader
Brush into the boot partition (boot.img is the path to the file being flushed into)
Fastboot flash boot boot.img
or
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
3. Restart
Fastboot reboot
Third, fastboot brush
Network disk fastboot flashable folder stored fastboot mode can be brushed into the img file
For example, you want to brush the system.img to the system partition (system.img is the path to the file you are working on)
Fastboot flash system system.img
or
Fastboot flash system_a system.img
Fastboot flash system_b system.img
For example, you want to brush the vendor.img to the vendor partition (vendor.img is the path to the file to be scanned)
Fastboot flash vendor vendor.img
or
Fastboot flash vendor_a vendor.img
Fastboot flash vendor_b vendor.img
Fourth, twrp card brush official ROM reserved twrp method
Twrp card brush official ROM brush common patch /twrp folder under the patch package
Note, twrp card brush official ROM, in fact, brush into the current partition does not start, after brushing is complete, activate the partition, restart after running this partition, but at this time twrp run in the current boot partition, need to restart the system into twrp Or restart the recovery mode into twrp, restart the boot partition and the partition started at this time is consistent, brush into the patch for the current boot partition has a role, otherwise the patch package is likely to be brushed into the next boot does not start Partition
Fifth, install magisk
If it is fastboot brush boot, directly brush into the boot with magisk
If it is twrp card brush official ROM, card brush twrp patch, restart twrp or restart boot into twrp, and then brush the patch under the commonly used patch / magisk folder
Six, install the supersu
Twrp card brush official ROM, card brush twrp patch, restart twrp or restart boot into twrp, and then brush the patch / supersu folder patch, even the computer input adb disable-verify, prompt Successfully disabled verity, restart
Seven, install xposed
If you have installed magisk, install xposed directly in magisk
If you have already brushed supersu according to the above method, add the official xposed patch and restart it.
Eight, third-party ROM
Temporarily unknown
Nine, expand the extension
Interested friends are expected to notice that you can choose to brush img into the _a or _b partition in the tutorial of brushing the img into the corresponding partition.
So how do we know if our phone is currently using a partition or b partition?
1.twrp mode, restart, there will be shown below
2. System mode, adb shell getprop ro.boot.slot_suffix
If _a is a partition, _b is partition b
AB Division, except for Google’s mobile phone, it is rare to see other mobile phones use,,,
So there are few methods related to playing online games,,,
Author:
Wuxianlin
Weibo: wuxianlin000000

You can't flash the recovery image... It boots up slowly into the OS, and that's it. Guess we will have to wait a little longer

The TWRP of OP6 looks like Google Pixel this time

Thanks!!!
But which version (file) do I need for Oxygen OS 5.1.5?
In each filename is someting with h2o-rom?

[Guide] How to flash Q GSI on OP6/T

Warning
Not for faint hearts. Proceed at your own risk.
Note: Before You can flash any GSI, You have to unlock Your bootloader. Back up your N**es if you haven't yet.
Objective:
The objective of this guide is to install Q GSI. I will predominantly concentrate on Erfan's GSI (pixel and Google Generic GSI) found on his telegram group. This should work for any other functional GSI just fine though. This guide is tested on OP6 but I really dont find any reason why it wouldn't work on OP6T. Test it at your own risk and report if it works.
Requirements:
OP6 with unlocked bootloader
OOS 9.0.7 (or equivalent for OP6T) flashed to both slots (important!)
Latest ADB and fastboot installed
Knowledge to use ADB and fastboot
GSI image (This guide will be focused on Erfarn's GSI)
Permisiver-V4.zip from here
TWRP (I used blu spark v9.101)
OOS 9.0.7 Boot and vbmeta Warning: DONOT USE THESE FOR OP6T! Extract them from OOS 9.0.7 equivalent for 6T yourself
The Guide:
1. Flash OOS 9.0.7 (or equivalent for 6T) to both slots.
2. Reboot to bootloader and flash the following:
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
All those should be flashed in one go without rebooting. boot and vbmeta are those taken from OOS stock rom.
3. Boot twrp from fastboot (without rebooting from fastboot)
4. Factory reset
5. Flash permisiver-V4.zip (push with adb if not available)
6. Pull "/vendor/build.prop" to PC, find the below line and comment it by prepending a "#" and push it back into same location
Code:
ro.frp.pst=/dev/block/bootdevice/by-name/config
7. Flash magisk if required
8. Reboot​
Credits:
Erfan - GSI used for the guide, permisiver

Known issues:
Fingerprint sensor doesn't work after 1st reboot (No fix at this time)
Dash charge seem not to work (unclear for now)
OBB files have issue. Known issue on DP5.
Can't finish device setup (Follow fix for "No audio on Call" )
No audio on call
1. Install this GMS version
2. Grant all permission to Google Play Services
3. Finish device setup from the notification
No camera available
1. Go to developer settings and turn off "Camera Laser Sensor"
2. Download OOS camera from here and install
Pixel launcher might crash upon reboot
1. Delete /vendor/overlays folder using root or from twrp
in-call audio always routed through Speaker.
Note: The below fix is a temporary, dirty fix. Will update this when a better fix is found
Edit "/system/vendor/etc/audio_policy_configuration.xml" and add this to <attachedDevices> node.
Code:
<item>Earpiece</item>
so your final result looks like:
Code:
<attachedDevices>
<item>Earpiece</item>
<item>Speaker</item>
<item>Built-in Mic</item>
<item>Built-in Back Mic</item>
</attachedDevices>
Note: It is fine if you have extra or less items. You only have to worry about "Earpiece"

vijai2011 said:
Warning
Not for faint hearts. Proceed at your own risk.
Note: Before You can flash any GSI, You have to unlock Your bootloader. Back up your N**es if you haven't yet.
Objective:
The objective of this guide is to install Q GSI. I will predominantly concentrate on Erfan's GSI (pixel and Google Generic GSI) found on his telegram group. This should work for any other functional GSI just fine though. This guide is tested on OP6 but I really dont find any reason why it wouldn't work on OP6T. Test it at your own risk and report if it works.
Requirements:
OP6 with unlocked bootloader
OOS 9.0.7 (or equivalent for OP6T) flashed to both slots (important!)
Latest ADB and fastboot installed
Knowledge to use ADB and fastboot
GSI image (This guide will be focused on Erfarn's GSI)
Permisiver-V4.zip from here
TWRP (I used blu spark v9.101)
OOS 9.0.7 Boot and vbmeta Warning: DONOT USE THESE FOR OP6T! Extract them from OOS 9.0.7 equivalent for 6T yourself
The Guide:
1. Flash OOS 9.0.7 (or equivalent for 6T) to both slots.
2. Reboot to bootloader and flash the following:
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
All those should be flashed in one go without rebooting. boot and vbmeta are those taken from OOS stock rom.
3. Boot twrp from fastboot (without rebooting from fastboot)
4. Factory reset
5. Flash permisiver-V4.zip (push with adb if not available)
6. Pull "/vendor/system.prop" to PC, find the below line and comment it by prepending a "#" and push it back into same location
Code:
ro.frp.pst=/dev/block/bootdevice/by-name/config
7. Flash magisk if required
8. Reboot​
Click to expand...
Click to collapse
Hello thanks for this amazing guide. I am stuck at the 6th step. Could you please clarify on them. Using TWRP File Manager shows no system.prop and adb pull also failed. If you could clarify on this step a little. Thanks in Advance.

Mannan Qamar said:
Hello thanks for this amazing guide. I am stuck at the 6th step. Could you please clarify on them. Using TWRP File Manager shows no system.prop and adb pull also failed. If you could clarify on this step a little. Thanks in Advance.
Click to expand...
Click to collapse
Mount vendor partition

Sorry if it's a dumb question, but I understood till step 5. Could someone please help me better with Step 6? The pull, vendor,....push. Really want to get this Pixel GSI to work.

vijai2011 said:
Mount vendor partition
Click to expand...
Click to collapse
Already did. Still same. We'd all appreciate it if you could clarify on that step with some more instructions as to how to pull and then push said file. Thanks

For step six
Use twrp file manager(advanced option)
Move system prop from /vendor to /sdcard(internal storage is called sdcard)
Edit the prop via pc
Put it back into internal storage
Move it again from /sdcard to /vendor

VaSU# said:
For step six
Use twrp file manager(advanced option)
Move system prop from /vendor to /sdcard(internal storage is called sdcard)
Edit the prop via pc
Put it back into internal storage
Move it again from /sdcard to /vendor
Click to expand...
Click to collapse
Hi, thanks. I already checked and there is no system.prop in /vendor.

Mannan Qamar said:
Hi, thanks. I already checked and there is no system.prop in /vendor.
Click to expand...
Click to collapse
Sorry, corrected it. It should be "/vendor/build.prop" and not "/vendor/system.prop"
Also, if you wish to do it entirely in adb from recovery, the steps are:
Code:
adb shell
cp /vendor/build.prop /sdcard
exit
adb pull /sdcard/build.prop .
Then modify the file and again,
Code:
adb push build.prop /sdcard
adb shell
cp -f /sdcard/build.prop /vendor/build.prop

I would say doesnt boot on 6T.

ashokmor007 said:
I would say doesnt boot on 6T.
Click to expand...
Click to collapse
If you got to the point of bootlooping at the OS boot animation (not bootloader splash screen), it could be incompatibility issue. But if you didn't even make it to that point, I'd say something was not done right

Could someone pm me with some extra help on step 6? Really sorry. Also, would love if it can be done via TWRP itself
---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------
sohailss111 said:
Could someone pm me with some extra help on step 6? Really sorry. Also, would love if it can be done via TWRP itself
Click to expand...
Click to collapse
Has anyone managed to boot it on the OP6?

cant fix de speaker problem ... can u send me that file pls

In the op6/t we have official Q so what's the benefits of this q version?

i found a quick fix for fingerprint ... now this rom is complete

@vijai2011
stuck on splash screen
did all steps 2 times to be sure
using dp6
correction :-
the vendor the incomptible ( need to use vendor from oos dp3 )
flash the oos dp3 and then do the step
works then
but still we lost fastboot boot command because latest BL from dp3 oos is not having that command and you need to use boot img from this post for a recovery since you cant use fastboot boot command
https://forum.xda-developers.com/oneplus-6/development/rom-pixel-3-xl-port-oneplus-6-t3856031
use vbmeta and boot image from this post
correction 2 :-
you can use normal steps also
1. flash oos zip 2 times to get on both slot
2. flash the gsi
3. flash dm verity disabler https://zackptg5.com/android.php#disverfe
4. flash magisk

【Reproduced】XZ2/XZ2P/XZ2C/XZ3 TWRP for Android 10

Reprinted to China xpeira Forum: GFan Author: machao44.Just reproduced, irresponsible
Original Link：
http://bbs.gfan.com/android-9634387-1-1.html
http://bbs.gfan.com/android-9634397-1-1.html
http://bbs.gfan.com/android-9634405-1-1.html
Bugs:Unable to read external SD card
Flash steps:
1.Flash firmware, do not start the device
2.Open the adb folder
xz2:
fastboot flash boot twrp-xz2.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
xz2p:
fastboot flash boot twrp-xz2p.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
xz2c:
fastboot flash boot twrp-xz2c.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
xz3:
fastboot flash boot twrp-xz3.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
3.Press and hold the volume down and power buttons to enter twrp, connect to the phone and enable MTP mode.
4.Drag boot_X-FLASH-ALL-B6B5.sin in the firmware to UnSIN.exe to decrypt it, and then rename it to kernel.img.
5.Put kernel.img in the startup folder, and then compress it to boot.zip (please note that the correct method is to select the META-INF folder and kernel.img for compression)
6.Copy boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip to the phone storage, and then refresh. (Xz3 only needs to copy boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip)
7.Carry out

Download Link:https://drive.google.com/drive/folders/1e2sWOLhhiYmDyd-aN7sx1iLplPtIAVNf

It does not work for me, the first time I get to the home screen, after 5 minutes it restarted and it does not happen from the Xperia animation, I used XZ2 Android 10. Your input is greatly appreciated

anjelz2012 said:
It does not work for me, the first time I get to the home screen, after 5 minutes it restarted and it does not happen from the Xperia animation, I used XZ2 Android 10. Your input is greatly appreciated
Click to expand...
Click to collapse
Maybe you should try again. Step 6 is that I did n’t write clearly. The correct flashing steps are: Flashing in order
1. Flashing boot.zip 2. Flashing twrp-installer-xz3-3.3.x.zip 3. Flashing Magisk-v20.3.zip 4. Flashing fstab.zip
---------- Post added at 12:03 ---------- Previous post was at 11:56 ----------
L1e" said:
Reprinted to China xpeira Forum: GFan Author: machao44.Just reproduced, irresponsible
Original Link：
http://bbs.gfan.com/android-9634387-1-1.html
http://bbs.gfan.com/android-9634397-1-1.html
http://bbs.gfan.com/android-9634405-1-1.html
Bugs:Unable to read external SD card
Flash steps:
1.Flash firmware, do not start the device
2.Open the adb folder
xz2:
xz2p:
xz2c:
xz3:
3.Press and hold the volume down and power buttons to enter twrp, connect to the phone and enable MTP mode.
4.Drag boot_X-FLASH-ALL-B6B5.sin in the firmware to UnSIN.exe to decrypt it, and then rename it to kernel.img.
5.Put kernel.img in the startup folder, and then compress it to boot.zip (please note that the correct method is to select the META-INF folder and kernel.img for compression)
6.Copy boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip to the phone storage, and then refresh. (Xz3 only needs to copy boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip)
7.Carry out
Click to expand...
Click to collapse
The correct way to step 6 is to refresh boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip in turn

I followed him in that order and he always got the same result

anjelz2012 said:
I followed him in that order and he always got the same result
Click to expand...
Click to collapse
Have you tried flash the firmware？Because after flashing the firmware according to the original text, do not start the phone

L1e" said:
Have you tried flash the firmware？Because after flashing the firmware according to the original text, do not start the phone
Click to expand...
Click to collapse
The process I have followed is as follows:
1.- Flash firmware 52.1.A.0.532 (android 10) and I don't start it
2.- I connect in fastboot mode to the pc and execute:
fastboot flash boot twrp-xz2.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.- I enter Twrp mode
4.- Prepare the boot.zip file (META-INF + kernel.img using 7zip)
5.- Copy: boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip in the phone storage
6.- Flashing in the following order:
*boot.zip
twrp-installer-xz3-3.3.x.zip
Magisk-V20
fstab.zip
7.- I restart my mobile and it doesn't work for me.
When it shows the lock screen after rebooting, it turns off and does not pass the Xperia animation
:cyclops::cyclops:

anjelz2012 said:
The process I have followed is as follows:
1.- Flash firmware 52.1.A.0.532 (android 10) and I don't start it
2.- I connect in fastboot mode to the pc and execute:
fastboot flash boot twrp-xz2.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.- I enter Twrp mode
4.- Prepare the boot.zip file (META-INF + kernel.img using 7zip)
5.- Copy: boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip in the phone storage
6.- Flashing in the following order:
*boot.zip
twrp-installer-xz3-3.3.x.zip
Magisk-V20
fstab.zip
7.- I restart my mobile and it doesn't work for me.
When it shows the lock screen after rebooting, it turns off and does not pass the Xperia animation
:cyclops::cyclops:
Click to expand...
Click to collapse
Sorry, it took a long time to reply to you. Through trial and error, I found no problems. I don't know what went wrong.

anjelz2012 said:
The process I have followed is as follows:
1.- Flash firmware 52.1.A.0.532 (android 10) and I don't start it
2.- I connect in fastboot mode to the pc and execute:
fastboot flash boot twrp-xz2.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.- I enter Twrp mode
4.- Prepare the boot.zip file (META-INF + kernel.img using 7zip)
5.- Copy: boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip in the phone storage
6.- Flashing in the following order:
*boot.zip
twrp-installer-xz3-3.3.x.zip
Magisk-V20
fstab.zip
7.- I restart my mobile and it doesn't work for me.
When it shows the lock screen after rebooting, it turns off and does not pass the Xperia animation
:cyclops::cyclops:
Click to expand...
Click to collapse
I think maybe your step 4 was wrong,
put Kernel.img into boot folder,then compression the folder,you will get boot.zip ,flash it.

Did anyone try this? Got success?
Tia

serajr said:
Did anyone try this? Got success?
Tia
Click to expand...
Click to collapse
I tried again and yes, this time it worked! Although it is somewhat unstable, because it causes forced reboots and forced encryption does not work!

anjelz2012 said:
I tried again and yes, this time it worked! Although it is somewhat unstable, because it causes forced reboots and forced encryption does not work!
Click to expand...
Click to collapse
Thanks bro! I didn't even get the 3rd step to work (entering twrp with combo keys after flashing it).
I'll try it once again tomorrow, after a fresh firmware installation! Maybe that's why things didn't work here.

I've just installed it with latest firmware, it works great
An advice, keep TWRP in chinese or it doesn't flash anything and get stucked

I was stuck on booting the first TWRP in the adb folder, with the screen screaming with a notification of a corrupt device & it will reboot.
I am thus assuming this TWRP pack is for the stock rom, not a custom one.

Works almost perfectly, thanks for sharing
---------- Post added at 12:05 AM ---------- Previous post was at 12:04 AM ----------
adwinp said:
I was stuck on booting the first TWRP in the adb folder, with the screen screaming with a notification of a corrupt device & it will reboot.
I am thus assuming this TWRP pack is for the stock rom, not a custom one.
Click to expand...
Click to collapse
Step One: Flash Firmware....

Beetle84 said:
Works almost perfectly, thanks for sharing
Step One: Flash Firmware....
Click to expand...
Click to collapse
I read that - it should probably be specified that only stock firmware is supported (in contrast to custom).

adwinp said:
I read that - it should probably be specified that only stock firmware is supported (in contrast to custom).
Click to expand...
Click to collapse
Generally, when someone says firmware, they mean stock. Custom roms are usually not called firmware

adwinp said:
I was stuck on booting the first TWRP in the adb folder, with the screen screaming with a notification of a corrupt device & it will reboot.
I am thus assuming this TWRP pack is for the stock rom, not a custom one.
Click to expand...
Click to collapse
I made progress
My twrp build for custom 10.0 works now.
Decryption is left in my to-do list, before I move to adapt changes for a stock twrp.

MartinX3 said:
[...] before I move to adapt changes for a stock twrp.
Click to expand...
Click to collapse
Just another amazing news from you... THANK YOU SO MUCH! Looking forward to it!!
The one provided from OP does work, I gotta say, but it makes use of unencrypted /data partition hack (fstab.zip), which is not - imho - a good choice.

serajr said:
Just another amazing news from you... THANK YOU SO MUCH! Looking forward to it!!
The one provided from OP does work, I gotta say, but it makes use of unencrypted /data partition hack (fstab.zip), which is not - imho - a good choice.
Click to expand...
Click to collapse
Thank you
Yeah, this TWRP is the same chinese TWRP like for stock 9.0 in the past

Redmi 9A MeYou Rom Rooted

Need unlocked bootloader
Download Rom https://gofile.io/d/44WiXf
Don't use recovery and boot img which is inside the Rom file. Here you have the updates with the corrections
Update recovery.img : https://gofile.io/d/UWjWjR
Update boot.img : https://gofile.io/d/z1ExYV
Vbmeta : https://gofile.io/d/4aIWrv
Root only mode :
If you just want root
flash only vbmeta and boot.img with fastboot
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
Full debloated and uncrypted rom with recovery mode :
Unzip vendor system product image file on your phone
Recovery.img boot.img vbmeta.img near your fastboot programm
Flash recovery.img boot.img and vbmeta with fastboot :
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta.img
fastboot flash vbmeta_vendor vbmeta.img
Boot on recoverymod
Install like an image
Give attention system for system vendor for vendor....
Format your data if you never installed modem rom,or just wipe if you allready got uncrypted mod
reboot
Don't try intsall magisksu new version it doesnt work, you can only install new manager
Don't forget in developer menu disable usb debuging if you don't need it
if things are missing, I will add as I go
The version for those the touchscreen does not work will come later.
If you want donate you can for my daughter

I'm sorry but there's no edit button, then i add what i forget here.
Last one thing mount cust partition under mount menu then you can enter this command under terminal recovery :
cd /cust
rm -r *

Also if you allready formated before with new vendor, you don't need format it again, just wipe crappy new forum

Don't forget you only need install MagiskManager then he ask you reboot once time
Archive.zip (MagiskManager, Youtube Vance, and...)
Gofile - Free Unlimited File Sharing and Storage
Gofile is a free, secure file sharing and storage platform. With unlimited bandwidth and storage, you can easily store and share files of any type without any limits. Our advanced features, such as CDN support and password protection, make Gofile the ideal choice for individuals and businesses...
gofile.io

Mistake rocevry.img sorry
This is the one good : https://gofile.io/d/UWjWjR

Need to flash vbmeta as well?

ahsan.ey.ca said:
Need to flash vbmeta as well?
Click to expand...
Click to collapse
You need reflash vbmeta and same vbmeta for vbmeta_system if you reinstalled full Miui rom

Recovery flashed, working fine. It stays too. Waiting for rom to download, doing it first time like this so please accommodate silly questions if any

I do my best, recovery it is very good now also you can flash super.img
If you allready formated Data whit last vendor.img for uncpryted mode, you don't need to format it again, just wipe it is oj

gsi flashing works?

I'll need help with these. My queries in brackets ( )
-Give attention system for system vendor for vendor.... (Please explain a bit)
-Format your data, do not wipe format (A bit more explanation)
-Last one thing mount cust partition under mount menu then you can enter this command under terminal recovery :
cd /cust
rm -r *
(Do I have to do this inside recovey menu?)
-Also if you allready formated before with new vendor, you don't need format it again, just wipe crappy new forum (Not formatted before)
Don't forget you only need install MagiskManager then he ask you reboot once time
Archive.zip (MagiskManager, Youtube Vance, and...) (Do i have to install magisk via zip in recovery? If so, which file? As u said latest wont work)

For me recovery no touch.Send me anethyng to test.

This is not gsi mode, it's Miui boot.img recovery.img and full rom hacked.
4 file in your phone
System.img Vendor.img Product.img and Boot.img
Recovery Menu :
Install > Install Image >> vendor.img >> Vendor Image Swipe
Same for all 4 image
Then format your data if you are on crypted Miui rom or just wipe if you got allready uncrypted data mode
Finaly Mount Menu
Check Cust to mount
Then back to Advanced menu choose Terminal :
cd /cust
rm -r *
Reboot and wait
Archive.zip it is for you make easyer to got what you need : just unzip it on your phone after reboot finish and install what you need

No don't install Magisk.zip as i say can't work, you don't need magisk.zip anymore, just install Magisk Manager under Anrdoid in the Archive.zip

vendor.img >> Vendor Image >> Swipe
system.img >> System Image >> Swipe
product.img >> Product Image >> Swipe
boot.img >> Boot >> Swipe

Then format your data if you are on crypted Miui rom or just wipe if you got allready uncrypted data mode
I'm not sur about this, I flashed Treble Rom when u shared and after that I did not change anything. So do I format now or just wipe?

Last time i share vendor uncrypted mode if you got this vendor mod then you allready formated it to got uncrypted data if not then format your data.

Format your data, do not wipe format
I've flashed vendor, system, product and boot. Now I'm on main menu. Where do I format from? Wipe I guess?

By clicking wipe, I have 2 options:
1. Advanced Wipe
2. Format Data
And then on bottom is "Swipe to factory reset"
What do i do?

"yes" >> swipe

[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi 10X 4G / Xiaomi Redmi Note 9)

PATCHED VBMETA.IMG for MERLIN by VD171
For what do I need it ?
If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once only. Once flashed, you don't need to flash vbmeta again.
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM
- V12.0.1.0.RJOMIXM
- V12.0.8.0.QJOMIXM
- V12.0.7.0.QJOMIXM
- V12.0.6.0.QJOMIXM
- V12.0.5.0.QJOMIXM
- V12.0.4.0.QJOMIXM
- V12.0.3.0.QJOMIXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
How to flash it?
Code:
fastboot flash vbmeta vbmeta_vd171.img
MD5 hashes:
AL2522-Merlin-V039-Q-0513: ca9ccb577b5a1efd348949f9ed99409f
AL2522-Merlin-V044-Q-0920: dccbc87dbedc7f758120feac72e6c6cf
V12.5.1.0.RJOMIXM: 9d052f5fd4a7df3b5ad39c07b9330d75
V12.0.1.0.RJOMIXM: 9d052f5fd4a7df3b5ad39c07b9330d75
V12.0.8.0.QJOMIXM: 4a59b0481aa2a3bd5381fd51d2da3184
V12.0.7.0.QJOMIXM: 64fa528e39ebcd4838b92d5b120b0035
V12.0.6.0.QJOMIXM: 974e9c3462b4346a70ff370f6c28527b
V12.0.5.0.QJOMIXM: 7c68fe2373188e20abd4f1c68cb949b1
V12.0.4.0.QJOMIXM: 39ef5250fd562e20b6530cf8a0a96943
V12.0.3.0.QJOMIXM: 13c896c8dc4924bed5b63673a0a38a1a
V11.0.5.0.QJOMIXM: 2323b64102370a98f1641bc4d8227c52
V11.0.4.0.QJOMIXM: 666c0fbbd4d329001290277fcfd052d8
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

Hi Broather , help me patched boot + vbmeta for this rom . I want to root it but after flash patched boot and disable vbmeta my devices hang on logo
https://bigota.d.miui.com/V12.5.3.0...JCNXM_20210429.0000.00_11.0_cn_1084bb7a7f.tgz
- Boot : https://drive.google.com/file/d/12Ne1FYZL_Mn9K2KP-VwHqO3Z3ACLti62/view?usp=sharing
- Vbmeta : https://drive.google.com/file/d/1LX7fbupDePK4aRY2CYZyRNmS4uf_BOZe/view?usp=sharing
thank so much
@VD171

empty.cad said:
Hi Broather , help me patched boot + vbmeta for this rom . I want to root it but after flash patched boot and disable vbmeta my devices hang on logo
https://bigota.d.miui.com/V12.5.3.0...JCNXM_20210429.0000.00_11.0_cn_1084bb7a7f.tgz
- Boot : https://drive.google.com/file/d/12Ne1FYZL_Mn9K2KP-VwHqO3Z3ACLti62/view?usp=sharing
- Vbmeta : https://drive.google.com/file/d/1LX7fbupDePK4aRY2CYZyRNmS4uf_BOZe/view?usp=sharing
thank so much
@VD171
Click to expand...
Click to collapse
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. (Attention: TAR and NOT tgz. You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file and wait until it finish.
6. Open the folder "Downloads" and uncompress the file magisk_patched.tar to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img. (You need to flash patched vbmeta because vbmeta verifies if any partition was changed.)
Done, you got patched boot.img and patched vbmeta.img files.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.

VD171 said:
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. ( You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file.
6. Open the folder "Downloads" and extract the magisk_patched.TAR to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img.
Done.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
Click to expand...
Click to collapse
Thank broather

VD171 said:
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. ( You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file.
6. Open the folder "Downloads" and extract the magisk_patched.TAR to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img.
Done.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
Click to expand...
Click to collapse
Thank broather , but my devices still hang on logo after flash patched boot and patched vbmeta . Too dificult to root it

empty.cad said:
Thank broather , but my devices still hang on logo after flash patched boot and patched vbmeta . Too dificult to root it
Click to expand...
Click to collapse
Did you unlock the bootloader?
The patched boot and patched vbmeta are enough to root it, but it requires unlocked bootloader.

Hey bro, can you help me root this device. My device is unlocked but none of the fastboot commands work , it just freezes and doesnt move ahead at all.

bismeet said:
Hey bro, can you help me root this device. My device is unlocked but none of the fastboot commands work , it just freezes and doesnt move ahead at all.
Click to expand...
Click to collapse
Try to flash the whole MIUI again and try to root again following properly the steps.

VD171 said:
Try to flash the whole MIUI again and try to root again following properly the steps.
Click to expand...
Click to collapse
Well, i havent changed anything really except the bootloader unlock so I dont understand why that should be the case.

bismeet said:
Well, i havent changed anything really except the bootloader unlock so I dont understand why that should be the case.
Click to expand...
Click to collapse
Did you mean the device froze at fastboot or boot?
Did you try USB 2.0 or USB 3.0 ?
Did you try other usb ports and other usb cables?

VD171 said:
Did you mean the device froze at fastboot or boot?
Did you try USB 2.0 or USB 3.0 ?
Did you try other usb ports and other usb cables?
Click to expand...
Click to collapse
The device isnt frozen. The commands freeze and dont do anything. fastboot devices works but other commands do not do anything. Yes, I tried both 2.0 and 3.0.

bismeet said:
The device isnt frozen. The commands freeze and dont do anything. fastboot devices works but other commands do not do anything. Yes, I tried both 2.0 and 3.0.
Click to expand...
Click to collapse
I know. You need keep trying other usb ports and usb cables.

VD171 said:
I know. You need keep trying other usb ports and usb cables.
Click to expand...
Click to collapse
Tried all. Guess I need to add new ports to my phones and laptops.

bismeet said:
Tried all. Guess I need to add new ports to my phones and laptops.
Click to expand...
Click to collapse
If you can, try in another computer too.
I had same problem with USB 2.0 and everything is fine now with USB 3.0.

VD171 said:
If you can, try in another computer too.
I had same problem with USB 2.0 and everything is fine now with USB 3.0.
Click to expand...
Click to collapse
Okay.
I guess this phone is not rootable.
Never buying mtk device again.

bismeet said:
Okay.
I guess this phone is not rootable.
Never buying mtk device again.
Click to expand...
Click to collapse
What is your device?

VD171 said:
What is your device?
Click to expand...
Click to collapse
Redmi note 9 mtk version from India/

bismeet said:
Redmi note 9 mtk version from India/
Click to expand...
Click to collapse
Everyone has already rooted it.

VD171 said:
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. ( You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file.
6. Open the folder "Downloads" and extract the magisk_patched.TAR to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img.
Done.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
Click to expand...
Click to collapse
Thank you so much for this guide bro!
I tried the same on my OPPO, but with Bootloader locked and flashed through SP Flash Tool. My phone detects a patched vbmeta (coz I tested flashing the patched vbmeta alone.)

llxxVENOMxxll said:
Thank you so much for this guide bro!
I tried the same on my OPPO, but with Bootloader locked and flashed through SP Flash Tool. My phone detects a patched vbmeta (coz I tested flashing the patched vbmeta alone.)
Click to expand...
Click to collapse
Yes, you can't flash patched vbmeta while bootloader is locked.
You need to unlock bootloader first if you want to apply any change to any partition.