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.
With an ICS ROM installed, I'm not able to use ADB in windows. It doesn't recognize the dinc. Looks like a driver issue, but I've not been able to successfully update the driver either.
Any tips as to what I'm missing on this?
Update: I was able to get it working by forcing windows to use a file that it complained was older. Really don't have a clue as to why that worked, but it did.
I'm trying to install clockworkmod and root, by following the guide here:
http://forum.xda-developers.com/showthread.php?t=2022270
Everything is going well until I reboot into clockworkmod, at which point my computer fails to recognize the Nexus 7 for ADB, and I can't continue.
The weird thing is, after installing the ADB drivers from Asus' website on my Windows 7 PC, it connects perfectly in Windows. However, in clockworkmod, it just shows up in my Windows Device Manager with a yellow exclamation mark next to it.
Anyone knows what the problem might be?
Okay, solved my own problem.
Dunno what the problem was. I also tried installing the official Google drivers from the SDK to no avail. Fixed it by using the PDANet drivers here:
http://www.junefabrics.com/android/download.php
Now all is well.
manekineko said:
Okay, solved my own problem.
Dunno what the problem was. I also tried installing the official Google drivers from the SDK to no avail. Fixed it by using the PDANet drivers here:
http://www.junefabrics.com/android/download.php
Now all is well.
Click to expand...
Click to collapse
Thanks verrrrrrrrrrryyyy much guy. It solved my problem:
http://forum.xda-developers.com/showthread.php?p=46754283
You are awsome for share your knowledge.
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.