I just got my new Oneplus 9RT 5G. I searched a lot but unable to find a method to root it via TWRP.
Can anyone please share a link to TWRP recovery so that I can flash it and root it via Magisk?
I tried to unlock the bootloader by going to the fastboot mode but keep getting 'failed' message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have enabled 'USB debugging' and 'allow OEM unlock' in the developer options.
Use fastboot flashing unlock instead of oem unlock.
penguinus said:
Use fastboot flashing unlock instead of oem unlock.
Click to expand...
Click to collapse
Okay and what about a compatible TWRP recovery file that I can flash?
No TWRP for now. You should get boot.img from stock firmware, then patch it using Magisk Manager, then load the phone using patched boot.img, an then install magisk to the system
penguinus said:
No TWRP for now. You should get boot.img from stock firmware, then patch it using Magisk Manager, then load the phone using patched boot.img, an then install magisk to the system
Click to expand...
Click to collapse
Okay. How to get the stock firmware? I checked the official website. It's not available.
archz2 said:
Okay. How to get the stock firmware? I checked the official website. It's not available.
Click to expand...
Click to collapse
Yes, it is not available on site. If you have chinese firmware (ColorOS), you can get full rom from OTA servers. Even more, for the most recent versions I can provide ready to use boot.img. But for indian Oxygen full roms not availabe yet. You can try to dump boot.img from your phone using dd.
penguinus said:
You can try to dump boot.img from your phone using dd.
Click to expand...
Click to collapse
How do I do it? Please provide step by step process. I bought this phone in India and it's running Android 11 , Oxygen OS.
Well, looks like to dump boot.img you need root. Please try attached file (unzip it). Found it in TG, labeled as boot.img for indian Oxigen. Please note that you should NOT flash it to your device, so it should be safe enough. We will try to sideload it.
You already have installed fastboot to your PC, so I will skip this part.
To check boot.img
1. Place boot.img to your computer, to the same folder where you have fastboot installed
2. Reboot your phone to fastboot mode i.e with adb reboot bootloader
3. Do fastboot boot boot.img.
If phone will start normally, looks like boot is ok and you can use it to get rooted.
To install Magisk (get root)
1. Place boot image to phone.
2. Download Magisk and install it to the phone. Note that we use canary version of Magisk. Latest stable version doesn't work at least on chinese (ColorOS) version.
3. Start Magisk on a phone, press "Install" and choose "Select and Patch a File" (the only available option), select boot.img file.
4. Patched boot.img will be placed to Download directory named something like "magisk_patched*.img". Download this file back to PC, place to the same directory with fastboot.
5. Reboot your phone to fastboot mode i.e with adb reboot bootloader
6. Do fastboot boot magisk_patched*.img (change to correct name of file). Phone should start correctly.
7. Start Magisk again. Select "Install". This time all options should be available. Select "Direct Install (Recommended)".
8. At the end reboot and check if root is working.
penguinus said:
Well, looks like to dump boot.img you need root. Please try attached file (unzip it). Found it in TG, labeled as boot.img for indian Oxigen. Please note that you should NOT flash it to your device, so it should be safe enough. We will try to sideload it.
You already have installed fastboot to your PC, so I will skip this part.
To check boot.img
1. Place boot.img to your computer, to the same folder where you have fastboot installed
2. Reboot your phone to fastboot mode i.e with adb reboot bootloader
3. Do fastboot boot boot.img.
If phone will start normally, looks like boot is ok and you can use it to get rooted.
To install Magisk (get root)
1. Place boot image to phone.
2. Download Magisk and install it to the phone. Note that we use canary version of Magisk. Latest stable version doesn't work at least on chinese (ColorOS) version.
3. Start Magisk on a phone, press "Install" and choose "Select and Patch a File" (the only available option), select boot.img file.
4. Patched boot.img will be placed to Download directory named something like "magisk_patched*.img". Download this file back to PC, place to the same directory with fastboot.
5. Reboot your phone to fastboot mode i.e with adb reboot bootloader
6. Do fastboot boot magisk_patched*.img (change to correct name of file). Phone should start correctly.
7. Start Magisk again. Select "Install". This time all options should be available. Select "Direct Install (Recommended)".
8. At the end reboot and check if root is working.
Click to expand...
Click to collapse
Okay. Thanks a lot.
I checked the boot image, all the three step went absolutely fine.
To obtain Magisk, everything went well till step no. 5.
When I try to reboot with the patched image in the bootloader, the phone keeps booting in the bootloader itself. I also changed the name of the image from 'magisk_patched_bco6o' to 'bestimage', just to make sure that there aren't any special characters in the filename. Same. The phone kept booting in the fastboot mode using the image.
Now what should I do?
Edit.
I just updated the Magisk app directly from its UI. Now the phone booted fine using step 6. My device is rooted! Thanks a ton!
Okay. I'm connected to the internet and ensure that magisk has internet connectivity. I cannot see any packages to download and install. Is this normal in canary version or I have to do something about it?
archz2 said:
Okay. I'm connected to the internet and ensure that magisk has internet connectivity. I cannot see any packages to download and install. Is this normal in canary version or I have to do something about it?
Click to expand...
Click to collapse
Canary doesn't have internet repository. You should install modules manually. Please note that "Magisk Hide" is not available also and replaced by Zygisk function in settings. Basically it works similar to magisk hide.
archz2 said:
My device is rooted! Thanks a ton!
Click to expand...
Click to collapse
What ROM version is it? Especially a build number. Want to know what version of Oxygen is elighble for rooting with provided boot.img.
Here's the build information
Okay.
penguinus said:
Canary doesn't have internet repository. You should install modules manually. Please note that "Magisk Hide" is not available also and replaced by Zygisk function in settings. Basically it works similar to magisk hide.
Click to expand...
Click to collapse
Okay can I install a normal magisk app now since my device is already rooted?
Having a direct internet repository in magisk is quite convenient.
Another question. I want to install Lsposed on this phone to install GravityBox module. Now in my previous phone, (oneplus 5t running stock oxygen OS, Android 10) , I always used to keep a edxposed uninstaller zip file which helped in cases when there would be a bootloop after installing a module. I used to flash that zip in the TWRP, get back things to normal, and then uninstall a particular xposed module.
Now I don't have any TWRP on this phone. I don't have any custom recovery installed on this phone!
What do you recommend for doing xposed/lsposed/edxposed based flashing and module installation?
I can't say for sure it will not work. I just know stable version of Magisk DOESN'T work with 9RT chinese version (ColorOS). The chance to get it worked on OxigenOS is minimal as it looks for me. And what is happening with chinese phone with current magisk is bootloop. So I think it is better to not even try. At least while you don't have full ROM to recover.
Regarding absense of net repository in canary, there is a post from Magisk creator about it. Unfortunately, these functions will not back. I don't use many Magisk modules - just installed safetynet-fix and Systemizer manually.
Sorry, I don't have much experience with Magisk modules, the only recommendation for now is to not experiment too much while we don't have msm tool or at least full ROM.
Okay. And any comment on installing xposed? I don't have any TWRP or any custom recovery.
I didn't tried it, but please check threads of lsposed and EdXposed
Looks like both can be installed as Magisk modules, but needs Riru. Probably will give them a try later.
Thanks. I successfully installed latest Riru, Lsposed and GravityBox. All good so far.
Having issues with Viper installations. Will post about it in a separate thread.
penguinus said:
I don't use many Magisk modules - just installed safetynet-fix and Systemizer manually.
Click to expand...
Click to collapse
I flashed safetynet fix and rebooted but I'm still not able to pass safetynet. Any solution?
archz2 said:
I flashed safetynet fix and rebooted but I'm still not able to pass safetynet. Any solution?
Click to expand...
Click to collapse
After installing and activating safetynet fix you should clear data for Google Play Store and Google Play Services. Then open Play Store -> Settings -> About -> Play Protect certification. Should be "Device is certified"
Related
Hi guys, it's been several years since I last rooted phone. I got my Pixel 3 XL and tried to follow [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + instructions.
Did steps 4 and step 7.
TWRP installed and working. After Magisk 17.3 installation phone will not boot into system.
It will show G for 2 minutes and then it reboots back to TWRP.
I used provided links to latest files. I am lost. Am I missing some important step?
Thanks for help.. Charles
EvergreenExpert said:
Hi guys, it's been several years since I last rooted phone. I got my Pixel 3 XL and tried to follow [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + instructions.
Did steps 4 and step 7.
TWRP installed and working. After Magisk 17.3 installation phone will not boot into system.
It will show G for 2 minutes and then it reboots back to TWRP.
I used provided links to latest files. I am lost. Am I missing some important step?
Thanks for help.. Charles
Click to expand...
Click to collapse
SDK Platform-tools: r28.0.1
fastboot boot.img to both slots #6, fastboot boot twrp.img, install magisk's uninstaller, install magisk-17.3.zip, reboot system, done.
EvergreenExpert said:
Hi guys, it's been several years since I last rooted phone. I got my Pixel 3 XL and tried to follow [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + instructions.
Did steps 4 and step 7.
TWRP installed and working. After Magisk 17.3 installation phone will not boot into system.
It will show G for 2 minutes and then it reboots back to TWRP.
I used provided links to latest files. I am lost. Am I missing some important step?
Thanks for help.. Charles
Click to expand...
Click to collapse
Possible corrupted magisk file? Re-download the latest beta 17.3. I didn't have that problem but the general consensus has been to extract and flash the original boot.img and start over. Yes you will lose twrp, but from the PC you can flash the boot.img and then twrp.img right behind. Personally what I do on the phone is to queue up twrp.zip, kernel.zip, and magisk.zip and flash all 3 at the same time. Kernel is optional. Works well for me. Best of luck.
I am using Magisk v17.4.r18 which I understand is more reliable for rooting a Pixel 3 than 17.3.
You can find a link on to the newer Magisk from kantjer by searching XDA.
Homeboy76 said:
SDK Platform-tools: r28.0.1
fastboot boot.img to both slots #6, fastboot boot twrp.img, install magisk's uninstaller, install magisk-17.3.zip, reboot system, done.
Click to expand...
Click to collapse
No go..
I installed factory image - wiped data to start from clean slate using 9.0.0 (PQ1A.181105.017.A1, Nov 2018) SDK Platform-tools: r28.0.1
Boots fine... I setup the phone, gooole account, key pass etc.
Fastboot boot.img (extracted from PQ1A.181105.017.A1) - fastboot flash boot --slot all boot.img
All good booting fine.
fastboot boot twrp.img and install magisk's uninstaller
All good. Booting fine.
fastboot boot twrp.img and install magisk-17.3.zip
No more successful boot anymore.. Getting Big G for 2 minutes. Then reboot and error as shown on the picture. Something gets messed up after installation of magisk-17.3.zip
https://photos.google.com/share/AF1...?key=aW1ZQU14QVdVWGV6RTh4cWtTbkFhU3k1X25ZXzhn
I have downloaded all files again to start fresh..
Any suggestions? It sounds easy but something is not working for me..
Homeboy76 said:
SDK Platform-tools: r28.0.1
fastboot boot.img to both slots #6, fastboot boot twrp.img, install magisk's uninstaller, install magisk-17.3.zip, reboot system, done.
Click to expand...
Click to collapse
swieder711 said:
I am using Magisk v17.4.r18 which I understand is more reliable for rooting a Pixel 3 than 17.3.
You can find a link on to the newer Magisk from kantjer by searching XDA.
Click to expand...
Click to collapse
I tried to to download latest one from https://github.com/kantjer/MagiskFiles
Getting same error after installing Magisk.
EvergreenExpert said:
No go..
I installed factory image - wiped data to start from clean slate using 9.0.0 (PQ1A.181105.017.A1, Nov 2018) SDK Platform-tools: r28.0.1
Boots fine... I setup the phone, gooole account, key pass etc.
Fastboot boot.img (extracted from PQ1A.181105.017.A1) - fastboot flash boot --slot all boot.img
All good booting fine.
fastboot boot twrp.img and install magisk's uninstaller
All good. Booting fine.
fastboot boot twrp.img and install magisk-17.3.zip
No more successful boot anymore.. Getting Big G for 2 minutes. Then reboot and error as shown on the picture. Something gets messed up after installation of magisk-17.3.zip
https://photos.google.com/share/AF1...?key=aW1ZQU14QVdVWGV6RTh4cWtTbkFhU3k1X25ZXzhn
I have downloaded all files again to start fresh..
Any suggestions? It sounds easy but something is not working for me..
Click to expand...
Click to collapse
@EvergreenExpert
Never saw that error before.
So your bootloader is unlocked on your Pixel 3/Pixel 3 XL.
You have the latest SDK Platform-tools.
The following files are in the Platform-tools folder:
- fastboot
- Bootloader..img
- Radio...img
- Imagecrosshatch....zip
- flash-all.bat
- flash-base.sh
- Twrp.img (twrp-3.2.3-1...img)
You opened a command prompt in the Platform-tools folder (on your computer), booted the phone in fastboot mode, and did the following:
- installed the November factory image
- fastboot flash boot --slot all boot.img
- fastboot boot twrp.img
- installed magisk's uninstaller:
(Magisk-uninstaller-20181022.zip)
- installed Magisk-17.3.zip
In that order and got that error?
Was your pin set before you booted twrp?
Homeboy76 said:
@EvergreenExpert
Never saw that error before.
So your boot loader is unlocked on your Pixel3/ Pixel 3 XL.
You have the latest SDK Platform-tools.
The following files are in the Platform-tools folder:
- fastboot
- Bootloader..img
- Radio...img
- Imagecrosshatch....zip
Flash-all.bat
- Flash-base.sh
- Twrp.img (twrp-3.2.3-1...img)
You opened a command prompt in the Platform-tools folder (on your computer), booted the phone in fastboot mode, and did the following:
- installed the November factory image
- fastboot flash boot --slot all boot.img
- fastboot boot twrp.img
- installed magisk's uninstaller:
(Magisk-uninstaller-20181022.zip)
- installed Magisk-17.3.zip
In that order and got that error?
Was your pin set before you booted twrp?
Click to expand...
Click to collapse
Yes.. I did exactly that. Also tried to install newer version of Magisk.
Here is screenshot of folder with SDK Platform-tools: r28.0.1 and all files in it used.
https://photos.google.com/share/AF1...?key=U29nMDFYWFJnNnA4LTJNLTJTOWl3c3V1NFV0b3JB
Here are all files that I am working with including ones that go on the phone. All done from Windows 10 machine.
https://photos.google.com/share/AF1...?key=VnF4czY2OTZXS2JEdUJXcE50N3VJLXliVWlkYVVR
Bootloader unlocked on Pixel 3 XL. Pin set. Files on the phone copied over USB to Internal Shared Storage.
Phone boots fine even after Magisk uninstaller is installed. As soon as Magisk is installed it will not boot right. It will start booting, will show G for 2 minutes and reboots again just to show the error mentioned above. If I install TWRP on the phone it will reboot to TWRP instead of showing the error.
Got my phone on black Friday.. Maybe that why the phone was discounted.. LOL
Quick update... and one question.
So I did the same procedure again with exception of swipe to allow modifications.
Phone boots fine and appears to be rooted.
Does that provide any clues?
Also, what that means for me and updates? Do I need to watch and not allow OTA system updates or is there more to it?
Thanks Charles
EvergreenExpert said:
So I did the same procedure again with exception of swipe to allow modifications.
Phone boots fine and appears to be rooted.
Does that provide any clues?
Also, what that means for me and updates? Do I need to watch and not allow OTA system updates or is there more to it?
Thanks Charles
Click to expand...
Click to collapse
@EvergreenExpert
So you Added swipe to allow modifications after fastboot boot twrp.img? When you Reboot system did you skip (uncheck the two boxes - One is, "Install twrp as system")?
No. I always suggest twrp users swipe to allow modification (See guide below)
OTA System updates will unroot your phone. You can download the OTA image and sideload it.
After I root my phone, I go to Settings > System > Advanced > Deveoper options > turn off 'Automatic updates.
Then I do the following, monthly: Open this guide: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Do #4 'keep data' to update the factory image , then #8 to reroot.
Maybe I am doing something wrong after all.
My understanding is that I should always use Swipe to allow modification when installing TWRP, Magisk uninstall and Magisk.
In my case I did not permanently install TWRP just fastboot TWRP to install Magisk uninstall and Magisk.
When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked.
I have disabled automatic updates or your suggestion.
EvergreenExpert said:
Maybe I am doing something wrong after all.
My understanding is that I should always use Swipe to allow modification when installing TWRP, Magisk uninstall and Magisk.
In my case I did not permanently install TWRP just fastboot TWRP to install Magisk uninstall and Magisk.
When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked.
I have disabled automatic updates or your suggestion.
Click to expand...
Click to collapse
" When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked."
Please, share the exact other option you use to help other XDA members that are having problem installing Magisk-7.3.zip.
Homeboy76 said:
" When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked."
Please, share the exact other option you use to help other XDA members that are having problem installing Magisk-7.3.zip.
Click to expand...
Click to collapse
I am referring to Keep Read Only button.. See the picture. I used that button instead of swipe button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EvergreenExpert said:
I am referring to Keep Read Only button.. See the picture. I used that button instead of swipe button.
Click to expand...
Click to collapse
So instead of swiping to allow modifications you chose 'Keep read only' and it worked.
Great, thanks for sharing.
EvergreenExpert said:
Maybe I am doing something wrong after all....
Click to expand...
Click to collapse
No. I believe your intuition is correct. Ever since systemless root was the norm, I have *always* hit "keep read only" per Chainfire. I also install TWRP via the zip file (perm) because it is a Swiss Army knife I insist on having, and the stock recovery blows.. and IF for whatever reason I need blowing... I just flash the original boot.img. End of story. I also turn off the "twrp app install" and in settings turn off the screen timeout. Best of luck! :good:
EvergreenExpert said:
So I did the same procedure again with exception of swipe to allow modifications.
Phone boots fine and appears to be rooted.
Does that provide any clues?
Also, what that means for me and updates? Do I need to watch and not allow OTA system updates or is there more to it?
Thanks Charles
Click to expand...
Click to collapse
Where is the swipe to Allow modifications...never seen it
EvergreenExpert said:
I am referring to Keep Read Only button.. See the picture. I used that button instead of swipe button.
Click to expand...
Click to collapse
What was the exact build of TWRP that you used?
Everytime i install twrp i am asked to modify system. Or keep read only. Every version ive ever flashed
Hey guys, I am running into the same issue, with Magisk 18.1. Freezes on the load screen and then resets recovery (TWRP) after. The last time I tried to load the Magisk zip however, I got an error that read that vendor was not found or was busy.
This is the OnePlus 8 Pro's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
mauronofrio said:
This is the OnePlus 8 Pro's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Click to expand...
Click to collapse
Awesome thanks for the support.
Guys with this tool you can finally root your device without have to flash the specified patched boot.img. I hope it will help you and i hope you will not break anymore the fingerprint sensor. Enjoy it.
mauronofrio said:
Guys with this tool you can finally root your device without have to flash the specified patched boot.img. I hope it will help you and i hope you will not break anymore the fingerprint sensor. Enjoy it.
Click to expand...
Click to collapse
Would you be so kind to elaborate on that? I broke my fingerprint sensor by using a already patched img.. Kind of lazy mistake. But had the phone for just a day so I send it back and I'll be getting a new one tomorrow.
I would love to root it and retain my FP.
mauronofrio said:
Guys with this tool you can finally root your device without have to flash the specified patched boot.img. I hope it will help you and i hope you will not break anymore the fingerprint sensor. Enjoy it.
Click to expand...
Click to collapse
I would also like to know the steps. I'm looking at the tool and when selecting "Only Root" I can choose Magisk 20.4 from the list. The note in the tool says "or you can use 'Only Root' to root your phone you are already in TWRP mode." But as far as I understand there is no legitimate TWRP for our device yet.
Balthazard said:
Would you be so kind to elaborate on that? I broke my fingerprint sensor by using a already patched img.. Kind of lazy mistake. But had the phone for just a day so I send it back and I'll be getting a new one tomorrow.
I would love to root it and retain my FP.
Click to expand...
Click to collapse
letum00 said:
I would also like to know the steps. I'm looking at the tool and when selecting "Only Root" I can choose Magisk 20.4 from the list. The note in the tool says "or you can use 'Only Root' to root your phone you are already in TWRP mode." But as far as I understand there is no legitimate TWRP for our device yet.
Click to expand...
Click to collapse
So you should go in "recovery flasher and rooter" option, there you have to select the only TWRP available, check if "only boot" is checked, check "root after boot", select magisk 20.4 and click on the button at the bottom of the page. The TWRP will be booted and magisk flashed, and then from TWRP you can manually reboot to system and your device will be correctly rooted.
mauronofrio said:
So you should go in "recovery flasher and rooter" option, there you have to select the only TWRP available, check if "only boot" is checked, check "root after boot", select magisk 20.4 and click on the button at the bottom of the page. The TWRP will be booted and magisk flashed, and then from TWRP you can manually reboot to system and your device will be correctly rooted.
Click to expand...
Click to collapse
Thank you! I will be doing that when I get my phone.
It's actually just using your twrp build but instead of installing it, booting it and using twrp to flash the stable build of Magisk.
Thank you for your hard work!
Is it possible to restore fingerprint with this tool and appropriate files?
t-mizzle said:
Is it possible to restore fingerprint with this tool and appropriate files?
Click to expand...
Click to collapse
If you lost fingerprint, due to Canary Magisk, just switch to stable Magisk, and reinstall the latest update. If you did a local upgrade the file is still in your download folder. Worked fine for me.
spotmark said:
If you lost fingerprint, due to Canary Magisk, just switch to stable Magisk, and reinstall the latest update. If you did a local upgrade the file is still in your download folder. Worked fine for me.
Click to expand...
Click to collapse
I've tried that, it doesn't work for me.
t-mizzle said:
Is it possible to restore fingerprint with this tool and appropriate files?
Click to expand...
Click to collapse
actually no
Gordietm said:
I've tried that, it doesn't work for me.
Click to expand...
Click to collapse
Restore your persist img ..
If you have a backup...
cultofluna said:
Restore your persist img ..
If you have a backup...
Click to expand...
Click to collapse
I don't have one.
This will work on any version of OOS?
Sent from my IN2025 using Tapatalk
czerdrill said:
This will work on any version of OOS?
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
Yes sure
Thank you mauronofrio..!!!!
Has anyone used this tool yet to unlock the bootloader and root their 8 pro?
I just can't be the first one. Lmao!!!!
Is there a Tool to install on a Chromebook/Linux?
mauronofrio said:
So you should go in "recovery flasher and rooter" option, there you have to select the only TWRP available, check if "only boot" is checked, check "root after boot", select magisk 20.4 and click on the button at the bottom of the page. The TWRP will be booted and magisk flashed, and then from TWRP you can manually reboot to system and your device will be correctly rooted.
Click to expand...
Click to collapse
I'm having some trouble, any guidance would be appreciated. I have "only boot" checked and "root after boot" checked, and the phone just boots into TWRP and then hangs there. I've tried closing the command prompt and selecting "root only" but my device isn't showing up in the device list.
Konfuzion said:
I'm having some trouble, any guidance would be appreciated. I have "only boot" checked and "root after boot" checked, and the phone just boots into TWRP and then hangs there. I've tried closing the command prompt and selecting "root only" but my device isn't showing up in the device list.
Click to expand...
Click to collapse
You have some problems with adb
I know it's out of place, but I'm posting here because it's not registered this device with XDA. Forgive me.
I have a BlackShark 3S, but I can't update it because it broke Recovery.:crying:
Therefore, BlackShark 3S Full OTA or Recovery dump is required.
If you have it, would you please share it?
Thank you for reading.
Try the following:
1. Unlock bootloader (if not already) https://forum.xda-developers.com/t/blackshark-3-3-pro-3s-unlock-bootloader-files.4141537/
2. Download https://pan.ydxby.com/刷机包/黑鲨3/KLEN2009280CN00MQ3.zip?preview
3. Get Fastboot https://developer.android.com/studio/releases/platform-tools
4. Flash my fixed (updated with new bs3 and 3s kernel) TWRP from the attachment (fastboot flash recovery_a *Link to the downloaded TWRP image* and fastboot flash recovery_b *Link to the downloaded TWRP image*)
5. Boot to recovery (fastboot reboot recovery/fastboot boot *Link to the downloaded TWRP image*)
6. (recommended, not necessary) wipe all partitions in TWRP/Factory data reset/format as F2FS (updated it)
7. plug Phone to computer, copy the KLEN2009280CN00MQ3.zip from 2. to internal storage
8. install the zip in TWRP
9. (optional) after install, reboot to fastboot and flash TWRP again (if you don't do that you will have stock recovery)
10. boot the system
Other option:
instead of 2. Find the exact rom you have on your device https://pan.ydxby.com/刷机包/黑鲨3/
4. Extract the payload https://forum.xda-developers.com/t/guide-payload-bin-install-ota-zip-without-twrp.3865319/
5. install the recovery by fastboot flash recovery_a *Link to recovery.img* and fastboot flash recovery_b recovery.img
11. Tell me if sth worked for you so the next one with this problem sees
12. never buy a phone from someone who does not provide official stock ROM downloads/bootloader unlock again.
Sorry xda was not allowing me to upload for whatever invisible reasons. it seems to have worked after 200 attempts but 7z is not allowed (its smaller xda!) so i renamed to .zip. Just rename it back to KLEN2009280CN00MQ3TWRP_3.4.2B_repack.7z and extract it....
Hi @wertus33333
I saw it now.
I'll try it now.
12. never buy a phone from someone who does not provide official stock ROM downloads/bootloader unlock again.
Click to expand...
Click to collapse
That's really true.They also don't provide source code of linux kernel. (You are also mentioned here. https://forum.xda-developers.com/t/...l-and-up-to-date-china-rom-downloads.4197717/)
I was saved because you were there. Thank you.
koumaza said:
...
I was saved because you were there. Thank you.
Click to expand...
Click to collapse
Happy to help. So it worked out?
wertus33333 said:
Try the following:
1. Unlock bootloader (if not already) https://forum.xda-developers.com/t/blackshark-3-3-pro-3s-unlock-bootloader-files.4141537/
2. Download https://pan.ydxby.com/刷机包/黑鲨3/KLEN2009280CN00MQ3.zip?preview
3. Get Fastboot https://developer.android.com/studio/releases/platform-tools
4. Flash my fixed (updated with new bs3 and 3s kernel) TWRP from the attachment (fastboot flash recovery_a *Link to the downloaded TWRP image* and fastboot flash recovery_b *Link to the downloaded TWRP image*)
5. Boot to recovery (fastboot reboot recovery/fastboot boot *Link to the downloaded TWRP image*)
6. (recommended, not necessary) wipe all partitions in TWRP/Factory data reset/format as F2FS (updated it)
7. plug Phone to computer, copy the KLEN2009280CN00MQ3.zip from 2. to internal storage
8. install the zip in TWRP
9. (optional) after install, reboot to fastboot and flash TWRP again (if you don't do that you will have stock recovery)
10. boot the system
Other option:
instead of 2. Find the exact rom you have on your device https://pan.ydxby.com/刷机包/黑鲨3/
4. Extract the payload https://forum.xda-developers.com/t/guide-payload-bin-install-ota-zip-without-twrp.3865319/
5. install the recovery by fastboot flash recovery_a *Link to recovery.img* and fastboot flash recovery_b recovery.img
11. Tell me if sth worked for you so the next one with this problem sees
12. never buy a phone from someone who does not provide official stock ROM downloads/bootloader unlock again.
Click to expand...
Click to collapse
Thanks a lot! Working perfect!
Some comments what I found:
- After flashing ROM, safety net fails, all points
- Rooting without any problem
- Magisk Hide working well for that apps wich doesn't work if detect root
- Smali Patch not working for spoofing in PoGo
- I used this method because after unlock mi BS3S couldn't even once, login into google account, now can login anytime
Still have to find the way to make smali patch works, but at now looks fine
Thanks again
LuigiHacks said:
Thanks a lot! Working perfect!
Some comments what I found:
- After flashing ROM, safety net fails, all points
- Rooting without any problem
- Magisk Hide working well for that apps wich doesn't work if detect root
- Smali Patch not working for spoofing in PoGo
- I used this method because after unlock mi BS3S couldn't even once, login into google account, now can login anytime
Still have to find the way to make smali patch works, but at now looks fine
Thanks again
Click to expand...
Click to collapse
Happy to have helped,
-Maybe safety net fails bcs its CN beta rom
-If you only need location spoof you could try enabling dev options and selecting a mock location app from aurora-/playstore/F-droid no idea if it works with PoGo tho
to further optimize the ROM you could disable some of the bloatware with a magisk system app disabler.
would also be quite interesting if GSI's work (so we would have multilanguage support on nice interfaces with newest CN firmware...) but i filled that 256GB and backups take ages without USB3.0 xD
wertus33333 said:
Happy to have helped,
-Maybe safety net fails bcs its CN beta rom
-If you only need location spoof you could try enabling dev options and selecting a mock location app from aurora-/playstore/F-droid no idea if it works with PoGo tho
to further optimize the ROM you could disable some of the bloatware with a magisk system app disabler.
would also be quite interesting if GSI's work (so we would have multilanguage support on nice interfaces with newest CN firmware...) but i filled that 256GB and backups take ages without USB3.0 xD
Click to expand...
Click to collapse
Hello my friend, you deserved a cold beer
I flashed back KLEN2009280CN00MQ3, flash noverity zip, root magisk, smali patcher + spoofing signature, full Google apps and now everything works perfect, sing in all my accounts, magisk by passing safety net and spoofing PoGo without issues. Really thanks for your help.
One last question, do you know how to lock apps working in background and holding his reference in the notification bar? (Even when you release memory closing apps) it's for the joystick that am using.
Regards
LuigiHacks said:
Hello my friend, you deserved a cold beer
I flashed back KLEN2009280CN00MQ3, flash noverity zip, root magisk, smali patcher + spoofing signature, full Google apps and now everything works perfect, sing in all my accounts, magisk by passing safety net and spoofing PoGo without issues. Really thanks for your help.
One last question, do you know how to lock apps working in background and holding his reference in the notification bar? (Even when you release memory closing apps) it's for the joystick that am using.
Regards
Click to expand...
Click to collapse
nice.
so you want the app to stay active in background? remove it from battery optimizations (not sure if cleaning recents will still clean it but the system won't stop it)
also check the app permissions of the apps you want to keep in notification bar maybe there is an option somewhere
safety net passed in beta
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I recommend litegapps
LiteGapps
Download LiteGapps for free. LiteGapps is a custom gapps which is ,small, friendly and complete. LiteGapps is an Custom Gapps for smartphones, tablet, desktop, free and open-source software. by providing complete, stable support and several additional features.
sourceforge.net
It works systemless xD
koumaza said:
And I recommend litegapps
LiteGapps
Download LiteGapps for free. LiteGapps is a custom gapps which is ,small, friendly and complete. LiteGapps is an Custom Gapps for smartphones, tablet, desktop, free and open-source software. by providing complete, stable support and several additional features.
sourceforge.net
It works systemless xD
Click to expand...
Click to collapse
i recommend no gapps most apps "requiring" play services work perfectly without (they are telling different stories tho xD) and there is aurorastore
I've seen it, it's awesome!
Unfortunately, I need a Google Play license, so I'll use both.
And I just tried it, and the app is amazingly complete!
I will now use the aurora store to manage my apps.
Thanks for the post. Just got my BS 3S, i would like to root it and debloat most of the apps. Also is there any way to change the launcher? I tried in the settings, default apps, it says cant set because the launcher that Im trying to use is not allowed my JOYUI, Im trying Nova and Lawnchair 2. Thanks
I tried in the settings, default apps, it says cant set because the launcher that Im trying to use is not allowed my JOYUI, Im trying Nova and Lawnchair 2
Click to expand...
Click to collapse
Try installing and using quickswitch with magisk.
Then you can change the SystemUI native launcher.
Also, CustoMIUIzer is an interesting app so please try it.
koumaza said:
Try installing and using quickswitch with magisk.
Then you can change the SystemUI native launcher.
Also, CustoMIUIzer is an interesting app so please try it.
Click to expand...
Click to collapse
My BS 3S is not yet rooted, can you guide me?
hello can update
Download https://pan.ydxby.com/刷机包/黑鲨3/KLEN2009280CN00MQ3.zip?preview ??
Can't download now
iampatricktan said:
My BS 3S is not yet rooted, can you guide me?
Click to expand...
Click to collapse
I write the method I performed.
First, one thing to keep in mind is that the BlackShark 3 and 3S are partially compatible.
1. Unlock Bootloader.
Follow This Thread.
BlackShark 3/3 Pro/3S unlock bootloader files.
This unlocking method was researched by myself, so I bought two machines to study it. I know that many Chinese can unlock the Bootloader, but they are unwilling to announce it. They charge high unlock fees to unlock for users in need. This is...
forum.xda-developers.com
2. Flash Magisk from TWRP
TWRP-LINK: https://mega.nz/folder/KU8DTZhR#M2YjCHUrmupBkovTam2HtQ
If you don't know what to do for, please ask me.
Root Motorola Devices with Magisk
Note:
This method has been working with most Moto Devices that the Bootloader can be UnLocked.
If the Bootloader cannot be Unlocked this method will not work.
Please only use this as a reference. If you require more help please post in your device's forum.
Mention me with @sd_shadow
Quick Steps
Unlock the Bootloader
Note: Unlocking will wipe Userdata
Install Magisk manager app
Spoiler: Check ramdisk status
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If Ramdisk is Yes continue to Download Firmware
If Ramdisk is anything else see
New check ramdisk status -26 March 2021
Download Firmware Rescue and Smart Assistant(LMSA)(PC)
Spoiler: Check the Current software version with the download version.
If the download is newer, now is a good time to flash the update.
The newer boot.img may not work correctly with the older software on the device.
If you want to keep the firmware version that is on the device see Other Firmware Options
Other Firmware options
Find the boot.img in the LMSA Downloads Folder
"ProgramData\LMSA\Download\RomFiles\"
Copy boot.img to Moto Device
Spoiler: Tap Magisk > Install
Spoiler: Tap "Select and Patch a File"
Spoiler: Check the Patched.img Filename and Location
Copy magisk_patched.img to PC
Flash magisk_patched.img
Reboot
Open Magisk manager to verify you have the current version.
Hide Magisk
If you use apps the won't work if rooted devices (Banking apps) Enable Hide Magisk
Safetynet fix (21 March 2022)
https://github.com/kdrag0n/safetynet-fix
More
Magisk Hide: Using banking Apps
Magisk Recovery Mode
Install Updates and Keep Root
Root with Magisk Twrp method
https://github.com/topjohnwu/Magisk/releases/
Troubleshooting
If you get a "no ramdisk" error
Try flashing patched.img anyway it may still work
https://github.com/topjohnwu/Magisk/issues/3239
You may need to also patch the recovery.img
Like in this Post
Additional Links
[Stock ROM] How to root the Snapdragon Moto E 2020
Moto One 5G Ace root guide
Motorola One Macro [Root Tutorial]
Flashing magisk_patched.img
Change .img name to exact file name.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
or
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Magisk in recovery
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Click to expand...
Click to collapse
This does not replace stock recovery.
Installation
The Magic Mask for Android
topjohnwu.github.io
Magisk
Magisk Manager is dead.Long live the Magisk app!Ever since the first Magisk release, Magisk (the core components) and Magisk Manager (the companion app) are released separately and isn't necessarily always in sync. This leads to some confusion and a lot of complexity when downloading/installing Magisk through the app. Starting from v22.0, the Magisk app (renamed from Magisk Manager) includes everything it needs within the APK itself, making installation a 100% offline process.
Custom recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC™. Check out the updated installation guide for more info.
Click to expand...
Click to collapse
Installation
The Magic Mask for Android
topjohnwu.github.io
Magisk Recovery mode
[DEPRECATED] [2019.4.4] Magisk Manager for Recovery Mode (mm)
THIS PROJECT IS NO LONGER SUPPORTED. # Magisk Manager for Recovery Mode (mm) ## LEGAL Copyright (C) 2017-2019, VR25 @ xda-developers This program is free software: you can redistribute it and/or modify it under the terms of the GNU General...
forum.xda-developers.com
New Magisk Instructions
Installation
The Magic Mask for Android
topjohnwu.github.io
Hiding root and bootloader from Banking apps
Magisk and MagiskHide Installation and Troubleshooting guide : MagiskHide
Magisk renaming is maybe required.
Try using VD INFOS, you can see every detectable thing. (Root/Magisk/Xposed/Riru/and others.)
[APP][v1.10] VD Infos (Package: com.vitaodoidao.vdinfos)
(Para quem fala PORTUGUÊS, o próximo post está totalmente traduzido !) VD Infos v1.10 As we all know, Android is a super powerful and super versatile operating system. What nobody tells you is that all your personal details and confidential...
forum.xda-developers.com
Wow, thanks so much for the comprehensive reply @sd_shadow. Think I may take a look at the non-TWRP method.
Interesting that you install Magisk immediately after unlocking bootloader. I had been following these instructions: https://appuals.com/root-Motorola-moto-g5-g5-plus/ which doesn't install Magisk until after TWRP - but then you're not using TWRP!
In answer to @Wolfcity, yes I had tried reboot to TWRP, but get the following:
C:\adb>fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
I should've said, that's mostly why I figured it had failed.
I'm actually rooting to make use of Nethunter on the device. It's an old device, so not one I'll be using for any everyday apps or accounts. It'll be dedicated to Nethunter - for legit purposes only!
sd_shadow said:
Root Motorola Devices with Magisk
Note:
This method has been working with most Moto Devices that the Bootloader can be UnLocked.
If the Bootloader cannot be Unlocked this method will not work.
Please only use this as a reference. If you require more help please post in your device's forum.
Mention me with @sd_shadow
Quick Steps
Unlock the Bootloader
Note: Unlocking will wipe Userdata
Install Magisk manager app
Spoiler: Check ramdisk status
If Ramdisk is Yes continue to Download Firmware
If Ramdisk is anything else see
New check ramdisk status -26 March 2021
Download Firmware Rescue and Smart Assistant(LMSA)(PC)
Spoiler: Check the Current software version with the download version.
If the download is newer, now is a good time to flash the update.
The newer boot.img may not work correctly with the older software on the device.
If you want to keep the firmware version that is on the device see Other Firmware Options
Other Firmware options
Find the boot.img in the LMSA Downloads Folder
"ProgramData\LMSA\Download\RomFiles\"
Copy boot.img to Moto Device
Spoiler: Tap Magisk > Install
Spoiler: Tap "Select and Patch a File"
Spoiler: Check the Patched.img Filename and Location
View attachment 5384841
Copy magisk_patched.img to PC
Flash magisk_patched.img
Reboot
Open Magisk manager to verify you have the current version.
Hide Magisk
If you use apps the won't work if rooted devices (Banking apps) Enable Hide Magisk
More
Magisk Hide: Using banking Apps
Magisk Recovery Mode
Install Updates and Keep Root
Root with Magisk Twrp method
https://github.com/topjohnwu/Magisk/releases/
Click to expand...
Click to collapse
Question, when I did all of this through magisk everything went swell but my moto Touchscreen stopped working but booted just fine not sure if it was a one time fluke or not gonna try again any suggestions? Should I also Flash Recovery?
Jr.17 said:
Question, when I did all of this through magisk everything went swell but my moto Touchscreen stopped working but booted just fine not sure if it was a one time fluke or not gonna try again any suggestions? Should I also Flash Recovery?
Click to expand...
Click to collapse
If the touchscreen stopped working you likely used the wrong boot.img
You don't need a custom recovery just for root.
Sweet thanks I'll look again at what I got
Jr.17 said:
Sweet thanks I'll look again at what I got
Click to expand...
Click to collapse
boot.img must match build version and channel that is on the device.
Ok I see Where I messd up now looks like I used wrong channel
sd_shadow said:
Flashing magisk_patched.img
Change .img name to exact file name.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
or
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
I can't get my pc to see the phone when the phone is in fastboot mode
Grimace78 said:
I can't get my pc to see the phone when the phone is in fastboot mode
Click to expand...
Click to collapse
See device manager, how is it listed?
@sd_shadow My devices is edge xt2063-2 （USA，5G brand N71），It’s can't connect to chinatelecom（5G band N78）
But xt2603-3（Europe）ROM include N78 band
Can I flash XT2063-3 EU ROM on mydevices just by fastboot mode?
Or Just need modify some .img files
Vger20192019 said:
@sd_shadow My devices is edge xt2063-2 （USA，5G brand N71），It’s can't connect to chinatelecom（5G band N78）
But xt2603-3（Europe）ROM include N78 band
Can I flash XT2063-3 EU ROM on mydevices just by fastboot mode?
Or Just need modify some .img files
Click to expand...
Click to collapse
If the bootloader is unlocked, no problem.
If the bootloader is still locked, just flash the radio part.
Flashing the Radio Firmware
Grimace78 said:
I can't get my pc to see the phone when the phone is in fastboot modemak
Click to expand...
Click to collapse
Also Make sure To Update Drivers
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Reserved !!
hamooz92 said:
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Click to expand...
Click to collapse
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
Exactly.
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
I don't understand
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
They are saying rename magisk from apk to zip and flash it in TWRP
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
Just rename the APK to .zip extention and install through zip installer in twrp
iam almost ready to root my device i have both zip files from adreas tutorial on how root it.
where those zips files need to be in order to flash it?
cmd can be used, sorry iam new to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3lgato said:
View attachment 5485447
Click to expand...
Click to collapse
You need to get the unlock token first
Here is the instructions:
https://www.oneplus.com/support/answer/detail/op588
raginhomosapien said:
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
Click to expand...
Click to collapse
Glad it worked for you. You're welcome
Why it wait forever for attached device, even removing and reconnecting phone?
Rulesless said:
View attachment 5568509
Why it wait forever for attached device, even removing and reconnecting phone?
Click to expand...
Click to collapse
You have to be in fastboot mode before you can flash the recovery. Reboot into fastboot by typing "adb reboot fastboot" (without the quotes). Your phone should then reboot into fastboot mode. NOW, assuming you have already unlocked your bootloader, you can flash the recovery.
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
wcoolj said:
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
Click to expand...
Click to collapse
Just to add to this.....If you are unable to use device unlock because you have not met your carrier's requirements to do so yet you can use the script at this thread and it will open up oem unlock even if your phone is not eligible yet.
I have the N20. No twrp. Flashed a patched boot.img and lost radios. No wifi Bluetooth or sim)mobile data. Hoping that the platform is similar enough that someone could help me recover my device. Phone was sim locked, not sure if that's the issue. I forgot to run the command from the debloat script after flashing the unlock token, shouldn't have rushed this. I don't have a backup of anything though. Was trying to get root to back up everything. Factory resetting did nothing to fix the issue
PsYk0n4uT said:
Factory resetting did nothing to fix the issue
Click to expand...
Click to collapse
LOL never does at this level, just wipes cache and user partition, but nothing of value where we play- the assumption is you (or the bad guys) can't figure out how to write to the system, boot, etc partitions. (snicker).
So the good news is if you can find the EDL image, and follow the procedure to reflash the phone... it should restore everything for you.
(To be clear @PsYk0n4uT I linked you to the N10 EDL thread, not the N20...)
Thanks. So my issue so far. I don't think there is even a stock firmware posted anywhere. Though there is a backup of another device posted. How would I go about finding the EDL files for mine? Can one be created? Or would I need to source that from OnePlus or wait on someone to do that? I actually wasn't aware that I could boot the boot omg without flashing it to test it out first