Develop Bugs

[ROOT] [MAGISK] How to root

Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.

Thanks so much! Will try this out! Nice work!

Thanks, after i root my mix 3 can i flash the xiaomi.eu rom on it too without problems ?

Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.

PJF16 said:
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
Click to expand...
Click to collapse
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.

Please report back your success and how it goes for you!

SacredSovL said:
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Click to expand...
Click to collapse
It's risky and something I won't be trying, I would wait for TWRP

Hi PJF16
How did you get the boot.img from your device without root? I'd love to make a unmodified copy before trying this out

I got it from the fastboot ROM which I also uploaded to the forum. See here: https://forum.xda-developers.com/mi-mix-3/development/xiaomi-mi-mix-3-fastboot-roms-t3869532

Tested and 100% working! Recommended

smiba said:
Tested and 100% working! Recommended
Click to expand...
Click to collapse
Did u flash xiaomi.eu rom or something else ?

PJF16 said:
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Click to expand...
Click to collapse
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to

souless poet said:
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
Click to expand...
Click to collapse
Nevermind figured it out...duh.

Not working on 8.11.15 dev china rom...
Patched boot is much smaller than it should be and after flashing and fastboot reboot command, phone goes back to fastboot mode

It's normal that the patched boot.img is smaller.

PJF16 said:
It's normal that the patched boot.img is smaller.
Click to expand...
Click to collapse
I know that.
But this is quite smaller than usual and, anyway, it doesn't boot after flashing

Anyone have any issues with v4A magisk module? After I flashed it I lost the ability to turn on wifi. Wondering if anyone else has had that issue.

where can i find the pre patched boot img of 10.0.12.0?

Just use the one for 10.0.11.0.

nosidefcp said:
where can i find the pre patched boot img of 10.0.12.0?
Click to expand...
Click to collapse
Hi, here You can find patched boot for 10.0.12.0:
https://yadi.sk/d/aVlSEC_r7xj0VA

[Recovery][Stock OOS 10.0.3BA]Oxygen OS Stock recovery with ADB enabled

While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery from the 10.0.1BA package but with ADB enabled.
Prerequisites:
Oneplus 7T Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery
(when taking the file as downloaded the filename is "OP7TP_StockRecovery_ADB_nosec.img")
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Downloads:
10.0.3BA Recovery
Modified 10.0.3BA recovery from GDrive
Original 10.0.3BA stock recovery from Gdrive
10.0.4BA Recovery
Modified 10.0.4BA recovery from GDrive
Original 10.0.4BA stock recovery from Gdrive
10.0.7BA Recovery
Modified 10.0.7BA recovery from GDrive
Original 10.0.7BA stock recovery from Gdrive
Open Beta 1 Recovery
Modified OB1 recovery from GDrive
Open Beta 2 Recovery
Modified OB2 recovery from GDrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.

I just need it, thank you very much.

But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.
Only the boot_a and boot_b that have not been modified by magisk are brushed in and the password is entered again after booting and re-entering rec, and the data can be modified.
但是这个rec有个BUG
刷入并进入REC后 界面不需要输入密码,并且adb shell打开/data是空的
只有刷入没有被magisk修改过的boot_a和boot_b并且开机后重新进入rec才有输入密码的界面,并且data可以修改

991547436 said:
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.
Only the boot_a and boot_b that have not been modified by magisk are brushed in and the password is entered again after booting and re-entering rec, and the data can be modified.
但是这个rec有个BUG
刷入并进入REC后 界面不需要输入密码,并且adb shell打开/data是空的
只有刷入没有被magisk修改过的boot_a和boot_b并且开机后重新进入rec才有输入密码的界面,并且data可以修改
Click to expand...
Click to collapse
English only pls?
OnePlus 7T Pro

s3axel said:
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery from the 10.0.1BA package but with ADB enabled.
Prerequisites:
Oneplus 7T Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery <recovery_filename.img>
(when taking the file as downloaded the filename is "OP7TP_StockRecovery_ADB_nosec.img")
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Downloads: (all based on 10.0.3BA image from Oneplus)
Modified recovery from GDrive
Original stock recovery from Gdrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
Click to expand...
Click to collapse
HolyChickenGuy said:
English only pls?
OnePlus 7T Pro
Click to expand...
Click to collapse
English is a translation. I don't know if the translation is correct.

991547436 said:
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.QUOTE]
I noticed the same behaviour when trying "fastboot boot", the recovery needs to be flashed to work.
Second I own an EU device with BA firmware/OS on it, maybe global devices with AA firmware are different...
Click to expand...
Click to collapse

Theres no flashable zip rom for twrp? Thanks
Enviado desde mi MI MAX 3 mediante Tapatalk

jorgeepelos said:
Theres no flashable zip rom for twrp? Thanks
Enviado desde mi MI MAX 3 mediante Tapatalk
Click to expand...
Click to collapse
TWRP doesn't even work for this device, and with devices launched Android 10 you can no longer flash system via TWRP.
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
TWRP doesn't even work for this device, and with devices launched Android 10 you can no longer flash system via TWRP.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Ok thanks!!!
Enviado desde mi MI MAX 3 mediante Tapatalk

Thank you very much for this recovery.
Just needed it after trying to install Viper4Android and only going to fastboot screen.
Cheers

Same as the user above, had problems with Viper. Used this and removed the modules, and now it boots. Thanks!

This has caused my device to bootloop to recovery. Flashing stock recovery doesn't fix this problem.
Doing fastboot boot boot.img starts my rom, but every time I reboot (via fastboot, adb or normally from rom) it goes back to recovery. I am running 10.0.3.HD01BA and don't have any ideas how to recover from this.
Any help would be appreciated, I am truly a novice in this scene.

Az4z3l11 said:
This has caused my device to bootloop to recovery. Flashing stock recovery doesn't fix this problem.
Doing fastboot boot boot.img starts my rom, but every time I reboot (via fastboot, adb or normally from rom) it goes back to recovery. I am running 10.0.3.HD01BA and don't have any ideas how to recover from this.
Any help would be appreciated, I am truly a novice in this scene.
Click to expand...
Click to collapse
Did you install any modules?
OnePlus 7T Pro

Az4z3l11 said:
This has caused my device to bootloop to recovery. Flashing stock recovery doesn't fix this problem.
Doing fastboot boot boot.img starts my rom, but every time I reboot (via fastboot, adb or normally from rom) it goes back to recovery. I am running 10.0.3.HD01BA and don't have any ideas how to recover from this.
Any help would be appreciated, I am truly a novice in this scene.
Click to expand...
Click to collapse
Just a thought: could it be that you flashed this recovery with "Fastboot flash boot <filename.img> ? This would explain that when booting not the original boot image but recovery comes up.
From your message I take that you have the original boot image at hand, you could try flashing it with "fastboot flash boot boot.img"
The recovery image in this thread is flashed with "fastboot flash recovery <filename.img>...
Hth, cheers,
Axel
Gesendet von meinem HD1913 mit Tapatalk

HolyChickenGuy said:
Did you install any modules?
OnePlus 7T Pro
Click to expand...
Click to collapse
Only one that came with my Swift Installer.
s3axel said:
Just a thought: could it be that you flashed this recovery with "Fastboot flash boot <filename.img> ? This would explain that when booting not the original boot image but recovery comes up.
From your message I take that you have the original boot image at hand, you could try flashing it with "fastboot flash boot boot.img"
The recovery image in this thread is flashed with "fastboot flash recovery <filename.img>...
Hth, cheers,
Axel
Gesendet von meinem HD1913 mit Tapatalk
Click to expand...
Click to collapse
Negative, I have the command prompt window still open, and was extra careful to flash the recovery with recovery, not boot.
The image I have is a patched boot image from another xda thread. I am scared that flashing that would brick my device.
EDIT: Is there a way to extract my original boot.img and then try to flash it?
EDIT2: Extracted my boot.img from /data folder in stock_boot_xxxxxxxxxxx.img.gz. I will try to flash it once I have backed everything up.
EDIT 3: Tried flashing original boot.img and re-rooting phone with magisk, and no luck. The solution was too obvious though. I didn't realize that my phone had encryption on and the password was my lockscreen PIN code. After decrypting the recovery the phone boots normally and the adb recovery works perfectly.
Thanks for the support, it seems that tinkering with your phone is way harder than I remember it from back in the days; hopefully TWRP will fix this, once it supports Android 10.
Thank you very much for the recovery!

Is there a recovery like this for the regular 7t?

Just curious, do you have a guide on how to this yourself?
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
Just curious, do you have a guide on how to this yourself?
Click to expand...
Click to collapse
It's actually pretty easy and this would most probably also work for the 7T...
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash

HolyChickenGuy said:
English only pls?
OnePlus 7T Pro
Click to expand...
Click to collapse
991547436 said:
English is a translation. I don't know if the translation is correct.
Click to expand...
Click to collapse
Moderator Announcement:
The way you did is very fine and exemplary!
*********
您的做法非常好，堪称典范！
XDA Forum Rules (excerpt):
...
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
...
Click to expand...
Click to collapse

991547436 said:
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.
Only the boot_a and boot_b that have not been modified by magisk are brushed in and the password is entered again after booting and re-entering rec, and the data can be modified.
Click to expand...
Click to collapse
I was in a bootloop, because of the GCam aux Magisk module. For me it was the same at first attempt. I installed with
Code:
fastboot flash recovery OP7TP_StockRecovery_ADB_nosec.img
After that I rebooted to recovery. I also did not get a password prompt. I connected with
Code:
adb shell
but /data was empty. Because I wanted to see if my system still works without Magisk, I booted with the unmodified boot.img by using
Code:
fastboot boot boot.img
System came up without Magisk and was usable. After that I rebooted and it got stuck at fastboot screen again. I tried one more time to select recovery from fastboot screen and it asked me for password. Since I don't have encryption I just tried to connect again with
Code:
adb shell
This time /data was properly mounted and I was able to delete the Magisk module. After that I rebooted to system with
Code:
adb reboot
and now I have my fully functional system back. I don't know why it didn't work in the first attempt but this is awesome.
 @s3axel you made my day! Thank you very much!!! Your work is appreciated!

[ROOT/MAGISK] OOS 10.0.12 Magisk patched_boot.img

For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.12 HD65AA (GLOBAL)
Only for OOS 10.0.12 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
When finished type
Code:
fastboot reboot
patched boot.img download: https://drive.google.com/file/d/1JeNPnEtKKkXYBVlo4pW0VUEnP1BQ7nt_/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1rrUcVyTBUl-sED35lxuK82UQ0hHM_PRg/view?usp=sharing

I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version
Tapatalk via OnePlus 7T

Thank You

I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.

ba47 said:
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
Click to expand...
Click to collapse
If u r already on 10.0.12 EU u dont need the rom
If u r on previous OOS then use the oxygen updater app from Play store to update

ba47 said:
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
Click to expand...
Click to collapse
One guy already upload this file here :
https://drive.google.com/file/d/1-_3fL5HkWS9cplro7iNiIzqlL_AGTz2B/view?usp=drivesdk
Tapatalk via OnePlus 7T

Hm, I have HD65AA India and after boot (not flash) via fastboot attached here patched boot.img I don't have internet (gsm and wifi).
Do you have India's version of that patch ?

KyoshiDev said:
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
Click to expand...
Click to collapse
4. and 5. Step isn't needed.
When you boot your image and check if you have root you just klick: Install --> Install --> direct install. It will automatically patch your actual boot.img and you will permanently have a rooted phone.

I didn't find patched boot.img to 10.0.12/10.3.4 India (!) version, so I created my own (faq linked above).
It works on my device like a charm. I have already gsm internet and WiFi and of course rooted device.
If someone wants to try on 10.3.4/10.0.12 AA (Global and only India version) , I put my patched boot.img here:
https://drive.google.com/file/d/1p6tgyc_WcLl2CW4ysq4xGgFXnmO95Kl0/view?usp=sharing

Did not work for me on reboot after root check says not rooted?
---------- Post added at 06:54 PM ---------- Previous post was at 06:44 PM ----------
Nope did not work for me say I do not have root on root check?

=dgim= said:
I didn't find patched boot.img to 10.0.12/10.3.4 India (!) version, so I created my own (faq linked above).
It works on my device like a charm. I have already gsm internet and WiFi and of course rooted device.
If someone wants to try on 10.3.4/10.0.12 AA (Global and only India version) , I put my patched boot.img here:
https://drive.google.com/file/d/1p6tgyc_WcLl2CW4ysq4xGgFXnmO95Kl0/view?usp=sharing
Click to expand...
Click to collapse
I have updated to 10.3.4.HD65AA yesterday. Have been rooted since much earlier version with Magisk Canary. Now I want to change to stable but not sure of the process.
How do I uninstall Canary version? There does not seem to be any uninstall option in Magisk Manager Canary version. Can I just uninstall as I would any other app?
Is the file you uploaded correct for my version? Would it install Magisk Stable version?
After going into fastboot do I have to connect to PC and give commands there or in the phone itself. Have done it earlier but I forgot. If from PC, which software to use for ADB?
Edit : Will this wipe data?

You can use via TWRP, I suppose (not tested) this Magisk's unistall zip file: https://github.com/topjohnwu/magisk_files/tree/canary
If you flashed a new rom (10.3.4) I believe that you have already stock boot.img, so device is unrooted.
If yes, you can - first, only booted my patched_boot.img to see that everything is OK (gsm, wifi, magisk manager works etc),
and, then, try flash it via fastboot.
I patched my stock boot.img (10.3.4 India version) via latest Magisk Canary.
Here is FAQ:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307

=dgim= said:
You can use via TWRP, I suppose (not tested) this Magisk's unistall zip file: https://github.com/topjohnwu/magisk_files/tree/canary
If you flashed a new rom (10.3.4) I believe that you have already stock boot.img, so device is unrooted.
If yes, you can - first, only booted my patched_boot.img to see that everything is OK (gsm, wifi, magisk manager works etc),
and, then, try flash it via fastboot.
I patched my stock boot.img (10.3.4 India version) via latest Magisk Canary.
Here is FAQ:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Click to expand...
Click to collapse
I think TWRP is not working for OnePlus7T so not sure about that.
I have updated from rooted 10.3.2 to 10.3.4 via OTP and I already have Magisk Canary. So I am rooted. I want to remove this and get to Magisk Stable version.

jesrani said:
I think TWRP is not working for OnePlus7T so not sure about that.
I have updated from rooted 10.3.2 to 10.3.4 via OTP and I already have Magisk Canary. So I am rooted. I want to remove this and get to Magisk Stable version.
Click to expand...
Click to collapse
Booting and flashing TWRP on recovery partition, I suppose, is working.
I didn't flash Magisk install or unistall via TWRP on OP7T.
Are you sure that, after flashing new rom, your device is rooted ?
Even you have installed Magisk Canary, but - SatetyNet etc, is passed in your device after flashed stock 10.3.4 ?
If not, you can just unistall apk (Magisk Manager), clear cache, flash patched boot.img and install stable Magisk (I didn't test stable on 10.3.4).

I'm lost somehow.
I'm rooted, Global (USA) phone. Last version is 10.0.11.
First, to which directory do I download the patched .img file. To my phone, to my computer? So far I have put in both Magisk directory and my root directory.
I reboot the bootloader. Fine. I fastboot the patched image. Fine. Check for root. Fine
I reboot the bootloader. Fine. Comes up with a menu. The top of the menu says Start.
Then I type fastboot flash boot magisk_patched_10_0_12.img. And nothing happens. I have tried the power button and nothing either. I tried going into Magisk and install as another forum member suggested, but now my phone comes up, still hasn't upgraded to 12. Also now when I click any app the phone it just reboots itself. So I'm really messed up.
My question is what was suppose to happen when i clicked fastboot flash boot magisk_patched_10_0_12.img with the bootloader menu on my screen and where was the .img file suppose to be located. Am I doing this right from my PC (Win10 - PowerShell).
I'm lost because I have been upgrading previously and have had no trouble. Where did I go wrong. Much thanks.
KyoshiDev said:
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.12 HD65AA (GLOBAL)
Only for OOS 10.0.12 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
patched boot.img download: https://drive.google.com/file/d/1JeNPnEtKKkXYBVlo4pW0VUEnP1BQ7nt_/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1rrUcVyTBUl-sED35lxuK82UQ0hHM_PRg/view?usp=sharing
Click to expand...
Click to collapse

davekaye said:
I'm rooted, Global (USA) phone. Last version is 10.0.11.
First, to which directory do I download the patched .img file. To my phone, to my computer? So far I have put in both Magisk directory and my root directory. .
Click to expand...
Click to collapse
to your computer, or rather, to the directory where your adb and fastboot files are, or if you have adb installed system widely, you should put your img in the folder where you are running your cmd window or you can navigate with cmd to the file with "cd"
davekaye said:
Then I type fastboot flash boot magisk_patched_10_0_12.img. And nothing happens. I have tried the power button and nothing either. I tried going into Magisk and install as another forum member suggested, but now my phone comes up, still hasn't upgraded to 12. Also now when I click any app the phone it just reboots itself. So I'm really messed up.
Click to expand...
Click to collapse
What do you mean with "still hasn't upgraded to 12"? You mean OOS 10.0.12? Then you need to update from 10.0.11 to 10.0.12 before rooting your boot partition with a boot.img from an OOS 10.0.12
davekaye said:
My question is what was suppose to happen when i clicked fastboot flash boot magisk_patched_10_0_12.img with the bootloader menu on my screen and where was the .img file suppose to be located. Am I doing this right from my PC (Win10 - PowerShell).
I'm lost because I have been upgrading previously and have had no trouble. Where did I go wrong. Much thanks.
Click to expand...
Click to collapse
nothing should happen to your bootloader screen, but you should see in your cmd window, that the flashing finished, then you can type "fastboot reboot" to reboot your phone.

KyoshiDev said:
to your computer, or rather, to the directory where your adb and fastboot files are, or if you have adb installed system widely, you should put your img in the folder where you are running your cmd window or you can navigate with cmd to the file with "cd"
What do you mean with "still hasn't upgraded to 12"? You mean OOS 10.0.12? Then you need to update from 10.0.11 to 10.0.12 before rooting your boot partition with a boot.img from an OOS 10.0.12
nothing should happen to your bootloader screen, but you should see in your cmd window, that the flashing finished, then you can type "fastboot reboot" to reboot your phone.
Click to expand...
Click to collapse
Thanks. My fault. Since I don't have a working TWRP I haven't been playing around with any ROMs and I guess I'm rusty. So I tried to put your upgrades on the wrong version of Oxygen (11 not 12) and ran into a bootloop. I could not boot into EDL mode (another issue I have to follow up) and it took me some time to finally boot back to 11 and then do the OTA upgrade to 12. All is working now, so thanks again.

Hello, is SafetyNet supposed to fail or I've messed something up?

1nikolas said:
Hello, is SafetyNet supposed to fail or I've messed something up?
Click to expand...
Click to collapse
Safetynet should pass

So i put this on my US version. HD1905. I should have been more careful. Anyway, everything works well except netflix., which is now a system app and will not run or uninstall.
PS: Do you have US version patched boot file ?

Android 11 / DP3: Steps to get rooted properly

Here you will get the correct steps, files and info to get rooted on Android 11 / DP3 build.
Boot file:
DP3_patched
Canary Manager:
Magisk Manager Canary
1. Download the files above
2. Put the Boot file into downloads directory
3. Install the Canary Manager
4. In the Manager do the following: select "Install" / "Select and patch a file" / Pick the Boot file in Downloads
5. When done take the newly created magisk_patched.img file from Downloads and copy to the ADB/Fastboot directory on your PC
6. Go to fastboot on your device
7. Use the command fastboot boot magisk_patched.img from your PC from ADB
8. Once the device reboots go back to fastboot mode
9. This time use the command fastboot flash boot_a magisk_patched.img
10. Then use this straight after fastboot flash boot_b magisk_patched.img
11. Reboot device and enjoy being rooted
This method should work first time in getting you rooted. Many other ways were tested and worked randomly for some and not others but with this I got it first time on two test attempts.
Hope it works for you all.
Thanks to @mwilky, @osm0sis and @Mike02z for figuring it out properly :good:

All credit to @osm0sis for the initial heads up!

Gpay is working with the root and magisk? Without doesnt works. Thanks

Great news!
Sent from my IN2025 using Tapatalk

vuoshino said:
Gpay is working with the root and magisk? Without doesnt works. Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8-pro/how-to/android-11-beta-t4113817/post83290875

after step 7, my phone restarts and I get Qualcom CrashDump Mode Attemped to kill init
what now?
i restarted phone with keys..
can i proceed with step 8?

I got root working, but my alert slider doesn't work and fails safety net.
Sent from my IN2025 using Tapatalk

enerGy said:
Here you will get the correct steps, files and info to get rooted on Android 11 / DP3 build.
Boot file:
Boot img
Canary Manager:
Canary Magisk Manager
1. Download the files above
2. Put the Boot file into downloads directory
3. Install the Canary Manager
4. In the Manager do the following: select "Install" / "Select and patch a file" / Pick the Boot file in Downloads
5. When done take the magisk_patched.img file created from Downloads and copy to the ADB/Fastboot directory on your PC
6. Go to fastboot on your device
7. Use the command fastboot boot magisk_patched.img from your PC from ADB
8. Once the device reboots go back to fastboot mode
9. This time use the command fastboot flash boot_a magisk_patched.img
10. Then use this straight after fastboot flash boot_b magisk_patched.img
11. Reboot device and enjoy being rooted
This method should work first time in getting you rooted. Many other ways were tested and worked randomly for some and not others but with this I got it first time on two test attempts.
Hope it works for you all.
Thanks to @mwilky, @osm0sis and @Mike02z for figuring it out properly :good:
Click to expand...
Click to collapse
im onrooted, for do this guide i have to open the bootloader or do something else at the beginning? because when i try to launch the command fastboot boot magisk..... the cmd give me this error: download is not allowed on locked devices... thanks
---------- Post added at 03:43 PM ---------- Previous post was at 03:10 PM ----------
vuoshino said:
im onrooted, for do this guide i have to open the bootloader or do something else at the beginning? because when i try to launch the command fastboot boot magisk..... the cmd give me this error: download is not allowed on locked devices... thanks
Click to expand...
Click to collapse
ok yes was for the locked bootloader. now works properly. thanks

Hi, could anyone send me a dmesg log with the patched boot? You can grab it through either adb root or terminal emulator. I need it as a reference to debug for another device. Thanks!

I cant make safety net to works properly...
Someone can help me?
---------- Post added at 05:03 PM ---------- Previous post was at 04:50 PM ----------
Basicintegrity not pass
Cts profile not pass
Evaltype basic...

This is the error

Now is working. Thanks

I had problems with hiding Magisk (repacking and change name of the Magisk Manager)
In my case it was Google Play Protect that refused me this, so temporarily disabling this worked for me! In case anyone else should stumble upon this issue!
Great guide!

is this method works with magisk manager not canary?

Does not work with the Oneplus pro in2025 keep getting carshdump Mode. Fastboot flashed the new.img so rom can boot. Now when I check magisk it shows I am rooted. So I guess it does work

Not work with magisk. But works fine with canary.
Now I am not eable to use 5g configuration can not be setted.
I am not eable to use the methods and apks
Like OnePlus logkit and engineermode.
These are not working with oos 11.
Is there any ways to enable the 5G connectivity.
Thanks

Spirit81 said:
after step 7, my phone restarts and I get Qualcom CrashDump Mode Attemped to kill init
what now?
i restarted phone with keys..
can i proceed with step 8?
Click to expand...
Click to collapse
I had the same issue of boot to crashdump mode every time I tried to boot the magisk_patched.img that I created using Magisk Manager as well. So, I ended up trying to boot the new.img (the one downloaded from OP) and it booted and was already rooted in Magisk Manager. So from there, booted back to fastboot and flashed the new.img to both boot_a and boot_b and now have root on DP3. Hope that helps.

jeffsga88 said:
I had the same issue of boot to crashdump mode every time I tried to boot the magisk_patched.img that I created using Magisk Manager as well. So, I ended up trying to boot the new.img (the one downloaded from OP) and it booted and was already rooted in Magisk Manager. So from there, booted back to fastboot and flashed the new.img to both boot_a and boot_b and now have root on DP3. Hope that helps.
Click to expand...
Click to collapse
Same for me,with the new img it works
Gesendet von meinem IN2023 mit Tapatalk

vuoshino said:
This is the error
Click to expand...
Click to collapse
How have you solved it?

Upgrade magisk, in the settings turn on the hide option and install magisk with another name. Go into the magisk hide and check google services. Anyway next to turn on magiskhide option google pay will works.
---------- Post added at 06:05 PM ---------- Previous post was at 05:47 PM ----------
Someone use skygo? Is strange, my magisk app is hide and google pay works but sky go is able to see the root. Is alreafy checked in the magiskhide options but i think there is an error with the hide options because magisk doesnt create a new icon. I have the same icon of the original magisk and the option in the settings is the same one: hide magisk manager app...

Rooting 7T without TWRP / Pre-patched Magisk boot.img for 10.0.13.HD65AA (Global)

For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.

I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?

>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.

This will delete all the data from the phone + bootloader needs to be unlocked?

Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).

GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!

Will this work for 10.0.13 tmobile ? Thanks

gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.

GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.