[ANSWERED] Unable to use ADB to connect CM10.1/driver issue - Epic 4G Q&A, Help & Troubleshooting

Hello,
I've been able to use ADB to install and test apps that I'm writing under the stock ROM for my Epic, as well as under CM9 (and I think an early CM10, not sure about that though). After installing the 20130101 build of CM10.1 (keeping the included kernel), I am having issues trying to deploy and debug apps from my any of my computer to the phone (all of which previously worked). I've verified that Android Debugging is still enabled on my phone.
In the device manager on my computer, "SAMSUNG Android USB Modem" and "Unknown Device" are both showing the "problem" icon. I've tried uninstalling and reinstalling various versions of the Samsung USB drivers, I've tried a few versions of Kies, and even a few third-party tweaked USB drivers. It doesn't seem like anything wants to recognize my phone now that is running CM10.1 (or CM10.1 in addition to something peculiar with my installation).
Additionally, if I have USB debugging enabled on my phone, even if I enable USB mounting, the computer won't recognize the mount until I disable debugging mode on the phone. Once I do that, then the volume will appear on my computer. Previously, when ADB debugging in general worked, I wouldn't have to disable debugging to get the USB mass storage mounting to work.
These problems happened at once on all three of my computers that I've been using for Android development, so I'm fairly convinced these issues are directly related to the ROM I'm running. I've attempted to search the forum and Google for others that may have had this issue and what the resolution/work-around might be, but so far I've not found anything. Surely other people are using CM10.1 and developing apps, which makes be believe it could be something unusual with my installations, but I've tried full wipe without a data restore and it didn't seem to have any impact. I've also tried searching to see if there were special drivers needed for CM10.1, and didn't find anything with that either. I know reverting back to an earlier ROM is an option to get ADB working, but I'm really hoping to get ADB working with CM10.1.
Does anyone have any suggestions on what I can check/do to get USB debugging working on CM10.1 (epicmtd)?
Thank you very much for your time
--James

Re: [Q] Unable to use ADB to connect CM10.1/driver issue
I had the same problem, tried absolutely everything I could to get it to work and couldn't... had to roll back to a tw rom to get it to work (not a fan of the HUGE battery drain on cm9)
Edit- I know this doesn't help you, just wanted to point out you're not the only one with this problem....

Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2

Re: [Q] Unable to use ADB to connect CM10.1/driver issue
jeffreyjicha said:
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...

flastnoles11 said:
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
Click to expand...
Click to collapse
I've tried this with my previous uninstall/reinstall driver attempts, but tried it again anyway.
Unfortunately, it didn't' seem to have a positive impact. It looks like it reinstalled the mass USB storage driver, but it did not reinstall any other drivers (like the modem driver) so I'm still not able to do anything with ADB.

Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Have you tried manually installing the drivers?
Here is the .exe that I used to install the drivers for my phone.
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
Have you tried manually installing the drivers?
Click to expand...
Click to collapse
Hello again. Yes. I've tried installing various versions of USB drivers floating around the net as well as Kies (after uninstalling and deleting current drivers to try to avoid conflicts). Other versions of Epic ROMs (Stock, CM9, etc.) worked with ADB using my installed drivers until I installed CM10.1 (maybe starting with CM10) on my Epic.
As an aside, using ADB requires some additional (special) drivers beyond the drivers required for mass storage support.
I'm hoping one of the CM10.1 developers will chime in with what they did and/or installed to have ADB working with CM10.1 on Windows 7.
Thanks!
--James

I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.

jeffreyjicha said:
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
Click to expand...
Click to collapse
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.

samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
No problem.

samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
Activating through developer options doesnt help? just go to about phone --> tap build number 7 times

I just went to device manager, uninstalled the failed USB device, and then plugged the phone back to the computer via USB.
Boom, just like that, all was well.

i tried everything and could not connect to my htc rezound (w/ CM10.1) thru adb. then i tried the following:
1. download the android adk from google (i can't post links)
2. connect phone thru usb
3. on your computer's adk download folder, navigate to sdk\platform-tools\
4. press shift + right click on the window, open command window here
5. type "adb devices" in the command window w/o the quotes
6. there should be a window pop up on ur phone asking for USB debugging permission. say OK.
7. type "adb devices" again and you should see ur phone connected thru adb.

Related

[Q] Yet another "no more prompt" on the phone

Hi,
So before going on, I've now spent couple hours trying to fix this issue, looking for tips and threads without luck.
I'm using a rooted DHD, with an Affinity rom. It works perfectly fine.
Yesterday, a friend asked me to install a custom rom on his tablet, which I did.
I had to clean all my Android drivers because the tablet wouldn't be recognized properly by my computer (no ADB driver).
In the end it didn't help and I had to use a fastboot method, which ended well.
Now, my phone doesn't prompt me what I want to do when I plug it to my computer.
I, once again, clean the usb drivers, installed HTC Sync and all its dependencies but the software doesn't recognize my phone (I couldn't care less, but I suppose it's part of my "no prompt" problem).
Of course I tried with and without AV, firewall... No luck (and I think I rooted my phone with both them ON anyway). I tried other USB ports as well
If I plug the phone without HTC Sync and its drivers installed, Windows 7 installs 3 out of 4 drivers, the last being in this suite I suppose.
I tried using the drivers provided with the sdk, they're not for that missing driver.
With the suite installed, I end up with 2 new devices on my devices manager : one "Android USB Device" labeled "My HTC" and one "mobile device" labeled as "J:" (drive name) which means no ADB drivers.
Of course, USB debug and ask when connect are both ON. I tried turning them ON and OFF, but still no luck (except a new driver installation).
ADB drivers start to install as soon as uninstall the "HTC Drive Installer" component, which is weird.
So I don't really know what to do now except that it's driving me nuts as I cannot do anything else than charging the phone now.
Is this a case of "USB brick" ? The threads I read about it all talk about "stock roms".
Try Multi Mount SD Card from the Market.
https://market.android.com/details?...vaWQubXVsdGltb3VudHNkY2FyZC53aWRnZXQuZnJlZSJd
Thanks for the alternative, it works fine
I'd still like to know how to fix this though, if anyone has any clue about it.
It's a sense rom?
Sense roms have an option to permanently put the usb state to charging or storage, etc, without prompting you again. It's an option you tick, in the settings (usb connections, or usb sync maybe? sorry, I don't use sense).
Yes it's a sense rom, with the "always ask me" option activated
Exactly. Yes.
That's strange.

[Solved] Do I need to uninstall/reinstall drivers? If so, how?

Hi everyone,
I'm currently trying to upgrade my phone from Yakjudv to Takju/JB. Unfortunately I've run into some issues, and as they are quite different from the questions in my original thread, I thought it best to start a new one. I do apologise if this was the wrong thing to do! I just thought that an answer to this may be helpful for others, as my searching for an answer is coming up blank.
Before I found XDA forums, I had downloaded and installed Wug's toolkit, and used it to manually install drivers for my phone. This led me to being able to find my phone's serial number when I load toolkits or run adb devices tools.
I then tried to backup my ROM using the method here: http://forum.xda-developers.com/showpost.php?p=21266325&postcount=239
Unfortunately, I got an error saying 'can't mount SD Card' (presumably because the GNex doesn't have an SD Card). Being worried about this, I thought it might be a driver based issue, so I tried to uninstall my drivers by:
1. uninstalling them from device manager (including deleting the driver software);
2. disabling downloads of drivers in windows; and
3. uninstalling all entries related to Galaxy Nexus, Google and Samsung in UDBview
I restarted, plugged my phone in, and the phone suddenly reinstalled, finding drivers on its own. It showed Galaxy Nexus and Samsung ADB device as being installed. When I tried to manually install universal drivers from here:http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 , I was told by my PC that up to date drivers were already installed.
I don't seem to be able to uninstall the drivers, no matter what I do. I have even tried to uninstall the drivers using Galaxy Nexus Toolkit (I'm trying to avoid using this, but thought it might do the job).
Is this a problem?
If so, is there anything I can do to uninstall the drivers properly?
Thank you so much in advance, everyone!
paul-g said:
Hi everyone,
I'm currently trying to upgrade my phone from Yakjudv to Takju/JB. Unfortunately I've run into some issues, and as they are quite different from the questions in my original thread, I thought it best to start a new one. I do apologise if this was the wrong thing to do! I just thought that an answer to this may be helpful for others, as my searching for an answer is coming up blank.
Before I found XDA forums, I had downloaded and installed Wug's toolkit, and used it to manually install drivers for my phone. This led me to being able to find my phone's serial number when I load toolkits or run adb devices tools.
I then tried to backup my ROM using the method here:
Unfortunately, I got an error saying 'can't mount SD Card' (presumably because the GNex doesn't have an SD Card). Being worried about this, I thought it might be a driver based issue, so I tried to uninstall my drivers by:
1. uninstalling them from device manager (including deleting the driver software);
2. disabling downloads of drivers in windows; and
3. uninstalling all entries related to Galaxy Nexus, Google and Samsung in UDBview
I restarted, plugged my phone in, and the phone suddenly reinstalled, finding drivers on its own. It showed Galaxy Nexus and Samsung ADB device as being installed. When I tried to manually install universal drivers from here: , I was told by my PC that up to date drivers were already installed.
I don't seem to be able to uninstall the drivers, no matter what I do. I have even tried to uninstall the drivers using Galaxy Nexus Toolkit (I'm trying to avoid using this, but thought it might do the job).
Is this a problem?
If so, is there anything I can do to uninstall the drivers properly?
Thank you so much in advance, everyone!
Click to expand...
Click to collapse
Drivers
cyanogenmod wiki said:
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Select "android_winusb.inf
Click to expand...
Click to collapse
Google USBDeview, and download the application. When you run the program, make sure to right click and "run as administrator". This will show you all of the drivers installed on your computer. Delete anything that says "Samsung" "Galaxy" or "Nexus". This will give you a clean slate to start with.
lowandbehold said:
Google USBDeview, and download the application. When you run the program, make sure to right click and "run as administrator". This will show you all of the drivers installed on your computer. Delete anything that says "Samsung" "Galaxy" or "Nexus". This will give you a clean slate to start with.
Click to expand...
Click to collapse
Thanks for the advice. I have tried to do this, and uninstalled all of the Google/Samsung/Galaxy/Nexus options, but the minute I plug my phone in, it all just reinstalls!
Originally Posted by cyanogenmod wiki
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Select "android_winusb.inf
Click to expand...
Click to collapse
Thanks for this. I have used it to install the drivers for when in fastboot mode, and I forced installation for the Samsung ADB Device that showed up in my Device Manager.
Do I need to do anything for the driver for the "Galaxy Nexus" device?
Thanks so much!
Paul

[Q] ADB Setup Problems with Cyanogenmod 10.1

I've been spending the better part of the day trying to resolve this problem, including poring through a good chunk of the 200+ pages of the 10.1 Nightlies thread over in development. I've been trying to set up ADB over USB with CM 10.1 however it does not register at all except as a USB mass storage device. I've tried uninstalling drivers and reinstalling them both directly from Samsung in the driver package as well as via Keis, having it auto-detect in Download mode, as well as using the modified INF drivers that have been floating around but nothing seems to work. I've tried right-clicking the four unknown Android devices in the Device Manager to install the aforementioned drivers but nothing seems to take. I've also attempted to follow the instructions at .ttp://itekblog.com/cyanogenmod-10-1-with-adb-tutorial to no avail. The most recent ADB from the SDK doesn't pull it up when listing devices either; please see the attached image.
Any help with this would be greatly appreciated.
You can use adb devices in command prompt and it should show your phone or use clockworkmod app and application for computer will work . Also easy tether pro works need the app on phone and computer as well.
Sent from my SGH-T989 using Tapatalk 2
ADB devices in the command prompt displays no devices as connected. From what I've been able to find, it seems to be a driver problem but I'm at a loss as to how to get it installed correctly. I have CM10.1 as well as TWRP installed and working fine, but I've been trying to do some application development recently and this is a major stumbling block, since if I can't get this sorted out I'll probably end up having to go back to using stock.
Edit: I have since been able to fix it. Here are the steps I followed.
1. Right click on the device in the device manager.
2. Click "Update Driver Software".
3. Click "Browse my computer for driver software".
4. Click "Let me pick from a list of drivers on my computer".
5. Select Manufacturer: Google Inc. and Model: Android ADB Interface.
6. You may receive a warning at this point. Ignore it and click yes.
7. It should be working at this point.
Stromgarde said:
ADB devices in the command prompt displays no devices as connected. From what I've been able to find, it seems to be a driver problem but I'm at a loss as to how to get it installed correctly. I have CM10.1 as well as TWRP installed and working fine, but I've been trying to do some application development recently and this is a major stumbling block, since if I can't get this sorted out I'll probably end up having to go back to using stock.
Edit: I have since been able to fix it. Here are the steps I followed.
1. Right click on the device in the device manager.
2. Click "Update Driver Software".
3. Click "Browse my computer for driver software".
4. Click "Let me pick from a list of drivers on my computer".
5. Select Manufacturer: Google Inc. and Model: Android ADB Interface.
6. You may receive a warning at this point. Ignore it and click yes.
7. It should be working at this point.
Click to expand...
Click to collapse
Is this fix also for my Xperia Mini? I'm using PAC Rom which based on CM10.1 as well and I also can't connect to my phone via ADB
My ADB is working whenever the phone is in Fastboot or Recovery but not when it is fully booted.
I can't find the developer "google inc". I guess i'll have to try some of the other steps that you have taken.
EDIT: i followed this guide even though it is for a Samsung phone and I have a HTC One X
hxxp://itekblog.com/cyanogenmod-10-1-with-adb-tutorial/

Help GNex has no OS and won't connect to a PC!

Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
stargazer127 said:
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
Click to expand...
Click to collapse
isajoo said:
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Click to expand...
Click to collapse
OK, downloaded universal naked driver 0.72, connected gnex, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, and will not allow install of of universal naked drivers, & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
KingWickedd said:
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
Click to expand...
Click to collapse
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
stargazer127 said:
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
Click to expand...
Click to collapse
You have to go to the device manager, double click on the "unknown usb..."
a dialog box may appear and then click on the 'driver' tab.
There u may find update/install driver button.
click on it and another window may open.
then select browse my computer for driver software and go to the respective folder where the drivers are.
then click next and it may install the drivers.
if you have installed the toolkit then you may find a folder in the toolkit's installation folder which has drivers in it.go through it if you want :good:

Cannot install USB drivers for Razer phone on Win10

Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Downloaded the latest driver zip from Google
Open Device Manager
Expand Portable Devices
Right-click on the Phone entry (notice, that's the entry, "Phone". Not Razer.)
Choose Update Drivers
Browse my way to the drivers folder and click Next.
Windows then returns immediately "The best drivers for your device are already installed", and shows that it's an MTP USB Device.
I noticed that under USB devices, there's an ADB Interface device listed, and I get the same results when I try to update that, too (excepting it says it's an "ADB Interface" device, of course). I have tried uninstalling both devices to get the drivers to install, but no such. I've rebooted both phone and computer as well.
On the phone, USB Debugging is turned on, and USB mode is set to MTP file transfer.
Please help!
Figured it out...
tkarakashian said:
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Click to expand...
Click to collapse
In case anyone else is seeing the same issues, I wanted to put my resolution up: I'd been trying to install the drivers with the Razer booted. On a whim, I rebooted it into Download Mode using "adb reboot bootloader". Once there, I had an Android Device listed in Device Manager. I ran the driver update wizard, and installed the "USB ADB Interface" option from the choices presented. I was then able to run the OEM unlock command and received the confirmation prompt on the Razer. Yay!
Now, since it's been so long, I've got to re-back-up everything so I can actually do this thing. LOL
Here's the PDF from Razer's how to install a factory image over PC guide. It explains how to do it all
s3.amazonaws(.)com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf (remove parantheses)

Categories

Resources