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.
Related
im new to the Gnex and im trying to install the device drivers and i cant seam to figure it out. i have installed the toolkit and tried to intall the drivers through there, no luck. i have also downloaded the drivers from the samsung website and tried manually installing them and no luck either. i also tried the PDAnet method and i encountered an error and the install aborts it self. i did have an Epic4gtouch before im thinking those drivers are causing some sort of problem i think. i read and watched the instructions on how to do things but i just cant seam to get it to work. if someone can point me in the right direction, that would be much appreciated. :good: also im not so sure what other info to provide here for someone to better assist me. im doing this through my PC that is running Windows 8 and its a sprint galaxy nexus running 4.1.1, build JRO03U.L700FH05 , UNLOCKED
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.
For some reason after installing the LG driver package I can't install the files it puts into the Program Files directory... (installusb64.exe). It just does nothing...
I was going to try to do some ROM deving for our phone (maybe even try to port 4.3 from N4) but I prefer to have adb drivers installed so I can debug.
Anyone have the same issue?
jamesadalpiaz said:
For some reason after installing the LG driver package I can't install the files it puts into the Program Files directory... (installusb64.exe). It just does nothing...
I was going to try to do some ROM deving for our phone (maybe even try to port 4.3 from N4) but I prefer to have adb drivers installed so I can debug.
Anyone have the same issue?
Click to expand...
Click to collapse
So I'm assuming for Windows? There's 3 sets in this thread. http://forum.xda-developers.com/showpost.php?p=35520144&postcount=1
Probably remove yours, reboot, and reinstall. This should get you going. Hope to see your work soon.
I have tried multiple custom roms and different driver versions and still can't get adb to work correctly on my note 2. I have a ZTE zinger as well and ADB works just fine on that. I am using windows 7 ultimate and have not yet tried my macOS install but I just want this to work. Any ideas?
I got it to work. What I did is uninstall the driver and use the skipsoft ultimate ADB driver to install it. Anyone with the same issue can find it here: "skipsoft.net/download-page"
(I would post it as a link but I haven't made more than 10 posts yet so I can't. Sorry for the inconvenience)
Running the Community build. Bone stock. No root. Stock recovery. No mods at all. Has taken every OTA to day without issue.
The new one just came out today, and it downloads it fine, reboots to install it, and just goes to Recovery. Doesn't install anything. I try to tell it to install from a file, point it to the update that was downloaded, instantly fails.
I try to sideload through ADB, but my PC will not see it in Recovery mode. I had this issue months ago, it has to do with the Win10 driver, but for some reason I can't recall how I fixed it.
Anyone have any ideas?
I would just skip the update, but battery life has been atrocious since the last one and I am hoping that this would fix it.
SquireSCA said:
Running the Community build. Bone stock. No root. Stock recovery. No mods at all. Has taken every OTA to day without issue.
The new one just came out today, and it downloads it fine, reboots to install it, and just goes to Recovery. Doesn't install anything. I try to tell it to install from a file, point it to the update that was downloaded, instantly fails.
I try to sideload through ADB, but my PC will not see it in Recovery mode. I had this issue months ago, it has to do with the Win10 driver, but for some reason I can't recall how I fixed it.
Anyone have any ideas?
I would just skip the update, but battery life has been atrocious since the last one and I am hoping that this would fix it.
Click to expand...
Click to collapse
Battery life has not much to do with the rom.. More with apps. So your phone does not show up under ADB? Well to the unbrick tool follow the first few steps to get your device shown up as something else in Device Manager. Don't actually use the unbrick tool just the drivers! It is required to boot windows 10 into driver signature enforcement before you change/update the driver to the one on the thread.
Puddi_Puddin said:
Battery life has not much to do with the rom.. More with apps. So your phone does not show up under ADB? Well to the unbrick tool follow the first few steps to get your device shown up as something else in Device Manager. Don't actually use the unbrick tool just the drivers! It is required to boot windows 10 into driver signature enforcement before you change/update the driver to the one on the thread.
Click to expand...
Click to collapse
Yeah, I just figured it all out a little while ago... Part of it was that Windows keeps installing the wrong drivers for ADB, and also I needed a newer version of ADB that can handle larger file size updates.