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.
Related
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
How to extract firmware from ozip the files are may be encrypted because they are giving me some error also i have tried to patch boot.img with Magisk Manager & it giving Unknown Image Format
siddhrsh said:
How to extract firmware from ozip the files are may be encrypted because they are giving me some error also i have tried to patch boot.img with Magisk Manager & it giving Unknown Image Format
Click to expand...
Click to collapse
- Use winrar to extract
- Patch boot.img can't root. Patch recovery.img
thatha said:
- Use winrar to extract
- Patch boot.img can't root. Patch recovery.img
Click to expand...
Click to collapse
LOL !
Hi I already try winrar but still the result says corrupt. Can you show me how step by step ?
Do someonne have a copy of rmx1809 boot.img ...need it for unbricking my phone
AfieyCyrus90 said:
Do someonne have a copy of rmx1809 boot.img ...need it for unbricking my phone
Click to expand...
Click to collapse
No I don't have one but I will suggest downloading ota update from realme site and extract it and I think you were to root your phone by trying to flash magisk_patched.img
I whicjh case I would suggest visting this site
Magisk installation site , cant provide link as being a new user
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
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
i've been looking for one everywhere but i cant really find one..
but if someone tells me how to like make a twrp for it (the latin variant), it'd be nice
thank you!
so, are there any news about this?
kalii_ said:
so, are there any news about this?
Click to expand...
Click to collapse
Nobody supports or develops for that variant of the A12. The only time was a custom recovery, that was abandoned and doesn't work anymore.
kalii_ said:
so, are there any news about this?
Click to expand...
Click to collapse
Nevermind... Ask @physwizz for your version.
TheWorldYT said:
Nevermind... Ask @physwizz for your version.
Click to expand...
Click to collapse
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
If it doesn't work I can easily modify it
physwizz said:
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
If it doesn't work I can easily modify it
Click to expand...
Click to collapse
well, it doesnt work for me sadly, since the A125F model is a little different from the 125m, itll just start rebooting. if you can make a modifed version for it, ill glady test it for you. the firmware that i got is the ZTO A125MUBU3BVG6
Thank you
kalii_ said:
well, it doesnt work for me sadly, since the A125F model is a little different from the 125m, itll just start rebooting. if you can make a modifed version for it, ill glady test it for you. the firmware that i got is the ZTO A125MUBU3BVG6
Thank you
Click to expand...
Click to collapse
Send me your stock recovery.img.lz4
And I'll see what I can do
physwizz said:
Send me your stock recovery.img.lz4
And I'll see what I can do
Click to expand...
Click to collapse
here it is:
recovery.img.lz4
Download recovery.img.lz4 for free from KrakenFiles.com
krakenfiles.com
kalii_ said:
here it is:
recovery.img.lz4
Download recovery.img.lz4 for free from KrakenFiles.com
krakenfiles.com
Click to expand...
Click to collapse
Ok
kalii_ said:
here it is:
recovery.img.lz4
Download recovery.img.lz4 for free from KrakenFiles.com
krakenfiles.com
Click to expand...
Click to collapse
thank you for the response, but unfortunally it soft bricks and won't boot past the boot screen. is there a way i can help to make it work?
hey, i've found the issue, i gave you the wrong file, sorry about that. if you got paypal maybe i can send you 5 dollars just to compensate you for my mistake...
thank you
@physwizz
kalii_ said:
hey, i've found the issue, i gave you the wrong file, sorry about that. if you got paypal maybe i can send you 5 dollars just to compensate you for my mistake...
thank you
@physwizz
Click to expand...
Click to collapse
Lol.
I don't take money
physwizz said:
Lol.
I don't take money
Click to expand...
Click to collapse
well, alright. just wanted to support you
kalii_ said:
well, alright. just wanted to support you
Click to expand...
Click to collapse
I do this for fun and to keep my old brain active
Unzip to get the tar file.
Installing instructions in next post
Installing Custom Recoveries
A. Preparation.
1. Download firmware for your device
2. Extract ap file using Zarchiver and extract recovery.img from recovery.img.lz4 and compress it to recovery.tar
3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img (from magisk, choose install then select file to patch)
Exynos 850 Resources
t.me
Alternatively you can extract boot.img.lz4 and vbmeta.img.lz4 from the ap file and compress them into a new tar file and then patch that file.
note: if you don't want root then just extract the vbmeta.img and use zarchiver to add it to my twrp.tar file.
You can flash this new file from odin at step 5
For Exynos 850 android 11 use a21s patched magisk.
For Exynos 850 android 12 and most other devices use delta magisk
4. Unlock OEM in developer options
5. Attach phone to pc and reboot to download mode
6. flash patched ap file.
Or..
Extract boot.img and vbmeta.img and add them to the TWRP zip.
7. Download recovery.img or download twrp.tar and extract recovery.img using Zarchiver.
B.Installation
Method 1.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp.tar into the ap slot
5. reboot to recovery
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Method 2.
If you have already installed recovery and decrypted.
Extract recovery.img
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to system then reboot to recovery
Backup boot, data, super and dtbo
(For Pitch-black just install the zip)
Method 3.
1. Install TWRP app
Extract recovery.img
2. Install TWRP
3. Choose file to flash.(don't select device)
4. Select recovery.img.
5. Reboot to recovery.
6. (You may need to change data partition to ext4 first if format ruins your system)
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
Method 4
Using a second phone
Physwizz Collection
To flash TWRP from phone1 to phone2 Only if you have already installed recovery and decrypted. 1. Install this termux on phone1 2. Setup storage termux-setup-storage 3. Install this Heimdall Magisk module on phone1 Or install chroot Linux on termux and then install heimdall 4. Copy...
t.me
C. Recovery Problems
Most recovery issues can be solved by attending to the following issues.
1. Did you root using the full ap file patched Magisk .
(This contains the patched boot.img and vbmeta.img)
Exynos 850 users must use the special a217 magisk?
2. Did you then go all the way through the setup process?
3. Did you download the recovery to match your baseband?
See https://t.me/a127f_res/54 for Exynos 850 recoveries
4. Did you hold down power and volume up after Odin says pass?
5. Did you format data from stock recovery?
If you forgot to do this, just install stock recovery.img from TWRP and reboot.
6. Did you type multidisabler twice?
7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?
8. To avoid touch issues go to settings and untick "allow time out"
D.To restore Stock Recovery
1. Attach phone to pc and reboot to download mode
2. flash patched ap file or stock recovery.tar
3. reboot
Or just flash stock recovery.img from twrp and reboot.
@physwizz