Database Users

[Q] Micro USB port not working

hello,
mi micro USB is not working propperly right now, for some reason it doesn´t charges correctly, it seems a little... "loose"... im currentl running CM 9 2012/05/26
and when it plugg it in the computer and manage it to start charging, it wont allow me to acces it as a mass storage device, in fact the computer wouldn´t recognize it at all!, any help!?

try another cable, or connecting it to other port after rebooting (usb musnt be connected)
Swyped off my Amazing Defy using ICS

happened with me too, got its motherboard replaced

crap... I`m rooted... so no warranty...
maybe in some repair shop of cellphones the will be able to replace it?
but.. did yours charged at all?
bacause mine does charges when appropietly connected... its just that sometimes it wont nad it will not allow me to get to the mass storage...

If your phone just charge but can't access to masive storage, look in the device manager , if you have a MTP device, your micro ubs port is fine, just try to install some stock rom.

it´s just that some times it doesn´t charges and I need to slowly start trying to adjust the micro USB port so it can charge... that´s why I say that it seems to be a little loose...
As well it will only charge when plugged into my XboX 360 or the computer (and some other devices) but not when plugged into the Stock charger... :S
Jkmoran said:
If your phone just charge but can't access to masive storage, look in the device manager , if you have a MTP device, your micro ubs port is fine, just try to install some stock rom.
Click to expand...
Click to collapse
now, exactly who should I look in the device manager if its MTP?
t

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

USB not working for flash
Hi everyone, I came with a similar issue.
The massive storage USB connection is not working for me, plus I can't flash a stock rom,
Currently I'm in MIUI for defy (and it's the only option I am able to install), I tried to wipe data cache to install cyanogenmod 7 from recovery but it's not working, it get stuck in the boot logo. I want to install cyanogenmod because it is fast than MIUI jelly bean.
My idea is to flash the device, but with the usb not working Im stuck,
any ideas to solve this? or should i go to have the usb repaired?

GabrielMercado said:
Hi everyone, I came with a similar issue.
The massive storage USB connection is not working for me, plus I can't flash a stock rom,
Currently I'm in MIUI for defy (and it's the only option I am able to install), I tried to wipe data cache to install cyanogenmod 7 from recovery but it's not working, it get stuck in the boot logo. I want to install cyanogenmod because it is fast than MIUI jelly bean.
My idea is to flash the device, but with the usb not working Im stuck,
any ideas to solve this? or should i go to have the usb repaired?
Click to expand...
Click to collapse
If after a boot in bootloader (power+vol-up) and connecting to PC via usb cable nothing appear onto PC display 3 possibilities exist.
1. Usb cable is broken.
2. Pc have no usb driver foryour device (but even in this case a error message appear)
3. Usb connector or circuitry fron Defy is broken.
Search.

Hi mates !
Please have a look to this fix: http://forum.xda-developers.com/showthread.php?t=2516956
I haven't picture posting permissions right now, but should be fixed soon

CJPJ said:
Hi mates !
Please have a look to this fix: http://forum.xda-developers.com/showthread.php?t=2516956
I haven't picture posting permissions right now, but should be fixed soon
Click to expand...
Click to collapse
Yes, is OK your method but is a little dangerous if you not cover the cleaned pins with some resin. More safe is to use a toothbrush soaked in isopropyl alcohol or 98% ethylalcohol to clean the soldered pins.

del//

[Q] USB Mount or Mass Storage not working on MT4G

The probem:
USB Mass Storage not working in Recovery. I tried everything, reflashing different recovery but its not working, it doesn't give an error message. When card is not inside however it does complain. SdCard is fine because I can flash zips that are on it. Tested on both windows and ubuntu. tried another card as well
USB Mount doesn't work in CM7.2 or any rom or nand restore i've done recently. I had Insomnia at some point, then inferno, then cm 7.1, none of these restores work. Again here no errors, I do not even see the sign for usb detection. usb debugging is enabled/disabled no difference. phone however still charges though.
I'm on a trip right now, but I've not had the chance yet to get another usb cable but the two I have dont work.

katsumeiyo said:
The probem:
USB Mass Storage not working in Recovery. I tried everything, reflashing different recovery but its not working, it doesn't give an error message. When card is not inside however it does complain. SdCard is fine because I can flash zips that are on it. Tested on both windows and ubuntu. tried another card as well
USB Mount doesn't work in CM7.2 or any rom or nand restore i've done recently. I had Insomnia at some point, then inferno, then cm 7.1, none of these restores work. Again here no errors, I do not even see the sign for usb detection. usb debugging is enabled/disabled no difference. phone however still charges though.
I'm on a trip right now, but I've not had the chance yet to get another usb cable but the two I have dont work.
Click to expand...
Click to collapse
Its either your USB cable or your phone USB jack mine does the same thing I have to wiggle it to get a good connection cuz my USB cable sucks cuz with others it recognizes it right away.

...Awesome... said:
Its either your USB cable or your phone USB jack mine does the same thing I have to wiggle it to get a good connection cuz my USB cable sucks cuz with others it recognizes it right away.
Click to expand...
Click to collapse
He has tried two cables, so I would tend to lean toward the port.
Sent from my HTC Glacier using XDA

i am in the same boat. looks like my charging port is bad. anyway to replace the charging port? i am not good with soldering

it's not ur usb port
it's htc.. htc devices doesn't support usb host feature.
If you have a rom and kernal that do support usb host then try powering the usb as the htc devices do not provide power out.. use usb Y cable

tempuser2005 said:
it's htc.. htc devices doesn't support usb host feature.
If you have a rom and kernal that do support usb host then try powering the usb as the htc devices do not provide power out.. use usb Y cable
Click to expand...
Click to collapse
What? He isn't trying to host the connection. He is trying to use his phone as a USB mass storage device.
Where did you get USB host from in his questions?
Sent from my HTC Glacier using XDA

Hi all,
I am having the same problem, except perhaps with a different cause. My user account on Windows 7 became corrupt and I can no longer log in, so I had to create a new one.
On the new account, my myTouch 4G is not recognized for mass storage/disk drive mode via USB. The USB cable does work, the port is okay, and I've used both with other devices. The myTouch shows as charging when connected to the computer. I have uninstalled and reinstalled all of the myTouch drivers, restarted computer and phone, to no avail.
When it is connected in USB, it shows as generic "Drive F" and is inaccessible. When I check properties it says mytouch4g. When I check "Devices" it is recognized as portable storage. I have tried with USB debugging on and off, and have set "connected to computer" mode to disk drive.
Any thoughts? I thought possibly loading the generic ADB driver again might help, but I cannot get to the stage where I can force it to load that driver instead of the HTC one.

[Q] Upgraded to CM10, lost all usb charge / data connectivity!

Hi,
So I upgraded from cm7.2 to 10 on my defy green lens. After a long and difficult upgrade, almost everything works - except any functionality of the usb port...
I'll jump right into the real deal: without usb connectivity, I cannot try to flash other SBFs to fix it! I can enter the bootloader screen just fine (says 09.10 on top, I believe that the last SBF I flashed was 3.4.2_179-002 , as recommended, before I rooted it, 2ndinit, and sucessfuly installed cm10) and the phone recognizes when I plug in a usb cable to it. but the computer always shows up a "usb device not recognized" error, and I tried on two machines, winxp/win7, and several different usb cables. I read some threads about crashing drivers between rsdlite and different tools motorola made; I never installed any of that junk but just to be on the safe side I removed all drivers and started fresh. still no go.
______________(That's the problem, now I'm just going to give more information about it)______________
The phone does not charge off a computer nor from a wall charger, with an assortment of different usb ports, cables and chargers. when connected to a computer (whether the phone is on or off) a "usb device not recognized" message comes up, on both windows xp/7 (different machines.) Seldom, when connected to wall charger, I can get the battery icon to show charging for about a second, (after a restart and plugging in to the pc briefly beforehand.) If I'm so lucky to make that happen, either it goes off in about one second, or it will change statues from charging to not charging several times very rapidly and then stay on not charging.
If the phone is off and I connect it, the white led sometimes come on, and then the phone comes on- presumably to go into battery charging screen, but instead it boots up normally. (this may be the correct behavior with this rom. idk.)
If you care for more information, let me elaborate about what I mean by "After a long and difficult upgrade":
I previously upgraded to cm10 (30/7/2012) CM10-20120730-NIGHTLY-mb525.zip,
but downgraded shortly after, back to 7.2. (I decided to wait for something a bit more functional)
Back then both the upgrade/downgrade went fine. This time I got into a bootloop (or stuck on bootscreen) after updating to 26/03/2013 God's version (oops I meant Quarx's version.)
Trying to use my nandroid backup for 7.2 I got a md5 mismatch and even after generating a new md5 file I couldn't restore /data.
Moving on. using CWM I tried installing some kernels (kernel-froyo-222-179.zip, and same thing but signed,),
then a fixed sbf (not full) 3.4.2_177-Fixed.NORDIC_DEBLUR.sbf,
and a very crappy sbf JRDNEM_U3_2.26.0_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B5TEL02A.0R_USAJORDANTELSTRA_P033_A017_M008_HWp3_Service1FF.sbf
** this one almost gave me a heart attack, after successful flash defy black screened with no LED indications. I was able to work my way into the bootloader and flash another SBF with rsdlite, without any indications from the device. lucky me.
Then I flashed the sbf I mentioned above and that's how I eventually got into cm10.
I can't even downgrade to stable cm7.2. Tried flashing a fresh install through CWM (wiping everything before and after, of course) and ended up stuck on boot screen. I don't know if it has anything to do with CG numbers or what, but I really can't figure out why CM7.2 wouldn't boot on the same SBF CM10 is booting fine right now.
I can't also share the SD card through CWM. (-> device not recognized)
I'm losing my marbles over here. Been working on it for two whole days and can't think of anything else I can try out... If I flashed the wrong rom using CWM I might get locked out because bootloader won't be any help!
:crying: cry for help... thanks :fingers-crossed:

Have you tried installing adb and the motorola drivers so you can try to communicate with the device?

Thanks for your word zero gravity!
Well, I thought that since "usb device not recognized", and since it shows up as unknown device under device manager (currently it disappears and reappears every 3 seconds, but I think this is a new behavior) I automatically assumed that I couldn't get proper communication with it! I guess I got to do some reading about adb commands any help with it would greatly be appreciated (No worries though I know how to google )

http://forum.xda-developers.com/showthread.php?t=1241935
Here's a simple guide for adb. Hopefully you can get some sort of communication to flash your stock sbf and start over again.

So, even though I have the drivers installed (Motorola_End_User_Driver_Installation_4.9.0_32bit.msi_.zip, and also installed MotorolaDeviceManager_2.3.9.exe,) Android SDK Tools installed, then I tried adb devices - nothing comes on.
by enabling ADB over network I can adb connect to the phone through wifi and go into shell. but I can't see how I can debug the buggy usb interface with network access.
Also tried starting the adb service through recovery - no go, won't show up.
(I plugged in a different Android phone (an Xperia), installed the drivers and had it running on adb usb in no time. So I'm doing it right.)
Any thoughts? are there commands to specifically listen and figure out what's coming from the usb port?
any other leads anyone may have? I'm listening!
Cheers, Shawn

The port must have suffered hardware damage. Examine the port for obvious conductivity hindrance. If not I'm afraid you'll have to get it repaired
As for cm7.2 after flashing just format to ext3 from boot menu(before this wipe dalvik cache), and after a reboot wipe data from stock recovery for good measure
Sent from my MB526 using xda premium

Well, thekguy seems to be on the right track.. I can fiddle around with the usb plug and get it to charge, So the problem seems to be mostly physical - if not completely.
I still can't get it to connect properly to the computer, but go figure which usb signal is dropping off. might be power, might be data.
After spraying it several times with contact cleaner the port is good enough for steady charge. No change about how it doesn't connect to a computer.
I feel like a dumbass, cus I already gutted the phone up a couple of days ago to try tracing conductivity paths through the port. the usb port is cast in plastic that is not removable from the pcb. There's no access to the USB pins, excepting four conducting points through the plastic right next to the port, but they are all connected to ground - they probably belong to a bracket that's holding the plastic to the pcb.
anyhow I did all that (I got closeup pictures if anyone's interested) but I wasn't able to check conductivity, and I didn't try fiddling with it after that. bah!
___________________________
Still wondering about one thing! The bootloader is locked, so that means it was never-ever changed since the phone was manufactured, correct? So no effect of writing different SBFs on the bootloader, correct? (minding the Efuse and CG numbers)
if so, than can I conclude only by that information (and that I cannot connect the phone to the computer anymore with bootloader) that there must be hardware/physical damage? I've just completely eliminated the software factor out of the equation. haven't I?
Did I miss anything? let me know.
P/S, I'm going to stick with this phone as it is. I can work around never having usb data connection.
Cheers

Can you try installing Linux and see if the you can mount /system or even /sdcard on Linux from bootmenu? Bootmenu mount only works in Linux. I've tried it in Ubuntu 10.10
Its worth a try, if Linux doesn't see it then it must be a hardware issue and would need a Motherboard replacement.
Use ubuntu live disk to make things easy and not mess your Windoze
Sent from my MB526 using xda premium

You're right, sbf flashing cannot break usb functionality. I'm not very well versed in mobile hardware but I think the port can be replaced, though I don't know how. It may be possible that a local mobile store could fix it.
Trying Linux is a good idea, though it may not work out from the looks of it(the phone)
Sent from my MB526 using xda premium

If anyone is reading this, I had some bad batteries and a usb port that is having physical problems. I'm flashing it with contact cleaner spray every now and again and it helps. I can get a usb connection to the computer and charge it with a bit of luck and while I keep it stationary.

USB error 43, can't figure it out.

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--

PC won't recognize Note 4

Have a note 4 on a custom rom- android kitkat. Was working fine, until i wiped data/cache a few times in TWRP recovery to do a clean install of the rom. Phone restarted without an OS, and then i couldn't get pass the boot logo screen. Couldn't flash any rom in recovery. So i did a restore thru TWRP from a backup. So now the phone boots, but it pc won't recognize it. Everytime i plug it, I get "One of the USB devices attached to your computer has malfunctioned, and Windows does not recognize it". Under device manager, I get "Unknown USB Device (device descriptor request failed)".
Things I have tried:
-Uninstalled usb drivers and let windows reinstall,
-at least 5 different usb cables
-at least 3 different Samsung oem usb cables
-other usb ports on the PC
-3 different pc (all with same- so im guessing its a problem with the phone)
-physically tried to push up the usb port on the phone- bad connection (someone recommended on google search)
- even when as far to reinstall windows OS
-*#0808# and set it to AP, MTP + ADB
-yes usb debugging is enabled
-download mode (odin does not see the phone, so cannot flash stock/custom rom
-diferent versions of odin
-different version of Samsung usb drivers
-have other samsung phones (note 5, and s6) and windows recognize those.
-phone does charge thru usb
need to get phone working again
-

Download stock rom from sammobile and flash it via odin.
Or else, flash the cf auto root file via odin, this reset all partitions.
Reporting Via N910G.

yashthemw said:
Download stock rom from sammobile and flash it via odin.
Or else, flash the cf auto root file via odin, this reset all partitions.
Reporting Via N910G.
Click to expand...
Click to collapse
You might try reading the whole post, rather than just replying.

JagDave said:
You might try reading the whole post, rather than just replying.
Click to expand...
Click to collapse
Sorry, my bad.
So, the author can try to repair partitions via twrp.
Go to wipe/advanced wipe and then select "Repair or change file system".
Select the partitions and repair them.
Reporting Via N910G.

Honestly man search my username ziggsta2 I had the same issue I had to buy another note 4 and even this used phone I got off eBay has the same problem when I wiggled the micro USB cord up and down I got it to connect, I don't suggest you doing this, but what might work is taking a very small piece of plastic and cleaning out your USB port on your phone, I believe these ports go bad after awhile as I have encountered this twice on two separate devices maybe you have a different issue but theres my two cents

ziggsta said:
Honestly man search my username ziggsta2 I had the same issue I had to buy another note 4 and even this used phone I got off eBay has the same problem when I wiggled the micro USB cord up and down I got it to connect, I don't suggest you doing this, but what might work is taking a very small piece of plastic and cleaning out your USB port on your phone, I believe these ports go bad after awhile as I have encountered this twice on two separate devices maybe you have a different issue but theres my two cents
Click to expand...
Click to collapse
i have tried. at this point i think it's hardware failure with the usb port. Stupid buying those cheap usb cables probably damaged the port because it seems to require a little more force than samsung cable. Planning ordering one and replacing. hopefully i don't do more damage. Had this phone for a long time and miss flashing roms on it.

i have still not fixed this problem....lol. had a new phone and been in drawer. did replace the usb port but it wasn't the problem. would like some solutions if anyone can help.

jxlee0215 said:
i have still not fixed this problem....lol. had a new phone and been in drawer. did replace the usb port but it wasn't the problem. would like some solutions if anyone can help.
Click to expand...
Click to collapse
Replace the battery