Hi people,
A few days ago the problem began. The headset icon was in the screen and was not leaving. Also I could not mount my SD card.
Fortunately, the icon automatically avoided, but the problem still exists with the SD. (Also I can not sync)
I already tried the following:
- New ROM flashed
- New RADIO flashed
- New USB cable tried
- Multiple OS's tried
log in /var/log/kern.log:
Code:
kernel: [11267.304066] usb 6-1: new low speed USB device using uhci_hcd and address 120
kernel: [11267.485057] usb 6-1: device descriptor read/64, error -71
kernel: [11267.712055] usb 6-1: device descriptor read/64, error -71
kernel: [11267.984093] usb 6-1: new low speed USB device using uhci_hcd and address 121
kernel: [11268.108056] usb 6-1: device descriptor read/64, error -71
kernel: [11268.333053] usb 6-1: device descriptor read/64, error -71
kernel: [11268.549060] usb 6-1: new low speed USB device using uhci_hcd and address 122
kernel: [11268.960050] usb 6-1: device not accepting address 122, error -71
kernel: [11269.072078] usb 6-1: new low speed USB device using uhci_hcd and address 123
kernel: [11269.481132] usb 6-1: device not accepting address 123, error -71
kernel: [11269.481160] hub 6-0:1.0: unable to enumerate USB device on port 1
Thanks.
goingwrong said:
Hi people,
A few days ago the problem began. The headset icon was in the screen and was not leaving. Also I could not mount my SD card.
Fortunately, the icon automatically avoided, but the problem still exists with the SD. (Also I can not sync)
I already tried the following:
- New ROM flashed
- New RADIO flashed
- New USB cable tried
- Multiple OS's tried
log in /var/log/kern.log:
Code:
kernel: [11267.304066] usb 6-1: new low speed USB device using uhci_hcd and address 120
kernel: [11267.485057] usb 6-1: device descriptor read/64, error -71
kernel: [11267.712055] usb 6-1: device descriptor read/64, error -71
kernel: [11267.984093] usb 6-1: new low speed USB device using uhci_hcd and address 121
kernel: [11268.108056] usb 6-1: device descriptor read/64, error -71
kernel: [11268.333053] usb 6-1: device descriptor read/64, error -71
kernel: [11268.549060] usb 6-1: new low speed USB device using uhci_hcd and address 122
kernel: [11268.960050] usb 6-1: device not accepting address 122, error -71
kernel: [11269.072078] usb 6-1: new low speed USB device using uhci_hcd and address 123
kernel: [11269.481132] usb 6-1: device not accepting address 123, error -71
kernel: [11269.481160] hub 6-0:1.0: unable to enumerate USB device on port 1
Thanks.
Click to expand...
Click to collapse
Did you do anything with your SD card? Like partitioning it for Apps2SD?
C0mpu13rFr34k said:
Did you do anything with your SD card? Like partitioning it for Apps2SD?
Click to expand...
Click to collapse
No, nothing.
Are the icons in the notifications bar coming up?
Andyt95 said:
Are the icons in the notifications bar coming up?
Click to expand...
Click to collapse
Nope, nothing happens when i plug in the cable.
The only thing that happens is that the battery LED lights.
goingwrong said:
Nope, nothing happens when i plug in the cable.
The only thing that happens is that the battery LED lights.
Click to expand...
Click to collapse
Then the problem is unrelated to your phone. You have tried a new USB cable, so you should try a different USB slot or a different computer. If that doesn't work, get and micro-SD adapter and format (deselect quick format as that won't do anything). After all else has failed, you should look into a new SD card...
Not necessarily a cable issue. I had an issue a few months ago where the phone went into some qxdm debug mode which meant that it disabled both SD and the UART (which controlled USB and Wi-Fi amongst other things).
Try these threads
http://forum.xda-developers.com/showthread.php?t=708776
http://forum.xda-developers.com/showthread.php?t=681583
They both refer to a page at modaco.com that solved it for me. You have to use fastboot oem commands, and then I had to load a new SPL (but it depends what your handset has, other people have been able to avoid that bit).
Andyt95 said:
Then the problem is unrelated to your phone. You have tried a new USB cable, so you should try a different USB slot or a different computer. If that doesn't work, get and micro-SD adapter and format (deselect quick format as that won't do anything). After all else has failed, you should look into a new SD card...
Click to expand...
Click to collapse
sync doenst work either..
Related
Hello!
How do i mount my HTC hero on ubuntu?
I have tried everything i know about.
Here's some info about it!
It's connected to the machine now.
Code:
[email protected]:~# dmesg|tail
[167350.745833] VFS: Can't find a valid FAT filesystem on dev sda2.
[167350.746019] qnx4: wrong fsid in superblock.
[167392.539945] FAT: bogus number of reserved sectors
[167392.539952] VFS: Can't find a valid FAT filesystem on dev loop0.
[167392.540057] qnx4: wrong fsid in superblock.
[167429.744606] attempt to access beyond end of device
[167429.744614] loop0: rw=0, want=4, limit=2
[167429.744619] EXT3-fs: unable to read superblock
[167584.269145] FAT: bogus number of reserved sectors
[167584.269154] VFS: Can't find a valid FAT filesystem on dev loop0.
[email protected]:~# sfdisk -l
Disk /dev/sda: 19457 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0 - 0 0 0 Empty
/dev/sda2 * 0+ 18768- 18769- 150759362 f W95 Ext'd (LBA)
/dev/sda3 18768+ 19457- 689- 5529600 8e Linux LVM
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 3916+ 18768- 14853- 119300096 7 HPFS/NTFS
/dev/sda6 0+ 3915 3916- 31455207 83 Linux
[email protected]:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 30G 3.3G 25G 12% /
udev 438M 276K 438M 1% /dev
none 438M 0 438M 0% /dev/shm
none 438M 200K 438M 1% /var/run
none 438M 0 438M 0% /var/lock
none 438M 0 438M 0% /lib/init/rw
/dev/sda5 114G 30G 85G 26% /mnt/sda5
/dev/sda6 30G 3.3G 25G 12% /mnt/sda6
[email protected]:~#
First, you should have your data partition of your SD card formatted as FAT32.
Then connect your Hero to your PC using original USB table (you can use non-original, but not everyone of them works).
You should see notification on hero about connected USB, click on this notification and Hero will ask you if you want to connect it as storage device.
Linux should now recognize your Hero as standard USB flash drive.
This works for me.
hELLO!
How can i format my data-partition on my SD-card to FAT32?
And when i connect the hero to the machine, there is no notification on the notification bar!
sorry for bad english.
Broken USB
Hmm, it seems you have some trouble with USB since Hero does not recognize it. My dmesg looks like this, when I connect my Hero (but before I enable it as storage device):
Code:
[47693.001261] usb 6-2: new full speed USB device using uhci_hcd and address 2
[47693.130013] usb 6-2: device descriptor read/64, error -71
[47693.370011] usb 6-2: device descriptor read/64, error -71
[47693.600011] usb 6-2: new full speed USB device using uhci_hcd and address 3
[47693.730011] usb 6-2: device descriptor read/64, error -71
[47693.971260] usb 6-2: device descriptor read/64, error -71
[47694.201263] usb 6-2: new full speed USB device using uhci_hcd and address 4
[47694.621263] usb 6-2: device not accepting address 4, error -71
[47694.680042] hub 6-0:1.0: unable to enumerate USB device on port 2
[47694.961263] usb 2-4: new high speed USB device using ehci_hcd and address 3
[47695.123330] usb 2-4: configuration #1 chosen from 1 choice
[47695.526904] Initializing USB Mass Storage driver...
[47695.527144] scsi6 : SCSI emulation for USB Mass Storage devices
[47695.527234] usb-storage: device found at 3
[47695.527236] usb-storage: waiting for device to settle before scanning
[47695.527250] usbcore: registered new interface driver usb-storage
[47695.527253] USB Mass Storage support registered.
[47700.521271] usb-storage: device scan complete
[47700.523257] scsi 6:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
[47700.523603] sd 6:0:0:0: Attached scsi generic sg3 type 0
[47700.533243] sd 6:0:0:0: [sdc] Attached SCSI removable disk
i'd try repartitioning the card, looks like a corrupted filesystem.
I don't think repartitioning will help here. /dev/sda is the disk in his computer, because /dev/sda6 is mounted as /. The dmesg output doesn't say anything about /dev/sdb, and there is not even anything about trying to connect a USB device.
My guess is either the cable is bad, or the USB socket on the computer is not connected.
Hi,
I get the same - in Windows it comes up as an unregognised device, and in linux i get
[ 1724.760062] usb 7-1: new full speed USB device using uhci_hcd and address 18
[ 1724.890058] usb 7-1: device descriptor read/64, error -71
[ 1725.130036] usb 7-1: device descriptor read/64, error -71
[ 1725.360077] usb 7-1: new full speed USB device using uhci_hcd and address 19
[ 1725.492549] usb 7-1: device descriptor read/64, error -71
[ 1725.730242] usb 7-1: device descriptor read/64, error -71
[ 1725.960394] usb 7-1: new full speed USB device using uhci_hcd and address 20
[ 1726.380063] usb 7-1: device not accepting address 20, error -71
[ 1726.500053] usb 7-1: new full speed USB device using uhci_hcd and address 21
[ 1726.920281] usb 7-1: device not accepting address 21, error -71
[ 1726.920302] hub 7-0:1.0: unable to enumerate USB device on port 1
and no option on the Hero to mount the partition. I'm open to suggestions
Try another cable and/or another USB port. E.g. the USB ports at the back of your PC are directly soldered to the mainboard, without a shoddy connector and cable in between.
Hi there,
I have a ZTE V9 light (now a brick).
It had a 2.1 update 1 and I used the z4root and OneClickRecoveryV9_20110531.apk to root it.
I was able to root and install the recovery-clockwork-4.0.1.5-v9-gen1.img.
I was also able to reboot it in recovery mode and tried to flash the update-cm-7.1.0-RC0-V9-KANG-signed_20110531.zip and update-cm-7.1.0-V9-signed.zip after all wipes.
Now i cannot reboot it in recovery mode because it's always the green android on screen.
It doesn't matter if I reboot it pressing the Vol- or Vol+ with the Power one. Always have the green android.
If I plug the V9 via USB in the syslog I get the following messages:
kernel: [30905.620641] usb 1-4: USB disconnect, address 12
Oct 15 11:06:57 kernel: [30909.017027] usb 1-4: new high speed USB device using ehci_hcd and address 13
Oct 15 11:06:59 kernel: [30911.180290] hub 1-0:1.0: unable to enumerate USB device on port 4
Oct 15 11:07:01 kernel: [30912.968046] usb 1-4: new high speed USB device using ehci_hcd and address 14
Oct 15 11:07:06 kernel: [30918.088060] usb 1-4: device descriptor read/64, error -71
Oct 15 11:07:11 kernel: [30923.314973] usb 1-4: device descriptor read/64, error -71
Oct 15 11:07:12 kernel: [30923.529030] usb 1-4: new high speed USB device using ehci_hcd and address 15
So i think now i have a beautiful brick, righgt?
Is there a solution? Can anybody help me?
Thanx in advance
BTW: The adb does not recognize the device.....
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Nobody?
Please help..........!!!!
I have noticed this morning that while my Xperia S is connected via USB cable to the PC it does not charge, ie. it indicates charging but battery level goes down rather than up. Also I've noticed that my OS (Fedora 16) stopped mounting Xperia's internal memory. Dmesg output is just that:
Code:
[34723.804074] usb 2-1.2: new full-speed USB device number 61 using ehci_hcd
[34723.877051] usb 2-1.2: device descriptor read/64, error -32
[34724.050920] usb 2-1.2: device descriptor read/64, error -32
[34724.224867] usb 2-1.2: new full-speed USB device number 62 using ehci_hcd
[34724.287808] usb 2-1.2: device descriptor read/64, error -32
[34724.461715] usb 2-1.2: device descriptor read/64, error -32
[34724.635655] usb 2-1.2: new full-speed USB device number 63 using ehci_hcd
[34725.037264] usb 2-1.2: device not accepting address 63, error -32
[34725.110414] usb 2-1.2: new full-speed USB device number 64 using ehci_hcd
[34725.512050] usb 2-1.2: device not accepting address 64, error -32
[34725.512180] hub 2-1:1.0: unable to enumerate USB device on port 2
Did a bit of research around the interwebs, found advice to clear data of the MtpApp app (settings -> applications -> all -> MtpApp), which I did but that didn't solve the problem, yet dmesg output changed a bit:
Code:
[34734.683275] usb 3-1: new full-speed USB device number 67 using xhci_hcd
[34734.686432] usb 3-1: Device not responding to set address.
[34734.890333] usb 3-1: Device not responding to set address.
[34735.091046] usb 3-1: device not accepting address 67, error -71
[34735.243993] usb 3-1: new full-speed USB device number 68 using xhci_hcd
[34735.247164] usb 3-1: Device not responding to set address.
[34735.451046] usb 3-1: Device not responding to set address.
[34735.651757] usb 3-1: device not accepting address 68, error -71
[34735.804727] usb 3-1: new full-speed USB device number 69 using xhci_hcd
[34735.807836] usb 3-1: Device not responding to set address.
[34736.011768] usb 3-1: Device not responding to set address.
[34736.212469] usb 3-1: device not accepting address 69, error -71
[34736.365416] usb 3-1: new full-speed USB device number 70 using xhci_hcd
[34736.368521] usb 3-1: Device not responding to set address.
[34736.572448] usb 3-1: Device not responding to set address.
[34736.773180] usb 3-1: device not accepting address 70, error -71
[34736.773208] hub 3-0:1.0: unable to enumerate USB device on port 1
Seems to also depend on the USB port I use in my laptop, ie. in one port it says "Device not responding", while on the other "device descriptor read/64, error -32". UPDATE: On double check it seems like USB 3.0 ports saying "not responding", while USB 2.0 port returns "descriptor error".
I obviously tried rebooting (including hard-reboot with volume-up key held), tried different cables, different PCs, including Windows one which just popped a balloon saying something about "unrecognized device". Nothing seems to rectify the issue. Needless to say it was working perfectly up until today.
Thankfully, it seems that's a software-related issue rather than physically borked USB port as I successfully managed to put device into flashmode (volume-up + usb plug). UPDATE: Unfortunately, even if physical plug to the port is recognized and green or blue light comes up, dmesg still returns "descriptor errors" and device is turning itself into charging-only mode (I initially thought just seeing blue/green light means either of modes is entered).
Running out of ideas what else I could do to get USB work again, apart from hard reset. Any suggestions more than welcome.
UPDATE: Out of the sudden, after 1525th reboot cycle somehow charging via USB cable works fine again, however internal storage is still not mounted to the PC. Doh! I guess I'll end up with warranty repair/replacement.
FINAL UPDATE: USB port died completely, plugging USB cable to the PC doesn't trigger any dmesg activity at all and handset after a while of doubt recognises connection as a standard wall charger. Sorting out warranty replacement as we speak.
Have you tried cleaning of the USB port/connector (of your phone)?
cognosco said:
Have you tried cleaning of the USB port/connector (of your phone)?
Click to expand...
Click to collapse
No, I haven't, but I doubt that's the case, as it wouldn't enter flashmode either.
Hi,
I have enabled USB-Debugging in the settings and connected the phone to my computer (running linux), but there is no notification that USB-Debugging was/is actually enabled on the phone and Eclipse doesn't recognize the Evo.
Might I be missing something, is this a bug of the ROM (I know that on Android < 4.0 there was a notification if USB-Debugging was enabled) or something else?
This is the output of dmesg when disabling USB-Debugging:
Code:
[130921.297574] usb 1-8: USB disconnect, device number 109
[130921.672047] usb 1-8: new high-speed USB device number 110 using ehci_hcd
[130921.808493] scsi79 : usb-storage 1-8:1.0
[130922.809698] scsi 79:0:0:0: Direct-Access HTC Android Phone 0000 PQ: 0 ANSI: 2
[130922.810846] sd 79:0:0:0: Attached scsi generic sg2 type 0
[130922.815181] sd 79:0:0:0: [sdb] Attached SCSI removable disk
This is the output when enabling USB-Debugging:
Code:
[131010.824084] usb 1-8: USB disconnect, device number 110
[131011.204101] usb 1-8: new high-speed USB device number 111 using ehci_hcd
[131011.347364] scsi80 : usb-storage 1-8:1.0
[131012.345085] scsi 80:0:0:0: Direct-Access HTC Android Phone 0000 PQ: 0 ANSI: 2
[131012.351805] sd 80:0:0:0: [sdb] Attached SCSI removable disk
[131012.353054] sd 80:0:0:0: Attached scsi generic sg2 type 0
Any hints?
Thank you.
exic
Anyone?
Maybe try a different ROM and see if it works. I'm not GSM, but I've heard that Leedroid is pretty good.
I tried NonSense 3.0.0 which shows the notification "USB-Debugging enabled", but it still isn't recognized by Eclipse. Since LeeDroid unfortunately has no ICS version, I guess I'll have to go with a non-ICS version.
exic said:
Since LeeDroid unfortunately has no ICS version, I guess I'll have to go with a non-ICS version.
Click to expand...
Click to collapse
What I meant was to try Leedroid just to see if it works on a Gingerbread ROM. If it does, then it is the ICS GSM leak. If not, then it could be something else (like your computer).
Last week I tried again with LeeDroid and obviously nothing worked because I hadn't made my computer ready. I was confused because I was used to seeing "USB debugging enabled" in the notifications which didn't appear on LeeDroid either.
I want to fix my bricked Nook (8g), in order to fix it I loaded cwm into a microsd card and my plan was getting adb to work while the Nook is in cwm recovery. The problem here is that my pc (Debian Wheezy) doesn't seem very happy with the tablet and I couldn't get it recognized.
Using Android SDK Manager I got the following in the usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2080
Click to expand...
Click to collapse
worth saying (probably), I also edited /etc/udev/rules.d/51-android.rules as follows:
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_fastboot"
Click to expand...
Click to collapse
When I finished doing that and still didn't work, I looked up what happens when I plug the tablet into the usb port,
[ 9634.796053] usb 2-9: new full-speed USB device number 39 using ohci_hcd
[ 9634.980037] usb 2-9: device descriptor read/64, error -62
[ 9635.268035] usb 2-9: device descriptor read/64, error -62
[ 9635.548038] usb 2-9: new full-speed USB device number 40 using ohci_hcd
[ 9635.732041] usb 2-9: device descriptor read/64, error -62
[ 9636.020041] usb 2-9: device descriptor read/64, error -62
Click to expand...
Click to collapse
so this seems to be the error. Is it possible to fix it? I tried a few things I found (like killing the usb services and start them again) but you can tell it wasn't exactly successful. Is there anything I can try?
You might want to consider the unbrick method described at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/.