Hey everyone, I'm trying to root my Xiaomi Mi a2 lite without twrp since, if i understand correctly, it needs the data partition to be formatted as it cant decrypt it, and I don't really need it anyway. I wanted to use Magisk manager to patch a boot image and flash it to get root, but the app explicitly asks for .img files. I've been looking everywhere and I can only find zip archives or .tgz files of my firmware. I'd appreciate any help, and btw my build number is 11.0.21.0
Ame76 said:
Hey everyone, I'm trying to root my Xiaomi Mi a2 lite without twrp since, if i understand correctly, it needs the data partition to be formatted as it cant decrypt it, and I don't really need it anyway. I wanted to use Magisk manager to patch a boot image and flash it to get root, but the app explicitly asks for .img files. I've been looking everywhere and I can only find zip archives or .tgz files of my firmware. I'd appreciate any help, and btw my build number is 11.0.21.0
Click to expand...
Click to collapse
A TGZ file is a TAR Archive file that has been compressed using Gnu Zip (gzip).
You can uncompress tgz files using 7-zip:
7-Zip
7-zip.org
VD171 said:
A TGZ file is a TAR Archive file that has been compressed using Gnu Zip (gzip).
You can uncompress tgz files using 7-zip:
7-Zip
7-zip.org
Click to expand...
Click to collapse
oooh thank you so much, feeling pretty stupid rn
Obviously, first you need unlocked bootloader, or your device will get bricked.
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.)
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 are rooted.
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.
You can use 7-Zip: https://7-zip.org
VD171 said:
Obviously, first you need unlocked bootloader, or your device will get bricked.
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.)
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 are rooted.
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.
You can use 7-Zip: https://7-zip.org
Click to expand...
Click to collapse
thanks dude, you're really helping me out with this
VD171 said:
Obviously, first you need unlocked bootloader, or your device will get bricked.
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.)
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 are rooted.
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.
You can use 7-Zip: https://7-zip.org
Click to expand...
Click to collapse
Hey i seem to be having a problem, i extracted the .tar file and i can see the boot.img file but i can't find the vbmeta.img one
Ame76 said:
Hey i seem to be having a problem, i extracted the .tar file and i can see the boot.img file but i can't find the vbmeta.img one
Click to expand...
Click to collapse
Actually i've looked around and everyone only shares the boot file, maybe flashing vbmeta is unnecessary for this device?
Maybe.
Related
Hi, sorry this is a really basic question but I can't find a proper answer.
How do I flash the modules for a kernel? I found the modules folder inside the zip but there are lots of files in it, how do I flash them to my phone?
Also the flashing tools provided with some roms never work for me, fastboot always says something like "....fastboot-windows isn't a recognised internal command..." but I have no problem flashing the boot.img manually through fastboot. Is the flasher tool needed to flash the kernel modules?
Any advice will be much appreciated, I'm trying to get CM9 Domination working but it just boot loops, I assume because I'm not flashing the kernel modules.
Thanks.
How to flash kernels.
first off, there should be two parts to the kernel that you have, first the module, that should be in a .zip format, and also a .img file that should be "kernel-11".img or boot.img or something or other. First you need to open fastboot, and in Command prompt with the ".img" file inside your adb.exe/fastboot.exe/adbwinapi.dll folder that contains these, forward CMD to this folder, , type "fastboot erase cache", then "fastboot flash boot "kernel-11.img" or whatever your .img filename is, then after this is complete you need to reboot recovery, then go to install zip from SD, of which you needed to place the module on your sd card, then simply flash the file and you should have installed your kernel!
^Remember to Hit thanks! ^^
Also, in regards to the error, i dont think your using the folder that you need to be in, What you should do is create a folder somewhere that is convenient for you that you can easily access and remember the address, then add the files fastboot.exe, adbwinapi.dll and adb.exe to, which are all located in your android-sdk/platform-tools/!
Thanks smithr179, I thought I'd have to flash through fastboot or adb, no wonder I couldn't figure it out! Recovery sounds much easier, thanks
The modules in the file I have for the stock kernel are in a normal folder (not a .zip) but they are inside a larger zip folder containing the boot.img, meta inf and system folders. Do I just flash the whole .zip file or should the modules be in a zip of their own?
I'm trying hard to get to grips with all this lol Many thanks for your help
NB. I just tried flashing the whole zip file with everything in it and it worked! Modules were flashed as well as the boot.img. Thanks for all your assistance, much appreciated
Attempting to extract the boot.img from your latest Essential PH-1 rom and all I'm seeing is a payload.bin
Is there a way to extract it from the bin?
Trying to flash Magisk which requires flashing a custom boot.img before Magisk.zip
Thanks!
Use Android kitchen
Bro try to use zip extractor and even you could use Android kitchen to extract boot.img to ramdisk &split-img
You could find required files therefore
jAm-0 said:
Attempting to extract the boot.img from your latest Essential PH-1 rom and all I'm seeing is a payload.bin
Is there a way to extract it from the bin?
Trying to flash Magisk which requires flashing a custom boot.img before Magisk.zip
Thanks!
Click to expand...
Click to collapse
10.5.10.IN11BA (European version):
I dumped the boot.img with payload dumper from the "OnePlus8ProOxygen_15.E.19_OTA_019_all_2007021957_d0064.zip" file and patched it with magisk
Note: This is for the European variant of version 10.5.10(.IN11BA)
Download links:
boot.img: https://drive.google.com/file/d/1q9BP31PO6tELbTR-4bWD8pP19_g_VSU0/view?usp=sharing
patched boot.img: https://drive.google.com/file/d/1peDOwsvoUVIoEkp8WZ3jGoRvyqd46MOo/view?usp=sharing
You can use these files to root your OP8Pro with the following guide: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-how-to-root-oneplus-8-pro-twrp-t4083981
10.5.10.IN11AA (global version):
I dumped the boot.img with payload dumper from the "OnePlus8ProOxygen_15.O.19_OTA_019_all_2005301411_63c531a1a94a4fc1.zip" file, you'll have to patch it yourself with magisk
Here is the boot.img file for 10.5.10.IN11AA : https://gofile.io/d/yavZRg
You can patch it using the following steps (source: Magisk github)
Copy the boot.img file to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. (If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img)
Flash the patched boot image to your device with adb:
Code:
fastboot flash boot /path/to/magisk_patched.img
reboot
Please give me feedback if it worked or not
Hello, Thanks for this work. Just a beginner's question, I suppose you must already have an unlocked bootloader to use your files.
vigneras said:
Hello, Thanks for this work. Just a beginner's question, I suppose you must already have an unlocked bootloader to use your files.
Click to expand...
Click to collapse
Yes of course.
Is this patched with magisk 20.4,not magisk canary? And fingerprint sensor works after that?
Thanks, I would come back after unlocking the bootloader
janitor9 said:
Yes of course.
Is this patched with magisk 20.4,not magisk canary? And fingerprint sensor works after that?
Click to expand...
Click to collapse
Yes indeed, patched with 20.4 and fingerprint works fine. I recommend backing up the persist.img just to be sure
Hey brother, any chance of patching 10.5.10AA? Thank you in advance. Cheers
Sent from my IN2025 using Tapatalk
rawhide85 said:
Hey brother, any chance of patching 10.5.10AA? Thank you in advance. Cheers
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
Here is the boot.img file for 10.5.10.IN11AA : https://gofile.io/d/yavZRg
You can patch it using the following steps (source: Magisk github)
Copy the boot.img file to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. (If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img)
Flash the patched boot image to your device with adb:
Code:
fastboot flash boot /path/to/magisk_patched.img
reboot
Unable to boot from patched image. Unable to boot from normal boot patched with magisk ... as a hole - no root with 10.5.10BA
Can someone suggest solution?
Lucifer4o said:
Unable to boot from patched image. Unable to boot from normal boot patched with magisk ... as a hole - no root with 10.5.10BA
Can someone suggest solution?
Click to expand...
Click to collapse
Boot the twrp and flash magisk
cultofluna said:
Boot the twrp and flash magisk
Click to expand...
Click to collapse
Same result - boot loop.
Does anyone have the stock boot.img for the Global version of 10.5.10? For the IN2017 OnePlus 8. IN21AA.
10.5.11 EU Patched pls ??
alxioa said:
10.5.11 EU Patched pls ??
Click to expand...
Click to collapse
Found it here:
https://forum.xda-developers.com/showpost.php?p=83137417&postcount=424
Flying Fox said:
Found it here:
https://forum.xda-developers.com/showpost.php?p=83137417&postcount=424
Click to expand...
Click to collapse
Thanks my friend
hi, sadly the payload unzip doesn't work on my computer. I am urgently looking for the boot.img for 10.5.10.IN21BA. Can anyone help me? i can't find it on the net.
I need a boot.img necessarily from 12.5.6.0.RKHEUXM GLOBAL.
Nowhere is this version of ROM in FastBoot format to download.
I need extract boot.img to magisk root.
I have an installed version of 12.5.6.0.
But I mistake I flash boot.img from version 12.5.3.0. , and now I have a broken system, it's not sound,wi-fi, etc.
Thanks very much
Hi. I used the boot.img from the 12.5.6 "Stable Beta" released a few weeks ago. I read somehere, here, that it is the same built as the one released over OTA a couple of days ago. And so far it's working fine. I have wifi and sound.
It is a recovery file, but you can unzip it and then use a payload dumper tool to extract the boot.img.
The recovery: https://xiaomifirmwareupdater.com/miui/alioth/stable beta/V12.5.6.0.RKHEUXM/
And this tool on my Mac: https://github.com/ssut/payload-dumper-go/releases/tag/1.0.0
kurtschmeichel said:
Hi. I used the boot.img from the 12.5.6 "Stable Beta" released a few weeks ago. I read somehere, here, that it is the same built as the one released over OTA a couple of days ago. And so far it's working fine. I have wifi and sound.
It is a recovery file, but you can unzip it and then use a payload dumper tool to extract the boot.img.
The recovery: https://xiaomifirmwareupdater.com/miui/alioth/stable beta/V12.5.6.0.RKHEUXM/
And this tool on my Mac: https://github.com/ssut/payload-dumper-go/releases/tag/1.0.0
Click to expand...
Click to collapse
If I may go off-topic for a question, recovery files are to be flashed in recovery? fastboot files in fastboot mode? hope you can help enlighten me.
I dont need recovery type rom , there is not after unzip the boot. img.
I need fastboot type rom, there is boot. img after unzip.
Thanks
I must flash boot.img over magisk, not twrp!
Please read my previous post again.
You can get a boot.img from the recovery file!
kurtschmeichel said:
Please read my previous post again.
You can get a boot.img from the recovery file!
Click to expand...
Click to collapse
Thanks very much I'll try it.
So far I have tried to extract boot.img from China V12.5.6.0.RKHCNXM Fastboot TYPE, I flashed it via magisk and everything works fine.
If everything works OK, then it's fine
When the official 12.5.6.0.RKHEUXM is published, you can still patch and flash its boot.img again, in order to be sure you have the right one. I will do it.
Or just wait for the Android 12 update.
kurtschmeichel said:
If everything works OK, then it's fine
When the official 12.5.6.0.RKHEUXM is published, you can still patch and flash its boot.img again, in order to be sure you have the right one. I will do it.
Or just wait for the Android 12 update.
Click to expand...
Click to collapse
;-)
To complete this thread, here is how I extracted the boot.img from the recovery file:
- Download the recovery file from here: https://xiaomifirmwareupdater.com/miui/alioth/stable beta/V12.5.6.0.RKHEUXM/
- Unzip it, you will find a payload.bin file inside.
- Download this command line tool for your platform, I used it on my Mac: https://github.com/ssut/payload-dumper-go/releases
- Unpack it and put the binary inside the folder of the unpacked recovery, next to the payload.bin file
- Run the command : ./payload-dumper-go payload.bin
- Let it do its thing and you will find a series of .img files, one will be boot.img
Credits: https://forum.xda-developers.com/t/tool-a-quick-android-ota-payload-dumper.4173271/
Is there any way to root a gsi? All the tutorials seem to make you flash stock everything. Any way to get magisk running on a android 12 gsi? (Descendant os)
Airpewdiepie said:
Is there any way to root a gsi? All the tutorials seem to make you flash stock everything. Any way to get magisk running on a android 12 gsi? (Descendant os)
Click to expand...
Click to collapse
You can get the boot.img from the stock firmware, lemme explain it to you:
1. Get the firmware.
2. Open the file beginning with AP
3. Extract boot.img.lz4 with WinRAR
4. Get lz4, drag the file into the lz4.exe
5. There is a new file named "boot.img"
6. install 7Zip
7. right click > 7Zip > Add to archive
8. make sure its .tar
9. Enable debugging mode and drag drop the boot.tar into any folder in your phone
10. Patch it with magisk
11. Drag it back to your PC.
12. Open ODIN, then put the magisk_patched... into the AP slot.
13. Press "Start" (i think)
Franzyy said:
You can get the boot.img from the stock firmware, lemme explain it to you:
1. Get the firmware.
2. Open the file beginning with AP
3. Extract boot.img.lz4 with WinRAR
4. Get lz4, drag the file into the lz4.exe
5. There is a new file named "boot.img"
6. install 7Zip
7. right click > 7Zip > Add to archive
8. make sure its .tar
9. Enable debugging mode and drag drop the boot.tar into any folder in your phone
10. Patch it with magisk
11. Drag it back to your PC.
12. Open ODIN, then put the magisk_patched... into the AP slot.
13. Press "Start" (i think)
Click to expand...
Click to collapse
It wont replace my rom? also, can i do it without a factory reset?
Airpewdiepie said:
It wont replace my rom? also, can i do it without a factory reset?
Click to expand...
Click to collapse
1. It wont replace your rom
2. You sadly have to do a factory reset, then reflash the boot.tar again
Never root at boot, there are many people who lost IMEI by rooting at boot.
Melky777 said:
Never root at boot, there are many people who lost IMEI by rooting at boot.
Click to expand...
Click to collapse
You have to delete the imei folder to make imei working again
Melky777 said:
Never root at boot, there are many people who lost IMEI by rooting at boot.
Click to expand...
Click to collapse
A fix has been found for it.
Franzyy said:
1. It wont replace your rom
2. You sadly have to do a factory reset, then reflash the boot.tar again
Click to expand...
Click to collapse
Any reason for the factory reset?
i was able to root my phone running crdroid 8.8. all i did was first download the firmware. after that i copied over the AP file of the firmware to my phone and then selected that in magisk to patch it. after it patched it i copied it back over to my pc and flashed the ap file along with bl, cp and CSC file. it reset and it worked fine! now any GSI i try and i install magisk v22.0 apk it works just fine.