Database Develop

Huawei p9, EVA-L09-problem with unlocking the bootloader.

Hello!
I am trying to root my phone, which requires and unlocked bootloader.
Here are the steps i have completed:
1. Got the unlock code.
2. Installed adb and fastboot drivers.
3. Installed HiSuite
4. Connected the phone to my desktop (windows 10).
Here i have to mention that the pc recognises my phone, and it is listed under devices. USB debugging and OEM unlock are enabled.
5. I opened cmd in the folder where abd is installed. Checked that abd devices finds my phone (which it does).
Here is where the problem comes in. After booting phone into fastboot (using adb reboot bootloader), i tried to find my phone using the command fastboot devices.
This doesn't find the phone. If i try to unlock anyways, it gets stuck on waiting for devices. I tried the same steps on a laptop (also running windows 10) and the problem stays the same.
Help is appreciated.
EDIT: solved the problem by using a windows 8 installed laptop.

Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.

monoxian said:
Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.
Click to expand...
Click to collapse
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.

Nastmi said:
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.
Click to expand...
Click to collapse
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone

monoxian said:
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone
Click to expand...
Click to collapse
Will try the tool when i get home from school, but fastboot devices doesn't detect my device.
EDIT: The tool didn't work. It is stuck on waiting for device.

Fixed the problem by unlocking on another laptop (has windows 8).

Nastmi said:
Fixed the problem by unlocking on another laptop (has windows 8).
Click to expand...
Click to collapse
Glad to hear that you got it working, I had windows 10 and that worked on mine =\
Sent from my iPhone using Tapatalk

Fastboot "waiting for device"

I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** device
Then I can do "adb reboot bootloader"
Phone shuts down and get on fastboot with this "waiting for device" I got stuck there.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Sent from my SM-A800F using XDA-Developers mobile app

Yeah I'm experiencing this too as well! I just recently updated to 20p and I am trying to root again. I was able to use fastboot to install twrp before. Don't know why this is happening.

This is what I did
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.

Bootloader unrecognized
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.

wish0 said:
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Click to expand...
Click to collapse
[email protected] said:
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
Click to expand...
Click to collapse
Can one of you share a link to the driver you used?

MaRz0o said:
Can one of you share a link to the driver you used?
Click to expand...
Click to collapse
I'm at work won't get off for another 13 hours but like the post maybe two above here it was Marshall something. Go to device manager look for the boot loader adb interface can't remember exactly what it's called and double click it and use the menu option to rollback not update the driver and you should be good. I tried everything else including the one touch and only the rollback worked.

For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!

chromiumfan said:
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
Click to expand...
Click to collapse
Do you have the driver? I have none to roll back to.

Okay...
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!

wish0 said:
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
Click to expand...
Click to collapse
I am having the "waiting for device" issue. But I dont have the "Marshal London" drivers. I have adb 15 sec drivers installed. Any idea where I could get them?

okay another try..
Okay have you tried, while the waiting for device prompt is up, instead of telling your computer you want to select from the list of drivers, to choose automatic: search online for the driver?

Device won't show up on fastboot adb or Mi Flash

So, my MI3W won't show up on fastboot devices command , neither does it show in MiFlash.....
I have installed minimal adb and fastboot also i have installed latest MiPcSuite . Even it doesn't show in device manager . I am runnig windows 10 with driver enforcement disabled .

gauravbhakuni90 said:
So, my MI3W won't show up on fastboot devices command , neither does it show in MiFlash.....
I have installed minimal adb and fastboot also i have installed latest MiPcSuite . Even it doesn't show in device manager . I am runnig windows 10 with driver enforcement disabled .
Click to expand...
Click to collapse
try this
en.miui.com/thread-73348-1-1.html

smh.saad said:
try this
en.miui.com/thread-73348-1-1.html
Click to expand...
Click to collapse
My phone is running fine. Its just that it is not showing up on PC device manager.And I can't use fastboot commands. ADB commands are running fine.

gauravbhakuni90 said:
My phone is running fine. Its just that it is not showing up on PC device manager.And I can't use fastboot commands. ADB commands are running fine.
Click to expand...
Click to collapse
might be windows drivers problem or USB FLex need to be replaced
or a bad USB cable

Help,device not detcted in fastboot

this is my frist time doing this. I follow step by step guide. I even look for solution online and still dont work. I dont know whats wrong. I want to unlock bootloader to install LOS 17.1.
im using windows 10. device not detected in fastboot.
I SURRENDER. I need help. T_T
thank you !

HELP...i tried installing flashtool driver and adb 1.4.3 still dont work

do you think I need original sony cable to be recognized?

ADB / FastBoot drivers are not all you need to access your phone via USB: you must also have the OEM specific "Android USB Driver" installed on your computer.
More here: https://www.getdroidtips.com/download-latest-sony-usb-drivers/

You mean OEM driver is, my device driver (viskan,Xperia sp driver)in picture 2.everytime I manually installed it (device can't start code error 10.)
pictures 3 and 4 show that I successfully installed the oem Sao sony adb driver and still device is not detected in fastboot mode?
I even tried it on windows 7 ultimate same problem.maybe I'm missing something?

[SOLVED] Windows drivers for Honor 4X (Che2-L11). Not detected in bootloader mode

Hi
I'm trying to flash TWRP on my CHe2-L11 via adb but it gets stuck at < Waiting for any device >.
I read somewhere that is because Windows lacks the necesary drivers (although Che2-L11 is listed as "MTP" in the devices connected to my computer).
Where can I find the necessary drivers for Win10?
Thanks a lot
Best,
-a-

OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess? Windows can not automatically find drivers for this...
Then it make sense that I cannot flash the custom recovery until the phone is detected again.
What should I do to have my phone detected in Windows while it is in bootloader mode?
Thanks a lot
-a-

Running windows update found a driver for
Google Android Bootloader Interface
However, ADB still cannot detect it
EDIT: Actually it works! Even though
adb devices
would not list anything when the phone was in bootloader mode, I was able to flash twrp
Problem solved!