OnePlus 8 pro, installer stops

I try to use installer on my oneplus8 pro. Everything goes well until it has downloaded the zip file. After restarting en showing thw menu on the phone with the FastBoot screen with the big Green START he can’t find my phone and installation stops. See picture.

It is from number 10/24

hello @maartje, Welcome to this forum.

you may try another cable, another USB port…

Thanks for your reply. Another usbport already tried. Will try with another cable and let you know

Are you using Windows ??

Is, perhaps, Windows update required while the phone is in Fastboot mode ?

Hello, thank you for your reply. I have Windows 11 en it is fully updated

When the phone is in fastboot and connected to the PC, check device manager in Windows to see that the device appears properly. If there’s a problem with the drivers you’ll see a yellow exclamation point under “other devices”. If that’s the case right click and select update driver from Windows Update. If it’s working properly you’ll see Android Bootloader Interface. It appears under Kedacom USB Device on my system.

1 Like

Thanks, it seems to be the problem indeed.

I have tried to install the driver through Windows update without result.

Than I installed the oneplus8 pro driver (3 times) via the download of OnePlus. It says each time the file must be corrupt. Maybe because it is for Windows 10? I have Win11. It says Bootloader is not correct

Than I installed a universal drive without succes. So now I am without possibilities.

You can raise an issue on the /e/OS installer not working correctly with the OnePlus 8 pro.
That way the team gets an idea of what issue can come up when users try out the /e/OS installer.

the traditionnal way to Install /e/OS on a OnePlus 8 Pro - “instantnoodlep” will be easier and faster than debugging the “web installer”…

I am a complete newbie on this, 70 years old haha. So I choosy the “easy way”. Well, I try the normal setup.

2 Likes

Windows update should be able to grab the correct fastboot driver. I needed the driver on Windows 10. I actually downloaded it manually from the Windows update catalog, but I’d recommend you use the automation, I have a special case in that I’ve disabled automatic driver updates for my own reasons.

I believe you need the phone connected to the computer in fastboot mode for the driver update to occur. I don’t believe Windows will update inactive drivers, not sure on that.

The installer does not always work perfectly for every phone. I have a OnePlus phone as well and it’s one of the easier makes to install from the command line instructions.

You should check your ADB and fastboot devices are working. ADB needs to be installed. From a console window enter “adb devices” with the phone connected in to check its working. Depending on how you installed ADB you may need to specify the full path to adb.exe or “cd” to the ADB directory before calling it.

For fastboot enter “fastboot devices” to make sure it’s working. The phone needs to be in fastboot mode for the fastboot check. To get the phone into fastboot do “adb reboot bootloader”.

In both cases the devices command will return the serial number of the phone. If it returns an empty line it’s not working. These checks are in the instructions.

BTW, I’m an old guy too. I got it installed using the command line instructions and I don’t feel it was terribly difficult.

Hello.
I managed to set the drivers. Normal update of Windows did not, I should install the options. So far so good.

After that I got one step further. It said the phone should be restarted with the fastbootscreen but that was not the case. It restarted with the message that it was rooted and after 5 seconds the normal oneplus screen turned up.

At he moment I have a rooted phone and the program won’t go further.

Complication is that I am not English, so that makes it more difficult

My guess would be that this has happened at the point where Web installer has flashed the e-Recovery image but you now have to very importantly get the phone into the new e-Recovery in order to “break” the Manufacturer’s version of Android.

If you do a standard “Reboot into recovery” you will simply boot into the pre existing Manufacturer’s version of Android Recovery.

The trick is to avoid the phone from doing a standard shutdown and restart cycle. Several contibutors explain it in different words in this thread Problems installing /e/ OS on Oneplus 3 - can't boot into the /e/ recovery mode.

Not all OnePlus use exactly the same technique, your phone may have a menu. Still the same thing, you want to trick the phone into booting to your new recovery, not the old one – booting to the old one wipes, destroys, e-Recovery so you have to repeat the flash of e-Recovery and try again.

One thing to do is to write any question or feedback in your own language, then copy and paste a DeepL Translate: The world's most accurate translator translation to English below.

I just checked of Adb.exe is installed, and it is.

Just tried to do the easy install again and it stopped after the second reboot.
Than I am asked to click build and so on. Seems to be in a circle.

He has not done the whole progress, so I doubt of e/os beeing installed.

I have found out how to get in the fastbootmode, but how further becouse the programm does not work anymore

There is a log. If you can include the log we can say more confidently where the problem is.

Indeed, agreed. The basic install concept is to flash and install e-Recovery … it looks like this

e-RecoveryImage

Getting to this point is what I described in my last post.

This is the half way point where we

It is only after this that we can install the ROM, that is /e/OS.

Where can I find the log?

In Post #1 you show the narrative of what is happening. I think the log is in the lower left of the screen.

I have tried again. The phone is rooted. I place the picture of where I am and where it stops.



You see, the program starts again. I don’t see any log