[Q] Odin drivers checkup? - Galaxy S II Q&A, Help & Troubleshooting

Hi guys,
I really do not want to install KIES as it looks to me a HUGE piece of bloatware.
Anyways, to make the story short, I think I got all S2 drivers installed the clean way but I need to make sure everything is OK, before I root my phone.
This is what I did (might be useful for others):
First, I plugged the phone through USB on my Windows 7 SP1 64bits box. It detected right away the phone and installed a set of drivers, except the CDC serial. I was able to see and browse the phone content (deleted some .ipk file I downloaded by accident also):
In Device Manager, I had flagged the CDC Serial:
I said, OK... let's get into Odin mode (Vol Down + Home + Power) and see what happens. To my surprise, once Odin was displayed on my phone, Windows detected new hardware and downloaded then actually installed the right drivers???
After the drivers were installed, I powered down the phone, removed the USB cable and start it in normal mode. Once the phone was powered up, I plugged back the USB cable and the CDC Serial was missing again into Device Manager! I powered down again the phone and start it in Odin mode, the CDC Serial driver showed as being properly installed... go figure, heh.
Finally, the question: I would like to know if there is a method to check if Odin software communicates properly with the phone, before I attempt the rooting. I don't care if I get a flagged CDC Serial when the phone is in normal mode.
I really hope all drivers are properly registered, so I don't need to install the creepy KIES... as a side note, if you extract the executable, you will find inside the archive a cab file that contains a huge set of drivers (C:\kies_win\CabFile\USB Driver\SAMSUNG_USB_Driver_for_Mobile_Phones.exe.cab). I extracted the .cab file and ran a driver upgrade in Device Manager for the CDC Serial with the phone in normal mode, it did not do jack.
Thanks for your help.

Related

[Q] Unknown Device :(

Hi everyone,
i'm having difficulties to connect my sgs2 to a pc.
i have tried it on 3 different machines (win7 64, win7 64, winxp 32) with the same problem:
I works fine when i first connect the phone in download mode. But as soon as i disconnect the cable i can't connect it again. Windows sais that it doesn't recognize the device and that's it. The device manager shows an "Unknown Device" under USB-Controller. And i am not even able to install drivers by manually pointing windows to a file.
as already sais, i have tried that on 3 different machines. I have tried installing driver via kies and via the driver file that is available here in the forums. i have also tried different usb ports.
Any ideas?
Goddchen
EDIT: Maybe this is an important information: the phone connects fine as long as it is running (can be found via adb, logcat is working, etc...) it only makes problem when in download mode...
I had exactly the same issue yesterday on my Windows 7 box. In the end I connected the phone in normal (not download) mode. Into device manager and uninstalled the drivers through there.
Then I uninstalled Kies and reconnected the phone, I allowed Windows to search windows update to find drivers (not that it did as it couldn't find any and reverted to the local ones. Then disconnect the phone, re-install Kies, run the install drivers from the tools menu, close Kies. Run up Odin and the connect the phone in Download mode, low and behold 2 minutes later after a lengthy installation process the phone was picked up.
I tried a number of things but for some reason this specific order seemed to sort it.
Hey,
thanks for you hints. But they didn't work for me.
I found the problem: believe it or not, it was THE CABLE. I went and got another cable and this one is working fine all the time. The other one doesn't... Very strange...

Will not connect to PC

For some reason when i connect my GS2 to my computer (running xp) it wont give me the options to make it a mass storage device but when i use it on my laptop (running Windows 7) it works fine any ideas why and i ahve debugging on as well please help
you probably don't have the drivers installed on your PC - does the computer recognize the phone at all? if not, download samsung kies, and this should give you the appropriate drivers. alternatively, go on samsung's website and search for the appropriate drivers for the i777.
I'm having this similar issue but on Windows 7. I've already installed correct drivers and Samsung Kies. This issue began after I rooted my phone. I plug in my phone and my computer makes the device recognition sound. My phone is recognized in device manager as Samsung mobile usb composite device and my phone isn't in debug mode and doesn't give me the option for usb storage. I want to flash a rom into my phone but can't because I can't get into the internal sdcard. Any suggestions?
Try downloading pdanet on your computer. Then plug in your phone again. I had this problem and that fixed it for me.

Driver problem

Need a little help here. I cannot get my phone to connect to my computer, I'm running Windows 7. I have kies installed and have also downloaded the drivers directly from the Samsung site, but still cannot connect. When I plug in, it says installing drivers, but then gives me an error.
If I go to Device Manager, I see SAMSUNG Mobile MTP Device but with the yellow exclamation mark. Under driver details it shows the correct driver installed, but has a Code 10 Error. "The Device cannot be started".
I've rebooted comp, rebooted phone, toggled USB debugging, uninstalled and reinstalled drivers, tried 2 different USB cables, and nothing is working. Anyone have any ideas?
I didn't have to do everything you listed to get it to work, but I did have to run the installer (T-Mobile_T999_GSIII_Samsung_USB_Driver_v1_4_6_0.exe) twice to get it to work.. it failed the first time.
I just unplugged and then plugged cable back in, ran the installer and installed again over old drivers.
You can also try going into Device Manager, right-click on the phone and "Update Driver Software" manually... installer extracts all drivers to the C:\Program Files\SAMSUNG\USB Drivers folder.
Still no luck. It installs the Samsung USB modem drivers fine and shows the phone correctly, but fails on the MTP Driver section.
Just for future reference for anyone that comes across this while searching. I did get this fixed. I tried a couple more usb cables and a friends computer with the same issues.
What I ended up doing was a factory reset on the phone. Plugged phone in after first boot and mtp drivers installed right away.

Odin does not see phone

Help mee.
I have bought a s3 that is locked to Orange, need to unlock, but odin does not see the phone in recovery/dl mode.
Odin see the phone in normal mode , but each time i put into start/+vol/home odin see nothing.
I have kies updated.
Thanks
crazydiamond1970 said:
Help mee.
I have bought a s3 that is locked to Orange, need to unlock, but odin does not see the phone in recovery/dl mode.
Odin see the phone in normal mode , but each time i put into start/+vol/home odin see nothing.
I have kies updated.
Thanks
Click to expand...
Click to collapse
I had a similar thing when i was plugged into a usb hub
Was ok when i plugged directly into the pc
Install Samsung Kies to be able your PC to detect your phone via Odin
also check the debugging mode in the developer options
bordikun said:
Install Samsung Kies to be able your PC to detect your phone via Odin
also check the debugging mode in the developer options
Click to expand...
Click to collapse
I have Kies, also tried debugging, i need root to unlock phone
Try to use the latest Odin
Odin v3.04
bordikun said:
Try to use the latest Odin
Odin v3.04
Click to expand...
Click to collapse
I have uninstalled the older Kies, re installed the latest.
I have installed the lastest odin.
Have tried to link up with and without debugging, odin still does not see phone when in recovery mode.
Only time odin see the phone when phone is in normal mode.
Starting to get annoyed now lol, i cant cut my sim to fit phone, untill this is done
I cant see my s2 on odin either, what am i doing wrong ????
1. Reboot PC
2. Ensure KIES is not running and kill any KIES processes in PC task manager.
3. Download mode
4. Connect USB directly to PC port (no hub)
5. Wait for any drivers to instal or load on PC
6. Start Odin in administrator mode
If still no good;
a) Different USB cable
b) Different PC USB port and wait for drivers
Sent from my GT-I9300 using xda premium
Thanks . Seems that I had been pressing volume up not down.
I have another question . I used chainfire Rom to debrand the phone but keis does not recognize . How can I solve this . Could it be because the phone is rooted ?
i am having this problem at the mo, I have tried all of the above, apart from a different pc.
oden worked fine with my galaxy s2
is there any more updates on how to sort this out please?
thanks
ian
I know this is a 7 day old thread, but I feel for you having been in the same situation. Firstly, have you installed the Android SDK? If not then I advise you to do so. Do a search on how to install the SDK. There maybe smaller downloads available with a package of the binaries you need to do some testing i.e. adb. The instructions will elaborate about how to set up your Environment settings in Windows. Essentially ADB needs to be called from within any part of your Windows system....or else you will have to cd to its location each and every time you want to do something like this. So once you have done that, open command prompt and type adb and see what comes up? If it says bad command or file name it means your environment settings for the ASK are incorrect, if it displays the adb help text in command prompt you are ready to proceed.
When you plug your device in (not in DL or recovery modes) is it detected by the PC? If so then your drivers are probably fine. If not then it maybe 1 of 2 things? 1 the device is detected but the MTP drivers have not been loaded or 2. No detection what so ever and all drivers need to be installed.
To determine how to proceed you will need to do a bit of investigating.
Note the USB drivers are included as part of the Android SDK.
Check in Device manager inside of Windows to see if anything is detected when you plug it in. If so but it has a yellow exclamation ! then it would indicate you need to update your drivers (but not always?). From here you can test to see if the phone is detected and you only need MTP drivers.
If not then I would suggest uninstalling Keis all together and downloading and installing the Samsung USB drivers separately. Install the drivers. Plug in the phone. If it is not detected straight away, then reboot the PC then plug the phone into a different USB port. From here you can determine how to proceed by using adb.
plug your phone in via USB and open command prompt and type this: adb devices
You should see 1 of 2 things.
1) The words "list of devices attached" followed by a 16 digit long ID number a gap and the word "device"
2) just the words "list of devices attached" and then blank and nothing else?
If a device ID is returned then you can proceed with the following. Otherwise you need to do some additional trouble shooting
Proceed here:
Once it is detected by Windows and shows up in Explorer then unplug the phone and go into settings and developer options and check enable USB debugging. Once you have done this it should allow your device to be seen in DL and recovery modes.
Troubleshoot: If not detected try the following:
1) Reboot the PC and plug into a new USB port that you have not previously plugged into.
2) Try disabling USB debugging plugging the device in and then unplugging it and reenabling USB debugging
3) From the status bar try switching modes between MTP and PTP modes. Wait a good minute or so between to allow Windows to detect the driver change. Tip a good indication is your notification tray Icon with green USB disk with a magnifying glass swirling around....Note if you cannot see this at all you probably should drag it into the notification panel so that you CAN!
4) Open up device manager again and ensure no yellow exclamation marks !
Once all this is right and you can get List of devices attached followed by an ID number then you can for sure be able to detect your device from Odin. Make sure you are running Odin 3.04, run it as admin (not necessary but have heard that it helps?)
Good luck
James
I have an S4 Active that NO MATTER WHAT I DO, Odin will NOT see phone in Download mode, it will with the phone on, and my PC will see the phone, but not Odin. I am stumped. I have tried 3 PC's, I have ALL the drivers and then some. I am Stumped.
rekamyenom said:
I have an S4 Active that NO MATTER WHAT I DO, Odin will NOT see phone in Download mode, it will with the phone on, and my PC will see the phone, but not Odin. I am stumped. I have tried 3 PC's, I have ALL the drivers and then some. I am Stumped.
Click to expand...
Click to collapse
have you tried factory resetting the phone?
afasayan said:
have you tried factory resetting the phone?
Click to expand...
Click to collapse
Several times
rekamyenom said:
Several times
Click to expand...
Click to collapse
You can try with minimal/no drivers i.e. uninstall kies if you have it and delete the drivers you might have installed on your own-it sounds counter productive but it has worked for me a few times.
You can also try to either install kies or the drivers separately.
Try the forum for your own phone, the people there might know better about this problem.
Also what OS are you on?
afasayan said:
You can try with minimal/no drivers i.e. uninstall kies if you have it and delete the drivers you might have installed on your own-it sounds counter productive but it has worked for me a few times.
You can also try to either install kies or the drivers separately.
Try the forum for your own phone, the people there might know better about this problem.
Also what OS are you on?
Click to expand...
Click to collapse
I will give all that a try. I'm on 4.4.2 build NH3. That's why I need Odin, to get back to build NE3
rekamyenom said:
I will give all that a try. I'm on 4.4.2 build NH3. That's why I need Odin, to get back to build NE3
Click to expand...
Click to collapse
By OS I meant the computer's OS.
afasayan said:
By OS I meant the computer's OS.
Click to expand...
Click to collapse
I have tried several computers using Windows 7 and Windows XP both 32 and 64

Hisense c20 bricked after root.

Hello all.
I have hit a problem with my Hisense c20. I rooted using kingoroot and everything seemed to work fine. SuperUser was installed and working as it should. The phone then ran flat so I plugged it in and booted but it just hung on the SMART powered by android screen. So I restarted again into recovery mode and cleared system cache. Rebooted again but same thing. So tried again but with the wipe user data option. Still just hangs there. I then decided to try flash a stock rom via needrom. I followed the instructions but cannot seem to get the phone to be visible as a com port on Windows 7 64 bit. I have tried different cables and USB ports and reinstalled drivers countless times. Please could anyone assist me on getting this phone to be seen as a com port so I can flash it with QFIL.
Kind regards
Ryan
Ok so i managed to figure this out on my own. Basically what i did was plugged phone into pc while holding volume + and power. Phone showed up as Hisense in device manager, along with ADB device and USB composite device. I then right clicked on Hisense and uninstalled driver. Then i downloaded QCDLoader drivers and manually installed the driver via Have disk option and made sure to select the 9006 port driver package from the qcser.inf driver package. Once that was installed the phone was detected as a COM port. I then went into eMMC software download program in QPST and set the phone to download mode. Then back to device manager and saw QHUSB unidentified device. Right clicked that and went through same procedure as the 9006 driver except selecting the QCDLoader option instead of 9006 package. Phone then allowed me to flash Stock rom and was unbricked after a cache clear and system wipe. Took 3 days to figure it out but it worked. If anyone reading this is struggling with the same problem, let me know and i can go into more depth to try help. Really late and about to head off to bed.
Kind regards
Ruan
Need a file *qcn. or backup NV backup ?
Who has the opportunity to give?
[email protected]
[email protected]
RuanRex said:
Ok so i managed to figure this out on my own. Basically what i did was plugged phone into pc while holding volume + and power. Phone showed up as Hisense in device manager, along with ADB device and USB composite device. I then right clicked on Hisense and uninstalled driver. Then i downloaded QCDLoader drivers and manually installed the driver via Have disk option and made sure to select the 9006 port driver package from the qcser.inf driver package. Once that was installed the phone was detected as a COM port. I then went into eMMC software download program in QPST and set the phone to download mode. Then back to device manager and saw QHUSB unidentified device. Right clicked that and went through same procedure as the 9006 driver except selecting the QCDLoader option instead of 9006 package. Phone then allowed me to flash Stock rom and was unbricked after a cache clear and system wipe. Took 3 days to figure it out but it worked. If anyone reading this is struggling with the same problem, let me know and i can go into more depth to try help. Really late and about to head off to bed.
Kind regards
Ruan
Click to expand...
Click to collapse
Hi Ruan. You haven't found a custom recovery?

Categories

Resources