I'm sure I'm not the only person who's had this issue but I've read through a bunch of threads and can't seem to find any that mirror the issues I'm seeing.
I downloaded the latest google drivers here:
https://developer.android.com/studio/run/win-usb.html
I changed the USB mode from charging to file transfer (not sure if that matters but one of the threads said this helped discover the ADB device needs, which was the case for me)
When I look at the device manager, I see this:
http://pasteboard.co/5UkUolhM2.png
I actually thought I was going to see this (based on a few user posts I read) but no luck . . .
http://pasteboard.co/5Uo9QvP8z.png
I hate asking such a basic question (I'm trying to root my phone but I'm already stuck at the backup stage . . . heh) but I've honestly tried to look through the threads and resolve it but I haven't found a solution yet. It doesn't mean one doesn't exist (I apologize if one does, I honestly have tried to solve this myself).
I apologize for the links rather than pics but it doesn't seem to want to let me use the IMG tags (do they not work with *.png?).
Any help you can give me would be greatly appreciated. Thanks!
I have a somewhat similar problem. Which I can attribute to some sort of driver/inf screw up
Any device i connect to my Win 10 PC in MTP mode gets recognized in device manager as MTP device and I can't do anything about it.
Unless I go back to driver setting, have it automatically find updated drivers, which it doesn't.
But then right after, if i go to manually select driver and switch it from MTP to MTP USB - it fixes everything
Any idea how to fix that. I'm sure it's a similar issue to this.
I couldn't use the Google drivers, I had to use the OnePlus Driver package.
Beside, did you guys enable USB debugging?
Cheers
Tom
if device manager is showing any unknown devices then start with that when you can plug in the phone without problems have a look at this.
https://forum.xda-developers.com/showthread.php?t=2317790
Which adb version do you use?
Sent from my ONEPLUS A3003 using Tapatalk
I've actually tried installing those drivers (on the partition), the google drivers, a fastboot and ADB program, and even an all in one tool for drivers and none of them worked.
That said, I might have found my problem. I've tried several approaches and found out the the virus protection on this computer (Cylance) is blocking everything. Also explains some issues I had getting things to work with some home automation projects . . . I'll have to find another computer for development.
I'll give you guys an update once I have one. Thanks for the quick replies.
I wanted to follow up on this since I got it up and working just fine.
First off, thanks to everyone that helped, either those that provided answers, or those that confirmed they were seeing the same issues.
It does appear that cylance (my antivirus) was blocking a number of things. I have a different laptop with a fresh version of windows 10 (not a requirement, just making note of this) and protected by bit defender and set it up with that. This is what I did:
1) Plug phone into computer
2) Went to pulldown menu, clicked on "charging mode" and changed it to "transfer files"
3) A partition was found on my computer called "Oneplus Drivers" (on the my computer page, next to the C drive). I double clicked on the directory and it installed the drivers to my computer
4) I downloaded and installed Minimal ADB with fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790. (You'll need to click a few links to get to the actual download but I wanted everyone to know that it's a legitimate link and not just my own personal/questionable source)
5) I ran minimal adb and typed "adb devices". It will show your device as "unauthorized" initially because it hasn't been accepted on your device. Open your device and click allow or ok or something to that effect (didn't think to take a screenshot). Your call if you want it to always remember that device.
6) Type "adb devices" again and it should show your device labeled "device"
So yeah, that's how I got the basic ADB up and working. Hopefully you guys resolve this as well. Good luck!
I was too having the same issue but solved using this easy method https://youtu.be/LbAq6d2Du0U
jbrookley said:
I'm sure I'm not the only person who's had this issue but I've read through a bunch of threads and can't seem to find any that mirror the issues I'm seeing. ...
Click to expand...
Click to collapse
Try the ones here? > http://www.technobuzz.net/download-oneplus-3-usb-drivers/
hello2010 said:
Try the ones here? > http://www.technobuzz.net/download-oneplus-3-usb-drivers/
Click to expand...
Click to collapse
I'm confused, I posted a solution to this 2 posts ago. Are these drivers any better than the ones that are on the phone itself as described in my previous post?
jbrookley said:
I'm confused, I posted a solution to this 2 posts ago. Are these drivers any better than the ones that are on the phone itself as described in my previous post?
Click to expand...
Click to collapse
I haven't compared them so I can't comment. The above link was where I learned to install the drivers once (because it worked the first time). If your connection is working fine now, just treat the info in the link as added reference.
hello2010 said:
I haven't compared them so I can't comment. The above link was where I learned to install the drivers once (because it worked the first time). If your connection is working fine now, just treat the info in the link as added reference.
Click to expand...
Click to collapse
Oh, ok! All caught up!
Having the same issue. Didn't have any issue with my old Huawei Ascend Mate 2 though.
j03x2 said:
Having the same issue. Didn't have any issue with my old Huawei Ascend Mate 2 though.
Click to expand...
Click to collapse
Have you tried any of the solutions that were posted?
Didgeridoohan said:
Have you tried any of the solutions that were posted?
Click to expand...
Click to collapse
Problem solved now. For some reason the USB Debugging flag changed without me doing it.
Related
sorry if this clutters up the forum for a bit, i promise to delete it when it dies.
i've recently started using adb when i flashed over to 5.0.2h. i followed the instructions in the tutorial and was able to use adb. 2 nights ago, i began doing more complicated commands (for me) and tried to push a .apk into /system/app.
i wasn't immediately successful but i eventually got it in there and decided to reboot my phone. after this reboot, however, i lost the use of adb. i tried upgrading to the usb drivers haykuro posted, uninstalling them and re-trying the old one, rebooting the computer, rebooting my phone and none of it works. i've since wiped my phone and flashed it with the latest h build from haykuro (thanks haykuro!) but that didn't work either. now i'm trying to see if the 1.5 sdk will work.
i was wondering if anyone would have an idea about what i should do next. should i reinstall adb? try it on another computer? another cable? it's not the worst loss in the world, my phone is fine and my usb cable still works in the conventional way. i even checked to see if i somehow lost root and i was able to get su on the terminal emulator. but i still want the use of adb for nandroid, if nothing else.
thanks in advance!
I had the same problem after flashing to the G rom. I couldn't get ADB to work but fastboot recognized my phone and I was able to flash back to my backup. First time I did a complete wipe before flashing, second time, no wipe, made no difference in either case for me
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
I just had the same problem, I had to update the driver and it is working fine now.
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
zer0day said:
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
Click to expand...
Click to collapse
Give me a few minutes I will find you a link for it.
jordanjf86 said:
Give me a few minutes I will find you a link for it.
Click to expand...
Click to collapse
Here it is. http://dl.google.com/android/android_usb_windows.zip after downloading this when you go to update your driver in device manager make sure to use this. Hopefully this will help it worked for me.
jashsu said:
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
Click to expand...
Click to collapse
yes, that's what it comes up as. and i've tried the usb drivers from haykuro's page and they didn't work before and after rebooting my computer.
i'm on vista and it wont accept the updated drivers. it downloads the standard removable memory drivers and wont let me update to anything else. anybody have any ideas
just installed the 1.5 apk and adb and it works again. for people running haykuro builds, i would suggest trying this if you have adb problems. just intall the 1.5 sdk as normal, copy adb.exe and AdbWinApi.dll into \system32 and you should be good.
unless requested i will delete this thread in two days. thanks everyone!
Hmm... i tried that and its still not working ):
Ive tried like 10 different USB drivers from various sites including this one, downloaded the 1.5 SDK and installed it, wen through several reboots and it always says either that the driver is for the wrong platform, the most up to date one is ALREADY installed (HTC Bootloader), or that Windows couldn't find any drivers.
Under ADB Interface in device manager is "%USB\VID_0BB4&PID0FFF.DeviceDescRelease%"
did you try and update the driver through the device manager? i've heard that it's the only way to update it for some people.
I had already Posted & Solved This Issue here : http://forum.xda-developers.com/showthread.php?t=493703
Go Check It, It ll work for sure....
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Hi
I actually replying about the bible quote you have mentioned? you into theology?
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.
my samsung galaxy s is not recognized by my computer no matter what i do!
don't know why, i've done some research, no results.
i've installed Kies, which i assume already installs the drivers, but when i connect, the computer shows no sign of connection (it says that i need to update drivers in device manager??) i tried different USB ports, toggled USB debugging on/off, NOTHING WORKS
the reason i want my computer to recognize the galaxy is because i want to update it to android 2.3.5 via odin. but when i enter download mode, the computer doesn't recognize it. when i'm in the system, the computer STILL doesn't recognize it...???
please somebody help, it's rooted, running a different MIUI version (not the ones in xda dev section), i'm not sure where i got it from, but it's called an ENG_MIUI?
CM7 (and subsequently MIUI) is built from the Nexus S source code, so find the proprer drivers for it. "CM7 drivers" should be a sufficient google search. Also, Kies sometimes interferes while using the other drivers. If you run into any problems, uninstall Kies.
Okaham said:
my samsung galaxy s is not recognized by my computer no matter what i do!
don't know why, i've done some research, no results.
i've installed Kies, which i assume already installs the drivers, but when i connect, the computer shows no sign of connection (it says that i need to update drivers in device manager??) i tried different USB ports, toggled USB debugging on/off, NOTHING WORKS
the reason i want my computer to recognize the galaxy is because i want to update it to android 2.3.5 via odin. but when i enter download mode, the computer doesn't recognize it. when i'm in the system, the computer STILL doesn't recognize it...???
please somebody help, it's rooted, running a different MIUI version (not the ones in xda dev section), i'm not sure where i got it from, but it's called an ENG_MIUI?
Click to expand...
Click to collapse
To get your phone recognized you need nexus s drivers. But that won't help you get it recognized by kies.
You need stock firmware on your phone to get it updated through kies.
Sent from my GT-I9000 using xda premium
I have same problem previously. But it solved after I do this: while Kies open, select Tools then press Install driver.
thanks guys, but how would i go about doing that? the directions i found don't make any sense?
ndemin said:
I have same problem previously. But it solved after I do this: while Kies open, select Tools then press Install driver.
Click to expand...
Click to collapse
Just to clarify, this won't help you. Samsung uses Samsung drivers. Since you do not currently have Samsung firmware on your phone, this won't do you any good. As previously stated by two very informative posters, you will need the Nexus S drivers to recognize your phone.
And, also as previously stated by just an absolutely wonderfully helpful poster, if you do a simple google search you'll find exactly what you need. Try either Nexus S Driver, CM7 Driver, Nexus S CM7 Driver, or really anything else similar. You could also check the CM7 Wiki, as I'm sure there would be a link for them there. And finally, if you simply search XDA Developers, I'm sure you'd find plenty of posts with what you need.
Hopefully that helps.
thanks
now my computer can see it when it's in android, but why does it STILL not see my Galaxy S in download mode???
do i need another set of drivers? (it said driver not found)
BTW THANKS GUYS!!! sorry if i'm being annoying
hello??
anybody??
Well did you install the Nexus S drivers yet?
upichie said:
Well did you install the Nexus S drivers yet?
Click to expand...
Click to collapse
yes, the nexus s drivers are installed, but i STILL can't connect through download mode...
try different computer, install samsung driver then connect your phone
still doesn't work???
Well, it seems to be a driver issue!
Try these (32-bit windows) but make sure that you are having a fresh win7 installed just in any case that your reg got corrupted with drivers (Ime ).
Still not working,then try on another pc..!
---------- Post added at 07:12 AM ---------- Previous post was at 07:06 AM ----------
upichie said:
Just to clarify, this won't help you. Samsung uses Samsung drivers. Since you do not currently have Samsung firmware on your phone, this won't do you any good. As previously stated by two very informative posters, you will need the Nexus S drivers to recognize your phone.
And, also as previously stated by just an absolutely wonderfully helpful poster, if you do a simple google search you'll find exactly what you need. Try either Nexus S Driver, CM7 Driver, Nexus S CM7 Driver, or really anything else similar. You could also check the CM7 Wiki, as I'm sure there would be a link for them there. And finally, if you simply search XDA Developers, I'm sure you'd find plenty of posts with what you need.
Hopefully that helps.
Click to expand...
Click to collapse
Well, CM7 drivers won't help SGS to get recognized on PC on DLD mode, you need another set of drivers and not those Nexus S's. I had the above ones installed on my PC (Google's your Best friend ) .
I had to install the drivers manually,
Right click on computer, click manage -> device something -> find your device in the list, select to update driver, search manually and enter the path to your android sdk and search.
Worked like a charm to me
Sent from my GT-I9000 using XDA App
pzayx said:
I had to install the drivers manually,
Right click on computer, click manage -> device something -> find your device in the list, select to update driver, search manually and enter the path to your android sdk and search.
Worked like a charm to me
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
computer could see device in download mode?
hi
i had same problem, but computer recognize the device as "unknown device"
in all modes, developed, storage etc...
i am close to think thats is problem of internal usb driver of the rom
want to downgrade from de device, whitout usb, but i dont know how do it, because i am not root, and its no possible in 2.3.4 whituot usb.
thanks
I had a lot of similar issues with my I9000, too.
Tried everything on ROM and driver side also on different computers.
Finally it turned out that my Micro USB connector was corroded.
I have around 30 people in our company that have the same phone, and 5 of them had similar issues. I guess it's a common problem with this device.
I took a toothpick and cleaned the contact of the connector by sliding it up and down for a couple of million times. This also did the trick for my colleagues.
I think it's at least worth to try it.
Good luck
i try to clean the contact, but still cant connect to the computer.
I wonder if a method of degrading the system with a signed rom from the recovery, without using the USB cable or ODIN.
i have a same problem. Any new solution?
snbmf said:
i have a same problem. Any new solution?
Click to expand...
Click to collapse
use this guide
Check this out! Links to useful Guides and " Banned " Documentaries
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.