Develop Bugs

[x Force] Installing Magisk Root & Universal Systemless Interface

Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Code:
adb reboot fastboot
Temporarily boot into into TWRP
Code:
fastboot boot C:\twrp-3.0.2-0-clark.img
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased

JimyKK said:
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Temporarily boot into into TWRP
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
Click to expand...
Click to collapse
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.

sam00561 said:
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
Click to expand...
Click to collapse
Maybe™
My banking app uses google's inbuilt SafteyNet library to detect root and from my understanding that is also how android pay works as well. Magisk's hide function seams to bypass this detection even though on the main screen of Magisk management app the SafetyNet check fails.

For this procedure is necesary unlock the bootloader?

Cameronbrujah said:
For this procedure is necesary unlock the bootloader?
Click to expand...
Click to collapse
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.

Yemble said:
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Click to expand...
Click to collapse
Thanks a lot for your prompt response!!!
I'll do it.

Cameronbrujah said:
Thanks a lot for your prompt response!!!
I'll do it.
Click to expand...
Click to collapse
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.

Yemble said:
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Click to expand...
Click to collapse
actually I have Nougat 7.0 Official and only for the moment I will to root the phone. In a near future, of course I will change the ROM to the CrashXXL
Thanks a lot for all your help.
Regards from Mexico!

And how are we gonna unlock the bootloader?
Is there a way to do that?

Root, change api and will we still get updates?

I am planning to root and use api2 for gcam. Will I receive updates after that? Also would those updates install successfully if rooted? If not any idea on how to just get api2. Can I UNROOT the device and will that install updates successfully?

No.
The thing you can do is that you install September ROM with MiFlash, then you get update. (You can install September ROM without loosing data.)
At the moment there is no way to keep root after update using current tools.

You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.

Ex-Hunter said:
[*]Download the latest Magisk Manager and install. DO NOT update Magisk.
Click to expand...
Click to collapse
Hi, i have some mistake at this point, if i try to install newer magisk manager i cant because "i have another app with the same name", so what? using magisk 13.3 with the manager 5.1.1 provided by itself to active the cameras module? thanks

---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
[/COLOR]
Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
-----------------------------------------------------------------------------------------------------------------------
just a question: it's possible to edit build.prop via adb with twrp "live" without installing it?!
in this case, I could just edit it to enable camera2 api without rooting or installing twrp..
Click to expand...
Click to collapse

How to enable Camera2api after rooting with magisk? Please inform
n6i5k7h5 said:
I am planning to root and use api2 for gcam. Will I receive updates after that? Also would those updates install successfully if rooted? If not any idea on how to just get api2. Can I UNROOT the device and will that install updates successfully?
Click to expand...
Click to collapse
I just got a MiA1.I know how to root it with magisk but don't know how to enable camera2api.Will you please help me?

Flare_91 said:
Hi, i have some mistake at this point, if i try to install newer magisk manager i cant because "i have another app with the same name", so what? using magisk 13.3 with the manager 5.1.1 provided by itself to active the cameras module? thanks
Click to expand...
Click to collapse
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.
After flashing install this.
If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.
Chazy12 said:
just a question: it's possible to edit build.prop via adb with twrp "live" without installing it?!
in this case, I could just edit it to enable camera2 api without rooting or installing twrp..
Click to expand...
Click to collapse
It should be possible. But I am wary of editing system partition because it might interfere with OTA updates and SafetyNet check.
Take a backup of system partition using TWRP just to be safe and proceed with editing.
Kindly report here if it works. Goodluck!:fingers-crossed:
Kripacharya said:
I just got a MiA1.I know how to root it with magisk but don't know how to enable camera2api.Will you please help me?
Click to expand...
Click to collapse
Sure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!

Ex-Hunter said:
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.
After flashing install this.
If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.
It should be possible. But I am wary of editing system partition because it might interfere with OTA updates and SafetyNet check.
Take a backup of system partition using TWRP just to be safe and proceed with editing.
Kindly report here if it works. Goodluck!:fingers-crossed:
Sure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!
Click to expand...
Click to collapse
Thanks for the answer.
It's only a line of code.. I hope there'll be not a problem for just one line..
Inviato dal mio Mi A1 utilizzando Tapatalk

Ex-Hunter said:
Yure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!
Click to expand...
Click to collapse
Ok, so I have Magisk 13.4 and manager app 5.4.0, and when I install camera module and restart it doesn't get that line written in build.prop so it doesn't work. In magisk it says that is installed. Is there something additional that has to be done or ?

Ex-Hunter said:
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.
After flashing install this.
If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.
Click to expand...
Click to collapse
Yes, my mistake i was already on 13.4 so i have unistalled magisk manager and then i have installed the latest version.
NITRO_100 said:
Ok, so I have Magisk 13.4 and manager app 5.4.0, and when I install camera module and restart it doesn't get that line written in build.prop so it doesn't work. In magisk it says that is installed. Is there something additional that has to be done or ?
Click to expand...
Click to collapse
Me too and i have add the lines manually then its ok for me.

Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
So the only difference for now (hope the good guys here will solve this) is that we can use twrp but only in temporary way using " boot" command and not "flash" then use the known progress and install root etc etc etc... Can this guide work in a vanilla out of the box phone with the October patch on it ?
To reboot to bootloader then boot to twrp install root then reboot then all ok ? Or you have to set a partition first
Thanks again for the help

nikkpap said:
So the only difference for now (hope the good guys here will solve this) is that we can use twrp but only in temporary way using " boot" command and not "flash" then use the known progress and install root etc etc etc... Can this guide work in a vanilla out of the box phone with the October patch on it ?
To reboot to bootloader then boot to twrp install root then reboot then all ok ? Or you have to set a partition first
Thanks again for the help
Click to expand...
Click to collapse
Yes it will work. No need to set a partition.

enricogrim said:
Hi, I followed your guide but when I boot to TWRP I can see only empty folder in the internal memory and I can't select the sd card. What was my mistake?
thank you very much
Click to expand...
Click to collapse
Do you use any PIN/password? If so, you have to input it when the TWRP boots up.

Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
Hi,
Have you tried using the newer Magisk V14.2 (1420) to root MI A1?
Thanks and best regards!
William

cmk7128 said:
Hi,
Have you tried using the newer Magisk V14.2 (1420) to root MI A1?
Thanks and best regards!
William
Click to expand...
Click to collapse
Yes, but unfortunately it doesn't work and the device will be stuck in a bootloop. @topjohnwu is working towards a fix. I'm sure we'll get the official Magisk on our device pretty soon.

Ex-Hunter said:
Yes, but unfortunately it doesn't work and the device will be stuck in a bootloop. @topjohnwu is working towards a fix. I'm sure we'll get the official Magisk on our device pretty soon.
Click to expand...
Click to collapse
Thanks for the feedback, much appreciated. BTW, do we have to fastboot flash the original/unpatched boot image before we proceed to download and install the new security update patch (eg. Oct to Nov 2017 update)?
Thanks!
William

cmk7128 said:
Thanks for the feedback, much appreciated. BTW, do we have to fastboot flash the original/unpatched boot image before we proceed to download and install the new security update patch (eg. Oct to Nov 2017 update)?
Thanks!
William
Click to expand...
Click to collapse
No, no need to flash the original boot img if you are already rooted with Magisk. Just download and install the update normally, but make sure to flash Magisk afterwards to get root back.

Ex-Hunter said:
No, no need to flash the original boot img if you are already rooted with Magisk. Just download and install the update normally, but make sure to flash Magisk afterwards to get root back.
Click to expand...
Click to collapse
Yes, I am rooted with Magisk v13.4 as per your steps. Thanks again.
Best regards!
William

Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
Just asking after rooted, can I re-lock the bootloader again? In order to pass safetynet?

soralz said:
Just asking after rooted, can I re-lock the bootloader again? In order to pass safetynet?
Click to expand...
Click to collapse
If I'm not mistaken it will pass safetynet if you are rooted with magisk.
Sent from my Mi A1 using Tapatalk

[How to root] Honor 6x with Magisk 14 - B367 (fast method for professional users)

[How to root] Honor 6x -B367- with Magisk 14
(fast method for professional users)
Use TWRP Recovery from the attachment.
Make a Backup first.
Uninstall SuperUser App-
[*]in TWRP flash unSu.zip-
[*]with TWRP restore the Stock Kernel (Boot Partition) from a backup-
[*]flash in TWRP Magisk-v14.0.zip-
[*]the magisk app is automatic installed .
[*]Reboot-
[*]flash in TWRP BusyBox-Magisk-1.25.zip-
[*]for Ad Block Plus first install the app and then flash the zip-
[*]if the flashing fails, please add the modules in the Magisk Manager App.
[*]Don't experiment with Xposed!
[*]The SafetyNet is thereby lost.
​
TWRP:
https://mega.nz/#!9l0jFQaZ!WJipSNyrecAuyok4Wpp_NM6fxWyFPWwn2aP34tW50sU

There's no point in installing MagiskManager. When you flash Magisk.zip, it automatically installs the manager apk. If your phone is not rooted, all you have to do is to flash the Magisk.zip in TWRP and that's it.

Thanks for your feedback. I will change the tuto immediately.

Can somebody share the boot.img for c432b367?
Thanks guys!

actually you can fix safetynet in honor 6x:
1. disable Hisuite HDB in settings>advanced settings>security
2. Go to developer options and enable adb debuging
3. go to apps and go to google play services and force stop it. and clear data (you know how to do it...)
4. run safetynet test
5. profit?
NOTE:you'll do this again if you reboot it except number 1...
EDIT: it works for me in my stock rom but IDK in other roms...
https://i.imgur.com/J8obP1l.png

I keep getting "error: cannot load 'berlin311'" when trying to flash twrp
Please help

If we have twrp from open kirin team installed, do we still need to flash this twrp or can use the same one?

Just realized that this is the same OpenKirin TWRP. Proceeding with Magisk for the first time now

Any thoughts on the error loading twrp?

Challah said:
Any thoughts on the error loading twrp?
Click to expand...
Click to collapse
I did not face any issue.. Was smooth. I am using magisk now

shashank1320 said:
I did not face any issue.. Was smooth. I am using magisk now
Click to expand...
Click to collapse
Sadly that doesn't help me much

Challah said:
Sadly that doesn't help me much
Click to expand...
Click to collapse
Which version of the are you using. I had one from open kirin team. Are you trying to boot to recovery with USB connected? Are you on emui 4/5?

Emui 5, tried using both versions, the one from your thread and the one from the kirin team thread.

Challah said:
Emui 5, tried using both versions, the one from your thread and the one from the kirin team thread.
Click to expand...
Click to collapse
Both are same file. Not sure why this issue. I flashed today couple of hours ago to install magisk as i did fload to be on stock.

I have tried all the guides, same issue each time.
My phone is unlocked, but I get an error loading the img

Challah said:
I have tried all the guides, same issue each time.
My phone is unlocked, but I get an error loading the img
Click to expand...
Click to collapse
Did you try relocking amd unlocking the bootloader again? Try once buddy

I figured it out, I had adb installed previously and it was opening it from a different place than I expected, so Berlin was in the wrong folder.

shashank1320 said:
Did you try relocking amd unlocking the bootloader again? Try once buddy
Click to expand...
Click to collapse
Only unlocking with unlock code. That's enough. Then activate OEM unlock and Debugging Mode in the Settings.

ChinHon said:
Only unlocking with unlock code. That's enough. Then activate OEM unlock and Debugging Mode in the Settings.
Click to expand...
Click to collapse
Working for me buddy. I was helping him as he had issue
Thanks for this..i got the confidence and was able to install magisk without issues which was not doing earlier

When on the step to flash busybox_magisk I get notified that magisk is not installed, magisk needs to be installed first, and then error "Updater process ended with ERROR: 1 Error installing zip file '/external_sd/BusyBox-Magisk-1.25.zip'?
I flashed magisk again, rebooted to recovery, tried busybox-magisk again, same error.

[GUIDE] How to Root OnePlus 7T without TWRP

So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi

Flashed and working flawless.
Really thanks for this.
Awesome work bro.

Can you please upload the patched boot.img please? I dont see it in the above folder at all.

nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder

Working, thanks a lot @mauronofrio

I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene

I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.

@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.

RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it

Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.

Thanks, rooted successfully

?
To be honest need video tutorial asap?

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.

[OP7T][Stock/Magisk] OxygenOS 11.0.2.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img

Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?

My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!

Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/

didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on

posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?

i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"

kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.

thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?

posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.

thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.

posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.

thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.

Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you