Related
I have a Pixel 3a that had Magisk installed and it has been rooted for a while. I want to upgrade to Android 11 but in Magisk Canary there is no option to install Magisk into the inactive slot. Am I missing a button somewhere or what?
SirHappyCatIII said:
I have a Pixel 3a that had Magisk installed and it has been rooted for a while. I want to upgrade to Android 11 but in Magisk Canary there is no option to install Magisk into the inactive slot. Am I missing a button somewhere or what?
Click to expand...
Click to collapse
I'm assuming youre still on 10 right? Follow the steps on magisk's github
Roarmaster said:
I'm assuming youre still on 10 right? Follow the steps on magisk's github
Click to expand...
Click to collapse
The issue is that those steps are for the stable magisk build, but as far as I can tell only Magisk Canary supports android 11. The issue being that Magisk Canary doesn't seem to have a button to install magisk into the inactive slot after downloading the update.
SirHappyCatIII said:
The issue is that those steps are for the stable magisk build, but as far as I can tell only Magisk Canary supports android 11. The issue being that Magisk Canary doesn't seem to have a button to install magisk into the inactive slot after downloading the update.
Click to expand...
Click to collapse
I see, well you can also do it the manual way (which is what I did).
- First search for the factory image for the pixel 3a Android 11 September.
- Download that on your computer, unzip it, and look for the boot.img
- Transfer that boot.img file to your phone and patch it with magisk (install > patch file > boot.img)
- Transfer that magisk-patched.img back to your computer
- Download ADB for your computer
- After updating your phone to android 11, reboot to fastboot mode after checking that USB debugging is enabled in developer settings
- on your computer check if ADB is connected: "fastboot devices"
- if you see a device there, go to the next step
- using ADB, enter the following in your terminal: "fastboot flash boot your-magisk-patched-boot.img"
- you're now rooted again
Roarmaster said:
I see, well you can also do it the manual way (which is what I did).
- First search for the factory image for the pixel 3a Android 11 September.
- Download that on your computer, unzip it, and look for the boot.img
- Transfer that boot.img file to your phone and patch it with magisk (install > patch file > boot.img)
- Transfer that magisk-patched.img back to your computer
- Download ADB for your computer
- After updating your phone to android 11, reboot to fastboot mode after checking that USB debugging is enabled in developer settings
- on your computer check if ADB is connected: "fastboot devices"
- if you see a device there, go to the next step
- using ADB, enter the following in your terminal: "fastboot flash boot your-magisk-patched-boot.img"
- you're now rooted again
Click to expand...
Click to collapse
Alright, I was hoping to avoid the manual route, but I'll try it, thanks.
Roarmaster said:
I see, well you can also do it the manual way (which is what I did).
- First search for the factory image for the pixel 3a Android 11 September.
- Download that on your computer, unzip it, and look for the boot.img
- Transfer that boot.img file to your phone and patch it with magisk (install > patch file > boot.img)
- Transfer that magisk-patched.img back to your computer
- Download ADB for your computer
- After updating your phone to android 11, reboot to fastboot mode after checking that USB debugging is enabled in developer settings
- on your computer check if ADB is connected: "fastboot devices"
- if you see a device there, go to the next step
- using ADB, enter the following in your terminal: "fastboot flash boot your-magisk-patched-boot.img"
- you're now rooted again
Click to expand...
Click to collapse
Well I've tried patching the boot image and flashing 3 times now to no avail. To be clear I updated to android 11, installed the latest canary magisk manager, downloaded stock images for pixel 3a, took the boot.img from the stock images, and patched it with magisk. Now when I try to flash the patched image I get infinite G logo.
SirHappyCatIII said:
Well I've tried patching the boot image and flashing 3 times now to no avail. To be clear I updated to android 11, installed the latest canary magisk manager, downloaded stock images for pixel 3a, took the boot.img from the stock images, and patched it with magisk. Now when I try to flash the patched image I get infinite G logo.
Click to expand...
Click to collapse
In magisk manager, set the update channel to Canary before you patch the boot.img file
captain sideways said:
In magisk manager, set the update channel to Canary before you patch the boot.img file
Click to expand...
Click to collapse
It is set to canary and I am on version d6dbab53. I'm going to downgrade to android 10 for now I suppose, I'm not sure what else I can do other than wait for stable magisk to support Android 11.
edit: seems like downgrading to android 10 required a device wipe. I might just need to live without root until I can get this to work.
SirHappyCatIII said:
It is set to canary and I am on version d6dbab53. I'm going to downgrade to android 10 for now I suppose, I'm not sure what else I can do other than wait for stable magisk to support Android 11.
edit: seems like downgrading to android 10 required a device wipe. I might just need to live without root until I can get this to work.
Click to expand...
Click to collapse
It deffo works - start with a clean slate and do it step by step - I do this all the time and it does work.
Right so:
Flash a clean boot.img from the stock firmware files so your phone will boot.
When it boots, uninstall magisk manager all together and reboot.
Install the Magisk Manager linked below (confirmed working)
Set the update channel to Canary and reboot just to be sure. Open manager and see there is an update available to manager so update it and reboot.
Now copy the clean boot.img to your phone's download folder.
In manager, install magisk by selecting and patching the boot.img
Copy the resulting magisk_patched.img to your computer's adb folder.
Open command prompt as administrator and navigate to your adb folder so your prompt should reads C:/adb
At the prompt, type:
adb reboot bootloader
With your phone now in bootloader at your prompt, type:
fastboot flash boot magisk_patched.img
When it completes, start your phone. This is how I do and I've done it loads of times and I boot first time.
I have a few extra reboots in there and you can do it with less, but it just keeps every thing clean and fresh and in place while you master the process ? let me know...
http://bit.ly/magiskcanarymanagerxda
captain sideways said:
It deffo works - start with a clean slate and do it step by step - I do this all the time and it does work.
Right so:
Flash a clean boot.img from the stock firmware files so your phone will boot.
When it boots, uninstall magisk manager all together and reboot.
Install the Magisk Manager linked below (confirmed working)
Set the update channel to Canary and reboot just to be sure. Open manager and see there is an update available to manager so update it and reboot.
Now copy the clean boot.img to your phone's download folder.
In manager, install magisk by selecting and patching the boot.img
Copy the resulting magisk_patched.img to your computer's adb folder.
Open command prompt as administrator and navigate to your adb folder so your prompt should reads C:/adb
At the prompt, type:
adb reboot bootloader
With your phone now in bootloader at your prompt, type:
fastboot flash boot magisk_patched.img
When it completes, start your phone. This is how I do and I've done it loads of times and I boot first time.
I have a few extra reboots in there and you can do it with less, but it just keeps every thing clean and fresh and in place while you master the process let me know...
http://bit.ly/magiskcanarymanagerxda
Click to expand...
Click to collapse
I followed these steps exactly, and I have waited 15 minutes at the G logo. Nada. Not sure why it won't work, but I guess I will just need to live with it for now. Flashing stock boot image makes the phone boot again, but without magisk obviously.
SirHappyCatIII said:
I followed these steps exactly, and I have waited 15 minutes at the G logo. Nada. Not sure why it won't work, but I guess I will just need to live with it for now. Flashing stock boot image makes the phone boot again, but without magisk obviously.
Click to expand...
Click to collapse
Ah OK, I'm sorry to hear that, I really am out of ideas now but hope you manage to get it sorted if you do, let me know cos I'll be wondering about it now trying to work it out ?
Did all of the steps work apart from your phone booting? Have a look at the file size of your magisk_patched.img in windows explorer, does it report as 0kb? That happened to me one time so I just did the whole process again and then it worked
Update: I wiped my entire phone, flashed stock images, and tried again. It worked first try. Maybe it had something to do with a module I had installed? No idea. Thanks for the help though everyone.
another update: seems like one of the modules i installed (probably riru edxposed?) stops the phone from booting. Time to wipe everything and try again yayyyy.
captain sideways said:
Ah OK, I'm sorry to hear that, I really am out of ideas now but hope you manage to get it sorted if you do, let me know cos I'll be wondering about it now trying to work it out ?
Did all of the steps work apart from your phone booting? Have a look at the file size of your magisk_patched.img in windows explorer, does it report as 0kb? That happened to me one time so I just did the whole process again and then it worked
Click to expand...
Click to collapse
I think the Rira - EdXPosed module in magisk is what was stopping it from booting. I wiped my phone and restarted everything and installing magisk worked first try. As soon as I installed EdXposed and rebooted I got infinite G logo.
SirHappyCatIII said:
I think the Rira - EdXPosed module in magisk is what was stopping it from booting. I wiped my phone and restarted everything and installing magisk worked first try. As soon as I installed EdXposed and rebooted I got infinite G logo.
Click to expand...
Click to collapse
Ah lush, right, OK that makes sense
I've not used exposed since I had the moto x play (years ago) so don't have that on my phone ? glad you worked it out, it's good knowledge to have for the future
For reference, you don't need to wipe your phone, just flash the stock boot img then you can go into magisk manager and remove the offending module ?
captain sideways said:
Ah lush, right, OK that makes sense
I've not used exposed since I had the moto x play (years ago) so don't have that on my phone glad you worked it out, it's good knowledge to have for the future
For reference, you don't need to wipe your phone, just flash the stock boot img then you can go into magisk manager and remove the offending module
Click to expand...
Click to collapse
Haha wish I knew that 3 hours ago. I don't know why I didn't think to just remove the module.
I know, it's a pain in the ass but you'll remember for the future?
SirHappyCatIII said:
I followed these steps exactly, and I have waited 15 minutes at the G logo. Nada. Not sure why it won't work, but I guess I will just need to live with it for now. Flashing stock boot image makes the phone boot again, but without magisk obviously.
Click to expand...
Click to collapse
I had issues also, rename the magisk_patched.img to boot.img, after I did that it booted and was rooted
Just an FYI, you can now set the update channel to beta and get the version of Magisk that supports android 11.
I am trying to root my IN2017 and am struggling with understanding the next steps. I have the bootloader unlocked (T-mobile and OnePlus), installed Magisk Manager, installed TWRP, but cannot figure out the next step. Basically all directions mention a boot.img but I cannot find one for the IM2017. Am I missing something here?
Any help would be greatly appreciated!
Since you are using a T-Mobile variant, you are still running Android 10. Simply download the latest Magisk zip from github and flash it in TWRP. Done.
Another possibility - in TWRP take a full backup of the device and transfer this to your computer. The boot should be named "boot.emmc.win" rename this to boot.img, upload it to your oneplus. In magisk manager, patch this file for magisk. Take the new magisk-patched-boot.img and transfer it back to you computer. From your computer use fastboot and in the directory with the patched boot image type:
fastboot flash boot_a magisk-patched-boot.img
fastboot flash boot_b magisk-patched-boot.img
(or replace magisk-patched-boot.img with whatever it is named)
Hope this helps.
Once the device is rooted, make sure you take the persistent.img and transfer this off the device, in case in the future you lose your fingerprint sensor! If this image on the device gets corrupted, then you will lose your ability to unlock by fingerprint.
Hope this helps.
Cheers,
B.D.
anyone have a step by step to root Bison GT? Been out of the game for a while.
You can follow the steps in the link below but use the Bison GT boot.img file from the rom on umidigi's site. I can confirm this works.
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
*Remember, unlocking your bootloader will cause your phone to be erased.
Here is the short version:
In a nutshell, assuming you have your drivers setup for ADB and Fastboot...on this phone, everytime I go into bootloader mode, I have to goto device manager and set the driver manually to the google bootloader one.
Steps:
unlock bootloader
install magisk apk on phone(https://magiskmanager.com/)
Extract boot.img from stock rom that is installed on your device. https://community.umidigi.com/forum.php?mod=forumdisplay&fid=258
Copy boot.img over to your phone
Run magisk app on your phone, click install, click from file, locate boot.img on your phone and start. This will patch that boot.img
Copy patched boot.img that magisk created from your phone to your PC
Reboot phone into bootloader mode/fastboot (adb reboot-bootloader)
Flash patched boot image to boot partition: fastboot flash boot nameofpatchedboot.img
Reboot into phone and see if it worked.
This will get root working on Bison GT
maamdroid said:
You can follow the steps in the link below but use the Bison GT boot.img file from the rom on umidigi's site. I can confirm this works.
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
*Remember, unlocking your bootloader will cause your phone to be erased.
Here is the short version:
In a nutshell, assuming you have your drivers setup for ADB and Fastboot...on this phone, everytime I go into bootloader mode, I have to goto device manager and set the driver manually to the google bootloader one.
Steps:
unlock bootloader
install magisk apk on phone(https://magiskmanager.com/)
Extract boot.img from stock rom that is installed on your device. https://community.umidigi.com/forum.php?mod=forumdisplay&fid=258
Copy boot.img over to your phone
Run magisk app on your phone, click install, click from file, locate boot.img on your phone and start. This will patch that boot.img
Copy patched boot.img that magisk created from your phone to your PC
Reboot phone into bootloader mode/fastboot (adb reboot-bootloader)
Flash patched boot image to boot partition: fastboot flash boot nameofpatchedboot.img
Reboot into phone and see if it worked.
This will get root working on Bison GT
Click to expand...
Click to collapse
I tried this method but I Thingk magiskis faliling to patch properly the boot.img. I get an errror : ERROR: STATUS_CHECKSUM_ERR (0xC0040003) when i try to flash the patchet boot with sp flash tool
ArgonTc said:
I tried this method but I Thingk magiskis faliling to patch properly the boot.img. I get an errror : ERROR: STATUS_CHECKSUM_ERR (0xC0040003) when i try to flash the patchet boot with sp flash tool
Click to expand...
Click to collapse
Why are you using sp flash tool to flash that?
maamdroid said:
Why are you using sp flash tool to flash that?
Click to expand...
Click to collapse
I'm a total noob, How it is suposed i have to flash the patched boot?
ArgonTc said:
I'm a total noob, How it is suposed i have to flash the patched boot?
Click to expand...
Click to collapse
Ah, You would use fastboot to flash it. Though, there are some steps in there I generalized. Like step 1, unlock bootloader requires a few steps and fastboot...
I'll have to go back and edit my post to get much more specific. I don't have time now, buy in a few days. Otherwise, if you find someone elses post about rooting and unlocking the older "Bison", those step should all be the same.
I think umidigi has this detailed out on their messageboard. Otherwise, just wait till I get back here to update this with all the details.
I had Magisk working with the release rom. The update today will bootloop if I install the magisk built boot.img. If I push the boot.img that came with the update then the phone will boot but no more magisk.
mrportico said:
I had Magisk working with the release rom. The update today will bootloop if I install the magisk built boot.img. If I push the boot.img that came with the update then the phone will boot but no more magisk.
Click to expand...
Click to collapse
Did you rebuild the boot.img from within Magisk on the phone using the update boot.img...not the original release boot.img.
Hi,
with the latest Magisk update I noticed the missing Magisk Hide and SafetyNet fix. So I decided to go back to Magisk 23. After a few unsuccessful attempts, I don't know what happened but now my phone is no longer rooted. So I tried some usual methods to re-root the device but nothing to do, still no root
I have used boot.img patching way with Magisk but when I send ADB command "fastboot flash boot magisk_patched.img", it seems to work fine but after reboot there is no root
So I tried the other method by booting the device with patched boot.img using ADB ("fastboot boot magisk_patched.img") then I open Magisk Manager but in the installation section there is no "direct install" option as it should be.
I also tried flashing Magisk.zip via TWRP as I did long ago and TWRP seems to do the job well but after rebooting again no root...
Any suggestions?
even though you don't have root, i suggest flashing the stock boot.img and then rebooting to be really sure that root has been removed. and then flash the magisk patched boot.img.
are you using the latest adb and fastboot? you can get the latest from here. https://developer.android.com/studio/releases/platform-tools
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
altwu said:
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
Click to expand...
Click to collapse
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
¿GotJazz? said:
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
Click to expand...
Click to collapse
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
altwu said:
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
Click to expand...
Click to collapse
Yes, I used the stock boot.img that I extracted from the 11.0.5.1 file that was downloaded as the normal OTA update from OnePlus. I patched that boot image with Magisk v24.1 that was already installed on my OP7P.
Then, I flashed that Magisk patched boot.img using fastboot onto both A and B slots (I switched slots by booting into TWRP 3.6, since I didn't see a way to switch slots with the now-loaded OnePlus Recovery Mode).
When I rebooted through the patched image, the phone came up (which is good!), but Magisk says that I don't have root (which is bad!). I haven't figured out how to fix that.
Could you PM me your patched boot.img? I could try flashing that to see if my OP7P acts any differently.
Thanks!
OK, I'm 100% positive that Magisk v24.1 patched my OP7P OOS 11.0.5.1 boot.img properly.
I extracted the 11.0.5.1 boot.img file from the OTA image that was in my .Ota folder from my phone. I extracted boot.img from the payload.bin file using two different methods of payload-dumper. Both boot.img files had the same SHA-512 checksums, so they were identical.
I also downloaded a copy of the Magisk v24.1 patched boot.img from the intenet and compared it to my Magisk v24.1 patched boot.img file. Again, the SHA-512 checksums matched for the two patched files, so I am sure that I have a properly patched boot.img file.
Note that my OP7P has loaded the full OOS 11.0.5.1 Stock image, so I currently have the OOS Recovery Mode and I do not have TWRP Recovery Mode.
Maybe I am doing something else wrong during my installation that is keeping me from getting root?
Here is the process I followed with my patched boot.img file:
I boot into Fastboot Mode
In Fastboot Mode, I go into TWRP Recovery Mode by typing: fastboot boot twrp-3.6.0_11-0-guacamole.img
After rebooting into TWRP Recovery, I installed the 11.0.5.1 OTA by doing an Install > Browse to the .Ota folder for the OTA .Zip file.
After the OOS 11.5.0.1 OTA installed, I rebooted back to Fastboot Mode (before booting normally) by selecting: Reboot > Slot A > Home > Reboot > Bootloader
Once I am back into Fastboot Mode, I type: fastboot flash boot magisk_patched_boot.img
In Fastboot Mode, I type: fastboot reboot
After I have rebooted back to normal mode, Magisk v24.1 is already installed and I don't do any updates to that. When opening Magisk, my screen flashes a couple of times before giving me a Toast pop-up that Magisk was denied Super User access. When I look at the Magisk App screen, it says that the App is installed, but that Magisk is not installed.
Are there any steps that I am missing?
Well, I finally got OOS 11.0.5.1 rooted with Magisk v24.1.
I ended up wiping my data and installing a fresh install of OOS 11.0.5.1 (Not sure if this is necessary, but I skrood up along the way and had to wipe as a result).
The one thing that was different this time around was that I disabled encryption/lock before flashing the Magisk-v24.1 patched boot image. I suspect that was what helped me make it to the finish line this time.
Good luck out there!
¿GJ?
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
altwu said:
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
Click to expand...
Click to collapse
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
¿GotJazz? said:
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
Click to expand...
Click to collapse
you can use fastboot to switch slots.
fastboot --set-active=a or b
i don't know if it's necessary, but i reboot the bootloader with "fastboot reboot bootloader" after switching slots.
i've never tried this, but you can also specify what slot when running fastboot flash, like "fastboot flash boot magisk_patched.img --slot a".
check out "fastboot help" to see the different options.
i haven't had to play around with slots though. when an update is available, i'll download the zip to a computer and then go through the normal update process via the os. after the update is done, the phone reboots and the correct active slot is set.
Thanks for the feedback, @altwu.
I am having issues getting my SMS notification sound working on my fresh(er) 11.0.5.1 installation. I haven't seen anybody respond back yet, and I am beginning to suspect it's just a problem on my OP7P. If I don't see anybody responding back by tomorrow, I'll assume it's "just me".
I am thinking about doing a total wipe again to see if it will clear up the issue I am seeing. I will end up trying your installation route this time to see if it helps at all.
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP