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 connection problems, root, and cwm

Hello. I bought a Fascinate on craigslist like a week ago. I plugged it into my Ubuntu laptop and nothing came up, nothing even on `lsusb`. So I figure I'd just go ahead and follow the steps. So heimdall complains it can't find any devices. Also note, I am using a generic MicroUSB cable bought on ebay. [And also, I have also tried a LG microusb cord, no luck with that either]. My generic cord works to connect my Droid X2 absoultely fine.
So then I checked my syslog, and I got USB error messages [cannot enumerate usb port, etc]. I tried it in Windows and it said "The usb device has malfunctioned and is not recognized." So I call Samsung, they say I have a warranty thru this month [December], and I say I want to send it in for repair and they say I cannot unless I have the OEM cord and then they will troubleshoot via the phone, and if it still fails, then they will arrange it so I can send it in for repair/evaluation. So I look on Amazon and I find I can get one for only $1.50, no big deal. So I ordered that on Tue. and was expecting it to come today and it hasn't. Probably will arrive Monday.
So anyway, I had found some white gunk/lint out of the Fascinate's usb port, and I was getting sick of waiting for my OEM cord to come in the mail, so I figured I might try taking a brush and gently try to clean it. I find a small dental brush and I clean the port, going in and out on both edges, in the middle, and I did that for 10-15 seconds.
The moment of truth! I plug it in, and it shows up! I was so happy. First thing I do is load up the Fascinate "full upgrade guide" on Cyanogenmod wiki. I download and untar cwm4-bml-i500.tar, then turn off my phone, plug it in holding the Vol Down button, and it goes into Download mode. `lsusb` shows a Samsung device, and so I type in heimdall flash --recovery recovery.bin. The blue bar on my device goes all the way up, and the heimdall on my terminal showed 100%, and then I think it rebooted. So I think "I have CWM installed now." So I downloaded CM 7.1 for my fascinate, transferred it to my sdcard, and try to figure out how to boot into CWM.
I failed a few times, and I looked it up and it says you have to hold both volume buttons.
So I hold both volume after turning my phone on [while plugged into my laptop, because for some odd reason it always shows an "empty battery" animation and will not boot if not plugged in] and it loads the recovery.
First I thought my CWM version was old, because I could not install a zip from the sdcard, it only let me use "update.zip". So I renamed the file on my sdcard, went back into [what I thought was CWM] and it says the signature failed, and it could not install. Then I realize I must be in the stock Recovery mode.
Next, here are the error messages:
Code:
Dec 10 15:12:53 dv6 kernel: [ 482.350279] usb 5-3: new full speed USB device using xhci_hcd and address 12
Dec 10 15:12:53 dv6 kernel: [ 482.350783] usb 5-3: Device not responding to set address.
Dec 10 15:12:54 dv6 kernel: [ 482.560668] usb 5-3: Device not responding to set address.
Dec 10 15:12:54 dv6 kernel: [ 482.770314] usb 5-3: device not accepting address 12, error -71
Dec 10 15:12:54 dv6 kernel: [ 482.770409] hub 5-0:1.0: unable to enumerate USB device on port 3
That's my 3.0 USB, on my 2.0 USB it says
Code:
Dec 10 15:17:58 dv6 kernel: [ 786.540313] usb 3-1: new low speed USB device using ohci_hcd and address 32
Dec 10 15:17:58 dv6 kernel: [ 786.960277] usb 3-1: device not accepting address 32, error -62
Dec 10 15:17:58 dv6 kernel: [ 787.130185] usb 3-1: new low speed USB device using ohci_hcd and address 33
Dec 10 15:17:59 dv6 kernel: [ 787.550167] usb 3-1: device not accepting address 33, error -62
Dec 10 15:17:59 dv6 kernel: [ 787.550233] hub 3-0:1.0: unable to enumerate USB device on port 1
Alright, thanks for reading all that. Now, here are some questions I hope someone will be able to answer.
Is CWM installed? If I send it in, will Samsung say my warranty is void because I installed a custom recovery rom? Because I can't boot into CWM so I'm thinkin it didn't install.
Next, what is the cause of the error messages? 1/2 hour ago, after cleaning the port with a brush, it worked. I was able to upload cm7 to my sdcard. Then it just quit working. Any ideas?
One last thing, I tried z4root. I clicked "permanent root" and then it got to 'acquiring root shell' and then it just quits, not force close, it just closes and I'm dumped back into my app drawer. I thought 'hey maybe it worked' so I installed ROM Manager and then it says I'm not rooted.
So if I send it in, will Samsung say I've voided my warranty? And why didn't the CWM install work? Or is it installed, and I'm just doing something wrong? Thanks!
Matt

Check out the guide by Droidstyle. It is very simple and covers everything. Good luck.
Sent from my SCH-I500 using XDA App

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

Unknown USB Device (Device Descriptor Request Failed)

Hello guys,
after trying everything I could imagine and find on the net, I still didn't get my PC to recognize my S6 edge plus.
Hopefully someone od you has got some more ideas.
The Problem:
Connected Phone shows "Unknown USB Device (Device Descriptor Request Failed)" in the device manager. No MTP connection and no ADB possible so far.
Done so far:
Samsung USB Mobile Drivers
Kies
Smart Switch (with reinstall of drivers)
6 different cables with 4 PCs (2 Win10, 1 Win7, 1 Linux)
USB-Debugging on / off
*#0808# switched through every mode
USB-Hub drivers
Factory Reset
More Info:
5 of the 6 cables are working just fine for data connection with my S3
There is no infobar tooltip to change USB mode at all, just telling me it's loading
In Download Mode the phone doesn't get recognized by Odin (with same cord and USB Port the S3 does)
In Stock Recovery Sideload Mode the Device does not show up in adb devices (with same cord and USB Port the S3 does)
Regards

up

I'm guessing you have downloaded and installed the Samsung drivers?

New Infos on this case:
Local tech support inspected the phone. They suspect the mainboard to be defective due to corrosion signs.
Of course the repair cost would be ridiculous.
I'm gonna repair it myself, but I'm not quite sure if it's really a faulty mainboard.
I rather think of changing the USB board first, because it's like a 10th of the mainboard and more likely to get wet if that's the reason for the damaged phone.
Any ideas??
Regards

You didn't mention if it charges via USB?

Im in the same situation..
charge via usb but is not able to recognize the phone in any computer (a lot of different cables with 3 PCs)
My unit was wet and i think that something is wrong for this reason.

Hello friend my s6 edge plus demo with smokkierom last day not working ota,
I have activate developer mode for check control usb, but not have possibility for change other mode. Is fixed to mtp mode and not possible change other type.
I have deleted more app. And have chek update for play store.
I have press multiple tap and have activate developer mode to play store.
My idea is phone have one one virus....ajaj
I have reboot the phone with charger connected, and at reboot I have recevied FRP LOCK!!!!!!
Question one.... is possible recovery data?
A this time need connecting with Odin for upload twrp... but pc not find my phone!!
Working only charging.
And have error unknow devices. And not install driver..
Device not have USB ID and PID
My phone have hardware problem?
Best regards thank s help support

Fix
Cento50 said:
Hello friend my s6 edge plus demo with smokkierom last day not working ota,
I have activate developer mode for check control usb, but not have possibility for change other mode. Is fixed to mtp mode and not possible change other type.
I have deleted more app. And have chek update for play store.
I have press multiple tap and have activate developer mode to play store.
My idea is phone have one one virus....ajaj
I have reboot the phone with charger connected, and at reboot I have recevied FRP LOCK!!!!!!
Question one.... is possible recovery data?
A this time need connecting with Odin for upload twrp... but pc not find my phone!!
Working only charging.
And have error unknow devices. And not install driver..
Device not have USB ID and PID
My phone have hardware problem?
Best regards thank s help support
Click to expand...
Click to collapse

Cento50 said:
Fix
Click to expand...
Click to collapse
Hi Cento50. Have You managed to get the phone to work? At first my phone was showing up in "This PC" on Win 10. but after trying Samsung usb drivers to get Odin3 working now it is the same as Yours. Shows in Device Manager as: Unknown USB Device (Device Descriptor Request Failed). A strange Conundrum.

Hello @Photobil2012 yes fix habe worked!
One little wire have replaced 2ohm resistor.
And have fix fast charger and data comunication with PC!
We i have repaced first one diode.
Phone a this time work complete.
First this problem i have connected one hard disk to otg cable with phone battery low!
My suggestion Please caution to use otg interface with high current if have low battery in the phone.
This cause high current drain and possibile burn diode and resistor.

Hi Cento50,
Alright! Thank you very much for the most timely reply and tech info on the successful fix. This is very good news to receive. I just replaced the battery so it is brand new and that works fine now. However, if it is necessary I can apply the same type of fix that you applied. Great work, and thanks again for your help.

Axon 7 - misflashed...

Hi all,
its a horrible day, after having done wrong (seems so...)
The following situation:
Had on my Axon 7 A2017G the ResurrectionRemix 7.0.2, then wanted to flash the TWRP 3.6 (wanted to try Lineage 17.1) - but after that nothing works:
Normal booting goes up to the lock screen, with the number field, and then nothing more.
Recovery doesn't seem to exist anymore, all possible key combinations for EDL/Fastboot/whatever never lead to a message...
Via adb I get so far, but there the device is marked as "unauthorized".
Can't change that with the tips either, because I can't get to the "Developer options".
And that's why in the MiFlash tool (neither Linux nor Windows variant) there is no way to get into EDL mode.
With Vol+ and Power I do get to the black screen with the lit LED, but MiFlash always wants to go into Fastboot mode, the Axon7Tool keeps saying "Device not detected". But it is detected by the Linux PC:
[ 1280.749935] usb 2-1.2: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 3.18
[ 1280.749940] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1280.749942] usb 2-1.2: Product: ZTE A2017X
[ 1292.958442] usb 2-1.2: USB disconnect, device number 12
[ 1334.979634] usb 2-1.2: new high-speed USB device number 13 using ehci-pci
[ 1335.090998] usb 2-1.2: New USB device found, idVendor=19d2, idProduct=0112, bcdDevice= 0.00
[ 1335.091005] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1335.091009] usb 2-1.2: Product: QUSB__BULK
[ 1335.091013] usb 2-1.2: Manufacturer: Qualcomm CDMA Technologies MSM
How do I get the device "Authorized" or otherwise into EDL mode?
I have a complete Backup of all prttions done with TWRP before "killing" Axon and my mood...
Or can anyone think of anything else?
In hope...
Bommel

It doesn't matter if I press Vol+, Vol- or both when the device is on - the ZTE logo appears, then the black screen with the red LED....
Basically the QUSB_BULK appears under "other devices", I specially set up a Win 7 computer with SP1 fresh and installed the Qualcomm USB drivers (Win 32).
On Linux the same as written in the first post.
Meanwhile, the login screen is also no longer shown, but only the black screen.

Ah. Was able to enter EDL mode again, now, with next cable flashing stock was successful...
TWRP, restore from RR-backup, all doing as before...
But next case arrived.