I have just bought oneplus 7 t pro and want to root it. How do I extract boot.img from the firmware so I can patch it using magisk ? Any help in rooting this device would be greatly appreciated. Thanks
you should wait the stock rom or you can try to boot the oneplus 7t twrp and backup the boot.img
Thanks
Will try and report back
boots into the twrp 7t recovery but boot.img is not being backed up . It fails to mount any partition . adb pull command not working .
I have boot image
are you able to patch it with magisk ?
ask77 said:
are you able to patch it with magisk ?
Click to expand...
Click to collapse
unfortunately not
I have now extracted boot.img and patched it with magisk but the output image is of 36.44 MB while the original image is of 96 MB so I am a bit wary in flashing this image as I do not want to go into a boot loop also I have a boot.img and a recovery.img both are identical in size and are identified by magisk as stock boot.img . i am uploading the install log . I will research a bit more before flashing the patched boot img to achieve root
ask77 said:
I have now extracted boot.img and patched it with magisk but the output image is of 36.44 MB while the original image is of 96 MB so I am a bit wary in flashing this image as I do not want to go into a boot loop also I have a boot.img and a recovery.img both are identical in size and are identified by magisk as stock boot.img . i am uploading the install log . I will research a bit more before flashing the patched boot img to achieve root
Click to expand...
Click to collapse
try just doing fastboot boot patchedbootimghere.img
if it bootloops you can just restart the phone and it will be back to normal since its not flashed
HolyChickenGuy said:
try just doing fastboot boot patchedbootimghere.img
if it bootloops you can just restart the phone and it will be back to normal since its not flashed
Click to expand...
Click to collapse
Thanks will do that.
sorry no go . It either goes to crashdump or is stuck with the fastboot screen
ask77 said:
sorry no go . It either goes to crashdump or is stuck with the fastboot screen
Click to expand...
Click to collapse
I'm having the same results
Sent from my OnePlus 7T Pro
same there no luck. just the crash dump screen
digitalashley said:
same there no luck. just the crash dump screen
Click to expand...
Click to collapse
Make sure to check Preserve AVB 2.0/dm-verify in advance settings before patching boot.img, then use command
fastboot boot imagenamehere.img, after boot, perform direct install to preserve root.
Related
Hello guys, I have few questions and hopefully someone can answer them.
I am trying to root my mate 10 pro with version:
BLA-L29 8.0.0.127(C432)
I want to root it with magisk and since twrp is not available yet,
is it possible to root by patching the boot image?
If it is possible, how do I extract the boot image without root?
This is what i found online.
Method 2: Patching Stock Boot Image
This method doesn’t require you to have TWRP in order to install Magisk 15.0 update.
1. Download the latest Magisk Manager APK: MagiskManager-v5.5.1.apk
2. Use a file manager to install the downloaded app on your device.
3. Grab the stock boot image (kernel) and it should be corresponding to the firmware installed on your device.
For Nexus and Pixel devices, you can extract it from the factory image. For other OEM devices, you might need to check it with your manufacturer’s support.
4. Copy the downloaded “boot.img” to the internal storage of your Android device.
5.Open the Magisk Manager app and tap on the ‘Install’ button.
6. Again, choose ‘Install’ and then ‘Patch Boot Image File’.
7. Navigate to the storage and select the ‘boot.img’ file you just transferred.
8. The Magisk Manager app will patch the stock boot image and place the resultant ‘patched_boot.img’ in the ‘MagiskManager’ folder.
9. Transfer the file from your phone to C:\adb folder on your PC.
10. Hold the SHIFT key on your PC and right-click on an empty space inside the folder. Then select ‘Open PowerShell window here’ from the menu.
11. Boot your Android into Fastboot mode and connect it to the PC.
Enter the following command to root your Android phone using Magisk 15.0 update:
fastboot flash boot patched_boot.img
Finally, reboot your device.
fastboot reboot
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Dagda-Esus said:
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
Did you get the boot.img file ? or did you do it in another way ?
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
trackloading said:
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
Click to expand...
Click to collapse
ramdisk.img is correct. boot.img is ramdisk and kernel combined, but as of Oreo it's now ramdisk.img and kernel.img.
So patching ramdisk.img is the way to go?
yfaykya said:
So patching ramdisk.img is the way to go?
Click to expand...
Click to collapse
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
dawnc said:
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
Click to expand...
Click to collapse
Do you know your model number?
Like
xxx-CxxxBxxx
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
Did you get magisk working ?
lisa99 said:
Did you get magisk working ?
Click to expand...
Click to collapse
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the "Your device is unlocked" screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
ante0 said:
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the Your devices is unlocked screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
Click to expand...
Click to collapse
let me know if you figure something out.
ante0 said:
do you know your model number?
Like
xxx-cxxxbxxx
Click to expand...
Click to collapse
bkl-al20c00
dawnc said:
bkl-al20c00
Click to expand...
Click to collapse
You seem to have fixed it already?
ante0 said:
You seem to have fixed it already?
Click to expand...
Click to collapse
I've made a boot.img with supersu inside.
But can't fix magisk root
dawnc said:
I've made a boot.img with supersu inside.
But can't fix magisk root
Click to expand...
Click to collapse
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
ante0 said:
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
Click to expand...
Click to collapse
Have u found a way to make magisk work?
dawnc said:
Have u found a way to make magisk work?
Click to expand...
Click to collapse
It might be because loop is not fully working.
But no, haven't found any way.
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
dawnc said:
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
Click to expand...
Click to collapse
Not both at once no.
Nougat STock boot.img
download from here
https://kuttysoft.cloud/drive/s/YFCHW3RGXTUJrvPbfR1hamMLQ5QZrk
step to flash
Boot in to Recovery TWRP
flash boot.img
reboot
/// sometimes magisk patched boot.img
when Update new magisk its Give boot loop
then u need this stock boot.img
so for recovery ur data flash this and boot in to system
Titanium backup is Suggested .........
Enjoy
Thank YOU
Bharath Raju said:
Here you go.
https://firmwarefile.com/lenovo-vibe-k6-power-k33a42
No need of separate thread just for this.
@daveyannihilation
@Fobos531
Mods can any of you close this thread.
Click to expand...
Click to collapse
man without losing data recover from bootloop from boot.img patching problem this is best solutions this one
no need download 2GB of Rom files just download 25MB this file enough
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
cubano2031 said:
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
Click to expand...
Click to collapse
Sent from my LGE LM-X410.FGN using XDA Labs
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Rebel_X said:
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Click to expand...
Click to collapse
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
Thanks a lot!! And it was as simple as that. It works fine. :good:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
MAREK10747 said:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
Click to expand...
Click to collapse
Hi,me devie is I4293
I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin
would you mind to make the kernel for me?
the file is here :
https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing
my gmail is [email protected]
you can send it to me.
thank you.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
yishisanren said:
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Zaben said:
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Click to expand...
Click to collapse
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
yishisanren said:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
Click to expand...
Click to collapse
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
wang4632 said:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
Click to expand...
Click to collapse
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
My I4293 stuck in bootloop~~help ~!
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
Zack_U said:
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
Click to expand...
Click to collapse
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.
Before rooting, you'll need an unlocked bootloader. Check my previous guide here: https://forum.xda-developers.com/x3...ck-bootloader-realme-x3-t4136325/post83109505.
After unlocking, we can get started with rooting.
First, you'll want to install Magisk Manager. You can find the latest APK here: https://github.com/topjohnwu/magisk/releases.
Next, you'll need to download the latest OTA OZIP. There's a link at the end of the post for this.
While that's downloading, you'll also need to grab a copy of an OZIP extractor. Follow the link below, download the repository as a ZIP, and unzip it.
For this program to work, you'll need Python 3 installed. On Linux systems, it should already be installed. On Windows 10, you can install Python from the Store.
Open a terminal or CMD window and cd to where you extracted the OZIP extractor files.
Use pip to install the docopt module: "pip3 install docopt".
Once the OZIP has finished downloading, move it to the same folder as the extractor program.
Run the following command: "python3 ozipdecrypt.py NAME_OF_OZIP_FILE". This will take a while!
Once it's done extracting, there will be a ZIP file with the same name as the OZIP. We only need two files from here: boot.img and vbmeta.img.
Extract those two files to the same folder as the extractor program.
Copy the boot.img file to your device.
Open Magisk Manager and choose the "INSTALL" option next to the Magisk status. Tap "INSTALL" in the dialog that appears and then choose "Select and Patch a File."
Browse to where you copied your boot.img to and select it. Magisk will now patch it and create a file named magisk_patched.img in your Download folder. Copy magisk_patched.img back to your computer.
Reboot your phone into fastboot: "adb reboot bootloader". If you don't have ADB or fastboot installed (which you should, since you needed them for the previous guide), you can find the link in the bootloader unlocking guide.
Before you flash the patched boot image, you need to disable image verification, which is where the vbmeta.img comes in.
Run "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (remember, you'll probably need to unplug and replug the device after hitting Enter). This will disable boot verification and allow the patched image to actually work.
Finally, run "fastboot flash boot magisk_patched.img". This will flash the rooted boot image to your device.
Run "fastboot reboot" and let the phone boot back into the system. Check Magisk Manager and you should now be rooted!
Troubleshooting:
If you get an error that the boot image was "destroyed," don't worry. You'll just need to flash the stock boot.img and try again. Unplug your phone from your computer and wait for it to turn off. Once the screen is black, hold down VOL-DWN and PWR to enter fastboot mode. You can then run "fastboot flash boot boot.img" (where boot.img is the stock image) to restore. Reboot, then try the vbmeta and patched image flashing again.
You can get the OTA OZIPs from Realme EU's site: https://www.realme.com/eu/support/software-update.
You can get an OZIP extractor from here: https://github.com/bkerler/oppo_ozip_decrypt. (NOTE: you'll need to install the "docopt" Python module.)
OZIPs contain a boot.img, which you can extract and patch with Magisk for root. If someone else has an idea for patching Magisk into the boot.img, this is where to start.
Here's my patched boot.img for A.32. I don't recommend using this on other versions: https://www.androidfilehost.com/?w=files&flid=315334
Could you share your patched boot.img for the latest OS version? And could you check if the aux magisk module from X2 pro works to activate all aux cameras in Gcam? Thanks
Patched boot image
Thanks Zacharee1....Could someone upload the patched boot image for the latest one? Also do we have a generic version of twrp that can be installed on x3 ?? If yes, then we could try installing havoc gsi...
I've added a link to a patched A.32 boot.img.
also needed pip install pycryptodome win10
Zacharee1 said:
I've added a link to a patched A.32 boot.img.
Click to expand...
Click to collapse
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
cheth20 said:
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
Click to expand...
Click to collapse
It's pretty simple to patch it yourself. Download the OZIP, use the Python tool to unencrypt it, take the boot.img file out of the created ZIP, copy it to your device, and then patch with with Magisk Manager.
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Firmware for RMX2085
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
The firmware is the same for them all.
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
phonedroid said:
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
Click to expand...
Click to collapse
Yes, and that's why. It might be possible to pull the boot image directly from your device, but I'm not sure.
Can someone tell me if I can use realme 6 pro vbmeta.img?
realme x3 super zoom twrp recovery bro give me
Hi Sukhad,
I updated the system to the latest OTA (39), but I do not have the latest magisk patched file. Could you kindly help me with latest version patched boot for x3 superzoom?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
Thanks Zacharee1!
Finally did it (15/20 year old windows machines... Win7 was dificult and finally use a win8). Worth big as root gives me a new smartphone
Had all sorts of problems (installing python... But once installed was pretty quick) mainly adb conneting...
Anyway I will share vbmeta.img attached for a38 rom.
Also link to boot img, again a38.
For A38 rom
http://www.mediafire.com/file/i9jvl1al95k40vv/magisk_patched_a38.img/file
bro please could u tell me.. help
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
bro please could u tell me.. after unlocking the bootloader of realme X3 superzoom , does it breaks the fingerprint sensor?
ota update after root
Someone have experiencing ota update failed on rooted device with this procedure? I m on RMX2081EU_11.A.40 but ota update to RMX2081EU_11.A.42 fails. how to update now?
Good afternoon. I want to get a root for my X3 super zoom, but I literally do not understand all the manipulations so that your description is attached with an image (screenshots). I think it will be useful for everyone who can't.
Anyone have working patched boot.img for a46?? I'm trying and always boot destroyed. Magisk 21.4
It's really weird on official en site there is a42 soft from September but on pl site there is a46 from December.
VERY IMPORTANT:
Please make sure your boot.img version matches the ROM version . that's mean if you update your device then you have to use patch boot.img from new recovery rom.never use the old one. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.(link in this post)
Then run this command
fastboot flash vbmeta vbmeta.img
fastboot flash boot patch-boot.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Shas45558 said:
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.
https://forum.hovatek.com/thread-32719.html
Go to method 3....log in to download vbmeta.img file.
Then run this command
fastboot flash boot patch-boot.img
fastboot flash vbmeta vbmeta.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Click to expand...
Click to collapse
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
nielsync said:
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
Click to expand...
Click to collapse
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Shas45558 said:
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Click to expand...
Click to collapse
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
nielsync said:
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
Click to expand...
Click to collapse
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Shas45558 said:
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Click to expand...
Click to collapse
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
nielsync said:
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
Click to expand...
Click to collapse
I use this version of magisk manager and it always work
Shas45558 said:
I use this version of magisk manager and it always work
Click to expand...
Click to collapse
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Thanks for the post. It helped me to root my redmi note 9.
nielsync said:
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Click to expand...
Click to collapse
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Shas45558 said:
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Click to expand...
Click to collapse
My issues was patching using the canary version of Magisk Manager which isn't stable enough and was probably not patching the boot image properly as opposed to Magisk Manager 7.5.1 which is the stable version. Nice explanation on the vbmeta.img file.
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
I guess this still doesn't unlock the bootloader, and what about system updates?
Kiwironic said:
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
Click to expand...
Click to collapse
Ok i do ir on top and bottom of the post and thanks for your advice:good::good:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
rizelgeorgel said:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
Click to expand...
Click to collapse
Download pbrp from official website.then extract it and you will get a .img file.flash it via fastboot mood and the cmd is
fastboot flash recovery pbrp.img
*Change pbrb.img according to your file name.
One big question..did you unlock your bootloader and root your device?
Thank you very much! I succeeded according to your advice!
shas hows pbrp?
regarding flashing?
mhark.moby said:
shas hows pbrp?
regarding flashing?
Click to expand...
Click to collapse
Pbrp is in beta testing....so it has some bug and there's no use to install..
Buenas tardes tengo problemas al cargar el parche de magisk en redmi 9. Cuando cargo el boot.img parchado de magisk el tlfn queda en bootloop estoy en la version 11.0.8 global.