How To Guide TUTORIAL TWRP AND ROOT NORD 2

Search This thread

vincebay

Senior Member
Jun 18, 2010
77
0
Lausanne
Just bought a Nord 2 5G and wanted to know if your procedure in first post is always good with the device in latest version of Manufactturer ROM ?

Thanks
 

vincebay

Senior Member
Jun 18, 2010
77
0
Lausanne

E-Chan42

Senior Member
Nov 25, 2010
103
4
Ok, I'm in TWRP. Now my goals are to install Magisk and have TWRP persist between reboots.

Every time I select and install magisk's zip file TWRP restarts.
Every time I reboot the phone TWRP needs to be fastbooted back...

Any ideas on how to tackle this?

UPDATE: magisk 24 was linked in the OP magisk 23 worked fine. Any reason to update?
 
Last edited:

pankspoo

Senior Member
Jun 27, 2013
1,818
966
in front of ENCHILADA
Ok, I'm in TWRP. Now my goals are to install Magisk and have TWRP persist between reboots.

Every time I select and install magisk's zip file TWRP restarts.
Every time I reboot the phone TWRP needs to be fastbooted back...

Any ideas on how to tackle this?

UPDATE: magisk 24 was linked in the OP magisk 23 worked fine. Any reason to update?
Download and rename this file as .zip https://github.com/topjohnwu/Magisk/releases/download/v25.0/Magisk-v25.0.apk
Then flash it via twrp reboot and rename it again to apk and install
 

Audoghast

Member
Jun 13, 2022
9
0
Good evening.



I just tried to root a Oneplus Nord 2 5G (EU Edition) and got as far as:



fastboot flash recovery twrp.img



It always returns “error flashing partition” “volume full”



Unfortunately, the phone was upgraded to Android 12. Could that be the problem?

If so, how can I get back to Android 11 (bootloader is unlocked).

I do not want to fiddle too much with it, not to make things worse.



Thanks a lot for your help.



Audoghast
 

pankspoo

Senior Member
Jun 27, 2013
1,818
966
in front of ENCHILADA
Good evening.



I just tried to root a Oneplus Nord 2 5G (EU Edition) and got as far as:



fastboot flash recovery twrp.img



It always returns “error flashing partition” “volume full”



Unfortunately, the phone was upgraded to Android 12. Could that be the problem?

If so, how can I get back to Android 11 (bootloader is unlocked).

I do not want to fiddle too much with it, not to make things worse.



Thanks a lot for your help.



Audoghast
On Android 12 OnePlus removed fastbootmode so no unlocking nothing.
But how did u booted in fastbootmode on oos 12 i can't understand
 

Audoghast

Member
Jun 13, 2022
9
0
Hello again.

Thanks for the quick reply.

Since I only flashed one phone more than 10 years ago, I followed everything by the letter.
The video clearly asked to update the system software (at the time to version 10). There was no mention of the disappearance of fastboot on version 12.
I cannot remember to which version I updated. I may still have version 11.

In any case fastboot works and adb commands are being accepted. It can also be put in fastboot via VOL UP, DN & POWER.
The last successful step was flashing the vbmeta image.

TWRP flashing results in “error flashing partition” “volume full”.

What shall I do now? Is there any test to run?

I am seriously at a loss here since I am sitting in front of a bricked phone.

There should also be a warning out not to update to version 12.

I would really appreciate your help and do not want to try out thousands of ideas from other websites.

Thank you again.

Audoghast
 

lolahuop

New member
Jun 19, 2022
3
0
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
i am on the oxygen os 12.1 rightnow after i use the command adb reboot bootloader the device switches off and it says in small text ''the serial not match and fastboot verify fail'' let me know how to fix it asap
 

pankspoo

Senior Member
Jun 27, 2013
1,818
966
in front of ENCHILADA
i am on the oxygen os 12.1 rightnow after i use the command adb reboot bootloader the device switches off and it says in small text ''the serial not match and fastboot verify fail'' let me know how to fix it asap
No solution for that you need to revert back to oos11
 

pankspoo

Senior Member
Jun 27, 2013
1,818
966
in front of ENCHILADA
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 ?
Patched boot image flashing replace u r stock boot imge and this twrp fashing of magisk also patches the stock boot image.
Nothing different
 

gawain.j

Senior Member
Aug 11, 2010
57
11
Thanks for your answer, so custom rom is the only way if you want to have stable root I guess!
 

eternalstudent

New member
Jun 24, 2022
1
0
Hi, thanks for the guide and help here. I followed the steps, and was able to unlock bootloader, flash vbmeta, but flashing recovery and then booting into it is failing because of error : "unknown reboot target recovery"







fastboot: usage: unknown reboot target recovery

Before that,

0. My goals are just rooting, and preferably passing safety net. TWRP is not necessary, but I used it because it was in the guide.
1. I have Indian version
2. Android 11
3. Build DN2101_11_A.11
4. When downloading TWRP from here, version twrp-3.6.0_11-0-UNOFFICIAL-denniz.img cannot find any mirrors, so I had to download version twrp-3.5.2_11-0-UNOFFICIAL-denniz.img
5. I am using Linux , and ubuntu provided android-tools-adb / android-tools-fastboot packages for ADB and fastboot
6. Error when rebooting into recovery
Bash:
# fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (131072 KB)...
OKAY [  4.148s]
writing 'recovery'...
OKAY [  0.274s]
finished. total time: 4.422s
# fastboot reboot recovery
fastboot: usage: unknown reboot target recovery

7. Error when booting into downloaded image is
Bash:
# fastboot boot twrp.img
downloading 'boot.img'...
OKAY [  4.198s]
booting...
FAILED (status read failed (No such device))
finished. total time: 16.388s


Mr Vag had also posted similar error "unknown reboot target recovery" in this thread, but I didn't find any reply to it.

Any help would be appreciated greatly.
 

pankspoo

Senior Member
Jun 27, 2013
1,818
966
in front of ENCHILADA
Hi, thanks for the guide and help here. I followed the steps, and was able to unlock bootloader, flash vbmeta, but flashing recovery and then booting into it is failing because of error : "unknown reboot target recovery"







fastboot: usage: unknown reboot target recovery

Before that,

0. My goals are just rooting, and preferably passing safety net. TWRP is not necessary, but I used it because it was in the guide.
1. I have Indian version
2. Android 11
3. Build DN2101_11_A.11
4. When downloading TWRP from here, version twrp-3.6.0_11-0-UNOFFICIAL-denniz.img cannot find any mirrors, so I had to download version twrp-3.5.2_11-0-UNOFFICIAL-denniz.img
5. I am using Linux , and ubuntu provided android-tools-adb / android-tools-fastboot packages for ADB and fastboot
6. Error when rebooting into recovery
Bash:
# fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (131072 KB)...
OKAY [  4.148s]
writing 'recovery'...
OKAY [  0.274s]
finished. total time: 4.422s
# fastboot reboot recovery
fastboot: usage: unknown reboot target recovery

7. Error when booting into downloaded image is
Bash:
# fastboot boot twrp.img
downloading 'boot.img'...
OKAY [  4.198s]
booting...
FAILED (status read failed (No such device))
finished. total time: 16.388s


Mr Vag had also posted similar error "unknown reboot target recovery" in this thread, but I didn't find any reply to it.

Any help would be appreciated greatly.
U r fastboot drivers are not updated
 
  • Like
Reactions: eternalstudent

lolahuop

New member
Jun 19, 2022
3
0
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
I Have a Non Rooted Nord 2 And Have Stock recovery Installed. And Have Bootloader Unlocked How Do I Relock It Again? Please Help Me!
 

Audoghast

Member
Jun 13, 2022
9
0
Hello again.

Thanks for the quick reply.

Since I only flashed one phone more than 10 years ago, I followed everything by the letter.
The video clearly asked to update the system software (at the time to version 10). There was no mention of the disappearance of fastboot on version 12.
I cannot remember to which version I updated. I may still have version 11.

In any case fastboot works and adb commands are being accepted. It can also be put in fastboot via VOL UP, DN & POWER.
The last successful step was flashing the vbmeta image.

TWRP flashing results in “error flashing partition” “volume full”.

What shall I do now? Is there any test to run?

I am seriously at a loss here since I am sitting in front of a bricked phone.

There should also be a warning out not to update to version 12.

I would really appreciate your help and do not want to try out thousands of ideas from other websites.

Thank you again.

Audoghast
Hello everyone.

I had the „volume full“ error before and have now found the reason why which was quite embarrassing: my phone is a Oneplus Nord CE 5G and this is the wrong forum.
I do not know how I could overlook that but I did and I am sorry if anyone put in too much thought into my problem.
The TWRP.img file was wrong and hence the “volume full” message which appears in such cases.
The volume was not really full.

I will now move to the right forum here.

Thanks and goodbye.

Audoghast
 

Zombnombs

Senior Member
I Have a Non Rooted Nord 2 And Have Stock recovery Installed. And Have Bootloader Unlocked How Do I Relock It Again? Please Help Me!
you wil need to reflash your stock recovery image, stock boot image for your current version, and a stock vbmeta.img again. Preferably via MTKclient you can check the thread below for instructions.

 

Giovix92

Recognized Developer
Oct 22, 2015
1,716
1,747
21
Catanzaro, Italy
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.
 

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.