Need help can't connect with Odin because of zadig driver replacement - Galaxy S I9000 Q&A, Help & Troubleshooting

Need help can't connect with Odin because of zadig driver replacement.
I just replace driver of my Galaxy S with zadig.exe refer from wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Now, I want to connect with Odin but don't know how to rollback to sscdbus on my phone:crying:
solved: by Heimdall with darkyrom 10.2

gostyx said:
Need help can't connect with Odin because of zadig driver replacement.
I just replace driver of my Galaxy S with zadig.exe refer from wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Now, I want to connect with Odin but don't know how to rollback to sscdbus on my phone:crying:
solved: by Heimdall with darkyrom 10.2
Click to expand...
Click to collapse
You can fix this by removing the driver installed by zadig from the Control Panel.
Disconnect your device from the computer and do the following:
1. Open command prompt
2. type "set devmgr_show_nonpresent_devices=1". This will allow Device Manager to show installed devices even if they are not connected.
3. type "devmgmt.msc" . This will open up Device Manager
4. Click View > Show Hidden Devices
5. Check under libusbk or libusb0 (depending on what you did in zadig)
6. Right click and uninstall your device (if the device was in Download Mode when you replaced the driver e.g. for heimdall, then look for MSM****)
7. Close Device Manager.
Reconnect your device; Windows should automatically detect the "new" device and install proper drivers for it.

Related

[Q] Android 2.2.2 fastboot issues

I recently bought a DS7 from dell.com, it is a tmobile edition. It came with Android 2.2.2 installed. Here are the specs:
Baseband version 11.809.05.03.00
Kernel version 2.6.32.9
OEM Version GLUNB1A133633
Build Number 15420.
So in order to use my front facing camera and skype i decided to upgrade to Honeycomb 3.2. I cannot seem to get my computers (AMD64 win7pro 64 and Intel i7 win7 32) to accept the drivers in the fastboot+ADB zip file on the forum.
Basically, when the DS7 is in fastboot mode, it has the red text, followed by white text "Starting Fastboot USB download protocol". I plug in the USB cord to the computer. Computer device manager recognizes the device as "fastboot", but does not associate any drivers to the hardware. Attempts to update driver through device manager, pointing to the unziped fastboot+ADB.zip folder does not work.
Both computer do not have drivers associated with this "fastboot" hardware that pops up when i plug the DS7 in the USB port of the computers. CWmod app cannot flash CWmod recovery, i am guessing because the DS7 has 2.2.2, and not 2.2 .
I also cannot seem to find the drivers.zipfile that should be in the rootdirectory of the ds7.
Help !
Anyone with any suggestions?
Could you do the following for me?
(assumes you're on windows, which you said you are)
Go to control panel
Open up device manager
Find the device (it should be yellow icon as it needs the driver)
Open the details tab
Go to "Hardware IDs"
Post the contents of the tab
That will help me get the driver package working
1. Get device into fastboot
2. Plug it in
3. Go to device manager.
4. Right click on device -> proprties
5. Click on "Update driver"
6. Click on "Browse my Computer for software driver"
7. Click on "let me choose from a list of device drivers on my computer"
8. Click on "All devices"
9. Click on "have disk"
10. point it to the directory with your drivers
11. Press okay
12. Select "Android bootloader"
13. Win
I had the same problem
It turns out the driver was already installed. An easy way to find out is...
Start fastboot while your device is plugged in and run the command: "fastboot devices" Mine shows up as "? fastboot" if nothing shows then you know the driver is still not installed.
I don't know if that will help you any.

[Q] CDC Serial & SAMSUNG_Android drivers

where can i install CDC Serial & SAMSUNG_Android drives?
weiverpool said:
where can i install CDC Serial & SAMSUNG_Android drives?
Click to expand...
Click to collapse
You just need to install Samsung KIES dude.
i try to download kies already but kies doesn't work on my pc.(can't open the kies after installed).Is there any different version or.........
weiverpool said:
i try to download kies already but kies doesn't work on my pc.(can't open the kies after installed).Is there any different version or.........
Click to expand...
Click to collapse
Here is where I got it from http://www.samsungapps.com/about/onPc.as
If you're running Vista or Windows 7 and are unsure whether you have UAC switch on or not, right click the file you downloaded from the website and choose "Run as Administrator" from the drop down list and see if that makes a difference.
You can find the galaxy note drivers on the US Samsung site (and only this one). I unfortunately cannot post the direct link as this is my first post...
If, like me, your Galaxy Note is not recognized by your PC with a "driver not found" message, try to look in your device manager.
I had for some reason a Bluetooth device that was not correctly recognized (yellow "!"). I uninstalled the Bluetooth device (which I never used anyway) and suprisingly when I plugged my Galaxy Note back it was perfectly recognized this time.
Hope this helps!
get it from here
32bit
64bit
problem with the latest samsung kies
its all problem with the latest samsung kies. I think I was using Kies_2.3.2.12064_10_1.exe
With latest samung kies, the drivers are not getting installed properly.
Steps to correct this problem
1) Uninstall samsung kies
2) Reboot system
3) Install an old version of kies - I used Kies_2.1.1.11124_17_6
4) Connect your S2
5) Old kies will install the drivers properly for your s2
6) Now with the mobile connected, update kies from kies itself.
All works after that.
usb cdc mod hatası
*#0808# tuşuna bas ac ap mtp atp kaydet sn makina bukadar da arıza yap
path for driver installation
after installation, samsung_android drivers window opens .
now guide me to select the correct path which will install drivers correctly.
kindly do reply asap
patel_gsm82 said:
after installation, samsung_android drivers window opens .
now guide me to select the correct path which will install drivers correctly.
kindly do reply asap
Click to expand...
Click to collapse
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows

WORKAROUND: Captivate adb over USB on Glitch v14 + AOKP m6

I'm running AOKP m6 with the default Glitch kernel v14. The problem I'm was having is no adb over USB.
My PC is running Windows 7 64-bit.
The problem lies in the device showing in Device Manager as "SGH-I897" instead of one of the more common identifiers (which obviously were used by other kernels and/or ROMs as other ones worked fine).
NOTE: unless you NEED adb over USB for something, it will probably just be easier for you to use adb over WIFI. The following isn't super-hard but if adb over WIFI works for you ... use it.
What I attempted to do to fix before doing the workaround (add "tested adb: FAIL" to each step below) ... try these, they may work in your case:
Updated to latest Android SDK, rebooted
"Uninstalled" device in Windows
Tried to "Update Driver Software" using Android SDK USB driver ... error: "Windows could not find driver software for your device"
Tried to "Update Driver Software" using Samsung Kies USB driver ... same error.
(over WIFI adb) ran `setprop persist.sys.usb.config mass_storage,adb` ... no luck, Mass Storage worked before and after, no adb
WORKAROUND:
Summary: you need to add your device string to the USB driver INF file. The following ATTEMPTS to be a full step-by-step to show those who haven't done this before what to do.
Go to your android-sdk folder (assuming you have installed the SDK -and- included the USB drivers ... if not ... that's your first step)
Open %ANDROID-SDK%\usb_driver\android_winusb.inf in your favorite text editor
add the following lines to BOTH sections [Google.NTx86] and [Google.NTamd64]
;Samsung Captivate with Glitch kernel
SGH-I897 = USB_Install, USB\VID_18D1&PID_4E22&REV_0231&MI_01
For OTHER phones with this same problem (skip if you are using a Captivate)
NOTE: For other phones or other ROMs ... try the steps I outline at the end of this post to see if they work BEFORE you hack the driver file. You may not have the same problem I've had here.
You will need to change the lines you add to the file above. To find the right string to add to your inf file:
find your Android device in Device Manager, it SHOULD have a yellow "disabled" triangle icon and is probably under "Other Devices".
right-click the entry for your phone and select "Properties"
go to the "Details" tab
change the "Property" from "Device Description" to "Hardware Ids"
right-click and "Copy" the first entry (should look similar to USB\VID_18D1&PID_4E22&REV_0231&MI_01)
Replace USB\VID_18D1&PID_4E22&REV_0231&MI_01 from my lines above with the value you copied in the previous step
Replace ;Samsung Captivate with Glitch kernel in my lines above with something that describes your device. KEEP the semi-colon at the front of the line.
find your Android device in Device Manager
right-click it and select "Uninstall"
(IF your computer tells you to reboot at this point ... yeah ... you gotta ... so just come back here when done and make sure you've done the "Uninstall" step)
in Device Manager, do "Action" > "Scan"
find your Android device again, this time likely under "Other devices"
right-click the device in Device Manager and select "Update Driver Software"
"Browse my computer for driver software"
click the "Browse" button and find %ANDROID-SDK%\usb_driver\
click "Next"
if it tells you it can't find a driver for your device, SOMETHING above went wrong OR this workaround can't solve your problem
if it tells you "Windows can't verify the publisher of this software" ... select ... "Install this driver software anyway"
you're basically done. Verify it worked by trying the command `adb devices`. Your device should now appear.
NOTES:
If you have this problem, both Recovery mode and normal mode will be unable to connect adb via USB
adb works over WiFi, but I have some scripts that are expecting a USB connection and don't behave well without USB connection for sensing when the device has rebooted
I had adb over USB running on the same phone using Doc's ICS, Stock 2.2 and Stock 2.3
adb recovery mode on my phone works with Corn kernel, so I really think this is an issue with Glitch kernel rather than AOKP

[DRIVERS] Nexus 4 Driver for Windows

If you have windows, you will need these drivers to use ADB or Fastboot with your Nexus 4. The long method of getting this is downloading the SDK and running it. I have extracted the drivers and put it into a rar file for easy use.
Follow these steps if you haven't plugged your phone into your computer before.
1. Download the file.
2. Extra the files into a folder.
3. Plug your phone in.
4. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
5. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
If you already installed other drivers and they don't work for you. Download the drivers below and follow these steps:
1. Enable USB Debugging on your phone.
2. Plug your phone into your computer.
3. Go to Device Manager on your computer and locate your device. It will either be under "Android Devices" or "Other Devices" depending whether drivers have been installed or not.
4. Right click on your phone and select "Uninstall."
5. In the box that appears, check the option to "Delete the driver software for this device" then proceed.
6. When that is done, go back to Device Manager and refresh.
7. Locate your phone and right click to select "Update Driver Software."
8. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
9. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
10. Unplug your phone and restart your computer.
11. Plug it back in and everything should work.
Download link:
http://www.mediafire.com/?8xb50uktar8096i
Thanks to efrant for clarifying exactly how to manually select your drivers.
I would suggest everyone download Android SDK.
You have a Nexus device right?
http://developer.android.com/sdk/index.html
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
ijip said:
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
This thread is for Nexus 4 drivers, not the SDK.
Ask your question in the Q&A section.
theexel said:
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
Click to expand...
Click to collapse
Yep, I never needed the whole SDK before. I only download the platform tools too.
Have any other ADB drivers installed? Because then you need to uninstall those:
Go into command prompt and write:
set devmgr_show_nonpresent_devices=1
start devmgmt.msc
Delete all devices including driver software in the "Android Device" section.
Then reinstall the Nexus 4 drivers.
If that still doesn't work, update the driver when connected with usb debugging on and manually add by rightclicking the device, click update driver software, then the "Browse my computer for driver software", then "Let me pick from a list..." then "Show all devices" and then Have disk.
Then you simply point to the driver and select the "Android ADB Interface" (Or something like that) it also has driver for bootloader and composite, bootloader is for fastboot, can't remember what composite is for, but you shouldn't use those.
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
qvert said:
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
Click to expand...
Click to collapse
Go to Device Manager on your PC. If debug mode is enabled, you should see your device listed as an Android phone or something of the sort. If it has a yellow exclamation mark or some sort of symbol next to it, then that means the drivers aren't properly installed. Assuming that is the case, follow FISKER_Q's directions:
Right clicking the device, click update driver software, then the "Browse my computer for driver software." Select the usb_driver folder that you extracted and you should be good to go.
Subbed to refer to later when i have the N4
Sent from my Nexus S
jark99 said:
Subbed to refer to later when i have the N4
Sent from my Nexus S
Click to expand...
Click to collapse
This thread is also in the Misc section of the reference guide in case you can't find it later
I did the same thing and I cant get adb to see my device however fastboot will =/
Shambala001 said:
I did the same thing and I cant get adb to see my device however fastboot will =/
Click to expand...
Click to collapse
Did you enable debugging on your phone yet?
If not, go to Settings > About phone, then tap on "Build Number" 7 times. Go back to settings and you will see developer options. Go in there to enable USB debugging.
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Nitemare3219 said:
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Click to expand...
Click to collapse
Glad you got it figured out. :good:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Try leaving the phone plug in. Go to Device Manager. Find the ADB drivers and uninstall it. While in Device Manager, have it scan for new changes. You should see your phone appear. Right click it and manually install the drivers.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
IAMLordspeed said:
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
Click to expand...
Click to collapse
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Stryder5 said:
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Click to expand...
Click to collapse
I had to put a check in the box next to "Delete the driver software for this device" to get this to work. Otherwise Device Manager will keep detecting the old drivers.

[Q] No matter what I try, I am unable to flash to the new bootloader!!!

I have been trying for don't know how long but am just unable to flash the new bootloader. I have tried the AIO tool kit but with the latest drivers installed, usb debugging enabled but it keeps saying no connection found. I have also tried nvflash method but still not able to work my way around it. currently i am on pa rom but really want to get the ICS rom. I really need some help....
Thank you in advance
Yeah I had the same problem fe(w days ago . i have bricked my device totally then i will suggest you flash it through NV flash mathod and yeah ,make sure you have all drivers (device ) the most imp driver is 'APX DRIVER " Download it and install it ..on your system or laptop , remove battery of your device .. press + and - together and plug in usb . a popup and sound will be appear on our computer . thats it now you can flash your device through NV flash ..Happy flashing .. HIT THANKS IF I M HELPFUL and for more queries message me here :laugh:[/B][/B][/I]
APX drivers are included in AIO tool
maddyrokieasta said:
Yeah I had the same problem fe(w days ago . i have bricked my device totally then i will suggest you flash it through NV flash mathod and yeah ,make sure you have all drivers (device ) the most imp driver is 'APX DRIVER " Download it and install it ..on your system or laptop , remove battery of your device .. press + and - together and plug in usb . a popup and sound will be appear on our computer . thats it now you can flash your device through NV flash ..Happy flashing .. HIT THANKS IF I M HELPFUL and for more queries message me here :laugh:[/B][/B][/I]
Click to expand...
Click to collapse
agree (see below)
I - Install APX (NVFlash Recovery) Drivers if not already installed. It starts a device driver wizard to help you install the drivers needed for NVFlash. It detects your system OS and gives on-screen instructions if running Windows 8. FYI the drivers are located under ToolKitFiles\nvflash\driver folder.
Click to expand...
Click to collapse
- via http://forum.xda-developers.com/showpost.php?p=34809475&postcount=1
Prepare Phone
-Power down phone
-Remove battery
-Hold VOL_DWN+VOL_UP & plug in USB connection from computer (note, your phone will not visibly respond but it will boot to APX mode quickly)
-Open Device Manager in Windows and you should see "APX Device" listed with an error, or not if you have used NVFlash before
-Right click on the APX device
-Select 'Update driver software'
-Select 'Browse my computer...'
-Select 'Let me pick...'
-Select 'Have disk'
-Browse to directory you extracted the *driver* software to above (It's included in Stefan's zip)
-Select 'NVIDIA USB Boot-recovery driver for mobile devices'
-Accept any warnings, including the big red alert (you may need to disable UAC)
-Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot, rinse and repeat
Install the rom:
- Go to the folder where you unpacked Stefans rom
- Run Windows installer and follow instructions on screen, should be peace of cake for everyone!
- DONE
I think you should try either updating your drivers for the phone and if that doesn't work, try an older version then.

Categories

Resources