Related
Hi
recently, i decided it was time to wipe my computer clean and do a fresh install (you know, its like flashing roms, sometimes fresh is better) so i reinstall win 7 ultimate x64 and for the life of me, i cannot get adb to recognize my g2 with cm7 rc1... ive searched through several threads on installing the proper drivers, installed the most recent version of htc sync, latest android sdk, and nothing... its not such a big deal, but i would like to flash to the final of cm 7, but i dont like a lot of the fluff in cm7 (adw, etc) and find it easier to remove and change things around through adb.
thanks in advance
Did you use the installer to install the android sdk? I had issues as well with that one. Removed it and just extracted the .zip package, after that it worked fine.
This REALLY is a tricky one. In the past I've had luck installing both the HTC sync software, and PDANet. Between those two all the drivers seem to work for me in Win 7 64bit.
Why not just use a file manager like 7zip to remove/add the things you want prior to flashing. Or do you just like doing things the hard way?
kamontryst said:
Hi
recently, i decided it was time to wipe my computer clean and do a fresh install (you know, its like flashing roms, sometimes fresh is better) so i reinstall win 7 ultimate x64 and for the life of me, i cannot get adb to recognize my g2 with cm7 rc1... ive searched through several threads on installing the proper drivers, installed the most recent version of htc sync, latest android sdk, and nothing... its not such a big deal, but i would like to flash to the final of cm 7, but i dont like a lot of the fluff in cm7 (adw, etc) and find it easier to remove and change things around through adb.
thanks in advance
Click to expand...
Click to collapse
See bold. Therein lies your problem.
dhkr234 said:
See bold. Therein lies your problem.
Click to expand...
Click to collapse
Unless it's specifically a problem with Ultimate, there's no reason it won't work. I run Win 7 Home Premium x64 at home and the steps I said work for me.
I run 7 ultimate 64bit and adb works fine for me.
I used the pdanet drivers.
Flash with rom manager and then install zip from card..the adwmod zip that is..take it out for you
Sent from my Vision using XDA Premium App
dhkr234 said:
See bold. Therein lies your problem.
Click to expand...
Click to collapse
I have to agree with everyone else on this. I'm running Windoze 7 X64 and adb works just fine. I also have Ubuntu 10.10 64bit and Sabayon 64bit on my HDD (yay multiboot!) and neither of them have issues either.
dhkr234 said:
See bold. Therein lies your problem.
Click to expand...
Click to collapse
i was using win 7 ultimate 64 before, and it worked just fine, im staring to think that its my actual hardware usb port on the tower, my wifes phone (mytouch slide) isnt recognized either, and i have gotten my younger sisters pc to recognize my phone no problem (except the pc is slow as dirt...
KCRic said:
Why not just use a file manager like 7zip to remove/add the things you want prior to flashing. Or do you just like doing things the hard way?
Click to expand...
Click to collapse
i use winrar to change files around before i flash it, but lately ive been having problems with the edited rom (i.e. install fails, boot looping even after a data/cache wipe, etc) i just wanted to try a different route this go around
You could try another usb cord, and make sure everything is installed under admin,and the way I got my drivers I edit the driver file and added the info for G2 (saw it in tmobile forum) and also I have no problem with win 7 x64 aswell... and I agree I don't like all the extra puff and bluff oin cm7
well, i havent been able to get a wired adb to connect, but i have gotten it to work with wirelessadb and i am now rockin a modified cm 7 final
Samsung Canada is a garbage website which has no drivers to download, only Kies. Installing Kies didn't work because my computer won't recognize the phone.
I also tried installing other random drivers for gnex found on the webz. None of them worked.
I was wondering if anyone knows of a good official driver for this guy.
Btw i'm running the non-verizon one.
convolution said:
Samsung Canada is a garbage website which has no drivers to download, only Kies. Installing Kies didn't work because my computer won't recognize the phone.
I also tried installing other random drivers for gnex found on the webz. None of them worked.
I was wondering if anyone knows of a good official driver for this guy.
Btw i'm running the non-verizon one.
Click to expand...
Click to collapse
Use these: http://forum.xda-developers.com/showthread.php?p=22915085
Sent from my Galaxy Nexus using Tapatalk
If you need the USB drivers so that you can use ADB and fastboot, you can install them in this. Just follow the instructions provided in there. I found it to be the easiest method to get them.
Tried both already. Didn't work. Comp still won't recognize my gnex is plugged into comp. Win 7 x64.
Then would it still be the drivers fault or my phones fault.
I have Win7 64 bit on both my laptops, no problem with recognition. I do however have the Android SDK + Google drivers installed on both machines; do you?
The drivers are shoddy. If you look under Device Manager while plugged in, it probably has a ! on the device. Manually update it, choose list from computer, and go under Samsung Android device or something like that.
Greetings fellow GNex owners and enthusiasts!
I've been trying to root my Galaxy Nexus unsuccessfully for the past week.
Here's what I've done so far:
1. I Unlocked the bootloader as per Droid-Life's instructions using an old method with the cmd prompt. (The complete How-To guide on their website) I installed the SDK on a windows 7 64-bit machine and went ahead with the process. This worked fine.
(*Note: My Gnex is stuck on 4.0.2 and it won't pull an update. I've tried the method of clearing the data from the framework app and resetting the clock to 1969 multiple times without success. probably 10-15 times.)
2. Since that I've tried uninstalling/reinstalling drivers, rebooting, and then rebooting some more. I've tried every available "noob-proof" method out there and i can't get it to work.
Tried Galaxy Nexus Tooklit v5.6
With and without the included drivers. tons of reboots and re-tries. root always fails.
Wugfresh's Toolkit 1.3
with and without the included drivers. tons of reboots and re-tries. root always fails.
Manually pushing CWM Recovery and SU to the phone with cmd promt via other tutorials floating around the internet, etc. Pushing CWM Recovery fails. Can't even get the temporary flash going to install SU
NOTHING works.
Is it because I unlocked the bootloader manually using an older method first?? I'm pretty sure I've been following the various instructions with each method accurately.
Can someone shed some light on me? I don't necessarily want to mess with kernels and custom ROMs. I just want to be able to wirelessly tether like I could with my OG and D2.
Thanks in advance,
Thanassi
Check my sig and try my method?
Haha.
But I'm guessing driver error.
The simplest method for getting drivers is to download and install pdanet on your PC. Then simply try again.
http://junefabrics.com/android/
I've had to root my phone 3 times and each time took 3 tries before it took. As mentioned before also make sure your drivers are good. And su files.
bow chicka wow wow.
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
shohratshankar said:
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
familyguy59 said:
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
Click to expand...
Click to collapse
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
shohratshankar said:
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
Click to expand...
Click to collapse
Yes. You don't need the SDK, as a matter of fact
The Rundll32 part, is a fact, when installing the drivers...
It has the following effect:
You have installed ADB drivers (no Rundll32). You are flashing away, and all of a sudden. BANG! Everything stoppen. Phone's bricked... Why? Windows thought it is being smart, and installed new drivers, whilst you were working. However, with the RunDll32 command, you can tell Windows, that YOU want to install the drivers manually, and check manually. Of course, you can turn this off, if you want. No prob. but I personally recommend leaving it off
It's saved many phones' lives ^^
so you are having trouble with the adb or fastboot drivers? is so i had this problem too and sometimes even have to reinstall those drivers after flashing a rom.
i had to manually install the drivers using device manager, just select the android device and go to update driver. Choose "Browse my computer for driver software" then pick "Let me pick from a list of device drivers on my computer" then choose Google in that list.
Error
familyguy59 said:
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
Click to expand...
Click to collapse
I get an error message with this application whenever I attempt to do something.
tried that
shohratshankar said:
I'm a noob too.
I followed the following method:
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
thanassi44 said:
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
GSM only??
efrant said:
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
Click to expand...
Click to collapse
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
thanassi44 said:
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
Click to expand...
Click to collapse
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
FINALLY! Have Root.
efrant said:
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for all your responses and suggestions. I finally got something to work. After some more driver swapping and rebooting, now on an XP machine, I got wugfresh's toolkit 1.3 to flash cwm recovery and I was able to install su. The program then ran an automated script to allow permanent flashing of cwm recovery. Got my titanium backup and from manager back, as well as wireless tether. Thank you all for your attention and patience!
Had such a hard time with this phone that I was beginning to have buyers remorse. Now its been set free.
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Sorry, but I've tested this program, over and over. I use it, myself. I never habe any problems...
But, I'm in the making, of a Youtube video. I'll post it, in my thread Then maybe you can see, what you did wrong
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Hang on... Did you install the scnd. file, within the ISO? If not, there's your problem...
When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?
Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app
Disregard. I figured it out. It was a driver issue after all.
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.
thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
fixed mine by just forcing it to reinstall the drivers.
fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.
Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app
To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.
So here's the thing, my Nexus 5X, when loaded into bootloader and connecting to my computer running Windows 10, doesn't work with the official drivers. (https://developer.android.com/studio/run/win-usb.html)
It connects fine, and reports itself with the hardware id "USB\VID_18D1&PID_D00D", which is not present in the android_winusb.inf or any drivers included in windows. In fact, I couldnn't find *any* official drivers, not even from LG, nor "universal" drivers. Tools like "SKIPSOFT ANDROID TOOLKIT" (http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444) didn't help, either.
I did some research on google and xda, too, and couldn't find anything conclusive. Hundreds of people should have this problem, if the Nexus 5X isn't supported by the official adb/fastboot drivers. I'm honestly puzzled, as it seems that most N5X owners don'tr have this issue. What's "wrong" here?
I found the same.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.
You can try the drivers in the attached post if you like. It should work fine on 32/64 bit windows.
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
I don't get it, what happens exactly when you try to run adb commands?
Shebee said:
I don't get it, what happens exactly when you try to run adb commands?
Click to expand...
Click to collapse
Same thing that happens if you ran adb commands with no device connected.
Shebee said:
I don't get it, what happens exactly when you try to run adb commands?
Click to expand...
Click to collapse
Well, without the right drivers, doing anything with adb is kinda pointless.
sfhub said:
I found the same.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.
You can try the drivers in the attached post if you like. It should work fine on 32/64 bit windows.
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
Click to expand...
Click to collapse
These help. Still, pretty weird that Google doesn't support the 5X, epsecially because literally no other Nexus device has these issues.
anon768 said:
These help. Still, pretty weird that Google doesn't support the 5X, epsecially because literally no other Nexus device has these issues.
Click to expand...
Click to collapse
I had even more problems on the Nexus 7 2013. Not only was adb not working, but neither were the MTP IDs being recognized so I had to "fix" them for myself also. Judging by the number of people that downloaded those drivers, other people had the same problems.
I don't know what the deal is with drivers and Nexus devices that I've used. I would have thought Nexus being a developer oriented device and with them being Google branded, drivers should be the last of my issues.
Perhaps everyone who uses Nexus and needs adb to work is savvy enough to search or fix themselves and Google doesn't get any complaints.
Also some people have installed "universal" drivers in the past, which may account for why they don't encounter issues with recognition as long as this isn't their first Nexus device.
sfhub said:
...
I don't know what the deal is with drivers and Nexus devices that I've used. I would have thought Nexus being a developer oriented device and with them being Google branded, drivers should be the last of my issues.
Perhaps everyone who uses Nexus and needs adb to work is savvy enough to search or fix themselves and Google doesn't get any complaints.
...
Click to expand...
Click to collapse
That's probably part of it. My guess is most developers use Linux or OSX (so they can develop iOS apps too) and simply don't have the driver issues that plague Windows.
anon768 said:
Well, without the right drivers, doing anything with adb is kinda pointless.
These help. Still, pretty weird that Google doesn't support the 5X, epsecially because literally no other Nexus device has these issues.
Click to expand...
Click to collapse
I use the Google drivers and they work fine.
On win10
Shebee said:
I use the Google drivers and they work fine.
On win10
Click to expand...
Click to collapse
Could you post the drivers and also their origin (ie came with win10, downloaded automatically by win10, downloaded with Android SDK, etc.)
Just the .inf file.