I tried the easy installer and ran into the problem, that apparently the checksum doesn’t match the downloaded /e/ rom file. I tried several workarounds and I gave up.
No I tried the “old way” and got to the point after flashing the recovery.
My OnePlus 8 now only boots into fastmode but not into the recovery.
(For clarification: Right now I have Lineage 20 installed on this phone, so the bootloader was already unlocked).
Can anyone send me in the right direction?
KInd regards, Take Care!
I flashed twrp as recovery in fastboot. But when I tried to get into recovery the phone just rebooted to fastboot.
Then I tried to boot into the twrp recovery with “fastboot boot twrp.img” which was the wrong command. It sent “boot.img” from lineage and gave me the error message “fast boot : error : command failed.”
BUT: I suddenly found myself in the Lineage recovery??
After factory resetting using the Lineage recovery I tried to sideload eOS via ADB. As mentioned in the official installation instructions it paused at 47%. The phone gave me two error messages:
Signature verification failes and
Error 21
The recovery gave me the option to ignore the failed signature verification which I said “yes” to.
The phone ran on with Step1/2 and Step 2/2.
Now the recovery said “To install additional packages you need to reboot recovery first. Do you want to reboot to recovery now?”
There I also replied yes. But I am stuck at fastboot mode again.
Only a technicality, but /e/ does not add additional packages so the answer is really no.
Just a thought, have you ruled out that your Lineage maybe more recent than the (unknown) version of /e/ and you are attempting to downgrade Android SPL.
I only skipped the unlocking of the bootloader because it was already unlocked due to Lineage. Problems began already wit the custom recovery. After flashing the eOS recovery the phone booted only in fastboot mode. The same happened with twrp.
So from the first link in my last post you can see the /e/ naming convention. The r in e-1.19.1-r- represents Android 11 (R). For a device already on Lineage 20 you should probably try the most recent dev build from https://images.ecloud.global/dev/instantnoodle/e-1.19.1-t-20240113373116-dev-instantnoodle.zip
I am going mad here.
I can’t get into the EDL mode which is needed for the MSM Tool. I used all the methods - everytime the phone is connected to the PC it starts into fastboot mode.
I also can’t seem to flash any recoveries although the command console tells me that the flashing process was successfull. When I try to get into recovery mode it is fastboot mode once again.
Do you @aibd have any suggestions? Is this a hard brick?
I flashed and rooted so many phones in the 2010s but never experienced such a case ;-/
Thanks @Xxpsilon - but I can’t boot into the FastbootD mode which the tool should do.
I arrive always in fastboot mode.
Should I try to flash the payload.bin anyway?
The tool says: The following partitions to flash may be unknown: odm product system system_ext vendor reserve. You may need to reboot to fastbootd mode.
The last method of getting into EDL mode is using TWRP. It’s the bottom option in the reboot menu. Note: This method doesn’t require for TWRP to be installed. You can simply fastboot boot into TWRP to achieve the desire results.
In my experience you can only move to fastbootd under certain circumstances – my guess would be that an existing failed (and / or Android 11) recovery is a potential blocker. Is the presently flashed Recovery Android 13 (despite it not booting), that is does it match the firmware ? Edit … but match of recovery to firmware is not the only issue which a Super partition might bring.
(Step 6b: Manual method)
But I got only to step 3: fastboot reboot fastboot
I receive the error message Failed to boot into userspace fastboot; one or more components micht be unbootable
Try it out Fastboot Enhance Tool from