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

Fastboot doesn't work on Windows 8.1

So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.

Theshawty said:
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Click to expand...
Click to collapse
I have been trying to get it recognized in fastboot for pas four hours without any luck.. Prior to this, I also had W8 with working fastboot and now I get the same error as well. I tried numerous times, even uninstalled all my drivers (except for display and mouse) to do a clean driver reinstall, but without luck :/

Theshawty said:
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Click to expand...
Click to collapse
rs70 said:
I have been trying to get it recognized in fastboot for pas four hours without any luck.. Prior to this, I also had W8 with working fastboot and now I get the same error as well. I tried numerous times, even uninstalled all my drivers (except for display and mouse) to do a clean driver reinstall, but without luck :/
Click to expand...
Click to collapse
Hi, can you guys try this method if you still in windows 8.1???
I personally having a samsung phone and I also having this problem after upgraded to windows 8.1 but now I'm back to windows 8 so I just cannot test it. After test please report back the results to me and I really hope it works. Thanks~
By the way, can you guys tell me your phone model???

DreamerTKM said:
Hi, can you guys try this method if you still in windows 8.1???
I personally having a samsung phone and I also having this problem after upgraded to windows 8.1 but now I'm back to windows 8 so I just cannot test it. After test please report back the results to me and I really hope it works. Thanks~
By the way, can you guys tell me your phone model???
Click to expand...
Click to collapse
Well, I tried something similar, but whenever I uninstalled the usb port from device manager, it reinstalled back and reported that the device is not recognized..
I've got HTC One and its drivers don't work on 8.1. However, I installed HTC drivers (by installing and uninstalling HTC Sync Manager - possibly the lamest method that exists) on Vista and it instantly recognized the phone. So the five hours on 8.1 could have been saved by spending circa 3 minutes on Vista.
But on some forum somebody mentioned that you can use live CD of linux and it will get recognized easily

rs70 said:
Well, I tried something similar, but whenever I uninstalled the usb port from device manager, it reinstalled back and reported that the device is not recognized..
I've got HTC One and its drivers don't work on 8.1. However, I installed HTC drivers (by installing and uninstalling HTC Sync Manager - possibly the lamest method that exists) on Vista and it instantly recognized the phone. So the five hours on 8.1 could have been saved by spending circa 3 minutes on Vista.
But on some forum somebody mentioned that you can use live CD of linux and it will get recognized easily
Click to expand...
Click to collapse
Thanks for your fast reply. Seems that even Microsoft is providing free update for windows 8 but a phone that unable to flash by using bootloader is kinda useless for unofficial ROM users like us.
I have something don't understand from your post. You mentioned that install and uninstall the sync manager on Vista but why not back to 8? The drivers will work on 8 right? I formatted my computer back to 8 and now finally the windows recognize back my phone.
Other than that, do you still have the link to the live CD forum??

DreamerTKM said:
Thanks for your fast reply. Seems that even Microsoft is providing free update for windows 8 but a phone that unable to flash by using bootloader is kinda useless for unofficial ROM users like us.
I have something don't understand from your post. You mentioned that install and uninstall the sync manager on Vista but why not back to 8? The drivers will work on 8 right? I formatted my computer back to 8 and now finally the windows recognize back my phone.
Other than that, do you still have the link to the live CD forum??
Click to expand...
Click to collapse
Well, my primary PC is my laptop with 8.1, but I've got desktop as well with dual-booting Vista and 8.1 and it is way faster to do it on vista, than to partition HDD and install Windows 8. Also I'm not dev or some tinkerer, so I don't need to use fastboot that often.
To answer the second question, I closed all tabs regarding the drivers on 8.1 as soon as I did what I needed on Vista, so I'm afraid I don't have the link. I could probably find it somehow using my internet history, but I spent several hours browsing various forums, so it would take me an eternity...

[Help] Google Nexus 5 might be bricked

Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead (Edit: For a strange reason, it didn't update to the latest version available.)
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3

Almogpas said:
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Click to expand...
Click to collapse
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom

bitdomo said:
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
Click to expand...
Click to collapse
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)

Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
hmmm... try lg flashtool. Link in my signature.

Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
http://developer.android.com/sdk/win-usb.html

doctor_droid said:
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
Click to expand...
Click to collapse
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.

Almogpas said:
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Click to expand...
Click to collapse
Yup if the pc is not detecting the phone best is to try wid another usb cable and a different pc... let us knw tomorrow

Did you install those libraries properly?
Freshly baked from my Nexus 5

This universal ADB driver + this ADB and Fastboot pack always does the trick for me.
When you get either ADB or Fastboot working we can help you recover the device.

USB driver problems, drivers not being kept

So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?

donk165 said:
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
Click to expand...
Click to collapse
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.

Mr hOaX said:
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Click to expand...
Click to collapse
Fair enough, well i'm thinking I may move back to CM11S if things don't work out on Blisspop. If I turn off USB debugging and then switch to camera (PTP) mode and then back to MTP mode, my phone then connects fine. I wanted it to connect so I could copy my Titanium backup files off the phone and onto the PC. In the end, my mate told me about Airdroid and I managed to download them through that as a ZIP file. For some reason, the titanium backup folder isn't visible from your computer, I tried copying it to the DCIM folder and it just gave me a 1kb file. I also tried a new folder called backups and it was empty when I looked on my PC, but the files were visible when using Airdroid and also when I used a file browser on my phone.
Weird stuff!

Just wanted to bump this and see if anyone has a solution or even just an explanation.
Whenever I plug my OPO into my PC (with the original cable), the device, A0001 is found but is shown in Device Manager with an exclamation point. If I then right click on it and chose uninstall, and then reconnect the phone, it will connect and work fine for MTP/PTP modes. If I put USB debugging on, the MTP doesn't always work after. But no matter what, if I shutdown my PC, and then come to connect the phone the next day etc, I have to do the uninstall of the driver then reconnect for MTP to work. Pretty frustrating!
Anyone know why the phone isn't remembered by my PC correctly? I'm on Windows 7 x64 if that means anything.

I'm moving back to stock ROM soon so I'll see then if its something to do with the unlocked bootloader or using a custom ROM. I'll report back if I have any luck

Bumping this again, its still the same on 6.0. I don't fancy moving back to stock ROM, I like CM over Cyanogen OS, but this problem is really frustrating. Every single time I connect the phone to the PC, it will come up as A0001 but with an exclamation mark next to it in Device Manager, if I right click and uninstall the driver, then reconnect the phone, it works fine then. But if I restart my PC, it does the same thing where it cant find the right driver for the phone.
Is there anything I can try to fix this?

Lost TWRP and ADB/Fastboot can't see phone to sideload. What can I do?

Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
NOTE: I'm on a Mac

rajah sulayman said:
(crossposting from here as this looks like a more active sub and I'm desperate).
Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
Click to expand...
Click to collapse
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Sent from my PH-1 using Tapatalk

sd_shadow said:
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Click to expand...
Click to collapse
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.

rajah sulayman said:
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.
Click to expand...
Click to collapse
do you know how to check which drivers are selected.?
Sent from my XT1254 using XDA Labs

sd_shadow said:
do you know how to check which drivers are selected.?
Click to expand...
Click to collapse
Is it through the Android Studio SDK manager? I remember using that way back when to get everything set up, but I haven't really used it since then.

Actually I just remembered that Mac don't need drivers, right? Per Google:
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. Instead see Using Hardware Devices."

Update: Pulled out my Windows laptop and installed everything (drivers, Android Studio, et al) to see if I'd have better luck there.
To test, I first plugged in my working Nexus 5X. Windows immediately recognized it. Pulled up a prompt and adb devices saw the phone no problem.
Unplugged the Nexus and plugged in my Pixel XL. Nothing. No "hardware plugged in" chime, nothing listed under Device Manager, nada. Likewise, the phone itself doesn't acknowledge that it's been plugged in because there's no Android System pulldown.
If it were a driver issue, Device Manager would still at least be able to see the phone (it just wouldn't know what it was). But I'm getting absolutely nothing.
I can only assume that the problem is indeed with the phone itself. I don't know what the problem is exactly, but I know it wasn't there before all of this. Either way, this means my only hope for a fix would have to be through the phone itself. But since Stock Recovery doesn't seem to offer me many options, I have no clue what to do next.
Is there some sort of "secret" key combo or command or something that'll do a low-level format of the phone or something? I'm grasping at straws here, I know, but I honestly don't know what else there is I can do.
-------
Update 2: If I plug it in while in Bootloader, Windows recognizes that a device was connected, but as an "Unknown USB Device (Device Descriptor Request Failed)"
None of the solutions I can think of (or Google) seems to work. Has anyone heard of this problem before? I'm vainly hoping there's a fix out there that I just haven't found yet.