I'm trying to work out unlocking bootloader, but when I get to the point where device should be in fastboot mode, and on computer I write fastboot oem get_unlock_data command in cmd, it shows "waiting for any devices" and nothing happens. Tried writing fastboot devices, but it shows blank list.
USB drivers are PROBABLY installed with some bugs, I cannot install nor unistall them now idk why, during installation process it shows error "Parameter is incorrect" and then Motorola Driver Installation Utility shows up, which stays at half of the process of scanning drivers. When I choose the "clean only" option, Runtime error shows up at some point. Choosing update driver does nothing.
Any ideas what to do?
turn on your mobile and make this cmd.
adb devices
a window will open on your mobile, check the box and restart the unlocking of the mobile.
lohanbarth said:
turn on your mobile and make this cmd.
adb devices
a window will open on your mobile, check the box and restart the unlocking of the mobile.
Click to expand...
Click to collapse
Did it, checked the box. Nothing have changed, still "waiting for any device "
Sarid said:
Did it, checked the box. Nothing have changed, still "waiting for any device "
Click to expand...
Click to collapse
your debugging usb and enabled?
lohanbarth said:
your debugging usb and enabled?
Click to expand...
Click to collapse
Yes
Sarid said:
Yes
Click to expand...
Click to collapse
did you install the adb drivers?
lohanbarth said:
did you install the adb drivers?
Click to expand...
Click to collapse
Installing adb drivers helped, thank you very much
Related
I have been trying to do this new method to unlock my DNA but im having difficulties getting my computer to recognize my phone. I installed the app and followed directions perfectly. But when i enter fastboot and enter the "fastboot oem readcid" command in the command prompt window it says "waiting for device". I have my phone connected via USB and i followed all directions, i want to unlock and get rooted. Anyone who could help or just tell me what i am doing wrong i would appreciate it very much Thank You.
did yaa enable enable usb debugging?
also what do you get when you do
Code:
fastboot devices
munchy_cool said:
did yaa enable enable usb debugging?
also what do you get when you do
Code:
fastboot devices
Click to expand...
Click to collapse
Yes i enable debugging, and when i get to the fastboot screen and enter the command "fastboot oem readcid" in the prompt window it excepts the command and says "waiting for device" like the PC is not recognizing my phone.
Guessphx said:
Yes i enable debugging, and when i get to the fastboot screen and enter the command "fastboot oem readcid" in the prompt window it excepts the command and says "waiting for device" like the PC is not recognizing my phone.
Click to expand...
Click to collapse
that's why i asked you to do a fastboot devices when in fastboot mode as that would list the devices attached, also are you on mac or windows and if windows which windows version, also please PM a mod and ask him to move this to the DNA q&a section, you'll get more help there.
As soon as I get back to the house in going to do that. But I have a PC with windows xp that I'm using.
Sent from my HTC6435LVW using xda app-developers app
I'm following the stickied unlocking bootloader and root thread.
I got to step 13. type this into your command prompt window fastboot oem get_identifier_token
It says waiting for device.
I got search in the thread and come across
ckpv5 said:
"waiting for device" usually means the usb bootloader driver is not installed.
Connect your device in fastboot mode. Open your device manager, manually update driver for that "android 1.0".
Attached here both driver for 32bit & 64bit. Use the one that suit to your PC.
Click to expand...
Click to collapse
I download the driver and follow instructions here
ckpv5 said:
I'm also on Windows 7 64bit.
What you need to try is, hopefully what I remember is correct ...
be on fastboot usb
open device manager, on the "android 1.0" :
update driver software
browse my computer for driver software
let me pick from a list of device drivers on my computer
android usb device
next
have disk
browse to the driver you downloaded (browse up to *.inf)
it will detect as my htc
next
ignore any error
the usb bootloader driver will be installed
EDIT : Tested.. the above step is correct.
Click to expand...
Click to collapse
Windows 7 says "The folder you specified doesn't contain a compatible software driver for your device."
I try using the Google driver from the android adk but that doesn't work either. I also tried letting windows update find it. Those drivers won't work either.
when you are in fastboot mode and connect it to the usb. you should now see fastboot usb. if you do not see "fastboot usb" you are not connected. something with your drivers
intrepid9 said:
I'm following the stickied unlocking bootloader and root thread.
I got to step 13. type this into your command prompt window fastboot oem get_identifier_token
It says waiting for device.
Windows 7 says "The folder you specified doesn't contain a compatible software driver for your device."
I try using the Google driver from the android adk but that doesn't work either. I also tried letting windows update find it. Those drivers won't work either.
Click to expand...
Click to collapse
Download the latest HTC Sync Manager, it will install all the drivers needed.
Then you can uninstall the Sync Manager if you want to but leave the drivers.
http://www.htc.com/www/software/htc-sync-manager/
jaredl45600 said:
when you are in fastboot mode and connect it to the usb. you should now see fastboot usb. if you do not see "fastboot usb" you are not connected. something with your drivers
Click to expand...
Click to collapse
I do see fastboot usb
ckpv5 said:
Download the latest HTC Sync Manager, it will install all the drivers needed.
Then you can uninstall the Sync Manager if you want to but leave the drivers.
http://www.htc.com/www/software/htc-sync-manager/
Click to expand...
Click to collapse
Thanks. It works!
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,
I try to flash my OP3.
I did first the UNLOCK, that worked with the CMD (Running Windows 10).
My device is Unlocked.
But when I wanna try fastboot flash recovery recovery.img
Or I type then it says waiting for device...
and when i typ: fastboot devices
then if gives nothing.
Yes, I did the OEM unlock in developers options en USB debugging is on.
HELP!
HELP!
Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.
peterk-1 said:
Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.
Click to expand...
Click to collapse
Yes, I did that.
But not working...
Over WiFi it's working, but not with USB.
Oke, ADB is working, but only when the device in ON.
When I does the device in Fastboot.
Than it doesn't work!
HELP!
Oke, I fix it.
Did it in an VM with Windows 7.
Bye.
YourTheBest said:
Oke, I fix it.
Did it in an VM with Windows 7.
Bye.
Click to expand...
Click to collapse
I'm also stuck with this, could briefly tell me how you set up a VM with window's 7 please? I tried with Ubuntu but no luck installing the adb and fastboot? Stuck with no recovery so please help
First Tick OEM unlock and enable usb debugging. And install latest driver
Ajshal said:
First Tick OEM unlock and enable usb debugging. And install latest driver
Click to expand...
Click to collapse
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
How did you install the driver? do you have windows 8 or above?
daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
I have same pblm on my LG K10 dude
therightperson_630 said:
How did you install the driver? do you have windows 8 or above?
Click to expand...
Click to collapse
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10
daviss101 said:
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10
Click to expand...
Click to collapse
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3
therightperson_630 said:
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3
Click to expand...
Click to collapse
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck
daviss101 said:
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck
Click to expand...
Click to collapse
go to device manager and manually uninstall kedacom driver and install minimal adb/fastboot from the link I posted, they'll install the driver automatically
daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.
YourTheBest said:
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.
Click to expand...
Click to collapse
How do I get a free version of windows 7 without downloading a cracked ISO?
I have a mi a2 lite and i want to unlock its bootloader, i have alrready enabled oem unlocking on developer options, when i boot my device in fastboot and connect to computer, command window says waiting for device and after 15-20 seconds of connecting my device to my pc, fastboot mode automatically exits and shows charging animation. Please anyone can help?
My device is in andoid pie (stable).
Check if you have installed drivers and run "fastboot devices" to see if device is recognised.
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
hossman said:
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
Click to expand...
Click to collapse
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
I've tried restarting my pc as well as my phone and after 5-6 attempts it is now unlocked.
Thanks guys for supporting and giving response to my post
Love ya'll
CherryFarmer8 said:
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
Click to expand...
Click to collapse
same problem boss, did you already solved this? please help me out
Andrew.kathy said:
same problem boss, did you already solved this? please help me out
Click to expand...
Click to collapse
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
capajga said:
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
Click to expand...
Click to collapse
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
CherryFarmer8 said:
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
Click to expand...
Click to collapse
I also have this problem drivers are installed and fine but when I go to fastboot within like 15 sec it automatically turns off.
I fixed it with this https://forum.xda-developers.com/attachments/howto_driver-zip.2480396/