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

[Raygen]

/*
* 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.
*/

This project is no longer actively mantained, help yourself in the comments! - OP switched to a custom ROM - AndroidFileHost is no longer available for uploads (downloads are still available)

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:​

• ADB & Fastboot drivers + MTK VCOM drivers
• PartitionsBackupper
• Python
• Mtkclient + UsbDk

Instructions:

• .img and .bin files are the same. Just rename them as you need.
• If you are on Android 11: Rollback guide from C.01/C.05 to Android 10

Spoiler: How to install and use Mtkclient (Windows)

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.
   2. Connect the phone via usb to the pc, 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, by reporting "device detected " in the cmd. Release all the buttons as soon as the phone is detected.
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)".
   3. 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" -> and change it to "USB serial device".
   4. Sometimes it likes to revert itself back to "MediaTek USB Port", so leave Device manager open to keep an eye on it.
   5. If the phone keeps rebooting itself out of BROM mode, try to be fast when changing the settings inside Device manager. Keep trying until you see that "USB serial device" has stick.
   6. If Mtkclient freezes on "waiting for preloader VCOM", or the phone keeps rebooting itself out of BROM mode, keep rebooting the phone into BROM mode without letting go of the buttons, without disconnecting it from the pc, and without closing Mtkclient. And release all the buttons just when the phone has been detected. (It could need 2 to 3 reboots. If more, disconnect the cable and retry).
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.

Spoiler: OLD METHOD: ReLive DVD iso (Linux)

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.
   2. Connect the phone via usb to the pc, 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, by reporting "device detected " in the cmd. Release all the buttons as soon as the phone is detected.
   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.

↓​

Spoiler: Flash Stock firmware with UNLOCKED bootloader

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.

Spoiler: For LOCKED bootloader

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

Spoiler: Fix corrupted fastboot / preloader partition

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

Spoiler: Flash Stock firmware via Mtkclient

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

Spoiler: My phone went into a bootloop after root!

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​

 

[pankspoo]

Can we flash this rom On locked bootloader also can we use this for Indian DN2101

 

[Raygen]

Can we flash this rom On locked bootloader also can we use this for Indian DN2101

Right, always forgot about the bootloader. Yup that needs to be unlocked.

About the Indian model, I dunno really. I heard you guys have the A.13 update instead of the A.12 so, I wouldn't risk it. Many system partitions could still be the same for both models though.

With the tool included you can extract a stock rom of your phone anyway, if you, revert it back to stock first obv.

 

[muppetz]

/*
 * 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 before asking or use anything on this thread.
 */

OxygenOS 11.3 A.12 EU Full Stock (except vbmeta..) Firmware for the OnePlus Nord 2
Extracted with PartitionsBackupper (included in the .zip)​

Requirements:​

• ADB & Fastboot + Google & MTK drivers
• Unlocked bootloader

Instructions:

1. If your phone is still not completely fcked up, and even if it is, do a full backup with the included .bat first + a Nandroid backup + Internal storage backup. (better safe than RMA it)
2. Extract all files in the same directory of adb & fastboot (usually the "platform-tools" folder)
3. Run the included .bat to flash all partitions with fastboot.
4. I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.

DOWNLOAD
Gdrive
​

PASSWORD ???

 

[Raygen]

PASSWORD ???

There's no password.

 

[muppetz]

There's no password.

What's the point ? Archive is encrypted . So , if I understand correctly , [STOCK][FULL-ROM] OxygenOS_11.3_A.12 EU contain your's personal data and cannot be open or decrypted ? Only necessary information is ".bat" ?

 

[Raygen]

What's the point ? Archive is encrypted . So , if I understand correctly , [STOCK][FULL-ROM] OxygenOS_11.3_A.12 EU contain your's personal data and cannot be open or decrypted ? Only necessary information is ".bat" ?

I've reuploaded the .zip, please try again

 

[muppetz]

Now we talking ... It's fine now , thank you!!!

 

[IgorSamsonov]

this firmware will not help if you erased some system partitions and the wi-fi bluetooth and camera do not work? ((

 

[exis_tenz]

Way to go, Raygen! Thank you very much!

 

[Raygen]

this firmware will not help if you erased some system partitions and the wi-fi bluetooth and camera do not work? ((

If the erased partitions include the persist partition, then I guess your only way is RMA.
The persist partition contains calibration data unique to your device only. It's not recoverable unless you've made a backup

 

[pankspoo]

/*
 * 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 before asking or use anything on this thread.
 */

OxygenOS 11.3 A.12 EU Full Stock Firmware for the OnePlus Nord 2 DN2103
Extracted with PartitionsBackupper (included in the .zip)​

Specifics:​

• Vbmeta is not stock
• Fastboot is already unlocked

Requirements:​

• ADB & Fastboot + Google & MTK drivers

Instructions:

For unlocked bootloader:​

1. If your phone is still not completely fcked up, and even if it is, do a full backup with the included .bat first + a Nandroid backup + Internal storage backup. (better safe than RMA it)
2. Extract all files in the same directory of adb & fastboot (usually the "platform-tools" folder).
3. Run the included .bat to flash all partitions with fastboot.
4. I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.

​

For locked bootloader:​

1. Download and install mtkclient (I reccomend to download the Re LiveDVD iso and flash it on a pendrive with Rufus).
2. Extract just the seccfg.img partition from the zip.
3. Place the seccfg.img in the same folder with the mtk executable (in the Re LiveDVD, it's the /opt/mtkclient directory)
4. Disconnect the phone from the pc, and start mtkclient (MTK on the desktop of the Re LiveDVD).
5. Backup your seccfg partition first! With the command python mtk r seccfg seccfg.bin
6. 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.
   2. As soon as it turns off, press and hold all 3 buttons (Vol+, Vol-, and Power) and connect the usb cable.
   3. The script should find your phone and start the backup. Release the buttons.
7. Now, disconnect the phone, and close and reopen mtkclient.
8. Write the seccfg.img partition with the command python mtk w seccfg seccfg.img, press Enter, and reconnect the phone as explained before.
9. You should now have an unlocked bootloader!

DOWNLOAD
Gdrive
​

Can you give me that specific file
seccfg.img(does it specific to regions or can be used for all)
Donna want to download that large file
And also can you explain that after flashing that mtk client using Rufus how to load that did we need to make it as boot able pendrive something?

 

[martinwildi]

/*
 * 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 before asking or use anything on this thread.
 */

OxygenOS 11.3 A.12 EU Full Stock Firmware for the OnePlus Nord 2 DN2103
Extracted with PartitionsBackupper (included in the .zip)​

Specifics:​

• Vbmeta is not stock
• Fastboot is already unlocked

Requirements:​

• ADB & Fastboot + Google & MTK drivers

Instructions:

For unlocked bootloader:​

1. If your phone is still not completely fcked up, and even if it is, do a full backup with the included .bat first + a Nandroid backup + Internal storage backup. (better safe than RMA it)
2. Extract all files in the same directory of adb & fastboot (usually the "platform-tools" folder).
3. Run the included .bat to flash all partitions with fastboot.
4. I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.

​

For locked bootloader:​

1. Download and install mtkclient (I reccomend to download the Re LiveDVD iso and flash it on a pendrive with Rufus).
2. Extract just the seccfg.img partition from the zip.
3. Place the seccfg.img in the same folder with the mtk executable (in the Re LiveDVD, it's the /opt/mtkclient directory)
4. Disconnect the phone from the pc, and start mtkclient (MTK on the desktop of the Re LiveDVD).
5. Backup your seccfg partition first! With the command python mtk r seccfg seccfg.bin
6. 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.
   2. As soon as it turns off, press and hold all 3 buttons (Vol+, Vol-, and Power) and connect the usb cable.
   3. The script should find your phone and start the backup. Release the buttons.
7. Now, disconnect the phone, and close and reopen mtkclient.
8. Write the seccfg.img partition with the command python mtk w seccfg seccfg.img, press Enter, and reconnect the phone as explained before.
9. You should now have an unlocked bootloader!

DOWNLOAD
Gdrive
​

Hi
I used your method to backup my phone, and restore your OxygenOS 11.3 A.12 EU Full Stock. The process went fine, but the phone doesnt boot after that. the phones shows this message:

fastboot flashing unlock shows "fastboot: error: Command failed"
if i want to flash any image or TWRP, i get "FAILED (remote: 'not allowed in locked state')"
fastboot getvar all tells me: (bootloader) unlocked: no
(it was unlocked before restore..?)

should i try your "For locked bootloader:" method? it sounds "funny"

 

[pankspoo]

Hi
I used your method to backup my phone, and restore your OxygenOS 11.3 A.12 EU Full Stock. The process went fine, but the phone doesnt boot after that. the phones shows this message:

View attachment 5470935

fastboot flashing unlock shows "fastboot: error: Command failed"
if i want to flash any image or TWRP, i get "FAILED (remote: 'not allowed in locked state')"
fastboot getvar all tells me: (bootloader) unlocked: no
(it was unlocked before restore..?)

should i try your "For locked bootloader:" method? it sounds "funny"

Yes try that unlocking bootloader and let me know can u give me that scccf. Img file as u downloaded whole firmware

 

[Raygen]

Hi
I used your method to backup my phone, and restore your OxygenOS 11.3 A.12 EU Full Stock. The process went fine, but the phone doesnt boot after that. the phones shows this message:

View attachment 5470935

fastboot flashing unlock shows "fastboot: error: Command failed"
if i want to flash any image or TWRP, i get "FAILED (remote: 'not allowed in locked state')"
fastboot getvar all tells me: (bootloader) unlocked: no
(it was unlocked before restore..?)

should i try your "For locked bootloader:" method? it sounds "funny"

That's odd, the rom is already unlocked by itself. I'll see if any others encounter the same issue.

The locked bootloader method should revert it back to unlocked.

Can you give me that specific file
seccfg.img(does it specific to regions or can be used for all)
Donna want to download that large file
And also can you explain that after flashing that mtk client using Rufus how to load that did we need to make it as boot able pendrive something?

The seccfg has been added to download as a separate file in the instructions

 

[kkdamion]

can you be more specific about the "locked bootloader methed" i cant get to figure out how get it working under windows.

 

[Raygen]

can you be more specific about the "locked bootloader methed" i cant get to figure out how get it working under windows.

Me neither sincerly. Since you would also need to install the dependecies for the kamakiri attack for our SoC, and there are no instructions to install them on Windows.
I've just downloaded the ready-to-go live dvd .iso and flashed it to a pendrive.

 

[jis251]

HI, again
I have had prbs with A.12 update - apps force close, sometimes OS doesn't accept my screen lock psw (numbers), sometimes stuck on boot, but I have been able to recover with force reboot. But now I am stuck on boot. Stuck where we have red dot and 2 white dots, it boots few times itself after waiting long time and then it boots to recovery (twrp).
Does your A.12 wipe/destroy user data? If it does perhaps I do factory reset and start from scrats. Or does anyone have idea how I can recover?
I tried to flash ota.zip (I have it stored) First I flashed A.11 boot.ini and then I tried to flash ota.zip but it end up with error 1. And before that there was message that system has been opened as R/W xx times. Last 29.11, unable to use metadata to correct errors. system partition fails to recover. (flashing done with TWRP).
Thank you

 

[pankspoo]

Me neither sincerly. Since you would also need to install the dependecies for the kamakiri attack for our SoC, and there are no instructions to install them on Windows.
I've just downloaded the ready-to-go live dvd .iso and flashed it to a pendrive.

I didn't understood means u have used iso file and flashed it in Penddrive then how to use it on windows (I think it's for Ubuntu OS)
Also seffc image is from A12 I am. Using A13 can i use thats

 

[kkdamion]

the livedvd, you used it how?

Me neither sincerly. Since you would also need to install the dependecies for the kamakiri attack for our SoC, and there are no instructions to install them on Windows.
I've just downloaded the ready-to-go live dvd .iso and flashed it to a pendrive.