Hello I try to play on my OnePlus Nord (AC2003) e/os. I followed the installation instructions.
Unlocking Bootloader - Done
Booting a custom recovery - Done (recovery-e-0.22-q-20220228166118-dev-avicii.img)
Sideload copy-partitions-20210323_1922.zip - **Signature verification failed, Install anyway? ** Error 21
If I skip the step, the same message comes when installing the “e-0.22-q-20220228166119-stable-avicii.zip”. **Signature verification failed, Install anyway? ** Error 21
Can anyone help me with my problem. Thank you in advance.
Markus
Pre-install instructions
at the end of that paragraph we see
Warning: The Recovery will present a screen that says Signature verification failed, this is expected, please click Continue.
It would be important not to skip that step … but to press cancel. (Signature verification does not happen with an /e/ ROM so you are being nudged to accept or acknowledge that.)
Hello Thank you very much for the quick help. I think the real problem is that I didn’t downgrade Oxygen11 to 10 … and therefore have problems with installation and later in use. I have now played Oxygen11 again. These days I will downgrade and start a new attempt to install eOS. For now, thank you very much.
hi, today the new installation started again. Downgrade from Oxygen11 to 10. The installation ran as described. After installation, I did a reboot. The name has now disappeared from the “Files” folder and some APPs can no longer be installed (PayPal). Deleting files is also no longer possible; the file manager then crashes. Something is wrong… and I have no idea what else I can do. Slowly I lose the desire…
Hello Since the installer is now offered for my Oneplus Nord (AC2003), I have made a new attempt to install it. Unfortunately, this one failed. As I have now discovered, the recovery is not accepted; at least the device keeps booting into the bootloader after flashing. By the way, this is also the case when flashing the TWRP version. I was amazed when I tested the Lineage recovery. Here you also have to flash dtbo and vbmeta. This works right away, even microG variant. Maybe someone has a tip for me. Even though Lineage is running great, I would like to switch to e/S with this device as well.
Official documentation is outdated since the structure of the provided .ZIP file has “recently” changed…
You will need an android 14 based stock Oxygen OS installed (or latest available if not exist).
What is the OS running on your PC ?
Have you already unlock the bootloader ?
new 'Installing /e/OS' instructions
.
Unlocking the bootloader
. Tip: The steps given below only need to be run once per device.
Warning: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or an online drive
Warning: Some vendors/manufacturers prevent the bootloader from being unlocked. Depending on where your device was acquired you may or may not be able to unlock the bootloader. To verify if your device is compatible please check the devices list.
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
You can also boot into fastboot mode via a key combination:
With the device powered off
hold Volume Up + Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
5.Tip:* If you see no permissions fastboot while on Linux or macOS, try running fastboot as root.
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.
.
Installing /e/OS
. Tip: For Windows users, we advise to use Git Bash. For more info about Downloads and Installation see Official Documentation
Unzip the archive
unzip <fileyoudownloaded>
Replace <fileyoudownloaded> with the name of the archive file you downloaded.
Alternately you can create a folder and unzip the archive there.
Confirm that extracted directory contains following content:
bin-linux-x86 directory - which contains linux tools including fastboot and adb
bin-msys directory - which contains Windows tools including fastboot and adb
img files - The img files that are to be flashed onto the device.
flash_avicii_factory.sh - The installer script.
Boot into bootloader/fastboot mode.
Power OFF the device.
While holding Volume Down button, plug in a USB Cable that’s connected to a PC on the other end.
Run the installer script on Terminal(Linux) or on Git Bash UI(Windows).
Make sure you are in the current directory which contains the flash_avicii_factory.sh file.Linux
thanks in this part is not clear which file you talk about. I think this /e/OS community avicii download
But as said my Nord is android 12, not 13 or 14 so I cannot find older version?
i made quick research on the web, seems like android 12 based oxygenOS was latest for your device, you should be abble to install e-2.9-a14
you don’t need it anymore to install last /e/ builds with new method, it will be flashed by the install_script,
but you will only need to use recovery in the future to update…
hi,
got the same device, AC2003. fastboot\bootloader says it’s unlocked.
if i fallow the steps from piero
booted into fastboot, then i enter the flash command, then the device boots into recovery mode. if i enter it and press volume down it boots to fastboot again but then i get the error below.
windows, phone reset to android 12.
linux can’t find the device
$ chmod +x flash_avicii_factory.sh && ./flash_avicii_factory.sh
INFO: You are using MinGW on Windows.
INFO: Looking for connected device(s)...
INFO: One OnePlus Nord in fastboot mode found (serial number: XXXXXXX).
INFO: Switching device to fastbootd mode...
Rebooting into fastboot OKAY [ 0.000s]
< waiting for XXXXXXX >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
ERROR: Unable to switch to fastbootd mode.
ERROR: Aborting now (press Enter to terminate).
first i tried the outdated install guide, which soft bricked the device but i was able to restore it with msm, and then updated to android 12 with local upgrade and now i’m stuck here.
i later realized the difference between fastboot/bootloader which is a few lines of text and fastbootd which looks like the recovery interface.
after entering the command, it reboots to fastbootd
then i have the option to select language on the phone but nothing happens on both bash and phone
if i select english i have Fastbootd Mode on the phone with the options Format data, reboot device, power off and advanced (reboot to fastboot or recovery)
should the flashing happening by now? after entering the command, bash just displays:
< waiting for device_serial >
i have tried 4 cables and several usb slots.
before i did reset the phone with msm, i switched the active slots a/b while trying stuff.
fastboot getvar current-slot
after msm the phone is on slot a. booting into android12. if i switch to b and recover it, recovers android 10. just in case this matters.
using windows:
Edition Windows 10 Enterprise LTSC
Version 21H2
OS build 19044.3693
Please try, boot the phone to Fastboot mode (not fastbootd) and check with Device manager that the phone has not become a Problem device now that it is in Fastboot mode. If yes Windows update will find the required “combination driver”.
It might be significant as /e/ will be installing on “the earlier slot”. Some device instruction include an instruction to harmonise partitions with a copy-partitions-script.
I have not read the script for this device. If it helps, the script may well ask for fastbootd at some point, but that would be because the script definitely intends to use fastbootd.
If you are not familiar with fasbootd, it is a “special” for dynamic partition devices. This does rather support the idea that the script is trying to install over “an incorrect Android version”.
will try to uninstall this driver and reinstall with windows update, will post an update if there is any change.
edit: ok it’s doing things.
when it rebooted to fastbootD, it had no driver and showed installed this driver as well and will report back if it succeeds. but with having a driver in fastboot wasn’t enough, it also needs an additional diver in fastbootD. which is something i have not read anywhere.
i now have Welcome to /e/OS so i guess it worked.
thanks for the input, and maybe include somewhere that it needs 2 drivers for both states.
and therefore have problems with installation and later in use. I have now played Oxygen11 again. These days I will downgrade and start a new attempt to install eOS. For now, thank you very much.
Problem device now that it is in Fastboot mode. If yes Windows update will find the required “combination driver”.