Database Info

[Kies] Crash on Win 7 x64 - Virtual PC work-around

So I had the dreaded Win 7 x64 crash. I uninstalled IE 9. No go. Used that DLL fix (which I can't remember where I found it). Still crashed. So here's how I got around the problem.
Note:
I'm just sharing what I found since none of the solutions I googled up worked for me (maybe I'm the only one). For those who wonder why anyone would bother with stock Froyo, I'm sure there are reasons. I just wanted to do some testing of the upgrade exactly as it came from Samsung. There's probably an Odin flashable package somewhere which may be bit-for-bit identical, but I didn't bother looking. I'm hoping this will work if another update comes down the pike (Ha!) and Kies is still broken.
Here's what worked for me. It may brick your phone so understand that before you start.
Step 1:
Load up Virtual PC.
In Virtual PC:
Install the Samsung drivers
Install Kies Mini
Install Samsung PC Studio (for Gadget Serial driver)
Step 2 - back to the phone:
Flash stock. I flashed one-click JF6, but use the right stock firmware for your phone (build 1010 and later phones should use something like this)
Step 3:
At this point you may want to make sure the Gadget Serial driver is loaded and working (if you one-click flashed JF6 skip to step 4), so put the phone into download mode and plug it into the PC.
In Virtual PC:
USB Menu->Gadget Serial Attach
Insure that driver is working. If it isn't then the update won't work because Kies Mini will not be able to communicate with the phone after it goes into download mode. If it works then skip to step 5. If not then do step 4.
Step 4:
Have CWM update.zip on you sdcard root directory
Reinstall packages
Reinstall packages again
Install zip from sdcard
Install sbl_CWM_update.zip (attached to this post)
Do the step 3 check. If that fails then the Gadget Serial driver isn't recognizing you phone and this isn't going to work unless you can fix it.
Step 5:
Reboot the phone, turn on USB debugging then plug it in to the PC.
In Virtual PC:
Start Kies Mini
USB->Samsung_Android Attach
Start the upgrade
Wait 12 years or so until the phone goes into download mode
USB->Gadget Serial Attach
The install should continue automatically. If it doesn't there is an upgrade button which should be enabled when driver is loaded and the phone is detected.
Wait for the install to finish, at which point to phone should boot into Froyo.
Done.

thanks
cool, i had tried all of the other ways of forcing kies to recognize my computer... but it always ended with the same crash, nice little white box where the program should be. so im trying this out but its taking forever to get xp virtual machine up and running. i will post again with my final results

ok now for my story
i have had flashed multiple versions of cognition on my phone and have become very familiar with the process. i do love cog 3.04 but the problem is that the swype that is loaded on the rom is a 60 day trial version and it ran out. so i wanted to try out the stock froyo and see what improvents i wanted so i could cook my own rom.
i went and got kies mini on the release date for froyo and it was crashing everytime i used it, giving me this lovely white box on my windows 7 x64 ultimate computer. i tried multiple work arounds and have never thought of virtual machine so thank you for that.
i want and ran my odin one click reflashed to jf6, then decided to see if kies recognized my phone. it imediately was recognized and started to update in the virtual machine.
it is currently downloading to my phone and i will repost again if my phone either becomes soft bricked or if the update goes through

Please help me find the Gadget Serial Driver for My Samsung Vibrant
I've been trying to Update my Samsung Vibrant from version KA2 to version KB5 using Samsung Kies mini to no avail. I am running Windows XP SP3.
I know, this is a developer site but I have a feeling I won't be able to develop at all because I when I try to update to (Official) Froyo (Provided through Kies mini), I get stuck in download mode with the yellow sign forever. Luckily I can restore by taking the battery out and rebooting my phone. This is problem is due to not having a Gadget Serial Driver installed. Now note, I have all the other USB drivers installed properly. They all show up in Device Manager, however the darn Gadget Serial Driver is MIA and Windows only notices that is missing the driver when the phone enters Download Mode. I have searched xda developers for this issue and I have seen a number of posts where other people have had the same issue and maybe a couple of people solved it by installing PC Studio. I have Googled up and down the internet, went to Samsung's website and even spoke to a Samsung Representative for a link to Samsung PC Studio. However all of the links I found were either dead, contained fake software or were just shady.
Samsung's site no longer contains an actual download link to PC Studio or New PC Studio (I don't know the difference). Can someone please help me get this Gadget Serial Driver or the PC Studio software which may solve this driver issue? Please don't point me to any "Samsung USB Drivers For Mobile Phones" links because I've downloaded that driver and it has solved nothing. Thanks in advance and sorry for sounding like a complete n00b.

privetKalla said:
I've been trying to Update my Samsung Vibrant from version KA2 to version KB5 using Samsung Kies mini to no avail. I am running Windows XP SP3.
I know, this is a developer site but I have a feeling I won't be able to develop at all because I when I try to update to (Official) Froyo (Provided through Kies mini), I get stuck in download mode with the yellow sign forever. Luckily I can restore by taking the battery out and rebooting my phone. This is problem is due to not having a Gadget Serial Driver installed. Now note, I have all the other USB drivers installed properly. They all show up in Device Manager, however the darn Gadget Serial Driver is MIA and Windows only notices that is missing the driver when the phone enters Download Mode. I have searched xda developers for this issue and I have seen a number of posts where other people have had the same issue and maybe a couple of people solved it by installing PC Studio. I have Googled up and down the internet, went to Samsung's website and even spoke to a Samsung Representative for a link to Samsung PC Studio. However all of the links I found were either dead, contained fake software or were just shady.
Samsung's site no longer contains an actual download link to PC Studio or New PC Studio (I don't know the difference). Can someone please help me get this Gadget Serial Driver or the PC Studio software which may solve this driver issue? Please don't point me to any "Samsung USB Drivers For Mobile Phones" links because I've downloaded that driver and it has solved nothing. Thanks in advance and sorry for sounding like a complete n00b.
Click to expand...
Click to collapse
This is for the flight II but the software has the PC Studio download. Good Luck!
http://www.samsung.com/us/support/downloads/SGH-A927ZAAATT

privetKalla said:
I've been trying to Update my Samsung Vibrant from version KA2 to version KB5 using Samsung Kies mini to no avail. I am running Windows XP SP3.
I know, this is a developer site but I have a feeling I won't be able to develop at all because I when I try to update to (Official) Froyo (Provided through Kies mini), I get stuck in download mode with the yellow sign forever.
Click to expand...
Click to collapse
Thanks man. That made my day. I needed that.

You can also get the Heimdall suite and open the drivers folder and run Zandig. Then connect your phone in download mode it should show gadget serial in the device window click install and it should complete and you're good to go, this is how I did it after 3 days trying to get my phone to stop showing the device malfunction error which is due to another problem on my main xp machine, a sony which I can't get usb 2.0 drivers for from sony or anywhere else to work correctly even though all 8 ports are 2.0 according to support, my manual, and previous xp install and that's after installing xp 4 times to get the graphics driver to install right so I could then install the right ati driver which everyone online with this model sony seems to have to do, but back on topic. I hopped on my windows server 2k3 machine which had correctly working usb 2.0 drivers ran zandig with my cappy in dl mode and BAM finally working gadget serial driver, just make sure you have zandig.exe open, and connect your phone in DL mode or you'll just install the equivalent of the standard samsung drivers which you prolly already have, I haven't been able to test this on a win7 machine but from what I've read the heimdall driver should work on them and worked great on both xp and server 2k3 on my home server machine.
Sent from my SAMSUNG-SGH-I897 using XDA App

Jsmokey said:
You can also get the Heimdall suite and open the drivers folder and run Zandig. Then connect your phone in download mode it should show gadget serial in the device window click install and it should complete and you're good to go, this is how I did it after 3 days trying to get my phone to stop showing the device malfunction error which is due to another problem on my main xp machine, a sony which I can't get usb 2.0 drivers for from sony or anywhere else to work correctly even though all 8 ports are 2.0 according to support, my manual, and previous xp install and that's after installing xp 4 times to get the graphics driver to install right so I could then install the right ati driver which everyone online with this model sony seems to have to do, but back on topic. I hopped on my windows server 2k3 machine which had correctly working usb 2.0 drivers ran zandig with my cappy in dl mode and BAM finally working gadget serial driver, just make sure you have zandig.exe open, and connect your phone in DL mode or you'll just install the equivalent of the standard samsung drivers which you prolly already have, I haven't been able to test this on a win7 machine but from what I've read the heimdall driver should work on them and worked great on both xp and server 2k3 on my home server machine.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Best first post I've seen in quite some time. Thanks for that.

boborone said:
Best first post I've seen in quite some time. Thanks for that.
Click to expand...
Click to collapse
Thanks I appreciate that I just wanna give back as much as I've received from the forums here its a great place to start. If anyone runs into any problem with this let me know and I'll see if I can reproduce and come up with something.
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] HTC Desire S and Windows 8

Hi all,
I am trying to upgrade my HTC Desire S to Android 4.0 via the official ICS update from HTC. However, I cannot get my laptop (Windows 8) to interact with my phone.
If I mount the SD card then I can view the contents but HTC sync won't find the phone and in 'Device Manager' the phone is labelled as "Android Phone" with the yellow warning triangle next to it. I have tried to download drivers but can't seem to get them working. Whether that is my fault or the laptops fault I am unsure.
Any help would be greatly appreciated!
Thanks,
benandrews54

Search for Windows 8 drivers in the main Android Development thread of XDA. I would have give you a link but it is hard via Tapatalk. I have 2 Windows 8 machines and it works perfect on both of them
Sent from my HTC Desire S

Cheers, I'll have a look now and let you know if it works or not.

benandrews54 said:
Hi all,
I am trying to upgrade my HTC Desire S to Android 4.0 via the official ICS update from HTC. However, I cannot get my laptop (Windows 8) to interact with my phone.
If I mount the SD card then I can view the contents but HTC sync won't find the phone and in 'Device Manager' the phone is labelled as "Android Phone" with the yellow warning triangle next to it. I have tried to download drivers but can't seem to get them working. Whether that is my fault or the laptops fault I am unsure.
Any help would be greatly appreciated!
Thanks,
benandrews54
Click to expand...
Click to collapse
HTC drivers are not yet compatible with win 8, I was having the same problem you shud use older version of windows.
with out the drivers sync cannot access the phone
When win 8 is officially released; HTC will release a compatible driver
This might work try once
http://forum.xda-developers.com/showthread.php?t=1775870

I found a fix for this... Follow these steps here:
http://*******/FeT5J
Then install your drivers like normal.
Let me know if this helped!

alexander7567 said:
I found a fix for this... http://*******/FeT5J Let me know if this helped!
Click to expand...
Click to collapse
That link is dead.

Searched and found multiple 'fixes' but none of them work for me.
Tried:
Restarting Windows 8 into "Disable driver signature enforcement" mode but HTC drivers still terminate as "not compatible with this version of Windows". cant post link, search "Installing Fastboot/ADB drivers in Windows 8"
Installing drivers via device manager but "Windows was unable to install your Android phone".
DL and installed full SDK but 'SDK Manager.exe' flashes up and closes with no further notice when trying to run.
Despite post count I'm not a noob, I am however starting to feel like one! I thought I knew what I was doing but I just can't find compatible drivers to get Windows 8 to recognise my Android so I can run ADB and Fastboot.
Appreciate some have no issues (and that's wonderful for you) but this is driving me crazy! Can someone please post a link to USB drivers that work with Windows 8 x64 and the Desire S.

olidroid said:
Searched and found multiple 'fixes' but none of them work for me.
Tried:
Restarting Windows 8 into "Disable driver signature enforcement" mode but HTC drivers still terminate as "not compatible with this version of Windows". cant post link, search "Installing Fastboot/ADB drivers in Windows 8"
Installing drivers via device manager but "Windows was unable to install your Android phone".
DL and installed full SDK but 'SDK Manager.exe' flashes up and closes with no further notice when trying to run.
Despite post count I'm not a noob, I am however starting to feel like one! I thought I knew what I was doing but I just can't find compatible drivers to get Windows 8 to recognise my Android so I can run ADB and Fastboot.
Appreciate some have no issues (and that's wonderful for you) but this is driving me crazy! Can someone please post a link to USB drivers that work with Windows 8 x64 and the Desire S.
Click to expand...
Click to collapse
I have managed to use adb and fastboot with the SDK only without any additional drivers. Try to run it in compatibility mode
Sent from my HTC Desire S

amidabuddha said:
I have managed to use adb and fastboot with the SDK only without any additional drivers. Try to run it in compatibility mode.
Click to expand...
Click to collapse
Thanks, I tried that under both XP and 7 mode to no joy. It's not just this one PC, I can't get it to work on any of my (3) Win 8 machines!
For the SDK, I dl and unzipped the (almost 400Mb package) with WinRAR. With Java install, Elaipse works fine but I cannot get 'SDK Manager.exe' to run. I tried to run from both GUI and CLI but not even an error message.
Device Manager still shows exclamation mark under 'Android Device'.
I even tried to run the HTC Sync Tool but this failed at the USB driver stage. Nothing seems to work
Very frustrating as I have a custom ROM which keeps powering down randomly so I need a reload very soon.

Edit reread the whole post

I was having a lot of trouble with windows 8 x64 and jugg1es pointed me to the guide posted by .blAcK. Worked perfectly for me. Tried it on 2 different PC's. I'm not sure why it's not working for you though. I used the x64 files posted by the author of the guide.

benandrews54 said:
Hi all,
I am trying to upgrade my HTC Desire S to Android 4.0 via the official ICS update from HTC. However, I cannot get my laptop (Windows 8) to interact with my phone.
If I mount the SD card then I can view the contents but HTC sync won't find the phone and in 'Device Manager' the phone is labelled as "Android Phone" with the yellow warning triangle next to it. I have tried to download drivers but can't seem to get them working. Whether that is my fault or the laptops fault I am unsure.
Any help would be greatly appreciated!
Thanks,
benandrews54
Click to expand...
Click to collapse
There is no problem with windows 8 and ADB or HTC desire S connention problem, since this post is from 2012, if you have that problem again , let me know to write back step by step tutorial.

azithro said:
There is no problem with windows 8 and ADB or HTC desire S connention problem, since this post is from 2012, if you have that problem again , let me know to write back step by step tutorial.
Click to expand...
Click to collapse
Dude - do you have a problem? Now you're necro-posting old threads for absolutely no reason at all

SimonTS said:
Dude - do you have a problem? Now you're necro-posting old threads for absolutely no reason at all
Click to expand...
Click to collapse
Hey Simon, wasup dude, Just trying to help some one, in my free time.
Dude why you chase me ?

There isn't a need to revive dead thread. Visit the ot if you're bored.
From my DesireDS

Please Help - MTP USB Device

Just got a HTC One SV this afternoon for the missus. (I am a Note 2 owner) and part of the deal to get her away from wanting an iPhone 5 was to convince her Android was the way to go. Of all the phones she looked at, she chose the HTC One SV because of its size ...
Brought it home with the promise I would set it up like my phone for her and all would be good.
Proceeded to follow instructions found in the HTC One SV section of these forums on unlocking the bootloader and so forth.
What a complete and utter nightmare HTC put their customers through for a simple unlock! Went to their site, followed the instructions, joined, emailed, got my "token" <-- what a joke! and proceeded with the next set of instructions which was to place a TWRP img on the phone.
Next thing I know windows pops up and says Device driver was not successfully installed. ? MTP USB Device ...
This I dont get at all. When I first plugged the phone into the PC the forst thing Windows did was install the drivers. The phone popped up in windows and I could access the internal storage.
I've installed HTC Driver & SyncManager but still whenever the phone is plugged in I get the MTP error and no phone in windows. So how am I to finish setting up this phone now?
The only reason for this post is I am exhausted, I've been searching these forums and the net for an answer, and I'm completely at my wits end.
I have an unlocked HTC One SV which may as well be bricked if I can't access it via PC. Maybe I should of let her have that damn iPhone 5 after all ...

Massive props to Seanie280672 who helped me get a recovery.img onto the phone. Phew!
Missus won't be giving me any grief over not getting an iPhone 5
That said, even though I managed to somehow connect the phone to the PC, it is still not coming up in windows explorer, and upon connection of the phone (USB) to the PC, windows always throws up the message that the drivers are not installed?
Check device manager and there's the dreaded little yellow astrix next to the mobile device. Somethings amiss here ...
Thx for the help, muchly appreciated. :good:

Since JB all HTC devices are recognized on PC as MTP device. Previous used UMS was kicked out.

Install the latest version of htc driver

I'm in Australia so I got the drivers from HTC.au site:
http://www.htc.com/au/support/news.aspx?p_id=537&p_name=htc-one-sv
The driver file is called setup_2.1.55.0_htc
Is this the latest or is there a different driver I should be using?

Burginthorn said:
I'm in Australia so I got the drivers from HTC.au site:
http://www.htc.com/au/support/news.aspx?p_id=537&p_name=htc-one-sv
The driver file is called setup_2.1.55.0_htc
Is this the latest or is there a different driver I should be using?
Click to expand...
Click to collapse
have u tried to enable usb debugging? Go to settings > developer options

If your driver is including HTC Sync, you should be fine.
You can uninstall Sync afterwards, driver for the phone will still remain.

Strangely deleting Sync did the trick. Plug in the phone and no pop ups saying drivers are not installed. Phone is now showing up in My Computer.

Yup, not the first time, Sync makes the problem.

[Q] Droid Razr HD XT926, CM11, Diag Mode, & CDMA Workshop

I'm trying to use CDMA Workshop to do a partial flash on my phone from Verizon to PagePlus. I can't figure out how to get CDMA Workshop and CM11 to play together nicely with me. At first I could not find the port in Win8.1 or CDMA Workshop, but then I found an online post on using a 3rd party virtual port program. As a result I did get a port (COM10, port 11008), but when I try to Read in CDMA Workshop I get an error stating the device did not answer (I think because it is still not in diag mode). In CM11 Android Debugging and ADB Over Network (for the virtual port) are on. Anyone know what I'm missing please? Thank you in advance for the help.
Droid Razr HD (XT926) Verizon
CyanogenMod 11 M2
CDMA Workshop v3.9.0

[SOLVED]
first, THANK YOU dragonhart6505 for your youtube vid how to install motorola qc diag driver for unlocking motorola droid razr m/hd (xt907/xt926). your words "hit vol up so phone boots properly" was what i was missing.
my problem was i wasnt really in diag mode. :crying:
heres how i resolved my problem. i went back to stock rom (4.1.1). im not sure, but i think i had to do this. i think nv mode is disabled by custom roms. that didnt resolve my problem completely though. i found out i wasnt really in diag mode (bp tools for my moto). i thought i was booting into bp tools mode. i did the three finger salute. i scrolled to bp tools. let phone boot and plugged it into usb port. no qc port (not even one that needed a driver). couldnt create a virtual serial/com port either using hw vsp. got a lan error. cdma workshop stated no answer from my phone. i could ping the ip though with no errors. all because i wasnt in bp tools mode as i thought! UGHHHHH!!!! after scrolling to bp tools, hit vol up (no dont scroll to factory reset). youll see when you do it. then i was able to manually install the qc driver. then i could read in cdma workshop.
the other thing i learned along the way was that with windows 7/8 (yes, and 8.1) the qc diag driver must be manually installed.

There is a thread about how to put this phone onto Page Plus over on Howard Forums. There may be a mirror of how to do this here as well. Also you do not need CDMA Tools to do this either. There is another thread about trying to put the phone onto Page Plus with the new 4.4.2 software. We have not been successful in that yet. If you do not have an unlocked bootloader then would work on getting that done ASAP.
Jackie

[Q] restoring bricked oneplus one problem

First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks

gl411 said:
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
Click to expand...
Click to collapse
Have you installed the Qualcomm driver?Its very tricky,Windows wont allow to install it easily.

Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?

gl411 said:
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
Click to expand...
Click to collapse
It should be the driver problem,no other choice.

maskelisuvari said:
It should be the driver problem,no other choice.
Click to expand...
Click to collapse
The easiest way for unbricking oneplus (yes, I tried it): http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
ColourOS firmware has all needed files for proper flashnig, including right tool for doing that.
Only thing that didnt work on my Win 8.1 x64 was drivers mentioned in post above.
I had to use this QHSUSB_DLOAD drivers from member DallasCZ (that I used for unbricking ZTE v9180). Only with that drivers my Windows recognized bricked phone and Flash tool could find and flash it.
Flash tool in only on chinese, that is a bit problem, but instructions given in post I linked are more/less usefull.
This is a link to DallasCZ shared folder with qhsusb drivers:
https://drive.google.com/folderview...&usp=sharing&tid=0B1T7tp6tJ_3kQkZSWjNsazJZbGc

If you are sure the driver is okay,plug in the usb cable and out and in,until you see the green line on the tool.Also you can follow the guide as in below link:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
The same thing but this time you can flash CM11s instead of ColorOs.Also there is a video.Pls check it.

Ok so I did the process over and over again, the sixth computer did it right! I was back on ColorOS and now back to CM11S.
This thread can be closed, thanks for the help!

No problem,glad to hear you solved the problem