I have latest Motorola drivers and Android SDK installed, so my PC itself should be up to date. However, whenever I select "install zip from sideload" my device is not recognized. It shows up as XT925 in my Device Manager with a yellow exclamation point. None of the ADB commands work because it says no device is found, and "adb devices" gives me a blank list. I have tried disabling, re-enabling, and uninstalling drivers (Of the "XT925" device in Device Manager) and rebooting into CWM and selecting the sideload option again, but when my PC is trying to download/install the XT925 drivers, it never finds proper drivers and I'm back to where I was. Trying to find drivers through the Device Manager leaves me with no results. Anything I can do to get my device recognized? When powered on or in fastboot mode, I have no issues executing any command or with device recognition. Thanks in advance!
By the way, the issue has persisted through Stock ROM flash in RSD Lite, HoloBlur-X PurePerformance ROM, and Carbon ROM v1.8
I have the same issue as well. I dont think we have a fix. I have heard universal adb driver might fix it, you might want to try it and see. It didnt work for me though.
Ahh, I see, so its a known issue. I guess I'll try those universal ADB drivers, not expecting anything though... Thanks
Edit: Wow! I installed the universal ADB drivers a few minutes ago and ADB is totally useable in CWM sideload mode! I can sideload files, send commands to reboot, etc etc. I dropped a thanks to you ai6908, thank you very much
I grabbed and installed them from here: http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/
Being able to sideload ROMs is going to save me a lot of headaches later on...
Neighbor808 said:
Ahh, I see, so its a known issue. I guess I'll try those universal ADB drivers, not expecting anything though... Thanks
Edit: Wow! I installed the universal ADB drivers a few minutes ago and ADB is totally useable in CWM sideload mode! I can sideload files, send commands to reboot, etc etc. I dropped a thanks to you ai6908, thank you very much
I grabbed and installed them from here: http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/
Being able to sideload ROMs is going to save me a lot of headaches later on...
Click to expand...
Click to collapse
You can also update to unofficial cwm 6.0.3.2. I find it faster and everything works
Sent from my PACman Atrix HD
I updated to 6.0.3.2 a few minutes ago, everything is going smooth, thanks guys
Related
USB/MicroSD mount is working, but I cannot get ADB to work. This is really pissing me off. I had it working fine on Vista but I'm a dumbass and decided to upgrade to Win7 Ultimate.
Device Manager does not show "Android Composite ADB Interface" or "Nexus One" or anything that looks remotely like that.
The instructions here: http://forum.xda-developers.com/showthread.php?t=613054 -- do not work for me, as you can see in the screenshot I've provided below, nothing shows up.
SCREENSHOT (same also attached in case something happens to the link): http://imgur.com/uoaWH.jpg
1. The Android SDK is installed.
2. Java JDK 64 & 32 bit versions are both installed.
3. Plugged in my phone, turned on USB Debugging, nothing happened. Device manager list didn't change at all. No alerts near the systray from Win7.
4. I used "USB Deview" and uninstalled everything that looked like "Google" or "HTC" (saw nothing that said HTC or Android, just Google).
5. After #4, gave this POS a reboot, no change when plugging the phone in.
I have the driver downloaded, separately, as well as the one that comes with the Android SDK.
I'm at a complete loss.
Help is deeply, truly, appreciated, and I'll be clicking on some "DONATE" links if you can help me fix this.
EDIT: RESOLVED
Windows7 didn't like this ROM: http://forum.xda-developers.com/showthread.php?t=702191
But it loves this one: http://forum.xda-developers.com/showthread.php?t=714184
Needless to say... I'm pretty happy!
usb driver installed?
rori~ said:
usb driver installed?
Click to expand...
Click to collapse
Yes.
And USB debugging is enabled.
I can mount the SD, but it looks like Windows thinks my phone is nothing more than a storage device. The ADB crap is not showing up in the Device Manager like it did on Vista, nor is there *anything* that says "Nexus One" except in... see new screenshot.
http://imgur.com/J7OzA.jpg
Is your Nexus running 2.2?
I had this exact problem as soon as I updated to 2.2; Windows 7 simply refuses to accept the device.
Put your device in recovery mode and see if fastboot can detect it. For me it can, but ADB and DDMS both think nothing is connected when the phone is on and in debug mode.
I have a HTC Magic as well which works absolutely fine (even when running CM6, which is 2.2 based) but the Nexus on 2.2 is just a no go. If you've unlocked your bootloader you could downgrade to 2.1 again. I never had problems on Win7 with 2.1.
Your only other option is to add your comments to the bug, here: code.google.com/p/android/issues/detail?id=9437 (sorry, I'm still not allowed to post proper links yet)
It seems very few people are experiencing this (or reporting it when they do) so my hopes for them fixing it are pretty low.
Are you on version R3 of the USB driver?
What happens when you plug in the phone with usb debugging turned on (on the status bar) ?
Does it ask for a driver? if so manually point it to C:\android-sdk-windows\usb_driver (may differ)
below is a SS of the driver files being uses on my win-7 64 bit desktop.
Try something for me. I am having the same as you but try this. Boot your phone in recovery mode and see if adb works then. My pc sees the phone as adb in recovery but it doesn't see it as adb on the home screen. Not sure why this is but it worked at one time.
Prod1702 said:
Try something for me. I am having the same as you but try this. Boot your phone in recovery mode and see if adb works then. My pc sees the phone as adb in recovery but it doesn't see it as adb on the home screen. Not sure why this is but it worked at one time.
Click to expand...
Click to collapse
Holy ****.
I love you.
I've been pulling my hair out. Seriously.
I booted into recovery, plugged the phone in, Windows tried installing drivers, but failed, then I saw "Nexus One" listed in Device Manager, and after installing the drivers that came with the SDK, the "Android Phone" and "Android Composite ADB Interface" stuff shows up in the device manager, and adb commands work... when my phone is booted into Recovery.
Recovery was the key.
Thank you!!!!!!
Could the ROM I'm using have anything to do with this?
ADB recognizes the device when I'm recovery, and the "adb push" commands do their thing, but I don't see the files being pushed where I'm pushing them to.
Do I just have to enable the "USB toggle" thing?
I just installed Win 7 and used these directions from the android developers website and everything worked flawlessly from the getgo:
http:// developer.android.com/sdk/index.html/
Hmmm, correct url, not working, 404, maybe it'll work if you copy/paste and take the spaces out from between // and developer.
What recovery image are you using? I've had good luck with ClockworkMod and it's 'mount system' option as far as push/pull while in recovery.
IT WAS THE ROM.
I went back to the ROM I was using previously, and ADB WORKS FINE NOW IN WINDOWS 7.
I was using this ROM: http://forum.xda-developers.com/showthread.php?t=702191
adb remount
adb devices
Nothing worked!
Completely wiped and, went back to this: http://forum.xda-developers.com/showthread.php?t=714184
It works now!!!
Something had to be wrong....that's stable rom. There's more than one custom rom that has it for a base.
pendo said:
Something had to be wrong....that's stable rom. There's more than one custom rom that has it for a base.
Click to expand...
Click to collapse
I'm not knocking the ROM or the developer of the ROM, but I made a backup, wiped everything, flashed the MCR ROM again, went back to the same problem.
Putting the other ROM back... no more problem. ADB commands work fine, and Windows7 sees my phone.
Ryjabo said:
I'm not knocking the ROM or the developer of the ROM, but I made a backup, wiped everything, flashed the MCR ROM again, went back to the same problem.
Putting the other ROM back... no more problem. ADB commands work fine, and Windows7 sees my phone.
Click to expand...
Click to collapse
And I don't doubt what you're saying...I was just thinking it was strange.....but hey strange things do happen so who knows, lol.
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes fastboot usb is shown and all fastboot commands work, its just that adb doesnt work when its in bootloader or recovery.
I did some more digging around and found that when the phone is connected while in recovery, the computer recognizes it as a "HTC MTP device"..and thats it. I cant upgrade the drivers of the said device or essentially do anything with it.
What am i missing?
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would start with these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
TygerByte said:
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would startpage these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Bhavpreet said:
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Click to expand...
Click to collapse
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
EddyOS said:
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
Click to expand...
Click to collapse
installed the 3 series driver, still the same problem. Heres some photos (which i should have attached originally) of whats happening.
The pictures are while the phone is normally booted, and then when the phone is in recovery.
Edit: Uninstalled all of the HTC drivers and devices inside the device manager, and only installed the Universal Naked Driver, the phone now shows up with a different name in device manager, but STILL does not work while in recovery.
Another pictures attached of how device manager looks with just the Universal Driver while in recovery.
anyone?
i have the same problem as u.. I tried both my missus Windowss PC now.. It used to detect it before. Now it suddenly doesn´t anymore. On my mac, same deal. Nothing detected.
Been googling around and i have found threads but they all end unsolved. ADB returns ADB devices blank. Kill-server or adb remount does nothing. in Fastboot USB its totally a ghost.
found any fixes?
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Me too...
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
bretula said:
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
Click to expand...
Click to collapse
In case this helps someone else: The reason I lost adb was that I'd installed the drivers on my mac for EasyTether. There's a note about this on the EasyTether FAQ page. When I disabled the EasyTether driver, I was able to use adb again.
TygerByte said:
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Click to expand...
Click to collapse
have you tied all-in-one-tool-kit ???
Not sure if this will help, but I had an issue like this with my asus tab - adb worked fine in android os but not in twrp recovery, device manager showing it as other device.
While in recovery with device connected to pc I followed this how-to from the device manager part on and got adb working in recovery.
ADB not connecting
Bhavpreet said:
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Click to expand...
Click to collapse
Re Install HTC drivers manually, windows sees HTC until you boot into recovery mode and try to use ADB, It worked for me.
HTC One(M7) not recognized by adb
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
TonyDEV said:
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
Click to expand...
Click to collapse
Take a look at this FAQ post and see if this doesn't help solve your problems. I would also recommend updating your CWM recovery to the latest.
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb... I can't install the naked drivers it just says that the file is incompatible
blu422 said:
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb...
Click to expand...
Click to collapse
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
thanks! did what you said i installed the drivers and the installation crashed the first time, then the second time it game me the option to remove or repair and i repaired and it worked thank you!!!
---------- Post added at 02:55 PM ---------- Previous post was at 02:37 PM ----------
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
so i have adb... but now it wont let me flash cyanogenmod... error executing updater binary in zip.... just fails.... help? updated to twrp 2.7.1.1. that fixed the problem
Hope this is in the right place.
I formatted my HTC1 like an idiot when I meant to wipe and am a little stuck.
ADB doesn't register on my PC so I can't sideload.
No installed ROM so I can't get into the system.
RUU flashes fail with a (remote: 24 parsing android-info fail)
Rooted, S-On and I have custom recovery images... TWRP and CWM...
I've tried everything I can think of and everything google can think of...
Any help at all would be greatly appreciated.
Thanks in advance
If you know someone with an OTG cable you can load it off a thumbdrive
Sent from my Nexus 10 using Tapatalk 4
Check this out:
http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload
You should be able to ADB Push a Rom to your phone, then ADB Sideload it. May need to reflash recovery first, I recommend TWRP
altimax98 said:
If you know someone with an OTG cable you can load it off a thumbdrive
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Figured this was my only remaining option and have ordered an OTG cable, arrives on Monday was just hoping to find another way so I didn't have to wait.
dgtiii said:
Check this out:
http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload
You should be able to ADB Push a Rom to your phone, then ADB Sideload it. May need to reflash recovery first, I recommend TWRP
Click to expand...
Click to collapse
I've tried this and many variants of ADB just isn't recognised on my PC
Thankyou both for your replies they are greatly appreciated!
Rechi03 said:
Figured this was my only remaining option and have ordered an OTG cable, arrives on Monday was just hoping to find another way so I didn't have to wait.
I've tried this and many variants of ADB just isn't recognised on my PC
Thankyou both for your replies they are greatly appreciated!
Click to expand...
Click to collapse
The only thing I can think of then is to find an RUU for your phone hopefully. ADB Push/Sideload normally works in your situation. Try a different cable, different USB port, different computer
dgtiii said:
Check this out:
http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload
You should be able to ADB Push a Rom to your phone, then ADB Sideload it. May need to reflash recovery first, I recommend TWRP
Click to expand...
Click to collapse
This guide saved my a$$ too, when I accidentally deleted my system folder. Try a different PC, it works all the time, it will work for you too.
And oh, OTG didn't work for me. I suggest you try a different machine.
humbug got my OTG cable this morning and it appears to work fine... installed Revolution HD 20.1.. tells me install compete and reboots and then brings me to the same blank screen I've been staring at for the last couple of days.
I'm obviously missing something but...
Rechi03 said:
humbug got my OTG cable this morning and it appears to work fine... installed Revolution HD 20.1.. tells me install compete and reboots and then brings me to the same blank screen I've been staring at for the last couple of days.
I'm obviously missing something but...
Click to expand...
Click to collapse
do you have a windows computer?
you most likely just need to install some drivers and then ADB will work.
https://dl.dropboxusercontent.com/u/74163067/HTC ONE DRIVERS.zip
those are the windows drivers. unzip the folder. open device manager. see here http://i.imgur.com/9LeGRJI.png
right click the "htc one" > "update driver software" > "browse my computer" then select the folder where you extracted the zip to. it will automatically install the correct driver. do the same for "my HTC" or any other devices that appear in those two top-level menus.
Have been through multiple drivers, some of which apparently work but still cant find the device when i try to push or sideload.
Have just done a full wipe and am going to attempt starting again from scratch with TWRP and Revolution HD.
Just to clarify I have tried multiple ports and cables, even bought a new USB 3 card, I don't have access to another PC or Laptop.
Rechi03 said:
Have been through multiple drivers, some of which apparently work but still cant find the device when i try to push or sideload.
Have just done a full wipe and am going to attempt starting again from scratch with TWRP and Revolution HD.
Just to clarify I have tried multiple ports and cables, even bought a new USB 3 card, I don't have access to another PC or Laptop.
Click to expand...
Click to collapse
Adb doesn't like usb 3, apparently.. Are you sure you're opening the cmd window from inside the adb/fastboot folder?
Sent from my HTC One using XDA Premium 4 mobile app
sideload is working as I type... it seems flashing recovery as aposed(SP?) to just booting a recovery makes a world of difference, will let you know if the install works. usb3 doesn't seem to be an issue though.
Hussah! It works! Thankyou all for you suggestions and input it has been greatly appreciated!
To flash with adb you need to boot ur phone in recovery mode, not in the bootloader... Took me a while to understand that
Ok, so, I made a bonehead move and flashed a rom that wasn't for the sprint htc one.
was able to get recovery back on the phone by using the command line.
I installed the android sdk and put google usb on there, reinstalled htc sync for those drivers too, still my pc doesnt see the phone, but my phone does show fastboot usb, and I can fastboot reboot the phone. When I goto adb push the zip file, it says error: device not found -- same thing if i try to sideload.
I have the rom, I just cant get it on the phone
fastboot commands work...is there a way to push a file using that (like I did with the twrp file)?
or another way?
thanks!!
DrRJE said:
Ok, so, I made a bonehead move and flashed a rom that wasn't for the sprint htc one.
was able to get recovery back on the phone by using the command line.
I installed the android sdk and put google usb on there, reinstalled htc sync for those drivers too, still my pc doesnt see the phone, but my phone does show fastboot usb, and I can fastboot reboot the phone. When I goto adb push the zip file, it says error: device not found -- same thing if i try to sideload.
I have the rom, I just cant get it on the phone
fastboot commands work...is there a way to push a file using that (like I did with the twrp file)?
or another way?
thanks!!
Click to expand...
Click to collapse
you can't use fastboot to push the file.
how about an OTG cable?
i'll order one just in case -- kinda hoping to get this thing up and running today though. Anything else I should try?
thanks!
DrRJE said:
i'll order one just in case -- kinda hoping to get this thing up and running today though. Anything else I should try?
thanks!
Click to expand...
Click to collapse
If fastboot is working, then so should adb in recovery. Can't really understand why it's not, are you sure you have the correct recovery? maybe check the Sprint forum: http://forum.xda-developers.com/sprint-htc-one
nkk71 said:
If fastboot is working, then so should adb in recovery. Can't really understand why it's not, are you sure you have the correct recovery? maybe check the Sprint forum: http://forum.xda-developers.com/sprint-htc-one
Click to expand...
Click to collapse
I have twrp 2.6.3.0 touch recovery, which appears to be the right one. Its like the phone recognizes that it's connected, but the pc doesnt (tried my mac too)...except that when I go into command line, fastboot commands work fine -- so the pc must see it...and when I plug the phone in, htc sync launches, but then says no device is connected -- so it recognizes the phone enough to launch, but then nada.
i've uninstalled drivers and reinstalled them and they install fine. this sucks
DrRJE said:
I have twrp 2.6.3.0 touch recovery, which appears to be the right one. Its like the phone recognizes that it's connected, but the pc doesnt (tried my mac too)...except that when I go into command line, fastboot commands work fine -- so the pc must see it...and when I plug the phone in, htc sync launches, but then says no device is connected -- so it recognizes the phone enough to launch, but then nada.
i've uninstalled drivers and reinstalled them and they install fine. this sucks
Click to expand...
Click to collapse
do you actually use sync manager? i recommend uninstalling HTC Sync Manager, just keep HTC Drivers.
as far as i know, there are GSM and Sprint variants of TWRP, so you have the Sprint one right?
and remember, fastboot will only work in bootloader/FASTBOOT USB, and adb will only work in a ROM or RECOVERY, it will not work in bootloader.
i reflashed recovery with one that is for sure for sprint...now adb pushing the file...i think its working.
will report back when i know for sure
DrRJE said:
i reflashed recovery with one that is for sure for sprint...now adb pushing the file...i think its working.
will report back when i know for sure
Click to expand...
Click to collapse
Make sure it's SPRINT compatible!!
Hit the thanks button if I helped
DrRJE said:
i reflashed recovery with one that is for sure for sprint...now adb pushing the file...i think its working.
will report back when i know for sure
Click to expand...
Click to collapse
thanks so much. adb push worked -- and have an OTG cable (which i didnt know about) on the way
DrRJE said:
thanks so much. adb push worked -- and have an OTG cable (which i didnt know about) on the way
Click to expand...
Click to collapse
No problem :good:
Would appreciate it if you hit the thanks button though
and also edit the main thread title to include [SOLVED] for others to know
Hi
I can't seem to get mt HTC One recognized with sideload because of drivers.
I have uninstalled HTC Sync Manager, installed universal drivers but can't get it to recognize the device.
The only drivers that install are HTC MTP Device, USB Composite device, USB Mass storage device and HTC Android Phone USB Device (Under CD/DVD Drives)
I'm using TWRP (and it's stuck there) and have been at this for 4 hours (searching etc..) now but no luck.
Really need help now.
Thanks
Edit: never mind sorted it.
Flashed CWM and adb sideloaded it, worked a treat.
Might be your version of TWRP cause I myself never got it working on CWM but since TWRP 2.6.3.3, sideloading all day long!
nodiaque said:
Might be your version of TWRP cause I myself never got it working on CWM but since TWRP 2.6.3.3, sideloading all day long!
Click to expand...
Click to collapse
With TWRP my computer just wouldn't recognize the device but with CWM it recognized it straight away.
tbh I have no idea what was wrong just glad I got it sorted.
Maybe I did something wrong with TWRP, no idea.