I'm sure it's been asked a bunch. I read the discussion for Jan 15 but none of those helped. Anyone have this problem lately? Maybe something updated in the last few months so I need a different driver? It must be a simple driver issue. If someone has the right driver maybe I can specifically install it. I just want to turn the headphone volume up. The volume on most phones sucks out of the box.
jeffrimerman said:
I'm sure it's been asked a bunch. I read the discussion for Jan 15 but none of those helped. Anyone have this problem lately? Maybe something updated in the last few months so I need a different driver? It must be a simple driver issue. If someone has the right driver maybe I can specifically install it. I just want to turn the headphone volume up. The volume on most phones sucks out of the box.
Click to expand...
Click to collapse
It usually is a driver issue. I assume you are on Windows 8.x or 10. If so go to Device Manager and find the QCOM device. I dont recall the full name of the device off my head. Once you find that go to the driver tab and then hit update drivers.
I do beleive that windows will pull down the latest drivers automagically.
Scott said:
It usually is a driver issue. I assume you are on Windows 8.x or 10. If so go to Device Manager and find the QCOM device. I dont recall the full name of the device off my head. Once you find that go to the driver tab and then hit update drivers.
I do beleive that windows will pull down the latest drivers automagically.
Click to expand...
Click to collapse
What funny is just now I used the power button to go into bootloader then I plugged it into the computer to see what it's called in device manager and it recognized it. It wasn't QCOM device or anything phone related so not sure what it was called. I then unlocked the bootloader, but now when I'm back in the bootloader it does not recognize it again and the name is "unknown usb device(device description request failed)". So maybe it's not a driver issue if it recognized it. I had just updated the phone to the new 9.016 or something. Maybe I should reboot the phone and try again. I'll try to update the driver again but that's what I've done quite a few times.
Update:
I decided to boot right into bootloader again with the power butter option by enabling it in Developer Options and then plug into the pc and check with powershell and fastboot devices worked. The only thing different is that I can think of is I enabled developer options just before but not sure if that did anything. It worked either way so I loaded twrp and magisk and I'm rooted. I just want to change the headphone volume but still get updates later. I'll google to see if an unlocked bootloader will allow updates or maybe root will prevent it. If I unroot and relock as long as my headphones are loud then that's cool. Thank for the help guys.
jeffrimerman said:
Update:
I decided to boot right into bootloader again with the power butter option by enabling it in Developer Options and then plug into the pc and check with powershell and fastboot devices worked. The only thing different is that I can think of is I enabled developer options just before but not sure if that did anything. It worked either way so I loaded twrp and magisk and I'm rooted. I just want to change the headphone volume but still get updates later. I'll google to see if an unlocked bootloader will allow updates or maybe root will prevent it. If I unroot and relock as long as my headphones are loud then that's cool. Thank for the help guys.
Click to expand...
Click to collapse
You also have to enable usb debugging and OEM unlocking, if you want to unlock your bootloader.
Yes, sorry I didn't mention that because I've done it many times. I was just trying to think of what was different this time why the bootloader was recognized in case someone reads this in the future and is trying everything. Maybe it was the factory reset, maybe it was enabling developer options immediately before who knows. I did nothing different with the computer or the usb debugging and oem unlocking. The first time bootloader was recognized I literally didn't do a darn thing. I used to have a phone that I could only use the wifi hotspot if I rebooted the phone and immediately signed on with my laptop. A few seconds too long and it wouldn't work.
Related
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
DTTD said:
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
Click to expand...
Click to collapse
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Fallon9111 said:
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for providing more information on this. I have done a Factory Reset via Settings and also via Recovery, but still not available.
I think I'm making progress with adb via Ubuntu over USB, but USB Debugging still gives the Epic crash and still will not charge while On, which is more just annoying than anything else.
Asus/Google Support are saying it is a physical pin issue, but that doesn't explain why USB Debugging is failing. Does anyone know where the USB files are contained? I'm wondering if I've messed up at the Kernel level. Any thoughts?
About my Nexus - More Info
I forgot that I should provide more information about what I'm running:
Phone: Nexus 7
Android Version: 4.2.2
Kernel version: 3.1.10-g05b777c
Build number: JDQ39
Prior to issue also had:
Recovery: TWRP
ROM: Stock JDQ39
MultiROM: Yes
UPDATE
So after more work on my Ubuntu we have found more information and seem to have narrowed down the issue! :fingers-crossed:
I have been able to flash via Fastboot just fine, which has thus allowed me to get TWRP installed and now I'm back rooted. I still cannot adb via USB though. We've double checked with multiple Nexus 7's of the same type, which allow command: adb devices and their devices will show, while it does not for my device. (Side note: my version of Ubuntu does not "see" the adb command in its pwd so... But tests have been done on other machines and worked...)
So after sifting down to adb issues, we found that in /data/property I'm missing persist.sys.root_access and persist.sys.usb.config ... But creation of persist.sys.usb.config didn't do anything...
Hello all,
I've searched and found reference to people having the issue, but couldn't find any resolution and wanted to see if anything new has come up.
I prefer the manual method of rooting, and need to get adb working with this device.
Nexus 10 running 4.3, factory unlocked manually using fastboot (which works fine). I updated all of the relevant stuff in SDKmanager, but still can't get my Nexus 10 to come up in "adb devices" even after killing and restarting adb server. This is on a mac, for the record.
My rooted nexus 4 comes up in adb without issue.
Any thoughts?
Thanks
Did you remember to check "USB Debugging" on Developer Settings?
To unlock Developer Setting you must press many times Build Number, then there you can turn on USB Debugging . Hope it works!
Sorry, should have mentioned that I did put it in USB Debugging mode. I've tried it with the "Verify apps over USB" setting in the Debugging section both checked and unchecked, killing and restarting ADB server each time.
As far as I know I'm doing everything correctly...
Any other ideas?
Did you try killing the server and starting it with sudo? When my adb gives me problem on my Fedora/Ubuntu I do it and solves the problem . Also try plugging in other USB Ports if it's the case.
Normally on Windows when you cant get the device to show up it is a driver issue, I would imagine the same is true for OS X as well. I cant really recommend an alternate driver though since I dont know much about installing this stuff and rooting when running Mac :/
EniGmA1987 said:
Normally on Windows when you cant get the device to show up it is a driver issue, I would imagine the same is true for OS X as well. I cant really recommend an alternate driver though since I dont know much about installing this stuff and rotting when running Mac :/
Click to expand...
Click to collapse
AFAIK Mac is like Linux, and in Linux we don't have this problem, although sometimes it's needed to modify the rules, I decided to keep this for later, only if the more simple methods doesn't work, as it's way harder than these ones I already pointed.
Im having an issue with my phone connecting to computer. I'm trying to get back to stock but have no way in getting into odin without usb. I think their is a problem with something on the phone it isn't a pc or cable problem. I also had a new flex port recently installed. My phone will charge when connected to computer but it will not sync nor even recognized by device manager. I cant find any info anywhere with this issue. I try to enable mtp through hidden menu using *#0808# but it wont stay enabled resets after reboot. I also cant find menu under settings for usb. There use to be a menu in storage but it seems like its not there anymore. im on beans 4.4.2 nc4 with nc2 bootloader. can't find a solution nowhere.
I have the same problem, been trying to search online for few days, can't find the solutions.
Sammguy said:
Im having an issue with my phone connecting to computer. I'm trying to get back to stock but have no way in getting into odin without usb. I think their is a problem with something on the phone it isn't a pc or cable problem. I also had a new flex port recently installed. My phone will charge when connected to computer but it will not sync nor even recognized by device manager. I cant find any info anywhere with this issue. I try to enable mtp through hidden menu using *#0808# but it wont stay enabled resets after reboot. I also cant find menu under settings for usb. There use to be a menu in storage but it seems like its not there anymore. im on beans 4.4.2 nc4 with nc2 bootloader. can find a solution nowhere.
Click to expand...
Click to collapse
bryanling said:
I have the same problem, been trying to search online for few days, can't find the solutions.
Click to expand...
Click to collapse
Try dl'g the Sammy drivers directly from here and just click on the "See all Downloads", click "Send" and save the .exe file.
Run it as administrator, and once complete, plug in phone and that should correct the pc to phone issue.
shaggy_kobain said:
Try dl'g the Sammy drivers directly from here and just click on the "See all Downloads", click "Send" and save the .exe file.
Run it as administrator, and once complete, plug in phone and that should correct the pc to phone issue.
Click to expand...
Click to collapse
Actually it's my phone problem, i try on 10++ pc, all are not working :crying:
bryanling said:
Actually it's my phone problem, i try on 10++ pc, all are not working :crying:
Click to expand...
Click to collapse
Enable developer mode (tap on settings, about and then tap on the build number 7 times to enable developer mode).
Then back to settings, developer options and turn on usb debugging.
Sent from my Note 3 via Tapatalk
. I have original VZ driver installed. and i tried running as admin
Already tried this. On multiple computers. It's not a driver problem it has to do with something that happen after flashing to the leaked kitkat. I flashed beans kitkat and firmware through odin and since then wasnt able to connect to computer via usb. I read somewhere you could flash back to mje but not sure if i could do that without odin. I covered all the basics including enabling developer mode etc.... Kies doesn't work either and that was suppose to be bullet proof. I vaguely remember something similar happening when we got Root de la Vega some people lost usb after flashing and couldn't odin back but cant find that thread with what they did to fix it.
Sammguy said:
. I have original VZ driver installed. and i tried running as admin
Already tried this. On multiple computers. It's not a driver problem it has to do with something that happen after flashing to the leaked kitkat. I flashed beans kitkat and firmware through odin and since then wasnt able to connect to computer via usb. I read somewhere you could flash back to mje but not sure if i could do that without odin. I covered all the basics including enabling developer mode etc.... Kies doesn't work either and that was suppose to be bullet proof. I vaguely remember something similar happening when we got Root de la Vega some people lost usb after flashing and couldn't odin back but cant find that thread with what they did to fix it.
Click to expand...
Click to collapse
Did you disable the mtp application?
drewcam888 said:
Did you disable the mtp application?
Click to expand...
Click to collapse
Do you mean through hidden menu or should there be an app on the phone? I didn't disable it i tried to enable it through hidden menu because it wasn't working but it just resets after rebooting the phone. Also there use to be a menu in storage under settings i could get to but it no longer exists. If you go into settings- storage- it should be a button in the top right corner of your screen which leads you into settings for mtp but it's not there.
Sammguy said:
Do you mean through hidden menu or should there be an app on the phone? I didn't disable it i tried to enable it through hidden menu because it wasn't working but it just resets after rebooting the phone. Also there use to be a menu in storage under settings i could get to but it no longer exists. If you go into settings- storage- it should be a button in the top right corner of your screen which leads you into settings for mtp but it's not there.
Click to expand...
Click to collapse
I too am having this issue... it is quite frustrating. I rooted using towel root and that worked fine up until the beginning of September then USB was gone gone gone!. I was thinking of just doing a factory-restore of my phone, but I am not sure that is possible with having Towel rooted my phone. I just don't know what steps to take. Any help would be greatly appreciated!
i am going to the local verizon store today and if they can not fix this, then i see no reason for me to continue to pay for my phone. there obviously is something wrong with all these phones that people are complaining about. i have been on the phone with verizon and samsung for HOURS. i now am a pro at knowing what's wrong but no one can help me. It does not stay in MTP mode or PTP and goes back to charging. this is a phone problem that should not even exsist. plug your phone in, upload pics. has anyone gotten verizon to replace the phone????that's my goal today
It takes two to tango; how do you know the problem is not the PC?
Older versions of stock software actually put the phone in Airplane Mode when you were using USB 3.0, and had an inactivity timer or something that would turn the USB link off after a while. That didn't happen if you were operating on a USB 2.0 link.
So, if your PC has any non-USB 3.0 ports (the connector will not be blue) you could try using a USB 2.0 port.
Sometimes intermittent behavior is caused by bad cabling or a damaged connector, so a second thing to try is using a replacement cable and/or alternate ports. (Don't buy bargain basement eBay $2 cables btw - you will get what you pay for)
good luck
nancyvf8 said:
i am going to the local verizon store today and if they can not fix this, then i see no reason for me to continue to pay for my phone. there obviously is something wrong with all these phones that people are complaining about. i have been on the phone with verizon and samsung for HOURS. i now am a pro at knowing what's wrong but no one can help me. It does not stay in MTP mode or PTP and goes back to charging. this is a phone problem that should not even exsist. plug your phone in, upload pics. has anyone gotten verizon to replace the phone????that's my goal today
Click to expand...
Click to collapse
Is this a phone that you flashed a custom rom, rooted, or unlocked the bootloader?
Hi all,
I am trying to root my phone, following this guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
However, I am stuck at entering 'fastboot devices' into the command prompt. It will not return my device's serial number. I know this is supposed to be becuase I don't have the correct drivers installed - but I'm pretty sure I do! I've spent hours scouring the internet for solutions and I can't find anything to help. So now I turn to you, please help me
I'm running windows 10.
I've double checked the google usb driver is installed.
I've manually installed the android bootloader interface driver.
The bootloader screen says on my phone says 'Connect USB data cable'. It is already connected and I have tried connecting it to all the ports on my laptop. I'm using the original cable that came with the phone.
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Eric214 said:
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Click to expand...
Click to collapse
I did indeed. And I also fixed it! I just needed to do some more tinkering. I set the fastboot.exe to recommended defaults. Not sure why it was not already but there you go. You can lock or delete this thread now, thanks!
A little history. I have rooted several other brands of tablets, so I am not new at this. Even thogh I am not a programmer by any stretch of the word. My Pixel C drivers work fine in normal mode, I can see the storage as a drive, no problem. I can transfer files back and forth. But, when I boot it into fastboot mode, it will not see it. It is listed as an unknown device in the device manager of Windows 10. I have tried to install the drivers, but they say not found. And this is the driver from the Android website. I'm at my wit's end. I'm not a newbie at windows, either. But, I need suggestions to get this to work. BTW this is the latest version of Windows 10 1903. And I have tried every solution I have found on google and on this website. TIA
Ok, fixed that by selecting a driver from a list of drivers so now I have ADB drivers. I have another issue which I will do some research on if not.....I'LL BE BACK.
What is your goal?
Do you want to use adb or fastboot?
Is the bootloader unlocked, have you enabled usb debugging in the developers menu (hidden) etc
Ok, as I said before, I figured it out. And yes, the bootloader was unlocked and yes USB debugging was enabled. I got everything
working and I am now running Android 9. Thanks for the reply, though.
Toolcrazy said:
Ok, as I said before, I figured it out. And yes, the bootloader was unlocked and yes USB debugging was enabled. I got everything
working and I am now running Android 9. Thanks for the reply, though.
Click to expand...
Click to collapse
Missed that! (you mentioned another issue)
Well done etc