Database Develop

[OOS: 9.0.5 | 9.0.6 | 9.0.7]Root With No Recovery (Patched Boot image).

Root the OnePlus 6T with no TWRP.
Required:
[*]Latest ADB/Fastboot.
[*]Have OOS 9.0.5 | 9.0.6 | 9.0.7 in place.
[*]Unlocked bootloader.
How to:
[*]Boot into bootloader
[*]Download the patched boot image 9.0.5 here.
[*]Download the patched boot image 9.0.6 here.
[*]Download the patched boot image 9.0.7 here.
[*]Drop the Patched boot image file inside your ADB/Fastboot folder.
[*]Open up a CMD window in the folder location.
[*]Type this command in CMD:
Code:
fastboot boot <filename>.img
[*]When the phone got booted download magisk manager here and install it.
[*]Open Magisk Manager and you'll see that it says that you're rooted.
[*]Make sure you checked "Preserve force encryption" and "preserve AVB 2.0/dm-verity".
[*]Click on Install and select Direct Install (Recommended)
[*]Wait till it's installed and ask you to reboot your device, reboot it.
Your'e now rooted.
If you need any help here is my telegram chat for support, or if you want to chat. here.

delete

Dark Nightmare said:
You should probably remove your telegram chat link, don't think it's allowed.
Click to expand...
Click to collapse
That's only for random links i think. i use a op6 kernel (smurf kernel) and he has his telegram chat open up for a long time.

mingo_mgx said:
That's only for random links i think. i use a op6 kernel (smurf kernel) and he has his telegram chat open up for a long time.
Click to expand...
Click to collapse
Oh okay, then disregard my comment, sorry.

mingo_mgx said:
Root the OnePlus 6T with no TWRP.
Required:
[*]Latest ADB/Fastboot.
[*]Have OOS 9.0.5 in place.
[*]Unlocked bootloader.
How to:
[*]Boot into bootloader
[*]Download the patched boot image here.
[*]Drop the Patched boot image file inside your ADB/Fastboot folder.
[*]Open up a CMD window in the folder location.
[*]Type this command in CMD:
Code:
fastboot boot patched_boot905.img
[*]When the phone got booted download magisk manager here and install it.
[*]Open Magisk Manager and you'll see that it says that you're rooted.
[*]Make sure you checked "Preserve force encryption" and "preserve AVB 2.0/dm-verity".
[*]Click on Install and select Direct Install (Recommended)
[*]Wait till it's installed and ask you to reboot your dervice, reboot it.
Your'e now rooted.
If you need any help here is my telegram chat for support, or if you want to chat. here.
Click to expand...
Click to collapse
Worked perfectly, thank you.

Sorry if this is super noob question, but you still have to unlock the bootloader to do this, correct?

Mdaly001 said:
Sorry if this is super noob question, but you still have to unlock the bootloader to do this, correct?
Click to expand...
Click to collapse
Yes

Hi, I must be missing it but where can I download the patched boot image? Also, is this the same as rooting by flashing Magisk in TWRP? I was rooted that way before but I had that bug where the phone gets stuck on the bootloader is unlocked screen, seems to be a bug in the latest Magisk so I uninstalled it and was holding off for the time being. Thx!

YrrchSebor said:
Hi, I must be missing it but where can I download the patched boot image? Also, is this the same as rooting by flashing Magisk in TWRP? I was rooted that way before but I had that bug where the phone gets stuck on the bootloader is unlocked screen, seems to be a bug in the latest Magisk so I uninstalled it and was holding off for the time being. Thx!
Click to expand...
Click to collapse
Perhaps you're not seeing the link highlighted in the OP on mobile or for whatever reason.
Anyhoo,click on the word "here",Step 2 under the "How To" sub-heading & the "here" Magisk link in the following sub-heading.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or,just click on this link,where it resides:
https://androidfilehost.com/?fid=11410963190603844693
As for the rest,perhaps someone else will chime in soon,I'm still stock/locked,last device I rooted was an Honor View 10 a few months back,have since sold.......

KOLIOSIS said:
Perhaps you're not seeing th link highlighted in the OP on mobile or for whatever reason.
Anyhoo,click on the word "here",Step 2 under the "How To" sub-heading & the "here" Magisk link in the following sub-heading.
Or,just click on this link,where it resides:
https://androidfilehost.com/?fid=11410963190603844693
As for the rest,perhaps someone else will chime in soon,I'm still stock/locked,last device I rooted was an Honor View 10 a few months back,have since sold.......
Click to expand...
Click to collapse
Whoa, there's a couple lines there that aren't showing up in the XDA Android app, one of them being the here button to download the image. of course I have to download them on my laptop but I have a Chromebook right now running Android apps, including XDA. Anyway, thank you for posting it for me ?
Ah ok, do you just not find root necessary? I am basically fine without it, especially when there is no root or it is kind of a hassle. But somehow I can't help but tinker when it's as easy as it is on this phone ?

YrrchSebor said:
Whoa, there's a couple lines there that aren't showing up in the XDA Android app, one of them being the here button to download the image. Thank you for posting it for me
Ah ok, do you just not find root necessary? I am basically fine without it, especially when there is no root or it is kind of a hassle. But somehow I can't help but tinker when it's as easy as it is on this phone
Click to expand...
Click to collapse
I plan on rooting eventually,to disable apps/services that ping back info to who knows where, & using AdAway,that's about it for the main points.
As for ROMs,the choices are awesome once all the different teams get on board,my favorite being either RR Remix or Lineage,otherwise stock/rooted OOS is just as good.
Yeah,root is easy w/this phone,even the T-Mobile version isn't all that bad.
This phone is a good bang for the buck,but,if rooting/ROMs weren't part of the eventual equation,I'd pass on it & opt for a mid-tier phone,as this is my secondary device (Note9 is my DD).
One nice thing about OnePlus phones is the past four models have been one of the better SIM/Carrier free phones to use on T-Mobile US,as they've had the latest LTE Bands & WI-FI Calling & VoLTE work.
VVM probably works as well,but,I have never used it on any phone & probably never will.

KOLIOSIS said:
I plan on rooting eventually,to disable apps/services that ping back info to who knows where, & using AdAway,that's about it for the main points.
Click to expand...
Click to collapse
I logged all the DNS lookups, and I was shocked at how much ET was phoning home.
I black-holed all the bullsh!t telemetry and analytics calls with my DNS server and in the 6T hosts file.

Thank you, works like a charm.

Couldn't we just use the magisk manager app to patch our boot image ourselves and flash it?

YrrchSebor said:
Hi, I must be missing it but where can I download the patched boot image? Also, is this the same as rooting by flashing Magisk in TWRP? I was rooted that way before but I had that bug where the phone gets stuck on the bootloader is unlocked screen, seems to be a bug in the latest Magisk so I uninstalled it and was holding off for the time being. Thx!
Click to expand...
Click to collapse
In this way did you resolve the problem?

Is there an advantage to this method, like being able to get system updates without having to flash them urself?

From a security perspective, how can we trust any images like these?
Unless the file has a digital signature from Google or OnePlus, or a least we can verify the hash, how do we know there is no 'rootkit' or some other backdoor?
No offense intended to OP.

mingo_mgx said:
Root the OnePlus 6T with no TWRP.
Required:
[*]Latest ADB/Fastboot.
[*]Have OOS 9.0.5 in place.
[*]Unlocked bootloader.
How to:
[*]Boot into bootloader
[*]Download the patched boot image here.
[*]Drop the Patched boot image file inside your ADB/Fastboot folder.
[*]Open up a CMD window in the folder location.
[*]Type this command in CMD:
Code:
fastboot boot patched_boot905.img
[*]When the phone got booted download magisk manager here and install it.
[*]Open Magisk Manager and you'll see that it says that you're rooted.
[*]Make sure you checked "Preserve force encryption" and "preserve AVB 2.0/dm-verity".
[*]Click on Install and select Direct Install (Recommended)
[*]Wait till it's installed and ask you to reboot your dervice, reboot it.
Your'e now rooted.
If you need any help here is my telegram chat for support, or if you want to chat. here.
Click to expand...
Click to collapse
Works like a charm thank you! Would you provide us with an updated patched boot file when there is an update to Oxygen OS?

I assume all of you are on tmobile OP 6t since non tmobile would get their updates via OTA, correct? Also, does applying the update in this manner wipe the existing programs on the phone, again, I assume it does since bootloader has to be unlocked and Magisk is reporting root?
And lastly, Magisk Manager newest update is 6.0.1 so is there a reason you state to download 5.8.1 in the OP? Just curious, could be just incidental...?

free4flight said:
I assume all of you are on tmobile OP 6t since non tmobile would get their updates via OTA, correct? Also, does applying the update in this manner wipe the existing programs on the phone, again, I assume it does since bootloader has to be unlocked and Magisk is reporting root?
And lastly, Magisk Manager newest update is 6.0.1 so is there a reason you state to download 5.8.1 in the OP? Just curious, could be just incidental...?
Click to expand...
Click to collapse
For OTA, remove root in current slot within magisk manager, install OTA (full zip) within OOS, don't reboot, then apply root with magisk manager on the other slot (the one where OTA have been flashed) then only you can reboot. Root is preserved.

[OOS] [11] Open_Beta_1_HD01AA [Global/India] [Stock/Patched boot.img] [Stock/ADB Recovery] [Full ZIP] [OOS 10.0.13/10.3.7]

OnePlus 7T Pro HD01AA Global 11 Open Beta 1
Magisk Patched Boot Image v21.4 Patched Manager v8.0.7
https://www.androidfilehost.com/?fid=17248734326145719979
May need to install Magisk Manager manually
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719978
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719976
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719977
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322189
OnePlus 7T Pro HD01AA India 11 Open Beta 1
Magisk Patched Boot Image v21.4 Patched Manager v8.0.7
https://www.androidfilehost.com/?fid=17248734326145719991
May need to install Magisk Manager manually
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719989
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719993
Stock Recovery Image
https://androidfilehost.com/?fid=17248734326145719992
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322190
OnePlus 7T Pro HD01AA Global 10.0.13
Magisk Patched Boot Image
https://www.androidfilehost.com/?fid=10763459528675591747
May need to install Magisk Manager manually
Full ZIP OxygenOS HD01AA 10.0.13
https://www.androidfilehost.com/?fid=10763459528675591755
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675591746
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591748
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591745
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320328
OnePlus 7T Pro HD01AA India 10.3.7
Magisk Patched Boot Image
https://www.androidfilehost.com/?fid=10763459528675592073
Full ZIP OxygenOS HD01AA 10.3.7
https://www.androidfilehost.com/?fid=10763459528675592086
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675592074
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675592075
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675592076
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320346
Usage (Unlocked Bootloader)
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot path/to/patched_boot.img or fastboot flash recovery path/to/patched_recovery.img
fastboot reboot

Wifi issue?
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?

isellmidgets said:
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
Click to expand...
Click to collapse
Make sure you flash the right boot for your model number.
Settings>About phone>Build number should end HD01BA or HD01AA so make sure it's the right one.
If you want to test that your Wi-Fi works with one of the boot images.
Instead of 'fastboot flash boot patched_file_name.img' do 'fastboot boot patched_file_name.img'

I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again

isellmidgets said:
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
Click to expand...
Click to collapse
I unlocked my OP 7t pro's bootloader, and every time there is an update I download the stuff mirrored by digidude512 ... I grab the magisk patched boot and the updated system pack.
I go to updates, update manually with having the update pack in the root of the storage.
When the update is done, I do not restart using the update reboot button - I use the boot to bootloader option at the power button menu (which can be enabled at the dev settings).
Then going to fastboot directly I flash the patched boot image using fastboot on windows cmd: fastboot flash boot boot_blabla.img --slot all
Reboot, go to magisk manager, update magisk using recommended direct install. Update magisk manager. Done.
Never had any problem (no wifi f*ery, nothing) and there is no need for TWRP at all. Open bootloader, magisk root and modules, adaway, stock ROM. Decent and clean.
Thanks a lot @digidude512 once again for this. Pretty convenient for others this way.

[zozi] said:
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
Click to expand...
Click to collapse
If you're rooting for the first time, use fastboot boot patched_boot.img and perform a direct install from within Magisk Manager to avoid potential headaches.
If you are doing an OTA update and want to retain root, you should not be fastboot flashing anything (you're not following the right guide).

[zozi] said:
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
Click to expand...
Click to collapse
Sorry for the late reply, I couldn't sign in while XDA was changing format.
For HD01BA you want this thread.
[OOS] [11] Open_Beta_2_HD01BA [EU] [Stock/Patched boot.img] [Stock/ADB Recovery] [Full ZIP] [OOS 10.0.13]
@digidude512 Every Update needs a new Thread... interesting. Stop this sh!t.
forum.xda-developers.com

can someone please provide me with batched boot image for OnePlus 7T (India), i extracted the boot.img by using payload dumper then i batched it using magisk 8.0.5 but unfortunately when i flash it using fastboot it loops at the OnePlus animation logo

Thread updated with files for OxygenOS 11 Open Beta 1 including both Global and India Variants.

Does patched boot.img Magisk work on MIUI V12.5.1.0? (Edit: Yes it does!)

Just curious if anyone has any insight as to whether I can use the Magisk app to patch the newest boot.img (12.5.1.0 global / Android 11 / mi9t pro) and whether it will go smoothly if I install it via fastboot flash boot patchedmagiskhere.img?
I just updated the device using the clean_all mode on MiFlash and everything looks to be working fine;
No TWRP or custom recovery installed
Bootloader in unlocked state
As the update is so new I just wanted to check if anyone had any experience before I go ahead. There's also the old method of flashing magisk as a .zip via TWRP which is now 'depreciated'. As the device says 'Ramdisk NO' it implies Magisk may need to be used in 'recovery mode' (i.e. patched recovery.img and vol+power on every boot) but it worked just fine in MIUI11 so I don't think that's right.
Update: If you've come here looking to find out how to do this then I added instructions in this post.

Can't find answers so I might try fastboot boot patched_magisk.img later today. In theory this'll let me test a patched boot.img instead of going in blind with fastboot flash boot patched_magisk.img so that the boot.img isn't flashed, just booted. If it works I assume I can probably just select Direct Install in Magisk.

droident said:
Can't find answers so I might try fastboot boot patched_magisk.img later today. In theory this'll let me test a patched boot.img instead of going in blind with fastboot flash boot patched_magisk.img so that the boot.img isn't flashed, just booted. If it works I assume I can probably just select Direct Install in Magisk.
Click to expand...
Click to collapse
Hey let me know if you find a solution for this.
I upgarded to this version via TWRP last night. Tried flashing Magisk via TWRP and it kept boot looping into TWRP.
Had to re-flash the rom again in order to boot into the system.
I tried patching the stock recovery image but couldn't get the system to boot into Magisk mode. Tried the Volume Up + Power and let go on splash screen combo but it kept going to stock recovery.
Any help would be appreciated. I'll go crazy having to use the phone without root.
Update: I tried what you mentioned. Manually booting patched boot image. No luck. After showing the MIUI logo for a long time it goes back to recovery. I guess it's basically the same as flashing via TWRP.

shajman said:
Hey let me know if you find a solution for this.
I upgarded to this version via TWRP last night. Tried flashing Magisk via TWRP and it kept boot looping into TWRP.
Had to re-flash the rom again in order to boot into the system.
I tried patching the stock recovery image but couldn't get the system to boot into Magisk mode. Tried the Volume Up + Power and let go on splash screen combo but it kept going to stock recovery.
Any help would be appreciated. I'll go crazy having to use the phone without root.
Click to expand...
Click to collapse
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock firmware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)

zgfg said:
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock formware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
Click to expand...
Click to collapse
This is what I have always done (patching boot). However it does not seem to be working with v12.5.1.0
I've just tried the Canary build of Magisk as well and no luck. The MIUI splash screen stays on for a while and then it goes to Recovery.
This never happened with any of the previous ROMS (Android 10)
Not sure if I'm doing something wrong.

shajman said:
This is what I have always done (patching boot). However it does not seem to be working with v12.5.1.0
I've just tried the Canary build of Magisk as well and no luck. The MIUI splash screen stays on for a while and then it goes to Recovery.
This never happened with any of the previous ROMS (Android 10)
Not sure if I'm doing something wrong.
Click to expand...
Click to collapse
You may have modules installed and enabled, that do no more work with the new firmware
If you didn't wipe/format Data, modules are still in: /data/adb/modules
(updating firmware does not affect there)
Use TWRP, go to that folder and add an empty file named: disable
(exactly as that), to each subfolder (each subfolder corresponds to one module, you may recignize them by folder names)
Then reboot with the patched boot.img
Later, manage your modules (enable, uninstall, update) from Magisk app (once you successfully boot to Magisk)

zgfg said:
You may have modules installed and enabled, that do no more work with the new firmware
If you didn't wipe/format Data, modules are still in: /data/adb/modules
(updating firmware does not affect there)
Use TWRP, go to that folder and add an empty file named: disable
(exactly as that), to each subfolder (each subfolder corresponds to one module, you may recignize them by folder names)
Then reboot with the patched boot.img
Later, manage your modules (enable, uninstall, update) from Magisk app (once you successfully boot to Magisk)
Click to expand...
Click to collapse
You Sir are an absolute LIFE SAVER!!!!!!!
Thank you!

I also patched magisk just fine . Thanks guys for sharing your experiences; it kinda reassured me it'd probably work - I was thinking booting a patched magisk boot.img might be safer so I did that first and it booted as expected. So I just returned to fastboot and flashed it properly. Installed a few modules (the essentials; ACC, Energized, Busybox), rebooted, we're all good ^_^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think it's already been explained above me but for anyone who hasn't figured it out yet:
Find the recovery zip or fastboot files you updated with (if you don't have them still then go here but use the *exact* region and version - if your device isn't raphael then don't use these), open with 7zip/winrar/whatever and copy the boot.img from them to any folder on your phone. Open Magisk Manager, browse for where you copied it to and patch it; recovery mode box unticked. Then look for Magisk_patched_xxx.img (xxx part being whatever Magisk called it) in your /Downloads folder on your phone. Copy it back to your PC, fire up Tiny ADB & Fastboot.
Do a test-run with fastboot boot Magisk_patched_xxx.img first. If it boots up fine and Magisk shows as working, commit the changes by returning to fastboot with adb reboot fastboot and then the command fastboot flash boot Magisk_patched_xxx.img. Then power it up.
If the temporary boot test-run didn't work, obviously don't execute the flash boot command; power-cycling the phone will get it unstuck.
I should probably note I don't have TWRP (using stock recovery) and I don't know how that factors into this. This was done the day after a clean_all fastboot flash; read previous posts if you've used Magisk previously and updated with your data intact.

I would like to add here to use the boot.img patch method. Flashing magisk as a zip through the recovery will cause a bootloop.
Tested this on my Mi 9T Pro (12.5.1 global) with system encryption enabled.

FPSUsername said:
I would like to add here to use the boot.img patch method. Flashing magisk as a zip through the recovery will cause a bootloop.
Tested this on my Mi 9T Pro (12.5.1 global) with system encryption enabled.
Click to expand...
Click to collapse
I was tempted to do the same because it's the conventional way of installing Magisk and it's how it's always been installed.
That and mucking with something called boot.img sounds like a one-way trip to brick-street. I.e. boot.img makes me think bootloader or in other words, bad news. Although from what I've heard it turns out you can completely screw up the boot.img and you should still have access fastboot and recovery modes. But I didn't run into any problems flashing a new boot.img so I didn't find out .

droident said:
I was tempted to do the same because it's the conventional way of installing Magisk and it's how it's always been installed.
That and mucking with something called boot.img sounds like a one-way trip to brick-street. I.e. boot.img makes me think bootloader or in other words, bad news. Although from what I've heard it turns out you can completely screw up the boot.img and you should still have access fastboot and recovery modes. But I didn't run into any problems flashing a new boot.img so I didn't find out .
Click to expand...
Click to collapse
Men, patching the images is nothing new or exotic.
If you ever read Magisk guide from TJW (the aurhor of Magisk) you would well know that the method has been described there for many years (I personally used the method back since 2018 on other phones)
Besides, it has many practical advantages - if anything goes wrong you just flash the original (unpatched) image
Or, when Magisk updates (unfortunately, it does no more and who knows would it ever again, at least from the established channels like Stable or Canary), if there is a problem with the new Magisk - you just flash your previous version of img that was patched with the working version of Magisk and you are back in business
And there is also nothing impractical here - if you have proper TWRP (you do have for this phone) you don't need to flash the patched img from fastboot but simply from TWRP
You can also use TWRP backup boot.emmc.win instead of extracted boot.img - simply give boot.emmc.win to Magisk for patching (you don't need to rename it) and then flash it

So, guys, did the patched boot image worked for you? for me it did not boot up... :/

HValenti said:
So, guys, did the patched boot image worked for you? for me it did not boot up... :/
Click to expand...
Click to collapse
Of course it does work. But read carefully above. If you just upgraded without Factory reset, and if you had Magisk before, some modules (that remained installed to /data) may cause you the bootloop
And/or, you have to patch exactly the boot.img corresponding to your current firmware, not some from an older A10, etc

In such case, how do you remove the magisk modules after the update? Without root, there is no access to modules.

HValenti said:
In such case, how do you remove the magisk modules after the update? Without root, there is no access to modules.
Click to expand...
Click to collapse
Why don't you read the previous messages in this thread - post #6
Or see:
zgfg said:
Yes, it was asked/answered several times but let it be answered again
Besides adb, there are two other ways of disabling (or even uninstalling) the remained modules
You have to flash your patched boot.img, then
a) Reboott to Android Safe mode, then reboot again to 'normal' mode.
All modules will be disabled but also you will have to re-enable Magisk Hide again
b) Use TWRP (if appropriate for your device), Advanced, File Manager, go to /data/adb/modules and to each folder (foder = module, you can recognize modules by folder names or by reading the textual file module.prop you will find inside) put a file that must be named: disable (exactly as that)
Click to expand...
Click to collapse
Or simoly read the Magisk Wiki, available from Magisk Github (linked from Magisk app):
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com

zgfg said:
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock firmware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
Click to expand...
Click to collapse
My Ramdisk says "no" should I still patch boot.img?
not sure how to delete. It does work

Vanmanman said:
My Ramdisk says "no" should I still patch boot.img?
not sure how to delete. It does work
Click to expand...
Click to collapse
It says for everybode on MUII No for Ramdisk but it was discussed snd written everywhere and zillion times that Xiaomi users have to patch boot img

Can I somehow extract boot.img from phone without custom recovery and root?

Rejerf said:
Can I somehow extract boot.img from phone without custom recovery and root?
Click to expand...
Click to collapse
Download the full OTA for your phone, and from it, you can extract the boot.img.
Link for the OTA download and instructions on how to do it is provided here: https://forum.xda-developers.com/t/...-5-1-0-edit-yes-it-does.4299669/post-85271375

Please does someone upgraded succefully from 12.0.5.0 to 12.5.1.0 with root and without wiping data ?
If yes, how did you flashed the 12.5 ROM because TWRP recovery does no support MIUI 12.5 A11 encryption, so I guess flashing it from TWRP is not recomanded.
I am quite afraid to be forced to wipe everything and preserve root is mandatory for me so I did not tried to upgrade for now.
Thank you in advance.

Question Problems to root cn version 13.0.5 android 12

Hi, i'm trying to root my CN version 13.0.5 without the twrp, I'm using the magisk to patch the boot file, but after patch and use the command "fastboot flash boot boot.img, the mi 11 ultra just stuck in the mi logo. I'm not been able to root my phone, right now, how to root the CN version 13.0.5?
i did the same root with the android 11 and worked, something change?

hi, did you install magisk canary and not magisk stable?
I have just Root Xiaomi.eu A12 Miui13 with the same method and it work.

Hi. FIrst - better to use Magisk 23.0 - as you will still have Magisk hide. But more important - just the "fastboot boot boot.img" command instead. Once you have booted without issues you can go into Magisk and patch the real boot image file from there and restart. This is how it always worked for me. Not really sure what is the big difference there but as I said - that worked for me.

When you are running the miui 13, copy the boot.img from fastboot folder to your phone(remember the location). Open magisk app, choose install and search for boot.img on your phone. After patching is done, copy the patched file into your fastboot folder on pc. Boot into fastboot, type fastboot flash boot (and drag the patched file from fastboot folder here) and hit enter. after flashing fastboot reboot

Thanks for the help, i'll try to patchin a few hours and back here to give the feedback!

marcel112 said:
When you are running the miui 13, copy the boot.img from fastboot folder to your phone(remember the location). Open magisk app, choose install and search for boot.img on your phone. After patching is done, copy the patched file into your fastboot folder on pc. Boot into fastboot, type fastboot boot (and drag the patched file from fastboot folder here) and hit enter. after flashing fastboot reboot
Click to expand...
Click to collapse
Does that Format my Data? And how do i remove the Patch(remove magisk)?

Afg Playa said:
Does that Format my Data? And how do i remove the Patch(remove magisk)?
Click to expand...
Click to collapse
It does not format. That's just for root. You can flash the rom in fastboot again or flash the boot.img again from the folder images

thiagoserrao said:
Thanks for the help, i'll try to patchin a few hours and back here to give the feedback!
Click to expand...
Click to collapse
Did IT Work?

Afg Playa said:
Did IT Work?
Click to expand...
Click to collapse
Using CN no, i tried with the rom downloaded but didn't worked. So i take a step and installed the EU version, not been able to connect to android auto and other stuffs was killing me!
After install the EU version, i just did the same steps to root the boot, and worked without problem

thiagoserrao said:
Using CN no, i tried with the rom downloaded but didn't worked. So i take a step and installed the EU version, not been able to connect to android auto and other stuffs was killing me!
After install the EU version, i just did the same steps to root the boot, and worked without problem
Click to expand...
Click to collapse
Great, It also worked for me Xiaomi.eu 13.0.9.0.

I have difficulties too rooting my Mi 11 Ultra with Android 12. I have installed the latest canary of Magisk and when I patch the boot.img and flash it the device stucks on Android logo. When I boot the device with fastboot boot magisk_patched***.img I'll get a black screen.
Can anybody post a patched boot.img from Xiaomi.eu 13.0.9.0 Rom? Perhaps it works when I flash this one on my device.

User1977 said:
I have difficulties too rooting my Mi 11 Ultra with Android 12. I have installed the latest canary of Magisk and when I patch the boot.img and flash it the device stucks on Android logo. When I boot the device with fastboot boot magisk_patched***.img I'll get a black screen.
Can anybody post a patched boot.img from Xiaomi.eu 13.0.9.0 Rom? Perhaps it works when I flash this one on my device.
Click to expand...
Click to collapse
i just lost my root without reason, i just restarted my phone, than no root anymore and not being able to installing again ;D. what a hell

Start from the beginning by flashing unpatched boot.img and use Magisk v23. V24 has nothing but problems. I was frustrated for a few hours with it and going back to v23 solved everything.

How To Guide [GUIDE] how to flash android 12-13 based gsi without bootloops

i have decided to post my personal procedure for flashing android 12 and android 13 gsi
all gsi that i will mention booted succesfull on my device (code M2103K19G)
i dont assume any responsability for possible bootloops. the procedure is 100%, if you follow will not have any problem
pre requisites:
bootloader unlocked
STOCK global miui13 installed. latest global is my favorite, but also other version works (no miui12, gsi could boot anyway, but maybe not)
magisk installed for testing the gsi before definitive flash (suggested but not necessary)
a pc with adb and fastboot installed + mtk driver
first step: choose your favorite gsi
my suggestions are: Spark a13.1 (my actual rom), crdroid 12.1 based, arrow 12.1 based, latest pphusson
download the gsi and test it via dsusideloader (you can try all gsi that you want). this is very important for verify have all what you need
in alternative read changelog of gsi or users feedback. the gsi that i have mentioned 100% boot guaranted
when you have chose the gsi wipe data and reboot phone to FASTBOOTD (i will not explain how to do, a modder must know this)
if you boot into fastboot cant flash system
download and extract fastboot stock rom
after this simply:
open image folder of your fastboot extracted rom
open a terminal (for linux user) or a cmd window (con win10 users)
flash vbmeta disabling dm-verity check typing: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
flash system.img (DONT ERASE SYSTEM PARTION!) typing: fastboot flash system system.img
flash stock kboot.img (or magisk patched for have root) typing; fastboot flash boot boot.img
reboot typing: fastboot reboot
no other commands needs, i'm 100% sure. tested directly by me
if you have made all steps correctly, and you have choosed and tested a good no wipe data is need and phone 100% boot
obviously, before flash gsi is important read the changelog of the rom for know bugs, function missing, fuction added, battery backup, performance, ecc ecc
for info about all gsi connect to official telegram channels
my favorites are pphusson channel and naz channel (the developer of my actual rom)
good look and dont ask me info about gsi. Ask directly to official telegran channel
READ WITH ATTENTION: this procedure is what i do every time i want to flash a gsi. i never encontered any bootloop, expect when a made wrong
thing like boot from slot b, flash a wrong boot.img image, flash a magisk module that is not compatible. so i dont will assume any responsability for damages to your device. it means that the problem isn't my procedure

PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help

this is the GSI img file that nned to flashed am i correct?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
fastboot flash system system.img
Click to expand...
Click to collapse

GrandEsquiRE said:
this is the GSI img file that nned to flashed am i correct?
Click to expand...
Click to collapse
No. Download suggestions unless you know how to solve bootloop.

up864 said:
No. Download suggestions unless you know how to solve bootloop.
Click to expand...
Click to collapse
Nvm, i'm already on corvus rn

viktak said:
I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
Click to expand...
Click to collapse
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file

GrandEsquiRE said:
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file
Click to expand...
Click to collapse
with dsu sideloader u can test gsi directly from xz file, no extraction is needed. is explained into the app

Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
Andyan will tell you
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
search if its BvN then its vanilla(no gapps) if BgN it has gapps

downlod arm64 bgN g=with gapps v=vanilla (no gapps)
slim version is no suggested for the gsi i have mentioned and tested
arm64= a/b device (like our)
a64= device with no dunamic partitions
i hope my guide could be helpfull to prevent a lot of possible bootloops
(also if my english is not perct, I tried to make it as easy and understandable as I could)

wetito said:
PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help
Click to expand...
Click to collapse
What rom is that? Can you give me the download link, and does fingerprint and 5g work?

This guide worked, thank you so much!

*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,

mg1122tt said:
*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,
Click to expand...
Click to collapse
thats exactly what I did. but no matter the branch/distro these new androids are so damn ugly chasing after ios and they're gettting uglier and bigger every update. .
I was mainly interested in newest GSI because of mKVM but didjt realise at the time that only two phones in the world c8rrehtlly posses requirements for it. Windows FTW!

Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
At what stage of the process? After what step?
In general, there is no time when you have to force reboot it. You can do the whole process using adb/fastboot commands as described in the OP.

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
install magisk fix for this issue, sometimes appear. u can find the guide in this forum section. the thread is gsi brightness fix