I tried to root my brand new OnePlus Nord N10 5G phone with instructions below:
How to unlock bootloader and root OnePlus Nord N10 5G - GadgetSay
OnePlus Nord N10 5G is the newly launched affordable device for Europe and North America by OnePlus. While the device packs much for the price tag, it
www.gadgetsay.com
I had some difficulties with flashing (tried TRWP), but finally success with a computer.
Image was made by the Magisk, using source below:
OnePlus Nord | AC01BA Europe | OxygenOS 10.5.8 Stock Boot Image - Droid Docket
Description Download OxygenOS 10.5.8 stock boot image for OnePlus Nord (AC01BA Europe) for Magisk rooting and unrooting. Version Download 19 File Size 12.81 MB File Count 1 Create Date November. read more...
droiddocket.com
After rooting I got message "Image corrupted" on phone screen, and phone don't continue booting, it stops on fastboot menu.
It seems that the image is wrong, and I'm not able to take step back and try again since stock image is not available at OnePlus site.
Attached is some photos. Could you please help me to solve the problem and get the phone rooted ?
Here how to root
Root N10 using Magisk
Warning: I'm not responsible for any damage or bricked phones! Mirror for all OxygenOS images General Info: You need adb and fastboot installed and should know how to use it TWRP is not needed You must do this process only once...
forum.xda-developers.com
Thanks powergo - I'm still not sure does N10 image run on N10 5G, it has different hardware and that may make compatibility impact. I have asked help from OnePlus, they may tell which image is correct.
Omiar said:
I tried to root my brand new OnePlus Nord N10 5G phone with instructions below:
How to unlock bootloader and root OnePlus Nord N10 5G - GadgetSay
OnePlus Nord N10 5G is the newly launched affordable device for Europe and North America by OnePlus. While the device packs much for the price tag, it
www.gadgetsay.com
I had some difficulties with flashing (tried TRWP), but finally success with a computer.
Image was made by the Magisk, using source below:
OnePlus Nord | AC01BA Europe | OxygenOS 10.5.8 Stock Boot Image - Droid Docket
Description Download OxygenOS 10.5.8 stock boot image for OnePlus Nord (AC01BA Europe) for Magisk rooting and unrooting. Version Download 19 File Size 12.81 MB File Count 1 Create Date November. read more...
droiddocket.com
After rooting I got message "Image corrupted" on phone screen, and phone don't continue booting, it stops on fastboot menu.
It seems that the image is wrong, and I'm not able to take step back and try again since stock image is not available at OnePlus site.
Attached is some photos. Could you please help me to solve the problem and get the phone rooted ?
Click to expand...
Click to collapse
In the first photo your bootloader is still locked, you need to unlock it for root access.
JrkSoldierX said:
In the first photo your bootloader is still locked, you need to unlock it for root access.
Click to expand...
Click to collapse
It was unlocked, I tested lock-state just to see if it helps. Programmer works, I just need correct image for the N10 5G.
Omiar said:
It was unlocked, I tested lock-state just to see if it helps. Programmer works, I just need correct image for the N10 5G.
Click to expand...
Click to collapse
Just follow steps in the thread mentioned.
It works fine because you take the right file from the right firmware, you enable root access with Magisk Manager app and u flash it through your computer.
Rom said:
Just follow steps in the thread mentioned.
It works fine because you take the right file from the right firmware, you enable root access with Magisk Manager app and u flash it through your computer.
Click to expand...
Click to collapse
NOP. I got the phone restored original condition with the instructions and files on the thread, but unfortunately rooting with the provided image (magisk_patched_U6YuI.img) the phone get stuck. The screen is stuck on "Fastboot" mode, computer gives error "no devices/emulators found" on command "adb shell su". Fastboot via computer seems to work, but it's hard to solve due to poor instructions. One positive thing is that N10 image seems to work also on N10 5G device, not confirmed yet by OnePlus technical customer care.
Omiar said:
NOP. I got the phone restored original condition with the instructions and files on the thread, but unfortunately rooting with the provided image (magisk_patched_U6YuI.img) the phone get stuck. The screen is stuck on "Fastboot" mode, computer gives error "no devices/emulators found" on command "adb shell su". Fastboot via computer seems to work, but it's hard to solve due to poor instructions. One positive thing is that N10 image seems to work also on N10 5G device, not confirmed yet by OnePlus technical customer care.
Click to expand...
Click to collapse
There is only one phone. N10 5G aka billie. And if you cannot follow those simple instructions I'd suggest reading through the net about what is fastboot, adb and boot images before attempting to flash anything on your device.
There are many sites providing step by step instructions with photos of what to do, too. The instructions are the same for every oneplus device from the last few years. Also, read carefully and don't flash your image before fastboot boot.
Omiar said:
NOP. I got the phone restored original condition with the instructions and files on the thread, but unfortunately rooting with the provided image (magisk_patched_U6YuI.img) the phone get stuck. The screen is stuck on "Fastboot" mode, computer gives error "no devices/emulators found" on command "adb shell su". Fastboot via computer seems to work, but it's hard to solve due to poor instructions. One positive thing is that N10 image seems to work also on N10 5G device, not confirmed yet by OnePlus technical customer care.
Click to expand...
Click to collapse
I got stuck in FastBoot mode as well when using the files in the rooting thread. I had to do the full restore to get it working again.
Okay, tried rooting again.Current build number on phone is 10.5.9.BE86AA. Unlocked bootloader, OEM unlocking in Developer options shows Bootloader already Unlocked. Downloaded magisk_patched_10.5.9.BE86AA.zip. Run this fastboot command: fastboot boot magisk_patched_10.5.9.BE86AA.zip. The phone reboots and goes back into bootloader mode. Any ideas as to what I am doing wrong?
maback said:
Okay, tried rooting again.Current build number on phone is 10.5.9.BE86AA. Unlocked bootloader, OEM unlocking in Developer options shows Bootloader already Unlocked. Downloaded magisk_patched_10.5.9.BE86AA.zip. Run this fastboot command: fastboot boot magisk_patched_10.5.9.BE86AA.zip. The phone reboots and goes back into bootloader mode. Any ideas as to what I am doing wrong?
Click to expand...
Click to collapse
Can you run the same command with unpatched boot.img ?
I have successfully rooted my N10
The progress is pretty straightforward.
All I need is matching boot.img to patch with Magisk Manager, and copy patched_boot to host computer to flash
Make sure Magisk Hide is enabled and you must clear Play Store data
Tried to root, now stuck in fastboot loop (will not reboot to recovery nor to EDL to flash the original rom, either using buttons or fastboot reboot edl on computer). Anyone have any ideas?
to everyone that has device not booting,
did you try fastboot boot boot.img before flashing it?
i just tested the BE86 10.5.9 magisk patched boot.img again and it boots fine.
make sure to use the correct fastboot mode:
andreas__ said:
to everyone that has device not booting,
did you try fastboot boot boot.img before flashing it?
i just tested the BE86 10.5.9 magisk patched boot.img again and it boots fine.
make sure to use the correct fastboot mode:
View attachment 5204763
Click to expand...
Click to collapse
yes , tried fastboot boot boot.i
andreas__ said:
to everyone that has device not booting,
did you try fastboot boot boot.img before flashing it?
i just tested the BE86 10.5.9 magisk patched boot.img again and it boots fine.
make sure to use the correct fastboot mode:
View attachment 5204763
Click to expand...
Click to collapse
yes , tried fastboot boot boot.img before flashing. (both original and patched image)
Just in case: you cannot see EDL mode, it just stays black ! So you must find it in device manager on PC
andreas__ said:
Can you run the same command with unpatched boot.img ?
Click to expand...
Click to collapse
Same result, does not work, I'm starting to think magisk_patched_10.5.9.BE86AA.zip may be mislabeled. Has anyone else successfully used this particular file to root?
maback said:
Same result, does not work, I'm starting to think magisk_patched_10.5.9.BE86AA.zip may be mislabeled. Has anyone else successfully used this particular file to root?
Click to expand...
Click to collapse
As I said, I tested that file today again and it booted just fine.. don't know why it wouldn't on the same rom on your phone :/
andreas__ said:
As I said, I tested that file today again and it booted just fine.. don't know why it wouldn't on the same rom on your phone :/
Click to expand...
Click to collapse
Hmm weird, I've tried different cables, 2 different PCs, it just boots to a screen with the OnePlus logo and says fastboot underneath (Still responds to fastboot commands).
The only other thing I can try is using a Windows machine, as both my computers run Ubuntu. Never had any issue rooting my other phones using fastboot.
When in bootloader mode my phone shows Device State as unlocked, but SecureBoot as Yes. Could that be my problem?
Related
I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?
Hello, I am from Canada and I just got a Moto G Power (2021) XT2117-4 with the firmware QZBS30.Q4-43-129-2. I unlocked the bootloader thru Motorola with no problems. I installed Rescue and Smart Assistant and downloaded my firmware. I patched the boot.img thru Magisk and flashed it to my phone using ADB. I was not able to achieve root. I also tried to boot thru recovery mode but got the no command sign. I then rescued my phone and tried it again flashing to both boot_a and boot_b still to no avail. If anyone has any info on why this is and has a solution to my problem it would be greatly appreciated.
jwreidmoto said:
Hello, I am from Canada and I just got a Moto G Power (2021) XT2117-4 with the firmware QZBS30.Q4-43-129-2. I unlocked the bootloader thru Motorola with no problems. I installed Rescue and Smart Assistant and downloaded my firmware. I patched the boot.img thru Magisk and flashed it to my phone using ADB. I was not able to achieve root. I also tried to boot thru recovery mode but got the no command sign. I then rescued my phone and tried it again flashing to both boot_a and boot_b still to no avail. If anyone has any info on why this is and has a solution to my problem it would be greatly appreciated.
Click to expand...
Click to collapse
Does the phone boot with the patched boot.img ?
sd_shadow said:
Does the phone boot with the patched boot.img ?
Click to expand...
Click to collapse
Yes.
jwreidmoto said:
Yes.
Click to expand...
Click to collapse
What does the magisk app say?
Can you share a screenshot?
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
What does the magisk app say?
Can you share a screenshot?
Click to expand...
Click to collapse
That is just how the patched boot.img is created.
Now you have to flash it with fastboot.exe
Been thru that already no root.
Do I have to rename it to boot.img when I flash it or can I leave with with the patched name?
I am going to start from scratch again. I don't think I made a mistake because I rooted my G7 Play this way too. I also get feedback from terminal confirming flashing.
jwreidmoto said:
Do I have to rename it to boot.img when I flash it or can I leave with with the patched name?
Click to expand...
Click to collapse
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
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...
forum.xda-developers.com
and
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more
Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.
www.xda-developers.com
Followed link instructions exactly and still no root. Maybe I have to go with a TWRP recovery method. I will keep checking forums for others having same issue.
jwreidmoto said:
Followed link instructions exactly and still no root. Maybe I have to go with a TWRP recovery method. I will keep checking forums for others having same issue.
Click to expand...
Click to collapse
Ok, if you want help you have to give details.
No root means nothing.
I downloaded firmware from Rescue assistant copied boot.img to phone selected it thru magical and patched it. Copied patched boot.img to PC. Put it in ADB folder renamed it back to boot.img. Opened up ADB terminal and flashed - fastboot flash boot boot.img. Terminal said writing boot_a......okay.....finished. reboot no root. Tried again with flashing to boot_a and to boot_b. Reboot still no root. That's about all I can tell you everything checked out including ramdisk - yes in Magisk, boot.img from same firmware that is currently on phone. Not sure why it's not working.
Actually, sorry phone is now rooted. Once I added root checker to superuser in magisk it showed phone was successfully rooted Thanks for all your help!
Just to confirm, as I've yet to root my device and may encounter this same issue. Did you solve it having done anything different with the rooting procedure or was it a simple matter of adding the root app to Magisk SU? If the latter, Did magisk display the SU prompt at all?
Yes, the root instructions are good. I think why Magisk did not prompt me, initially was because my phone was setting up for the first time and it was bogged down by Google restoring apps etc. Now Magisk prompts me every time for root apps.
So I'm Down to Help this is what I did. So
Download Rescue and blah blah assistant
Found My Phone Checked and Double Checked all information then when I did so I extract led the Folder to My desktop, looked inside it's little bundle of goodness to find boot.img pulled it out and connect my Moto G.
At This Point I Just Opened up My Phone storage (from My P.C) pulled it out and stuck it in my main storage.
At that point Went and Got Magisk v.23 renamed the download as Magisk v.23.apk
Then Riped her Open Like A wild animal installed the .apk (If the File Manager or whatever you are using won't let you install go to settings for the particular File Manager you are using on your phone and allow download a from unknown sources)
Pulled out the boot.img I put in my main storage and went to My sexy New Magisk App and selected "select and Patch a file"
At the Point stepped out for a quick smoke and had a tug.
Then your final product will be Magisk_patchedv23.img (or something like that)
Then after you get all that mumbo move that back to your P.C
I assume you have adb fastboot
So then I pull it up (not sure if it affects anything but I did adb Root)
Anywho first I did
adb devices -l
As soon as I see my phone se then I know I got it.
#also side not make sure the wording next to the device says device
Ok so at the point type
adb reboot fastboot
Then repeat same command as the adb one
Fastboot devices
#seeyour device? Dope
Then wherever you put that patched image sometimes you need to put the FULL path
Example for me it was
Fastboot flash magisk_patched.img boot
Which didn't work so tried the _a still nothing soo hence the FULL PATH I put it on my desktop if you don't know the full path right click the file and hit properties
final Command for me
fastboot flash boot C:\Users\insan\Desktop\magisk_patched.img
Boom Done and Done!!!! And as always take Back Ups Before and After and Save that Patch .img
I've needed it like 10 times !
Hope That Helps Ya
And the last pic Is Proof
God Bless, and Good Luck!
Note: This process is shown for OnePlus Nord 2 and work for any MTK device just replace files as per your model you need to Serch for that)
Credits @Raygen @TheWing
After relocking bootloader you can do safety net pass check to confirm by using following app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettes
Download Re LiveDVD mtk. Client ( this is ready mtk client ubuntu os no need to Install python, drivers ready to go iso)
re_livedvdV3.iso
drive.google.com
Download Rufus for windows 32/64bit)
https://github.com/pbatard/rufus/releases/download/v3.17/rufus-3.17.exe
Note:Relocking has been done on OOS 11.1 v13 so stock boot img of v13, vbmeta from update zip of v13 is required, recovery must be given below.
Your need to replace files as per oxygen os version you are using.
FOLLOWING are images of DN2101 A13 OOS UPDATE IMAGES EXCEPT RECOVERY IMAGE IT WILL WORK IN ANY PHONE, U NEED YOUR AS PER YOUR REGION I WILL UPDATE THREAD AFTER COLLECTING ALL HERE
Boot img (This is stock A13 indian, other regions must use there current OOS version boot img)( other mtk devices must use there boot img here)
https://forum.xda-developers.com/attachments/boot-img.5460945/
Stock recovery(in zip unzip it you will get img file this will work for any region)( other mtk devices must use there recovery img here)
https://forum.xda-developers.com/attachments/recovery_stock-zip.5464685/
Vbmeta:must have correct vbmeta of current OOS Rom. Version (from stock A13 indian update.zip if U r using EU, OR GLOBAL region NORD replace it with the current OOS version you are for which you want to relock)(other mtk devices must use there vbmeta img here)
vbmeta.img
drive.google.com
All files for EU DN2103 ON A12 UPDTAE :
EU varient v12 files:
Boot. Img:
https://forum.xda-developers.com/attachments/boot_stock_a12-img.5461083/
Vbmeta. Img/
vbmeta.img
drive.google.com
Recovery same link for all)
recovery_stock.zip
drive.google.com
Terminal emulator commands :
1) BOOT TO FASTBOOT connect phone to pc in on condition)
adb reboot fastboot
2)to relock bootloader in terminal emulator connect phone to pc in fastboot mode and type)
fastboot flashing lock
MTK client commands:
1)Flash boot img:
python mtk w boot boot.img
2) Flash recovery img:
python mtk w recovery recovery.img
3) Flash Vbmeta :
python mtk w vbmeta vbmeta.img
wifi is not working. everything working after relock bootloader but wifi is not working
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
Factory reset u r phone and reboot see
pankspoo said:
Factory reset u r phone and reboot see
Click to expand...
Click to collapse
i did it. but it's not working
farhansaeeddnp3021 said:
i did it. but it's not working
Click to expand...
Click to collapse
Update yourbphone to latest v14
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
NetSoerfer said:
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
Click to expand...
Click to collapse
Your device will go in to boot img corrupt after that.......
PLEASE NOTE: This isnt working if you are on a custom rom! My Bootloader ist broken and locked and I have to figure out how to fix this ****.
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
7tyjupiter said:
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
Click to expand...
Click to collapse
Check YASNAC app from play store if it's showing safety net check passed your locked.
While installation of OTA what's errors u r getting.
After locking OEM unlock not grates off actually now it's available to unlock again with switchable tab
Sorry for crossposting a lot today, but I am really stuck and it seems that this may be the tool I need. I am on A15, cannot lock bootloader and cannot update.
So, to be sure, for this to work I need the boot.img, recovery.img and vbmeta.img for A15 stock rom? If yes, where can I get those files?
I found the files! Thank you for this guide! It worked perfectly. I really thought my phone was completely bricked. Coming from a Pixel, the root/restore process on this thing is a complete nightmare!!
https://forum.xda-developers.com/attachments/boot-img.5460945/
this link says like this
Oops! We broke the matrix. Someone call Neo!You do not have permission to view this page or perform this action.
Ok. So I think if f-ed up big time! only message I get now is a big red "!" and: "the current image have been destroyed please flash te correct image....
HELP!
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
lachatol said:
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
Click to expand...
Click to collapse
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
exis_tenz said:
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
Click to expand...
Click to collapse
I want to lock the botloader, I don't want root anymore. I just need to be sure that if I service the phone for reinstallation to the original firmware, then the bootloader will be locked. Will be? thank you for answer
No worries, it'll be locked after a factory flash!
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
extranoob said:
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
Click to expand...
Click to collapse
If u gets wifi issue just flash boot image of OOS version u r using via fastboot
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
when it stared, I patched it with Magisk directly.
____________________________
Firmware updating (Full update) keeping the Root:
by using "oneplus local update for android 12" the root can be kept.
Install the firmware with oplocal, dont reboot, open magisk flash it on the second slot; only now you can reboot.
DON'T REBOOT after the FW installation.
The firmware can be downloaded through the app Oxygen Updater. (Full update)
---------------------------
Attachment:
Boot Patched 10T from Indian version img
OPLocal Update for Android 12 apk
Stock boot A06 CPH2415 img
Patched Boot A06 CPH2415 (Magisk 25.2) img
Marco589 said:
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
Click to expand...
Click to collapse
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
slavekve said:
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
Click to expand...
Click to collapse
Don't follow that guide. You just need to boot (not flash) a patched boot image and then run direct install. This also creates backups of your stock images which you'll need when you OTA.
EtherealRemnant said:
Don't follow that guide. You just need to boot (not flash) a patched boot image and then run direct install. This also creates backups of your stock images which you'll need when you OTA.
Click to expand...
Click to collapse
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
slavekve said:
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
Click to expand...
Click to collapse
Again, DON'T flash the patched image! You must use the direct install method in Magisk after booting the patched image.
EtherealRemnant said:
Again, DON'T flash the patched image! You must use the direct install method in Magisk after booting the patched image.
Click to expand...
Click to collapse
I understand that, but in the instructions, the repaired vendor_boot.img is also flashed. Oneplus 7 Pro does not contain vendor_boot.img file in payload.bin
slavekve said:
I understand that, but in the instructions, the repaired vendor_boot.img is also flashed
Click to expand...
Click to collapse
Are you not listening to me? I just told you how to do it. Boot the patched image and run the direct install. Magisk installer will do what needs to be done for you. This is also the same thing the OP has done. Ignore those other instructions you found, they are incorrect and pose problems when you take OTA updates as OnePlus is moving away from full OTAs to incremental ones that will not flash to a phone with modified images.
For the record, patched dtbo and vendor_boot are needed as well but Magisk does this for you.
Ok, I will follow the instructions above when my phone arrives
any way to activate 5g & volte on non supported carriers - countries?
akaloith said:
any way to activate 5g & volte on non supported carriers - countries?
Click to expand...
Click to collapse
Unlock the bootloader, Install the Global ROM that supports 17 5G Bands both SA & NSA. Which Country you are in ?
Marco589 said:
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
when it stared, I patched it with Magisk directly.
Click to expand...
Click to collapse
I have 10T Global, Indian and Chinese ROM Full Package ZIP file, I want to try Global & Chinese ROM on Indian 8/128GB Version
already unlocked bootloader, if I Flash Global or Chinese ROM will my device brick ?
As previously I was using MSM Download Tool which was free now it need authentication, so shifted to Fastboot Enhance
Will the process of flashing via payload.bin brick my device ?
Today it is possible to download EU full package CPH2315_11_A.06 using Oxygen updater
slavekve said:
Today it is possible to download EU full package CPH2315_11_A.06 using Oxygen updater
Click to expand...
Click to collapse
I already root mine OP10T Model CPH2415 which is international ROM but i tried to flash that CPH2315 in Oxygen Updater it was a success but the model of my phone was change also from CPH2415 to CPH2315.
I have OP8T Cyberpunk Edition Which Is Chinese ROM and i Flash Global ROM the thing is it change only the Build number which is right and the model Number still The same KB2000 but this OP10T is different including the model was change when i flash. Anyway it was a success but it shouldn't be like that.
ryu091 said:
I already root mine OP10T Model CPH2415 which is international ROM but i tried to flash that CPH2315 in Oxygen Updater it was a success but the model of my phone was change also from CPH2415 to CPH2315.
I have OP8T Cyberpunk Edition Which Is Chinese ROM and i Flash Global ROM the thing is it change only the Build number which is right and the model Number still The same KB2000 but this OP10T is different including the model was change when i flash. Anyway it was a success but it shouldn't be like that.
Click to expand...
Click to collapse
So that mean all 10T devices are China made and later flashed with region specific firmware's.
slavekve said:
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
Click to expand...
Click to collapse
Hi @slavekve , Sadique this side, sorry for the confusion. Till the OnePlus 9, you only needed to flash the patched boot.img for root.
But with the OnePlus 10 series [10 Pro], flashing patched vendor_boot and vbmeta for disabling verity seems to have become an additional requirement in numerous instances.
But thanks to @Marco589 for letting us know that he has already achieved root without the vbmeta and vendor. Henceforth I have updated my post accordingly as well.
Guys, I have a CPH 2413 device and have tried several times to unlock bootloader... But fastboot commands do not work on my device. Have tried "OEM unlock" as well "flashing unlock" through fastboot. Updated the fastboot and adb drivers, tried to do it through platform tools as well... Got my device replaced as well after the first one didn't get unlocked...
Help needed please
gonetask said:
Unlock the bootloader, Install the Global ROM that supports 17 5G Bands both SA & NSA. Which Country you are in ?
Click to expand...
Click to collapse
I am in greece and carrier vodafone
will i sure have 5g and volte? cause device is not supported by vodafone greece
SREEPRAJAY said:
Guys, I have a CPH 2413 device and have tried several times to unlock bootloader... But fastboot commands do not work on my device. Have tried "OEM unlock" as well "flashing unlock" through fastboot. Updated the fastboot and adb drivers, tried to do it through platform tools as well... Got my device replaced as well after the first one didn't get unlocked...
Help needed please
Click to expand...
Click to collapse
I came across to the same issue, I solved by adding ".\":
.\fastboot devices
.\fastboot flashing unlock
PS
did the OS install the driver of the phone in fastboot mode?
Marco589 said:
I came across to the same issue, I solved by adding ".\":
.\fastboot devices
.\fastboot flashing unlock
PS
did the OS install the driver of the phone in fastboot mode?
Click to expand...
Click to collapse
.\ does not work. Can you please explain which tool you used? or how you managed?
Hello everyone hope you are all keeping well.
Since I believe that many of you don't know about this, I've decided to share the steps I've done in order to root the OP 11R ( ACE 2 )
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
1 - 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:
adb devices
adb reboot bootloader
(so your phone will reboot into fastboot mode)
fastboot flashing unlock
(device should now unlock)
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
2 - Download OP 11R 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...)
Indian Boot.img A_0.8 - download
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - 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
5 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
6 - 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...)
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
7 - 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!
8 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
Why title says NORD 2T?
firoz3321 said:
Why title says NORD 2T?
Click to expand...
Click to collapse
MB ... typo
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
firoz3321 said:
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
Click to expand...
Click to collapse
Sorry but there is no msm tool available for new OnePlus devices. + You can use Fastboot enhance tool from github to recover softbrick , magisk is always recommended for rooting because of ease of steps and simple to use
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
saifsohel said:
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
Click to expand...
Click to collapse
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
shiki_senpai said:
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
Click to expand...
Click to collapse
Then remember to take a backup of the boot before rebooting. I messed up big time.
Thanks for the detailed information man. Can I know if bootloader unlock decreases widevine L1 to L3? As this was case with my OP6