Development [STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide
- Thread starter Raygen
- Start date
Hello everyone. Please help. My phone turned into a brick because of my crooked hands. I tried to root, but something went wrong. As a result, as far as I remember (it was 2 months ago), I decided to return everything to the factory settings. Did not work out. Now, when I try to flash it, I get an error:
when I enter "fastboot flashing unlock" writes an error
FAILED (remote: '
Unlock operation is not allowed
and on phone: unlock filed
Next when trying "adb reboot bootloader":
:\Users\Ilya>adb reboot bootloader
error: no devices/emulators found
C:\Users\Ilya>adb reboot bootloader
error: no devices/emulators found
I understand that the bootloader is blocked. Can't unlock. I ask for help in this matter.
when I enter "fastboot flashing unlock" writes an error
FAILED (remote: '
Unlock operation is not allowed
and on phone: unlock filed
Next when trying "adb reboot bootloader":
:\Users\Ilya>adb reboot bootloader
error: no devices/emulators found
C:\Users\Ilya>adb reboot bootloader
error: no devices/emulators found
I understand that the bootloader is blocked. Can't unlock. I ask for help in this matter.
Hey people i need your help i have the euro version of the One Plus Nord 2 5g. I was on systemfirmeware A15 and did a magisk canary update. since then my phone won't boot anymore. I know tried to flash stock A15-EU files from mega. And it still dosen't boot.
Can anyone help I can install twrp. Did data format in twrp and stock recovery nothing help. I even relocked to Bootloader and still didn't help.
I use this for restore:
I attached te restore log.
@Raygen Are you aware of an issue like this ?
Let me know if you need to know more.
I now found out my device reports as DN2101 - is it possible i flashed an indian image or something? i live in west-europe.
and why can't i flash it back?
UPDATED PB.log
Can anyone help I can install twrp. Did data format in twrp and stock recovery nothing help. I even relocked to Bootloader and still didn't help.
I use this for restore:
I attached te restore log.
@Raygen Are you aware of an issue like this ?
Let me know if you need to know more.
I now found out my device reports as DN2101 - is it possible i flashed an indian image or something? i live in west-europe.
and why can't i flash it back?
UPDATED PB.log
Last edited:
Okay guys, there really needs to be some form of order to these guides, because everyone gives different methods and avenues for absolutely everything when it is effectively the same phone, and my situation has gone from bad to worse.
I'm pretty sure my phone is hard bricked after this guide. I had started with a magisk root, which broke WiFi and Bluetooth, so with flashing fixes trying to get back to stock to fix that I ended up breaking the recovery, which in turn took me back to the error message we saw at the beginning of this thread with people saying they addressed it with MTK. So I had to load up MTKClient Live OS, fine, and flashed the A.16 stock firmware images, but that didn't work, and now im pretty sure it's entirely hard bricked. Won't turn on at all.
Any suggestions before I try a warranty claim?
I'm pretty sure my phone is hard bricked after this guide. I had started with a magisk root, which broke WiFi and Bluetooth, so with flashing fixes trying to get back to stock to fix that I ended up breaking the recovery, which in turn took me back to the error message we saw at the beginning of this thread with people saying they addressed it with MTK. So I had to load up MTKClient Live OS, fine, and flashed the A.16 stock firmware images, but that didn't work, and now im pretty sure it's entirely hard bricked. Won't turn on at all.
Any suggestions before I try a warranty claim?
Okay so it managed to startup finally back here:
Before I make any more mistakes. What is the clear avenue from here
Edit-----
Alright I've managed to get back to fastboot and have PartitionBackup working. But I'm back to square one. I'm experiencing an issue after flashing Super, where it reboots to stock fastboot (not sure what it's called, says Fastbootd), and it hangs there. If I reboot back to the small text fastboot, it continues, but with serious sounding errors citing not available in locked state, but I'm pretty sure the bootloader is unlocked. Until it finishes and gets stuck on a boot loop.
I attached the PBlog.txt
I'll deal with it in the morning. If someone could help here I'd be eternally greatful, seriously.
Before I make any more mistakes. What is the clear avenue from here
Edit-----
Alright I've managed to get back to fastboot and have PartitionBackup working. But I'm back to square one. I'm experiencing an issue after flashing Super, where it reboots to stock fastboot (not sure what it's called, says Fastbootd), and it hangs there. If I reboot back to the small text fastboot, it continues, but with serious sounding errors citing not available in locked state, but I'm pretty sure the bootloader is unlocked. Until it finishes and gets stuck on a boot loop.
I attached the PBlog.txt
I'll deal with it in the morning. If someone could help here I'd be eternally greatful, seriously.
Last edited:
I got the same problem noone here explaind it very well!Okay so it managed to startup finally back here:
Before I make any more mistakes. What is the clear avenue from here
Edit-----
Alright I've managed to get back to fastboot and have PartitionBackup working. But I'm back to square one. I'm experiencing an issue after flashing Super, where it reboots to stock fastboot (not sure what it's called, says Fastbootd), and it hangs there. If I reboot back to the small text fastboot, it continues, but with serious sounding errors citing not available in locked state, but I'm pretty sure the bootloader is unlocked. Until it finishes and gets stuck on a boot loop.
I attached the PBlog.txt
I'll deal with it in the morning. If someone could help here I'd be eternally greatful, seriously.
The thing is this phone got 2 fastboot-modes:
1 fastboot reboot bootlaoder - "bootloader fastboot"
2 fastboot reboot fastboot - "userspace fastboot"
the partitions you can't flash is because you cant boot into the "userspace fastboot" after messing with the phone!
but don't worry you can easy fix it!
my recommend way is to go boot into bootloader fastboot (with key combo) and flash twrp + vbmeta from the twrp threat!
in twrp go into -> reboot -> reboot fastboot
then go and restore everything with partionsbackupper!
after 1 frist boot go into bootloader again and flash vbmeta (maybe not neccesery)
your phone should now boot again!
Hey,
So I've managed to flash twrp again, however when entering the twrp fastboot mode, the device is still undiscoverable.
Others in this thread said the stock "userspace fastboot" should have worked as well, but for some reason the device isn't being recognized in either of these methods. Only the small text "bootloader fastboot" shows the device, but I get errors there.
I've also tried flashing the provided preloader_ul1.bin in the OP, but that's made no difference in detecting the device in these modes.
I'm also pretty sure the persist is gone, as the partition shows 0mb. And the backup of these partitions failed in TWRP. So it looks like an RMA. I mean people give warnings about bricking your phone in rooting, but hell I didn't expect the guides to be this bad. I won't be rooting my replacement that's for sure.
Last edited:
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.
Persist partation is Device specific so author removed that from partation backup folder similarly he also removed nvdata(responsible for imei etc) and userdata.
U can not solve persist issue if you don't have your own backup of persist.
Even if you FALSH anyone's persist still u r issue will be reamains there only way is to go back to OP
I'm back, Question about unreliable behavior:
So far i've had my phone bootloop a couple of times after i rooted it back in november. First time it happened about after a month of use . With great help from forum member "Scarythib" i was able to revive my fully bricked phone. Another month went by and it somehow happened again after a reboot, another bootloop. Lucky i remembered what to do and after trying a few things i got it back running from scratch. And again a couple of days ago it happened again. Is there an explenation why this phone gets into bootloop after a few reboots? I have tried a few versions of Magisk as i read this could be the problem, but even the Canary edition is no good. It sucks this phone is not reliable when rooted, cause you always need a computer to get it back on its feet.
A twrp Nandroid seems to be not enough to fix a broken boot, nor partitionbackup doesn't help in my case.
My latest Fix procedure:
Open Powershell
Boot phone into Fastboot (Vol- & PWR buttons)
Connect USB
Command Fastboot flash recovery recovery_stock
command Fastboot reboot recovery
In stock recovery -> wipe data -> format data
Fastboot flash recovery twrp 3.6
Do a twrp restore to a recent nandroid backup
Reboot in fastboot
Command Fastboot flash persist persist_image.emmc (file from twrp backup to fix fingerprint scanner)
Fastboot reboot
So far i've had my phone bootloop a couple of times after i rooted it back in november. First time it happened about after a month of use . With great help from forum member "Scarythib" i was able to revive my fully bricked phone. Another month went by and it somehow happened again after a reboot, another bootloop. Lucky i remembered what to do and after trying a few things i got it back running from scratch. And again a couple of days ago it happened again. Is there an explenation why this phone gets into bootloop after a few reboots? I have tried a few versions of Magisk as i read this could be the problem, but even the Canary edition is no good. It sucks this phone is not reliable when rooted, cause you always need a computer to get it back on its feet.
A twrp Nandroid seems to be not enough to fix a broken boot, nor partitionbackup doesn't help in my case.
My latest Fix procedure:
Open Powershell
Boot phone into Fastboot (Vol- & PWR buttons)
Connect USB
Command Fastboot flash recovery recovery_stock
command Fastboot reboot recovery
In stock recovery -> wipe data -> format data
Fastboot flash recovery twrp 3.6
Do a twrp restore to a recent nandroid backup
Reboot in fastboot
Command Fastboot flash persist persist_image.emmc (file from twrp backup to fix fingerprint scanner)
Fastboot reboot
Last edited:
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
as you described, I just used a one-liner command based on mtkclient's README:
The syntax is the following one:
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!
@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
Bash:
python mtk w lk,lk2,boot,recovery,vbmeta lk.img,lk2.img,boot.img,recovery.img,vbmeta.img
Code:
python mtk w name_1,name_2 name_1.img,name_2.imgHard 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!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
11
I had firmware on Android 12, Extension. But in the end, I removed it and put the stock firmware on Android 11.
Thank you very much for the help, REDOTHELLO
I did all operations with MTK Client11Hi, 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
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:
- Download and, install Python, extract Mtkclient, and install UsbDk.
- Open a terminal (cmd) inside the extracted Mtkclient folder, and type the command
pip3 install -r requirements.txt - After the installation has completed, type the command
python mtk_guito start Mtkclient GUI. - Reboot your phone in BROM mode:
- Turn off your phone, and connect the usb cable only to the pc.
- After it turns off, connect the usb cable to the phone and immediately press and hold all 3 buttons (Vol+, Vol-, and Power).
- 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.
- If the phone won't connect properly, check that's being correctly detected in device manager:
- Open Device manager.
- 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.
- 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".
- 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.
- 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)
- You can now use Mtkclient GUI. (see the guides below)
- After you're done flashing, you can exit BROM mode by press and hold Vol+ and Power.
- Download and install the Re LiveDVD iso of mtkclient and flash it on a pendrive with Rufus.
- 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.
- Start the mtkclient live usb. The login credentials are "user" for both name and password.
- 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.
- Copy the whole /img and /img_bak directories into the /opt/mtkclient directory.
- Disconnect the phone from the pc, and start the MTK script on the desktop of the live usb.
- Write the desired command (see below) and press Enter.
- 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:- Turn off your phone, and connect the usb cable only to the pc.
- 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.
- 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.
- 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.
- 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). - 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. - Use the command
python mtk r preloader img_bak/preloaderdump_backup.bin --parttype=lu1to 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). - Use the command
python mtk w preloader img/preloaderdump_stock.bin --parttype=lu1to flash the preloader partition.
- 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)
- Download the stock firmware .zip, and the latest version of PartitionsBackupper.
- Extract both of them in the same directory where adb.exe & fastboot.exe are located (usually the "platform-tools" folder).
- Run PartitionsBackupper, choosing the restore option, to flash all partitions with fastboot.
- Reboot into the stock recovery and do a full data format before going back messing around. It usually wipes better than TWRP.
- Follow this guide only if the command
fastboot flashing unlockdoes not work. - Download and extract the attached seccfg.img unlocked partition.
- Download and extract the boot.img, recovery.img, and vbmeta.img from the stock firmware .zip file.
- Put all 4 images in a new empty folder, and do not rename the files.
- Open Mtkclient (see the guide above).
- 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.
- 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.
- If you're stuck in a bootloop after this, some users have reported that flashing vbmeta a second time fixed it.
- You should now have an unlocked bootloader
This procedure has been successfully tested by an external user.- This guide is useful if your device is not getting recognized via fastboot.
- Download and extract the attached preloaderdump_stock.bin image.
- Download and extract the boot, recovery, vbmeta, and super images from stock firmware .zip file.
- 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.
- Open Mtkclient (see the guide above).
- 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.
- In the fourth tab "Flash Tools": Choose "Read preloader" to backup it up. Save it in a different folder from the one created before.
- Still in the fourth tab "Flash Tools": Choose "Write preloader" and flash the downloaded preloaderdump_stock.bin image.
- 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.
- If you're stuck in a bootloop after this, some users have reported that flashing vbmeta a second time fixed it.
- You should now have a working fastboot connnection
This procedure has been successfully tested by an external user.- This guide is useful as a last resort. If you are not able to restore the stock rom in any other way.
- Download the stock firmware and extract the folder inside the .zip file.
- Open Mtkclient (see the guide above).
- 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.
- 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.
- 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.
- 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:- Make a backup of your Internal storage, recovery, boot, vbmeta, and userdata partitions. Both with PartitionBackupper or Mtkclient, what's more handy for you.
- Flash the stock firmware on the phone.
- Format data with the stock recovery.
- Restore your previously backupped partitions and storage.
- 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.
- Finally, go into the setting and reset your password / sequence / PIN.
Thanks to Zombnombs, TheWing, SeBright, Giovix92 for the help!
3i 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
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.3Hey 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 usingas you described, I just used a one-liner command based on mtkclient's README:Bash:python mtk wl imgThe syntax is the following one:Bash:python mtk w lk,lk2,boot,recovery,vbmeta lk.img,lk2.img,boot.img,recovery.img,vbmeta.imgThe 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.Code:python mtk w name_1,name_2 name_1.img,name_2.img
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!
