twrp/cwm usb drivers failing to install - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

cant get windows to find USB driver for cwm/trwp... missing drivers or something tried most common dl links, vmware to isolate. i337m latest trwp openrecovery-twrp-2.6.3.1-jfltecan/GalaxyS4-CWM-6.0.4.4-Canada. ive also tried forcefully installing from the latest samsung/adb cab/exe and windows wont recognize the manual install either.
used these so far
http://forum.xda-developers.com/showpost.php?p=11498043&postcount=1&nocache=1&z=8984906396242748
neither after extracting files can manual install the required drivers, not sure what the ****ing hell is wrong. its not a windows thing its a matter of the infs are lacking the hwids or im just installing the wrong things here.
win 7 x64.

Related

[Request] Recovery/Cyanogen/adb

Hi,
I have been messing with this for a few weeks now.
I have a magic 32B, spl 0004
I don't know how but i got cyanogenmod 4.2.5 on my phone.
But then i tried to use the update app and it fails.
It seems that there are 2 problems.
1. my recovery is still the stock one
2. i just cant seem to get a good connection with my computer.
Every time i try something its waiting for device.
Or with adb devices its an empty list.
i used a windows vista machine and a windows 7 machine
Is there someone who is willing to help me get this done?
I checked threads about, usb drivers, installing adb, installing recovery.img, installing cyanogen.
But there is always a step that just doesn't go according to the manuals.
i was about to give up, but i just really want this to work.
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
justbenjp said:
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
Click to expand...
Click to collapse
I have tried to install a custom recovery, but when i follow the steps i cant seem to connect to my phone via CMD.
When i check the drivers.. i'm not sure its 100% correct.
I have installed the once before.
and now he doesn't ask me for the drivers anymore.
but neither do i see it in the devicemanager, the way its being described in the manuals.
just something else involving android, but not ADB
i have tried to follow the manual, and threats about how to get the driver right..
but with this, i also have had problems with the steps..
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
justbenjp said:
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
Click to expand...
Click to collapse
I have done this..
I will try again on a vista machine which i havent used for this yet
anheuer said:
I have done this..
I will try again on a vista machine which i havent used for this yet
Click to expand...
Click to collapse
Great.. it would not install the SDK..
So back on my windows 7 machine..
still getting device not found in CMD - adb devices
connected with usb debugging on..
cant see anything in device manager, but the system also doesnt ask for drivers...
I went into fastboot and then it asked me for drivers..
Now i do have
Android phone - Android Bootloader interface
but in any other situation, it does not show anything or ask anything.
I just keep getting device not found...

having trouble with usb drivers

so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.

Nexus 7, Not recognized, cant transfer files, Please help!

hi,
im in need of help, i just bought my nexus 7, within the first hour of course i wanted to unlock, root and flash CWM on it, this is what happened, i downloaded the files necessary, went on cmd on my computer and fallowed some simple directions and i unlocked it, the problem started when i couldnt copy and paste the CWM file onto my nexus 7 it just wouldnt copy, so i went to do install the drivers for my nexus 7 on device manager, and my computer sees my nexus 7 as my previous tablet samsung tab 2, now after trying to make it work, my computer wont recognize the device at all,
so im trying to get it back to stock, factory rom when everything was working okay, because i think i somehow renamed the device as my old tablet samsung tab 2, im suprised as it still works fine, however i cant transfer files over, and i cant root because the toolkit program on my computer wont recognize the nexus 7, if there is a simple method to fix this problem or bring my nexus 7 to the way i bought it please do tell, it will be highly appreciated,
Thanx
It sounds like the drivers got messed up.
Get http://forum.xda-developers.com/showthread.php?t=1766475
it includes a tool & instructions for fixing the drivers under the "full driver installation guide".
You can also download a stock image here https://developers.google.com/android/nexus/images#nakasi
I think uninstalling the previous drivers with USBDview (step 1 in the full driver installation guide) will help.
Note that while it says "guide" it includes buttons for launching included programs and scripts.
Use Wugs toolkit, click on the big button to install drivers manually/automatic I think is how it's labeled.
One of the first step offers a tool to view and delete drivers and it even specifically tells you which drivers to delete to prevent it being misrecognized and/or having conflicts.
Once you've uninstalled those just follow the instructions to install the correct ones. Once they're uninstalled you will see it in device manager as something else until you install the new drivers.
Sent from my ADR6425LVW using xda premium

Help nexus

Hi I'm new here,
I'm trying to root my phone, I installed android sdk to my c drive
I cant seem to install the correct the drivers, i have uninstalled my current ones and now i cant seem to install the right one. i have tried the universal naked driver. no luck there
I am using windows 7 .
please help
Just open the sdk.exe in the adt folder and select drivers from there
You just need fastboot, naked drivers, superuser, and custom recovery too root. I don't recall needing anything else to get root.
Or you can try this driver here. Driver.

[Odin issue] N4 not being picked up on Windows 8.1

Howdy,
My question is, does Odin not work with Windows 8.1 in general? If you have managed to get Odin to register that a device has been connected was there any special way you managed to get around this?
Some background:
I mentioned this issue in the noob friendly section but it seems I am the only one having the issue there. So I'm asking around here if anyone has had this issue under Windows 8.1. All I wish to do is flash the unbranded firmware to remove carrier bloat-ware.
I've downloaded Odin 9.07/9/10 and have the same result, that the device just does not appear.
System is running Win8.1 and has driver signature disabled.
Kies is installed and picks up the device without error
Phone has USB debugging on and appears under 'Device Manager' when in Download mode.
I've had a look around and found nothing with this issue, watched folks do it in various videos too but they were using Win7.
Thanks for reading!
Ste_JDM said:
Howdy,
My question is, does Odin not work with Windows 8.1 in general? If you have managed to get Odin to register that a device has been connected was there any special way you managed to get around this?
Some background:
I mentioned this issue in the noob friendly section but it seems I am the only one having the issue there. So I'm asking around here if anyone has had this issue under Windows 8.1. All I wish to do is flash the unbranded firmware to remove carrier bloat-ware.
I've downloaded Odin 9.07/9/10 and have the same result, that the device just does not appear.
System is running Win8.1 and has driver signature disabled.
Kies is installed and picks up the device without error
Phone has USB debugging on and appears under 'Device Manager' when in Download mode.
I've had a look around and found nothing with this issue, watched folks do it in various videos too but they were using Win7.
Thanks for reading!
Click to expand...
Click to collapse
My guess is that you need to install Samsung's USB drivers for your device. Have a look at the instructions at this, and this page. I suspect that you haven't installed SAMSUNG's Android ADB Interface Driver (look at OP of the second thread), which is used by Odin if I'm not mistaken to talk to your phone and push the images you want via ADB.
Install the Samsung usb drivers!
Odin works fine on my windows 8.1 computer.
ernani said:
My guess is that you need to install Samsung's USB drivers for your device. Have a look at the instructions at this, and this page. I suspect that you haven't installed SAMSUNG's Android ADB Interface Driver (look at OP of the second thread), which is used by Odin if I'm not mistaken to talk to your phone and push the images you want via ADB.
Click to expand...
Click to collapse
That was it. Thanks so much! I removed Kies, rebooted, installed the driver from samsung and rebooted again, after that Odin worked like a charm.

Categories

Resources