Unable to unloack the bootloader on relame X50 Pro 5G

[X50_user]

Hi,

After I run the In-depth Test, and I'm at the stage when I see that the bootloader is locked, when I plug the X50 Pro 5G into a Windows 10 USB port, the device manager shows an "android" generic device, while it shows a "X50 Pro" when the phone is in normal mode.

The adb and fastboot commands can see the X50 in normal mode, but not when it is in In-depth Test mode, all I get is "waiting for any device".

I tried to update the driver of the "android device" with "Realme_USB_Driver" or "latest_usb_driver_windows_2", but Windows answers that the best driver is already installed.

So, I'm stuck, unable to perform a "fastboot flashing unlock" command.

I have enabled the developer options, and OEM and USB debugging.

What am I missing?

Thanks.

 

[ocnbrze]

have you tried a different cable? i would also disable any antivurus program running on your pc. so when you type the command

fastboot devices

you get the "waiting for devices" output?

also it might be better if you grab some screenshots of what is going on and post it here.

 

[X50_user]

have you tried a different cable? i would also disable any antivurus program running on your pc. so when you type the command

fastboot devices

you get the "waiting for devices" output?

also it might be better if you grab some screenshots of what is going on and post it here.

have you tried a different cable? i would also disable any antivurus program running on your pc. so when you type the command

fastboot devices

you get the "waiting for devices" output?

also it might be better if you grab some screenshots of what is going on and post it here.

First, thanks for trying to help. That's vey much appreciated.

I tried a different cable, the one used to fast charge. I also tried a different USB 3 port.

Here are the screen shots.

have you tried a different cable? i would also disable any antivurus program running on your pc. so when you type the command

fastboot devices

you get the "waiting for devices" output?

also it might be better if you grab some screenshots of what is going on and post it here.

First, thanks for trying to help. That's very much appreciated.
I tried a different cable, the one used to fast charge. I also tried a different USB 3 port.
Here are the screen shots.

 

[James L]

Did you use the official bootloader unlock app and validate the bootloader? You should get a review success message then you should have no issues unlocking the bootloader.

Let me look at your fastboot commands.

 

[James L]

Are you in cmd or powershell?

 

[X50_user]

I solved the problem!

I ad to install the drivers from this Japanese file:

QcomMtk_Driver_Setup_V2.0.1.1.exe

from here:

https://www.hardreset.info/download/oppo-qualcomm-cpu-drivers/

and update the "android device with it"

That allowed fastbot to connect.

Did you use the official bootloader unlock app and validate the bootloader? You should get a review success message then you should have no issues unlocking the bootloader.

Let me look at your fastboot commands.

 

[X50_user]

I used the Windows initiated by minimal_adb_fastboot_v1.4.3_setup, you can see the fastboot comands on the screenshots, and the review was successful.

As I said, it worked only after I installed the drivers from https://www.hardreset.info/download/oppo-qualcomm-cpu-drivers/
This tutorial should be updated with this information. The Generic Windows 10 "Android" device does not work.

Now, I have to install TWRP and Magisk!

 

[ocnbrze]

NICE!!!!!!!!!!!!!!!!!!!!!!!!

thanx for posting your solution.

.....now go and get your root on!!!!!

 

[X50_user]

You're very welcome, it would be quite rude not to.

Unfortunately, I'm blocked again. TWRP says that Magisk-v20.4.zip has a wrong signature, same for the 20.2 release, and install fails in both cases.
So, if anybody has an idea...