Related
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Install HTC Sync, then reboot your computer
JvIo55iBl3r said:
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Click to expand...
Click to collapse
I did, actually. As a matter of fact, i do have that sync icon in my task bar
I am not sure, but i was wondering if the adb driver is necessary to be installed?
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
adseguy said:
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
Click to expand...
Click to collapse
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
JvIo55iBl3r said:
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
Click to expand...
Click to collapse
this should definitely be in the Q&A board, not the developers board.
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Exit HTC sync first on your computer so it is not running or just uninstall it. It should find it after that.
joeykrim said:
this should definitely be in the Q&A board, not the developers board.
Click to expand...
Click to collapse
Sorry about that, will do next time
joeykrim said:
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Click to expand...
Click to collapse
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
JvIo55iBl3r said:
Sorry about that, will do next time
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
Click to expand...
Click to collapse
any help? anyone?
UPDATE: Got it working on a windows 7 machine.
I've been trying to unlock my bootloader but have been having issues. I have done the following:
- Enabled Developer Options
- Enabled USB Debugging
- Enabled the OEM Unlock in the Developer Options
- Installed drivers via android SDK
I have adb and fastboot installed from the android SDK. Using that, I have been able to see my device with 'adb devices'. I have also been able to reboot it using 'adb reboot bootloader'. However, once the phone is in fastboot, it does not seem to be detected by my machine. I have tried 'fastboot devices' to no avail. Using 'fastboot oem unlock' just stalls at '< waiting for device >'. Am I missing something?
I have also tried:
- Using a different computer
- Using different USB ports
- Using different ADB / fastboot package (the minimal one).
Please assist! I'd really like to unlock my bootloader now for future flexibility.
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.
yourbuddypal said:
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.
Click to expand...
Click to collapse
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"
amitte said:
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"
Click to expand...
Click to collapse
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working
yourbuddypal said:
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working
Click to expand...
Click to collapse
Yes this is normal. For the bootloader part, do not let windows search automaticly. Do as i described earlier exept use the driver i uploaded for you or search any other nexus usb driver install guide since the process did not change
Same applies to the installation when you are in the system already. Exept do not override any driver that is under portable devices since its the file transfer protocoll driver.
I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!
yourbuddypal said:
I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!
Click to expand...
Click to collapse
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solution on Linux
I had a similar problem earlier today on one of my linux boxes. Turns out, in order to use fastboot (successfully) under linux, you need to run fastboot with sudo rights.
If I had to guess, I'd guess this is because unlike adb, fastboot doesn't run as a server, so fastboot always needs to get elevated permissions to communicate with a device on a USB port.
Maybe it's possible that Windows wants Administrator rights for similar reasons?
duckxtales said:
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
Click to expand...
Click to collapse
Sorry, I really don't have any more feedback to give you. It really did seem like voodoo when it worked. The only thing I can think to explain the "random" aspect is that perhaps it is related to the quality of cable used. I was using these (http://www.amazon.com/Orzly-Type-Cables-Assorted-Colours/dp/B013RMG5WY/ref=cm_rdp_product), which have now been taken down due to cable standards as described in the comments section for that product. I was thinking that maybe the different USB port on the desktop machine was somehow able to get sufficient voltage or something. Voodoo!
I am having the exact same issue with my 6P right now. However it shows when I do adb devices, just not fastboot devices. Weird...
I even uninstalled the Google USB driver and reinstalled it using Android Studio but Still did not work. Then I even went to Device Manager and uninstalled and deleted the driver. Then went manually to file path C:\Users\MyWindowsLoginName\AppData\Local\Android\sdk\extras\google\usb_driver and clicked next. It installed successfully, but displays as Android Composite ADB Interface. So I guess that is correct then?
Tried to just sideload the new 6.0.1 OTA update using adb since adb devices was recongizing it but still not found...
C:\Users\Matthew\AppData\Local\Android\sdk\platform-tools>adb sideload angler-MMB29M-from-MDB08L.zip
loading: 'angler-MMB29M-from-MDB08L.zip'
error: device '(null)' not found
EDIT: I got it after unplugging my phone, killing the adb.exe process in task manager, waiting until in bootloader before plugging phone in, then running fastboot devices shows the serial number now. I hope that helps others!
I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?
I had the same trouble on my 64 bit Windows system. I believe it was HTC sync software that threw the monkey wrench. But I uninstalled that software together with all the adb fastboot drivers for my other devices, removed all adb fastboot versions, then installed the 64 bit version of the Minimal adb fastboot tool.
All good now
Garvinr said:
I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?
Click to expand...
Click to collapse
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Thank you.
I follow this step. now I can use fastboot.
crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
Thanks man! Worked immediately after updating the drivers!
I too had this issue.
Manually installed drivers using this guide.
(pretty much the same instructions as wangxiangg, but with pics)
wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Man. That was it. Worked like a charm. Thank you.
To clarify, you do this while you are in Fastboot Mode and you right-click on "Android" in step 1.
You can go through the steps while you are in Fastboot Mode and with the cable still plugged in.
amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Someone give this man a cookie!
it worked!!!!!!!!
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/