When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects
Anyone?
no one?
bigd19888 said:
When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects
Click to expand...
Click to collapse
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have minimal adb and fastboot installed
device is h811 20v
bootloader is already unlocked
and yes I'm using LGMobileDriver_WHQL_Ver_4.2.0
sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp
After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.
RuedasLocas said:
After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.
Click to expand...
Click to collapse
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
Don't allow Windows 10 to update your drivers - you can set that up in Windows. Google it for the how-to.
bigd19888 said:
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp
Click to expand...
Click to collapse
bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck
RuedasLocas said:
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck
Click to expand...
Click to collapse
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Your device should be seen as "LGE Android Phone" (if your lg drivers are good).
Now gonna be tricky because my OS is in Portuguese, I don''t know exactly the path name in English... use your imagination
Connect the device on a USB 2 Port !!!
In windows device manager, select "update driver", "search software on the computer", "allow to choose from a list of avalable drivers". unmark the "compatible hardware" and find on the list the needed drivers. If the "LGE" drivers don't work, try to download Universal ADB Drivers, maybe it works.
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
I'm thinking it could be a corrupted LG driver. Download another from the LG US site, ONLY. Uninstall the one you have installed now, reboot and install the newly downloaded one. Then connect your phone and see if it is recognized and shown correctly in Windows Device Manager. Also, in adb type lsusb and see if the phone is listed in the output.
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Boss, no need to struggle with this ADB anymore.. there is a tool called FWUL which was created for people who have driver issues... Check it out here:
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
:good:
Related
Hi Guys,
Any help would be great! i do have google talk if anyone is willing to help me out!
My R800i Is rooted and has a version of recovery but not sure which version, i am wanting to update my phone with a better kernel and rom since the current one i have installed is giving me issues ( not being able to receive incoming calls for example )
Another problem is i reformatted the phone since i was having issues with receiving calls but now when i connect my phone to ANY computer via the USB cable the computer trys to install MTP or MSC driver ( depends on which connection type i select ) the Installer fails and i cant even take any files off my phone.
Provided details below. i want to somehow get into the current bootloader and install the ROM thats on my SD card! i do have flashtool installed and Android tool SDK installed but still no success in phone wanting to talk to my laptop.
I am running windows 7 64 bit. i am starting to think the phone is belond repair since i cant get any software to work between the phone and computer.
does anyone know what buttons i need to push on the Xperia Play to enter into the boot loader, i have tried pressing the back button and search button on phone boot but nothing happens apart from the phone starts up normally.
would a factory reset delete the boot loader and other config-ed software off the phone is this why i cant enter the boot loader or am i not pressing the right buttons on boot.
Any help would be really appreciated!
IMEI:
357302043579712
IMEI Software Verson
49
Available Speech Codecs
HR, FR, EFR, AMR_HR, AMR_FR
Working Bands
GSM850, GSM900, GSM1800, GSM1900, UMTS_BC1, UMTS_BC8
Rooting Status Bootloader Unlocked Allowed: Yes
Phone Software Version
1245-8821_4.0.1.A.0.283
S1 Boot Version
1241-3656 R9A021
EST Software Version
1242.5099_10
Android Version
2.3.4
Baseband Version
8x55A-AAABQMAZM-203028A-49
Kernel Version
2.6.32.9-perf
Build Number
4.0.1.A.0.283
If you want to change the kernel you must unlock your bootloader. If your Xperia Play is a SIM free one, you can do it for free in this link: http://unlockbootloader.sonymobile.com
For SIM locked devices I think you must find another ways to do it. There are some online sites that unlock bootloader to SIM locked devices for a fee.
Once you have unlocked your bootloader, turn off the phone, hold on the search button, plug the USB cable in the computer, release the search button (power button LED will be blue) and install this driver: http://drivers.softpedia.com/progDownload/Google-USB-Driver-Revision4-Download-139077.html
Now you are ready to flash any kernel you want with Flashtool or any other app.
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
PsychoShaft said:
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
Click to expand...
Click to collapse
I have tried what you said but having problems with connecting my phone to my Windows 7 Laptop!
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
jcarbox said:
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
Click to expand...
Click to collapse
Hi I tried what you said, i Turned off my phone and holded the search button and turned it back on, the light went blue and the computer popped up trying to install fast boot i point to the SDK folder to update the driver but it fails.
do you have google talk might be easier on there to talk! cheers!
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
jcarbox said:
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
Click to expand...
Click to collapse
Thanks for the download link, i going to try this in a bit and get back to you! thanks for the support guys! :good:
Just tried, i put my phone into Media Transfer Mode.. my computer tried to install the MTP usb device and i directed the installation to the driver you linked..
Update Driver Software says: the best driver software for your device is already installed MTP USB DEVICE, there is a small yellow triangle on the icon and in MTP USB Device Properties it says: This device cannot start. (Code 10)
i need someone to Teamviewer with me, for the record i don't have the Sony Ericsson software installed on my Computer because that still wont install the drivers for my phone, i also know its not needed for installing new kernel and roms.
i tried connecting this phone to a bunch of pcs including my friends and it still fails to install any drivers!!! i think i am just going to bin this phone! i have had enough (
You must install that driver when you plug the phone in fastboot mode. It shouldn't work in any other case. In other words, when you plug your Xperia Play being powered on and Android is running it needs one driver, and when you boot it in fastboot mode you need other driver.
Please, install the driver following the steps previously posted with your phone in fastboot mode (blue LED).
Hello, i put my phone into fastboot mode, my device manager shows 1 device not installed S1Boot Fastboot, i right click go to properties and click update driver...
then i browse my computer for driver software i point the location to usb_driver_rev4\usb_driver and it says: Windows was unable to install your s1Boot fastboot!
Ok, let's see...
Try to update the driver using the "choose from a list" option to force the installation, point to the driver folder and select "Android ADB Interface" from the list. If Windows shows a warning message don't worry about it and go ahead.
i tryed this and its not wanting to work (
Sorry to hear that because I don't have any more ideas for your problem.
Maybe you may spend some minutes searching in the forum to find some detail that can help you.
i need someone with teamviewer to help me go though the setup process again, if anyone is willing to get my phone working i will happy pay them some money!
Thanks Jcarbox for all your support!
Regards
Paul
I just check the Windows device manager with my phone plugged in bootloader mode and it appears as Android Bootloader Interface, so this is the device you must choose from the list when you install the driver.
Hope this helps you.
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
This may work
PsychoShaft said:
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
Click to expand...
Click to collapse
hi PsychoShaft,
I had similar problems. I don't know how to fix it permanently. but i do this to make it work for some time.First, download flashtool and install it.Open your device manager and select view->show hidden drivers.Then, delete all your drivers related to xperia play. like the adb interface, semc flash ,etc. All of them in all categories. then reboot your computer into safe mode with administrator and connect your device with flashtool running in your windows in safe mode. then the flashtool will indicate that you don't have the drivers. then,open the drivers folder in flashtool and use the setup to install arc-play-...,flashmode drivers and fastboot mode drivers.then after the installation is over windows will ask you to reboot.now reboot with your mobile connected. after boot windows will automatically install the drivers. then unplug your phone and turn off it and connect in flash/fastboot mode.it will automatically install drivers.wait for windows to say drivers installed successfully or installation failed. don't unplug it in the middle of the process then you will have to start from first.sometimes it will not work in the first time ,then reboot into safe mode and try again installing the drivers and rebooting into safe mode itself and connecting your device.at one point of time flashtool will say your device is connected in flas/fastboot mode.then continue with flashing
Gladwin.
Thanks for the support guys i managed to solve the issue!
^^^^ Glad i could help
Sent from my GT-I9300
Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.
That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..
Turned off device signing. No effect.
Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.
in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
have you tried un-installing HTC SYNC?
SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.
TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app
ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"
SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img
Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4
SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu
Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.
I have an HTC One M8, bought from UAE. I rooted it and it all went well. Now I want to get OTA updates on the phone and I want to unroot for the moment. The problem is that I connect my phone to my laptop run adb but it doesnt do anything. All it says is list of devices attached and thats it. Nothing else at all. I cant give my phone commands or anything of the sort. I want to update my phone to the latest android version with sense 7 and I would prefer that I have a stock rom hence the OTA but without getting my phone recognised with ADB I dont know how to do it. Please help!
P.s. I am running windows 7 and my CID is HTC__J15
I got the CID from an app from the app store, dont know if its legit but I the gulf region uses this CID so I guess its safe to assume its correct.
P.s.s. Yes I have tried reinstalling HTC drivers and it hasnt done anything. The device manager doesnt have any unknown device listed either. Yes USB Debugging is also on and I get the notification on the phone as well but my computer doesnt recognise it.
P.s.s.s. Is there anyway to get the latest OTA without hooking my phone up to the computer? I'm not a tech guy so I need help. A step by step would be very nice. Thanks
Boot into bootloader and perform the "fastboot getvar all" command. Post the output here without IMEI and serial no. as the software number is needed to provide further instructions and identify the correct RUU and/or backup you'd need.
Send by the swarm intelligence of my coffee machine ?.
flamingpenguin said:
The device manager doesnt have any unknown device listed either.
Click to expand...
Click to collapse
Meaning the device doesn't show up at all in Device Manager (HTC, Android phone, etc.)?
If you boot the phone into bootloader-fastboot mode, any response to fastboot commands (fastboot devices, etc.). Sometimes fastboot works, when adb doesn't. And fastboot is the really critical one you want.
HTCNerdYoda said:
Boot into bootloader and perform the "fastboot getvar all" command. Post the output here without IMEI and serial no. as the software number is needed to provide further instructions and identify the correct RUU and/or backup you'd need .
Click to expand...
Click to collapse
I tried booting into fastboot mode and then hooking it up with the computer. I enter the fastboot getvar all command and all I get is < waiting for device > it just stops there for as long as I wait and it doesnt do anything. Please help!!! I've tried different cables as well. Also a different laptop. I'm not sure whats wrong. The sync manager doesnt work either. Doesnt detect my phone :crying:
redpoint73 said:
Meaning the device doesn't show up at all in Device Manager (HTC, Android phone, etc.)?
If you boot the phone into bootloader-fastboot mode, any response to fastboot commands (fastboot devices, etc.). Sometimes fastboot works, when adb doesn't. And fastboot is the really critical one you want.
Click to expand...
Click to collapse
Media Transfer Protocol works. I just get a new drive with my phones internal and external storage. I can transfer files but thats the only response my computer gives to the phone. Help please :crying:
flamingpenguin said:
Media Transfer Protocol works. I just get a new drive with my phones internal and external storage. I can transfer files but thats the only response my computer gives to the phone. Help please :crying:
Click to expand...
Click to collapse
Did you activate the developer options and if so USB debugging as well. Did you try installing Sync Manager to install the needed HTC drivers, uninstall it (as it interferes with adb/fastboot sometimes) to just keep the drivers? Which adb/fastboot are you using?
Send by the swarm intelligence of my coffee machine ?.
flamingpenguin said:
Media Transfer Protocol works. I just get a new drive with my phones internal and external storage. I can transfer files but thats the only response my computer gives to the phone. Help please :crying:
Click to expand...
Click to collapse
Try this: Go into Windows Device Manager, find the device, pick the option to manually select the drivers. Then pick the generic Android MTP device drivers (or some such name like that). I often have to do this to get my home computer to pickup my phone via adb/fastboot, while MTP works just fine.
HTCNerdYoda said:
Did you activate the developer options and if so USB debugging as well. Did you try installing Sync Manager to install the needed HTC drivers, uninstall it (as it interferes with adb/fastboot sometimes) to just keep the drivers?
Click to expand...
Click to collapse
I have both developer options and USB debugging on. I also tried drivers that came with the phone via the sync manager. Tried after getting rid of the sync manager but it still doesnt work. I can get my software number from setting>about etc no? My CID and Software number is all I need to unroot the phone and install the stock recovery, if I'm not mistaken? I am completely dumb at this tech thing. I'm a civil engineer. I understand concrete and rebar
redpoint73 said:
Try this: Go into Windows Device Manager, find the device, pick the option to manually select the drivers. Then pick the generic Android MTP device drivers (or some such name like that). I often have to do this to get my home computer to pickup my phone via adb/fastboot, while MTP works just fine.
Click to expand...
Click to collapse
I cant find my device in the Device Manager at all =/
flamingpenguin said:
I cant find my device in the Device Manager at all =/
Click to expand...
Click to collapse
I'd suggest downloading the drivers again and first of all try with another USB data cable. If it doesn't show up at all, it sounds as if you got a connection problem. So could also be caused by a defective cable and/or USB port on your phone.
I'd check the following:
1) try connection to another USB port
2) try with another data cable
3) download latest HTC drivers from HTC.
Send by the swarm intelligence of my coffee machine ?.
I had this happen to me and to resolve it I went into the C: drive of my computer and in the program files folder I located the HTC folder. Once there I looked for the apk files that allow you phone to connect to HTC sync. If I remember correctly, I copied apk file #2 to my phone and installed it. Once it was install that issue went away. To be on the safe side, copy and install each apk file one at a time(there should be 5 of them) to your phone. Only one of them will install the others will not. This will help you to locate and install the correct apk file. Once you have found and installed the correct one, you can removed the other apk files that wouldn't install and reboot your phone. After that connect your phone to your computer, and htc sync and adb should recognize your device. There is a thread on this but I can not remember where to locate it.
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
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?