• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

pankspoo

Senior Member
Jun 27, 2013
1,714
934
in front of ENCHILADA
So peoples got confused watch this live how to do just replace your files with your stock rom boot img and vbmeta from update zip of current roms update zip package except recovery file.
 

SeBright

Member
Sep 1, 2018
8
2
OnePlus Nord 2 5G
You can find the OTA A.12 zip file here: https://mega.nz/folder/rQhhHQpA#nNHvPlmzBXwPjmaFpuDa2Q

The partition images are extracted directly from the phone memory, so all images have the exact same dimensions of the partitions size on the phone memory, not the "real" size of the data in them.
In practice, they're filled with lot's of zeros at the end to reach all the same size.
Don't worry about it, both files, smaller ones that came in the OTA files, and the 8Mb+ ones extracted with the tool, are exactly the same.

emmc.win files should be just .img files renamed yes. You can renamed them back to .img or even flash them directly like that.

Try to flash just the vbmeta img from the OTA file and see if it works btw.
I'm about to implement @TheWing fix soon this week in the thread.

Took a bit of fiddling around, I think I erased a few partitions by accident (due to following the github page's official instructions for how to unlock bootloader)

Flashing VBmeta from the OTA 12 update file in the mega link above, along with flashing the boot.img and recovery image from the google drive link in the OP should work for most people.

If you're like me and used the "python mtk e cache[and a few other partitions]" command as instructed by the mtkclient's github page's instructions for how to unlock bootloader (which doesn't work for the oneplus nord 2, so don't bother) I found I had to reflash those erased partitions from my nandroid backup as well. Then for some reason, it seems like vbmeta has to be the LAST partition you flash. As I flashed all sorts of other things, and the phone wouldnt boot, until i flashed vbmeta as the most recent one. No idea why that matters though.


Have to step away from my computer but currently the phone seems to boot up just fine, I'm going to leave it at the "welcome setup" screen for now and I'll report back if I see anything unusual.

If anyone else runs in the same issues and got to the fix, just know that if you wiped all partitions, or used someone else's persist.img partition, you'll need to manually flash in the persist image from your own backup or your fingerprint + camera won't work.

Thank you both ! Using a combination of those methods worked for me after my phone was completely bricked.
I had to flash preloader (using the attached file that I flashed with
Code:
python mtk w preloader preloader_lu1.bin --parttype=lu1
), boot, recovery and super from the GDrive save and then the vbmeta from the Mega OTA.
And another thank you to @Raygen who was most helpful and to whom I owe my phone.
 

Attachments

  • preloader_lu1.bin
    4 MB · Views: 11
  • Like
Reactions: Raygen

pankspoo

Senior Member
Jun 27, 2013
1,714
934
in front of ENCHILADA
Thank you both ! Using a combination of those methods worked for me after my phone was completely bricked.
I had to flash preloader (using the attached file that I flashed with
Code:
python mtk w preloader preloader_lu1.bin --parttype=lu1
), boot, recovery and super from the GDrive save and then the vbmeta from the Mega OTA.
And another thank you to @Raygen who was most helpful and to whom I owe my phone.
What happened to your device
 

NetSoerfer

Senior Member
Sep 29, 2009
125
64
Dortmund
OnePlus Nord
I think in the .bat for unlocked phones, the actual fastboot flash command is missing...

Code:
echo Restore started!
echo Restore started! >> PBlog.txt
echo.
::restore
for %%F in (PartitionsBackup\*.img) do (
    echo flashing %%~nF...
    echo flashing %%~nF... >> PBlog.txt
    :: controllo errori, fastboot
    if errorlevel 1 (
        echo Error with fastboot command
        echo Error with fastboot command >> PBlog.txt
        set error=1
        echo.
    ) else (
        echo %%~nF restored.
        echo %%~nF restored. >> PBlog.txt
        echo.
    )
)
cls
echo Restore completed!
echo Restore completed! >> PBlog.txt

Which would explain that it takes only two or three seconds to go through the restore process and then the .bat reports success...
 
Last edited:

Raygen

Senior Member
Feb 21, 2014
91
32
Mantova
I think in the .bat for unlocked phones, the actual restore command is missing...

Which would explain that it takes only two or three seconds to go through the restore process and then the .bat reports success...
That's.. unusual. Thanks for reporting. There should definitely be a fastboot command in there.
You can find the working script also in his dedicated post for now: https://forum.xda-developers.com/t/tool-no-root-partitionsbackupper-nandroid-alternative.4366055/
I'll reupload the .zip without the script included and just a link to the dedicated post, to avoid future versions mixup issues.
 

NetSoerfer

Senior Member
Sep 29, 2009
125
64
Dortmund
OnePlus Nord
After running v1.4 with the files from the OP, I'm still getting into a boot loop - with an android boot screen instead of the OnePlus loading screen, oddly.

And the "Orange State" screen is taking ages - more than a minute - to disappear...
I fixed that flashing vbmeta.img again - now it's disappearing in about five seconds.

edit: I didn't run a data format... hang on.
...... nope, still getting a boot loop with the android boot screen. Any ideas?
 
Last edited:

Raygen

Senior Member
Feb 21, 2014
91
32
Mantova
After running v1.4 with the files from the OP, I'm still getting into a boot loop - with an android boot screen instead of the OnePlus loading screen, oddly.


I fixed that flashing vbmeta.img again - now it's disappearing in about five seconds.


...... nope, still getting a boot loop with the android boot screen. Any ideas?
Could you share your PBlog.txt file?

Your short reboots looks similar to the ones @Zombnombs encountered

You could try to flash the vbmeta patched image instead of the stock one, with the command fastboot flash vbmeta --disable-verity --disable-verification PartitionsBackup\vbmeta_patched.img
 
Last edited:

NetSoerfer

Senior Member
Sep 29, 2009
125
64
Dortmund
OnePlus Nord
Could you share your PBlog.txt file?

sure:
Logging started...

Main menu
restore
Rebooting to fastboot...
Restore started
flashing audio_dsp...
audio_dsp restored.
flashing boot...
boot restored.
flashing boot_para...
boot_para restored.
flashing cache...
cache restored.
flashing cam_vpu1...
cam_vpu1 restored.
flashing cam_vpu2...
cam_vpu2 restored.
flashing cam_vpu3...
cam_vpu3 restored.
flashing cdt_engineering...
cdt_engineering restored.
flashing dpm_1...
dpm_1 restored.
flashing dpm_2...
dpm_2 restored.
flashing dtbo...
dtbo restored.
flashing expdb...
expdb restored.
flashing flashinfo...
flashinfo restored.
flashing frp...
frp restored.
flashing gz1...
gz1 restored.
flashing gz2...
gz2 restored.
flashing lk...
lk restored.
flashing lk2...
lk2 restored.
flashing logo...
logo restored.
flashing mcupm_1...
mcupm_1 restored.
flashing mcupm_2...
mcupm_2 restored.
flashing md1img...
md1img restored.
flashing metadata...
metadata restored.
flashing misc...
misc restored.
flashing my_carrier...
Error with fastboot command
flashing my_company...
Error with fastboot command
flashing my_engineering...
Error with fastboot command
flashing my_heytap...
Error with fastboot command
flashing my_manifest...
Error with fastboot command
flashing my_preload...
Error with fastboot command
flashing my_product...
Error with fastboot command
flashing my_region...
Error with fastboot command
flashing my_stock...
Error with fastboot command
flashing ocdt...
ocdt restored.
flashing odm...
Error with fastboot command
flashing oplusreserve1...
oplusreserve1 restored.
flashing oplusreserve2...
oplusreserve2 restored.
flashing oplusreserve3...
oplusreserve3 restored.
flashing oplusreserve5...
oplusreserve5 restored.
flashing oplusreserve6...
oplusreserve6 restored.
flashing oplus_custom...
oplus_custom restored.
flashing otp...
otp restored.
flashing para...
para restored.
flashing param...
param restored.
flashing pi_img...
pi_img restored.
flashing product...
Error with fastboot command
flashing recovery...
recovery restored.
flashing scp1...
scp1 restored.
flashing scp2...
scp2 restored.
flashing sec1...
sec1 restored.
flashing spmfw...
spmfw restored.
flashing sspm_1...
sspm_1 restored.
flashing sspm_2...
sspm_2 restored.
flashing super...
super restored.
flashing system...
Error with fastboot command
flashing tee1...
tee1 restored.
flashing tee2...
tee2 restored.
flashing vbmeta_patched...
Error with fastboot command
flashing vbmeta_system...
vbmeta_system restored.
flashing vbmeta_vendor...
vbmeta_vendor restored.
flashing vendor...
Error with fastboot command
flashing vendor_boot...
vendor_boot restored.
vbmeta restored.
Restore completed
rebooting to recovery
exit 1

Your short reboots looks similar to the ones @Zombnombs encountered

Not sure - it takes several minutes of android boot animation until it loops. I think @Zombnombs had the loop occur after seconds, right?

You could try to flash the vbmeta patched image instead of the stock one, with the command fastboot flash vbmeta --disable-verity --disable-verification PartitionsBackup\vbmeta_patched.img

I'll do that. I'll let you know how it goes, thanks for your help :)

...it didn't work. Still boot looping even after flashing vbmeta_patched.img :(
 
Last edited:

NetSoerfer

Senior Member
Sep 29, 2009
125
64
Dortmund
OnePlus Nord
Looking through the log a little more awake I noticed a couple of errors, after mistakenly assuming that the success message at the end meant that all has gone as expected.

From my point of view, there's three kinds of errors:

flashing my_carrier...
Error with fastboot command
flashing my_company...
Error with fastboot command
flashing my_engineering...
Error with fastboot command
flashing my_heytap...
Error with fastboot command
flashing my_manifest...
Error with fastboot command
flashing my_preload...
Error with fastboot command
flashing my_product...
Error with fastboot command
flashing my_region...
Error with fastboot command
flashing my_stock...
Error with fastboot command

I don't know about these, but there is an old note in the PartitionsBackupper OP about the my_* partitions, so it might not be related to my particular phone.

flashing odm...
Error with fastboot command

flashing product...
Error with fastboot command

flashing system...
Error with fastboot command

flashing vendor...
Error with fastboot command

These are the four partitions inside that weird super partition, right?

I made a mistake early on, after I rebooted my phone and it went into a boot loop. I hadn't installed an Update (at least not explicitly - the update to A.14 was available, but I never explicitly installed it, so I really don't know what the boot loop was caused by. (I could imagine that it was installed when I rebooted? Don't know if OnePlus would auto-install updates on reboot?)

Anyway, when trying to fix it I mistakenly flashed system.img into the super partition, which was obviously not a very good idea. So I did some searching on that super partition and found that it contains those four above (odm, product, system, vendor), and that I had probably destroyed those partitions.

What I did find was that I can't easily flash odm, product, system, vendor, I get Writing 'system' FAILED (remote: 'This partition doesn't exist'). I previously thought this could be fixed by flashing super, but that was wrong, even afterwards I got that error.

flashing vbmeta_patched...
Error with fastboot command

This last one is probably just because no similarly named partition exists, which is fine because vbmeta_patched.img is an alternative to vbmeta.img, right?

The above mostly happened in the fastboot mode with the weird tiny text - the one you get into when pressing Power+VolDown. Mostly because I think I occasionally went into the other fastboot mode (using fastboot reboot fastboot, the one with the English/Asian language choices, is that OOB Recovery?) because I didn't know there were differences between the two.

After realising that I couldn't flash system even after super anymore, I went back to fastboot reboot recovery.

In that one, I noticed that I can flash system just fine, however, running the PartitionsBackupper_v1.4.bat failed to update super this time. See the new PBlog.txt:
Logging started...

Main menu
restore
Restore started
flashing audio_dsp...
audio_dsp restored.
flashing boot...
boot restored.
flashing boot_para...
boot_para restored.
flashing cache...
cache restored.
flashing cam_vpu1...
cam_vpu1 restored.
flashing cam_vpu2...
cam_vpu2 restored.
flashing cam_vpu3...
cam_vpu3 restored.
flashing cdt_engineering...
cdt_engineering restored.
flashing dpm_1...
dpm_1 restored.
flashing dpm_2...
dpm_2 restored.
flashing dtbo...
dtbo restored.
flashing expdb...
expdb restored.
flashing flashinfo...
flashinfo restored.
flashing frp...
frp restored.
flashing gz1...
gz1 restored.
flashing gz2...
gz2 restored.
flashing lk...
lk restored.
flashing lk2...
lk2 restored.
flashing logo...
logo restored.
flashing mcupm_1...
mcupm_1 restored.
flashing mcupm_2...
mcupm_2 restored.
flashing md1img...
md1img restored.
flashing metadata...
Error with fastboot command
flashing misc...
misc restored.
flashing my_carrier...
my_carrier restored.
flashing my_company...
my_company restored.
flashing my_engineering...
my_engineering restored.
flashing my_heytap...
my_heytap restored.
flashing my_manifest...
my_manifest restored.
flashing my_preload...
my_preload restored.
flashing my_product...
my_product restored.
flashing my_region...
my_region restored.
flashing my_stock...
my_stock restored.
flashing ocdt...
ocdt restored.
flashing odm...
odm restored.
flashing oplusreserve1...
oplusreserve1 restored.
flashing oplusreserve2...
oplusreserve2 restored.
flashing oplusreserve3...
oplusreserve3 restored.
flashing oplusreserve5...
oplusreserve5 restored.
flashing oplusreserve6...
oplusreserve6 restored.
flashing oplus_custom...
oplus_custom restored.
flashing otp...
otp restored.
flashing para...
para restored.
flashing param...
param restored.
flashing pi_img...
pi_img restored.
flashing product...
product restored.
flashing recovery...
recovery restored.
flashing scp1...
scp1 restored.
flashing scp2...
scp2 restored.
flashing sec1...
sec1 restored.
flashing spmfw...
spmfw restored.
flashing sspm_1...
sspm_1 restored.
flashing sspm_2...
sspm_2 restored.
flashing super...
Error with fastboot command
flashing system...
system restored.
flashing tee1...
tee1 restored.
flashing tee2...
tee2 restored.
flashing vbmeta_patched...
Error with fastboot command
flashing vbmeta_system...
vbmeta_system restored.
flashing vbmeta_vendor...
vbmeta_vendor restored.
flashing vendor...
vendor restored.
flashing vendor_boot...
vendor_boot restored.
vbmeta restored.
Restore completed
rebooting to recovery
exit 1

Still, that worked, I just got greeted by a Hello! screen. Fingerprint enrols fine, Bluetooth finds devices, I'm guessing because I was lucky enough not to mess with the partition that breaks those.

So I guess the takeaway is: Don't try to flash partitions in the tiny text fastboot mode (even if it seems to work, identifying the devices with fastboot devices and flashing some partitions without error), but always go to the English/Asian language choice screen first using fastboot reboot fastboot, where some partitions behave differently.
 
Last edited:
  • Like
Reactions: Raygen

GaryFisher88

Senior Member
Jan 23, 2010
105
11
hi Guys,

can someone provide a stock EU a.13 boot, recovery and vmbeta to make unbick porcedure with locked bootloader?
 

Raygen

Senior Member
Feb 21, 2014
91
32
Mantova
Looking through the log a little more awake I noticed a couple of errors, after mistakenly assuming that the success message at the end meant that all has gone as expected.

From my point of view, there's three kinds of errors:



I don't know about these, but there is an old note in the PartitionsBackupper OP about the my_* partitions, so it might not be related to my particular phone.



These are the four partitions inside that weird super partition, right?

I made a mistake early on, after I rebooted my phone and it went into a boot loop. I hadn't installed an Update (at least not explicitly - the update to A.14 was available, but I never explicitly installed it, so I really don't know what the boot loop was caused by. (I could imagine that it was installed when I rebooted? Don't know if OnePlus would auto-install updates on reboot?)

Anyway, when trying to fix it I mistakenly flashed system.img into the super partition, which was obviously not a very good idea. So I did some searching on that super partition and found that it contains those four above (odm, product, system, vendor), and that I had probably destroyed those partitions.

What I did find was that I can't easily flash odm, product, system, vendor, I get Writing 'system' FAILED (remote: 'This partition doesn't exist'). I previously thought this could be fixed by flashing super, but that was wrong, even afterwards I got that error.



This last one is probably just because no similarly named partition exists, which is fine because vbmeta_patched.img is an alternative to vbmeta.img, right?

The above mostly happened in the fastboot mode with the weird tiny text - the one you get into when pressing Power+VolDown. Mostly because I think I occasionally went into the other fastboot mode (using fastboot reboot fastboot, the one with the English/Asian language choices, is that OOB Recovery?) because I didn't know there were differences between the two.

After realising that I couldn't flash system even after super anymore, I went back to fastboot reboot recovery.

In that one, I noticed that I can flash system just fine, however, running the PartitionsBackupper_v1.4.bat failed to update super this time. See the new PBlog.txt:
Logging started...

Main menu
restore
Restore started
flashing audio_dsp...
audio_dsp restored.
flashing boot...
boot restored.
flashing boot_para...
boot_para restored.
flashing cache...
cache restored.
flashing cam_vpu1...
cam_vpu1 restored.
flashing cam_vpu2...
cam_vpu2 restored.
flashing cam_vpu3...
cam_vpu3 restored.
flashing cdt_engineering...
cdt_engineering restored.
flashing dpm_1...
dpm_1 restored.
flashing dpm_2...
dpm_2 restored.
flashing dtbo...
dtbo restored.
flashing expdb...
expdb restored.
flashing flashinfo...
flashinfo restored.
flashing frp...
frp restored.
flashing gz1...
gz1 restored.
flashing gz2...
gz2 restored.
flashing lk...
lk restored.
flashing lk2...
lk2 restored.
flashing logo...
logo restored.
flashing mcupm_1...
mcupm_1 restored.
flashing mcupm_2...
mcupm_2 restored.
flashing md1img...
md1img restored.
flashing metadata...
Error with fastboot command
flashing misc...
misc restored.
flashing my_carrier...
my_carrier restored.
flashing my_company...
my_company restored.
flashing my_engineering...
my_engineering restored.
flashing my_heytap...
my_heytap restored.
flashing my_manifest...
my_manifest restored.
flashing my_preload...
my_preload restored.
flashing my_product...
my_product restored.
flashing my_region...
my_region restored.
flashing my_stock...
my_stock restored.
flashing ocdt...
ocdt restored.
flashing odm...
odm restored.
flashing oplusreserve1...
oplusreserve1 restored.
flashing oplusreserve2...
oplusreserve2 restored.
flashing oplusreserve3...
oplusreserve3 restored.
flashing oplusreserve5...
oplusreserve5 restored.
flashing oplusreserve6...
oplusreserve6 restored.
flashing oplus_custom...
oplus_custom restored.
flashing otp...
otp restored.
flashing para...
para restored.
flashing param...
param restored.
flashing pi_img...
pi_img restored.
flashing product...
product restored.
flashing recovery...
recovery restored.
flashing scp1...
scp1 restored.
flashing scp2...
scp2 restored.
flashing sec1...
sec1 restored.
flashing spmfw...
spmfw restored.
flashing sspm_1...
sspm_1 restored.
flashing sspm_2...
sspm_2 restored.
flashing super...
Error with fastboot command
flashing system...
system restored.
flashing tee1...
tee1 restored.
flashing tee2...
tee2 restored.
flashing vbmeta_patched...
Error with fastboot command
flashing vbmeta_system...
vbmeta_system restored.
flashing vbmeta_vendor...
vbmeta_vendor restored.
flashing vendor...
vendor restored.
flashing vendor_boot...
vendor_boot restored.
vbmeta restored.
Restore completed
rebooting to recovery
exit 1

Still, that worked, I just got greeted by a Hello! screen. Fingerprint enrols fine, Bluetooth finds devices, I'm guessing because I was lucky enough not to mess with the partition that breaks those.

So I guess the takeaway is: Don't try to flash partitions in the tiny text fastboot mode (even if it seems to work, identifying the devices with fastboot devices and flashing some partitions without error), but always go to the English/Asian language choice screen first using fastboot reboot fastboot, where some partitions behave differently.
Glad that worked!

I've noticed the logs are not really useful with these level of details.. So I've updated a new version of the script with better logs for future cases.
And about the difference between flashing in bootloader mode (with the tiny white text) vs fastboot mode (inside the recovery), I've noticed the partitions that cause the issue and also included this fix in the updated version of the script.

hi Guys,

can someone provide a stock EU a.13 boot, recovery and vmbeta to make unbick porcedure with locked bootloader?
I'm still on A.12 sorry, that's why the post is not updated. I'm completely out of free time in this period.
You could try to fully flash the A.12 and then update back to A.13 though.
 
Last edited:
  • Like
Reactions: muppetz

Elaba

Senior Member
Jun 27, 2010
87
14
So i'm back after i previously posted here at the end of november. The first version of Partitionsbackup v1.3 helped me out back then. I was able to root it properly back then aswell. After using my phone for over 1 month, without problems .I didn't instal the latest OTA and didn't really instal special apps or anything in the past few days.

Last night i put it on the charger, like always, and this morning when i woke up, the phone was rebooted into twrp. When i pressed the reboot button, it was back into a bootloop. I have no idea what triggered it to boot into twrp this morning and no idea what went wrong to make it bootloop again. Now i'm trying again to get it to a "normal" state, already made a nand backup and backupped all my user data trough twrp connected to my pc.

I've already restored a Nand backup i made previously, and can't get into twrp anymore due to wrong password pattern (altough its always been the same) . After this i tried the new version of the PartitionsBackupper v1.6. Now it's bootlooping into the "ANDROID" screen.

I own the Nord 2 Pac-Man edition, not sure if this has something to do with compatibility issues.

Current state:
So far the bootloader is still unlocked and the original recovery is on the phone. I can't get into the file system anymore nor can i mount the filesystem on a PC



PB log:
Logging started...

Main menu
restore
[fastboot] 45L7B645JJNBR4PF fastboot
Restore started
flashing boot...
[fastboot] Sending 'boot' (32768 KB) OKAY [ 0.825s]
Writing 'boot' OKAY [ 0.253s]
Finished. Total time: 1.095s
boot restored.
flashing cache...
[fastboot] Invalid sparse file format at header magic
Sending sparse 'cache' 1/1 (164 KB) OKAY [ 0.046s]
Writing 'cache' OKAY [ 15.003s]
Finished. Total time: 18.635s
cache restored.
flashing dtbo...
[fastboot] Sending 'dtbo' (8192 KB) OKAY [ 0.241s]
Writing 'dtbo' OKAY [ 0.326s]
Finished. Total time: 0.581s
dtbo restored.
flashing metadata...
[fastboot] Sending 'metadata' (32768 KB) OKAY [ 0.823s]
Writing 'metadata' OKAY [ 1.367s]
Finished. Total time: 2.218s
metadata restored.
flashing recovery...
[fastboot] Sending 'recovery' (131072 KB) OKAY [ 3.184s]
Writing 'recovery' OKAY [ 1.206s]
Finished. Total time: 4.413s
recovery restored.
flashing super...
[fastboot] Invalid sparse file format at header magic
Sending sparse 'super' 1/55 (131068 KB) OKAY [ 2.933s]
Writing 'super' OKAY [ 0.707s]
Sending sparse 'super' 2/55 (131048 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 0.572s]
Sending sparse 'super' 3/55 (131056 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.539s]
Sending sparse 'super' 4/55 (131052 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.455s]
Sending sparse 'super' 5/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.286s]
Sending sparse 'super' 6/55 (131068 KB) OKAY [ 2.979s]
Writing 'super' OKAY [ 0.640s]
Sending sparse 'super' 7/55 (131068 KB) OKAY [ 2.895s]
Writing 'super' OKAY [ 0.942s]
Sending sparse 'super' 8/55 (125544 KB) OKAY [ 2.811s]
Writing 'super' OKAY [ 0.539s]
Sending sparse 'super' 9/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.387s]
Sending sparse 'super' 10/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.337s]
Sending sparse 'super' 11/55 (129108 KB) OKAY [ 2.861s]
Writing 'super' OKAY [ 0.471s]
Sending sparse 'super' 12/55 (131068 KB) OKAY [ 2.945s]
Writing 'super' OKAY [ 1.851s]
Sending sparse 'super' 13/55 (131068 KB) OKAY [ 2.912s]
Writing 'super' OKAY [ 0.404s]
Sending sparse 'super' 14/55 (116388 KB) OKAY [ 2.558s]
Writing 'super' OKAY [ 4.242s]
Sending sparse 'super' 15/55 (131068 KB) OKAY [ 2.947s]
Writing 'super' OKAY [ 0.454s]
Sending sparse 'super' 16/55 (127872 KB) OKAY [ 2.828s]
Writing 'super' OKAY [ 1.482s]
Sending sparse 'super' 17/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.354s]
Sending sparse 'super' 18/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 3.788s]
Sending sparse 'super' 19/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.471s]
Sending sparse 'super' 20/55 (131068 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 2.374s]
Sending sparse 'super' 21/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.454s]
Sending sparse 'super' 22/55 (131068 KB) OKAY [ 2.913s]
Writing 'super' OKAY [ 3.569s]
Sending sparse 'super' 23/55 (131068 KB) OKAY [ 3.014s]
Writing 'super' OKAY [ 0.640s]
Sending sparse 'super' 24/55 (131068 KB) OKAY [ 3.014s]
Writing 'super' OKAY [ 1.667s]
Sending sparse 'super' 25/55 (131068 KB) OKAY [ 2.964s]
Writing 'super' OKAY [ 0.505s]
Sending sparse 'super' 26/55 (125860 KB) OKAY [ 2.812s]
Writing 'super' OKAY [ 3.855s]
Sending sparse 'super' 27/55 (127960 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 0.556s]
Sending sparse 'super' 28/55 (131068 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 1.886s]
Sending sparse 'super' 29/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.437s]
Sending sparse 'super' 30/55 (130216 KB) OKAY [ 2.964s]
Writing 'super' OKAY [ 0.437s]
Sending sparse 'super' 31/55 (131068 KB) OKAY [ 2.879s]
Writing 'super' OKAY [ 0.774s]
Sending sparse 'super' 32/55 (131068 KB) OKAY [ 2.862s]
Writing 'super' OKAY [ 3.266s]
Sending sparse 'super' 33/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.387s]
Sending sparse 'super' 34/55 (123048 KB) OKAY [ 2.710s]
Writing 'super' OKAY [ 1.364s]
Sending sparse 'super' 35/55 (131068 KB) OKAY [ 2.945s]
Writing 'super' OKAY [ 0.353s]
Sending sparse 'super' 36/55 (125284 KB) OKAY [ 2.794s]
Writing 'super' OKAY [ 2.290s]
Sending sparse 'super' 37/55 (130184 KB) OKAY [ 2.912s]
Writing 'super' OKAY [ 0.674s]
Sending sparse 'super' 38/55 (131068 KB) OKAY [ 2.979s]
Writing 'super' OKAY [ 2.054s]
Sending sparse 'super' 39/55 (131068 KB) OKAY [ 2.913s]
Writing 'super' OKAY [ 0.454s]
Sending sparse 'super' 40/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 2.593s]
Sending sparse 'super' 41/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.437s]
Sending sparse 'super' 42/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 1.852s]
Sending sparse 'super' 43/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.303s]
Sending sparse 'super' 44/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 2.256s]
Sending sparse 'super' 45/55 (131068 KB) OKAY [ 2.930s]
Writing 'super' OKAY [ 0.505s]
Sending sparse 'super' 46/55 (131068 KB) OKAY [ 2.862s]
Writing 'super' OKAY [ 2.929s]
Sending sparse 'super' 47/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.505s]
Sending sparse 'super' 48/55 (131068 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 1.869s]
Sending sparse 'super' 49/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.538s]
Sending sparse 'super' 50/55 (117884 KB) OKAY [ 2.660s]
Writing 'super' OKAY [ 2.745s]
Sending sparse 'super' 51/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.454s]
Sending sparse 'super' 52/55 (131068 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 3.098s]
Sending sparse 'super' 53/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.471s]
Sending sparse 'super' 54/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 2.070s]
Sending sparse 'super' 55/55 (119156 KB) OKAY [ 2.710s]
Writing 'super' OKAY [ 29.614s]
Finished. Total time: 339.546s
super restored.
flashing vendor_boot...
[fastboot] Sending 'vendor_boot' (65536 KB) OKAY [ 1.624s]
Writing 'vendor_boot' OKAY [ 1.441s]
Finished. Total time: 3.087s
vendor_boot restored.
Rebooting to fastboot...
flashing audio_dsp...
[fastboot] Sending 'audio_dsp' (8192 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Error with fastboot command
flashing boot_para...
[fastboot] < waiting for any device >
^C
 
Last edited:

Raygen

Senior Member
Feb 21, 2014
91
32
Mantova
So i'm back after i previously posted here at the end of november. The first version of Partitionsbackup v1.3 helped me out back then. I was able to root it properly back then aswell. After using my phone for over 1 month, without problems .I didn't instal the latest OTA and didn't really instal special apps or anything in the past few days.

Last night i put it on the charger, like always, and this morning when i woke up, the phone was rebooted into twrp. When i pressed the reboot button, it was back into a bootloop. I have no idea what triggered it to boot into twrp this morning and no idea what went wrong to make it bootloop again. Now i'm trying again to get it to a "normal" state, already made a nand backup and backupped all my user data trough twrp connected to my pc.

I've already restored a Nand backup i made previously, and can't get into twrp anymore due to wrong password pattern (altough its always been the same) . After this i tried the new version of the PartitionsBackupper v1.6. Now it's bootlooping into the "ANDROID" screen.

I own the Nord 2 Pac-Man edition, not sure if this has something to do with compatibility issues.

Current state:
So far the bootloader is still unlocked and the original recovery is on the phone. I can't get into the file system anymore nor can i mount the filesystem on a PC



PB log:
Logging started...

Main menu
restore
[fastboot] 45L7B645JJNBR4PF fastboot
Restore started
flashing boot...
[fastboot] Sending 'boot' (32768 KB) OKAY [ 0.825s]
Writing 'boot' OKAY [ 0.253s]
Finished. Total time: 1.095s
boot restored.
flashing cache...
[fastboot] Invalid sparse file format at header magic
Sending sparse 'cache' 1/1 (164 KB) OKAY [ 0.046s]
Writing 'cache' OKAY [ 15.003s]
Finished. Total time: 18.635s
cache restored.
flashing dtbo...
[fastboot] Sending 'dtbo' (8192 KB) OKAY [ 0.241s]
Writing 'dtbo' OKAY [ 0.326s]
Finished. Total time: 0.581s
dtbo restored.
flashing metadata...
[fastboot] Sending 'metadata' (32768 KB) OKAY [ 0.823s]
Writing 'metadata' OKAY [ 1.367s]
Finished. Total time: 2.218s
metadata restored.
flashing recovery...
[fastboot] Sending 'recovery' (131072 KB) OKAY [ 3.184s]
Writing 'recovery' OKAY [ 1.206s]
Finished. Total time: 4.413s
recovery restored.
flashing super...
[fastboot] Invalid sparse file format at header magic
Sending sparse 'super' 1/55 (131068 KB) OKAY [ 2.933s]
Writing 'super' OKAY [ 0.707s]
Sending sparse 'super' 2/55 (131048 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 0.572s]
Sending sparse 'super' 3/55 (131056 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.539s]
Sending sparse 'super' 4/55 (131052 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.455s]
Sending sparse 'super' 5/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.286s]
Sending sparse 'super' 6/55 (131068 KB) OKAY [ 2.979s]
Writing 'super' OKAY [ 0.640s]
Sending sparse 'super' 7/55 (131068 KB) OKAY [ 2.895s]
Writing 'super' OKAY [ 0.942s]
Sending sparse 'super' 8/55 (125544 KB) OKAY [ 2.811s]
Writing 'super' OKAY [ 0.539s]
Sending sparse 'super' 9/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.387s]
Sending sparse 'super' 10/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.337s]
Sending sparse 'super' 11/55 (129108 KB) OKAY [ 2.861s]
Writing 'super' OKAY [ 0.471s]
Sending sparse 'super' 12/55 (131068 KB) OKAY [ 2.945s]
Writing 'super' OKAY [ 1.851s]
Sending sparse 'super' 13/55 (131068 KB) OKAY [ 2.912s]
Writing 'super' OKAY [ 0.404s]
Sending sparse 'super' 14/55 (116388 KB) OKAY [ 2.558s]
Writing 'super' OKAY [ 4.242s]
Sending sparse 'super' 15/55 (131068 KB) OKAY [ 2.947s]
Writing 'super' OKAY [ 0.454s]
Sending sparse 'super' 16/55 (127872 KB) OKAY [ 2.828s]
Writing 'super' OKAY [ 1.482s]
Sending sparse 'super' 17/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.354s]
Sending sparse 'super' 18/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 3.788s]
Sending sparse 'super' 19/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.471s]
Sending sparse 'super' 20/55 (131068 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 2.374s]
Sending sparse 'super' 21/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.454s]
Sending sparse 'super' 22/55 (131068 KB) OKAY [ 2.913s]
Writing 'super' OKAY [ 3.569s]
Sending sparse 'super' 23/55 (131068 KB) OKAY [ 3.014s]
Writing 'super' OKAY [ 0.640s]
Sending sparse 'super' 24/55 (131068 KB) OKAY [ 3.014s]
Writing 'super' OKAY [ 1.667s]
Sending sparse 'super' 25/55 (131068 KB) OKAY [ 2.964s]
Writing 'super' OKAY [ 0.505s]
Sending sparse 'super' 26/55 (125860 KB) OKAY [ 2.812s]
Writing 'super' OKAY [ 3.855s]
Sending sparse 'super' 27/55 (127960 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 0.556s]
Sending sparse 'super' 28/55 (131068 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 1.886s]
Sending sparse 'super' 29/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.437s]
Sending sparse 'super' 30/55 (130216 KB) OKAY [ 2.964s]
Writing 'super' OKAY [ 0.437s]
Sending sparse 'super' 31/55 (131068 KB) OKAY [ 2.879s]
Writing 'super' OKAY [ 0.774s]
Sending sparse 'super' 32/55 (131068 KB) OKAY [ 2.862s]
Writing 'super' OKAY [ 3.266s]
Sending sparse 'super' 33/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.387s]
Sending sparse 'super' 34/55 (123048 KB) OKAY [ 2.710s]
Writing 'super' OKAY [ 1.364s]
Sending sparse 'super' 35/55 (131068 KB) OKAY [ 2.945s]
Writing 'super' OKAY [ 0.353s]
Sending sparse 'super' 36/55 (125284 KB) OKAY [ 2.794s]
Writing 'super' OKAY [ 2.290s]
Sending sparse 'super' 37/55 (130184 KB) OKAY [ 2.912s]
Writing 'super' OKAY [ 0.674s]
Sending sparse 'super' 38/55 (131068 KB) OKAY [ 2.979s]
Writing 'super' OKAY [ 2.054s]
Sending sparse 'super' 39/55 (131068 KB) OKAY [ 2.913s]
Writing 'super' OKAY [ 0.454s]
Sending sparse 'super' 40/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 2.593s]
Sending sparse 'super' 41/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 0.437s]
Sending sparse 'super' 42/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 1.852s]
Sending sparse 'super' 43/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.303s]
Sending sparse 'super' 44/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 2.256s]
Sending sparse 'super' 45/55 (131068 KB) OKAY [ 2.930s]
Writing 'super' OKAY [ 0.505s]
Sending sparse 'super' 46/55 (131068 KB) OKAY [ 2.862s]
Writing 'super' OKAY [ 2.929s]
Sending sparse 'super' 47/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.505s]
Sending sparse 'super' 48/55 (131068 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 1.869s]
Sending sparse 'super' 49/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.538s]
Sending sparse 'super' 50/55 (117884 KB) OKAY [ 2.660s]
Writing 'super' OKAY [ 2.745s]
Sending sparse 'super' 51/55 (131068 KB) OKAY [ 2.963s]
Writing 'super' OKAY [ 0.454s]
Sending sparse 'super' 52/55 (131068 KB) OKAY [ 2.896s]
Writing 'super' OKAY [ 3.098s]
Sending sparse 'super' 53/55 (131068 KB) OKAY [ 2.946s]
Writing 'super' OKAY [ 0.471s]
Sending sparse 'super' 54/55 (131068 KB) OKAY [ 2.929s]
Writing 'super' OKAY [ 2.070s]
Sending sparse 'super' 55/55 (119156 KB) OKAY [ 2.710s]
Writing 'super' OKAY [ 29.614s]
Finished. Total time: 339.546s
super restored.
flashing vendor_boot...
[fastboot] Sending 'vendor_boot' (65536 KB) OKAY [ 1.624s]
Writing 'vendor_boot' OKAY [ 1.441s]
Finished. Total time: 3.087s
vendor_boot restored.
Rebooting to fastboot...
flashing audio_dsp...
[fastboot] Sending 'audio_dsp' (8192 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Error with fastboot command
flashing boot_para...
[fastboot] < waiting for any device >
^C
Something similar happened to me like a week ago. I was rebooting the phone just 'cause, and it never booted back on. Got stuck in a bootloop, just like that.
I tried everything I could think of, but at the end I was forced to backup everything and wipe the phone with the stock recovery, and start fresh. (That's also where I took the occasion to update to A.15...)

I still have no idea what happened really. But it happened again a couple of times while trying to flash Magisk back after the wipe. So, it could be because of Magisk.
I'm running Magisk Canary rn without issues so far, we'll see if it's more stable.
 

Elaba

Senior Member
Jun 27, 2010
87
14
Something similar happened to me like a week ago. I was rebooting the phone just 'cause, and it never booted back on. Got stuck in a bootloop, just like that.
I tried everything I could think of, but at the end I was forced to backup everything and wipe the phone with the stock recovery, and start fresh. (That's also where I took the occasion to update to A.15...)

I still have no idea what happened really. But it happened again a couple of times while trying to flash Magisk back after the wipe. So, it could be because of Magisk.
I'm running Magisk Canary rn without issues so far, we'll see if it's more stable.
I have also tried alot of things, so far it only got worse. The bootloader is locked again, and also have the stock recovery on it. But now when i want to boot i get the error message " boot/recovery is destroyed ". I guess this will be an RMA. I'm unable to reach the internal storage, not able to push files onto it. Already tried this other youtube method, but it fails because the bootloader doesn't want to unlock anymore.
 

Raygen

Senior Member
Feb 21, 2014
91
32
Mantova
I have also tried alot of things, so far it only got worse. The bootloader is locked again, and also have the stock recovery on it. But now when i want to boot i get the error message " boot/recovery is destroyed ". I guess this will be an RMA. I'm unable to reach the internal storage, not able to push files onto it. Already tried this other youtube method, but it fails because the bootloader doesn't want to unlock anymore.
There's a procedure for a locked bootloader situation available on the first post of this thread. Take a chance with that before RMA
 

Elaba

Senior Member
Jun 27, 2010
87
14
Going to try this option, but the link in step 2 doesn't work anymore. Not sure where i can find this " seccfg.img " File?

Seems the day after this link got fixed. Thx
 
Last edited:

Elaba

Senior Member
Jun 27, 2010
87
14
There's a procedure for a locked bootloader situation available on the first post of this thread. Take a chance with that before RMA
Hello, I have tried the option to unlock the bootloader via the MTKclient , and all went well without errors, but so far no change (exept i have the stock recovery back). Partitionsbackupper gives alot of issues with fastboot and doesn't finish. So i guess the bootloader is still locked. (The bootscreen doesn't show the tiny words about the unlocked bootloader)

A few questions:

When i load the stock recovery , i have an option to do an Online Update, via wifi, (unfortunatly it doesn't find any wifi connection points (altough i can verify there are accespoints around)

Is there a way to load the Stock firmware on the phone, because it seems there is no firmware on the phone and doesn't get further than the boot screen.
 
Last edited:

Raygen

Senior Member
Feb 21, 2014
91
32
Mantova
Going to try this option, but the link in step 2 doesn't work anymore. Not sure where i can find this " seccfg.img " File?

Seems the day after this link got fixed. Thx
All files are always attached at the end of the post anyway
Hello, I have tried the option to unlock the bootloader via the MTKclient , and all went well without errors, but so far no change (exept i have the stock recovery back). Partitionsbackupper gives alot of issues with fastboot and doesn't finish. So i guess the bootloader is still locked. (The bootscreen doesn't show the tiny words about the unlocked bootloader)

A few questions:

When i load the stock recovery , i have an option to do an Online Update, via wifi, (unfortunatly it doesn't find any wifi connection points (altough i can verify there are accespoints around)

Is there a way to load the Stock firmware on the phone, because it seems there is no firmware on the phone and doesn't get further than the boot screen.
Yeah the "online update" option never worked, just ignore that. I guess you need to setup a dedicated AP for that

You could try to flash each partition (or at least the main ones, like "super") trought MTKclient yes, with the command python mtk w <partitionname> <partitionname>.img and repeating the steps 10 and 11 of the guide for each one.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Looking through the log a little more awake I noticed a couple of errors, after mistakenly assuming that the success message at the end meant that all has gone as expected.

    From my point of view, there's three kinds of errors:



    I don't know about these, but there is an old note in the PartitionsBackupper OP about the my_* partitions, so it might not be related to my particular phone.



    These are the four partitions inside that weird super partition, right?

    I made a mistake early on, after I rebooted my phone and it went into a boot loop. I hadn't installed an Update (at least not explicitly - the update to A.14 was available, but I never explicitly installed it, so I really don't know what the boot loop was caused by. (I could imagine that it was installed when I rebooted? Don't know if OnePlus would auto-install updates on reboot?)

    Anyway, when trying to fix it I mistakenly flashed system.img into the super partition, which was obviously not a very good idea. So I did some searching on that super partition and found that it contains those four above (odm, product, system, vendor), and that I had probably destroyed those partitions.

    What I did find was that I can't easily flash odm, product, system, vendor, I get Writing 'system' FAILED (remote: 'This partition doesn't exist'). I previously thought this could be fixed by flashing super, but that was wrong, even afterwards I got that error.



    This last one is probably just because no similarly named partition exists, which is fine because vbmeta_patched.img is an alternative to vbmeta.img, right?

    The above mostly happened in the fastboot mode with the weird tiny text - the one you get into when pressing Power+VolDown. Mostly because I think I occasionally went into the other fastboot mode (using fastboot reboot fastboot, the one with the English/Asian language choices, is that OOB Recovery?) because I didn't know there were differences between the two.

    After realising that I couldn't flash system even after super anymore, I went back to fastboot reboot recovery.

    In that one, I noticed that I can flash system just fine, however, running the PartitionsBackupper_v1.4.bat failed to update super this time. See the new PBlog.txt:
    Logging started...

    Main menu
    restore
    Restore started
    flashing audio_dsp...
    audio_dsp restored.
    flashing boot...
    boot restored.
    flashing boot_para...
    boot_para restored.
    flashing cache...
    cache restored.
    flashing cam_vpu1...
    cam_vpu1 restored.
    flashing cam_vpu2...
    cam_vpu2 restored.
    flashing cam_vpu3...
    cam_vpu3 restored.
    flashing cdt_engineering...
    cdt_engineering restored.
    flashing dpm_1...
    dpm_1 restored.
    flashing dpm_2...
    dpm_2 restored.
    flashing dtbo...
    dtbo restored.
    flashing expdb...
    expdb restored.
    flashing flashinfo...
    flashinfo restored.
    flashing frp...
    frp restored.
    flashing gz1...
    gz1 restored.
    flashing gz2...
    gz2 restored.
    flashing lk...
    lk restored.
    flashing lk2...
    lk2 restored.
    flashing logo...
    logo restored.
    flashing mcupm_1...
    mcupm_1 restored.
    flashing mcupm_2...
    mcupm_2 restored.
    flashing md1img...
    md1img restored.
    flashing metadata...
    Error with fastboot command
    flashing misc...
    misc restored.
    flashing my_carrier...
    my_carrier restored.
    flashing my_company...
    my_company restored.
    flashing my_engineering...
    my_engineering restored.
    flashing my_heytap...
    my_heytap restored.
    flashing my_manifest...
    my_manifest restored.
    flashing my_preload...
    my_preload restored.
    flashing my_product...
    my_product restored.
    flashing my_region...
    my_region restored.
    flashing my_stock...
    my_stock restored.
    flashing ocdt...
    ocdt restored.
    flashing odm...
    odm restored.
    flashing oplusreserve1...
    oplusreserve1 restored.
    flashing oplusreserve2...
    oplusreserve2 restored.
    flashing oplusreserve3...
    oplusreserve3 restored.
    flashing oplusreserve5...
    oplusreserve5 restored.
    flashing oplusreserve6...
    oplusreserve6 restored.
    flashing oplus_custom...
    oplus_custom restored.
    flashing otp...
    otp restored.
    flashing para...
    para restored.
    flashing param...
    param restored.
    flashing pi_img...
    pi_img restored.
    flashing product...
    product restored.
    flashing recovery...
    recovery restored.
    flashing scp1...
    scp1 restored.
    flashing scp2...
    scp2 restored.
    flashing sec1...
    sec1 restored.
    flashing spmfw...
    spmfw restored.
    flashing sspm_1...
    sspm_1 restored.
    flashing sspm_2...
    sspm_2 restored.
    flashing super...
    Error with fastboot command
    flashing system...
    system restored.
    flashing tee1...
    tee1 restored.
    flashing tee2...
    tee2 restored.
    flashing vbmeta_patched...
    Error with fastboot command
    flashing vbmeta_system...
    vbmeta_system restored.
    flashing vbmeta_vendor...
    vbmeta_vendor restored.
    flashing vendor...
    vendor restored.
    flashing vendor_boot...
    vendor_boot restored.
    vbmeta restored.
    Restore completed
    rebooting to recovery
    exit 1

    Still, that worked, I just got greeted by a Hello! screen. Fingerprint enrols fine, Bluetooth finds devices, I'm guessing because I was lucky enough not to mess with the partition that breaks those.

    So I guess the takeaway is: Don't try to flash partitions in the tiny text fastboot mode (even if it seems to work, identifying the devices with fastboot devices and flashing some partitions without error), but always go to the English/Asian language choice screen first using fastboot reboot fastboot, where some partitions behave differently.
    Glad that worked!

    I've noticed the logs are not really useful with these level of details.. So I've updated a new version of the script with better logs for future cases.
    And about the difference between flashing in bootloader mode (with the tiny white text) vs fastboot mode (inside the recovery), I've noticed the partitions that cause the issue and also included this fix in the updated version of the script.

    hi Guys,

    can someone provide a stock EU a.13 boot, recovery and vmbeta to make unbick porcedure with locked bootloader?
    I'm still on A.12 sorry, that's why the post is not updated. I'm completely out of free time in this period.
    You could try to fully flash the A.12 and then update back to A.13 though.
    1
    Here is my backup made with Raygen's partitionsbackupper tool :
    A.16 EU Stock OnePlus Nord 2 5G Pac-Man Edition
    You can surely restore with Raygen tool.
    Then send your twrp backup file to your phone >flash recovery twrp > Boot to recovery > restore > and only check persist and persist image from your nandroid backup if you have issue with camera and fingerprint
    1
    Is this a fresh backup? (no personal settings) thx
    Raygen said that his tool doesn't keep personal data. Be sure you have your nandroid backup on your computer and keep it in a safe place cause persist and persist image are linked to your phone.
  • 8
    Code:
    /*
     * 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 EU Full Stock Firmwares for the OnePlus Nord 2 DN2103
    A.12 - A.15 - A.16

    Specifics:

    • This rom will not overwrite your userdata 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.
    • The vbmeta partition is not stock.

    Requirements:


    Instructions:

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

    1. Download and install the Re LiveDVD iso of mtkclient and flash it on a pendrive with Rufus.
    2. Download and extract the attached seccfg.img unlocked partition.
    3. Download and extract the boot.img, recovery.img, and vbmeta.img from the zip of the stock firmware.
    4. Create a new folder named "img" in the pendrive you just flashed with Rufus, and paste the 4 images there.
    5. Start the mtkclient live usb. The login credentials are "user" for both name and password.
    6. 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.
    7. Copy the whole /img directory into the /opt/mtkclient directory.
    8. Disconnect the phone from the pc, and start the MTK script on the desktop of the live usb.
    9. Backup your seccfg partition first! With the command python mtk r seccfg seccfg_backup.img
    10. 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 screen of the phone should remain completely black and the script should find your phone and start the backup. Release the buttons.
    11. Now, disconnect the phone, and close and reopen mtkclient.
    12. Do also a backup of your boot partition with the command python mtk r boot boot_backup.img, repeating the steps 10 and 11.
    13. You can find your backed up partitions in the /opt/mtkclient directory. Copy them to the pendrive or they will be wiped as soon as you turn off the pc!
    14. Now write all 4 partition images with the command python mtk wl img, by repeating the steps 10 and 11.
    15. If you're stuck in a bootloop after all of this, some users have reported that flashing vbmeta a second time fixed it.
    16. You should now have an unlocked bootloader

    This procedure has been successfully tested by an external user.
    1. Follow the instructions in the "locked bootloader" procedure for how to install and run mtkclient.
    2. Download and extract the attached preloader_lu1.bin image, and the boot, recovery, vbmeta, and super images from the stock firmware .zip file, and paste them in the /opt/mtkclient directory.
    3. Run the command python mtk r preloader preloader_lu1_stock.bin --parttype=lu1 to backup your existing preloader partition first!
    4. Also backup your boot, vbmeta, and super partitions as described in the "locked bootloader" procedure.
    5. Run the command python mtk w preloader preloader_lu1.bin --parttype=lu1 to flash the preloader partition.
    6. Also run the commands as described in the "locked bootloader" procedure to flash the boot, recovery, vbmeta, and super images.
    7. If you're stuck in a bootloop after all of this, some users have reported that flashing vbmeta a second time fixed it.
    8. You should now have a working fastboot connnection

    Thanks to Zombnombs, TheWing, and SeBright 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!
    2
    So I got successful to flash your given seccfg.img.
    Then I booted in. Fastboot mode so tried try unlock bootloader commands to. Check and it's saying not allowed.
    Means its still locked i think
    i could also flash seccfg.img. But also still locked bootloader.
    will try again later this week.

    Here's a little more detailed instruction (@Raygen you can take this to your instructions, if you want):

    Download and install mtkclient (I reccomend to download the Re LiveDVD iso and flash it on a pendrive with Rufus).
    Go to https://github.com/bkerler/mtkclient, scroll down to "Use Re LiveDVD" (https://github.com/bkerler/mtkclient#use-re-livedvd-everything-ready-to-go-based-on-ubuntu) > Download
    Download rufus from http://rufus.ie/en/
    Insert a pendrive
    Start Rufus, select your pendrive (1), click "select" (2), select "re_livedvdV3.iso", click "START" (3)
    Extract just the seccfg.img partition from the zip.
    I had to rename the File after Download from seccfg_unlocked_A12.tif to seccfg.img
    Place the seccfg.img in the same folder with the mtk executable (in the Re LiveDVD, it's the /opt/mtkclient directory)
    Insert pendrive in windows-pc, open it, make a new directory "nord2" and copy the img-File to this folder
    Disconnect the phone from the pc, and start mtkclient (MTK on the desktop of the Re LiveDVD).
    Shutdown your PC, plugin pendrive, start PC. It should start from pendrive to MTK
    Enter Password "user" (without "")
    Open "Home" from Desktop, you'll need that later
    Backup your seccfg partition first! With the command python mtk r seccfg seccfg.bin
    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.
    As soon as it turns off, press and hold all 3 buttons (Vol+, Vol-, and Power) and connect the usb cable.
    The script should find your phone and start the backup. Release the buttons.
    You'll find the file in the explorer > file system > opt > mtkclient (rename it to something like "seccft-backup.img")
    Copy the file from earlier from file system > cdrom > nord2, to the above directory
    Now, disconnect the phone, and close and reopen mtkclient.
    Write the seccfg.img partition with the command python mtk w seccfg seccfg.img, press Enter, and reconnect the phone as explained before.
    You should now have an unlocked bootloader!
    2
    I'll add a log generator in the next version of the tool so it can be seen what went wrong.
    So far the best I can advise is to format data with the stock recovery before trying a second time (backup your data before that ofc)



    Alright we're at 3 users to whom the bootloader got locked.
    I'll reupload the .zip with the seccfg.img partition removed to avoid further harm for now, looks like it's another trouble making partition.
    Strange that the firmware in @sakarya1980 's thread does include it without issues. I've tagged him to see if he can help us about this.



    And we have 2 users to whom the bootloader unlock method doesn't work. I'll try to look into that, but for now it's the only method I'm aware of.


    I see you've tried to flash the seccfg with a .tiff extension. Why's that?
    I also tried the bootloader unlock method (after the broken boot/recovery message) and got the same result, fastboot saying it was still locked. After i messed with mtkclient flashing some images again or trying the proper mtkclient unlock method (from their github page) but no luck.

    I managed to fix it today flashing with mtkclient the stock boot, recovery and vbmeta images from latest A12 ota, getting into the recovery and wiping all data, and after that the phone was finally working, and I could unlock the bootloader again and flash magisk and so.
    2
    Took a bit of fiddling around, I think I erased a few partitions by accident (due to following the github page's official instructions for how to unlock bootloader)

    Flashing VBmeta from the OTA 12 update file in the mega link above, along with flashing the boot.img and recovery image from the google drive link in the OP should work for most people.

    If you're like me and used the "python mtk e cache[and a few other partitions]" command as instructed by the mtkclient's github page's instructions for how to unlock bootloader (which doesn't work for the oneplus nord 2, so don't bother) I found I had to reflash those erased partitions from my nandroid backup as well. Then for some reason, it seems like vbmeta has to be the LAST partition you flash. As I flashed all sorts of other things, and the phone wouldnt boot, until i flashed vbmeta as the most recent one. No idea why that matters though.


    Have to step away from my computer but currently the phone seems to boot up just fine, I'm going to leave it at the "welcome setup" screen for now and I'll report back if I see anything unusual.

    If anyone else runs in the same issues and got to the fix, just know that if you wiped all partitions, or used someone else's persist.img partition, you'll need to manually flash in the persist image from your own backup or your fingerprint + camera won't work.