I recently had my phone unlocked by Alejandrissimo so I can now get into fastboot. The only problem is that when in cmd after putting in a command a message pops up saying "waiting for device" even when my phone is in fastboot mode.
My bootloader is unlocked by the way.
Are your usb drivers set up ok? check installed devices in "device manager" if it shows an exclamation mark you need to install the relevant driver http://www.multiupload.com/BMJ24IL6XY
Hope that helps
Thank you for that. I've got it working now.
please upload driver again¿¿
garner said:
Are your usb drivers set up ok? check installed devices in "device manager" if it shows an exclamation mark you need to install the relevant driver http://www.multiupload.com/BMJ24IL6XY
Hope that helps
Click to expand...
Click to collapse
I checked on device manager like you said and there is no exclamation mark but it is still waiting for device. Also can you upload the link on another website because multiupload doesn't work.
Thanks
Related
Hi everyone
Since i updated firmware from .42 to .62 via flashtool, i've got a weird behaviour when i plug my phone in Flash mode.
It's recognized as S1 boot download with a yellow triangle thingy, i installed usb flash drivers, now it's with SEMC Flash Device as hardware, then after 30s-1min it reboots and turns to SEMC HSUSB Device, a mass storage entity.
Can you help me fix this so i can access fastboot?
I reverted back to .42 via wotan, erase all drivers with usbdeview, plug it back, nothing works. I surely did something wrong but i can't spot it.
Tried on another pc, same behavior. Something's missing/corrupt in the phone.
i have a similiar problem, i cant access fastboot, message waiting for device, in device manager i cant install the driver cause it tells me not found.
Any Idea?
I was having strange problems when trying to install the drivers on a windows 7 PC. i had to install GordansGate drivers but it still didnt work. I ended up installing PDAnet or something and it installed all the correct drivers for me and using the latest version of flashtool i can do everything from there (flashtool, fastboot, adb)
i tried so much, but it wont recognize the driver -.- dont know what to do, every time when i try it with device manager->S1BootFastboot->install driver it tells me that my drivers directory are not the right drivers -.-
install this and run through the setup carefully and follow each step. this fixed my driver (not recognizing device) problems on my desktop
http://junefabrics.com/android/download.php
hope this solves your problems because i was going mad with mine for ages
ok solved my problem by installing flashtool and the flashtool drivers. now everything works fine
Hey! I have the same problem on my Mini.
When connecting, Device manager says "S1boot ..." and the icon has yellow triangle, but then it changes to "SEMC Flash Device"
Fastboot gives "<waiting for device>"
What Flashtool version have you had when you installed it's drivers?
Did you add that .inf file from SE site?
Theonewithideas said:
Hey! I have the same problem on my Mini.
When connecting, Device manager says "S1boot ..." and the icon has yellow triangle, but then it changes to "SEMC Flash Device"
Fastboot gives "<waiting for device>"
What Flashtool version have you had when you installed it's drivers?
Did you add that .inf file from SE site?
Click to expand...
Click to collapse
i have the same problem
francois90 said:
i have the same problem
Click to expand...
Click to collapse
Try switching the USB cable and USB port
Theonewithideas said:
Try switching the USB cable and USB port
still nothing ... if u can give me more instructions i'd appreciate it , ty
Click to expand...
Click to collapse
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.
My HTC desire 820 keeps restarting itself as it is stuck in an endless boot loop. I have come across threads speaking of the same issue but the solutions don't seem to work on my phone.
My boot loader is locked. When i try to unlock it in fastboot mode, the device doesn't show up on the PC.
I need the boot loader unlocked so that i could push in a custom recovery mode as i cant get into the stock recovery too.
Does anybody have a solution for my kind of problem?
Also, when the phone is in fastboot usb mode, the computer makes a notification sound which indicates it recognizes the phone.
The only thing i can get into is my boot loader and which looks like this now:
***LOCKED***
A51_DTUL PVT SHIP S-ON
HBOOT-3.19.0.0000
OS-3.17.708.3
eMMC-boot 2048 mb
Apr 12 2016, 11:49:54.0
NOTE: I never tried to install a custom ROM. This problem arose on its own for reasons unknown to me. Moreover, my phone is UNROOTED.
PLEASE SOMEBODY HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE!
I'm clueless!
themember1993 said:
PLEASE SOMEBODY HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE!
I'm clueless!
Click to expand...
Click to collapse
Have you installed the adb/fastboot drivers on your PC?
Sounds like a drivers issue to me.
Try this thread to install the drivers then try communicating with the bootloader again.
https://forum.xda-developers.com/showthread.php?t=2588979
Gibz97 said:
Have you installed the adb/fastboot drivers on your PC?
Sounds like a drivers issue to me.
Try this thread to install the drivers then try communicating with the bootloader again.
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Thank you for replying, friend.
I did what you asked me to do i.e. installed adb/fastboot drivers and then ran the command to identify.
But all i get is this. I have attached a screenshot of the message i'm getting in the command prompt.
What do i do?
themember1993 said:
Thank you for replying, friend.
I did what you asked me to do i.e. installed adb/fastboot drivers and then ran the command to identify.
But all i get is this. I have attached a screenshot of the message i'm getting in the command prompt.
What do i do?
Click to expand...
Click to collapse
Still a drivers issue
Try installing HTC Sync Manager from here and try again.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
Gibz97 said:
Still a drivers issue
Try installing HTC Sync Manager from here and try again.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
Click to expand...
Click to collapse
I had installed the htc manager again as per your instructions even though i had it on my pc earlier.
HTC sync manager doesn't detect the phone.
Nor does fastboot command in the command prompt.
i have the adb drivers installed as you asked me to install them earlier.
I get the same message "waiting for phone" in cmd. I rebooted fastboot but even that doesn't change anything.
What do i do now? Is it a hardware issue? I do not think it could be a hardware issue because the phone has never undergone physical damage. it just decided to turn itself off one unfortunate day by itself.
Is there another way? another software?
themember1993 said:
I had installed the htc manager again as per your instructions even though i had it on my pc earlier.
HTC sync manager doesn't detect the phone.
Nor does fastboot command in the command prompt.
i have the adb drivers installed as you asked me to install them earlier.
I get the same message "waiting for phone" in cmd. I rebooted fastboot but even that doesn't change anything.
What do i do now? Is it a hardware issue? I do not think it could be a hardware issue because the phone has never undergone physical damage. it just decided to turn itself off one unfortunate day by itself.
Is there another way? another software?
Click to expand...
Click to collapse
Open device manager.
Connect phone to PC. Does the device manager show a new device added?
And BTW why can't you get into the stock recovery?
Gibz97 said:
Open device manager.
Connect phone to PC. Does the device manager show a new device added?
And BTW why can't you get into the stock recovery?
Click to expand...
Click to collapse
When i select "fastboot mode" in the bootloader screen, the PC makes a connection notification sound.
And the device shows up as "Android 1.0" in Device manager.
I have attached a screenshot which shows the same.
Also, when i try any of the options in the bootloader i.e., factory reset, recovery mode, reboot or power down, the device goes back to the endless bootloop and never really lets me do anything.
themember1993 said:
When i select "fastboot mode" in the bootloader screen, the PC makes a connection notification sound.
And the device shows up as "Android 1.0" in Device manager.
I have attached a screenshot which shows the same.
Also, when i try any of the options in the bootloader i.e., factory reset, recovery mode, reboot or power down, the device goes back to the endless bootloop and never really lets me do anything.
Click to expand...
Click to collapse
Try downloading usb deview from here. Uninstall all the USB drivers, reinstall them then try again
http://downloads.tomsguide.com/USBDeview,0301-13254.html
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?