Hey, I have a Samsung Galaxy S 2, flashed with clockwork mod and Cyanogen 7 (nightly 27/9/11)
On the mod from the 26th, I experienced the 2G/3G switch's unhandled circumstance and com.android.phone got caught in an endless loop.
When I plugged my phone in, and tried to use ADB to install sqlite3 and fix the problem, my device wasn't listed.
I've tried reinstalling samsung drivers, and using kies, and I've tried to find an ADB driver for the phone, but to no avail.
It's annoying the hell out of me, as this is my only phone, and for a day and a half now I have had no means to receive calls.
Does anyone have any ideas on how to fix this?
I'd like to continue using cwm and cyanogen, if possible.
From the Cyanogen thread:
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you installed the SDK
That are the drivers that you need.
Related
Attempting to update new Vibrant (Galaxy S) using "Unleash the beast v0.1" - post reboot my XP machine is asking for a "Gadget Serial" driver. I've been looking around for such a beast but not having much success. The phone is displaying a lovely "Do not turn off target!!" error too. Makes me a tad nervous.
Suggestions?
[Solution]
FWIW: This can be fixed by downloading "PC Studio" from Samsung. (This board isn't letting me post the link but you can search on the Samsung main site).
I tried installing that pc studio. Did not work. I have windows vista-64 bit.
Same problem
Hi I'm new in this forum and new to Android also.
I'm having the exact same problem, when I'm trying to flash my phone (AT&T Captivate) back to stock using Odin3 One-Click Downloader my PC is asking me for a Gadget Serial Driver.
I already install ( a few times ) the Phone drivers downloaded from the Samsung site and my PC recognize my phone with no issues. My problem is when I'm in Download mode.
I have a Samsung Captivate rooted with 2.1 update 1 (JH7)
MY PC is running Windows XP Professional Service Pack 3
I will try the PC Studio from Samsung
Problem solved
Problem solved after installing the Samsung PC Studio. Thanks
It did not fix my problem. Is there another fix? Device manager even says that it is "other device" no drivers.
Try installing Keis mini. i had the same problem and that fixed it.
samsung.com/us/support/downloads/SGH-I897ZKAATT
WTF are Samsung up to? Seriously?
I have a Galaxy S2 and i'm stuck on this Gadget driver issue. So I googled, found this thread and started looking. I've now found:
Kies Lite (Samsung site)
Kies 2.0 (Samsung site)
PC Studio 7.blah.blah... (Some driver download site)
PC Studio 3.blah (Samsung site)
NEW PC Studio 1.blah (Samsung site)
Talk about f*&king confused!
Oh and Kies 2.0 never finishes installing, I suspect its in a look as it sticks on "Evaulating Launch Conditions"...
WTF?
Anyone ANY clues on WHICH is the correct software AND version?
please anybody help us
I tried all of the above but nothing working. I tried on 2 different computers. one with
win7 64bit the other with winxp. both had the same problem. the stupid gadget serial
driver.
Try updating your Samsung drivers to the most recent ones:
http://forum.xda-developers.com/showthread.php?p=11633550#post11633550
I totally got it to work for my Galaxy SII
I remember putting my phone into some sort of usb tethering in the setting
so I just unchecked it and the drivers installed themselves
Settings> Wireless And Network > USB Utilities
and just push the connect to PC button and when you put your phone into Download mode the download wizard should install the drivers
Just so you wont switch..
From July 2012 Kies version
7HUND3R said:
Here it is: version 1.5.6.0 of the samsung usb drivers just extracted from latest updated kies
http://www.mediafire.com/?5fy7vwxhrhrpiwj
Click to expand...
Click to collapse
Pierrick
Gadget Serial
None of that worked for me. Doing the following worked for me. Basically you have to tell your pc what kind of driver this "Gadget Serial" is.
Goto "Device Manager".
Find the "Gadget Serial" device.
Right click and choose select update driver.
select "browse my computer for drivers" and then choose "Let me pick the drivers to install".
zachol said:
Try updating your Samsung drivers to the most recent ones:
http://forum.xda-developers.com/showthread.php?p=11633550#post11633550
Click to expand...
Click to collapse
Thanks so much . This fixed my issue on Win8 x64 with Hemdal and Epic 4g
micromax a71
micromax a71 driver gadget serial error how to solve
I want to flash my Q mobile i6 metal one but when I connect to computer and it has yellow icon too and it not working.... do I flash if gadget serial drive not work properly ??? How to flash Qmobile i6 metal one
I installed latest version of Kies in my Windows 7 Professional 64bits (UAC disabled, install was "ran as admin")
In the end of the installation process, Windows shows a balloon saying it is installing the driver for the device (note that there is no phone connected to the computer at that moment), but it fails saying that it could not find the driver for the device.
After installation finishes, I can connect the phone, open and use Kies normally, but if I go to Windows device manager, in the "Other devices" branch, it still lists an "Unknown device".
Any idea about how to solve this? I already searched the forum, but could not find anything that worked for me.
Thanks!
PS: I'm using the original USB cable from Samsung.
As long as you are able to connect and work via Kies just leave it. Just check how many people are having problem with Kies, you should consider yourself lucky that you don't have a connection problem
Regards.
Leave your phone plugged in and do a windows update. It should find the missing drivers.
You can find the drivers inside the dir where kies was installed, alternatively a copy is stored on my 4shared, link in my sig.
You can try installing the drivers and see if that helps.
Kies is a huge PITA, you may need to swap USB port and uninstall/reinstal for it to get its act together.
Thanks all who answered.
Unfortunately, Windows Update can't find any driver (already had tried that), and also asking to update the driver and setting it to search in the Kies driver directory has no effect either.
I'm trying to run Revolutionary to gain root, but running into some driver issues. I've never had a problem connecting as a disk drive and transferring files from PC to TB or vis versa, so I haven't encountered this yet. But when I run Revolutionary I get stuck at "Identifying Device" (or finding, or whatever it says first). Uninstalled HTC Sync, uninstalled and reinstalled drivers. Installation process says everything goes along fine, but when I look in Device Manager I have an /!\ with this error message:
"Windows was able to successfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is 37."
Tried 2 different cables, 3 different ports (could they all suck?) Shows up in "My Computer" as CD Drive (K Verizon Wireless.
Running Windows Vista
Searched around a bit and saw some similar problems but under different circumstances and with solutions that didn't seem to apply. Anybody seen this? Know how to get it going?
Also, I'll run into the same problems trying to root through ADB, correct?
May have some corruption issue.
From the command prompt (on your PC), try running this:
sfc /scannow
Let it run then reboot and see if it fixes anything.
Good Luck
Nope....
Tried that, said there were some errors that were fixed (surprisingly vague about what), rebooted, but same problem. Any other ideas?
Unplug device.
Uninstall all drivers related to the device and reboot the computer.
Install the newest driver package from the HTC website (sync not required). *Optionally, you can just update your current driver using the inf located in step 12 here instead of the driver package from HTC.*
Reboot if prompted.
Turn on USB Debugging in settings->applications->development.
Plug phone in.
Try again.
I'm sorry if this is a bad post, I'm new to these forums. I used the viperMod tool to install CWM, rebooted, and I now get the 1a brick error described the the developers section. However when I try to fix it using adb (which I have installed correctly), it doesn't work.
To be specific, my computer (running windows) doesn't recognize that I've hooked it up in devices. I do an adb devices and get "List of devices attached" and nothing shows up. Each time I plug in the prime, I get the usual beep that windows recognizes it is attached, however it does 3 real quick beeps and then nothing happens. I think if I could get it hooked up properly the fix described in the developers section would work, but for some reason my computer doesn't like it.
Any suggestions and/or help would be greatly appreciated!
This might sound a little silly but have you installed the drivers?
If you have the drivers installed windows should detect the device correctly and you'll be able to use adb. There is a link to universal drivers in the dev section, or you can get ASUS' from their support website.
I had the drivers installed properly prior to the CWM installation. However, the 3-tone beep does indicate that the drivers are not installed. Unfortunately the prime isn't showing up in device manager at all, so I need to figure out how to re-install the drivers and see what happens from there. Is it possible to install drivers for a device that doesn't show up in device manager?
Ok, so I can't install the drivers for the device. The only thing device that pops up in device manager is "Full Android on Emulator" in "Other devices". I try to install drivers for it, and it does not like either the universal drivers or the drivers from ASUS.
Why would windows not recognize it as an android device like before? I haven't touched the drivers which I had installed and previously worked. I feel like the only thing stopping me from unbricking the device is a connection issue. Any suggestions?
Well, here was my fix in case someone else had this problem:
In device manager under "Other Devices", I selected "Full Android on Emulator". I selected to install drivers, and browse to drivers. Now where the stock ASUS drivers would not work, the universal driver posted in the dev section worked, although it thought the device was some samsung phone.
It turns out that was OK. I followed the unbrick instructions from 1a in the dev section and all is well.
I appreciate the geniuses who post all these fixes and mods. Great work!
Hello, im trying to get rid of the stock, heavy and crappy ROM from SONY and install a lightweight ROM with 4.0 or higher.
Im stuck at the very first steps though..
Installed JAVA SDK + Android SDK plus the Google Drivers. I downloaded a newer USB driver linked in a thread in XDA.
I connect the phone using the MENU button and the driver installation begins, BUT the driver fails to install.
In Windows8 Device Manager, i can see the S1Boot Fastboot device marked with an exclamation mark. Trying to update the driver manually, selecting the driver that i replaced the older one, in the android SDK/extras/google/usb (or something) gives me an error of incompatible devices and fails.
Any help please?
BLiapis said:
Hello, im trying to get rid of the stock, heavy and crappy ROM from SONY and install a lightweight ROM with 4.0 or higher.
Im stuck at the very first steps though..
Installed JAVA SDK + Android SDK plus the Google Drivers. I downloaded a newer USB driver linked in a thread in XDA.
I connect the phone using the MENU button and the driver installation begins, BUT the driver fails to install.
In Windows8 Device Manager, i can see the S1Boot Fastboot device marked with an exclamation mark. Trying to update the driver manually, selecting the driver that i replaced the older one, in the android SDK/extras/google/usb (or something) gives me an error of incompatible devices and fails.
Any help please?
Click to expand...
Click to collapse
I guess Google will help you better here bro.. Because your problem you know better.. Its difficult to find the reason behind the failure of driver installation.. There can be infinite number of reasons.. You cannot predict.. Search the error you are getting.. You will find your answer..
Sent from my MT11i using xda premium