Hello team,
I've been trying to unlock the bootloader of my device for the last couple of days. I have tried installing the drivers from LG suite, couple of drivers from the forum and google as well.
When i try to type in the command line oem device-ID i get "waiting for device"
According to the internet this is an issue with the drivers.
Can anyone suggest suitable ADB drivers ?
gogobaba said:
Hello team,
I've been trying to unlock the bootloader of my device for the last couple of days. I have tried installing the drivers from LG suite, couple of drivers from the forum and google as well.
When i try to type in the command line oem device-ID i get "waiting for device"
According to the internet this is an issue with the drivers.
Can anyone suggest suitable ADB drivers ?
Click to expand...
Click to collapse
did you select usb debuggin in developers options.?
when you go iinto fastboot did you allow phone to acces adb in phone screen?
Yes to both of your questions. I'm using windows 10 x64 with the latest drivers for my laptop
Related
Trying to unlock my bootloader and I'm having the dreaded problem of adb, fastboot and google usb drivers not working.
Tried the idiotic Sony documented way of installing Android SDK and development tools, tried 15 Second ADB, Flashtool and Minimal ADB installers - after doing all three of these and then running Flashtool it informs me that drivers need to be installed for the device.
Running "fastboot devices" results in no message at all, running "fastboot device" results in a "waiting for device" message.
Any ideas please?
diji1 said:
Trying to unlock my bootloader and I'm having the dreaded problem of adb, fastboot and google usb drivers not working.
Tried the idiotic Sony documented way of installing Android SDK and development tools, tried 15 Second ADB, Flashtool and Minimal ADB installers - after doing all three of these and then running Flashtool it informs me that drivers need to be installed for the device.
Running "fastboot devices" results in no message at all, running "fastboot device" results in a "waiting for device" message.
Any ideas please?
Click to expand...
Click to collapse
Do a search on how to install unsigned drivers on windows 10, that should fix your problem
Cheers that fixed it although using BCEDIT didn't I had to use the restart method.
diji1 said:
Cheers that fixed it although using BCEDIT didn't I had to use the restart method.
Click to expand...
Click to collapse
Cool
Now don't forget to backup your TA partition before unlocking your bootloader...
Happy rooting
I got my OP3 today and am trying to unlock the bootloader. I've tried every tutorial and toolkit out there but they all get stuck at the same point in adb, "waiting for device". The "adb devices" command works fine but anything else gets stuck on "waiting for any device". I've tried googling the issue but none of the suggestions have worked so far. Any input would be great.
did you enable oem unlocking from developer options?
bro you may be running win 10 and to connect fastboot on that u need adb driver which u will find on windows update all u have to do is just connect your phone with data transfer mode and update the window 10 . ull find something name qalllcom its adb drive or i dont but after that it will like charm.
I have all the necessary developer options checked. After futzing with it for hours, I tried a different computer (also Windows 10) and it worked right away. I'm going to see what the driver issue is this evening because I still would like to use the original computer I was using. Thanks for the replies!
What does "adb devices" return?
aadityarulez said:
What does "adb devices" return?
Click to expand...
Click to collapse
Screenshot:
for bl unlock, you need to be at fastboot mode, and installed right driver, for me working any of stock Google USB package fastboot bootloader driver.
Go to fastboot mode and do "fastboot devices", then try unlocking bl.
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
harish15 said:
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
Click to expand...
Click to collapse
I've tried everything including disabling driver enforcement on Win 10 but I still have the same issue. I have the wrong drivers installed. I've tried uninstalling and reinstalling the drivers but when I plugin the phone, the wrong drivers get installed. I got it to work on another Windows 10 computer and below are device manager screenshots of the working (with right drivers) and not working (with wrong drivers) computers. I have no idea how to get the right drivers installed on the computer where its not working and unfortunately, its the primary computer I use.
shobuddy said:
I've tried everything including disabling driver enforcement on Win 10 but I still have the same issue. I have the wrong drivers installed. I've tried uninstalling and reinstalling the drivers but when I plugin the phone, the wrong drivers get installed. I got it to work on another Windows 10 computer and below are device manager screenshots of the working (with right drivers) and not working (with wrong drivers) computers. I have no idea how to get the right drivers installed on the computer where its not working and unfortunately, its the primary computer I use.
Click to expand...
Click to collapse
Right click, uninstall the wrong drivers.. Tick delete button too in the dialog prompt. Try installing now.
Sent from my Xiaomi Mi 5 using XDA Labs
harish15 said:
Right click, uninstall the wrong drivers.. Tick delete button too in the dialog prompt. Try installing now.
Sent from my Xiaomi Mi 5 using XDA Labs
Click to expand...
Click to collapse
I've tried this several times over. I do not get the tick option to delete.
shobuddy said:
I've tried this several times over. I do not get the tick option to delete.
Click to expand...
Click to collapse
Pm me, if case, you need some guidance.
Sent from my Xiaomi Mi 5 using XDA Labs
Same here. When I reboot in fastboot mode, the driver adb interface disappears and I get the Android Bootloader Interface (Kedacom USB Driver).
"waiting for any device" each time.
Thx for help
shobuddy said:
I've tried this several times over. I do not get the tick option to delete.
Click to expand...
Click to collapse
Try this:
Connect the op3 to usb port - don't bother changing from "charging"
Right click on "ADB Interface" in dev man and disable it.
Without unplugging the op3 use the buttons to reboot into bootloader.
Hopefully W10 will now detect your op3 and either load the correct "oneplus" driver or create a new entry in dev man of Other Devices > Android Composite ADB Interface. Right click on this and then Update driver software > Browse my computer.... > Let me pick... > and if you're lucky One plus will show up in the manufacturer column and allow you to select the composite interface
peterk-1 said:
Try this:
Connect the op3 to usb port - don't bother changing from "charging"
Right click on "ADB Interface" in dev man and disable it.
Without unplugging the op3 use the buttons to reboot into bootloader.
Hopefully W10 will now detect your op3 and either load the correct "oneplus" driver or create a new entry in dev man of Other Devices > Android Composite ADB Interface. Right click on this and then Update driver software > Browse my computer.... > Let me pick... > and if you're lucky One plus will show up in the manufacturer column and allow you to select the composite interface
Click to expand...
Click to collapse
I tried this but didn't see any new/different entry in DM when I rebooted into bootloader. Didn't see OnePlus under manufacturers either.
cyspak said:
Same here. When I reboot in fastboot mode, the driver adb interface disappears and I get the Android Bootloader Interface (Kedacom USB Driver).
"waiting for any device" each time.
Thx for help
Click to expand...
Click to collapse
Okay so this is the problem. I figured it out 2 days ago.
check the bootloader driver when you're in fastboot. Right click it and update driver, it should be the Android Bootloader 9.00, and not Bootloader 11.00
it's a silly weird fix, but it should be under Android and not Kedacom
I was using the Android SDK Studio Platform Tools and Google Drivers provided from SDK Studio
deleted
Similiar to the previous users post I'll try and be a bit more clear.
unplug your device if plugged in.
boot in to fastboot mode on your device.
Go to your PC and access device manager
plug your device in and you should see
"kedacom" instead of android interface
now inside you wanna click update driver
browse my compute for driver software > let me pick from a list of driver software > "Android adb sooner interface"
if its not that exact one check for the one that does say adb interface.
https://www.youtube.com/watch?v=Gdl6P2akRK0
I created a bootable USB drive with Linux Mint to solve my problem. It was Windows 10 that would recognize my OnePlus 3 in "Fastboot Mode" with Kedacom drivers.
Hi all!
I'd like to unlock my bootloader, but fastboot just saying "waiting for any device". ADB works fine and i use "adb reboot bootloader" command to enter fastboot mode.
I think that i have installed all drivers. I tried three different computers and usb 3.0 and 2.0... nothing. ADB works with every machine, fastboot doesn't.
What can i do? Is there any other way to get Device-ID? Need help. Stock ROM is awful
sorry for the wrong section, can you move this to Q&A
My phone has exatly the same issue...The key is the usb driver...With the stock LG drivers the fastboot did not work to me either.
1, uninstall any lg drivers from your os
2, install PdaNet universal usb drivers
3, enjoy!
When i finish with the fastboot, i installed back the LG drivers for the correct MTP communications, but it's not neccesary!
Give it a try, good luck!
Use Ubuntu Linux on USB Stick
no driver issues just works
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Hmmm..
edshawn911 said:
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Click to expand...
Click to collapse
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
RaiderWill said:
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
Click to expand...
Click to collapse
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
edshawn911 said:
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
Click to expand...
Click to collapse
Ok... Since I have no intention to root until Huawei pushes the Oreo and Facial Recognition updates, I have kept USB Debugging "OFF" and set Select USB Configuration to: Media Transfer Protocol (MTP)
Then, I attempted to do what you are trying to do... and it worked perfectly..
So.. Do This:
Step 1 Click on your windows icon and in the search bar type "CMD"
Step 2 Set USB Configuration to MTP.
Step 3 Again I had Debugging off.. you can try it with it on if you like.. either way turn off your device.
Step 4 Hold down the Vol-Down button while plugging your device into your USB cable connected to your computer.
Step 5 This will turn on your device and put you in Fastboot Mode.
Step 6 Now go to your ADB Command Line and type "fastboot devices"
You'll see it.....
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Mambobuzzz said:
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Click to expand...
Click to collapse
This is a problem related to Windows 10 that uses the wrong driver.
Somewhere I have found a guide to manually choose the correct one, but at the moment I don't remember where... googling you will find instructions
Mambobuzzz said:
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Click to expand...
Click to collapse
This is not the Q&A section. Please post your questions there, according to the forum rules. Can a moderator please move this? Thanks.
Monfro said:
This is a problem related to Windows 10 that uses the wrong driver.
Somewhere I have found a guide to manually choose the correct one, but at the moment I don't remember where... googling you will find instructions
Click to expand...
Click to collapse
I've googled it. Tried many. Event tried to boot Windows without driver signature. Didn't work. :/
michie said:
This is not the Q&A section. Please post your questions there, according to the forum rules. Can a moderator please move this? Thanks.
Click to expand...
Click to collapse
Oh sorry.
Does someone have an idea?
This might come a year too late, but in case someone else runs into the same problem (like myself), you can solve it by installing the latest (signed) ADB drivers with this Tool, then rebooting the tablet to fastboot mode and run the tool again. This still doesn't install the correct fastboot drivers, but it should now be listed as "ADB Interface" -> "Unknown Device" in the device manager, and if you right click and choose "Update driver" -> "Browse my computer for driver software", you should see a driver called "Fastboot interface (Google USB ID)", that installs and works correctly for the Pixel C.
@Mambobuzzz
One option you have and it's been updated this month too, is you could try installing and using tiny adb & fastboot from here: https://forum.xda-developers.com/t/tool-windows-tiny-adb-fastboot-august-2021.3944288/
I can't stand Windows for a few reasons! Make a live USB and try a Linux distro! You will never have this problem again and I guarantee you won't miss Windows.
Edit added:
Reasons why this is happening:
Bad connection somewhere.. The USB connection you are plugging in to on your PC could be messed up, the USB cord could be messed up, or where your type c plugs in to your device is messed up.... Oooorrrrr it's driver issue. And knowing Windows I betcha it's a driver issue. When you plug your tablet in are you enabling USB debugging and developer options and changing the "default USB configuration" from "Charging" to "File tansfer ?" And when you do those things are you watching the table REALLY CLOSELY for the little box that pops up for 5 seconds that you MUST put a checkmark in otherwise adb and fastboot will not work? Reboot a few times on your PC and update the drivers in Windows Device manager.. I remember once I had to reboot 3-4 times to finally get mine working. When you type adb --version then push enter in terminal and fastboot --version push enter what does it say?