I installed /e/ on a brand new OnePlus Nord today following these instructions: Install /e/ on a OnePlus Nord - “avicii”. As I am new to /e/, and there is no explicit TWRP installation step in the instructions, I mistook the recovery system as downloaded (recovery-e-0.19-q-20211027142972-stable-avicii.img) for TWRP. I failed to find the “wipe” buttons described and, after much contemplation, finally resolved to upload the new /e/ firmware via adb without prior formatting.
Now the device is in a boot loop and displays endlessly the bouncing e logo. I can force power off (Vol+ and PWR for 10 seconds). Upon repowering I get the warning message about the unlocked boot loader and I can interrupt the boot process (PWR button), but nothing much happens after that.
Adb and fastboot cannot make a connection to the device.
Any chance to revive the phone? Any help much appreciated!
I meanwhile managed to boot into fastboot (power off, press VOL- and PWR long).
I then uploaded the recovery image again (fastboot flash recovery recovery-e-xxx.img) and booted into it.
More when I have the courage to go on, need some sleep now…
@chrisrg: thanks for the support. I now understand that the /e/ recovery does the required formatting, making TWRP unnecessary. Partitions are copied (the ‘a’ and ‘b’ slot thing, right?). With the given instructions I did the formatting and I am now just ready to sideload /e/ via adb from the recovery image.
However, I am not sure whether I upgraded to Android 11 by following the instructions for installing /e/. I confess I did not pay much attention as I expected everything to be replaced with /e/ anyway. Apparently /e/ does not replace the whole installation, though.
How would I downgrade to Android 10 at this stage?
I come at this more intuitively rather than technical ( in some aspects) in the sense that I “feel” that a full set of restored partitions of the desired Android 10 is called for as the base for the eOS?
On that xda thread though it says it is only for unbranded phones, and I’m not sure I understand that. Do you ?
I am agree with you a clean, base in safer !
Here another interesting xda thead to restore back to earlier version, even if bricked (that’s not the case here)
The restore method looks promising. I shall download it and look at the *.bat to see where I can hook up into the process.
The branded/unbranded thing is probably a SIMlock to a carrier, it makes sense that this cannot be broken through a stock ROM. My phone has no such limitation so it should not be a problem.
I would use branded loosely in those circumstances to describe “Carrier branded” - I see no real references to that and any locks. This would be an example of a branded phone https://www.pocket-lint.com/phones/news/oneplus/157327-oneplus-nord-n200-release-t-mobile-specs but I cannot tell if that is what he refers to. Just my two cents, but @chrisrg’s path seems safe: or I might ask the author on the thread before committing.