How To Guide TUTORIAL TWRP AND ROOT NORD 2

Search This thread

pankspoo

Senior Member
Jun 27, 2013
1,812
961
in front of ENCHILADA
SO finally I successfully rooted with TWRP and root access.thanks to all developers @Eastw1ng @TheMalachite

Following are all download links combined in one post Also there are two threads like unlocking boot loader and twrp but there are some steps are not mentioned which we must need to understand so see the video tutorial at the end of thread.
If you have issues please post comment I will try to solve at my best

NOTE: REMOVE ALL PASSWORD AND PINS ON PHONE BEFORE FLASHING TWRP
All data will be erased so keep backup

Download:
TWRP IMAGE:

Vbmeta image:


Mediatek USB VCom drivers:




ADB AND FASTBOOT DRIVERS(WHEN FASTBOOT NOT DETECTING ONLY)


magisk v24 zip:


magisk 23 apk:


CMD COMMNADS HIT ENTER:


1)detect adb devices:


adb devices


2)Reboot to bootloader mode:
adb reboot bootloader


3)To detect FASTBOOT devices:


fastboot devices


4)To OEM unlock:
fastboot flashing unlock


5)To flash Vbmeta image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img


6) flash twrp image:
fastboot flash recovery recoveryname.img


7)Reboot from FASTBOOT mode to recovery:
fastboot reboot recovery


If you have any issue follow this tutorial correctly
 
Last edited:

Kenaestic

Member
Nov 27, 2013
25
2
OnePlus Nord 2 5G
This worked great! Only problem I had was unlocking the bootloader and flashing TWRP without booting up caused the stock recovery to overwrite it again for some reason. After repeating the steps after unlocking it worked. Also, if you have the same problem as me with Magisk being unable to bypass the safety net, try this:

I wish I found this before I sunk hours into learning what build prop editing is :p
 
  • Like
Reactions: pankspoo

pankspoo

Senior Member
Jun 27, 2013
1,812
961
in front of ENCHILADA
This worked great! Only problem I had was unlocking the bootloader and flashing TWRP without booting up caused the stock recovery to overwrite it again for some reason. After repeating the steps after unlocking it worked. Also, if you have the same problem as me with Magisk being unable to bypass the safety net, try this:

I wish I found this before I sunk hours into learning what build prop editing is :p
I already mentioned in the video regarding re-writing of STOCK recovery. For that when we reboot after typing
fastboot reboot recovery
Immediately press volume down+ power button till you saw the recovery name at the bottom om the phone screen and leave the phone it will boots to twrp that's it.
 

Kenaestic

Member
Nov 27, 2013
25
2
OnePlus Nord 2 5G
I already mentioned in the video regarding re-writing of STOCK recovery. For that when we reboot after typing
fastboot reboot recovery
Immediately press volume down+ power button till you saw the recovery name at the bottom om the phone screen and leave the phone it will boots to twrp that's it.
It did boot to TWRP with just the command, though. It just didn't save it for some reason. Still no major problem or anything. Your guide worked in the end and I'm happy :)! However I noticed GPS is terrible now for some reason. When I'm on WiFi there's no problems but as soon as I go on mobile data: my weather app can't refresh anymore, Google Maps thinks I'm 50 meters from my actual location and the GPS is always turned 90 degrees away from forward. Is this a common problem?
 

pankspoo

Senior Member
Jun 27, 2013
1,812
961
in front of ENCHILADA
It did boot to TWRP with just the command, though. It just didn't save it for some reason. Still no major problem or anything. Your guide worked in the end and I'm happy :)! However I noticed GPS is terrible now for some reason. When I'm on WiFi there's no problems but as soon as I go on mobile data: my weather app can't refresh anymore, Google Maps thinks I'm 50 meters from my actual location and the GPS is always turned 90 degrees away from forward. Is this a common problem?
Root doesn't have to do with these things anymore please check any other app is causing issue
 

pankspoo

Senior Member
Jun 27, 2013
1,812
961
in front of ENCHILADA
Ciao, ho effettuato il root del mio telefono con questo metodo (https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/ ) come Non sono riuscito a installare TWRP. Ora mi chiedo se posso fare la procedura installando TWRP e poi procedere all'upgrade alla versione A.11. Perderò i miei dati? Grazie
Use this method to. Upgrade you will not loose data if you already unlocked your bootloadee
 

caccola69

Member
Oct 26, 2013
24
2
Use this method to. Upgrade you will not loose data if you already unlocked your bootloadee
Thanks for the answer .... as I said I don't have TWRP. When I tried to install it, after restarting the phone, it was no longer accessible. For this I used the other method for root (I didn't understand how to fix TWRP)

What do you advise me to do?
 

pankspoo

Senior Member
Jun 27, 2013
1,812
961
in front of ENCHILADA
Thanks for the answer .... as I said I don't have TWRP. When I tried to install it, after restarting the phone, it was no longer accessible. For this I used the other method for root (I didn't understand how to fix TWRP)

What do you advise me to do?
Did you seen the video after flashing twrp using fastboot you need to type

fastboot reboot recovery and hit enter

You will boot in Twrp and its permenant
 
Last edited:

caccola69

Member
Oct 26, 2013
24
2
Did you seen the video after flashing twrp using fastboot you need to tyoe
F
fastboot reboot recovery and hit enter
You will boot in. Twrp and its permenant
thanks for your patience but I'm afraid to make a mistake
Do I redo the whole procedure described?

CMD COMMNADS HIT ENTER:

1)detect adb devices:
adb devices


2)Reboot to bootloader mode:
adb reboot bootloader


3)To detect FASTBOOT devices:
fastboot devices


4)To OEM unlock:
fastboot flashing unlock


5)To flash Vbmeta image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img


6) flash twrp image:
fastboot flash recovery recoveryname.img


7)Reboot from FASTBOOT mode to recovery:
fastboot reboot recovery
 

pankspoo

Senior Member
Jun 27, 2013
1,812
961
in front of ENCHILADA
thanks for your patience but I'm afraid to make a mistake
Do I redo the whole procedure described?

CMD COMMNADS HIT ENTER:

1)detect adb devices:
adb devices


2)Reboot to bootloader mode:
adb reboot bootloader


3)To detect FASTBOOT devices:
fastboot devices


4)To OEM unlock:
fastboot flashing unlock


5)To flash Vbmeta image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img


6) flash twrp image:
fastboot flash recovery recoveryname.img


7)Reboot from FASTBOOT mode to recovery:
fastboot reboot recovery
Yes correct
 

caccola69

Member
Oct 26, 2013
24
2
this procedure deleted all my data. I have upgraded the phone to version A.11 and now waiting to figure out how to root

I redid the procedure and in twrp I did a wipe data. I restart twrp and now I see all the memory but I can't copy magisk to the phone and then flash it
 
Last edited:

pankspoo

Senior Member
Jun 27, 2013
1,812
961
in front of ENCHILADA
Reboot
this procedure deleted all my data. I have upgraded the phone to version A.11 and now waiting to figure out how to root

I redid the procedure and in twrp I did a wipe data. I restart twrp and now I see all the memory but I can't copy magisk to the phone and then flash it
OEM unlocking always wipes your data no need to mention things again and again.
If you have TWRP first click wipe> format data >yes now reboot back to TWRP again
now click MTP disable and enable it now see if you are able to copy files.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi, I successfully followed this procedure but had bootloop problem with twrp+root a few months ago and decided to stay unrooted for some times, I found that root may be stable if I followed these steps : https://gist.github.com/Giovix92/c7e69123dbc51adf3f3a26f9c3c0208e#rooting. Can someone confirm that root is stable (no bootoloop) with this procedure ?

    As @Giovix92 states in the post above, rooting through patched with magisk boot.img works without problems.

    I can confirm 10 months rooted without any problem. No TWRP, just root.
    1
    Hello everyone,
    it's been years since I last rooted my phone and the process seems to be a bit less straight-forward nowadays.

    I have some questions and would appreciate it if someone could answer them:
    1) How does "twrp-3.6.0_11-0-UNOFFICIAL-denniz.img" differ from the official TWRP versions for denniz? Can I use the official versions at twrp.me as well?
    2) Where does "vbmeta.img" come from? I suppose it's from some stock firmware image for denniz. How would I go about obtaining this file myself? I'm on DN2103_11_A.21 but I couldn't find any sources online to download the stock image. Not even Oneplus seems to be offering this anywhere.

    I feel a bit uncomfortable downloading all these files from threads or telegram channels and would rather gather all needed files from official sources. (I know that I'm talking to experienced developers in this forum, please don't take it the wrong way)

    I will try to answer, regarding my experience:

    1) The "twrp-3.6.0_11-0-UNOFFICIAL-denniz.img" is a bit outdated. We have now official at twrp.me as you notice. I wil use the latest official.

    2) The update.zip from A.20 to A.21 has vbmeta.img. Can be obtained from the official updater, copied and stored.

    The other vbmeta shared here is an ''empty' one to use after unlocking.

    Hope helped. Cheers.
    1
    Hey roldev!

    1) I was already wondering if that was the reason. Thanks for clearing that up!
    2) Which updater do you mean? I updated my phone using Settings -> Software Update. I'm not seeing the image file in any of my folders. Also, do I need to use the "empty" vbmeta or can I use the real one too if my goal is to root my phone?

    You need to be rooted, to obtain the update.zip package from /data/ota_package. I don't know if this file still exist after update.

    Said this you don't need vbmeta for rooting. Just a copy of your boot.img to patch it with magisk. Then flash it from PC and fastboot mode.

    You can check the @Giovix92 excellent notes on GitHub here:


    If you don't trust the shared boot.img file, you can dump yours from the phone partition. There are few methods for this. If I'm not wrong: booting into TWRP and dump raw data, SP Tool, or mtkclient. Cheers.
  • 15
    SO finally I successfully rooted with TWRP and root access.thanks to all developers @Eastw1ng @TheMalachite

    Following are all download links combined in one post Also there are two threads like unlocking boot loader and twrp but there are some steps are not mentioned which we must need to understand so see the video tutorial at the end of thread.
    If you have issues please post comment I will try to solve at my best

    NOTE: REMOVE ALL PASSWORD AND PINS ON PHONE BEFORE FLASHING TWRP
    All data will be erased so keep backup

    Download:
    TWRP IMAGE:

    Vbmeta image:


    Mediatek USB VCom drivers:




    ADB AND FASTBOOT DRIVERS(WHEN FASTBOOT NOT DETECTING ONLY)


    magisk v24 zip:


    magisk 23 apk:


    CMD COMMNADS HIT ENTER:


    1)detect adb devices:


    adb devices


    2)Reboot to bootloader mode:
    adb reboot bootloader


    3)To detect FASTBOOT devices:


    fastboot devices


    4)To OEM unlock:
    fastboot flashing unlock


    5)To flash Vbmeta image:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img


    6) flash twrp image:
    fastboot flash recovery recoveryname.img


    7)Reboot from FASTBOOT mode to recovery:
    fastboot reboot recovery


    If you have any issue follow this tutorial correctly
    4
    Patched boot image flashing replace u r stock boot imge and this twrp fashing of magisk also patches the stock boot image.
    Nothing different
    Just a little correction: it is, in fact, different.
    By patching the boot.img, you'll avoid (as expected) flashing the magisk zip, that avoids permanent TWRP and other patches applied to the system directly. It's not only a boot.img matter, it's a general OS matter. Also, reduces the risk of boot failing since recovery stays fully stock at every reboot*. One thing less to care about.

    Since it is kown that oplus likes to stop booting whenever root is available (hey there OPLUS_ROOT_CHECK), patched boot.img is the only safest way to root it, as of now. No bootloops, no problems.

    * Note: this happens because, if the recovery is different and there isn't any patch for stopping this process, it'll get overwritten at boot with the stock recovery present into /system. Magisk tends to patch this process in order to NOT overwrite it.
    1
    This worked great! Only problem I had was unlocking the bootloader and flashing TWRP without booting up caused the stock recovery to overwrite it again for some reason. After repeating the steps after unlocking it worked. Also, if you have the same problem as me with Magisk being unable to bypass the safety net, try this:

    I wish I found this before I sunk hours into learning what build prop editing is :p
    1
    Worked like a charm on a DN2103 OxygenOS v11.3 phone.

    Thank you.
    1
    Hey roldev!

    1) I was already wondering if that was the reason. Thanks for clearing that up!
    2) Which updater do you mean? I updated my phone using Settings -> Software Update. I'm not seeing the image file in any of my folders. Also, do I need to use the "empty" vbmeta or can I use the real one too if my goal is to root my phone?

    You need to be rooted, to obtain the update.zip package from /data/ota_package. I don't know if this file still exist after update.

    Said this you don't need vbmeta for rooting. Just a copy of your boot.img to patch it with magisk. Then flash it from PC and fastboot mode.

    You can check the @Giovix92 excellent notes on GitHub here:


    If you don't trust the shared boot.img file, you can dump yours from the phone partition. There are few methods for this. If I'm not wrong: booting into TWRP and dump raw data, SP Tool, or mtkclient. Cheers.