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 folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
Basically, I have posted this exact same problem here months ago, but with not a lot of help. I came here to get help and I intend of leaving with a bit of some. Basically, I rooted my HTC One, turned S-On, and finally installed Cyanogen Mod. Everything was working for the most part. I remember being able to attach my phone to my PC and being able to transfer files over to my phone. Recently that has been working out so well. I try to transfer files from my PC to my phone, such as music/videos/etc, but my phone doesn't show up. I can go to device manager and see my HTC One under other devices with the caution triangle, so basically my device is read to be connected to my PC but is lacking the drivers to use it. Like I said before, I have posted this problem on other forums before, and I have been sent the link to the drivers. I've installed HTC drivers, USB drivers, HTC One Sync, and so much more, but none of that has worked. All that happens is that my phone will connect to my PC, charge, be noticed by the PC but is completely unusable from PC to phone. On the phones side, it's 100% okay. No problems other than the simple nightly bugs, but I know it's the ROM version I am using. I reverted to the last known stable Cyanogen Mod, and the one previous to that. That hasn't fixed the problem as well. I'm running out of idea's and I'm just looking for some help. If you can help, rather then posting a link for drivers and thinking I'm retarded, please do so. I will appreciate it to the fullest. As for that, that is all I have to say. Please help, and all help is appreciated.
PlasticSandals said:
Basically, I have posted this exact same problem here months ago, but with not a lot of help. I came here to get help and I intend of leaving with a bit of some. Basically, I rooted my HTC One, turned S-On, and finally installed Cyanogen Mod. Everything was working for the most part. I remember being able to attach my phone to my PC and being able to transfer files over to my phone. Recently that has been working out so well. I try to transfer files from my PC to my phone, such as music/videos/etc, but my phone doesn't show up. I can go to device manager and see my HTC One under other devices with the caution triangle, so basically my device is read to be connected to my PC but is lacking the drivers to use it. Like I said before, I have posted this problem on other forums before, and I have been sent the link to the drivers. I've installed HTC drivers, USB drivers, HTC One Sync, and so much more, but none of that has worked. All that happens is that my phone will connect to my PC, charge, be noticed by the PC but is completely unusable from PC to phone. On the phones side, it's 100% okay. No problems other than the simple nightly bugs, but I know it's the ROM version I am using. I reverted to the last known stable Cyanogen Mod, and the one previous to that. That hasn't fixed the problem as well. I'm running out of idea's and I'm just looking for some help. If you can help, rather then posting a link for drivers and thinking I'm retarded, please do so. I will appreciate it to the fullest. As for that, that is all I have to say. Please help, and all help is appreciated.
Click to expand...
Click to collapse
Ok,
I think the best thing we can to in this case is the classic troubleshooting.
Try different USB Cables, slots on your PC, DON'T connect it to a USB HUB (I think you already know that.. I just mentioned it to ensure that)
Make a backup and flash the stock Sense ROM
If you can get a connection to your PC .. Cyanogen causes this issue
That was to determine wheter it's your phone or your computer that causes this issue. Pretty basic.
Uninstall your drivers from the device manager interface
Uninstall everything that is related to your HTC One(HTCSync, maybe Kies or other programs like this, Every driver)
Now, make a registry clean to reinstall everything on a clean way
Use Wise Registry Cleaner
Proceed a computer reboot
Now, download the latest version of HTC Sync
Install it with every driver component.
Then uninstall HTC Sync WITHOUT the drivers
Plug in your phone and wait until other drivers are installed
If that's done, try if the connection works
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.
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.