Exactly.
I did the update to android 11. Let me guess, will getting back to android 10 be complicated now? It certainly has to be… 
Is there an instruction that can I follow?
Might be. Depends.What is the device state at the moment? Can you boot it to stock? I guess not if you’ve been wiping and formatting.
I’m making enquiries to see if there is any more helpful info.
Thank you chris, I really need help.
Yes, I was able to start the stock rom, I downgraded to Android 10 by following a guide.
Then I flashed the e-recovery and copied the contents of slot A to slot B as it says in the guide.
Now I have to try to flash with the e-recovery instead of TWRP.
What do you mean by formatting data in e-recovery?
Can you tell me the steps more precisely?
Well done with the downgrading!
I can help you continue, no problem, but a quick word or two about what’s in store for this device would be good if you have the time.
I know that there is a build in testing at the moment for R, so in the near future this device may be moving on to R. In addition to that there are a number of other one plus devices moving on to R this week.
Yourself and many other oneplus users are going to have to install stock android 11 before flashing e OS R.
I don’t know how easy it is to return to stock after flashing a custom rom but I’ll have to find out in order to help a friend of mine who has a oneplus 6 running e!
I’ll post again in a few minutes with some instructions for flashing with e-recovery.
Ok but the planning is up to the end of the year and there is no Oneplus Nord. So will it be in 2022?
If I can flash the e-rom with e-recovery, can’t I do the same thing with the stock rom and then upgrade to Android 11?
Thats right. Flash the e-recovery onto device in the same way you did earlier. Can I ask what command you use for that? Did the given example in the install instructions work, or did you use another? It would be helpful to know. 
It’s just factory reset really, but it formats data as well. Slightly different steps to twrp but achieving the same results more or less.
- When e-recovery home screen is up and running, select Factory reset. Next select Format Data/factory reset.
Screen will go white and output at bottom left (very small letters) when done.
- Return to e-recovery home screen (if not already there, can’t remember ) and select Apply update. Next select Apply from ADB.
If device wasn’t plugged to pc, plug it in now and issue the command to sideload the OS zip.
Terminal output should now show " serving"something or other as the zip is transferred across, with a percentage amount.
It will stop at 47% (all being well) and everything is being done on device. Watch the on screen output for Step 1 and then step 2. Its quite slow and you may think nothing is happening, but wait until the recovery screen changes and you then press the back arrow at top left. Output should show install status.
Press reboot system.
I don’t know. I’m trying to find out.
It’s different steps to return to stock, you can’t do it from custom recovery. Not sure of the procedure at the moment but I’ll be researching over the weekend.
But I don’t think it’s impossible, we will surely find how to do it.
What are the differences between Q and R?
Can you link me where they explain it?
I do not find it sorry.
One cannot flash stock OOS from custom recovery, I believe.
There is no definitive post to explain diffeneces between Q and R, but I would say not much. In fact Q may be preferred at the moment; for its stability, amongst other things. Main difference is Q will become unsupported first.
But this is a bit off topic
When it’s time to switch to R I’ll think about it.
I did as you said with e-recovery. It works!
Over the weekend I will try a bit this OS and write a message here with all the steps I took to install it, so if anyone needs they have a summary. Thanks chris!
2 Likes
Hey, congratulations Sheriff!! That’s great. Enjoy e.
Sorry, but what command works to install recovery?
The command was “sudo fastboot flash recovery recoveryfilename.img” as in the guide but runned as root with the sudo command (otherwise it doesn’t work).
1 Like
Could you please post a link to the guide in Nord documentation thread, it may help others
Sure, it’s a guide that just came out on November 10 on getdroidtips.com
Really easy
https://www.getdroidtips.com/downgrade-oneplus-nord-android-11-10/
Can you link me the Nord documentation thread? I’m sorry I can’t find it
1 Like
Sure ! It’s here : OnePlus - Nord - avicci - Documentation Suggestions
Thank you for your help improving documentation 
Hi sceriffo,
Can you put here the required instructions that are required to install /e/ os on a oneplus nord?
Regards
Fak
Yes, later today or tomorrow I will.
1 Like
I wrote the procedure but I can’t post it because new users can insert a maximum of two links per message.
I have to ask a moderator to unlock this limit otherwise I have to write more messages and it gets a bit confusing…
1 Like
Pl send me the post in a message and also the location where you want to post it and I can do the needful.
I wrote an email at contact@e.email because I can’t direct message you
The procedure is as follows:
-
Back up your phone data if necessary.
-
Charge the phone battery to at least 50%.
-
Enable ADB and fastboot on your PC. Instructions here: Installing adb and fastboot on Linux PC
-
Download the Q stable /e/OS ROM and the e-recovery from the official link: /e/ image ROM download
-
Enable developer mode on your phone and then enable USB debugging from developer options. Instructions here: Enable USB Debugging and OEM Unlock
Unlocking the bootloader:
-
Enable OEM unlock in the Developer options under device Settings, if present.
-
Connect your device to your PC via USB.
-
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type: “adb reboot bootloader”
-
Once the device is in fastboot mode, verify your PC finds it by typing: “fastboot devices”
Tip: If you see “no permissions fastboot” while on Linux or macOS, try running fastboot as root (typing the command “sudo” before the command “fastboot …”). I runned fastboot as root from here to the end of the procedure.
-
Now type the following command to unlock the bootloader: “fastboot oem unlock”
-
If the device doesn’t automatically reboot, reboot it. It should now be unlocked.
-
Since the device resets completely, you will need to re-enable USB debugging to continue.
Booting a custom recovery:
-
Connect your device to your PC via USB.
-
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type: “adb reboot bootloader”.
-
Once the device is in fastboot mode, verify your PC finds it by typing: “fastboot devices”.
-
Flash a recovery image onto your device by typing “fastboot flash recovery recoveryfilename.img”.
Replace the “recoveryfilename” with the name of the recovery image you downloaded in the previous section.
- Now reboot into recovery to verify the installation.
Pre-install instructions (copying the content of the slot A to the slot B):
-
To do this, sideload the “copy-partitions-20210323_1922.zip” package by doing the following:
-
Download the “copy-partitions-20210323_1922.zip” file from here: copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
-
Sideload the “copy-partitions-20210323_1922.zip” package:
-
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
-
On the host machine, sideload the package using: “adb sideload copy-partitions-20210323_1922.zip”.
Warning: The Recovery will present a screen that says “Signature verification failed”, this is expected, please click “Continue”.
So far was the official guide summarized, from here it’s chrisrg’s instructions.
Installing /e/ from recovery:
- When e-recovery home screen is up and running, select Factory reset. Next select Format Data/factory reset.
Screen will go white and output at bottom left (very small letters) when done.
-
Return to e-recovery home screen (if not already there, can’t remember ) and select Apply update. Next select Apply from ADB.
-
If device wasn’t plugged to pc, plug it in now and issue the command to sideload the OS zip: “adb sideload filename.zip” changing the “filename” to the name of the file you downloaded (probably e-0.19-q-20211027142972-stable-avicii.zip if you didn’t changed it.).
Terminal output should now show "serving"something or other as the zip is transferred across, with a percentage amount.
It will stop at 47% (all being well) and everything is being done on device. Watch the on screen output for Step 1 and then step 2. Its quite slow and you may think nothing is happening, but wait until the recovery screen changes and you then press the back arrow at top left. Output should show install status.
Press reboot system.
- Done.
Let me know if there is any problem, I checked very well but I could be wrong. I wrote this procedure a few days after doing it.
6 Likes