Development [STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide

Search This thread

muppetz

Senior Member
Sep 27, 2015
231
74
I upgraded to Oxygen 12open beta, cant enter to bootloadedr, so I used mtkclient to downgrade Oxygen 11 and then I couldn't boot, black screen and hard bricks, maybe it's anti-rollback, I don't know how to solve it . any one has solution?


"Oxygen Updater" apk has a thread regarding A12 beta , you can download A11 rollback zip file from them but it will get you to A11 indian version .
 

valfr7e

New member
May 6, 2022
1
0
Thanks for all the help, I followed all the instructions here and now I got back my phone with stock firm and flashing locked but now I cant set a lock screen password it just doesnt work. In some desesperate tries to recover the phone I've deleted locksettings.db I dont know if this can be the prob. Can anybody could share persist.img to reflash that partition on my phone? thanks
 
Last edited:

kaiseryeahhh

Senior Member
Oct 31, 2008
112
16
I have a problem, I have returned to the EU rom and perfect, when doing the flash lock, now it tells me that it can not boot.
The problem I have is that to enter fastboot I can only do it from adb (with the phone booted) with the buttons I am not able to enter fastboot (I can only go to recovery).
What can I do?
 

Raygen

Senior Member
Feb 21, 2014
122
55
Mantova
Thanks for all the help, I followed all the instructions here and now I got back my phone with stock firm and flashing locked but now I cant set a lock screen password it just doesnt work. In some desesperate tries to recover the phone I've deleted locksettings.db I dont know if this can be the prob. Can anybody could share persist.img to reflash that partition on my phone? thanks
The persist partition is unique to your phone only, you cannot flash one from another phone.
If you didn't make a backup of it, only way is to send it back for warranty.

I have a problem, I have returned to the EU rom and perfect, when doing the flash lock, now it tells me that it can not boot.
The problem I have is that to enter fastboot I can only do it from adb (with the phone booted) with the buttons I am not able to enter fastboot (I can only go to recovery).
What can I do?
For locking the bootloader you need to have everything stock, vbmeta included, or it will not boot telling you the boot partition is corrupted.

You should still be able to enter fastboot mode by disconnecting the usb cable (if connected) and hold Power + Vol- at boot.
If it's not working, try the related guides with Mtkclient.
 
  • Like
Reactions: kaiseryeahhh

kaiseryeahhh

Senior Member
Oct 31, 2008
112
16
The persist partition is unique to your phone only, you cannot flash one from another phone.
If you didn't make a backup of it, only way is to send it back for warranty.


For locking the bootloader you need to have everything stock, vbmeta included, or it will not boot telling you the boot partition is corrupted.

You should still be able to enter fastboot mode by disconnecting the usb cable (if connected) and hold Power + Vol- at boot.
If it's not working, try the related guides with Mtkclient.
In the end with the mtkclient live CD I was able to revive it.
Thank you very much.
 

Quercy

Member
Oct 2, 2016
32
4
OnePlus Nord 2 5G
I need help. Once again my One Plus Nord 2 with root went into bootloop. But this time unable to access the fastboot. It does not see it. If I connect an old One Plus 5 it's ok. I tried your procedure to install MTKclient but I got the error 'File "C:\Users\Home\Downloads\mtkclient-main\mtk_gui", line 6, in <module> import mock ModuleNotFoundError: No module named ' mock" when I enter the command "python mtk_gui". An idea ? I installed another MTKclient tool but without GUI and it's ok I manage to launch the "python mtk payload" command without error and connect my smartphone in brom mode. But I want to be able to use your MTKclient. Thanks a lot for your help. I guess in my case I will have to use procedure 3 or 4???
 

Raygen

Senior Member
Feb 21, 2014
122
55
Mantova
I need help. Once again my One Plus Nord 2 with root went into bootloop. But this time unable to access the fastboot. It does not see it. If I connect an old One Plus 5 it's ok. I tried your procedure to install MTKclient but I got the error 'File "C:\Users\Home\Downloads\mtkclient-main\mtk_gui", line 6, in <module> import mock ModuleNotFoundError: No module named ' mock" when I enter the command "python mtk_gui". An idea ? I installed another MTKclient tool but without GUI and it's ok I manage to launch the "python mtk payload" command without error and connect my smartphone in brom mode. But I want to be able to use your MTKclient. Thanks a lot for your help. I guess in my case I will have to use procedure 3 or 4???
Looks like I've forgot to add a step in the installation guide, my bad. Please type "pip3 install -r requirements.txt" in the terminal before starting Mtkclient.

I'd suggest to go with the "fix corrupted fastboot partition" procedure yes.
I've also added a procedure for the bootloop issue with root
 
Last edited:

Quercy

Member
Oct 2, 2016
32
4
OnePlus Nord 2 5G
Thank you Raygen I will try again. But my OnePlus is going to be repaired. I think during my testing mode connection BROM there was a power surge on during usb connection and now is dead and it will not power on. 😭
 

guaro94

New member
May 27, 2015
3
0
It seems like mtkclient cant recognize the phone in BROM mode (tried all the stuff you said). Hope there will be a way to solve soon
 
Help please!

I flashed the Pixel Experience on my Nord 2.
Then I wanted to go back to oxygen OS. I followed the procedure "flash stock firmware with unlocked bootloader"
I did not make a backup (yes I know).

I can get into fastboot mode and trwp recovery,
in Mtk client its stuck on preloader.

What can I do?
 

Raygen

Senior Member
Feb 21, 2014
122
55
Mantova
Help please!

I flashed the Pixel Experience on my Nord 2.
Then I wanted to go back to oxygen OS. I followed the procedure "flash stock firmware with unlocked bootloader"
I did not make a backup (yes I know).

I can get into fastboot mode and trwp recovery,
in Mtk client its stuck on preloader.

What can I do?
Since fastboot is working, re-flashing the ROM through it doesn't change anything?
What's the issue with the installation, does it bootloops?
Mtkclient is stuck trying to flash preloader or is a connection issue with the device?
 
Since fastboot is working, re-flashing the ROM through it doesn't change anything?
What's the issue with the installation, does it bootloops?
Mtkclient is stuck trying to flash preloader or is a connection issue with the device?
I got stuck in bootloop after the first try. The word android appeared on the screen for a while and than it rebooted.
Then I tried to sideload pixel experience via twrp en got again a bootloop.

So I thougt to revert to the method via mtk clien, but it cant connect because its waiting on preloader Vcom.
Schermafbeelding 2022-05-19 190206.png
 
Last edited:

Raygen

Senior Member
Feb 21, 2014
122
55
Mantova
@Raygen . So now i once again have a bootloop where I get to the screen with the word android on it. The loop took aprox. 4-5 minutes.

I used the fastboot oem unlock and then used partionbackupper to restore.
I cannot offer support for mtkclient myself. If the methods to fix the connections issue available in the main thread don't work, I suggest to search for a solution in the original GitHub project page.
If you find a fix, please report it here so I can add it to the main thread for future use.
As an alternative, you can use the old method, with the live DVD iso of Mtkclient.
Be sure you're rebooting the phone in BROM mode in the right way instead of Preloader mode
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi, I don't know if this is working but instructions found here: https://gist.github.com/Giovix92/c7e69123dbc51adf3f3a26f9c3c0208e#rooting says that the rooting problem comes from permanent TWRP + root
    I've asked if other users tested this but haven't got any answer so far: https://forum.xda-developers.com/t/tutorial-twrp-and-root-nord-2.4340477/post-87060493
  • 13
    /*
    * Your warranty is... still valid!
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed.
    * Please do some research yourself before asking or use anything on this thread.
    * I do not offer private assistance via Telegram or any other social outside XDA.
    */

    OxygenOS 11.3 EU Full Stock Firmwares for the OnePlus Nord 2 DN2103
    A.20

    Specifics:

    • This rom will not overwrite your userdata or metadata partition.
    • This rom will not overwrite your IMEI, sensors calibration data, or bootloader unlock status.
      Since these partitions are not included: seccfg, nvcfg, nvdata, nvram, persist, proinfo, protect1, protect2.
    • These partitions are not included since are present in the super partition: my_*, odm, product, system, vendor.
    • The vbmeta partition is not stock.
    • The vbmeta partition is stock. A vbmeta_patched partition for root users can be found attached to this thread.

    Requirements:


    Instructions:

    1. Download and, install Python, extract Mtkclient, and install UsbDk.
    2. Open a terminal (cmd) inside the extracted Mtkclient folder, and type the command pip3 install -r requirements.txt
    3. After the installation has completed, type the command python mtk_gui to start Mtkclient GUI.
    4. Reboot your phone in BROM mode:
      1. Turn off your phone, and connect the usb cable only to the pc.
      2. After it turns off, connect the usb cable to the phone and immediately press and hold all 3 buttons (Vol+, Vol-, and Power).
      3. The screen of the phone should remain completely black and Mtkclient should find your phone and connect to it. Release all the buttons immediately, as soon as the phone is found.
    5. If the phone won't connect properly, check that's being correctly detected in device manager:
      1. Open Device manager.
      2. While the phone is connected in BROM mode to the pc, search for "MediaTek USB Port" under "Ports (COM and LPT)". If it's not being detected properly, a yellow warning triangle should be visible.
      3. To fix this, right click on it -> Choose "Update driver" -> "Browse my computer for driver software" -> "Let me pick from a list of available drivers on my computer" -> Choose "USB serial device".
      4. Sometimes it likes to revert itself back to "MediaTek USB Port", so leave Device manager open and set it back again as "USB serial device" if it happens.
      5. If Mtkclient freezes, or the phone keeps rebooting itself out of BROM mode, try to reboot the phone into BROM mode again without disconnecting it from the pc, and without closing Mtkclient. (Try to be fast in device manager, before it reboots)
    6. You can now use Mtkclient GUI. (see the guides below)
    7. After you're done flashing, you can exit BROM mode by press and hold Vol+ and Power.
    1. Download and install the Re LiveDVD iso of mtkclient and flash it on a pendrive with Rufus.
    2. Create two new folders named "img" and "img_bak" in the pendrive you just flashed with Rufus, and paste inside /img all the files and images you will need.
    3. Start the mtkclient live usb. The login credentials are "user" for both name and password.
    4. Note! the keyboard is set to german by default in the liveusb. To change it, as soon as you boot up in the desktop, click on the "DE" blue text up on the right.
    5. Copy the whole /img and /img_bak directories into the /opt/mtkclient directory.
    6. Disconnect the phone from the pc, and start the MTK script on the desktop of the live usb.
    7. Write the desired command (see below) and press Enter.
    8. As soon as you press Enter, the script will start searching for an attached phone in BROM mode.
      To reboot your phone in BROM mode:
      1. Turn off your phone, and connect the usb cable only to the pc.
      2. As soon as it turns off, press and hold all 3 buttons (Vol+, Vol-, and Power) and immediately connect the usb cable to the phone side.
      3. The screen of the phone should remain completely black and the script should find your phone and continue with the command. Release all the buttons immediately, as soon as the phone is found.
      4. It is necessary to disconnect the phone, close and reopen the MTK script on the desktop, and reconnect the phone in BROM mode, every time you want to run another command.
    9. To backup any partitions on your phone, use the command python mtk r partition_name_1,partition_name_2,partition_name_3,... img_bak/partition_name_1.img,img_bak/partition_name_2.img,img_bak/partition_name_3.img,.... Example: python mtk r boot,vbmeta,super img_bak/boot.img,img_bak/vbmeta.img,img_bak/super.img. You'll find all your backups inside the /opt/mtkclient/img_bak folder (copy them back to your pendrive to not loose them).
    10. To write all the partitions present in the /img directory to your phone, use the command python mtk wl img. Be sure that the file names have the same name of the partition they're meant to write! Example: The file named "boot.img" <---> Will write the "boot" partition.
    11. Use the command python mtk r preloader img_bak/preloaderdump_backup.bin --parttype=lu1 to backup your preloader partition. You'll find your backup inside the /opt/mtkclient/img_bak folder (copy it back to your pendrive to not loose it).
    12. Use the command python mtk w preloader img/preloaderdump_stock.bin --parttype=lu1 to flash the preloader partition.



    1. If your phone is still not completely fcked up, and even if it is, do a full backup with PartitionsBackupper first + a TWRP backup + Internal storage backup. (better safe than RMA it)
    2. Download the stock firmware .zip, and the latest version of PartitionsBackupper.
    3. Extract both of them in the same directory where adb.exe & fastboot.exe are located (usually the "platform-tools" folder).
    4. Run PartitionsBackupper, choosing the restore option, to flash all partitions with fastboot.
    5. Reboot into the stock recovery and do a full data format before going back messing around. It usually wipes better than TWRP.

    1. Follow this guide only if the command fastboot flashing unlock does not work.
    2. Download and extract the attached seccfg.img unlocked partition.
    3. Download and extract the boot.img, recovery.img, and vbmeta.img from the stock firmware .zip file.
    4. Put all 4 images in a new empty folder, and do not rename the files.
    5. Open Mtkclient (see the guide above).
    6. In the first tab "Read partition(s)": Select the seccfg, boot, recovery, and vbmeta partitions. Click "Read" to backup them up. Save them in a different folder from the one created before.
    7. Now in the second tab "Write partition(s)": Choose "Select from directory" and choose the new folder created before. It should automatically place all 4 images in the correct corresponding partitions. Click "Write" to flash them.
    8. If you're stuck in a bootloop after this, some users have reported that flashing vbmeta a second time fixed it.
    9. You should now have an unlocked bootloader

    This procedure has been successfully tested by an external user.
    1. This guide is useful if your device is not getting recognized via fastboot.
    2. Download and extract the attached preloaderdump_stock.bin image.
    3. Download and extract the boot, recovery, vbmeta, and super images from stock firmware .zip file.
    4. Put the 4 images extracted from the stock firmware, in a new empty folder, and do not rename the files. Do not put the preloader image in this folder.
    5. Open Mtkclient (see the guide above).
    6. In the first tab "Read partition(s)": Select the boot, recovery, vbmeta and super partitions. Click "Read" to backup them up. Save them in a different folder from the one created before.
    7. In the fourth tab "Flash Tools": Choose "Read preloader" to backup it up. Save it in a different folder from the one created before.
    8. Still in the fourth tab "Flash Tools": Choose "Write preloader" and flash the downloaded preloaderdump_stock.bin image.
    9. Last, in the second tab "Write partition(s)": Choose "Select from directory" and choose the new folder created before. It should automatically place all 4 images in the correct corresponding partitions. Click "Write" to flash them.
    10. If you're stuck in a bootloop after this, some users have reported that flashing vbmeta a second time fixed it.
    11. You should now have a working fastboot connnection

    This procedure has been successfully tested by an external user.
    1. This guide is useful as a last resort. If you are not able to restore the stock rom in any other way.
    2. Download the stock firmware and extract the folder inside the .zip file.
    3. Open Mtkclient (see the guide above).
    4. In the first tab "Read partition(s)": Choose "Select all partitions" and click "Read" to backup them up. Save them in a different folder from the one with the stock firmware.
    5. Now in the second tab "Write partition(s)": Choose "Select from directory" and choose the folder with the stock firmware. It should automatically place all the images in the correct corresponding partitions. Click "Write" to flash them.
    6. If you're stuck in a bootloop after this, try flashing the preloader and seccfg partitions following the guides above, and then repeat this procedure a second time.
    7. Your device should hopefully boot now

    Yeah.. Looks like OxygenOS doesn't really like to be rooted. Your phone will occasionally go into a bootloop without any notice or known reason (so far).​
    The cause of this behavior is still unknown to me, if you are able to find any explanation or better solution please post it here!
    The only solution I know so far, is to just format your phone back to stock, and then restore your userdata partition:​
    1. Make a backup of your Internal storage, recovery, boot, vbmeta, and userdata partitions. Both with PartitionBackupper or Mtkclient, what's more handy for you.
    2. Flash the stock firmware on the phone.
    3. Format data with the stock recovery.
    4. Restore your previously backupped partitions and storage.
    5. When booting to system for the first time, it's possible your interface / GUI will be malfunctioning. Just reboot one more time to fix this.
    6. Finally, go into the setting and reset your password / sequence / PIN.

    Thanks to Zombnombs, TheWing, SeBright, Giovix92 for the help!




    DOWNLOAD
    AndroidFileHost
    3
    i also had some sort of a victory :).
    my device was also stuck (Post#13)
    only flashing seccfg.img with the pendrive didnt work, still stuck, and still locked bootloader
    i had to flash the correct versions of boot.img, recovery.img and vbmeta.img via mtktools (in my case A.07)
    now i can start the phone, it's on the welcome screen
    and it seems to have locked bootloader right now.

    i have to see later, what i'm doing now :)

    @All: thanks for your help!
    3
    I've reuploaded the file, please try again
    3
    Are you using windows ? check it in device-manager when you are in "userspace-fastboot" it should report as adb-bootlaoder-interface. If not click on use driver - > adb bootlaoder interface

    Thank you! You beautiful person Kingslayer! It's unbricked!

    Sometimes you overlook the obvious when you're dealing with issues, and for me it was as you said - not installing the device as 'adb bootloader interface' from device manager while in the userspace fastboot. I also started PartitionBakckupper from TWRP as you said so that may have helped as well. But also, as a note for anyone who may face this issue - after it all completed, I received the same red boot error message as earlier, but by booting into fastboot from that screen and reflashing the vbmeta.img from the latest a.16 stock in the OP, it allowed it to boot fine. Is that what you meant at the end there?

    Fingerprint scanner and camera are working fine as well, so the persist is actually still intact too.

    Bloody hell, what a relief. Thank you again man, you saved me the stress of an RMA request I was prepared to make in the morning. And thanks as well Raygen for the tool, once you understand how to actually work it, it does the trick.
    3
    Hey there! Nord 2 5G user and, mostly, developer.
    @Raygen I guess you can add another 'usecase' to the overall guide: managed to hard brick the device. Basically wasn't booting in any mode: fastboot, recovery or whatever; achieved this by flashing boot.img into recovery partition (don't ask me why lol).

    By the way, used your "Locked bootloader" guide with a little modification:
    - I've also added lk & lk2 from my backup, because those apparently are 'damaged' by the previous command (don't ask me how cause I don't have any clue about it).
    - Instead of using
    Bash:
    python mtk wl img
    as you described, I just used a one-liner command based on mtkclient's README:
    Bash:
    python mtk w lk,lk2,boot,recovery,vbmeta lk.img,lk2.img,boot.img,recovery.img,vbmeta.img
    The syntax is the following one:
    Code:
    python mtk w name_1,name_2 name_1.img,name_2.img
    The one-liner command basically flashes everything in one shot, and afterwards, when you disconnect the usb cable and power it on, it *should* boot up. If it doesn't, flash preloader like you did, re-trigger BROM mode and redo that one-liner command.
    Hard bricked intentionally another time to test this out and, at least, have some proofs. :)
    I could attach mines lk & lk2, if needed.

    Hope y'all like it! Cheers!