Develop Bugs

[Q] [Hlep]Can only use the CM9 Rom. others stuck at HTC page

My inc2 is always at the htc face, i have tried the RUU, with the USB, and also tried the rom.zip to TF card,with the PG32IMG.zip.
but they did not work.
I can go into the hboot and recovery.
it is s-off.
and now what else can I do.
thanks!!!!!!!!!
[update] i just found that i can only use the cm9 rom.
http://forum.xda-developers.com/showthread.php?t=1561816
so, what the difference of CM9 and others?

Go into recovery.. wipe all data and then flash a rom...
Sent from my Incredible 2 using Tapatalk 2

THE PG32IMG has to be installed from the bootloader. make sure it doesn.t have two zips on it : power down phone hold power button and volume down at same time to get bootloader and if the zip on ROOT of sd card is ok it will pick it up and install it.
what rom are you running now

i have tried a few roms, and today i use the PG32IMG.zip from the forum
this link. http://forum.xda-developers.com/showthread.php?t=1599767
it still does not work.
i am very very puzzle...

i have tried "dmesg | grep mmc0" on adb shell
will u tell me sth from the following information?
<3>[ 10.749847] mmc0: No card detect facilities available
<6>[ 10.750488] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 10.750640] mmc0: Platform slot type: MMC
<6>[ 10.750762] mmc0: 4 bit data mode disabled
<6>[ 10.751007] mmc0: 8 bit data mode enabled
<6>[ 10.751159] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 10.751403] mmc0: Slot eject status = 0
<6>[ 10.751525] mmc0: Power save feature enable = 1
<6>[ 10.751647] mmc0: DM non-cached buffer at ffa0d000, dma_addr 0x2a4b0000
<6>[ 10.751953] mmc0: DM cmd busaddr 0x2a4b0000, cmdptr busaddr 0x2a4b0300
<4>[ 10.864257] mmc0: high speed mode max_dtr = 50000000
<4>[ 10.864593] mmc0: host does not support reading read-only switch. assuming
write-enable.
<6>[ 10.864807] mmc0: new high speed SDHC card at address aaaa
<6>[ 10.865875] mmcblk0: mmc0:aaaa SE04G 3.69 GiB

Does recovery say anything when you try to install roms?
Sent from here

i can flash all the roms of IC2.
and i also can change different kinds of recoveries.
the rec works well.

anyone can help me ?
i have no idea for a few days already.
thanks .

Maybe your partitions are ext4? Try converting back to ext3
Sent from my Xoom using XDA Premium HD app

Use 4ext recovery man... it auto converts it
Sent from my Incredible 2 using Tapatalk 2

it should not be the matter of filesystem.
i have changed Ext3 and ext4 for a try , it didn't work.

[Q] sdcard suddenly stopped working

I have had my refurbished HTC Vision for about three weeks and it hadn't had any problems. Then yesterday, I rebooted it and now the sdcard doesn't work. Not just that it doesn't mount, rather there is not even a /dev/block/mmcblk1 device.
Here is what I tried:
* Boot into ClockworkMod, and run adb shell. Still no /dev/block/mmcblk1.
* Boot into fastboot and run "fastboot oem enableqxdm 0" and "fastboot oem eraseconfig".
* Per some random instructions on the net, I held vol-up and power, then pulled the battery after the phone vibrated. Then I held vol-up, vol-down, power and did the same. Then the fastboot commands again.
* Bent the sdcard port's pins out a bit with tweezers.
* SDcard works in computer (Linux).
* Tried another card that has nothing but a vfat partition.
Nothing works! There are some errors in dmesg:
Code:
$ dmesg |grep mmc
<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.02.01.15_M2 androidboot.cid=T-MOB010 androidboot.batt_poweron=good_battery androidboot.carrier=TMUS androidboot.mid=PC1010000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT09LR200858 androidboot.bootloader=0.76.2000 no_console_suspend=1 console=null
<6>[ 2.532989] vision: vision_init_mmc
<3>[ 3.267822] mmc0: No card detect facilities available
<6>[ 3.268341] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 3.268615] mmc0: Platform slot type: MMC
<6>[ 3.268737] mmc0: 4 bit data mode disabled
<6>[ 3.269012] mmc0: 8 bit data mode enabled
<6>[ 3.269134] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.269378] mmc0: Slot eject status = 0
<6>[ 3.269531] mmc0: Power save feature enable = 1
<6>[ 3.269653] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2b774000
<6>[ 3.269927] mmc0: DM cmd busaddr 0x2b774000, cmdptr busaddr 0x2b774300
<6>[ 3.270751] mmc1: Qualcomm MSM SDCC at 0x00000000a3000000 irq 96,0 dma 8
<6>[ 3.270996] mmc1: Platform slot type: N/A
<6>[ 3.271148] mmc1: 4 bit data mode enabled
<6>[ 3.271392] mmc1: 8 bit data mode disabled
<6>[ 3.271514] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.271789] mmc1: Slot eject status = 1
<6>[ 3.271911] mmc1: Power save feature enable = 1
<6>[ 3.272064] mmc1: DM non-cached buffer at ffa0d000, dma_addr 0x2b777000
<6>[ 3.272308] mmc1: DM cmd busaddr 0x2b777000, cmdptr busaddr 0x2b777300
<6>[ 3.273468] mmc2: Qualcomm MSM SDCC at 0x00000000a3100000 irq 100,0 dma 8
<6>[ 3.273712] mmc2: Platform slot type: SD
<6>[ 3.273834] mmc2: 4 bit data mode enabled
<6>[ 3.273986] mmc2: 8 bit data mode disabled
<6>[ 3.274230] mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.274353] mmc2: Slot eject status = 0
<6>[ 3.274658] mmc2: Power save feature enable = 1
<6>[ 3.274810] mmc2: DM non-cached buffer at ffa0e000, dma_addr 0x2b778000
<6>[ 3.275054] mmc2: DM cmd busaddr 0x2b778000, cmdptr busaddr 0x2b778300
<6>[ 3.275207] mmc2: Polling status mode enabled
<6>[ 3.425598] mmc0: new high speed MMC card at address 0001
<6>[ 3.427093] mmcblk0: mmc0:0001 SEM04G 2.09 GiB
<6>[ 3.428100] mmcblk0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 >
<6>[ 3.569030] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 3.703063] mmc2: high speed mode max_dtr = 50000000
<4>[ 3.703491] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 3.703643] mmc2: new high speed SDHC card at address 0001
<6>[ 3.704498] mmcblk1: mmc2:0001 00000 7.41 GiB
<6>[ 3.705291] mmcblk1: p1
<4>[ 4.648254] EXT4-fs (mmcblk0p26): warning: maximal mount count reached, running e2fsck is recommended
<7>[ 4.651062] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24790
<7>[ 4.655670] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24741
<6>[ 4.657012] EXT4-fs (mmcblk0p26): 2 orphan inodes deleted
<6>[ 4.657379] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 4.703216] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts: noauto_da_alloc
<4>[ 4.758331] EXT4-fs (mmcblk0p27): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.760345] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 4.762298] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 4.886474] EXT4-fs (mmcblk0p28): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.888580] EXT4-fs (mmcblk0p28): recovery complete
<6>[ 4.890563] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: barrier=1
<7>[ 20.824981] mmc1: card_present 1
<6>[ 20.825134] mmc1: Slot status change detected (0 -> 1)
<7>[ 23.383300] mmc1: queuing CIS tuple 0x91 length 3
<6>[ 23.383331] mmc1: new high speed SDIO card at address 0001
<3>[ 38.746368] mmc2: Data CRC error
<6>[ 38.746978] mmc2: Controller has been reset
<3>[ 38.747467] mmcblk1: error -84 transferring data, sector 2080, nr 1, card status 0x900
<6>[ 38.747619] mmc2: reinit card
<4>[ 38.747863] mmc2: Starting deferred resume
<3>[ 38.814849] mmc2: Data CRC error
<6>[ 38.815521] mmc2: Controller has been reset
<3>[ 38.815856] mmc2: Re-init card rc = -84 (retries = 5)
<3>[ 38.997650] mmc2: Data CRC error
<6>[ 38.998291] mmc2: Controller has been reset
<3>[ 39.001403] mmc2: Re-init card rc = -84 (retries = 4)
<3>[ 39.200927] mmc2: Data CRC error
<6>[ 39.201507] mmc2: Controller has been reset
<3>[ 39.201721] mmc2: Re-init card rc = -84 (retries = 3)
<3>[ 39.384826] mmc2: Data CRC error
<6>[ 39.385406] mmc2: Controller has been reset
<3>[ 39.385650] mmc2: Re-init card rc = -84 (retries = 2)
<3>[ 39.583618] mmc2: Data CRC error
<6>[ 39.584228] mmc2: Controller has been reset
<3>[ 39.584472] mmc2: Re-init card rc = -84 (retries = 1)
<6>[ 39.666137] mmc2: Deferred resume failed
<6>[ 39.666412] mmc: reinit failed, remove card
<6>[ 39.666625] mmc2: remove card
<3>[ 39.666778] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.667053] Buffer I/O error on device mmcblk1p1, logical block 32
<4>[ 39.667205] lost page write due to I/O error on mmcblk1p1
<3>[ 39.667480] mmc_blk_issue_rq failed!!
<6>[ 39.667633] mmc2: mmc_remove_sd_card
<6>[ 39.667907] mmc2: card 0001 removed
<3>[ 39.670318] mmcblk1: error -123 sending status comand
<3>[ 39.670471] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.670867] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.671783] mmc_blk_issue_rq failed!!
<3>[ 39.671966] mmcblk1: error -123 sending read command, response 0x0
<4>[ 39.672210] mmcblk1: retrying using single block read
<3>[ 39.672332] mmcblk1: error -123 sending status comand
<3>[ 39.672607] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.672882] end_request: I/O error, dev mmcblk1, sector 32378
<3>[ 39.673126] end_request: I/O error, dev mmcblk1, sector 32379
<3>[ 39.673278] end_request: I/O error, dev mmcblk1, sector 32380
<3>[ 39.673522] end_request: I/O error, dev mmcblk1, sector 32381
<3>[ 39.673675] end_request: I/O error, dev mmcblk1, sector 32382
<3>[ 39.673919] end_request: I/O error, dev mmcblk1, sector 32383
<3>[ 39.674072] end_request: I/O error, dev mmcblk1, sector 32384
<3>[ 39.674316] end_request: I/O error, dev mmcblk1, sector 32385
<3>[ 39.674499] mmc_blk_issue_rq failed!!
<3>[ 39.674774] mmcblk1: error -123 sending status comand
<3>[ 39.674926] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.675292] end_request: I/O error, dev mmcblk1, sector 32378
... and so on. In this run, I see that at least briefly the kernel could read the mmcblk1 partition table (although there still was not /dev/block/mmcblk1). However, most of the time it can't and just gives the CRC errors.
Is this a hardware or software problem. Any suggestions? Thanks.

Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium

worked!
demkantor said:
Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Worked, thanks!!! The CRC errors made me suspect hardware, but I wanted someone else to say it before I tore the thing open. I've always had bad luck tearing these things apart (only junk phones in the past), but I bought a cheapo disassembly kit a while back which has helped greatly with popping the case off. And thankfully I only had to get to about step three of the instructions before the ribbon cable was accessible!

[Q] Desire Z (Tmobile G2) Help do I have eMMC problem noted in this forum, HELP!

Hello, I am asking for help. I am new to this forum.
I have a T-Mobile G2 (HTC Vision Z equiv) that I was given by a friend. He rooted it and put CyanogenMod on it.
Two days ago, the phone rebooted of its own, and stayed stuck at the HTC white screen.
I did take the battery out and reinserted it in order to reboot the phone ( I have read several forum threads here about eMMc and battery problems resulting from battery removal, fwtw)
I am asking for assistance to determine if I can restore this phone, if its suffering the eMMC problem that has been noted in this forum, etc. I'm okay with the command line, new to Android hacking, so please keep your comments light.
On my laptop, I am running Linux Mint Nadia 14, I have the Android SDK installed and Oracle Java latest as well. I can bring the phone, plugged in via USB<-->MicroUSB cable, up in Android Debug Bridge, and see its serial number with ./adb devices, as long as my udev and the adb server are started in the right order
I can, using VOL-DOWN and POWER, get to HBOOT. Here is the headers:
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
and below, I have:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
I can then get the phone to RECOVERY,
ClockWorkMod Recovery v3.0.2.4
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recover/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Now, on my laptop, from the platform-tools directory, I can issue:
platform-tools # ./adb devices
List of devices attached
SH12SR201118 recovery
and I can enter adb-shell:
platform-tools # ./adb shell
~ # ls
boot init sys
cache init.rc system
data proc tmp
datadata res ueventd.goldfish.rc
default.prop root ueventd.rc
dev sbin ueventd.vision.rc
emmc sd-ext
etc sdcard
Now the disturbing bits begin, that make me suspect the fried eMMc.
According to /etc/fstab, which when cat'd, yields:
/etc # cat fstab
/dev/block/mmcblk0p27 /cache auto rw
/dev/block/mmcblk0p26 /data auto rw
/dev/block/mmcblk0p25 /system auto rw
/dev/block/mmcblk1p1 /sdcard vfat rw
So is it correct that on my internal eMMC, that is /dev/block/mmcblk0p27 for /cache, ...0p26 for /data, etc?
fdisk is unable to give me any information about /dev/block/mmcblk0:
/etc # /sbin/fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/block/mmcblk0': I/O error
while fdisk is fine to give me information about my sdcard (mmcblk1, according to fstab cat'd above):
/etc # /sbin/fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 2001 MB, 2001731584 bytes
42 heads, 41 sectors/track, 2270 cylinders
Units = cylinders of 1722 * 512 = 881664 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 2271 1954751+ 6 FAT16
Okay, xda folks, what should my next steps be?
thank you very very much,
Forrest :cyclops:

And...where should I go in xda to find actual help?
40 views of this message....and not a single reply? Where do I go for help?

http://forum.xda-developers.com/showthread.php?p=43195539
Sent from my Nexus 4 using Tapatalk 2

That's an information repository for sure, but...
demkantor, you posted a link to your gold mine of information http://forum.xda-developers.com/showthread.php?p=43195539. that's wonderful.
I will use the eMMC testing tips at http://forum.xda-developers.com/showthread.php?t=1983163. Remember that I posted a fairly complete description in my post of my situation....

Does this mean I have a fried eMMC? Looks like it. could someone verify?
Using the procedures on the page http://forum.xda-developers.com/showthread.php?t=1983163, i found the following:
In ADB shell, grepping for the eMMC yields this:
~ # dmesg | grep mmc0
<3>[ 4.904113] mmc0: No card detect facilities available
<6>[ 4.904663] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8
<6>[ 4.904907] mmc0: Platform slot type: MMC
<6>[ 4.905059] mmc0: 4 bit data mode disabled
<6>[ 4.905273] mmc0: 8 bit data mode enabled
<6>[ 4.905426] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.905670] mmc0: Slot eject status = 0
<6>[ 4.905792] mmc0: Power save feature enable = 1
<6>[ 4.905914] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x0bb9a000
<6>[ 4.906158] mmc0: DM cmd busaddr 0x0bb9a000, cmdptr busaddr 0x0bb9a300
<6>[ 5.065429] mmc0: new high speed MMC card at address 0001
<6>[ 5.067108] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB
<3>[ 6.364196] mmc0: failed to get card ready
<6>[ 6.364440] mmc0: reinit card
<4>[ 6.364562] mmc0: Starting deferred resume
<6>[ 8.404327] mmc0: Deferred resume failed
<3>[ 8.510040] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.511199] mmc0: Controller has been reset
<6>[ 8.511962] mmc0: Worked around bug 1535304
<3>[ 8.514099] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.515228] mmc0: Controller has been reset
<6>[ 8.515655] mmc0: Worked around bug 1535304
<6>[ 8.524291] mmc0: reinit card
<4>[ 8.524963] mmc0: Starting deferred resume
<6>[ 10.564331] mmc0: Deferred resume failed
<3>[ 10.715789] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.716217] mmc0: Controller has been reset
<6>[ 10.716430] mmc0: Worked around bug 1535304
<3>[ 10.717803] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.718200] mmc0: Controller has been reset
<6>[ 10.718414] mmc0: Worked around bug 1535304
<6>[ 10.725219] mmc0: reinit card
<4>[ 10.725433] mmc0: Starting deferred resume
<6>[ 12.764282] mmc0: Deferred resume failed
<3>[ 12.766510] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.766967] mmc0: Controller has been reset
<6>[ 12.767181] mmc0: Worked around bug 1535304
<3>[ 12.768585] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.769042] mmc0: Controller has been reset
<6>[ 12.769226] mmc0: Worked around bug 1535304
<6>[ 12.776184] mmc0: reinit card
<4>[ 12.776306] mmc0: Starting deferred resume
<6>[ 14.814331] mmc0: Deferred resume failed
<3>[ 14.936950] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.937408] mmc0: Controller has been reset
<6>[ 14.937622] mmc0: Worked around bug 1535304
<3>[ 14.938964] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.939422] mmc0: Controller has been reset
<6>[ 14.939727] mmc0: Worked around bug 1535304
<6>[ 14.946594] mmc0: reinit card
<4>[ 14.946716] mmc0: Starting deferred resume
<6>[ 16.984283] mmc0: Deferred resume failed
<3>[ 16.986480] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.986938] mmc0: Controller has been reset
<6>[ 16.987152] mmc0: Worked around bug 1535304
<3>[ 16.988525] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.988983] mmc0: Controller has been reset
<6>[ 16.989257] mmc0: Worked around bug 1535304
<6>[ 16.996093] mmc0: reinit card
<4>[ 16.996215] mmc0: Starting deferred resume
<6>[ 19.034301] mmc0: Deferred resume failed
<3>[ 19.175415] mmc0: DMA channel flushed (0x80000004)
<6>[ 19.175872] mmc0: Controller has been reset
<6>[ 19.176208] mmc0: Worked around bug 1535304
<3>[ 19.177459] mmc0: DMA channel flushed (0x80000004)
<6>[ 19.177917] mmc0: Controller has been reset
<6>[ 19.178222] mmc0: Worked around bug 1535304
<6>[ 19.185028] mmc0: reinit card
<4>[ 19.185180] mmc0: Starting deferred resume
<6>[ 21.224273] mmc0: Deferred resume failed
<3>[ 21.226348] mmc0: DMA channel flushed (0x80000004)
<6>[ 21.226806] mmc0: Controller has been reset
<6>[ 21.227111] mmc0: Worked around bug 1535304
<3>[ 21.228393] mmc0: DMA channel flushed (0x80000004)
<6>[ 21.228942] mmc0: Controller has been reset
<6>[ 21.229156] mmc0: Worked around bug 1535304
<6>[ 21.235961] mmc0: reinit card
<4>[ 21.236083] mmc0: Starting deferred resume
<6>[ 23.274291] mmc0: Deferred resume failed

Perhaps I should have posted in General?
I am reading the thread at http://forum.xda-developers.com/showthread.php?t=1039504&page=3, which appears to be in General, about fried eMMCs in the Desire.
If anyone reading this can verify that my phone indeed has that condition (fried eMMC), thanks!

[Q] soft bricked or hardware fried?

hello dear all desire users, I've got this desire hd of my friend and it keeps boot looping, in the recovery i get
E:can't mount /cache/recover/command
E:can't mount /cache/recover/log
E:can't mount /cache/recover/last_log
E:can't open /cache/recovery/log
E:can't open /cache/recovery/last_log
I have tried flashing RUU on fastboot but it didn't help and i have read a thread of other device about this internal card fried thingy then i have done my adb shell lookup and heres the output
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 6.260070] mmc0: No card detect facilities available
<6>[ 6.260803] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 6.260955] mmc0: Platform slot type: MMC
<6>[ 6.261199] mmc0: 4 bit data mode disabled
<6>[ 6.261352] mmc0: 8 bit data mode enabled
<6>[ 6.261474] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 6.261718] mmc0: Slot eject status = 0
<6>[ 6.261871] mmc0: Power save feature enable = 1
<6>[ 6.262115] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2aa2f000
<6>[ 6.262268] mmc0: DM cmd busaddr 0x2aa2f000, cmdptr busaddr 0x2aa2f300
<3>[ 6.384063] mmc0: unrecognised CSD structure version 0
<3>[ 6.384246] mmc0: error -22 whilst initialising MMC card
~ #
can someone verify this output and let me know if its dead or can be fixed? a helpful link will be a great help, thanks in advance and sorry for my bad English....

A common problem - anything I can do?

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.