I've come across so many posts on the internet for drivers for this phone and yet none of them seem to work. My phone keeps coming up as CDC Serial.
I haven't given up on it yet, but while my phone responds under fastboot, while plugged in and booted into Download mode, under regular connection with both USB debugging enabled as per directions, no driver I have used recognizes it under regular ADB mode.
I'd really appreciate it if anyone can help.
I do have a clean machine I can install on if necessary but most links review to Huawei's website for the drivers and that page is gone and replaced with the current Huawei software which doesn't seem to work with this phone.
If anyone wants that files lemme know i will upload it.
Related
I recently soft-bricked my Vibrant so now it get stuck at the Vibrant screen and it is hardware locked. I can get my phone into download mode using adb but then it does not show up in ODIN. When I plug the phone in during the Vibrant screen, it shows up as COM 6 but then it is removed when it gets to Download mode.
I searched around for a while looking for a solution and tried a bunch of things but nothing worked.
Also, when I plug my phone in during download mode, it says "The USB device attached to the computer has malfunctioned and Windows does not recognize it."
I'm on Windows XP 32-bit
PC Not Recognizing Vibrant in Download Mode
My stock, rooted Vibrant was soft-bricked by the latest update. I've been following the instructions on this thread: forum.xda-developers.com/showthread.php?t=803492, but cannot get Odin to recognize the device in Download Mode.
One caveat of my current situation is that I'm running Windows XP (32bit) on VMWare on a Mac. Not sure if this is the cause of my pain, but I simply don't have a PC handy.
Currently, when the phone is connected via USB in Recovery Mode, it mounts and everything is cheery. Even on the Mac side, adb recognizes the device and lets me tunnel into it. But the instant I boot into Download Mode the computer no longer recognizes it.
I've reinstalled drivers, tried using 64-bit versions of drivers, tried Kies, but Odin simply does not see the device in Download Mode.
Has anyone experienced this and resolved the issue? Should I hunt down a PC and ditch VMware? That's pretty much my final option prior to heading down to T-Mobile.
theorginazation said:
I recently soft-bricked my Vibrant so now it get stuck at the Vibrant screen and it is hardware locked. I can get my phone into download mode using adb but then it does not show up in ODIN. When I plug the phone in during the Vibrant screen, it shows up as COM 6 but then it is removed when it gets to Download mode.
I searched around for a while looking for a solution and tried a bunch of things but nothing worked.
Also, when I plug my phone in during download mode, it says "The USB device attached to the computer has malfunctioned and Windows does not recognize it."
I'm on Windows XP 32-bit
Click to expand...
Click to collapse
What version of Odin were you using 1.0 or 1.3?
ckalima said:
My stock, rooted Vibrant was soft-bricked by the latest update. I've been following the instructions on this thread: forum.xda-developers.com/showthread.php?t=803492, but cannot get Odin to recognize the device in Download Mode.
One caveat of my current situation is that I'm running Windows XP (32bit) on VMWare on a Mac. Not sure if this is the cause of my pain, but I simply don't have a PC handy.
Currently, when the phone is connected via USB in Recovery Mode, it mounts and everything is cheery. Even on the Mac side, adb recognizes the device and lets me tunnel into it. But the instant I boot into Download Mode the computer no longer recognizes it.
I've reinstalled drivers, tried using 64-bit versions of drivers, tried Kies, but Odin simply does not see the device in Download Mode.
Has anyone experienced this and resolved the issue? Should I hunt down a PC and ditch VMware? That's pretty much my final option prior to heading down to T-Mobile.
Click to expand...
Click to collapse
It's the Mac....sounds like you've done everything correctly. do you have the option for Parallels?
Download mode uses a different usb driver. If you are running in a vm you need to set the vm app to pass that usb device thru to the guest os.. i use odin in virtualbox on linux just fine. I haven't tried it on osx though. There's also an app in development in the i9000 dev forum that runs natively on osx.
@shinybuddha unfortunately parallels is not an option, but I could likely hunt down a PC
@ttabbal thanks for the tip, I've been suspicious of the drivers. Currently I have version 5.2.0.5 installed, and when connecting the Vibrant in download mode, a "Generic Serial Device" appears, but fails to connect.
Unfortunately the device exhibits the same behavior on the Mac side, and isn't being recognized in Download Mode, at least not by "adb devices".
Is there a specific driver I should install in the virtual XP os? Or could you provide a link to the osx app?
I think I need to find a PC. After scouring the forums it appears there has been no successful Odin use on a Mac via VM.
forum.xda-developers.com/showpost.php?p=7854560&postcount=12
Also discovered this interesting bit from the Heimdall developer:
After some serious investigation and a bit low-level debugging it appears as though there is very little I can do to correct the GT-I9000's lack of USB specification compliance when in download mode. When in download mode the GT-I9000 is using an embedded Gadget Serial driver and not the one provided by the linux kernel (zImage). As such I have made Samsung aware of the issue although I don't know if they will resolve it or how long it will take.
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=755265&highlight=heimdall&page=16
Found a Windows Vista 64-bit installation and followed the directions on the following thread:
forum.xda-developers.com/showthread.php?t=803492
My Vibrant is back! Done in 30 minutes, after spending 3 days trying to get it to work via VM on a Mac. Sometimes iCan't.
Just to help out anyone else with a similar problem using Windows directly... I also found that Odin would recognize my phone when on normally but not in download mode. To solve, what I did was put the phone in download mode, then open up device manager and there was a new unknown device... gave it the path to the downloaded drivers and let it install. Then another unknown device popped up (might have to close and reopen device manager, or refresh, or unplug and plug phone). Pointed it to drivers download again and it magically appeared in Odin.
Aerankas said:
Just to help out anyone else with a similar problem using Windows directly... I also found that Odin would recognize my phone when on normally but not in download mode. To solve, what I did was put the phone in download mode, then open up device manager and there was a new unknown device... gave it the path to the downloaded drivers and let it install. Then another unknown device popped up (might have to close and reopen device manager, or refresh, or unplug and plug phone). Pointed it to drivers download again and it magically appeared in Odin.
Click to expand...
Click to collapse
What drivers did you "point" too. Im having the same issue as you, except in my device manager is says "Gadget Serial." Either way, I need my PC to recognize my phone in download mode so please help!
I had the same proble. It showed Gadget serial in device manager. I uninstalled all other samsung and keis related drivers and installed 5.2.0.4 and it worked out fine. You can download them from here. Good luck.
http://forum.xda-developers.com/showthread.php?t=728929
omg thanks
ya, the other drivers were screwed somehow, switched to these and bam... odin sees the vibrant. Thanks in bunches, lifesaver move there
Hi, been lurking around here for a good while now....fantastic website website and I've learned so much but now I have an issue.
For what ever reason my nexus 7 will not boot, I can get into fastboot and have been following the guides to do a full factory restore through fastboot. Everything goes fine until is comes to "Sending System" then just.....stops. I have used the nexus toolkit and also the official sdk drivers and fastboot contained there. I only have an old laptop as my main pc for some reason does not recognise the nexus.
I have tried alternative USB cable too.
Does anyone have any other advice.
Also the device is complete stock no custom rom has been installed so no custom recovery available.
I really appreciate any help.
Cheers!
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Try a search, shouldn't be hard to find what others have done with Windows 8 difficulties...
singlemanriot said:
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Click to expand...
Click to collapse
Go to Device Manager, show hidden devices and uninstall any Android or ADB related devices that you have. Disable USB debugging on your Nexus, then plug it into your PC and see if it's recognized. If it is, then re- enable USB debugging, then go to Device Manager and reinstall the Google USB drivers to get ADB support back.
Thanks for the advice, first thing I did was try searching....I have tried countless methods suggested but nothing works its like windows cant find the drivers. In the device manger its recognised but no diver installs no matter what I do. If I force the manual driver install it fails!? I have tried the Naked drivers, the SDK even making sure the media components of windows are installed properly
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
asylumxl said:
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
Click to expand...
Click to collapse
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Gizmoe said:
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Click to expand...
Click to collapse
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
asylumxl said:
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
Click to expand...
Click to collapse
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Gizmoe said:
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Click to expand...
Click to collapse
I'll give that a go, that's the only thing I haven't tried so far. It's just bizarre it shows in every other mode. The device is there in the Device Manager under hidden, but doesn't actually show up as connected. Thanks .
hello I'm really hoping somebody can help me because I'm not getting answers anywhere I've halfway through a course to learn mobile tech repairs and I'm completely stuck on a Samsung SM g925a when trying to remove the FRP. I have written my class instructors and I'm not getting any response. I've downloaded all the drivers from Samsung I've updated them all but however it is not allowing me to connect the device to my PC so I can get it into odin to flash combination files. When I plug the device in to my windows 10 pc I receive a pop up saying the last USB device you connected to this computer malfunctioned and windows does not recognize it and then in device manager when I open it it shows as unknown USB device device descriptor request failed. I tried to download the drivers again reinstalled and updated them and that didn't work. I changed all my cords tried it on every Cord I had and it didn't work, yet these cords recognized other devices I had. I also uninstalled the USB driver and then I ran the hardware troubleshooter still got nothing and then I also disabled fast startup none of this has worked. I also have spent countless hours researching on line and I'm just not getting any answers and I get the same troubleshooting ideas I've already tried however I did come across a program USB debugger r but I don't know if I had just downloaded it wrong or had the wrong firmware files but it wasn't working for me I thought maybe that would help me to connect to PC. I'm still learning and only halfway through the course but it seems like this is such an easy issue that I just can't seem to figure out is there anybody out there willing to help me figure this out please I'm sure something simple Im missing or forgetting but I've been dedicated to this phone and I sure can't figure it out it's stopping me right at the gate. Thanks in advance
A little history. I have rooted several other brands of tablets, so I am not new at this. Even thogh I am not a programmer by any stretch of the word. My Pixel C drivers work fine in normal mode, I can see the storage as a drive, no problem. I can transfer files back and forth. But, when I boot it into fastboot mode, it will not see it. It is listed as an unknown device in the device manager of Windows 10. I have tried to install the drivers, but they say not found. And this is the driver from the Android website. I'm at my wit's end. I'm not a newbie at windows, either. But, I need suggestions to get this to work. BTW this is the latest version of Windows 10 1903. And I have tried every solution I have found on google and on this website. TIA
Ok, fixed that by selecting a driver from a list of drivers so now I have ADB drivers. I have another issue which I will do some research on if not.....I'LL BE BACK.
What is your goal?
Do you want to use adb or fastboot?
Is the bootloader unlocked, have you enabled usb debugging in the developers menu (hidden) etc
Ok, as I said before, I figured it out. And yes, the bootloader was unlocked and yes USB debugging was enabled. I got everything
working and I am now running Android 9. Thanks for the reply, though.
Toolcrazy said:
Ok, as I said before, I figured it out. And yes, the bootloader was unlocked and yes USB debugging was enabled. I got everything
working and I am now running Android 9. Thanks for the reply, though.
Click to expand...
Click to collapse
Missed that! (you mentioned another issue)
Well done etc