Hey! Does anyone know how to get ADB Debugging work with Xiaomi 5S?
I've tried all day, but although developer options are enabled (and usb debugging), my pc doesnt recognize my phone as android-device, only as media-device.
My phone also doesn't even ask me to accept the Computers fingerprint...
Hello,
Just install Mi PC Suite and it should install correct drivers for phone. Don't forget to uninstall others.
AlexShostak said:
Hello,
Just install Mi PC Suite and it should install correct drivers for phone. Don't forget to uninstall others.
Click to expand...
Click to collapse
Well the Mi PC Suite I tried said it wasn't compatible with Mi 5S :/
I tried to uninstall in device manager, but it doesn't include deinstall drivers, so I don't know if there are other old drivers....
Edit: Mi PC Suite doesn't seem to work with Marshmallow
Sounds like you don't have original rom installed, what is the exact software version on your phone?
towadroid said:
Well the Mi PC Suite I tried said it wasn't compatible with Mi 5S :/
I tried to uninstall in device manager, but it doesn't include deinstall drivers, so I don't know if there are other old drivers....
Edit: Mi PC Suite doesn't seem to work with Marshmallow
Click to expand...
Click to collapse
I had the same problem Even now Mi PC Suite cannot recognize my phone. Of course, I forget: turn off USB-debugging...
---------- Post added at 02:24 PM ---------- Previous post was at 02:15 PM ----------
Oh sorry. If you want that your phone will be recognizable by pc via cmd-fastboot, turn off USB-debugging. Turn off the phone. Hold power button and Volume Down, wait till fastboot loaded. Then pc (I have Win10) will install needed drivers. Then you will able to see your device in cmd <fastboot devices>
I had problems with this but fastboot. adb worked but fastboot failed. Try this method maybe it might work for you as well
1. you need to have miflash installed on your computer first first
2. in device manager update the bootloader interface driver with the google driver that comes inside the C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver folder
but for your problem maybe try the same as above but instead of bootloader interface driver, do it for ADB interface driver. note that windows10 you may have to disable driver signature verification for this.
patoberli said:
Sounds like you don't have original rom installed, what is the exact software version on your phone?
Click to expand...
Click to collapse
It's the original Rom for phones in China, Android 6.0.1MXB48T with MIUI 8.0.10.0. I didn't flash another Rom.
@Derodraaa solved the problem for me!
So if anyone has the same problem, what worked for me was:
1. Uninstall all adb related drivers
2. Use "minimal adb and fastboot"
Related
Hi all, Purchased my Galaxy Nexus today - First thing on the list; Unlock and Root.
I have downloaded all of the necessary files but cmd is stuck on < waiting for device >
My phone is in fastboot mode but i cannot get this command to work to unlock the bootloader - I have installed the Samsung drivers... Is there anything I am missing here?
Any help or suggestions welcome, Thanks!
Try with a different USB cable if you can.
I had the same issue (device not being found) using the cable that came with it, so I swapped it for the one that came with my Desire and it worked fine.
Worth a shot.
Cheers! I'll give it a try!
Just tried my original Nexus One USB cable but no luck - I'm thinking it could be something to do with the drivers?
lexarjump said:
Hi all, Purchased my Galaxy Nexus today - First thing on the list; Unlock and Root.
I have downloaded all of the necessary files but cmd is stuck on < waiting for device >
My phone is in fastboot mode but i cannot get this command to work to unlock the bootloader - I have installed the Samsung drivers... Is there anything I am missing here?
Any help or suggestions welcome, Thanks!
Click to expand...
Click to collapse
If you run "fastboot devices" and there's nothing found, then you need to install the fastboot drivers (these are not the same as the USB debug drivers from the zip).
I've found the easiest way to get the drivers is to install pdanet - as part of the installation process you install all needed drivers. You can then uninstall pdanet (or in my case, have the installer crash), leaving just the fastboot driver for you to carry on your rooting
lexarjump said:
Just tried my original Nexus One USB cable but no luck - I'm thinking it could be something to do with the drivers?
Click to expand...
Click to collapse
mybe, you can try fastboot devices and check if the device is found.
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
braingravyuk said:
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
Click to expand...
Click to collapse
Honestly, not willing to check this one after spending today setting up my device, and no custom recovery available yet.
But given it's a Nexus device, and noting the ease with which we can unlock, then I'd say it's a pretty surefire bet that relocking will be just as easy.
Thanks alot! It worked
I'm looking to just unlock the bootloader of my Galaxy Nexus which will hopefully arrive tomorrow morning. I currently have AndroidSDK and samsung drivers both installed on my pc as well as a file called fastboot.exe. my question is do I need both the Samsung Drivers as well as AndoidSDK installed for this?
rock7632 said:
I'm looking to just unlock the bootloader of my Galaxy Nexus which will hopefully arrive tomorrow morning. I currently have AndroidSDK and samsung drivers both installed on my pc as well as a file called fastboot.exe. my question is do I need both the Samsung Drivers as well as AndoidSDK installed for this?
Click to expand...
Click to collapse
I think PDAnet should be sufficient
Proyoyo said:
I think PDAnet should be sufficient
Click to expand...
Click to collapse
okay thanks
I tried all day yesterday to unlock bootloader with no success. I installed the latest sasmsung usb drivers for mobile (released on 31/10/2011). This allowed the PC to recognise the phone installing the drivers properly. But then starting the phone in recovery mode (power+up+down bottons) I get the android 1 not recognised in device manager.
I then saw this thread and decided to install pdanet 3.02 client on the pc. I couldn't complete that step as pdanet cannot see the phone.
I gave up in the end. If you manage to do it successfully could you please tell me the step you did?
I am going to try tonight on my mac as apparently on mac you do not have this drivers issue. Will post with my results.
---------- Post added at 10:41 AM ---------- Previous post was at 10:34 AM ----------
By the way the latest samsung usb drivers can be found here:
http://forum.xda-developers.com/showthread.php?t=961956
---------- Post added at 11:39 AM ---------- Previous post was at 10:41 AM ----------
Forget my previous post.
Installing pdanet and saying no to install the usb drivers (as part of pdanet install) everything should be fine.
Done mine and working fine.
Thanks.
braingravyuk said:
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
Click to expand...
Click to collapse
yes
fastboot oem lock will lock it
Hey I seem to be having some troubles as well,
windows 7 recognizes it as an ADB device and when I use - adb reboot bootloader
it takes me to the fastboot screen that it should.
but once I'm there it doesn't recognize any fastboot devices.
And yes I have reinstalled the SDK, Samsung drivers, and Android ADB driver
Would it matter that I had previously done a bunch of messing around with my ASUS transformer on this computer?
under device manager it says:
ASUS Android Devices - Android ADB Interface
I'm going to try it on another computer tomorrow but I'm curious if that should make a difference.
The driver failed to install on my phone...when I reboot into my bootloader it looks a bit different from in the video. Mine just has an android and it says start above it. The oem unlock command fails to do anything as well.
Why is nothing ever simple?
Does your phone need to be connected when you install the samsung drivers on it? Or does it install these drivers after booting into the bootloader?
When I install the samsung drivers on my computer with the phone connected, it says the following:
Android phone: No drivers found
Samsung Mobile USB Composite Device: Ready to use
Samsung Mobile MTP Device: Failed
Samsung Android ADB Interface: Ready to use
When I hold the volume buttons and power it on now, it just goes straight to the google logo...not even getting the android logo with the start option anymore. I think I might have accidentally uninstalled the ADB drivers in my device manager because I saw 2 copies and thought I installed it twice...
Hi
ADK is working fine with my other devices, but my PC can't seem to install the drivers for Huawei Watch. The devices is in the device manager, but a little yellow triangle at the side, which means the device drivers are not installed.
I have tried Google, but the guides just say install the devices drivers but clicking update in Device manager with the xx file I downloaded, but windows can't see the file.
Thanks in advance
only pdanet drivers works for me for adb but in twrp i cannot connect to pc . how have you solved the issue i have same problem in device manager. tried more than 6 ways after googling pc
i've tried pdanet drivers 64bit on my win7 64bit version.
but the installation cannot continue.. did u success installing pdanet ? what version of your windows u have ?
why is this marked as solved because i dont see the solution. i just received my watch today and cant seem to get device manager to recognize any drivers.
PDAnet doesnt fully install because i cant install drivers
Minimal ADB and fastboot dont recognize any devices attached
Universal Naked driver 0.73 doesnt work even after modifying the android_winusb file
I even installed the Google USB driver from the SDK Manager, but i dont see anything on my machine.
ive had this watch for 2 hours and already frustrated as hell lol. can someone provide assistance?
thanks!
PS. im running this on Windows 7 64 bit and the watch is at LCB43B already
same problem with me.. attaching usb cable into charger dock, detect huawei watch in device manager but drivers cannot be installed..
what's the problem ? which drivers can be used ?
hendry said:
same problem with me.. attaching usb cable into charger dock, detect huawei watch in device manager but drivers cannot be installed..
what's the problem ? which drivers can be used ?
Click to expand...
Click to collapse
i was trying all day on my work computer which runs windows 7 x64 with no luck, but the watch was detected immediately on my windows 10 machine at home. strange.
Success!
I fixed my issue! I had the same issue everyone here mostly had. I could unlock the bootloader, but I couldn't get the Fastboot recovery to work because the drivers were not detected by Windows 10, or my other Windows 7 machine. Both machines installed a standard version of Google Android device drivers and boot loader drivers, but they were not detected by ADB commands once in the bootloader.
First I went here to download all the drivers, but got stuck:
http://www.thecountrycaller.com/37260-how-to-unlock-huawei-watch-bootloader-and-flash-twrp-recovery/
So what I did was ran the commands to reboot to bootloader, then flash commands for the recovery, left my device plugged in. Then I went into the Windows Device manager, and looked for the Android or Adb drivers loaded. I double clicked the driver, and clicked on uninstall driver, and told windows to delete the drivers. I then unplugged my device (still in bootloader mode), plugged it back and in windows instantly detected the ADB flash commands and boom, TWRP recovery completed.
Hope this helps some of you.
this did not solve my issue ive installed the drivers and nothing over and over can someone help me with the drivers please
thanks
running windows 7
tried to install every driver possible
Weird as it may be, I managed to get Hwatch to connect to ADB via USB by installing the watch as a Motorola Android Sooner Composite ADB Interface - in device manager-update driver-select from PC-select from device list-android usb device-motorola
Is there anything what i can do when my classic watch is NOT recognized on both pc and notebook? I hear no sound, i can´t see anything in device manager...any help?
Hi I`m using the huawei 2 LTE version - can I take the same driven from here or will that cause problems ?
---------- Post added at 08:11 AM ---------- Previous post was at 08:09 AM ----------
Is this may be a real help https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
MrHaPpY66 said:
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
Click to expand...
Click to collapse
Have you enabled oem unlocking from developer options?
I'm having the same problem. After going back to Oxygen OS (now 3.5.4) from MIUI 8 fastboot just doesn't work anymore. ABD works just fine (tried on Minimal ABD and Fastboot on Windows and ABD installed over Android Studio on Ubuntu. Fastboot did recognize the phone on Ubuntu but flashing TWRP resolved in a bootloop (tried the old and the new recovery image).
All drivers are installed on both Windows and Ubuntu (I even removed all drivers on Windows and added them again) and just to make sure everything gets installed I disabled driver signature verification on Windows, but as I said - still no luck.
Edit: Of course USB Debugging and OEM Unlocking is enabled (my bootloader is also unlocked since I already had tried out multiple roms)
Had the same Problem, Win10 is the Problem + the old OP Drivers + the new Update to Win10 etc.
Nothing worked, tryed everything. Created a Thread last week here also...
After that i created a new Partition and installed Win7 on it. All works fine, only thing is while Boot ur System u have to pick ur OS or it waits 30sec to boot up but thats ok.
Now i have Win10 for everything and i reboot to win7 for Fastboot/OP3
http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Didnt tryed the last Tip.
KornY10 said:
Win10 is the Problem
Click to expand...
Click to collapse
Can't solve your problem, but OP3 fastboot does work in Windows 10. I did have to disable driver signature verification to install the driver in the first place, and you'll have to leave it off for the driver to stay functional, but it definitely works on Win 10.
I dont tryed ur Way, so yes after disable Driver sign. it works like u Said but i did not Test it.
i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .
Same here
It's driving me crazy. I've updated from a rooted stock OS (incl TWRP) via full OTA directly to 3.2.7, which removed TWRP and root.
I now cannot enter a Fastboot mode which detects the USB connection. Thus I can't flash TWRP again and can't root my phone, making lots of apps unusable.
I've tried every suggestion on every thread but nothing works...
Sent from my ONEPLUS A3003 using Tapatalk
Also got kedacom on my device manager after automatic driver update but my phone still isn't recognised in adb devices, does everyone else's serial number show up?
You guys still have the problem?
Sent from my Xiaomi Mi 5 using XDA Labs
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
Good that you found the solution..
Sent from my Xiaomi Mi 5 using XDA Labs
Well I didn't really solve the problem on win 10 so i just decided to use Ubuntu instead. Worked well
SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
I tried that too, but didn't work. What driver did you select in Device manager?
superiscch said:
I tried that too, but didn't work. What driver did you select in Device manager?
Click to expand...
Click to collapse
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
SgtIcetea said:
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
Click to expand...
Click to collapse
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good ?
superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Yeah that one. After disabling the driver signature verification you have to re install it, when it's not disabled windows just doesn't install it although it says it does. After I disabled it Windows actually showed a completely new window during installation to install the driver properly
superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Man, had to just do it through my Ubuntu VM. Tried Win 10 Win 7, all gave me troubles.
Started Ubuntu, setup ADB and unlocked in a breeze
i have same problem
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
download minimal ADB and Fastboot and turn on usb debugging from developer options. Also accept the popup on screen when you connect phone to PC after this
I have the same problem, have you succeeded ?
Thank you
I have the same issue with my Note 8T
i had the same problem with my note8. try to google around 1 hour. & that's the ones topic about it. unfortunately it has no answer poor me
johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
Try downloading the Xiaomi unlocking tool, I didn't have problems with drivers, but I saw a messages about downloading drivers and "Driver already installed" for my phone within the application log.
Give that a try!
But problem with Note 8. I don't remember when it started, but on crDroid 6 it definitely worked.
After that I notice in device manager what it determinate as some SAMSUNG Adb Device with Clock World driver. I had ADB Universal Driver installed, after uninstalled everything start work fine.
I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?
scarlos89 said:
I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?
Click to expand...
Click to collapse
Use W7
W10 always have problems with some driver signature
loopypalm said:
Use W7
W10 always have problems with some driver signature
Click to expand...
Click to collapse
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.
scarlos89 said:
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.
Click to expand...
Click to collapse
you have to wait
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.
windows 11 is still on its embryonic stage expect some bugs and compatibility issue, try reinstalling all drivers of your poco f3 but before that, you need to disable driver signature enforcement before reinstalling drivers search on google on how to disable this matter
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
i am currently running on win 10, nebrassy and vasishath twrp build no issue about fastboot, maybe you should try to downgrade your pc
Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
Phat Phreddy said:
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.
Click to expand...
Click to collapse
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
mlcattini said:
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
Click to expand...
Click to collapse
But I said its working on ADB..
RollDload said:
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
Click to expand...
Click to collapse
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
Phat Phreddy said:
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
Click to expand...
Click to collapse
you could try, however miflash doesn't need installation you just need to unzip it. you can also try to change USB port better if rear and 2.0
Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
Phat Phreddy said:
Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
Click to expand...
Click to collapse
then it was definitely a problem in the driver.