Situation: My fully stock, no root, gt-i9195 was restarting last week shortly after an OTA update from 4.4.2 Kitkat to 5 Lollipop. The initial error message was "failed to mount /data (invalid argument)". I read up on ROM flashing and tried to connect to Odin 13 and 9 using Windows and ADB using Debian and got messages indicating that the phone is not being recognized by the USB. I used multiple cables and all different USB ports on three different PCs with the same result. This prevents me from flashing TWRP.
dmesg is showing this error:
usb 2-1-port4: attempt power cycle
usb 2-1.4: new full-speed USB device number 19 using ehci-pci
usb 2-1.4: device not accepting address 19, error -32
usb 2-1.4: new full-speed USB device number 20 using ehci-pci
usb 2-1.4: device not accepting address 20, error -32
usb 2-1-port4: unable to enumerate USB device
Any ideas? Thanks in advance!
Cheers!
Related
I have following problem:
Today i bought new usb cable, as oldr one was in bad state and did not charge phone. When i connected it to pc with new cable, phone charged properly, but was not recognised by pc. I tried on win 7, win 8, still nothing. Updated htc sync manager, didnt help. Cant update drivers, as i get message: "drivers are up to date: unknown device". Currently I download ADT bundle, maybe it will help.
In device managed phone is listed as unknown device in universal serial bus controllers , and under its state there is error 43.
When i connect phone using old cable, everything is fine(except charging ofc).
Can anyone help?
mwys said:
I have following problem:
Today i bought new usb cable, as oldr one was in bad state and did not charge phone. When i connected it to pc with new cable, phone charged properly, but was not recognised by pc. I tried on win 7, win 8, still nothing. Updated htc sync manager, didnt help. Cant update drivers, as i get message: "drivers are up to date: unknown device". Currently I download ADT bundle, maybe it will help.
In device managed phone is listed as unknown device in universal serial bus controllers , and under its state there is error 43.
When i connect phone using old cable, everything is fine(except charging ofc).
Can anyone help?
Click to expand...
Click to collapse
i would say that you bought a defective cable
I'm trying to salvage some important files from a dead HTC One X (stock everything) - from what I've been told, it was in use and suddenly turned off. After attempts to charge the phone etc. to no avail (monitor does not turn on, no LEDs turn on at all) it was sent for repair with the instructions to not proceed if they could not salvage the files. The repair shop opened the phone, molested some plastic parts and sent it back in two parts, stating that they could not proceed further without loosing the data on the phone. I have no idea what they tried, so I'm hoping they didn't try very much before giving up.
So - I put the thing back together and tried to turn it on and charge it. The display and LEDs show no signs of life, even when charging, holding down power button etc. When I attach the phone to my (Linux) PC, I get the following in dmesg:
Code:
[142745.586102] usb 3-2: new high-speed USB device number 99 using xhci_hcd
[142745.603030] usb 3-2: New USB device found, idVendor=0955, idProduct=7130
[142745.603038] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[142745.603042] usb 3-2: Product: APX
[142745.603045] usb 3-2: Manufacturer: NVIDIA Corp.
which is the only sign of life I've seen so far (why NVIDIA vendor ID and not HTC?). When holding down the power button for ~15 seconds, there's a "USB disconnect" and it re-appears.
Sometimes the phone seems to enter a slightly different state, giving me some sort of connect-timeout-reconnect loop four times:
Code:
[143124.943256] usb 3-2: new high-speed USB device number 101 using xhci_hcd
[143129.944609] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[143130.148758] usb 3-2: Device not responding to set address.
[143130.352699] usb 3-2: device not accepting address 101, error -71
I was hoping that it was just a busted display, and booting a recovery image would let me grab the files via adb - but it does not show up when doing "fastboot devices". I've tried different blind combinations of holding the power button and volume down, but nothing seems to happen (not sure if I'm doing something wrong though, since nothing appears on screen).
Maybe someone here on xda has an idea on how I could get into the device? Recovering the phone does not matter, but getting the files is very important to the owner.
Tausen said:
I'm trying to salvage some important files from a dead HTC One X (stock everything) - from what I've been told, it was in use and suddenly turned off. After attempts to charge the phone etc. to no avail (monitor does not turn on, no LEDs turn on at all) it was sent for repair with the instructions to not proceed if they could not salvage the files. The repair shop opened the phone, molested some plastic parts and sent it back in two parts, stating that they could not proceed further without loosing the data on the phone. I have no idea what they tried, so I'm hoping they didn't try very much before giving up.
So - I put the thing back together and tried to turn it on and charge it. The display and LEDs show no signs of life, even when charging, holding down power button etc. When I attach the phone to my (Linux) PC, I get the following in dmesg:
Code:
[142745.586102] usb 3-2: new high-speed USB device number 99 using xhci_hcd
[142745.603030] usb 3-2: New USB device found, idVendor=0955, idProduct=7130
[142745.603038] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[142745.603042] usb 3-2: Product: APX
[142745.603045] usb 3-2: Manufacturer: NVIDIA Corp.
which is the only sign of life I've seen so far (why NVIDIA vendor ID and not HTC?). When holding down the power button for ~15 seconds, there's a "USB disconnect" and it re-appears.
Sometimes the phone seems to enter a slightly different state, giving me some sort of connect-timeout-reconnect loop four times:
Code:
[143124.943256] usb 3-2: new high-speed USB device number 101 using xhci_hcd
[143129.944609] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[143130.148758] usb 3-2: Device not responding to set address.
[143130.352699] usb 3-2: device not accepting address 101, error -71
I was hoping that it was just a busted display, and booting a recovery image would let me grab the files via adb - but it does not show up when doing "fastboot devices". I've tried different blind combinations of holding the power button and volume down, but nothing seems to happen (not sure if I'm doing something wrong though, since nothing appears on screen).
Maybe someone here on xda has an idea on how I could get into the device? Recovering the phone does not matter, but getting the files is very important to the owner.
Click to expand...
Click to collapse
For me the battery is dead. Try changing battery... Has the repair center remounted all connectors like the screen/battery connector?
Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???
fdelago said:
Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???
Click to expand...
Click to collapse
Any luck unbricking your device?
I have the same problem here
Hello since some day, I have the following issue on my phone :
At some point, randomly, the phone freeze and reboot (it may boot loop one or two time)
No freeze nor reboot while charging
The phone is not recognized anymore when trying to connect thru USB (I tried with two different USB cable and with three different PC, one on windows 7, one on Archlinux and another on Unbuntu studio)
No USB access in system, bootloader (via fastboot) or in recovery (TWRP)
Code:
device descriptor read/64, error -71
So I suspect an hardware issue. If so, is someone already have this ? Can I fix it by myself ?
The phone runs ResurrectionRemix v5.8.3 with ElementalX kernel.
Thanks in advance for your help
Hello, everybody,
I am experiencing problems with my hardware/kernel module when connecting two softbricked devices:
Motorola Moto C (xt1757)
Fiesta Duo I6C (China phone)
I am connecting them without battery so I can access them as /dev/ttyACM0; which would allow me to use SP Flash Tool.
However, device gets disconnected after 3 seconds or so, with the following error message:
Code:
kernel: usb 1-3: new high-speed USB device number 83 using ehci-pci
kernel: usb 1-3: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 1-3: Product: MT65xx Preloader
kernel: usb 1-3: Manufacturer: MediaTek
kernel: cdc_acm: probe of 1-3:1.0 failed with error -22
kernel: cdc_acm 1-3:1.1: ttyACM0: USB ACM device
mtp-probe[17092]: checking bus 1, device 83: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-3"
mtp-probe[17092]: bus: 1, device: 83 was not an MTP device
mtp-probe[17110]: checking bus 1, device 83: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-3"
mtp-probe[17110]: bus: 1, device: 83 was not an MTP device
kernel: usb 1-3: USB disconnect, device number 83
which tells me that the device is being detected by the Kernel and the right module kicks in; yet, it might not have the firmware, or something like it, necessary to achieve successful communication.
So has anyone being able to overcome this issue?
I am currently using artix linux (fork of arch linux without systemd) with ck kernel 4.20.5.1
I have tried connecting the phones at my USB 2.0 (as shown above) and USB 3.0 ports. The same result is obtained.
I will appreciate any assistance that could be provided. Thank you in advance.
Regards.
I managed to get it working.
You have to
open SP Flash Tool,
provide all your data (scatter file, download agent, authentication, et cetera),
click download,
then connect the device.
Hope this helps somebody.