Related
Hi All, I've got a USB connection problem with my Galaxy Nexus. When I connect it to a computer, it will start charging, but doesn't show that it's connected to a computer and the computer doesn't show that a device is connected. I've tried on a few different Windows machines and don't get any change in the device manager. There is no "unknown device" nor device with an error. I've been searching the Internet and this forum, but still can't find the problem after a couple of days. Here's some details and things I've done:
I did not install the "force fast charge" kernel mod.
I've tried a couple different cables and verified that the cables worked with my wife's Galaxy II.
I've tried several different computers.
I've tried MTP and PTP storage options.
I rebooted everything several times.
I drank heavily.
I tried a factory reset.
I updated Windows Media Player to get the latest MTP software.
I installed drivers packages even though it never gets to the point of installing drivers.
Does anyone have any other ideas before I smash this thing with a hammer?
Does anyone have any ideas? At this point, I'm thinking there is a hardware problem.
Go into Menu -> System Settings -> Developer Options -> Turn on USB Debugging.
Not a guarantee, but something to rule out.
I've got USB Debuging on. Thanks for the reply.
Can anyone help? I'm having the same exact problem. My phone charge but is not detected by my computer. I am having this problem right after flashing AOKP ROM B35. This is very important, one mistake and my phone will be bricked as a computer to phone is so important !! There is nothing detected at all under device manager. Tried it on several laptop to make sure it isn't just my computer.
someone?
Uninstall the drivers you have for the s2. Reboot and install the official drivers for the galaxy nexus. Reboot. Then try.
If that doesn't work... let the phone load a while and just keep trying other ports on the computer. I saw this with my other gnex that it would take a while to realize a USB to be connected. Also make sure the USB is in completely... don't jam it in but make sure you know its All the way in. ( no pun intended) What's funny is my gnex will detect it instantly... but the other one takes a few tries.
Sent From My Sprint Galaxy Nexus via Xda Premium
Thank you dude. It doesn't work. Prior to installing this rom, my nexus is detected instantly. There is something wrong with the process i root or something. Now i can't do anything as It is not detected by my computer. Someone please help.
Indeed is the rom that is causing the problem. I opened NEXUS toolkit and rebooted my phone into boot image. It will sense it and i can operate from there. I've restored to factory and now my phone is being detected. I hope the thread starter gained something out of it too
Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.
You may not want to try this either but try a system restore
Sent from my SPH-L710...if some one helps you press the thanks button
Volknochi said:
Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.
Click to expand...
Click to collapse
I had the same issue what ended up fixing it for me was watching when I plugged the phone in after a clean driver install and stopping Windows from downloading and installing an updated driver. Dont know if its the same for you but that fixed it for me. I was really frustrated by it and found no help either.
probably an easy fix
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.
I won't do a system restore, that won't do anything. Not to mention it would erase some programs that were installed (not related to phone). So, not doing that. Also, my computer will not automatically update any drivers or any thing else, as I have it set to manual mode.
And, I do not have Kies installed. It never worked for me properly, when it came to driver installation. I've done the "go into device manager" bit many times before, it still likes to play the "Hardware ID doesn't match" card. Drivers won't install either. I don't know what it is, but damn this is the most stubborn thing I've ever encountered.
i've post this in other forums today. what i do to get it working is i toggle USB debugging and try it out, then start toggling the ptp and mtp until it works. the combo that works for me is turn on debug, plug in computer, unplug, turn off debug, plug in. if it doesnt work then i toggle back and forth MTP and PTP. 5 tries at most, for me. Also, i did a nandroid back to my oem ICS that was 2 weeks old and just rooted. the problem is worse there. i'm using freegsmr6 with trinity kernel on Tmo. hope it helps.
Ditto
Yeah that whole "Hardware ID missing" was an irritating situation. This is what I recommend as far as making it work.
1. Plug in.
2. When you get the error message, I think its because of a conflict with the ADB interface. Go to Settings, Developer Options, and check off USB Debugging.
3. Plug in once again and it should work. If not, try toggling between Camera and MTP.
I have Windows 7 Ultimate and it works fine for me
I always get that error as well with my SGS 3. I have to reinstall Kies everytime it does that which is annoying.. ANyone has a permanent solution about this?
Fix for me was...
1-plug in phone. Get the hardware ID message. Leave phone plugged in.
2- open device manager. Click on. Android Phone and Uninstall Samsung Android ADB Interface. Also check the "delete software driver" when the dialog box shows.
3-still in device manager. Scroll down to Universal Serial Bus Controllers. Uninstall Samsung Mobile USB Composite Device.
4-unplug phone.
5-reboot pc.
6-install SAMSUNG USB drivers from their site or from here
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
7-reboot or not. Plug in phone.
This worked for me and no issues for the last 6 days. YMMV..
this works!
stevounit said:
yeah that whole "hardware id missing" was an irritating situation. This is what i recommend as far as making it work.
1. Plug in.
2. When you get the error message, i think its because of a conflict with the adb interface. Go to settings, developer options, and check off usb debugging.
3. Plug in once again and it should work. If not, try toggling between camera and mtp.
I have windows 7 ultimate and it works fine for me :d
Click to expand...
Click to collapse
But why this problem now out of nowhere when everything worked fine before.
Sent from my SPH-L710 using xda app-developers app
Hardware ID missing - SOLVED!!
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
UPDATE!! (Oct.11.2012)
After a few Kies updates and going through various ROM's:
- the procedure listed above works 100% but a few steps are just not needed (redundant) - see bellow
- the problem is mostly caused by Windows "forcefully" trying to install its own drivers, rather than allowing Samsung's suggested.
- Samsung's fault is providing "updated" drivers that don't always work (hence, use the suggested 1.4.6.0 drivers)
- Following EVERY Kies update, DISCONNECT from internet before plugging your phone (otherwise you'll have to go through this, AGAIN).
Some suggested here that plugging the phone into a different USB port (without disconnecting from internet) would be the culprit - which happens to be true, but as a mere effect, not the cause: every time an unknown device is plugged into a different USB port, Windows is trying to download/install the appropriate drivers if it doesn't recognize the hardware - and there you are again.
So, the simplified procedure becomes:
1. Not needed - leave Kies installed, as is - no harm at all
2. N/A
3. YES
4. Not (always) required
5. MUST
6. MUST
7. MUST
8. Yes
Furthermore, if still interested in connecting your I747(M) as UMS (USB mass storage) the solution presented here works. I tested it myself - read my comment on this post for the very few existing hiccups.
- while installing the USB mass storage device drivers you don't have to disconnect from the internet
Install Drivers
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
For someone experiencing the "hardware ID missing" error, just reinstalling the drivers won't do anything. Like many others, I've been banging my head trying to solve this for quite some time; the suggested steps are truly a compilation of successful ideas and trials mingled with tons of frustration, coming from my own experience as well as from many different people and forums.
If, on the other hand, you had a different type of connectivity issues - without this error, then, yes, reinstalling the drivers is Samsung's recommendation.
billard412 said:
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.
Click to expand...
Click to collapse
Just wanted to say thank you. Did this and the last 2 days, works everytime. I made sure that after the first time I plugged the phone in after doing all this, and the screen pops up asking what I wanted to do, made sure to check the box for "do this everytime" and then choose the view folder option or whatever that is.
Thank you again,
Whiteice
One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.
nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thank you so much for this. This solution worked for me.
nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thanks for this i will try it tomorrow as still new to these tabs.
For moment i change to camera PTP and it pops up, so at least i can use it for now.
Will let you know how i get on.
Best wishes :good:
adamspud said:
One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.
Click to expand...
Click to collapse
The Android Developers toolkit DOES install the USB drivers 1.4.6.0 - which seems to be the ONLY one that works, BUT the rest of the steps suggested in my previous post are needed in order to get rid of the problem - otherwise the fix is just temporary.
Re-loading OS drivers corrected issue.
tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
I removed the updates to Kies on my Note and uninstalled the Kies update on the PC which is what started this issue of the OS not recognizing the device and then a fresh driver load for my phone from the Samsung site. Worked Perfectly, Thanks!
Cowoholy
I'm trying to root my Samsung Galaxy SIII, and whenever I try to connect it to my laptop, it gives me the "USB device not recognized" error. I have tried everything I can think of.
Kies uninstalled, registry cleaned, searched my computer to erase every file linked to Kies, and no dice.
Installed, uninstalled, reinstalled, re-uninstalled, re-reinstalled drivers. Nothing.
After every driver change, rebooted computer and phone, nothing.
Factory reset the phone since one post I found had that work, still nothing.
So right now I have a laptop with no Kies, Samsung drivers installed, a factory reset phone, and the USB cable still won't work. It is the cable that came with the phone. The phone is Android 4.1.1, an SGH-I747, build number JRO03L. This is extremely agitating since I can't even connect my phone to see the files on it! I had a Motorola Atrix and had a similar problem, but fixed it with a simple driver reinstall. I've even gone into the hidden code menu and set the USB mode to MTP+ADB, and the UDAP (or whatever) is set to PDA. That won't even work. At this point, I'm willing to do anything. I hate stock ROMs, and want to remove all the crap this phone has on it, especially that damn voice thing and Kies.
self bump, since it's been three or four days with no reply. I could really use advice on this.
In your laptop, when you go to Devices manager, do you see an unknown device? If you try searching online for the appropriate driver through Windows Update, does it find any helpful driver?
CTurmoil said:
I'm trying to root my Samsung Galaxy SIII, and whenever I try to connect it to my laptop, it gives me the "USB device not recognized" error. I have tried everything I can think of.
Kies uninstalled, registry cleaned, searched my computer to erase every file linked to Kies, and no dice.
Installed, uninstalled, reinstalled, re-uninstalled, re-reinstalled drivers. Nothing.
After every driver change, rebooted computer and phone, nothing.
Factory reset the phone since one post I found had that work, still nothing.
So right now I have a laptop with no Kies, Samsung drivers installed, a factory reset phone, and the USB cable still won't work. It is the cable that came with the phone. The phone is Android 4.1.1, an SGH-I747, build number JRO03L. This is extremely agitating since I can't even connect my phone to see the files on it! I had a Motorola Atrix and had a similar problem, but fixed it with a simple driver reinstall. I've even gone into the hidden code menu and set the USB mode to MTP+ADB, and the UDAP (or whatever) is set to PDA. That won't even work. At this point, I'm willing to do anything. I hate stock ROMs, and want to remove all the crap this phone has on it, especially that damn voice thing and Kies.
Click to expand...
Click to collapse
I was dealing with this on my Win7 rig, and came across some advice that helped. If you have an SD card installed, turn the phone off, remove it and then reboot and connect the phone to the computer. I don't know why it worked for me, but it did.
Good luck to you.
CTurmoil said:
I'm trying to root my Samsung Galaxy SIII, and whenever I try to connect it to my laptop, it gives me the "USB device not recognized" error. I have tried everything I can think of.
Kies uninstalled, registry cleaned, searched my computer to erase every file linked to Kies, and no dice.
Installed, uninstalled, reinstalled, re-uninstalled, re-reinstalled drivers. Nothing.
After every driver change, rebooted computer and phone, nothing.
Factory reset the phone since one post I found had that work, still nothing.
So right now I have a laptop with no Kies, Samsung drivers installed, a factory reset phone, and the USB cable still won't work. It is the cable that came with the phone. The phone is Android 4.1.1, an SGH-I747, build number JRO03L. This is extremely agitating since I can't even connect my phone to see the files on it! I had a Motorola Atrix and had a similar problem, but fixed it with a simple driver reinstall. I've even gone into the hidden code menu and set the USB mode to MTP+ADB, and the UDAP (or whatever) is set to PDA. That won't even work. At this point, I'm willing to do anything. I hate stock ROMs, and want to remove all the crap this phone has on it, especially that damn voice thing and Kies.
Click to expand...
Click to collapse
Possibly two things download revouninstall to uninstall your drivers it searchs bolth registry and system for left over files (delete them)
I had same problem all I did was use revouninstaller to uninstall old drivers (it scans entire system and registry for left overs. a must.
Then I used these drivers, also when letting your installing drivers (turn internet off) don'lt update them there older, but they work for everyone who does this. If you need a better guide search there is one somewhere but point is use these drivers and don't update them (smile) works with adb everything you won't see a difference these drivers work better. peace.
Drivers------>Samsung Drivers 1.4.6.0 search for 1.4.6.0 drivers samsung fix for more info later
search for revo uninstaller
Whenever I have this problem, I must manually install the driver.
Open device manager.
Go to the unrecognized device that you know is your phone.
Properties and "update driver".
Tell it you have your own driver.
Don't let it "search" for a driver.
Manually point it to the exact driver file you need.
Works every time for me.
I took out the SD card to try all possible solutions posted.
Uninstalled drivers and installed the older versions that one of you linked me to, didn't help.
Tried directing Device Manager to install the driver manually, but I have no idea where to find it. If you have the driver file or at least the name and version, I can get it and use that.
I can't believe how much trouble it is just to hook an android phone to a computer, this happened with my Atrix as well.
Have you tried and different cable ?
So I was having a problem with my laptop recognizing my S3 when connected via USB. The notification would not appear in the status bar that a connection was made, and neither Fedora Linux or Windows 7 would recognize that the device was connected. I tried reinstalling Kies/drivers under Windows, and checking the output of dmesg/lsub on Linux. Nothing.
Did some googling and found this thread that help solve the problem!
http://blog.vacs.fr/index.php?post/...ot-detected-problem-on-Android-Samsung-phones
I found the problem. It was the cable. Somehow, it was severed where the cable connects to the mini-USB connector. I discovered this when the entire mini-USB piece fractured and fell off, revealing the tangled and snapped wires. I went today to AT&T to buy a replacement, and it worked on the first try. I don't know how the cable got damaged like that without being detected, but there we go. Now how do I set a question as resolved?
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Hi i have a similar problem as you, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
bigillz said:
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
Click to expand...
Click to collapse
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
I am confused what you mean by calculator, I am on Win 10 and have a similar problem, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
thank you very much. it worked.
Hi
I would appreciate any input/help on this issue.
I bought the Korean Note 10 + 5g exynos (SM-N976N), specifically for the purposes of being able to root it. I would prefer to use the Magisk approach, because I would like to be able to use Google Pay, amongst others
Try as I might, I cannot get my PC to "see" the android phone. I have engaged developer mode, checked USB debugging, checked the the USB connection as MTP mode, and gone through several cables, going by the advice of "experts" I consulted. I even went as far as returning my original phone and buying a new one, again, on the advice of an "expert" who determined that my original phone was faulty (unlikely, since I had literally taken it out of the box and attempted the rooting before trying to load my multiple software). I am using Windows 10, 64k, with all current Microsoft updates.
I have reloaded the Samsung USB drivers, rebooted both the phone and PC several times, to no avail. When I connect, in download mode, the USB cable between the two devices, I hear the "ping" on the PC, indicating that the two have made contact, but then - nothing. I have established that the cable works fine, by connecting my Note 8 to the PC, where it shows up as a device with two drives (int and SD card)
I have installed Magisk on the 10+, and modified the stock ROM with Magisk, and then copied that over to the PC, as advised by the rooting solution; the problem is that I cannot use Odin to flash that modified ROM because Odin does not recognize any phone attached to it!
Help, Please!!
Could be the Odin version your using
Perhaps, I hadn't thought of that. I am using 3.13.1. Do you have a suggestion about using a more stable/useful one? My only issue with your answer is that it's not just Odin that isn't responding- it's the entire computer - it's as if the phone doesn't exist when connected.
I'm guessing you are using a USB 3.0 port on pc? If you have access to USB 2.0 try that....
Next thing I'd suggest (with note plugged in while in download mode)....go into device manager (right click This PC)
Find device under Modem, open properties Ports tab, Advanced Settings and manually change the port setting to a lower port assignment (preferably between 1 & 5). Reboot pc and just for kicks reset the phone into Download Mode again....Give odin a try now.
Hope one or a combination of these methods help.
Sent from my [device_name] using XDA-Developers Legacy app