Database Users

[Q] Half-bricked phone (USB isn't working)

Hi all
my USB doesn't seem to work anymore. However I don't believe it is a HW failure.
In Linux, when I connect my I9000 to usb, I see the following in the syslog:
Oct 14 17:17:29 xsdnied kernel: [ 1222.601065] usb 3-1: new low speed USB device using uhci_hcd and address 3
Oct 14 17:17:29 xsdnied kernel: [ 1222.670996] hub 3-0:1.0: unable to enumerate USB device on port 1
This happens both in "Download mode" and if I boot in OS and choose "Mass storage for USB", also in Debug Dev Mode ON.
Also in Windows Odin can't see the device via USB. Windows at least told me under certain condition that a new USB device detected but it failed to recognize it (albeit all needed drivers have been already installed)
The phone is working, but I can't even install CM7.1 on it because of signature verification error that seems to be unavoidable under <3e>.
Any idea how to fix this situation?

have u tried a different pc?

hezibanda said:
have u tried a different pc?
Click to expand...
Click to collapse
I've tried two. at least one of them was already working via usb with this I9000 both in windows and linux

Have you reinstalled the drivers, or tried another cable?

Talon26 said:
Have you reinstalled the drivers, or tried another cable?
Click to expand...
Click to collapse
I've tried another cable. I connect/disconnect several times and once of 20 attempts Windows makes its usual USB-discovery sound, but then says something like: USB-device is either broken or device is not recognized.
Well, just took another SGS1 that we have in our family and tested -- both cables are 100% OK.
Hm, maybe USB is indeed broken and that's it :-/
But how? why? Charging after all works.

Got the same problem bro...
One contact broke on the USB port, bricked my Phone too. I wasnt able to use odin to flash my Phone. The crazy thing is that my phone was able to charge but no connection to the PC.
I sent the bricked phone to an thrid partner from samsung, they flashed my phone and repaired the USB port. No is everything okay.
I tried several things to get the USB to work, nothing helped.

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

[Q] Nexus 4 gone stealth

... and is no longer recognized when connected to a computer via USB, meaning I can't return to stock to get ready for the Lollipop OTA.
Got a rooted Nexus 4 running the latest PA beta.
What happens when connecting to PC:
- On two different Windows machines: systray popup saying "USB device not recognized. The last USB device you connected to this computer malfunctioned etc.". In device manager it says "Unknown USB device (device descriptor request failed)"
- On elementary OS, based on Ubuntu 12.04: nothing, besides charging.
No USB debugging connection notification on the Nexus 4 either when plugging in.
What I've tried (USB debugging enabled, all relevant drivers installed):
- Settings > Storage > USB computer connection > check Camera PTP (used to be required in order to get an RSA key prompt when connecting to a computer, now it does nothing)
- Flashing latest stable CM to see if PA was to blame. Made no difference.
- Uninstalling device through device manager in Windows and reconnecting. No effect. Driver update doesn't work either, finds nothing.
- Using Wugfresh's Nexus toolkit to see if that worked, but that obviously doesn't work either when the device isn't recognized, same with the Universal Nexus Linux Toolkit on Linux.
- Scouring the net for solutions and coming up with nothing
I have flashed factory images before on this phone without problems. Should I consider it a hardware failure by now, or is this a known issue with a fix?

Try a new wire, different usb port on computer, finally look into cleaning your charging port on the phone/replacing it.

DrFredPhD said:
Try a new wire, different usb port on computer, finally look into cleaning your charging port on the phone/replacing it.
Click to expand...
Click to collapse
Tried three different cables, every port on two laptops, no joy - my girlfriend's phone connects normally.
Wouldn't replace the charging port, then I'd just get a new phone since it's a 2 years old Nexus 4. If only there was a way to flash the factory image using only TWRP.

bimsebasse said:
Tried three different cables, every port on two laptops, no joy - my girlfriend's phone connects normally.
Wouldn't replace the charging port, then I'd just get a new phone since it's a 2 years old Nexus 4. If only there was a way to flash the factory image using only TWRP.
Click to expand...
Click to collapse
Flash this in twrp http://forum.xda-developers.com/showthread.php?p=47476426
Sent from my Nexus 5 using XDA Free mobile app

Thanks jd1639, that seemed to be exactly what I was looking for -
- but then I had an extremely blonde moment and formatted everything in TWRP, wiping the ROM I was gonna flash in the process, on a device where USB file transfer doesn't work anymore
My phone is now a paper weight.

Have you tried the file manager in twrp yet? I've found it connects when nothing else will...

[Q] Recover Phone Only Sideload Available

I have brought this up in a couple other threads but it was suggested I start a separate question. It's a good suggestion especially because doing so may help others in the future. Here's the situation. I have a VS980 that HAD TWRP and CrDroid. In the process of trying to flash another ROM, something went haywire. When I use Vol Down/Power to get to Recovery I get the Factory Data Reset screen which unfortunately says "ROOTED" at the top. Pushing power twice which would ordinarily get me to TWRP instead gets me to a LG Logo/Reset endless loop. The button combination which would usually get me to download mode gets me the same loop. However, if I continue to hold down Vol Up, I get Android System Recovery <3e> from which I CAN get the phone into sideload mode. Sideload is thus the only connectivity I have to the phone. Ordinarily I would think I could just sideload a ROM but when I try this, I get:
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error in /tmp/update.zip
(Status 7)
Installation aborted.
Likewise I tried a bumped recovery, but this time it errored with /tmp/panelfix.sh.
Yes, sideload appears to be the only choice I have but I also confess I am not entirely clear on what bumping is exactly and how to do it.
Absent reviving this phone, I am stuck returning it to Verizon for a warranty replacement but this presents a problem since the factory data reset screen clearly says rooted. One thought that came to mind is if I got the official OTA zip that gets downloaded during OTA updates, I might not be able to sideload that and whether or not doing so is advisable. Any and all suggestions are greatly appreciated. Although I prefer being able to use Windows on my PC, I do have access to an Ubuntu VM I can run if that factors in at all.
Thanks in advance...

In an effort to further troubleshoot, since I now have 1 working LG G2 and the aforementioned misbehavor I was wondering if it would be possible to adb sideload from the good phone to the bum one and if so are there any particular apps or drivers needed (besides a terminal emulator)?

gospodinwizard said:
I have brought this up in a couple other threads but it was suggested I start a separate question. It's a good suggestion especially because doing so may help others in the future. Here's the situation. I have a VS980 that HAD TWRP and CrDroid. In the process of trying to flash another ROM, something went haywire. When I use Vol Down/Power to get to Recovery I get the Factory Data Reset screen which unfortunately says "ROOTED" at the top. Pushing power twice which would ordinarily get me to TWRP instead gets me to a LG Logo/Reset endless loop. The button combination which would usually get me to download mode gets me the same loop. However, if I continue to hold down Vol Up, I get Android System Recovery <3e> from which I CAN get the phone into sideload mode. Sideload is thus the only connectivity I have to the phone. Ordinarily I would think I could just sideload a ROM but when I try this, I get:
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error in /tmp/update.zip
(Status 7)
Installation aborted.
Likewise I tried a bumped recovery, but this time it errored with /tmp/panelfix.sh.
Yes, sideload appears to be the only choice I have but I also confess I am not entirely clear on what bumping is exactly and how to do it.
Absent reviving this phone, I am stuck returning it to Verizon for a warranty replacement but this presents a problem since the factory data reset screen clearly says rooted. One thought that came to mind is if I got the official OTA zip that gets downloaded during OTA updates, I might not be able to sideload that and whether or not doing so is advisable. Any and all suggestions are greatly appreciated. Although I prefer being able to use Windows on my PC, I do have access to an Ubuntu VM I can run if that factors in at all.
Thanks in advance...
Click to expand...
Click to collapse
It's looking like [APP][4.0+] Craze - ADB Toolkit may be of some use here.

gospodinwizard said:
It's looking like [APP][4.0+] Craze - ADB Toolkit may be of some use here.
Click to expand...
Click to collapse
Doubt it. That just looks like an app built ontop of ADB.
Just in case you see replies before PMs, I sent you a PM with a modified CM11 zip. I bumped the boot.img and removed the asserts in the install script. Basically, it wont check your device to make sure it's right before installing/bring forward GAPPS/or check that the OTA is correct. None of these matter in your situation, and the errors they might give would just be a nuisance.
That zip if for VS980. I saw your profile says verizon, so I assume that's the right model.

/dev/sda
/dev/sda1
/dev/sda2
/dev/sda5
Nope not mounted as a device (ls -1 /dev/sd*)
Bus 001 Device 005: ID 1004:631f LG Electronics, Inc.
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Obviously it sees the phone (lsusb)
[ 1536.349950] usb 1-1: >new high-speed USB device number 5 using ehci_hcd
[ 1536.898447] usb 1-1: >New USB device found, idVendor=1004, idProduct=631f
[ 1536.898455] usb 1-1: >New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 1536.898460] usb 1-1: >Product: LGE Android Phone
[ 1536.898465] usb 1-1: >Manufacturer: LG Electronics Inc.
[ 1536.898468] usb 1-1: >SerialNumber: 094bbeb261899279
Again, it clearly sees the phone (dmesg).
So the question remains....why can I neither mount the phone or successfully sideload to it?

Unbrick J320FN ?

Hi all,
Someone just give me my first samy device.
It is a J320FN. I cannot get a response from it.
After some tries it show on lsusb:
Code:
Bus 006 Device 010: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
I tried kies 2 (see screenshot) and Kies 3 but both answer no connection.
The win device manager show something about a missing driver for 'MTP' device.
On the linux host it expose some serial device:
Code:
[ 3134.991753] usb 6-1.1.2: USB disconnect, device number 9
[ 3285.036152] usb 6-1.1.2: new high-speed USB device number 10 using ehci-pci
[ 3285.129517] usb 6-1.1.2: New USB device found, idVendor=04e8, idProduct=6860
[ 3285.129521] usb 6-1.1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 3285.129522] usb 6-1.1.2: Product: SAMSUNG_Android
[ 3285.129524] usb 6-1.1.2: Manufacturer: SAMSUNG
[ 3285.129525] usb 6-1.1.2: SerialNumber: 420090a9e02ca300
[ 3285.130283] cdc_acm 6-1.1.2:1.1: This device cannot do calls on its own. It is not a modem.
[ 3285.130349] cdc_acm 6-1.1.2:1.1: [B]ttyACM0: USB ACM device[/B]
Id like to fix that device to be able to help porting rom on it.
Please let me know any advices.
Thanks in advance

Install official phone drivers from Samsung. Kies doesn't work with newer phones. Does the phone boot , or show the logo? If yes use Vol- and Home and Power button at same time to get in download mode . Then flash the recovery with ODIN (in AP tab) and flash ur custom rom after wiping system,data,preload,dalvik,and cache partitions
Also use a real Windows machine,might help.

FrostOnXDA said:
Install official phone drivers from Samsung. Kies doesn't work with newer phones. Does the phone boot , or show the logo? If yes use Vol- and Home and Power button at same time to get in download mode . Then flash the recovery with ODIN (in AP tab) and flash ur custom rom after wiping system,data,preload,dalvik,and cache partitions
Also use a real Windows machine,might help.
Click to expand...
Click to collapse
Thanks for the answer. Looks like it was another problem.
I made all the process to flash through download mode and, except the screen who keeps black, looks like the process went fine.
Now, after a bit of time, I can hear the volume sound while pushing volume button, etc....
Looks like the device lcd is broken.
Thanks for your answer.

nailyk said:
Thanks for the answer. Looks like it was another problem.
I made all the process to flash through download mode and, except the screen who keeps black, looks like the process went fine.
Now, after a bit of time, I can hear the volume sound while pushing volume button, etc....
Looks like the device lcd is broken.
Thanks for your answer.
Click to expand...
Click to collapse
No problem. Sorry to hear the lcd is broken. Good luck fixing!