My AT&T sgh 1337 Galaxy s4 has been a great phone, it was Loki'd back before the bootloader lock OTA's hit and I've been running CM11's latest milestone releases.
Lately I have had issue with my USB jack. When I would plug it in, I would just get an Error code 43 Unknown Device in windows, no device detected in linux & mac. I tried 3 different USB cables. I cleaned out the USB jack, didn't help. I did notice the interior of the jack was a bit worn and torn. It charges fine.
I went ahead and ordered a new USB jack/microphone board, verified the new part is specific and exact to the sgh-1337 model and installed it.
Plugged into a charger and tested, charging works, ~1300 mah draw on a 1.4amp charger. Looks good.
Plugged into a PC and immediately got Error code 43 USB device unrecognized. Still doesn't work. I changed USB modes in Settings>Storage>menu and, nothing. I enabled and disabled USB debugging several times. I've tested my machine with all samsung & ADB drivers installed and fresh machines, nothing. (Windows made the USB connect/disconnect sound between switching modes every time)
I installed Drivedroid (very sweet app for hosting disk images over USB) and used its settings panel to change USB modes, every single USB mode reports error 43.
Booting up into Recovery and mounting USB mass storage mode, same thing Error 43.
Booting into Download mode: Error 43.
USB OTG cable with mouse plugged in: nothing.
Is it possible that the USB controller on my phone's main board died? I hope not, that's unfortunate. It'd be hard to find a bootloader-unlocked motherboard replacement.
I read that an HTC user had the exact same problem, he reflashed his bootloader image from SD card and BAM, usb came alive again. I don't think that'd be a possibility with a samsung device though... hmm. Bummer, anyone think they can help?
I appreciate you reading.
wow, sorry to here that--could be hardware, you did about everything you could do--
Here are Google links which I am sure you already looked into
https://www.google.com/?gws_rd=ssl#q=usb+code+error+43+fix
Wild ideas--wipe your internal, reformat external or boot without it
Odin the MDL tar back to stock, keeping same bootloader
Odin and upgrade to NC1 with new bootloader
Use wifi apps for transfers
Not much help I know--just throwing stuff out there--:good:
Good Luck
Worst case lots of new phones out this fall--
Related
Hey guys,
Just recently, my PC and any other PC Ive tried for that matter will not recognize my Note 3. I had Windows 7 and it worked fine for months, then just the other day it came up on the bottom as USB Device Not Recognized, and no matter what I do it will not do so. Yesterday, I upgraded to Windows 8.1 and still the same result. I have installed Kies 3, uninstalled and resintalled Samsung drivers and still nothing. I am running a custom rom in the stock slot using Safestrap...is it possible that that might have messed up something? Even when the cord is plugged into the PC, the phone doesnt come up with anything notification that it's plugged in, but it does say it is charging. If any of you have any tips or something please help because I am at my wits end.
Thanks
Have you tried with another cord?
Computer doesn't see device... Device doesn't detect plug in... Sounds like a bad USB cord
b00mb00mchuck said:
Have you tried with another cord?
Computer doesn't see device... Device doesn't detect plug in... Sounds like a bad USB cord
Click to expand...
Click to collapse
Yes, actually I have and still nothing...forgot to mention that in the original post.
It's a strange problem which leads me to believe that something has gone wrong in the phone, or that I caused something to go wrong by flashing a rom or three, since it did work previously. Unfortunately, I'm at status: Custom, although my Knox is 0x0.
When you dial ##366633# is it disabled?
Sent from my Galaxy Note 3
mexiking713 said:
When you dial ##366633# is it disabled?
Sent from my Galaxy Note 3
Click to expand...
Click to collapse
Yes, this shows as disabled. What should this be?
Can't help you solve your problem, but last night I had a hiccup where I plugged my (17 day old) N3 into my computer in a USB2 port and ... nothing at all. (As if it were electrically disconnected - no "unknown devices" showing)
Tried it in a different USB2 port, and ... nothing.
Tried in in a USB 3.0 port - same computer, same OEM cord - and everything was fine. As far as I knew, nothing had changed on either end of things, although the previous evening I had used a different OTG cable for a USB key with the phone, and I had also had a automatic update of the Samsung Push Service on the phone. Nothing had been plugged into the PC's usb ports since it's prior cold boot. (Win 7 x64 Pro).
This morning (both PC and phone have been rebooted), everything is back to normal - both on the phone and the PC. Both the USB2 and USB3 ports all seem fine.
Ugh. Makes me nervous - brand new hardware.
Boot into Odin mode THEN plug the device in, let windows find the drivers for it then once that's done, reboot the phone regularly and see if it works then. It appears to be an issue with most to ALL Samsung devices, but this worked for my wife's galaxy S3 when the computer wouldn't recognize it and the phone didn't detect a PC connection.
Sent from my SM-N900V using xda app-developers app
pmt223 said:
Hey guys,
Just recently, my PC and any other PC Ive tried for that matter will not recognize my Note 3. I had Windows 7 and it worked fine for months, then just the other day it came up on the bottom as USB Device Not Recognized, and no matter what I do it will not do so. Yesterday, I upgraded to Windows 8.1 and still the same result. I have installed Kies 3, uninstalled and resintalled Samsung drivers and still nothing. I am running a custom rom in the stock slot using Safestrap...is it possible that that might have messed up something? Even when the cord is plugged into the PC, the phone doesnt come up with anything notification that it's plugged in, but it does say it is charging. If any of you have any tips or something please help because I am at my wits end.
Thanks
Click to expand...
Click to collapse
Did you fix this problem?
Thank you! Worked perfectly!
I have the same problem, do you have any solutions ? Thanks.
I too have been struggling with this problem. The is no USB symbol in the notifications area on my phone whether I plug into to my computer at work (Win7) or at home (Win7), using a usb3 cable or a usb2 cable. Its as if there was a setting on my phone that allows recognition when plugged into a computer that has been turned off.Is there such a setting? I would love some help on this as well. Thanks in advance! I am rooted with towel root and have had no problems until last week. When I look in the device manager on my computer it shows :
SAMSUNG Android Phone
SAMSUNG Android ADB interface
I tried uninstalling the above and then plugging my phone back in and it re-installs the same driver shown above.
For what it is worth here are the drivers for SAMSUNG Android ADB Interface:
c:\windows\system32\DRIVERS\winusbsys
c:\windows\system32\WdfCoinstaller01007.dll
c:\windows\system32\WinUSBCoinstaller.dll
Should I be using different drivers ? Thanks|!
please help!
any solution yet? i have same problem, no usb detection and camera wont work i want to flash stock rom whit odin but i cant get the computer to recognize my phone...
I was able to fix the usb recognition problem. i had to do a factory restore. I lost root but gained usb recognition AND the Over the Air update to 4.4.4 and patiently awaiting the update to 5.0 hopefully this month!
Hi i have a nexus 7 (2012) everything was working fine until android 5. The device was slow and almost unusable. Then the 5.0.2 update came out and guess what? I updated it and now my laptop wont recognize the device so i tried a different cable and nothing. I plugged the nexus 7 in my second computer and nothing not even the sound that means you plugged something in the usb port. So i went to my brothers house and tried his computer.... the same... nothing. We plugged his nexus 7 (2012) 5.0.2 wich is the exact same device as mine and it works so we thought that it was the usb connector on the device and we switched my connector with his....NOTHING happens. computer wont recognize the device, no sound, no pop-up, no ADB detection. Does anyone have the same problem or a solution on how to downgrade 5.0.2 back to 4.4 without usb cable?
Thank you
Did you tried out to start n7 into fastboot mode and recovery mode?
Is usb not available also there?
fastboot and recovery mode also has no USB. absolutely nothing happens. when i connect the device it charges but the lightning icon does not appear on the battery in the status bar. and its not the usb port on the N7 i changed it.
?????????????????
Same here
I have the same Problem - a N7 GSM with 5.0.2 and no communication via USB.
I have tried different computers with Win7 and Ubuntu14.10. As well as differnt cables. (And all combinations of that work with my HTC M7, by the way)
Under Linux, not even lsusb shows the device, or dmesg shows any connection to a usb device.
To be completly honest, I did not give much love to my N7, I have been using it hardly. But when I did, I have been flashing some differnt Roms and testing different bootloaders so this might be some kind of my fault.
i updated to 5,1 and still the same problem so i assume its hardware related. but i know it is not the USB connector because i tried it on my brothers N7. and it works
Mine is quirky, comp recognizes it and can order boot but sideload and push to device don't work. Its odd.
Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Does adb see the device
jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.
crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?
Hello XDA, my virtual phone heros, i appreciate your good work, i am reading here for a few years as a ghost and today i signed up because i am lost with a serious problem on my Note4 N910C (English is not my native language)
THE CONDITIONS AND ENVIRONMENT:
My Phone was first running on stock Lollipop 5.1.1 when i rooted it over ODIN 3.10.6 with space X kernel and CF Autoroot, SuperSU then i flashed the latest TWRP...
After that i flashed a Custom Rom: Sweet_ROM_V17.1_COJ2_N910C...
Everything was running flawlessly for about 2 weeks...I installed Titanium Backup, Xposed, Xprivacy Pro, Busybox and a lot more and made a complete TWRP Backup then, it was running like a charme...The backup is fine because when i messed up my phone through trying harder xprivacy parameters and other tweaking i needed to set it back by TWRP into the old state...
Nothing happened after that, it was running 100% for over a week of heavy usage...
THE PROBLEM:
The one morning i took it from the charger with 100% Battery and went to work...
Before the error occured I did some searching on the internet, used chats. movies, nothing special this day, USB Debugging was On, i remembered something messed up my chrome browser like this ad hijackers, i set it back by erasing data,cache of chrome in the app menu, then there was nothing else strange i remembered, my AF Firewall was closed, only Whatsapp and Browser were allowed to going through...
The same day in the afternoon i tried to use my car charger to recharge my Note 4 as usual, but this time it wasnt recognizing the charger and my first thought was that the charger is faulty or the cable, so i turned off the phone by the androids power menu...I retried loading my battery In the phones off state but when i plug in the charger, the battery symbol came up for short and then it remained dead, it s the same scenario until today, so i used my powerbank to try charging, because the powerbank has an indicator to show the loading state and everytime i plugged it in, it came up for short, battery symbol shows up for a few seconds, but no percentage or animation is showing as usual and no red LED, then its switching off, the powerbank LED indicator stops the loading state after a few seconds, so the loading current stops...
At home i tried the stock charger and it remained the same, since that, i have to charge the battery outside the phone...
The strange thing is:
The Rom is still booting fine, TWRP is booting, but its not going into download mode from Androids Power Menu like before, its always just rebooting back into android if i choose download mode and i have to take the battery out and back in and hit the download mode pattern Vol- Home Power, to enter Download Mode and even the booting into Download mode from TWRP gives the same strange results:
On my Laptop i started the device manager to see the USB hardware string parameters after a windows popup was telling me something like "Device not recognized"
The USB Driver ID dont fit the old right driver ID, it seems to be empty and the port is not communicating anymore
since the charging bug occured,( Everything worked fine the day before.)
I tried my Laptop to narrow down the bug with the same driver i used for flashing phones (S6,910F,910C) over ODIN and my Lappy has USB 2.0 and USB 3.0 ports.
I always used the same USB 2.0 port for ODIN and other MTP stuff, but since the bug showed up the 910C is not recognized at the USB 2.0 Port anymore, seems to be dead in the devices manager table, only the USB 3.0 Port shows it as unknown device with a strange empty ID --> I tried the other devices like the N910F and G920F that are still recognized by ODIN on the same USB2.0 and 3.0 Ports both with the same USB hardware strings, its just the N910C that isnt recognized anymore, in no mode, no ADB, MTP, no download mode, everywhere the same, USB is bricked! Windows finds no driver and says its no info avaiable on this device so I tried to force the right driver to run with the wrong buggy driver ID but its not communicating, ODIN indicator and log remains unchanged...So it seems to be the same situation like other people getting from killing the bootloader by bad flashing, the only difference is that my phone is still booting fine into recovery and even Android but with no charging. My USB Port is totally useless now, its like if Samsung or Google OTA update has overwritten my bootloader or something hidden in the rom that woke up to kill my mods i dont know and now.
PS: Things i tried so far with no results on fixing my issue....
1. Complete fresh reinstall of Sweetrom, 2. Flashing another kernel...
3. Roll back to my TWRP Backup of perfect running ROM but with no USB support anymore:
The Phone remains in unknown state, not affecting ODIN to switch into flash mode
I am sure its the bootloader, since its battery bug is still occuring while the phone is in off state...
Unable to tell the charger the right ID without USB communication...
i was wondering if there is a solution to make a bootloader hotflash from out of Android or something like getting me back on stock first with download mode, forcing the USB ID or communication with a tool out of android, SD card boot image like on note 3 whatever, please tell me! I cant find something related to my USB and Charging ISSUE
PLEASE HELP ME, I am lost
Still the same. It's booting fine, USB2.0 no reaction on the laptop in Fastboot/Adb/Mtp ... On USB 3.0 Device remains unknown with strange Device ID String in windows 10 hardware Manager... Forced the old formerly working driver, but Odin can't find it anymore... Adb, Mtp, fastboot don't work, no communication... USB Cid is hard bricked, Charging never works in no state, just showing up for a few seconds in off state while plugging it in for short.... Bootloader must be damaged, fastboot and twrp can be started with dead USB... So is there a way to run a boot image to fix my bootloader from SD card, Aroma, or like OTA Updates are flashing? If Samsung and Google apply bootloader updates over OTA and simply restart, why we can't do that??? I need a new bootloader, is there any way without USB?
Greetings,
Thank you for using XDA Assist.
I have moved your question to your device's Q&A forum. You'll receive expert advice here. Good luck!
Fixed!
The problem is the USB Connector Port itself, figured it out after bending the inner contacts up with a flat screwdriver and cleaned them. Before that i always tried the same gently with no change, but please do it at your own risk only. After searching for many hours about possible reasons for the problem, I came to the conclusion to even compromise the Port and heavy bending it up, now it's charging! I will exchange the port soon and change the frame too to have it back like as new... OK, if anyone in the future have problems with the bootloader or USB hardbrick n910c, feel free to ask me, I upgraded my knowledge on many causes now
Thank you very much
My 2cents stick to one charger. Do not share that charger with others.
The worst culprit are the cheap china car chargers.
I went thru two USB ports on my first phone to figure this out.
Ever since I have adopted the policy of using only one cable. Never had this issue.
I've got 5 S7s on my desk, all Canadian variant, all from the same manufacturer all the same model. - SM-G930W8
All are recognised by my PC but one and I can't work out why not!
Plugging the phone into the PC makes no noise from the PC but the phone seems to detect a regular charger not a PC.
I have plugged it in using different cables including the one in its box and the ones used on other devices that were recognised and only this phone doesn't work with any of them.
I have plugged in, unplugged and rebooted many times.
I have set the USB configuration to MTP (Media Transfer Protocol)/Transferring files.
USB Debugging is ON and OEM unlocking is ON.
I have tried booting into stock recovery and wiping cache AND factory resetting.
When phone is turned on "adb devices" returns nothing.
I have installed Samsung Kies and Samsung Smart Switch to reinstall the drivers.
NOTHING IS WORKING!
All threads I find tell me to do the things I have listed above and have people saying these have worked but all of them I had already tried and double tried and nothing is working.
The cables are correct and working with other S7s of the same model.
All the correct drivers are installed and have been uninstalled and reinstalled.
All the correct setting are selected and OEM unlock and USB debugging enabled.
Phone was fresh out the box as were the other four and all cables.
Samsungs apps installed on PC to ensure best drivers installed.
Would really appreciate some guidance or consolation that its not something stupid I'm doing! I work with these phones everyday and this has never happened! Just banging my head against a brick wall trying to resolve it
maybe faulty usb port, my nephew had S6 with the same issue, service replaced usb port and it started
to work with PC.
try download mode and see if odin see your phone.
try to move the cable a lil bit and see if sth appears for a second.
yaro666 said:
maybe faulty usb port, my nephew had S6 with the same issue, service replaced usb port and it started
to work with PC.
try download mode and see if odin see your phone.
try to move the cable a lil bit and see if sth appears for a second.
Click to expand...
Click to collapse
Thanks but unfortunately Odin doesn't recognise in download mode.
Could it be a USB port problem if I used the same port for the other 4 devices and have no issue?
I'm considering sending the phone back to manufacturer to be honest I think it may just be a faulty device or something!
I bet its microusb port fault
Had a similar issue on Windows 10 , if that's what your running let the phone be connected, uninstall the driver from device manager, and then install driver select have disk and select the basic mtp , if this doesn't help connect to Microsoft support and they'll guide you through it , worked for me , my phone used to detect on other laptops but mine , also I could connect other phones on mine but not my phone, hope this helps
same issue here