Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
1337Dev said:
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
Click to expand...
Click to collapse
install kies if you have it installed already then uninstall it then install again
1337Dev said:
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
Click to expand...
Click to collapse
Since you're already looking in the right place, consider installing a custom recovery (such as philz) with odin and then flash the zip.
Thanks for the help. I was finally able to get my computer to recognize the GS3 (Installed Samsung USB Drivers from their website instead of Kies). But now after it recognizes that I have new hardware installed, when I try to use the Wizard to automatically install the drivers I get the error: "The required section was not found in the inf", did some searching and realized that this is due to not having the wpdmtp.inf file on your computer. I've checked and it is indeed missing, does anyone now of a way to install this file?
I'm still locked out of my phone. And I don't have an SD Card to install recovery and flash the zip as dxppxd suggested.
1337Dev said:
Thanks for the help. I was finally able to get my computer to recognize the GS3 (Installed Samsung USB Drivers from their website instead of Kies). But now after it recognizes that I have new hardware installed, when I try to use the Wizard to automatically install the drivers I get the error: "The required section was not found in the inf", did some searching and realized that this is due to not having the wpdmtp.inf file on your computer. I've checked and it is indeed missing, does anyone now of a way to install this file?
I'm still locked out of my phone. And I don't have an SD Card to install recovery and flash the zip as dxppxd suggested.
Click to expand...
Click to collapse
Take another shot by booting into a custom recovery, most give you adb access while in recovery.
If the phone is locked with usb debugging disabled you won't be able to get adb access.
Related
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
I just plugged my S3 into my PC to copy some files over, and all of a sudden i got this error from windows saying USB Device not recognized and this USB device has malfunctioned. I heard its a known problem on android phones, but never really found a solution for it. Can someone help?
cr0wnest said:
I just plugged my S3 into my PC to copy some files over, and all of a sudden i got this error from windows saying USB Device not recognized and this USB device has malfunctioned. I heard its a known problem on android phones, but never really found a solution for it. Can someone help?
Click to expand...
Click to collapse
I had the same problem.Make a back up of your phone
and do a factory reset.
tried installing usb drivers sgain ??
Sent from my GT-I9300 using xda premium
try installing Kies?
Its ok i got it to work. Went into download mode and plugged into my PC and windows installed some drivers, Odin detected the phone just fine. Then i booted up into android like normal but switched to PTP mode, windows then installed the MTP drivers (though it was already installed) then after that all worked well again
Please help...
Im having the same problem. But nothing seems to work for me. Tried everything possible. Re-installed drivers, connected in download mode, installed Kies, reset to factory setting..ALL TO NO AVAIL. I keep getting 'USB device attached to this computer has malfunctioned...' message...
The solution isnt always the same for all users.. Fortunately mine was fixed by a simple driver install. I remember browsing the internet and found out that there is a way to fix it but it requires simple adb commands and the Android SDK.
winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
vsp33ddyv said:
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
Click to expand...
Click to collapse
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Ghand0ur said:
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Click to expand...
Click to collapse
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
vsp33ddyv said:
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
Click to expand...
Click to collapse
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Ghand0ur said:
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Click to expand...
Click to collapse
Still can't read it...
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
911jason said:
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
Click to expand...
Click to collapse
YES THIS IS WHAT WORKED ONLY I DID SOME OTHER STEPS TOO!!! Now I got adb running again and I can only push , I'll explain later in a full tutorial how to fix this now you guys can help me , I'm trying to download a cyanmod for my HTC because the stock is german and I can't download it , so can anyone upload the cyanmod endeavouru for me I keep getting error 502 bad gateway I almost fixed it !!!!! I need it badly !
OOkay so I thought I had figured it out , I uste TWRP to push files from PC to my Phone , then I installed cmw and tried to install the ROMS , but apperantly my roms were deleted. (I can't use TWRP because I need touch and the touch doesn't work , while in cmw the touch does work)
So if we can fix the TWRP touch I will know how to fix my problem !
I fixed the problem
I fixed the problem , thread how comming soon !
Here is my thread http://forum.xda-developers.com/showthread.php?p=52550145
Hi,
I was able to install custom rom on my v300s
but found out that twrp wasn't installed.
I used my computer adb to open twrp and installed custom rom
Then i found our something was wrong, any way to install twrp from now on?
i tried to open twrp with adb again,
when i use adb devices I was able to find lge~~~ on there.
but when i try fastboot boot twrp, it shows awaiting for devices then nothing happen
(I set my phone as ptp mode then usb debugging was on.
on my laptop the phone was resister as portable device and using MTP usb driver, wasn't able to change it to adb driver)
then i tried to boot my v30 as bootloader but pressing volume down key didn't work.
any way to install twrp from this state?
sorry for my bad English
I think you need to ensure you have the correct drivers installed. Even when they are, you need to also check in Device Manager that the correct driver is used when the phone is connected. It also sounds like you don't have USB debugging enabled.
ldeveraux said:
I think you need to ensure you have the correct drivers installed. Even when they are, you need to also check in Device Manager that the correct driver is used when the phone is connected. It also sounds like you don't have USB debugging enabled.
Click to expand...
Click to collapse
Ah the usb debugging was enabled.
I found something called qfil from qualcom and was able to reinstall my bootloader img file with it.
then i was able to connect my device as ADB devices
Thanks btw