Related
Anyone else have a problem with USB host mode and copying big files?
If so, can we fix this?
I have tried formatting my drive in FAT32,NTFS, and ext2. But the result is always the same, the drive dies if I copy a file bigger than 30 or 40 MB. I have tried stock, Faux123, and francoKernel as well.
The drive doesn't die at a specific MB each time, but it is generally around 30 MB but sometimes makes it to 80 or even 140 MB one time. I am trying to off-load some 700MB movies.
Here is the kernel message error:
<6>[ 1920.842529] max17040 4-0036: online = 1 vcell = 3547500 soc = 22 status = 3 health = 1 temp = 370 charger status = 0
<3>[ 1926.574005] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.594299] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.649810] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1927.740753] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
<6>[ 1927.773895] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
<6>[ 1927.938781] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
<3>[ 1968.389251] L3 CUSTOM SRESP error with SOURCEMM2 info=0x84
<4>[ 1968.389434] ------------[ cut here ]------------
<4>[ 1968.389739] WARNING: at arch/arm/mach-omap2/omap_l3_noc.c:130 l3_interrupt_handler+0x31c/0x360()
<4>[ 1968.390045] L3 custom sresp error
<4>[ 1968.390197] Modules linked in:
<4>[ 1968.390686] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 1968.390991] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 1968.391326] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0074898>] (l3_interrupt_handler+0x31c/0x360)
<4>[ 1968.391632] [<c0074898>] (l3_interrupt_handler+0x31c/0x360) from [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178)
<4>[ 1968.391967] [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178) from [<c00d4760>] (handle_irq_event+0x3c/0x5c)
<4>[ 1968.392150] [<c00d4760>] (handle_irq_event+0x3c/0x5c) from [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164)
<4>[ 1968.392456] [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164) from [<c00d3f50>] (generic_handle_irq+0x2c/0x40)
<4>[ 1968.392791] [<c00d3f50>] (generic_handle_irq+0x2c/0x40) from [<c004904c>] (asm_do_IRQ+0x4c/0xac)
<4>[ 1968.393096] [<c004904c>] (asm_do_IRQ+0x4c/0xac) from [<c004eb08>] (__irq_svc+0x48/0xe4)
<4>[ 1968.393402] Exception stack(0xc0799f28 to 0xc0799f70)
<4>[ 1968.393554] 9f20: c0799f70 3b9aca00 4c534d85 000001ca 4c4bda2c 000001ca
<4>[ 1968.393859] 9f40: 000003ff c1192210 8000406a 412fc09a 00000000 00000000 00000000 c0799f70
<4>[ 1968.394042] 9f60: c007c690 c0068380 00000013 ffffffff
<4>[ 1968.394348] [<c004eb08>] (__irq_svc+0x48/0xe4) from [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4)
<4>[ 1968.394683] [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4) from [<c03af838>] (cpuidle_idle_call+0x94/0x118)
<4>[ 1968.394989] [<c03af838>] (cpuidle_idle_call+0x94/0x118) from [<c0050538>] (cpu_idle+0xbc/0xfc)
<4>[ 1968.395172] [<c0050538>] (cpu_idle+0xbc/0xfc) from [<c00088ac>] (start_kernel+0x298/0x2e8)
<4>[ 1968.395477] [<c00088ac>] (start_kernel+0x298/0x2e8) from [<80008040>] (0x80008040)
<4>[ 1968.395782] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 1968.396087] ---[ end trace 33de6ebe35ad56b6 ]---
<6>[ 1970.874023] max17040 4-0036: online = 1 vcell = 3532500 soc = 22 status = 3 health = 1 temp = 380 charger status = 0
<6>[ 1993.138793] usb 1-1: reset high speed USB device number 2 using musb-hdrc
<6>[ 2000.347503] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<6>[ 2000.347717] usb 1-1: USB disconnect, device number 2
<4>[ 2000.350708] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2000.351989] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2001.361236] max17040 4-0036: online = 1 vcell = 3585000 soc = 21 status = 2 health = 1 temp = 380 charger status = 0
<6>[ 2003.287322] sd 0:0:0:0: Device offlined - not ready after error recovery
<6>[ 2003.287597] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287628] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287658] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.287689] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 00 3f 00 00 08 00
<3>[ 2003.287719] end_request: I/O error, dev sda, sector 63
<3>[ 2003.287750] Buffer I/O error on device sda1, logical block 0
<4>[ 2003.287780] lost page write due to I/O error on sda1
<6>[ 2003.289154] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.289459] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 21 e7 00 00 08 00
<3>[ 2003.291625] end_request: I/O error, dev sda, sector 8679
<3>[ 2003.291778] Buffer I/O error on device sda1, logical block 1077
<4>[ 2003.292114] EXT4-fs warning (device sda1): ext4_end_bio:258: I/O error writing to inode 13 (offset 217088 size 4096 starting block 1085)
<3>[ 2003.297576] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.297851] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.299560] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.299743] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.300415] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.300720] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301116] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.301391] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301727] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.302032] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.302398] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.302703] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.303802] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.304168] EXT4-fs error (device sda1): ext4_free_branches:4377: inode #13: block 536: comm libestool.so: Read failure
<3>[ 2003.305358] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.305755] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.306365] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.306518] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.336242] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.336364] EXT4-fs error (device sda1): ext4_find_entry:934: inode #2: comm libestool.so: reading directory lblock 0
<3>[ 2003.411834] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.412017] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm ngs.android.pop: unable to read itable block
<2>[ 2003.412414] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.412567] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2008.311859] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.312194] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm bdi-default: unable to read itable block
<3>[ 2008.313110] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.313415] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm bdi-default: unable to read itable block
<6>[ 2025.582702] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2026.233337] usb 1-1: new high speed USB device number 3 using musb-hdrc
<3>[ 2026.388244] usb 1-1: device v090c p6200 is not supported
<6>[ 2026.388427] usb 1-1: New USB device found, idVendor=090c, idProduct=6200
<6>[ 2026.388763] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 2026.389068] usb 1-1: Product: Generic USB2.0 card
<6>[ 2026.389221] usb 1-1: Manufacturer: Silicon Motion, Inc.
<6>[ 2026.389373] usb 1-1: SerialNumber: 12345678901234567890
<6>[ 2026.392089] scsi1 : usb-storage 1-1:1.0
<6>[ 2030.177124] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2030.180053] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2030.181335] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2031.197509] max17040 4-0036: online = 1 vcell = 3600000 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<6>[ 2034.948303] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2035.182495] usb 1-1: USB disconnect, device number 3
<6>[ 2045.606109] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2045.609100] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2045.610321] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2046.627288] max17040 4-0036: online = 1 vcell = 3602500 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<4>[ 2048.832824] ------------[ cut here ]------------
<4>[ 2048.832916] WARNING: at drivers/usb/musb/musb_host.c:125 musb_h_tx_flush_fifo+0x78/0x84()
<4>[ 2048.833068] Could not flush host TX2 fifo: csr: 2003
<4>[ 2048.833160] Modules linked in:
<4>[ 2048.833404] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 2048.833526] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 2048.833679] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84)
<4>[ 2048.833862] [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84) from [<c0367724>] (musb_cleanup_urb+0xb0/0xd4)
<4>[ 2048.834014] [<c0367724>] (musb_cleanup_urb+0xb0/0xd4) from [<c0367990>] (musb_urb_dequeue+0xfc/0x13c)
<4>[ 2048.834167] [<c0367990>] (musb_urb_dequeue+0xfc/0x13c) from [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac)
<4>[ 2048.834350] [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac) from [<c035d938>] (usb_stor_stop_transport+0x48/0x60)
<4>[ 2048.834442] [<c035d938>] (usb_stor_stop_transport+0x48/0x60) from [<c035c36c>] (command_abort+0x80/0x84)
<4>[ 2048.834564] [<c035c36c>] (command_abort+0x80/0x84) from [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c)
<4>[ 2048.834716] [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c) from [<c00b227c>] (kthread+0x80/0x88)
<4>[ 2048.834899] [<c00b227c>] (kthread+0x80/0x88) from [<c0050148>] (kernel_thread_exit+0x0/0x8)
<4>[ 2048.835052] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 2048.835144] ---[ end trace 33de6ebe35ad56b7 ]---
<6>[ 2048.837768] scsi 1:0:0:0: Device offlined - not ready after error recovery
I found a thread on TI site for the OMAP4460 that discusses an error like mine but the signature is not the same, seems there they were having a problem with the the TCP/IP stack becoming corrupted because the processor was allocating memory too fast. Something like that is happening here. All I really know is it has to do with the handling of the L3 cache.
I think this may have to do with the cpu trying to idle when it should not.
What kind of drive are you using? If its a portable usb hard drive then this could be a power issue.
It's not a portable HD, just usb sd card reader.
With further investigation I have found that the problem might stem from the x-loader being mismatched to the kernel, which is part of the bootloader.
I tried different bootloaders, but none made a difference.
Finally, I tried a different USB OTG cable, a slightly more expensive one, and it worked.
Hi everyone,
sorry for the lengthy post, but I wanted to be precise. Please read the whole of it, if you think you might be able to help. I love this phone but it's useless without WiFi for me. I am also sorry, if I unwittingly violated any forum rules. I tried the best I could.
Currently, I am having a severe issue with the WiFi of my HTC Desire Z. It won't turn on or do anything. First of all: I worked myself through all threads that I could find which were just remotely connected with this issue, also in forums concerning other devices. I still hope I overlooked something... Btw.: My phone is almost 3 years old and a German version. I don't remember what method I used to root it since it was one of the first things I did.
The aforementioned problem appeared right after the following incident: My phone went out of battery while I was listening to an audiobook via Audible. I put the phone in airplane mode some 10 minutes earlier to prevent this, very <irony>successfully<\irony>...
After rebooting, I tried to turn WiFi on, but it just kept telling me "turning wifi on". The switch turned grey and nothing happened. I tried rebooting, turning WiFi on and of several times as well as airplane mode. I flashed the following ROMs, some of which I have been using sometime earlier where WiFi has definitively been working: Andromadus JellyBean by Flinny (version 123, 133 if that matters), all CM stable releases, Andromadus Mimicri 1.50 together with the sugested WiFixIt. With these ROMs I did the same. I could not find any stock ROM that has been able to boot. I did not try to reverse root and s-off (seems pointless to me).
I update the Radio to (afaik most recent version) and I downgraded it a few other versions without any change. I also did a superwipe with the tools given on the following page and reinstalled the ROMs, to no avail: http://forum.xda-developers.com/showthread.php?t=1044992
I also tried different sim-cards (from UK and Germany), both with and without sim-card and sd-card. Also no success.
Bluetooth is working flawlessly. I have just copied a file from my Laptop over to my phone via BT, which is strange, because, as far as I know, both WiFi and BT use the same chips and the same antenna.
I pulled all the logs I found (logcat: main, event, radio; dmesg) and boiled it down to the driver not being able to be loaded. Please correct me, but the WiFi drivers come with the ROM, therefore it CANNOT be due to a faulty driver, since I installed some that worked months ago (tried this before and after flashing different radios).
I reckon that the following parts are the important ones, but I attached the complete logs (cover the boot process and me trying to turn WiFi on) to be on the safe side. As far as I understand, it just says that it tries to load the driver bot fails to attach some kind of module.
Dmesg:
<6>[ 45.185119] [WLAN] ## wifi_probe
<4>[ 45.185302] [WLAN][WRN] wifi_set_power = 1
<6>[ 45.185455] [WLAN]vision_wifi_power: 1
<6>[ 46.075988] [WLAN] wifi_set_carddetect = 1
<6>[ 46.076141] vision_wifi_set_carddetect: 1
<6>[ 46.076293] mmc1: Slot status change detected (0 -> 1)
<6>[ 46.089599] [WLAN] Dongle Host Driver, version 5.90.125.120
<6>[ 46.089599] Compiled in drivers/net/wireless/bcmdhd on Oct 1 2012 at 17:46:03
<4>[ 46.129547] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[ 46.129882] mmc1: new high speed SDIO card at address 0001
<6>[ 47.087982] [LED]pm8058_drvx_led_brightness_set: bank 3 brightness 0 +
<6>[ 47.088287] [LED]pm8058_drvx_led_brightness_set: bank 3 brightness 0 -
<6>[ 47.935516] [TP][email protected],797
<3>[ 48.187652] mmc1: CMD53: Data timeout
<6>[ 48.187927] mmc1: SDCC PWR is ON
<6>[ 48.188110] mmc1: SDCC clks are ON, MCLK rate=50000000
<6>[ 48.188262] mmc1: SDCC irq is enabled
<6>[ 48.188507] ===== SDCC-CORE: Register Dumps @base=0xec832000 =====
<6>[ 48.188629] Reg=0x00: 0x00000003, 0x00009b00, 0x15000004, 0x00001475.
<6>[ 48.188903] Reg=0x10: 0x00000035, 0x00001000, 0x00000000, 0x00000000.
<6>[ 48.189025] Reg=0x20: 0x00000000, 0x05f5e100, 0x00000004, 0x00000043.
<6>[ 48.189270] Reg=0x30: 0x00000004, 0x00400200, 0x00000000, 0x00a081ff.
<6>[ 48.189514] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.189666] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.189910] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.190063] mmc1: PIO mode
<6>[ 48.190307] mmc1: xfer_size=4, data_xfered=0, xfer_remain=4
<6>[ 48.190429] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
<4>[ 48.190917] [WLAN][WRN] F1 signature read @0x18000000=0xffffffff
<6>[ 48.797210] [TP][email protected],866
<6>[ 48.798217] [TP]calibration confirm with recal by position
<6>[ 48.823303] [TP]0x01 0x10 0xA8 0x85 0x00
<6>[ 48.835113] [TP]0x01 0x00 0xA8 0x85 0x00
<3>[ 50.226043] mmc1: CMD53: Data timeout
<6>[ 50.226226] mmc1: SDCC PWR is ON
<6>[ 50.226409] mmc1: SDCC clks are ON, MCLK rate=50000000
<6>[ 50.226684] mmc1: SDCC irq is enabled
<6>[ 50.226806] ===== SDCC-CORE: Register Dumps @base=0xec832000 =====
<6>[ 50.227081] Reg=0x00: 0x00000003, 0x00009b00, 0x15000004, 0x00001475.
<6>[ 50.227233] Reg=0x10: 0x00000035, 0x00001000, 0x00000000, 0x00000000.
<6>[ 50.227478] Reg=0x20: 0x00000000, 0x05f5e100, 0x00000004, 0x00000043.
<6>[ 50.227630] Reg=0x30: 0x00000004, 0x00000200, 0x00000000, 0x00a081ff.
<6>[ 50.227874] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228149] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228271] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228546] mmc1: PIO mode
<6>[ 50.228668] mmc1: xfer_size=4, data_xfered=0, xfer_remain=4
<6>[ 50.228820] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
<4>[ 50.229370] [WLAN][WRN] dhdsdio_probe_attach: si_attach failed!
<4>[ 50.229644] [WLAN][WRN] dhdsdio_probe: dhdsdio_probe_attach failed
<4>[ 50.242645] [WLAN][WRN] dhd_module_init: wifi_fail_retry is true
<6>[ 50.247802] [WLAN] ## wifi_remove
<4>[ 50.247985] [WLAN][WRN] wifi_set_power = 0
<6>[ 50.248107] [WLAN]vision_wifi_power: 0
<6>[ 51.038665] [WLAN] wifi_set_carddetect = 0
<6>[ 51.038818] vision_wifi_set_carddetect: 0
<6>[ 51.038970] mmc1: Slot status change detected (1 -> 0)
<6>[ 51.039978] mmc1: card 0001 removed
<6>[ 51.041442] [WLAN] ## wifi_remove leave
Click to expand...
Click to collapse
Logcat main:
E/CommandListener( 115): Failed to open /proc/sys/net/ipv6/conf/wlan0/disable_ipv6: No such file or directory
E/WifiStateMachine( 294): Failed to disable IPv6: java.lang.IllegalStateException: command '1 interface ipv6 wlan0 disable' failed with '400 1 Failed to change IPv6 state (No such file or directory)'
...
I/WifiService( 294): WifiService starting up with Wi-Fi enabled
D/WifiService( 294): setWifiEnabled: true pid=294, uid=1000
D/WifiWatchdogStateMachine( 294): Disabling poor network avoidance for wi-fi only device
...
may times:
E/WifiHW ( 294): Supplicant not running, cannot connect
E/WifiHW ( 294): Supplicant not running, cannot connect
E/WifiStateMachine( 294): Failed to setup control channel, restart supplicant
Click to expand...
Click to collapse
Methinks it is a hardware issue and I am very close to taking the thing apart, which will possibly break something else... Second last comment: As I try to turn WiFi on via the status bar, it reboots after like one minute. Last comment: Is there any way to check whether it really is a hardware fault?
I apprecieate any comment intended to be helpful. Even when it is you telling me that it IS a hardware issue. If you need any further information, I am more than happy to provide it. I would also be happy to make the life of my phone-saviour more enjoyable with one or two pints of something, if we can arrange a meeting.
haha, i doubt ill be in germany any time soon... but i will be in greece in a month or so...
well it sounds like youre trying all the right things and it possibly is a hardware fault. but being you rooted 3 years ago you dont have true radio s-off, as it wasnt around.
if it were me, i would unroot, then follow the gfree method to downgrade and root via gfree, this will fully wipe out all partitions (except efs) and then flash a tried and true rom like cm7, hopefully all will be well at this point... if not, hardware...
Thank you for your advice. I did as you told me and went through the pain to reinstall stock Froyo as well as stock recovery and hboot. I also had s-on (at leats that's what hboot and gfree_verify said). Then I went to reroot it again, this time using gfree1.0 (which was definitely not what I used last time).
But unfortunately WiFi did not work neither with stock Froyo nor after rerooting and running CM7. Bluetooth still worked fine in every case... Log still says the exact same thing.
There is just two things left that might be worth a try, but it's a long shot. Could it be a problem with some data on the efs-partition that is messed up? As far as I understand it that is where android stores important information about IMEI, MAC-adress an the like. But I really do not know how to restore this partition even if it were the cause. Or could it be a problem with the RIL since that is what communicates with the radio? But I also do not know how to restore this if it were the cause (but it's just said that matching the RIL might just improve performance).
What's your opinion about this? Do you think that a look at the phone's insides might yield any results/certainty?
Unfortunetly if you never made a backup of your efs partition there is no way to restore this, you can back it up now, wipe it, restore and see if that helps but I doubt it.
Ril is matched when you downgraded so that's not it. Trutfully my best guess is hardware, sorry
Sent from my HTC Vision using xda premium
Unfortunately, I never made a backup of my /efs. I also tried wiping it, but no change.
The only sad thing is, that there is no adequate replacement...
I still don't get why BT is working and WiFi is not while both use the same chip, but that will stay a mystery forever unresolved.
Is there any way to close this tread? Somehow I don't see any.
Mine does what you are describing, but it's cause my gf dropped it
Sent from my SGH-T999 using xda premium
---------- Post added at 01:10 AM ---------- Previous post was at 01:08 AM ----------
And disconnected the wireless "modem"
The drop was pretty severe, however. I needed a whole new battery cover
Sent from my SGH-T999 using xda premium
op did you solved error ?
Nope, I could not solve the issue and I did not disassemble my phone and risk being left without one. So far, my mobile data plan has been sufficient and for large data, I access the internet via a USB-cable. I will get a new phone though when I am less busy at work.
Sent from my HTC Vision
Hi,
I think I have the SDS bug on my N7100. My phone crashed during a morning wake-up alarm and it won't boot again. I want to sent it for repair because it's under warranty only I can't flash my recovery to stock (or don't know how to do it) i'm currently using Philz Recovery.
Does anyone now how I can flash stock recovery or even if it's possible.
What i tried to fix my problem:
1. Tried to flash the original stock rom from sammobile using odin, it says it's passed and flashed system/cache/boot/recovery images. But then when I reboot it's still stuck at Samsung Bootloader logo. when i enter recovery it's still Philz Recovery.
2. Tried to flash recovery while using fastboot, but it won't recognize the device in download mode or recovery mode.
3. When i boot into recovery none of the partitions get mounted. I get the following error using: adb shell "dmesg | grep mmc0"
Code:
<3>[ 2.124315] c3 mmc0: Version ID 0x5342240a.
<6>[ 2.124568] c3 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 2.125100] c3 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<3>[ 2.155873] c0 mmc0: cmd 52 response timeout error
<3>[ 2.156724] c0 mmc0: cmd 52 response timeout error
<3>[ 2.160779] c0 mmc0: cmd 8 response timeout error
<3>[ 2.161629] c0 mmc0: cmd 5 response timeout error
<3>[ 2.162465] c0 mmc0: cmd 5 response timeout error
<3>[ 2.163300] c0 mmc0: cmd 5 response timeout error
<3>[ 2.164130] c0 mmc0: cmd 5 response timeout error
<3>[ 2.164987] c0 mmc0: cmd 55 response timeout error
<3>[ 2.165859] c0 mmc0: cmd 55 response timeout error
<3>[ 2.166706] c0 mmc0: cmd 55 response timeout error
<3>[ 2.167553] c0 mmc0: cmd 55 response timeout error
<3>[ 2.186791] c0 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 2.186822] c0 mmc0: VTU00M: 15010056545530304df1d72b21e9af87
<3>[ 2.291768] c0 mmc0: cmd 13 response timeout error
<6>[ 2.291871] c0 mmc0 : disable PON feature : ffffff92 : 00(0c) : 00000000
<3>[ 2.292721] c0 mmc0: cmd 6 response timeout error
<3>[ 2.293551] c0 mmc0: cmd 6 response timeout error
<3>[ 2.294380] c0 mmc0: cmd 6 response timeout error
<3>[ 2.295210] c0 mmc0: cmd 6 response timeout error
<3>[ 2.295265] c0 mmc0: error -110 whilst initialising MMC card
And when I run adb shell "ls /dev/block" i don't see any reference to the internal storage MMC card:
Code:
adb shell "ls /dev/block"
loop0 loop2 loop4 loop6 ram0 ram10 ram12 ram14 ram2 ram4 ram6 ram8 vold
loop1 loop3 loop5 loop7 ram1 ram11 ram13 ram15 ram3 ram5 ram7 ram9
Also when booting it points out that it can't mount any of the partitions.
Thanks in advance,
Jesse
If you can get the Samsung boot screen it is not sds. Sds the phone will not turn on. I would try the recovery firmware from skipsoft.net. There is a thread on here for mskips toolkit, but that is the website for it
Sent from my GT-N7105 using Tapatalk
Thanks tried it with mskips toolkit but it couldn't get futher then 'waiting for ADB mode'. When i run "adb devices" my device popups although in recovery mode or sideload mode. I cannot mount any device that should be available on internal storage. Also flashing the device using a zip file that's pushed to external storage (like twrp or cwm) in Philz Recovery won't stick . Also tried to repartition using a PIT file but no afail... (although it says it passed).
Seems like i'm screwed ...
Hi I'm having exactly the same problem with my Galaxy S3 GT-i9300. I get exactly the same logs from ADB, and get a write fail from Odin when I try to write a new PIT file.
Did you have any success resolving your problem? I'm starting to think I might need to replace the eMMC.
Thanks!!
Gibbitup said:
Hi I'm having exactly the same problem with my Galaxy S3 GT-i9300. I get exactly the same logs from ADB, and get a write fail from Odin when I try to write a new PIT file.
Did you have any success resolving your problem? I'm starting to think I might need to replace the eMMC.
Thanks!!
Click to expand...
Click to collapse
No sorry man mine is still gathering dust. Sent it in for repair wouldn't repair it because it is rooted .
I know this is a common problem, and this is the fourth time this happens to my phone, but since last summer I have no warranty left to keep my phone alive.
My phone has too many unexpected random reboots, since four days they are increasing heavily, the three other times this happened HTC replaced the mainboard. I am using Flinnys CM 11 Alpha 3 since its release, I know it is unstable, but these kinds of problems are new and reflashing this rom or CM 10.1 did not helped.
I searched a bit and I found out nothing positive, but are there chances JTag can fix this problem? I haven't detected any mmc error yet, and I want to keep this phone alive, but it isn't worth to buy a new mainboard. My phone is S-Off with Engineering HBoot.
I do not want to buy JTag cables/acessoires without a chance it could fix that, since I would need to import something to Germany and I think my phone is hardware damaged, hoping I am wrong.
In recovery mode I checked MMC: adb shell dmesg | grep mmc
Code:
<5>[ 0.000000] Kernel command line: board_vision.disable_uart2=0 board_vision.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0 board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true androidboot.baseband=26.13.04.19_M androidboot.cid=HTC__102 androidboot.batt_poweron=good_battery androidboot.carrier=HTC-GER androidboot.mid=PC1011000 androidboot.keycaps=qwerty androidboot.mode=recovery androidboot.serialno=[I]*removed*[/I] androidboot.bootloader=0.84.2000 no_console_suspend=1 console=null
<6>[ 7.228332] vision: vision_init_mmc
<3>[ 8.179473] mmc0: No card detect facilities available
<6>[ 8.180084] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.180328] mmc0: Platform slot type: MMC
<6>[ 8.180480] mmc0: 4 bit data mode disabled
<6>[ 8.180603] mmc0: 8 bit data mode enabled
<6>[ 8.180847] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.180999] mmc0: Slot eject status = 0
<6>[ 8.181121] mmc0: Power save feature enable = 1
<6>[ 8.181274] mmc0: DM non-cached buffer at ff00d000, dma_addr 0x0f518000
<6>[ 8.181396] mmc0: DM cmd busaddr 0x0f518000, cmdptr busaddr 0x0f518300
<6>[ 8.182434] mmc1: Qualcomm MSM SDCC at 0x00000000a3000000 irq 96,0 dma 8
<6>[ 8.182678] mmc1: Platform slot type: N/A
<6>[ 8.182800] mmc1: 4 bit data mode enabled
<6>[ 8.182952] mmc1: 8 bit data mode disabled
<6>[ 8.183197] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.183349] mmc1: Slot eject status = 1
<6>[ 8.183593] mmc1: Power save feature enable = 1
<6>[ 8.183715] mmc1: DM non-cached buffer at ff00e000, dma_addr 0x0f519000
<6>[ 8.183990] mmc1: DM cmd busaddr 0x0f519000, cmdptr busaddr 0x0f519300
<6>[ 8.185363] mmc2: Qualcomm MSM SDCC at 0x00000000a3100000 irq 100,0 dma 8
<6>[ 8.185516] mmc2: Platform slot type: SD
<6>[ 8.185760] mmc2: 4 bit data mode enabled
<6>[ 8.185882] mmc2: 8 bit data mode disabled
<6>[ 8.186035] mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.186279] mmc2: Slot eject status = 0
<6>[ 8.186401] mmc2: Power save feature enable = 1
<6>[ 8.186676] mmc2: DM non-cached buffer at ff00f000, dma_addr 0x0f51b000
<6>[ 8.186798] mmc2: DM cmd busaddr 0x0f51b000, cmdptr busaddr 0x0f51b300
<6>[ 8.187072] mmc2: Polling status mode enabled
<6>[ 8.345214] mmc0: new high speed MMC card at address 0001
<6>[ 8.347290] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<6>[ 8.348724] mmcblk0: p1 p2 p3 p4 < p5
<4>[ 8.635314] mmc2: high speed mode max_dtr = 50000000
<4>[ 8.635650] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 8.635894] mmc2: new high speed SDHC card at address e624
<6>[ 8.644683] mmcblk1: mmc2:e624 SU08G 7.40 GiB
<6>[ 8.645538] mmcblk1: p1
<6>[ 10.405792] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts:
<3>[ 10.565460] EXT3-fs (mmcblk0p25): error: couldn't mount because of unsupported optional features (40)
<3>[ 10.567626] EXT2-fs (mmcblk0p25): error: couldn't mount because of unsupported optional features (40)
<6>[ 10.618499] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 19.993225] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts:
<6>[ 20.125244] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts:
<3>[ 20.269561] EXT4-fs (mmcblk1p1): VFS: Can't find ext4 filesystem
<3>[ 20.274169] EXT4-fs (mmcblk1): VFS: Can't find ext4 filesystem
my phone says goodbye ;(
It now rebooted or made a sudden shutdown in the last hour at least four times.
Do you get the reboots if you leave it in recovery or bootloader? Can you rule out a sticky power button? Have you been able to capture a logcat or last_kmsg when this happens? It may be fixable
Sent from my Nexus 4 using XDA Premium 4 mobile app
I haven't got any reboots in bootloader or recovery mode, but my phone is not in recovery for long time, but i do not have a good possibility to test it, since i need the phone powered on. My power button is not sticky, besides it has been replaced last year. No i have not been able to capture it yet, every time my phone has these problems i am not sitting next to my pc, i will try to get these. Thank you for your answer.
Since this morning I am running logcat and kmsg, but no reboots since i started capturing.
Full logs: kmsg.log logcat.log
Edit: Sorry I have seen you wanted last_kmsg, I have attached it now
log is very long so I hope I found all relevant information, don't know but this seems to be relevant:
Code:
E/ConsumerIrService( 1902): Can't open consumer IR HW Module, error: -2
[...]
E/FlpHardwareProvider( 1902): Error hw_get_module 'flp': -2
E/FlpHardwareProvider( 1902): Error hw_get_module 'flp': -2
I ran kmsg the first time, so I don't know what is relevant, but I think this could be, since it is returning over and over again:
Code:
<6>[ 745.429565] msm_vidc_enc: Inside vid_enc_open()
<4>[ 745.433837]
<4>[ 745.433837] res_trk_download_firmware(): Request firmware download
<6>[ 745.592529] Loading CONTROL_FW of FW_SIZE 9000
<6>[ 745.598175]
<6>[ 745.598175] msm_vidc_enc: Inside vid_enc_release()
<6>[ 745.598449]
<6>[ 745.598449] msm_vidc_enc: Inside vid_enc_close_client()
<6>[ 745.600219]
<6>[ 745.600250] msm_vidc_enc: Sending VCD_EVT_RESP_STOP to client
<6>[ 746.333374] [LS][CM3602] ALS value: 0x1, level: 0 #
<6>[ 747.293975] [LS][CM3602] ALS value: 0x0, level: 0 #
<6>[ 747.451019] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 747.548919] call alarm, type 3, func alarm_triggered+0x0/0xd8, 0 (s 0)
<6>[ 749.616058] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1526265000000 (s 1526265000000)
<6>[ 750.089538] microp_led_pwm_brightness_set, data[1] = 0
<3>[ 750.597900] vid_enc_close_client:ERROR vcd_stop time outrc = 0
<6>[ 750.627227]
<6>[ 750.627227] msm_vidc_enc: Return from vid_enc_release()
<6>[ 750.672058] [CAM]msm_enqueue: queue event new max is 6
<6>[ 750.893615] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 750.895965] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1526264000000 (s 1526264000000)
<6>[ 751.206268] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 751.206787] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1526265000000 (s 1526265000000)
<6>[ 751.710205] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 751.710632] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1526265000000 (s 1526265000000)
<4>[ 752.062774] send sigkill to 5943 (nt.android.mail), adj 764, size 6342
<6>[ 753.234069] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1529883000000 (s 1529883000000)
<4>[ 753.447265] send sigkill to 5929 (droid.gallery3d), adj 647, size 4243
<4>[ 754.797363] send sigkill to 6155 (.bitspin.timely), adj 647, size 10701
<6>[ 755.095642] microp_led_pwm_brightness_set, data[1] = 45
<6>[ 760.327087] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1536976000000 (s 1536976000000)
<6>[ 760.764038] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1537413000000 (s 1537413000000)
<6>[ 760.990051] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1537639000000 (s 1537639000000)
<6>[ 761.089080] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1537738000000 (s 1537738000000)
<6>[ 762.833496] [CAM] vfe31_proc_general: V31_STOP
<6>[ 762.833587] [CAM]vfe_stop() enter
<6>[ 762.834442] [CAM]vfe_stop() exit
<6>[ 762.834625] [CAM] irq resetAckIrq
<6>[ 762.834747] [CAM] irq resetAckIrq
<6>[ 762.893371] [CAM]msm_release_frame: frame0
<6>[ 762.893463] [CAM]__msm_release:sync->opencnt:3
<6>[ 762.895507] [CAM]release frame atomic_set pmsm->opened as 0
<6>[ 762.895629] [CAM] msm_release_frame: draining queue frame
<6>[ 762.895812] [CAM]msm_release_frame,q->len = 0
<6>[ 762.903411] [CAM] msm_release_frame, completed
<6>[ 763.018707] [CAM] msm_pmem_table_add: type 15, paddr 0x2dd96000, vaddr 0x43b30000
<6>[ 763.031066] [CAM] msm_pmem_table_add: type 15, paddr 0x2dee8000, vaddr 0x43f4a000
<6>[ 763.036804] [CAM] msm_pmem_table_add: type 15, paddr 0x2e03a000, vaddr 0x4426a000
<6>[ 763.047454] [CAM] msm_pmem_table_add: type 15, paddr 0x2e18c000, vaddr 0x446a3000
<6>[ 763.069427] [CAM] msm_pmem_table_add: type 15, paddr 0x2e2de000, vaddr 0x44a4e000
<6>[ 763.085021] [CAM] msm_pmem_table_add: type 15, paddr 0x2e430000, vaddr 0x44de3000
<6>[ 763.094635] [CAM] msm_pmem_table_add: type 15, paddr 0x2e582000, vaddr 0x450a0000
<6>[ 763.103454] [CAM] msm_pmem_table_add: type 14, paddr 0x2e6d4000, vaddr 0x45237000
<6>[ 763.110900] [CAM] msm_pmem_table_add: type 14, paddr 0x2e826000, vaddr 0x45389000
<6>[ 763.116973] [CAM] msm_pmem_table_add: type 14, paddr 0x2e978000, vaddr 0x454db000
<6>[ 763.153625] [CAM] msm_pmem_table_add: type 14, paddr 0x2eaca000, vaddr 0x4562d000
<6>[ 763.171356] [CAM] msm_pmem_table_add: type 14, paddr 0x2ec1c000, vaddr 0x4577f000
<6>[ 763.180114] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1539829000000 (s 1539829000000)
<6>[ 763.186645] [CAM] msm_pmem_table_add: type 14, paddr 0x2ed6e000, vaddr 0x458d1000
<6>[ 763.199859] [CAM] msm_pmem_table_add: type 14, paddr 0x2eec0000, vaddr 0x45a23000
<6>[ 763.225616] [CAM] msm_pmem_table_add: type 14, paddr 0x2f012000, vaddr 0x45b75000
<6>[ 763.241241] [CAM] msm_pmem_table_add: type 16, paddr 0x2f164000, vaddr 0x45cc7000
<4>[ 763.254211] [CAM]msm_pp_release: pp not in progress for 0
<6>[ 763.255645] [CAM] vfe31_proc_general: V31_RESET
<6>[ 763.255859] [CAM] irq resetAckIrq
<6>[ 763.263153] [CAM] vfe31_config_axi: mode = 3, bufnum1 = 3, bufnum2 = 3
<6>[ 763.286712] [CAM] vfe31_proc_general: V31_START
<6>[ 763.288665] [CAM] VFE opertaion mode = 0x2.
<6>[ 763.288848] [CAM] VFE output path out mode = 0x5.
<6>[ 763.344512] [CAM] irq camifSofIrq, count 1
<6>[ 763.354034] [CAM] irq startAckIrq
<6>[ 763.354278] [CAM] msm_camio_disable_csi_log
<6>[ 763.379516] [CAM]>>>>>>>>(2014-04-30 06:17:13.763715307 UTC)<<<<<<<
<6>[ 763.379791] [CAM]msm_open_common: open frame0
<6>[ 763.379882] [CAM] msm_open_common: rc 0
<4>[ 763.969879] send sigkill to 5738 (gle.android.gms), adj 647, size 5183
<6>[ 764.134490]
<6>[ 764.134490] msm_vidc_enc: Inside vid_enc_open()
<6>[ 764.193817] Loading CONTROL_FW of FW_SIZE 9000
<6>[ 764.206939]
<6>[ 764.206939] msm_vidc_enc: Inside vid_enc_release()
<6>[ 764.208923]
<6>[ 764.208953] msm_vidc_enc: Inside vid_enc_close_client()
<6>[ 764.209320]
<6>[ 764.209320] msm_vidc_enc: Sending VCD_EVT_RESP_STOP to clientsend sigkill to 6186 (nt.android.mail), adj 529, size 7345
<6>[ 764.723083] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1541372000000 (s 1541372000000)
<4>[ 764.739593] send sigkill to 5086 (ndroid.settings), adj 529, size 5385
<6>[ 768.847198] microp_led_pwm_brightness_set, data[1] = 0
<3>[ 769.207122] vid_enc_close_client:ERROR vcd_stop time outrc = 0
<6>[ 769.237396]
The logcat would have to be running during reboot to get much out of it, so if its not easily replicable then try to get the kernel log. So right after reboot grab the last_kmsg, this should give the reason for the reboot
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thank you for your help, I will see what I can do, but my phone is really annoying me. Everytime I am at home, and have the possibility to get logcat during reboot my phone runs perfectly, but when I am outside you can imagine what it does.
If I am not able to get a logcat soon or the problems suddenly stop, I will buy a new phone.
At home are you always on WiFi? Maybe there is an issue with your radio where switching between 3g/2g or whatever causes constant reboots?
Just a thought but maybe try flashing a new radio
Sent from my Nexus 7 using XDA Premium 4 mobile app
I am using latest radio 26.13.04.19_M since last summer and haven't had any problems yet. I will reflash it and if problems aren't gone I will try to downgrade. Perhaps something is messed up.
No I am not constantly on WiFi, besides my WiFi does not reach all rooms/floors so my phone sometimes switches to 3g. Also it is not constantly rebooting, it may work some hours, a day (only yesterday), or only half an hour, I am doing different actions, while getting reboots. Like sending a video with WhatsApp or something else, even if I do nothing, it is just laying around on a table.
Flashing new radio reduced the reboots, but they aren't gone. Now I also have network-connection issues, my phone disconnect itself from carrier (with full signal strength, my friends with same carrier have also full signal strength at the same time), I am missing important phone calls, so I flashed back 26.13.04.19_M, but the problem isn't gone. Force closes with apps which worked fine before (like WhatsApp) are increasing.
Since three days my phone does not recognize my original charger correctly, it needs about 4 hours to get 100%, wiping battery stats didn't helped. Perhaps it is more than three days, normally I plug in charger when I go sleeping. This is happening with two original batteries (one I bought last year).
I do not have any hope left I was wrong with hardware problem. So I will buy LG G2 on Tuesday, if I can't reduce the problems, I need a working phone.
Hi folks!
I purchased an OTG micro-sd reader, but I get the power consumption error when I plug it in my rooted Z1c 5.1.1.
I learned about the /sys/bus/usb/devices/1-1/bConfigurationValue trick, but my /devices/ folder is empty so I can't use it...
Here is the relevant log from dmesg:
<6>[ 1632.217199] xhci-hcd xhci-hcd: xHCI Host Controller
<6>[ 1632.217212] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 1
<6>[ 1632.217293] xhci-hcd xhci-hcd: irq 163, io mem 0xf9200000
<6>[ 1632.218513] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 1632.218520] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 1632.218525] usb usb1: Product: xHCI Host Controller
<6>[ 1632.218530] usb usb1: Manufacturer: Linux 3.4.0-perf-gd26777b-00851-ga8b7b55 xhci-hcd
<6>[ 1632.218535] usb usb1: SerialNumber: xhci-hcd
<7>[ 1632.219525] xHCI xhci_add_endpoint called for root hub<7>[ 1632.219531] xHCI xhci_check_bandwidth called for root hub
<6>[ 1632.220004] hub 1-0:1.0: USB hub found
<6>[ 1632.220016] hub 1-0:1.0: 1 port detected
<6>[ 1632.220670] xhci-hcd xhci-hcd: xHCI Host Controller
<6>[ 1632.220680] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 2
<6>[ 1632.220723] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
<6>[ 1632.220729] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 1632.220734] usb usb2: Product: xHCI Host Controller
<6>[ 1632.220738] usb usb2: Manufacturer: Linux 3.4.0-perf-gd26777b-00851-ga8b7b55 xhci-hcd
<6>[ 1632.220743] usb usb2: SerialNumber: xhci-hcd
<7>[ 1632.221100] xHCI xhci_add_endpoint called for root hub<7>[ 1632.221105] xHCI xhci_check_bandwidth called for root hub
<6>[ 1632.221811] hub 2-0:1.0: USB hub found
<6>[ 1632.221824] hub 2-0:1.0: 1 port detected
<4>[ 1632.324911] healthd: battery l=71 v=3941 t=41.8 h=2 st=3 c=-358 chg=
<4>[ 1632.379681] healthd: battery l=71 v=3949 t=41.9 h=2 st=3 c=-510 chg=
<6>[ 1632.538218] usb 1-1: new high-speed USB device number 2 using xhci-hcd
<6>[ 1632.559752] usb 1-1: New USB device found, idVendor=14cd, idProduct=1212
<6>[ 1632.559764] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=2
<6>[ 1632.559775] usb 1-1: Product: Mass Storage Device
<6>[ 1632.559783] usb 1-1: Manufacturer: Generic
<6>[ 1632.559791] usb 1-1: SerialNumber: 121220130416
<4>[ 1632.560162] usb 1-1: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1632.561670] usb 1-1: ep 0x2 - rounding interval to 32768 microframes, ep desc says 0 microframes
<6>[ 1632.563063] scsi8 : usb-storage 1-1:1.0
<6>[ 1632.628390] qpnp_chg_check_unpluged_charger: Assume reverse boost issue happens
<5>[ 1633.558981] scsi 8:0:0:0: Direct-Access Mass Storage Device 1.00 PQ: 0 ANSI: 0 CCS
<3>[ 1633.609919] qpnp_regulator_vs_ocp_isr: 8941_mvs1: OCP triggered 11 times; no further retries
<6>[ 1633.613501] usb 1-1: USB disconnect, device number 2
<6>[ 1633.613717] dwc3_ocp_work: receive ocp notification
<6>[ 1633.613725] dwc3 f9200000.dwc3: XCVR: ID clear
<6>[ 1633.613730] dwc3 f9200000.dwc3: XCVR: BSV clear
<6>[ 1633.613737] dwc3 f9200000.dwc3: a_host state
<6>[ 1633.613873] xhci-hcd xhci-hcd: remove, state 1
<6>[ 1633.613884] usb usb2: USB disconnect, device number 1
<7>[ 1633.614020] xHCI xhci_drop_endpoint called for root hub
<7>[ 1633.614025] xHCI xhci_check_bandwidth called for root hub
<6>[ 1633.614311] xhci-hcd xhci-hcd: USB bus 2 deregistered
<6>[ 1633.614320] xhci-hcd xhci-hcd: remove, state 1
<6>[ 1633.614329] usb usb1: USB disconnect, device number 1
<5>[ 1633.628477] sd 8:0:0:0: [sda] READ CAPACITY failed
<6>[ 1633.628490] sd 8:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<5>[ 1633.628497] sd 8:0:0:0: [sda] Sense not available.
<5>[ 1633.628539] sd 8:0:0:0: [sda] Write Protect is off
<7>[ 1633.628549] sd 8:0:0:0: [sda] Mode Sense: 13 01 00 00
<5>[ 1633.628586] sd 8:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
<5>[ 1633.629184] sd 8:0:0:0: [sda] Attached SCSI removable disk
<3>[ 1633.630437] hub 1-0:1.0: hub_port_status failed (err = -19)
<3>[ 1633.630449] hub 1-0:1.0: connect-debounce failed, port 1 disabled
<7>[ 1633.630608] xHCI xhci_drop_endpoint called for root hub
<7>[ 1633.630613] xHCI xhci_check_bandwidth called for root hub
<6>[ 1633.630940] xhci-hcd xhci-hcd: USB bus 1 deregistered
<4>[ 1633.679917] healthd: battery l=71 v=3916 t=42.0 h=2 st=3 c=-776 chg=
<4>[ 1633.719931] healthd: battery l=71 v=3898 t=42.1 h=2 st=3 c=-911 chg=
<6>[ 1633.924292] usb_host_ext_event: sending USB_HOST_VBUS_DROP event
<6>[ 1633.925266] dwc3 f9200000.dwc3: a_idle state
<6>[ 1634.118262] qpnp_chg_rb_work: stopping worker usb/dc disconnected
<4>[ 1634.184094] healthd: battery l=71 v=3906 t=42.0 h=2 st=3 c=-841 chg=
<4>[ 1634.212750] healthd: battery l=71 v=3905 t=42.0 h=2 st=3 c=-774 chg=
Click to expand...
Click to collapse
I tried plugging the reader on the OTG Sony cable I got with the phone, same error message.
Any idea?
People online mention a "USB detection" toggle but I don't seem to have such a thing.
Cheers!
Edit: the reader works fine on my computer, and another USB drive works fine on the phone with my OTG cable.
I think this specific micro-sd reader exceeds the mA threshold set on the phone, and I would like to override that threshold.