A
AC Question
I've got a galaxy s6 and am slowly going nuts. Initially, when plugging my phone into my labtop (dell xps, windows 10) an error would appear, error 42.
Something to the effect of, "your device malfunctioned and is not
supported by windows"
Now, my computer won't recognize the phone at all. It does charge, but makes the charging and then immediately after, the uncharging sound when I plug it in.
I've been troubleshooting for a week, and tried the following all to no avail:
1. a factory reset to windows 8 (!)
2. unchecking and rechecking the usb in bios
3. uninstalling the usb under the device manager
4. installing samsungs 's connect'
5. different usb cords including the original
6. unpluging computers power source
7. doing a hard shut down (as opposed to a restart) of PC
8. calling*#0808# from the phone
9. installing media feature pack N&KN
10. switching the usb debugging mode
11. samsung's new 'usb' driver released 2 weeks ago
12. testing multiple usb inputs
13. making sure the phone is unlocked
I'm been using airdroid to get around this problem, but would really like to get to the bottom of it. I thought for sure samsung's new driver would do it, but no dice.
Something to the effect of, "your device malfunctioned and is not
supported by windows"
Now, my computer won't recognize the phone at all. It does charge, but makes the charging and then immediately after, the uncharging sound when I plug it in.
I've been troubleshooting for a week, and tried the following all to no avail:
1. a factory reset to windows 8 (!)
2. unchecking and rechecking the usb in bios
3. uninstalling the usb under the device manager
4. installing samsungs 's connect'
5. different usb cords including the original
6. unpluging computers power source
7. doing a hard shut down (as opposed to a restart) of PC
8. calling*#0808# from the phone
9. installing media feature pack N&KN
10. switching the usb debugging mode
11. samsung's new 'usb' driver released 2 weeks ago
12. testing multiple usb inputs
13. making sure the phone is unlocked
I'm been using airdroid to get around this problem, but would really like to get to the bottom of it. I thought for sure samsung's new driver would do it, but no dice.