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?
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?
okay ... a new question and also soo weird....
I want that my 2 PC´s recognize my device when its in bootloader mode
1º pc recognizes it well and its running UBUNTU.
2ºmy sister´s PC RUNNING WIN7 doesn´t recognize my DHD into bootloader mode.. but if i look the screen of the device the device automatically was changed his status to "HBOOT USB PLUG" but here is the problem:
When windoze7 detects and recognizes my device It issues a sound, but when I connect my DHD it issues different other one, that is to say detects it but it does not recognize her, then the usb mode I cannot use it
but if i boot my dhd and put her in debugging mode and run adb parameters windoze recognizes the device perfectly...
i am not an experienced user in windows
and i don´t know whats the problem. its strange..
any advise?thx in advance
Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?
Mr_JMM said:
Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?
Click to expand...
Click to collapse
lololol we have a lot of problems Especially with windows i hate it
but she is afraid of not being able to handle it if I am not in house (SHE HAS ANOTHER DHD) in addition she likes the Microsoft OFFICE. LOL (and not open office)
Yes i had installed htc sync drivers, and sdk working well in usb debugging mode with the DHD turned on
Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?
Mr_JMM said:
Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?
Click to expand...
Click to collapse
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically
SERGI.3210 said:
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically
Click to expand...
Click to collapse
the problem appears into fastboot and into bootloader
ok in fastboot mode into sdk shell write fastboot devices and shows me a message:
"unable to initialize the aplication because ADBWINAPI.DLL not found
Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).
Mr_JMM said:
Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).
Click to expand...
Click to collapse
ok tried another socket but the PC says to me :LOL
good idea mate... if i create aN ubuntu root/live cd i can try with the konsole
windoze please... burn in the ****ing hell
edit:with ubuntu works well again
.........................................................................................
spike_14 said:
.........................................................................................
Click to expand...
Click to collapse
good apreciation to the forum mate... LOL
okay... in advance thank´s again to my friend Mr_JMM for help me again (pressing your thank´s button AGAIN lol)
i solved my problem with "winfuck"7 (windows for microsoft´s friends)
ok when i was tried to input a fastboot code the CMD (shell) of windows returned me:
"unable to initialize the program because ADBWINAPI.DLL does not exist...
well i browsed for this file and its a library file for adb.exe commands.
under my experience fastboot parameters shouldn´t be afeccted by the ausence of this file but when i was downloaded it (a zip file with adbwinapi.exe, adbwinusbapi.dll and adb.exe) and i have put it in the folder "tools" of the sdk (Rightly where it shelters fastboot.exe) VOILÀ!!!!
i tried to enter:
"fastboot devices"
and returned to my
"HT.........."
also i tried to rebbot the device from fastboot with
"fastboot reboot" and WORKS WELL!!!!
END OF THIS THREAD.... SOLVED!!!!!!!!!!
Hello, peoples. I recently got a Sony Smartwatch 3, and updated it to the latest software (5.1.1).
I figured, "Hey, since I'm probably gonna do a ton of stuff on this Android thingy that requires an unlocked bootloader, I should unlock my bootloader!"
Although my ADB works fine, once I type in "adb reboot bootloader", wait for it to get into fastboot, and type "fastboot drivers", it shows that no devices are connected. I am using the ADB and fastboot provided by Google's Android SDK tools. In device manager (I am using Windows 10, by the way), it shows my watch in "Unknown Devices", titled "tetra" with a question mark and an exclamation mark. Clearly, this is not supposed to happen. I have tried manually installing the drivers, but it states that the drivers do not support my device. So, in conclusion, can anyone help me?
Wow, I think I accidentally wrote a paragraph. Whoops. I'll try not to let it happen again.
Same here (but I have Windows 8.1)
Depending on mode (adb/fastboot) your PC sees different USB-IDs.
Try: http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
ranf said:
Depending on mode (adb/fastboot) your PC sees different USB-IDs.
Try: http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Click to expand...
Click to collapse
Okay, so, after trying to use this, it says that the hash check failed. Although, I was able to select the Google Inc. ADB driver anyway? I don't know how, but it's fixed. Thank you!
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.
I have searched the net high and low for a answer to this question but nothing I have tried works.
I have used every adb and fastboot installer i could find, but nothing i do get fastboot working on my 5t. ADB is recognised and i can reboot to the bootloader from a command shell. But as soon as i type "fastboot devices" it shows nothing.
I have been into device manager and it shows issues with the fastboot driver, i have tried everything i can think of to fix this issue.
I would really love to root my 5t and and have never encountered this many issues on any of my previous devices.
Running a 64gb OP5T and Windows 10
Thank you for your help
I have now re-installed windows 10, re-installed all drivers and ADB and fastboot. ADB is still working but nothing from fastboot. It's recognised properly in device manager but nothing shows up when I type fastboot devices or fastboot OEM unlock. Any tips would be great.
http://www.codeshuffle.in/2016/12/kenzo-fastboot-adb-connection-fix.html
check this link specially driver signature enforcement disable part, it may help
When you say "nothing shows up", what exactly is the response?
How are you getting into the bootloader? Use this from recovery or system:
Code:
adb reboot bootloader
Then proceed.
ADB is working fine. But as soon as I reboot to fastboot mode the phone doesn't respond. I can't work it out have tried everything.
djmcnz said:
When you say "nothing shows up", what exactly is the response?
Click to expand...
Click to collapse
^^
It just says waiting for device or says nothing and brings up a new line. I'm guessing the fastboot driver is the problem. I have installed the Oneplus drives included with the phone. I've installed the universal ones, still nothing.
Is there an individual fastboot driver I could manually install through device manager?
Appreciate the help.
The issue is finally fixed! I went into device manager and changed the driver from a list of drivers on my pc to WINUSB and now its working
Same problem here pal, how did you change driver to winusb, seems I've got all the gear just no idea... By gear I mean files/drivers lol. Rooted so many devices I thought this would be easy, looking forward to getting it sorted. I love a custom rom