Database Info

[Solved] Elephone P8 Max Root

Hello, this is my first post
Don't let me waste time...
Requirements
1.Stock boot.img for your phone model (its best its for your Build Number / Variant ) . You can extract from the stock rom / firmware of your device OR backup from your device using a box e.g Miracle box, CM2, etc
2.Download Latest Magisk Manager
Steps on how to root an Elephone P8 Max using Magisk Manager and patched boot.img
Step 1: Patching the stock boot.img
1.Install MagiskManager apk on your android device
2.Copy the stock boot.img of your device to your phone's internal storage or SD card
3.Launch Magisk Manager app
4.If prompted to install Magisk, select NO THANKS
5.If you are using a samsung device and wish to flash using Odin, then select Options > Settings > Update Settings > Patched Boot Output Format > img.tar )
6.Select Install > Install > Patch Boot Image File >
7.Navigate to the location of the stock boot.img you copied earlier on, then Select it
8.Magisk Manager should begin downloading the magisk zip file used for patching
9.Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img[.tar]
Step 2: Flashing the patched boot.img
You have a variety of options to flash the patched boot.img depending on you
1.Sp Flashtool
2.Fastboot
3.Miracle Box
1. For Sp Flashtool copy the patched boot.img with mt6755 scatter file and make sure to rename patched boot.img to boot.img before flashing
2.For fastboot copy the patched boot.img to your fastboot folder and press shift right click on a free space in the fastboot folder, you would see open command here. Click on it and boot your Elephone P8 Max to fastboot with power+volume up and use volume down to select fastboot and connect your Elephone P8 Max. Your PC type fastboot devices to check if the system as seen it. Now type fastboot flash boot patched_boot.img
You are done.
3.For miracle box rename the file from .img to .bin before flash.
In case you lazy..:laugh:
I have the patched_boot.img here
https://drive.google.com/file/d/17jjlC_znGMEA6HY0H0l4XP6LaBIv7n_t/view?usp=drivesdk
Enjoy..use root checker to confirm
Anyone who can support for custom recovery

TWRP for Elephone p8 Max
I need the newest TWRP for Elephone p8 Max. Can anybody help?
Thanks

Iamkratos said:
Hello, this is my first post
You have a variety of options to flash the patched boot.img depending on you
2.Fastboot
Click to expand...
Click to collapse
Hi I tried fastboot.
fastboot oem unlock OK
fastboot flash recovery patched_boot.img
works, but after switch off an boot into recovery, just normal android 7 starts, no twrp.
When boot finished, touching on display does not work anymore.
Any hinds?
Elephone P8_Max
Android 7.0
Build-Number:
Elephone_P8_Max_20171221
Thanks for any help.

aaaalbi2 said:
Hi I tried fastboot.
fastboot oem unlock OK
fastboot flash recovery patched_boot.img
works, but after switch off an boot into recovery, just normal android 7 starts, no twrp.
When boot finished, touching on display does not work anymore.
Any hinds?
Elephone P8_Max
Android 7.0
Build-Number:
Elephone_P8_Max_20171221
Thanks for any help.
Click to expand...
Click to collapse
Because you flash boot.img as recovery
That why your phone is getting that fault
You are suppose to flash boot
Fastboot flash boot patched_boot.img OK
Or use sp flashtool or miracle box
I included the scatter file

I have the twrp but it doesn't touch only if you use otg with Mouse

Alternative scatter file for MT6750
Hi lmkratos,
thank you very much!
This worked like a charm but I had to use a different scatter file (attached here) as the P8 Max has a MT6750 (not MT6755) and the PMT didn't match so spflash refused to flash boot ("PMT changed for the ROM").
If you happen to be on Linux: spflash works perfectly but take care to stop ModemManager (WAN modems) before flashing as it interferes, so
"service ModemManager stop".

rec Please send it, thank you
Iamkratos said:
I have the twrp but it doesn't touch only if you use otg with Mouse
Click to expand...
Click to collapse
rec Please send it, thank you
---------- Post added at 04:18 AM ---------- Previous post was at 04:16 AM ----------
Iamkratos said:
I have the twrp but it doesn't touch only if you use otg with Mouse
Click to expand...
Click to collapse
twrp Please upload, thank you

[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/folde...sx1iLplPtIAVNf

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
Download Link:https://drive.google.com/drive/folde...sx1iLplPtIAVNf
Click to expand...
Click to collapse
The link is down. Do you mind re-uploading? Thanks.

[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.

Question can't install magisk

after the latest apdate 13.0.3 i lose my magisk
and when i want to install it using adb it gives me a boot loop and i shoold to flash the original boot.img
Nb : ramdisk yes

Uninstall it thn flash it using Twrp

twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%

souhail39 said:
twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%
Click to expand...
Click to collapse
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963

pl1992aw said:
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963
Click to expand...
Click to collapse
This is what i did
The original boot run finely but the patched one give me a boot loop

Miui 13 doesn't support yet unless you patch the boot img. Just revert to 12.5.9

souhail39 said:
This is what i did
The original boot run finely but the patched one give me a boot loop
Click to expand...
Click to collapse
The safe way is to not flash boot image with TWRP or Orangefox custom recoveries. Flash with fastboot mode with PC is better to prevent issue.
What version of Magisk?
If you are using the latest Magisk v24.X but it bootloop, you may report issue to Magisk author in his github.
If you used Magisk v23, it is said not working on Android 12, so will not work on MIUI 13.

1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img

VD171 said:
1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img
Click to expand...
Click to collapse
thx for your answer but always the same problem with patched img files