Question (solved) How to use magisk with V14.0.1 global rom? - Xiaomi Mi 11 Ultra

Hi there, did anyone install magisk and root on new global rom using Fastboot?
To get boot.img I used this tool - https://github.com/ssut/payload-dumper-go/releases/tag/1.2.2
After that I patched boot.img in Magisk app as usual and then upload patched img using ADB and fastboot. But as a result - phone endless reboot.
Of course I uploaded original boot.img and the phone is back, but right now I`m trying to understand what I messed up.
Magisk 25.2, rom miui_STARGlobal_V14.0.1.0.TKAMIXM_f8a19b0595_13.0
Any ideas? Thx

Bro, download 14.0.1 global rom and open with winrar then pull out source file boot.img and copy to phone to patch it. Using tool to reverse build boot.img may cause errors.

diorlee90 said:
Bro, download 14.0.1 global rom and open with winrar then pull out source file boot.img and copy to phone to patch it. Using tool to reverse build boot.img may cause errors.
Click to expand...
Click to collapse
This method also causes loop. Phone boots to main screen, but after 10 seconds, it reboots into stock recovery.

Venomz33 said:
This method also causes loop. Phone boots to main screen, but after 10 seconds, it reboots into stock recovery.
Click to expand...
Click to collapse
i used many times without any errors, after patch boot.img via magisk you must copy patched file img to computer and flash via adb_platform-tools. If any error check command again.

diorlee90 said:
i used many times without any errors, after patch boot.img via magisk you must copy patched file img to computer and flash via adb_platform-tools. If any error check command again.
Click to expand...
Click to collapse
I've done exactly the same. Done before but 14 gives this problem. I patched using the command below from CMD.
C:] fastboot flash boot boot.img

Related

So has anyone figured out how to root the phone?

I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
TheRedPandaSSN said:
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
Click to expand...
Click to collapse
I haven't been able to root it either. How'd u unlock the bootloader ?
greeneyez15o said:
I haven't been able to root it either. How'd u unlock the bootloader ?
Click to expand...
Click to collapse
If you go into developer options it allows you to unlock the bootloader.
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
I don't think that completely unlocks the bootloader
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
All that does is ALLOW the bootloader to be unlocked - it doesn't unlock it.
I just unlocked the bootloader
Used adb
"Fastboot flashing unlock"
Next im gonna try to apply root
Wish me luck
I have just ordered this phone. Will hopefully be able to share backup copies of ramdisk(boot) to be used with magisk to give root
Well if anyone is Interested in trying out mtk-su to get system-less, boot-less root it should work. It worked with my umidigi phone that also has mtk p70 soc. And running pie.
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Here is device back up script project I had done based on that mtk-su.
https://github.com/mrmazakblu/Root-Backup-Helper
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (currently i used V 7.3.4, after magisk update, V20 caused device trouble. Recommend stay with mahisk v19.3) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
:::UPDATE::10-27
Successfully flashed magisk with twrp. But because the current twrp has no working touchscreen. It was done with ADB commands.
mrmazak said:
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (use most recent version, currently i used V 7.3.4) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
Click to expand...
Click to collapse
How'd u patch the boot.img ?
Thanks !!!
greeneyez15o said:
How'd u patch the boot.img ?
Thanks !!!
Click to expand...
Click to collapse
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
Click to expand...
Click to collapse
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
Click to expand...
Click to collapse
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Code:
adb pull /sdcard/Download/patched_boot.img c:\adb\
adb reboot bootloader
fastboot flash boot c:\adb\patched_boot.img
fastboot reboot
mrmazak said:
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Click to expand...
Click to collapse
Got it !!! Had to reboot my computer ?
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Does anyone manage to change the system file? when you try the phone freezes helps reboot
fafanakatr said:
Does anyone manage to change the system file? when you try the phone freezes helps reboot
Click to expand...
Click to collapse
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
mrmazak said:
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
Click to expand...
Click to collapse
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
fafanakatr said:
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
Click to expand...
Click to collapse
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
I will try to do as you suggested and let you know) I will be well waiting for your success
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
thank you very much I did everything according to the instructions and everything worked out for me,I tried to turn on the camera2api but so far without success,
can you understand this?

Root and bootloop issues help

Hi everyone ,
First of all sorry if my english is bad it's not my first language .
Let me explain my problem :
- I root magisk using twrp to root my phone but every time i do that my phone can't boot to system but only twrp (boot loop) and i have to factory reset to get back to the system . Also when i try to install unimod when i installed magisk it says that magisk is not installed .
- So i tried super su , it installed correctly and can boot properly but root checker says that he's not rooted ...
Can someone help me ? Thanks
Astrusky said:
Hi everyone ,
First of all sorry if my english is bad it's not my first language .
Let me explain my problem :
- I root magisk using twrp to root my phone but every time i do that my phone can't boot to system but only twrp (boot loop) and i have to factory reset to get back to the system . Also when i try to install unimod when i installed magisk it says that magisk is not installed .
- So i tried super su , it installed correctly and can boot properly but root checker says that he's not rooted ...
Can someone help me ? Thanks
Click to expand...
Click to collapse
Extract "boot.img" from your stock rom and flash it.
Reboot again to TWRP, then flash magisk. Reboot
gringo80 said:
Extract "boot.img" from your stock rom and flash it.
Reboot again to TWRP, then flash magisk. Reboot
Click to expand...
Click to collapse
Can you tell me how i can extract it ? I'm a beginner xD
gringo80 said:
Extract "boot.img" from your stock rom and flash it.
Reboot again to TWRP, then flash magisk. Reboot
Click to expand...
Click to collapse
Or maybe a tutorial ?
Astrusky said:
Or maybe a tutorial ?
Click to expand...
Click to collapse
With software like winrar or 7zip click right click on recovery rom and extract, then turn off your phone, press volume down and connect usb, you will see fastboot logo on your phone. Put previously extracted boot into same folder with minimal adb fastboot, flash with command fastboot flash boot boot.img
Stefke93 said:
With software like winrar or 7zip click right click on recovery rom and extract, then turn off your phone, press volume down and connect usb, you will see fastboot logo on your phone. Put previously extracted boot into same folder with minimal adb fastboot, flash with command fastboot flash boot boot.img
Click to expand...
Click to collapse
When i do that twrp is not working anymore i get back to the regular recovery ...
Astrusky said:
When i do that twrp is not working anymore i get back to the regular recovery ...
Click to expand...
Click to collapse
Edit when i install magisk via a pre patched boot image it works until the app asks me to install additional things to make it work and then stuck in twrp
Stefke93 said:
With software like winrar or 7zip click right click on recovery rom and extract, then turn off your phone, press volume down and connect usb, you will see fastboot logo on your phone. Put previously extracted boot into same folder with minimal adb fastboot, flash with command fastboot flash boot boot.img
Click to expand...
Click to collapse
And in the app they say everything is installed except additional zip but when i try to install uninstall mod they say magisk is not installed

Nokia 4.2 Bricked, but can still enter FastBoot

Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u
Search on google and try do download and flash the stock firmware (unrooted)
Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.
#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Posted
alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?
Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.

OOS stable boot image and patched magisk boot image both for 11.1.1.1.

Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​
235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)
previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later
abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.
I got boot loop after updating to 11.1.2.2
Any new boot img?
izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.
The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes
rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you
Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.​​I uninstalled magisk by mistake and could regain root, quick and painless​
Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?

Question Magisk ROOT MIUI 14

I would like to know if someone has managed to root with magisk from CMD without twrp?
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
or965 said:
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
Click to expand...
Click to collapse
ive use your method but my phone still gone to bootloop. im using eu rom currently.
martin132014 said:
ive use your method but my phone still gone to bootloop. im using eu rom currently.
Click to expand...
Click to collapse
What did you do? I wrote several options.
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
System23 said:
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
Click to expand...
Click to collapse
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
or965 said:
What did you do? I wrote several options.
Click to expand...
Click to collapse
I use the method for eu that you posted. First i install magisk 25.2 and then i patch the rom boot.img. I boot to fastboot and flash the patch boot.img using the command. It flash successful then i reboot. But it still bootloop.
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
martin132014 said:
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
Click to expand...
Click to collapse
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
martin132014 said:
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
Click to expand...
Click to collapse
and what your experience with that!!! Tell me why you like this!!!
System23 said:
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
Click to expand...
Click to collapse
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
ok a Tip to you!!! when you only Backup Data Partition you can restore it and all Contacts,SMS,Accounts,Apps are availibile again on new ROM!!!
Why you dont use the Magisk.zip and flash it via TWRP after Flash ROM!!! you can rename Magisk.apk to Magisk.zip and flash it!! than you dont need other steps to Root!!! when it dosnt work use the recovery.img to Patch it and try this Method for Rooting, but dont forgett when ya do so you need to try the Buttons-Combo to start in Recovery to boot the System in Root and you have no Recovery-Mode at this Method!!! Also to use Recovery again you must Flash it again via Fastboot!!
And in TWRP use the WIPE Option to make a Factory Reset or WIPE a Single Partition, after some Flashing CROMS its needed to be WIPE the Data Partition!!!
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
you can ask me what you would i share my Informations with ya!!! when iam not knowing iam googleing it out to find a solution!! the talk we have start are hope helpfully!! when ya have intresst we can stay in kontakt and make what we can, even its public 4 all or PM!!! PS i must not hide my Knowledge, but PM its OK too!!!

Categories

Resources