Related
Ok here it goes...
Ive come to the conclusion by having no luck with my previous thread which was asking how to fix " the usb is not recognized" after trying everything known to man and reading every thread that this is kind of a grey area. If your problem isnt obvious ie: debugging off or new usb cord etc... then ur sol ? I say this because the people who know their stuff are extremely detailed and make insanely great write-ups.
FTW can anyone explain or knows how to do this:
Fix the phone so that I can have full usb function ie: when i plug it in the comp wants to install drivers and the phone gives me the option to mount?
If not can someone tell me what choices I have???
To give some info my phone started this after (dont judge why i did this like this lol) installed freshhh 2.0b then the new radio then the new....heroc recov(from reading all day and night im guessing its the recovery)
also the phone will boot in heroc recov and will boot in fastboot but NO ADB sigh. and to take the cake me being frusturated seemed to break the cardinal rule no nandroid backup sigh sigh. basically i just want the usb back in action and fresh 2.0 w/radio. im sorry about the long post but im losin my mind over this. Thanks in advance guys as always every bit counts.
Go into your android dev kit and make sure you have the most current version of the ADB drivers. Are they updated? If so, make sure those are the ones you are using.
I've had similar issues before and I know it's wicked frustrating. Just keep toying with it... sure you'll get it eventually.
illogic6 said:
Go into your android dev kit and make sure you have the most current version of the ADB drivers. Are they updated? If so, make sure those are the ones you are using.
I've had similar issues before and I know it's wicked frustrating. Just keep toying with it... sure you'll get it eventually.
Click to expand...
Click to collapse
this happened to me with my brother's moment. I can't remember if usb debugging had to be on or off but it that is what I messed with to get it to work. Try throttling it on and off... Good luck
illogic6 said:
Go into your android dev kit and make sure you have the most current version of the ADB drivers. Are they updated? If so, make sure those are the ones you are using.
I've had similar issues before and I know it's wicked frustrating. Just keep toying with it... sure you'll get it eventually.
Click to expand...
Click to collapse
I have every one you can think of lol its frusturating because im a computer programmer and this to me is madness ive actually began learning alot about this language because of this trying to fine the bug im so close to just starting from scratch/stock but being stubborn i cant give in thanks for the advice bro!
have you tried it on another computer to see if it works?
chavo2005 said:
have you tried it on another computer to see if it works?
Click to expand...
Click to collapse
yes i have and no it doesnt...
Re-install HTC Sync.. It updates the drivers...
there's some driver incompatibility if you've ever used another device with adb... you have to find the original device, put in dev mode, and overwrite drivers with that of the hero, then plug hero in and try agian.... if that is in fact your problem....
otherwise, htc sync should fix ya
pjung1 said:
because im a computer programmer
Click to expand...
Click to collapse
what do you do?
PDAnet for android has some driverS you could try as well...
http://www.junefabrics.com
Yes PDAnet but I also had success with installing HTC Sync for the Eris.
I am using Win7 64bit.
http://www.htc.com/us/support/droid-eris-verizon/downloads/
As per crunchybutternut's suggestion in a different thread, I followed the instructions in this link: hxxp://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ (sorry, I can't post links yet)
Basically, I downloaded USBDeview and ran it in administrator mode to delete all HTC and Android related drivers (while phone is plugged in).
I then unplugged and plugged the phone back in and it reinstalled everything fine except for the ADB driver, so I told it to let me manually choose a driver from a list, selected Have Disk and pointed it to C:\android-sdk-windows\usb_driver
After that, I just set the phone to HTC Sync mode when plugging it in and it worked fine.
regaw_leinad said:
what do you do?
Click to expand...
Click to collapse
right now im doing alot of sql for companies who want full dbms. But pretty much know a little bit of it all. this is really fun to play with just a lil rough around the edges. i always liked linux tho!
And back to the problem i like the eris suggestion and I did all the rest. My only thought is this why after heroc attempt***???what does heroc do at the core behind being a boot prog what could it mess up or change if not flashed correctly? Thanks guys for the love
First, make sure your phone is NOT connected and open a command prompt. Then type the following command:
set devmgr_show_nonpresent_devices=1
You won't get any sort of output, it just goes to the next line. Then type in devmgmt.msc to open the device manager. Got to VIEW and select "Show Hidden Devices".
Now, expand the ADB Interface section, right click on each device individually, and uninstall. When prompted to delete the driver choose YES!
Go to the HTC Website to download and install the newest version of HTCsync.
http://www.htc.com/uk/SupportDownload.aspx?p_id=283&cat=3&dl_id=852
Once installed it would probably be a good idea to reboot your computer before you connect your HTC Hero. Once the Hero is connected make sure you pull down your notification bar and select HTC Sync or it won't connect for ADB access.
Hope this helps!
I've had this problem before but it was usually after I rooted my hero and had messed around. I've bricked two of them with the RUU trying to fix it. Don't really know why the phones bricked still. Usually I just kept plugging the phone on over and over until it recognized it.
I have 2 Nexus One's. The first was rooted and I had the ADB USB driver (v3) installed on my Windows XP Pro SP3 desktop and all worked fine.
I now have a second Nexus One. I rooted it, and after turning on "USB debugging" and wanting to use it with ADB, the driver USB installed again. But now I get constant "Found New Hardware Wizard" install loops, for both phones with "USB debugging" turned on.
Every time I plug either phone in, or reboot, Windows wants to reinstall the ADB driver. Right after it completes a driver install it wants to do it again.
Solutions I've tried; I have rebooted after install, uninstalled the drivers from Device Manager, deleted the drivers manually from the registry, removed any possibly associated hidden drivers that were marked error in Device Manager, and combinations of the above in various order.
I know that USB driver install loops on Windows can happen to any type of device, not just the Nexus, but in my case it's only on the ADB driver for Nexus One.
Can anyone suggest what I can do other than what I listed to stop the ADB driver endless install loop, or what is causing it?
Thank you.
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
No, I haven't found a solution to this yet. And you are the only person here that has replied.
I did contact Google and HTC and asked for their help. But since the phone is rooted I got the expected replies from both, that rooting violates warranty so they refused to help. I was expecting that, but have heard that the occasional tech support person at Google will still offer support within reason. But not in my case.
If and when I figure this out, I'll post it here to help you out.
johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
Hi JohnG75,
Just wanted to let you know my constant ADB driver reinstalls have stopped. But unfortunately I have nothing constructive to point out as a solution. I spent hours online researching for a possible solution, and found nothing worthwhile yet. I've posted in several places and got no helpful replies other than trying System Restore and going back to a point before this happened. Of course that's hardly a guaranteed fix, plus you loose any other updates and installs you have made since then.
In my case, I left "USB debugging" turned off on my phone since I wrote you last, and the only thing that has changed system wise for me, is I have installed 2 unrelated device drivers since, and MS has pushed out a security update. So today when I turned "USB debugging" back on in the phone, it did a single device install, and it didn't repeat. So hopefully this resolves it for me.
If I were to take a guess as to what appears to have solved it in my case, I would say it was the new unrelated device driver installs. Perhaps it cleared whatever was wrong in the device driver system. So maybe if you were to install some new device driver you need, or uninstall an existing one, reboot and then reinstall that same device driver, perhaps it will clear whatever is messed up in your device drivers.
Sorry I can't be of more help, and my suggestion is only a guess based on my only recent system changes.
There is very little documented solutions to this problem out there, only lots of people that have complained about the same type of problem, with every sort of device you can think of. And the solutions documented are always specific to those exact devices.
psouza's one-click root is not working for me. when i try to run it, it says "searching for the phone" and hangs.
I just got a replacement from Verizon and i notice it is XT862. Does this matter?
I have the proper drivers installed, I have Debugging enabled, and it USB is set to Charge Only. Not using the original usb cable bc I don't have it (does this really make a difference??) but i have tried numerous different cables.
When I go into adb and type adb devices, it says list of devices is attached, and there are no entries. It seems my phone is not being recognized, despite the f
Any ideas???
Did you try mass storage or pc mode?
I had that issue with my USB cable. I used the one with my device and it didn't come up. I went grab another USB cable in the house and it worked.
yeah, tried them. Didn't mention that cause if I understand correctly, it should be in charge only.
thanks for the help!
I hope you figure something out good luck
Edit: have you tried running command prompt as administrator?
yeah. same result.
I read in another thread that you were required to us the cable that came with the phone for it to be detected. But also, I used a BlackBerry branded cable to do it on mine, and it worked.
come to think of it, i think i used a blackberry cable to root my first d3. will give it a shot and report back.
why the heck would it matter what cable you use? Though it doesn't make sense to me, it appears that the cable is indeed important.
SrulDog said:
psouza's one-click root is not working for me. when i try to run it, it says "searching for the phone" and hangs.
I just got a replacement from Verizon and i notice it is XT862. Does this matter?
I have the proper drivers installed, I have Debugging enabled, and it USB is set to Charge Only. Not using the original usb cable bc I don't have it (does this really make a difference??) but i have tried numerous different cables.
When I go into adb and type adb devices, it says list of devices is attached, and there are no entries. It seems my phone is not being recognized, despite the f
Any ideas???
Click to expand...
Click to collapse
Download the USB and Charging Drivers off of Motorolas website, make sure your phone connects to USB mass storage after you do this, then switch to charging mode.
It took a blackberry cable *and* reinstall of the moto drivers, but im up and running and rooted. now, to figure out how to get my other d3 to stop bootlooping...
glad to hear that you were able to root sorry about the bootloop though, have you tried using the SBF file to flash your rom back to stock to attempt again? i'm just getting into the d3 mod scene so i can't provide links to files or anything other than what i was told to do in response to questions i had and unfortunately that was one of them lol,
I had to use the cord that came with my phone. For some reason Motorola is bad about not using standards. For example there was an old 355 flip phone that is a Motorola I used to have and it wouldn't charge with anything but a Moto charger. It may be the same port but not the same compatibility. Thankfully it will accept a charge from any microUSB source.
Sent from my DROID3 using XDA App
Doesn't your phone have to have "USB Debugging" enabled as well?
USB Debugging enabled + choose Charge Only mode. That should do it.
LaZiODROID said:
Doesn't your phone have to have "USB Debugging" enabled as well?
USB Debugging enabled + choose Charge Only mode. That should do it.
Click to expand...
Click to collapse
yeah, to fiddle w/ any rooting, you need to have debug on
digitalsynner85 said:
glad to hear that you were able to root sorry about the bootloop though, have you tried using the SBF file to flash your rom back to stock to attempt again? i'm just getting into the d3 mod scene so i can't provide links to files or anything other than what i was told to do in response to questions i had and unfortunately that was one of them lol,
Click to expand...
Click to collapse
Yeah, I was able to flash the SBF. It was really exhausted and couldn't figure it out when I originally posted, but after a nights sleep, I was able to do it just fine.
Before I send my phone back to verizon, I was wondering - Is my phone still rooted after I flashed the SBF? I would ordinarily just run an app that checks, but i can't get past that annoying "activate your phone" screen.
SrulDog said:
Before I send my phone back to verizon, I was wondering - Is my phone still rooted after I flashed the SBF? I would ordinarily just run an app that checks, but i can't get past that annoying "activate your phone" screen.
Click to expand...
Click to collapse
that sucks that you're sending it back to verizon, hopefully next time when you root and rom, it won't botch the radio up lol
digitalsynner85 said:
that sucks that you're sending it back to verizon, hopefully next time when you root and rom, it won't botch the radio up lol
Click to expand...
Click to collapse
uhm, what are you talking about exactly?
my keyboard is broken so they sent me a replacement. It was during the process that I was trying to unroot the one thats going back to verizon that I softbricked it.
I have fixed it. Now I want to know if the phone is still rooted or not. And the radios have been totally fine the whole time.
SrulDog said:
uhm, what are you talking about exactly?
my keyboard is broken so they sent me a replacement. It was during the process that I was trying to unroot the one thats going back to verizon that I softbricked it.
I have fixed it. Now I want to know if the phone is still rooted or not. And the radios have been totally fine the whole time.
Click to expand...
Click to collapse
oh ok, you said you couldn't get past the phone activation screen, i thought you were saying that your radio got botched in the process somehow lol, my bad
SrulDog said:
Now I want to know if the phone is still rooted or not. .
Click to expand...
Click to collapse
if you used rsd to sbf you are no longer rooted.
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Youngtusk said:
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Click to expand...
Click to collapse
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
eyeyousee said:
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
Click to expand...
Click to collapse
Thanks for the tip. Does flashing a boot.img and stock recovery require adb? Currently, that is where my main setback is.
If it doesn't require adb, can you point me into the direction of the right keywords to Google to find out how to do that?
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
AlkaliV2 said:
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
Click to expand...
Click to collapse
So, I've been on stock until I switched over to CM12. I do have a twrp backup but apparently only did that after I moved to CM12. I have only the most basic (read basically nonexistent) understanding of ADB, and can follow directions I find online but no real knowledge as to how anything works. I also did not use wugfresh, but unlocked via ADB and rooted via chainfire. Honestly, I followed most of the direction I found on youtube via a creator called wwjoshdo (I'd link but I'm not allowed).
Otherwise that feels like the info. I didn't fiddle with my nexus until I started have battery issues and then decided to unlock/root/flash, and that was about 6 weeks ago. I'm also running what standard apps for a rooted device on CM12, flashify, cyandelta, setcpu, and, Titanium Backup. Help?
llawhsoj said:
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
Click to expand...
Click to collapse
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
RMarkwald said:
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
Click to expand...
Click to collapse
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
llawhsoj said:
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
Click to expand...
Click to collapse
So this link will get you up and running with ADB (if it isn't already working): http://forums.team-nocturnal.com/index.php?/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10-updated-9-11-2015/
These are the most common commands that are used with ADB once you get it installed. Also, an excellent way to pull a log from the command prompt: http://developer.android.com/tools/help/shell.html
Assuming you can see the device once you pass the command, "adb devices" it means you are connected but the MTP driver hasn't been loaded properly. I had to fix this by cycling Android debugging and ADB notification in developer's option until Windows was like, "Hey! There it is!" Also, MTP works properly for me when booted into TWRP so if you desperately need to transfer a file you can do it from the TWRP recovery menu.
Noob Tip/Reminder: Make sure that when you plug it in the first time you change it from 'Charge Only' to MTP and if things still seem quirky reboot Windows. It's all just a game of getting it recognized at this point.