Database Info

[Q] [solved] Reverted from EOS to stock, now unable to update to 3.1 (green bot of !)

Hello,
I have the MZ601 (Xoom UK 3G) and had EOS Everest JB stable on it.
Now I wanted to go back to stock. I downloaded the original firmware from Motorola, flashed the img files with adb and everything was fine (I did not relock the bootloader). The first OTA went fine too, now I am on Android 3.0.1 (H.6.1.-38-1).
It now detects the next OTA (about 44 MB, 63.5.25.en.EU), downloads it, tries to install it but at about 1/3 of progress the green bot of ! appears. I reflashed the stock firmware several times now, same result.
Then I googled, flashed Tiamat CWM recovery, rooted the device and then did:
adb remount (got message: succeeded)
adb shell rm /system/recovery-from-boot.p (message: no such file or directory)
adb shell rm /system/etc/install-recovery.sh (no message, so guess it worked)
Now I have no idea what else to try. I'd like to get back to stock ICS.
edit: reflashed back to stock once more. This time I entered recovery mode before I applied the very first OTA and the green bot of ! already appears, what's wrong here?

Hi,
It looks like your problem is not big deal. Just try flashing again all the files and principally DON'T FORGET TO FLASH RECOVERY! And I don't see why wouldn't you lock bootloader , if you really wants it unlocked and go to stock ICS I'd recommend you to flash stock, lock bootloader and then you update, after you get to the version you want unlock again :thumbup:
Wish you the best luck
Any problems please give me an up!

​Thanks for your reply!
I think I flashed recovery with the specific adb command (see below), not sure, not really an expert. :/ I even wiped dalvik cache and factory reset in cwm recovery before flashing back to stock.
Here's what I did in detail when reverting to stock:
I downloaded MZ601_H.6.1-38-1_Retail_Europe.zip from the official Motorola website, extracted all files and used these commands in adb:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Also, I noticed the green bot of ! appears after reboot when I enter recovery mode even before I flash the very first OTA (so just after flashing the stock files and reboot). Looks like recovery is somewhat broken or so?
I didn't want to relock the bootloader simply because I might want to root the device once I am back on stock ICS. Basically, I just wanted to get away from a custom ROM (Team EOS).
Would locking the bootloader make a difference for my success? According to google it doesn't but I am no expert to judge it right.

Yea, it looks like something is going wrong there...
Try downloading the files again, and then flash recovery. If you have no success try locking your BL, maybe it can works. The two times I went back to Stock I relocked my BL and had no problems to update via OTA. Then you relock your BL and use LordAIOTool to root again, which can easy your work...
Also you should try erasing system, recovery, cache and data before flashing, but it looks like what you did is fine.
Good luck

Thanks! I will give that a shot and post the result here.
By the way, that is one thing I read about and didn't dare to try yet: formatting system.
From what I read, after formatting /system the tablet will no longer be able to boot into android. In that case, how can I perform adb commands still? Afaik USB debugging has to be on but I will not be able to get into settings (due to lack of boot) and turn it on (and it will be off after reflashing afaik).

When you format system you can't boot in Android, but you can still flash things via fastboot, which uses a different protocol from adb. There was one time I had to format system to fix a cellphone, but if you don't want to try that, no worries , it may turn out without risking

I believe in order to upgrade you need to lock the BL. Once you update you can unlock it again.

Okay, downloaded the image again, this time via XDA. Suprisingly, all files were flashed in less than a min each (sometimes flasing system.img took half an hour or longer). Same result though. Since I forgot to lock the bootloader I flashed everything again after reboot:
Code:
>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 49.293s]
writing 'boot'... OKAY [ 2.155s]
finished. total time: 51.477s
>fastboot flash system system.img
sending 'system' (262144 KB)... FAILED (remote: (00120003))
finished. total time: 1196.176s
Not sure why it failed here, worked dozens of times. So I simply decided to reflash system.img once more in the same run:
Code:
>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.391s]
writing 'system'... OKAY [ 14.744s]
finished. total time: 40.136s
Worked fine apparently, then continued from there as normal:
Code:
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All went well this time, no error messages on the latest full reflash or locking bootloader. Then rebooted, and now it is stuck at the Motorola boot screen:
Code:
Failed to boot LNX 0x0004
Starting RSD mode 2
(charger information bla bla here)
Not sure why this happened and what this actually means? It won't boot up and since the bootloader is locked I can't enter recovery or anything. What do I need to do now?

Man... You forgot to flash the kernel (boot.img)!!! And it's probably appearing because of this small mistake!!! Now that you're on RSD Mode 2 you have to fix it another way... I never went to it (only went twice to mode 3), so sorry, I can't help you this time , I will search a little and see what I can do for you.

My mistake on posting, I did flash boot.img before that, corrected my previous posting.
Now I am stranded. And I can't even turn off the device on boot screen.
edit: rescued it, thanks to this posting:
Pushed power + vol up for reboot, waited 5 sec, then held vol down until fastboot appeared (kept pressing the button for about 17 sec until fastboot showed up).
Once there, I unlocked bootloader successfully again to flash all stock files. Xoom booted up bravely afterwards, phew.

Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.

Landorin said:
Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.
Click to expand...
Click to collapse
Glad you made it
Congrats!!

[Q] HELP - NVFlash Bootloader failed

I'm on ICS and never upgraded to JB. I've just unlocked my bootloader so I can do NVFlash Backup and start flashing ROM's.
I unlocked without any problems. I've rebooted into bootloader and selected the USB icon. My computer found the drivers and correctly identified as 'ASUS Android Bootloader Interface'.
From the guide http://androidroot.mobi/pages/tegra3-guide-nvflash/
I ran the command
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
I got the following output from my Windows console
Code:
sending 'staging' (1002KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 7.935s
On my tablet appears
Code:
Failed to process command download:000fa98d error(0x120003)
Also the device now appears in my windows device manager with the following error
Code:
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
I've not rebooted my tablet for fear of this question...
Have I bricked my tablet?
P.S. At this point I haven't attempted to reboot my device because I'm worried it might never come back.

So I've been crawling around the internet for anyone else who's had this problem and the only person with a similar issue is
http://forum.xda-developers.com/showpost.php?p=32222050&postcount=110
So since my OP, I've removed the USB cable from my laptop, plugged it back in and I can see my TF300.
When I run
Code:
fastboot devices
I get
Code:
00000 fastboot
Which I assume means my computer can see it?
At the moment I've still not rebooted. From what I've read Staging partition is applied at boot, which I assume means no changes have been made yet?
Because my transfer failed, will anything be applied from Staging on next reboot? Or should I run a command now to prevent any changes?
Thanks

Any help on this will be much appreciated.
Just to clarify, I've still not rebooted my device since I attempted the flash and seem to have access to Fastboot. I don't want to reboot unless I know it's safe to do so.
Thanks!

I thought this morning I'd try and change my drivers and run the command again.
I thought first I'd use Universal Naked Drivers, when I select the INF 'android_winusb.inf' file I get two options both called 'Asus Fastboot Interface'.
If I select either of these I get the following error
The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tempered with.
The other option I do seem to have is under manufacturer 'Google, Inc.' I've got 'Android Bootloader Interface'. Is that any better?

So I eventually got the Universal Naked Drivers to work (after disabling Driver signature enforce from Windows boot options) and I could see my device in device manager and from 'fastboot devices'.
So I re-ran
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
And this time it also failed with another message. In my console showed
Code:
sending 'staging' (1002 KB)...
FAILED (remote: (AccessDenied))
finished. total time: 0.014s
And my TF300 displayed the line
Code:
Failed to process command download:000fa98d error(0x30010)
But this time, I can no longer see my device from device manager or 'bootloader devices'. Windows doesn't even make the 'device inserted' sound when I plug it in.

So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks

psjw12 said:
So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks
Click to expand...
Click to collapse
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.

daws said:
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.
Click to expand...
Click to collapse
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.

psjw12 said:
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.
Click to expand...
Click to collapse
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan

Claudii said:
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan
Click to expand...
Click to collapse
That's odd, it's like Fastboot says image was deployed but then it doesn't apply the change. Thank goodness there's a staging partition on Asus! I also had the problem of the device disconnecting whilst trying to flash and then not showing up.
How does the tablet show up in your device manager? As 'Asus Fastboot' or 'Android Fastboot'? Mine was ASUS and I was thinking of trying the Android driver instead.
I've not tried to flash mine again since trying, I'm going to wait for an appropriate time for me to have a heart attack if it all goes wrong
Edit: The next command it wants to issue is
Code:
fastboot -i 0x0b05 reboot
I wonder if that what makes it commit the changes? Hopefully someone can answer that for me.

[Q] Huawei Ascend G6-L11 Unlocked. Error on system img flashing.

Hi, so I got this phone about a month ago, with stock rom and filled up with bloat and unnessecary crap. So being the fundamentalist I am, I rooted this phone too (5th android phone I've had), and started playing with it.
By default, the bootloader is locked, so I unlocked it using Huawei's website unlock helper and fastboot.
I have no memory card to go with this phone, so I've had to try out the fastboot/adb way of doing this, and so far it's been a hit and miss.
I've been testing with SlimStock KK, and with Ascend G6 Mod, and I'm able to flash the boot and recovery successfully, but when it comes to flashing the system, it fails. Here's the output of that:
Code:
Karls-MBP% fastboot devices
90587873 fastboot
Karls-MBP% fastboot flash system /Volumes/ODIN/karleirik/Downloads/Firefox/Huawei_Ascend_G6-L11_Modded_B370_ROM/SYSTEM.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.039s]
sending 'system' (1048576 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (Undefined error: 0))
finished. total time: 26.000s
So right now my device is softbricked. Does anyone know how to get around this problem ? Or have another approach to flashing it?
Edit: I might add that I've tried different system images, and different hardware USB ports on my laptop to no avail. I have also tried the flashall, which fails due to no product ID and adb sideload <zip> fails because of a timeout:
Code:
* failed to write data 'protocol fault (couldn't read status length): Connection reset by peer' *
- Phossk

Phossk said:
Hi, so I got this phone about a month ago, with stock rom and filled up with bloat and unnessecary crap. So being the fundamentalist I am, I rooted this phone too (5th android phone I've had), and started playing with it.
By default, the bootloader is locked, so I unlocked it using Huawei's website unlock helper and fastboot.
I have no memory card to go with this phone, so I've had to try out the fastboot/adb way of doing this, and so far it's been a hit and miss.
I've been testing with SlimStock KK, and with Ascend G6 Mod, and I'm able to flash the boot and recovery successfully, but when it comes to flashing the system, it fails. Here's the output of that:
So right now my device is softbricked. Does anyone know how to get around this problem ? Or have another approach to flashing it?
Edit: I might add that I've tried different system images, and different hardware USB ports on my laptop to no avail. I have also tried the flashall, which fails due to no product ID and adb sideload <zip> fails because of a timeout:
- Phossk
Click to expand...
Click to collapse
Try putting the .zip file inside your adb and fastboot files and just type the .zip file name when flashing instead of the whole path to the .zip
Hope this will solve your problem.

2nd life for PH-1?

In a long and painful process I've lost most of my trust in being able to revive my good old PH-1 to life.
When updates stopped, I moved to the Pixel 4 and gave the essential to my son, with the (unofficial) lineageos and TWRP installed. I surely changed to January back-to-stock, otherwise TWRP would not be installed. That's what happend next (summary):
- lineageos stopped working, system wasnt't booting any more
- Junior went into twrp, could not decrypt phone, wiped system, changed boot slot, for what he told me.
- downloaded Carbon Rom 5 and tried to flash it via twrp
- ignored the warning (no system installed)
- reboot to recovery leads to carbon rom recovery (errors showing up at the bottom). No adb connection can be established. Rebooting via hardware leads back to TWRP, obviously on the other slot.
- My decision: Back to Stock again! -> Reboot to bootloader. fastboot devices is showing my device.
[email protected]:~/devices/essential/QQ1A.200105.007_Jan2020-NOVENDOR$ ./flashallnowipe.sh
target didn't report max-download-size
sending 'abl_a' (780 KB)...
- phone keeps hanging there, no response.
Now there is no recovery any more. Pushing a new recovery does not succeed:
[email protected]:~/devices/essential/QQ1A.200105.007_Jan2020-NOVENDOR$ fastboot devices
PM1Lxxxxxxxx fastboot
[email protected]:~/devices/essential$ fastboot flash boot__a lineage-17.1-20201116-recovery-mata.img
target didn't report max-download-size
sending 'boot__a' (25737 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
Now: any hope? Where to start?

well, it has been quite while, but since I got through about the same you may be having here, let me give you a few hints that worked for me to resolve a soft-brick of my mata device.
Make sure you have the latest platformtools from from a reliable source.
Restart your computer and also your phone after any error message.
Best is to go back to stock, but after LOS you may need to flash the boot.img with the following command:
fastboot flash:raw boot_a|b [stock_boot.img]

Was in the same situation and this helped me to sort out the flash recovery problem:
fastboot flash:raw boot_a recovery.img
Just enter correct value - boot_a or boot_b and the right name of your recovery instead of rcovery.img
Btw. if you have problem to use flashall, then you can always flash manually - each part by yourself. They are listed in flashall file. You can read it by any text viewer
(I use a Linux Ubuntu based machine for works on phones. Even live distro booted with just on fly installed fastboot and adb works fine)

I was getting all sorts of fastboot errors, despite the device accepting ADB commands. The solution was to use a different USB cable on a different USB port. This Essential mata has a stubborn USB port. It only works with the correct cable, port combo. Some people say you must use USB3 other say they used USB2. I've seen the same thing with VR headsets only working on certain USB controllers. So keep trying different things.

Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.

Hello, friends. So I am here following this exact tutorial :
How to Restore OnePlus Nord Back to Stock OxygenOS Software - A Complete Guide
In this guide, we will show you how to restore the stock OxygenOS software on the OnePlus Nord by flashing the factory image/Fastboot ROM. Things like custom ROMs, TWRP, and Magisk root are pretty…
www.thecustomdroid.com
I currently am stuck there
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (1996 KB)...
OKAY [ 0.055s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.057s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock_critical
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
Click to expand...
Click to collapse
I just simply do not understand what could be wrong here.
In fastoot mode I get "device - State unlocked"
As you already saw, it seems the device is completely unlocked. What could be wrong ?
Also, some steps before, I get that :
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
I suspect switching to the automated in Windows won't change much.
It is strange because I am able to perform these steps without problems, ones the ones after seem to not work :
./fastboot flash boot boot.img
./fastboot flash dtbo dtbo.img
./fastboot flash modem modem.img
./fastboot flash recovery recovery.img
./fastboot --disable-verity flash vbmeta vbmeta.img
./fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
My phone is a Oneplus Nord and I am using the advised Oxygen OS ROM provided in the tutorial I linked at the beginning of my message.
I hope you'll be able to get me out of this as I unfortunately can't figure out how to solve this problem on my own.
Best regards

krakard said:
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Yes, that makes sense.
Fastboot should be located at /usr/bin/fastboot. Since you're not in that directory, ./fastboot won't work. (This ./ means: "Look at the current working directory for the command fastboot." If it cannot find fastboot there or it isn't a shell command, it will throw an error.)
However, since you didn't install fastboot globaly, you have to address its exact path inside your platform-tools folder. If fastboot is not in Partition-image folder, ./ won't work.
Can't help you with your main issue though.
Edit: You seem to have fastboot installed globally though:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
So my first explaination is valid.

Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.

krakard said:
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
Click to expand...
Click to collapse
You're welcome.
BTW:
krakard said:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
There is no "fastboot" to boot into. Instead, type
Code:
fastboot reboot bootloader
I didn't mention that yesterday for some reason.

Guys, here is where I am at now. Still struggling but I feel I am very near ! Some help maybe ?
https://forum.xda-developers.com/t/...your-device-to-oxygenos.4148415/post-85022511
best regards

SOLVED

krakard said:
SOLVED
Click to expand...
Click to collapse
How did you fixed this? I'm currently stuck at the same point as you with a oneplus 8

Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?

mbootsman1 said:
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
Click to expand...
Click to collapse
I found the solution, you have to do fastboot reboot fastboot which reboots you to fastbootd instead of fastboot. There you can flash critical partitions without issue.

Hi,
As the command recommanded everywhere :
Code:
fastboot flashing unlock_critical
had never worked for me in the bootloader environment,
I have to reboot i my rom embedded recovery in order to flash the file (apply update menu) through the :
fastbootD
To sum up :
#From Android (while having all prerequisite done ie bootloader unlocked...)
Code:
adb reboot bootloader
#From the bootloader I choose to boot to recovery and I get to the rom custom recovery
#In the custom recovery, I choose the menu "apply update" that will lead me to the fastbootD mode
#I type the appropriate command to flash the persist partition
Code:
fastboot flash persist "c:\your_path_to_your_persist_file\persist.img"
#Then I simply reboot the phone
Code:
fastboot reboot
PS : Initially flash the OxygenOS (OOS) 11, then apply the CRdroid Android v8 custom rom (based on Android 12)

I did it similar like solid-snake:
In my case I also had no access to fastbootD
The solution came randomly when I flashed back the first part from my lineageOS package:dtbo.img, vbmeta.img and the recovery.img --> after that my phone naturally booted in a fastbootD mode from the lineageOS package.
I modified the flash-all.bat from the stock ROM fastboot flash package:
I removed the line with the reboot command, because I'm already in the fastbootD mode.
Then I ran the modified flash-all.bat and everything went well.

If anyone else struggles (like I did) to get the phone in EDL mode, or the "Flashing is not allowed for Critical Partitions" error ,even if the "fastboot flashing unlock_critical" cmd was executed, here are some hints that might help.
I tried forever on a Linux computer without any luck, so I ended up installing Windows 10 on actual hardware to finally unbrick my One Plus Nord (Avicii). Here are the most important steps, YMMV, execute at own risk:
bcdedit.exe /set nointegritychecks off run this cmd as admin in terminal, toggle to "on"
then install edl drivers as admin, This is where I struggled the most, I finally found an .exe file(QDLoader HS-USB Driver_64bit_Setup.exe) that I just installed and then phone showed up as it should in device manager. ("Qualcomm HS-USB QDLoader 9008," not "QUSB_BULK")
install adb and fastboot. (platform-tools)
install MSM-Download-Tool
download stock OS for use in MSM-Download-Tool program
open msm tool, if phone is not recognised try turning on and holding power pluss both volume, or just one of the volumes.
uncheck the "sha hash check" box
flash
if you get the "Sahara Communication Failed", just try again, it worked for me.
wipe
erase Windows 10 and replace with any Linux distro, tell your PC it will never happen again.
enjoy
Here are link to the EDL-drivers that worked for me. Or just do a web-search for "QDLoader HS-USB Driver_64bit_Setup.exe"
The flashing process will take over 300 seconds, be patient.