/e/OS/ clean install on OnePlus 8 Pro issue

The fist command was succesfull:

sudo fastboot flash dtbo dtbo-e-3.6-a15-20260314594290-community-instantnoodlep.img
Sending ‘dtbo’ (24576 KB) OKAY [ 0.846s]
Writing ‘dtbo’ OKAY [ 0.073s]
Finished. Total time: 0.933s

But not the second one:

fastboot flash vbmeta vbmeta-e-3.6-a15-20260314594290-community-instantnoodlep.img
< waiting for any device >

The phone is obviously not responding any more. Should I disconnect the phone and repeat the procedure?

Waiting for any device is generally a very reliable indicator. The phone in Fastboot mode is not on the end of the USB cable.

  1. Could you tell with certainty that the phone was still in Fastboot mode?

  2. You can deliver fastboot commands but perhaps not reliably.

Perhaps look at the whole USB chain. It has been reported that certain USB will not carry fastboot commands or complex fastboot commands. You will need a good quality (full capacity) data cable, so not a thin, skinny cable. Avoid a USB-C to USB-C cable as it may be provisioned through a hidden hub. Avoid USB hubs including any USB hub that might be hidden in the PC / laptop; for predictably good results check (if necessary with a manual) that you are connecting to a USB-2 port soldered to the motherboard.

  1. Ofc rule out any possibility of a loose or dirty USB port on phone, cable or PC.
1 Like

Could you tell with certainty that the phone was still in Fastboot mode?

I have to use both commands with sudo. It worked then:

sudo fastboot flash dtbo <dtbo>.img
sudo fastboot flash vbmeta <vbmeta>.img

New problem emerged though :slight_smile:

sudo fastboot flash recovery recovery-e-3.6-a15-20260314594290-community-instantnoodlep.img
Sending 'recovery' (102400 KB)                     OKAY [  3.516s]
Writing 'recovery'                                 OKAY [  0.378s]
Finished. Total time: 4.070s

Shut down the phone => Volume down + Power => doens't show the Main recovery screen but the bootloader so I can not install from e/OS recovery

This is a well known issue which varies by manufacturer.

This first boot into recovery is the time you break original Android.

When you have flashed recovery you must avoid getting the phone to do a standard shutdown and restart Recovery cycle. This will fail and overwrite the new recovery. The e-recovery will have to be flashed again after any such fail.

I don’t know the phone, a good idea to check OnePlus - 8Pro - instantnoodlep - Documentation Suggestions for ideas from other installs but you must boot direct to the new recovery without shutdown. Some phones will have a menu from bootloader which will allow to “change” to Recovery with no shutdown. Do have this? Edit, found this: OnePlus - 8Pro - instantnoodlep - Documentation Suggestions - #4 by nestabodre

i hope you mean :

sudo fastboot flash dtbo dtbo-e-3.6-a15-20260314594290-community-instantnoodlep.img
sudo fastboot flash vbmeta vbmeta-e-3.6-a15-20260314594290-community-instantnoodlep.img

what about trying :

fastboot reboot recovery

Yes, i did put the file names into the commands respectively. Thank you for checking this!

I think I’m stuck now. Android OS wont start any more so I don’t know how to connect the phone to the computer. The adb devices list and fastoboot devices list aren’t showing any connected devices. I can only access the phone’s bootloader.

Is there any help in this situation?

please share photo of your phone in bootloader mode

I did menage to connect the phone after all. I have also repeated the whole procedure from flashing additional partion on and have succesfuly installed eOS.

THANK YOU BOTH for helping me and staying with me untill the end!

2 Likes

The pleasure was short living :slight_smile: I get a general warning after the restart of the phone:

The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it.

Tried to repeat the whole procedure but Volume down + Power won’t open the Recovery main screen any more. I get a general warning.

Did you ever heard of such an event?

are you sure to not have mixed e-a15 and e-a16 files ?

I have double checked. All the files are e-3.6-a15.

But now that you asked - I’m not sure any more was the original OS Oxygen 13 on Android 13 or the underlying android was 12. As far as I remember they are not always the same :frowning: :frowning:

I did the update of the phone right before the flashing though.

the /e/ build include latest needed firmware parts :

piero@HP-p6-2038fr:~/Téléchargements$ ./payload-dumper-go -l e-3.6-a15-20260314594290-community-instantnoodlep.zip
Please wait while extracting payload.bin from the archive.
payload.bin: /tmp/payload_767291595.bin
Payload Version: 2
Payload Manifest Length: 114821
Payload Manifest Signature Length: 267
Found partitions:
abl (225 kB), aop (205 kB), bluetooth (455 kB), boot (101 MB), cmnlib (401 kB), cmnlib64 (520 kB), devcfg (57 kB), dsp (67 MB), dtbo (25 MB), featenabler (90 kB), hyp (451 kB), imagefv (1.2 MB), keymaster (266 kB), logo (9.6 MB), modem (193 MB), multiimgoem (16 kB), odm (88 MB), product (777 MB), qupfw (57 kB), recovery (101 MB), storsec (25 kB), system (1.7 GB), system_ext (512 MB), tz (3.2 MB), uefisecapp (127 kB), vbmeta (8.2 kB), vbmeta_system (4.1 kB), vendor (542 MB), xbl (4.0 MB), xbl_config (94 kB)

To be honest I don’t understand the data in your post. It’s way to technical for an elderly guy :slight_smile:

Is there a way to restore the eOS on my phone or do you think not? Oneplus 8 pro is not my primary phone. I’m using a Fairphone 6 with eOS so it’s not s big disaster. I would like to use this one too if possible :slight_smile:

https://droidwin.com/fix-the-current-image-boot-recovery-have-been-destroyed/

I menaged to flash the original Oxygen 13 on Android 13 so I’m now back to square one.

I tried with windows 11 this time but ran into problems again. The phone is now unlocked. I tried the procedure on page /e/OS Installer . I got to the step where ROM was successfuly downloaded to the phone. After the restar to a bootloader the phone can not be connected to go on with procedure. The error is:

Error on step: connect-bootloader

Cannot execute command connect bootloader
The device is not connected Failed to connect: Cannot connect to bootloader after 3 attempts. The device may not be in bootloader mode yet. Please ensure the device is in bootloader/fastboot mode and try again. Error: Failed to request USB device: Failed to execute ‘requestDevice’ on ‘USB’: Must be handling a user gesture to show a permission request.
Proposal: Check connection and that no other program is using the phone and retry.

Do you have any ideas why?

because even well illustrated, the “web-installer” often don’t work,

and because the install instructions provided by /e/ can be imbuvable for some new users and can lead to errors.

here is a safe guide to install /e/OS

Install /e/OS on a OnePlus 8 Pro - “instantnoodlep”

Looks like your OP. Try Post #5

With the screen beeing unlocked software downloaded but after the restart of the phone in bootloader mode after trying to connect the phone to a computer a new connection error has appeared.

What is the output for

fastboot devices

?