Database Info

[Q] eMMC Fried?

Ok I have searched through all the relevant eMMc fried posts however I have not found a similar post to this with the same cmd return so you help would be appreciated..
After the dmesg grep command this was what the cmd returned...
Code:
C:\android-tools\android-tools>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 7.922210] mmc0: No card detect facilities available
<6>[ 7.922760] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.923004] mmc0: Platform slot type: MMC
<6>[ 7.923126] mmc0: 4 bit data mode disabled
<6>[ 7.923339] mmc0: 8 bit data mode enabled
<6>[ 7.923492] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.923736] mmc0: Slot eject status = 0
<6>[ 7.923858] mmc0: Power save feature enable = 1
<6>[ 7.923980] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2d3000
<6>[ 7.924224] mmc0: DM cmd busaddr 0x0c2d3000, cmdptr busaddr 0x0c2d3300
<6>[ 8.077545] mmc0: new high speed MMC card at address 0001
<6>[ 8.079345] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
Is this a fried chip or some other issue?
I am still getting the usual fried error in the bootloader:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Currently running:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
Thanks for your help.

Your eMMC is fine.
Wipe your /cache from recovery. Use 4EXT

veejayjameson said:
Ok I have searched through all the relevant eMMc fried posts however I have not found a similar post to this with the same cmd return so you help would be appreciated..
After the dmesg grep command this was what the cmd returned...
Code:
C:\android-tools\android-tools>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 7.922210] mmc0: No card detect facilities available
<6>[ 7.922760] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.923004] mmc0: Platform slot type: MMC
<6>[ 7.923126] mmc0: 4 bit data mode disabled
<6>[ 7.923339] mmc0: 8 bit data mode enabled
<6>[ 7.923492] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.923736] mmc0: Slot eject status = 0
<6>[ 7.923858] mmc0: Power save feature enable = 1
<6>[ 7.923980] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2d3000
<6>[ 7.924224] mmc0: DM cmd busaddr 0x0c2d3000, cmdptr busaddr 0x0c2d3300
<6>[ 8.077545] mmc0: new high speed MMC card at address 0001
<6>[ 8.079345] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
Is this a fried chip or some other issue?
I am still getting the usual fried error in the bootloader:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Currently running:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
Thanks for your help.
Click to expand...
Click to collapse
Try wipe the whole phone and install a new rom xD

massi99 said:
Try wipe the whole phone and install a new rom xD
Click to expand...
Click to collapse
+1 Yup, that would be my advice too... it's just your cache partition that gone tits-up, and i think a format of the cache should solve it. But why not just be double sure and nuke all the bloody partitions and do a clean flash!

massi99 said:
Try wipe the whole phone and install a new rom xD
Click to expand...
Click to collapse
apk24 said:
+1 Yup, that would be my advice too... it's just your cache partition that gone tits-up, and i think a format of the cache should solve it. But why not just be double sure and nuke all the bloody partitions and do a clean flash!
Click to expand...
Click to collapse
Only one of the "all the bloody partitions" can give this error. Guess which one is it...
But nothing against the double sure, full wipe and clean install of new ROM should solve this for sure
I recommend to use 4EXT Recovery to convert all partitions to ext4 filesystem, then format/wipe all of them, then install a new ROM
But if he wants to keep the present ROM, just wiping cache is the solution...

amidabuddha said:
Only one of the "all the bloody partitions" can give this error. Guess which one is it...
But nothing against the double sure, full wipe and clean install of new ROM should solve this for sure
I recommend to use 4EXT Recovery to convert all partitions to ext4 filesystem, then format/wipe all of them, then install a new ROM
But if he wants to keep the present ROM, just wiping cache is the solution...
Click to expand...
Click to collapse
My favorite savior of bricked devices!
Wherever there's a potential brick, i find you there... maybe i'm vain, but it sure does make me feel secure knowing that there is someone like you around at the DS forum!

I have the same problem. I think my cache partition is corrupted. But after many try I can't format it. It take long time to format.
Also I cant flash 4ext or anything else via adb, fastboot or clockworkmod.
Can HTC service center solved this? Or they will just change the whole PCB?
Plz help me.
Sent from my HTC Legend using xda premium

enigmaamit said:
My favorite savior of bricked devices!
Wherever there's a potential brick, i find you there... maybe i'm vain, but it sure does make me feel secure knowing that there is someone like you around at the DS forum!
Click to expand...
Click to collapse
+1 to that !

Some how I've f***-up /data and /cache partitions [desperately needing help please]

Hello,
Will installing a new rom on my S-OFF Desire S, it has been a glitch and I've removed the battery to reboot the phone. Now I'm stuck at the "htc logo step".
After some investigation it appears that neither /cache nor /data are now mountable.
I've been think that my eMMc card (which belongs to the faulty serie (M4G2DE)) may have been fried. How ever It appears it is not the case since using adb shell to issue
Code:
# cat /proc/kmsg | grep mmc0
Code:
<3>[ 10.141387] mmc0: No card detect facilities available
<6>[ 10.142028] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 10.142150] mmc0: Platform slot type: MMC
<6>[ 10.142395] mmc0: 4 bit data mode disabled
<6>[ 10.142517] mmc0: 8 bit data mode enabled
<6>[ 10.142639] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 10.142883] mmc0: Slot eject status = 0
<6>[ 10.143005] mmc0: Power save feature enable = 1
<6>[ 10.143249] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0b8c8000
<6>[ 10.143371] mmc0: DM cmd busaddr 0x0b8c8000, cmdptr busaddr 0x0b8c8300
<6>[ 10.296691] mmc0: new high speed MMC card at address 0001
<6>[ 10.297943] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 34.849822] mmc0: Failed to get card ready i = 126959
<6>[ 34.850036] mmc0: reinit card
<4>[ 34.850128] mmc0: Starting deferred resume
<6>[ 36.891876] mmc0: Deferred resume failed
<3>[ 60.337951] mmc0: DMA channel flushed (0x80000004)
<6>[ 60.338317] mmc0: Controller has been reset
<6>[ 60.338562] mmc0: Worked around bug 1535304
<3>[ 60.339935] mmc0: DMA channel flushed (0x80000004)
<6>[ 60.340301] mmc0: Controller has been reset
<6>[ 60.340545] mmc0: Worked around bug 1535304
<6>[ 60.347320] mmc0: reinit card
I've tried to clean the file systems using e2fsck but also to make brand new fs using mke2fs and mkfs.ext2, these processes have be able to run, but the mount still fails :
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
Click to expand...
Click to collapse
I've been going through several thread here and there : http://forum.xda-developers.com/showthread.php?t=1305950 ; http://forum.xda-developers.com/showthread.php?t=1456036 ; http://forum.xda-developers.com/showthread.php?t=1854558
there is some tips inhere but no working solution, have you any suggestions ? Is there any way to "go back" to standard settings for theses two partitions ?
Thanks a lot !
François.

Can you boot to recovery? If so, have you tried formatting the partitions from there?
Sent from my Desire S using xda app-developers app

Can you boot to recovery? If so, have you tried formatting the partitions from there?
Click to expand...
Click to collapse
Yes I can boot to recovery, and I've tried formatting cache/data partitions, it was not successful.
Should I give it a try with ADB shell ?
Thanks for helping !
F.

[email protected] said:
Yes I can boot to recovery, and I've tried formatting cache/data partitions, it was not successful.
Should I give it a try with ADB shell ?
Thanks for helping !
F.
Click to expand...
Click to collapse
Try 4EXT Recovery if you are using different.
Another solution is to flash a RUU it will restore everything. But be carefully for the version, it has to be the same or higher of your current one
EDIT: looked at the first post and I am sorry to say this but your EMMC is corrupted.
Code:
<3>[ 34.849822] mmc0: Failed to get card ready i = 126959
<6>[ 34.850036] mmc0: reinit card
<4>[ 34.850128] mmc0: Starting deferred resume
<6>[ 36.891876] mmc0: Deferred resume failed
Read carefully through this thread there is a scanner that analyzes corrupted emmc card and it *may* (if you are lucky) to isolate the bad blocks and allows to use the device again with a bit shortened storage. No guarantees. The other way is a replacement of the chip - you can find one here

amidabuddha said:
EDIT: looked at the first post and I am sorry to say this but your EMMC is corrupted.
Click to expand...
Click to collapse
My should question should have been "is my eMMC corrupted", thanks for carefully reading my post.
I'll give a try to the software solution ASAP, thanks for pointing it out !

Read carefully through this thread there is a scanner that analyzes corrupted emmc card and it *may* (if you are lucky) to isolate the bad blocks and allows to use the device again with a bit shortened storage. No guarantees. The other way is a replacement of the chip - you can find one here
Click to expand...
Click to collapse
Scan have been able to go through the whole eMMC's partitions. I would like to believe that the eMMC is still some how usable, but it can't use them. Should I try to "shift" the partitions, to try to get ride of the old file system ?
Thanks again,
F.

[email protected] said:
Scan have been able to go through the whole eMMC's partitions. I would like to believe that the eMMC is still some how usable, but it can't use them. Should I try to "shift" the partitions, to try to get ride of the old file system ?
Thanks again,
F.
Click to expand...
Click to collapse
Sorry it didn't helped. Unfortunately I am not aware of any other method besides replacement to suggest
Sent from my HTC Desire S

There are a few threads were they use the sd card to load a rom with fried emc. I don't know anything more about it.
Sent from my Desire S using xda app-developers app

There are a few threads were they use the sd card to load a rom with fried emc. I don't know anything more about it.
Click to expand...
Click to collapse
Yeah this one for example http://forum.xda-developers.com/showthread.php?t=1756287
but I fail using the provided boot.img with fastboot
The other way is a replacement of the chip - you can find one here
Click to expand...
Click to collapse
Since the eMMC seems to be badly fried, I'm now considering physical replacement. So I've watched the following disassembly video : http://www.youtube.com/watch?v=W7sp3gN-vc0
It does not show the mother border without it's protections, so I am wondering what I'll have to do once the protection removed ? any soldering work ?
A last question about the site you've mentioned (parts4repair.com) is it reliable ?

[email protected] said:
Yeah this one for example http://forum.xda-developers.com/showthread.php?t=1756287
but I fail using the provided boot.img with fastboot
Since the eMMC seems to be badly fried, I'm now considering physical replacement. So I've watched the following disassembly video : http://www.youtube.com/watch?v=W7sp3gN-vc0
It does not show the mother border without it's protections, so I am wondering what I'll have to do once the protection removed ? any soldering work ?
A last question about the site you've mentioned (parts4repair.com) is it reliable ?
Click to expand...
Click to collapse
Luckily I have never ordered a chip for myself but this site was referenced from another users in the past. It is even shipped with a bootloader preinstalled so you just have to put it into the device.
As per the soldering process IMO is best to use a services of a skilled technician to do the job
Sent from my HTC Desire S

[Q] Random restarts

My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.

Moon2 said:
My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.
Click to expand...
Click to collapse
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?

DennisBold said:
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?
Click to expand...
Click to collapse
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)

I'm having the same problem with my sensation with alternative battery!!! Please help!!!

It just happened again and I've got another logcat, I'll try and do the dmesg now.
I've tried letting the phone sleep without wifi/3g, taking sd card out, formatting it.

Moon2 said:
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)
Click to expand...
Click to collapse
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?

DennisBold said:
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?
Click to expand...
Click to collapse
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.

Moon2 said:
Miui v4
Click to expand...
Click to collapse
Is your GPS enabled, and does this happen when your GPS is disabled?
Moon2 said:
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.
Click to expand...
Click to collapse
Never really looked at that, well, the only thing I can connect it with is GPS.

DennisBold said:
Is your GPS enabled, and does this happen when your GPS is disabled?
Click to expand...
Click to collapse
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.

Moon2 said:
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.
Click to expand...
Click to collapse
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?

DennisBold said:
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?
Click to expand...
Click to collapse
No, I've tried all of the roms with & without adding any apps.

Moon2 said:
No, I've tried all of the roms with & without adding any apps.
Click to expand...
Click to collapse
There's not exactly any errors other than this on dmesg.
Code:
<3>[ 475.735900] init: cannot execve('/system/bin/DxDrmServerIpc'): Permission denied
That isn't really a problem. Neither are these:
Code:
E/MobileDataStateTracker( 242): Error mapping networkType 23 to apnType.
Code:
D/MobileDataStateTracker( 242): internet: mMobileDataState=DISCONNECTED mTeardownRequested=false got [AnyDataCSC] : type=internet state=DISCONNECTED reason=dataDetached apn=null roaming=false unavailable=true NetworkType=0 NetworkTypeName=UNKNOWN entitleError=0 apnCarrier=null

I've just installed cm9 and run the logcat to just before it rebooted.

Moon2 said:
I've just installed cm9 and run the logcat to just before it rebooted.
Click to expand...
Click to collapse
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.

DennisBold said:
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.
Click to expand...
Click to collapse
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.

Moon2 said:
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.
Click to expand...
Click to collapse
Thanks.
Can you try:
Code:
adb shell
dmesg | grep mmc
And copy and paste the results?
You should see:
Code:
[email protected]:/ # dmesg | grep mmc
dmesg | grep mmc
[email protected]:/ #
---------- Post added at 08:04 PM ---------- Previous post was at 07:33 PM ----------
Could you run?
Code:
cat /sys/class/block/mmcblk0/device/name

Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M

Moon2 said:
Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M
Click to expand...
Click to collapse
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc

DennisBold said:
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc
Click to expand...
Click to collapse
Code:
dmesg | grep mmc
Code:
<5>[ 0.000000] Kernel command line: poweron_status=1 board_pyramid.disable_ua
rt3=0 diag.enabled=0 board_pyramid.debug_uart=0 userdata_sel=0 androidboot.emmc=
true androidboot.pagesize=2048 androidboot.baseband=10.14.9035.01_M androidboo
t.cid=11111111 androidboot.batt_poweron=good_battery androidboot.carrier=ALL and
roidboot.mid=PG5813000 androidboot.keycaps=qwerty androidboot.dq=FAIL androidboo
t.mode=normal androidboot.serialno=SH191V463715 androidboot.bootloader=1.17.1111
zygote_oneshot=off msm_watchdog.enable=1 console=ttyHSL0 androidboot.hardware=p
yramid no_console_suspend=1
<6>[ 0.335052] pyramid: pyramid_init_mmc
<6>[ 0.907806] Create /proc/emmc OK.
<3>[ 2.389921] mmc0: No card detect facilities available
<6>[ 2.390287] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18
<6>[ 2.390379] mmc0: Platform slot type: MMC
<6>[ 2.390562] mmc0: 8 bit data mode enabled
<6>[ 2.390654] mmc0: 4 bit data mode disabled
<6>[ 2.390745] mmc0: polling status mode disabled
<6>[ 2.390928] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.391020] mmc0: Slot eject status = 0
<6>[ 2.391203] mmc0: Power save feature enable = 1
<6>[ 2.391294] mmc0: DM non-cached buffer at ff007000, dma_addr 0x5751b000
<6>[ 2.391386] mmc0: DM cmd busaddr 0x5751b000, cmdptr busaddr 0x5751b300
<6>[ 2.391966] mmc1: Qualcomm MSM SDCC at 0x0000000012180000 irq 134,654 dma
20
<6>[ 2.392149] mmc1: Platform slot type: SD
<6>[ 2.392240] mmc1: 8 bit data mode disabled
<6>[ 2.392332] mmc1: 4 bit data mode enabled
<6>[ 2.392515] mmc1: polling status mode disabled
<6>[ 2.392607] mmc1: MMC clock 144000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.392790] mmc1: Slot eject status = 0
<6>[ 2.392881] mmc1: Power save feature enable = 1
<6>[ 2.392973] mmc1: DM non-cached buffer at ff008000, dma_addr 0x5751c000
<6>[ 2.393156] mmc1: DM cmd busaddr 0x5751c000, cmdptr busaddr 0x5751c300
<6>[ 2.393644] mmc2: Qualcomm MSM SDCC at 0x00000000121c0000 irq 133,0 dma 21
<6>[ 2.393736] mmc2: Platform slot type: N/A
<6>[ 2.393919] mmc2: 8 bit data mode disabled
<6>[ 2.394010] mmc2: 4 bit data mode enabled
<6>[ 2.394102] mmc2: polling status mode disabled
<6>[ 2.394285] mmc2: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.394377] mmc2: Slot eject status = 1
<6>[ 2.394468] mmc2: Power save feature enable = 1
<6>[ 2.394651] mmc2: DM non-cached buffer at ff009000, dma_addr 0x5751d000
<6>[ 2.394743] mmc2: DM cmd busaddr 0x5751d000, cmdptr busaddr 0x5751d300
<6>[ 2.513761] mmc0: new high speed MMC card at address 0001
<6>[ 2.526975] mmcblk0: mmc0:0001 MLL00M 2.25 GiB
<6>[ 2.527555] mmcblk0: p1 p2 p3 p4 < p5 p6
<6>[ 2.568296] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly file
system
<6>[ 2.568662] EXT4-fs (mmcblk0p22): write access will be enabled during reco
very
<4>[ 2.666654] mmc1: high speed mode max_dtr = 50000000
<4>[ 2.667081] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 2.667264] mmc1: new high speed SD card at address 1234
<6>[ 2.667753] mmcblk1: mmc1:1234 SA02G 1.83 GiB
<6>[ 2.668149] mmcblk1: p1
<6>[ 2.697813] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.705625] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mod
e. Opts: (null)
<7>[ 3.291562] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22945
<7>[ 3.292050] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22946
<6>[ 3.292416] EXT4-fs (mmcblk0p23): 2 orphan inodes deleted
<6>[ 3.292691] EXT4-fs (mmcblk0p23): recovery complete
<6>[ 3.334836] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.389493] EXT4-fs (mmcblk0p24): recovery complete
<6>[ 3.397031] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.516964] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 3.521115] EXT4-fs (mmcblk0p27): mounted filesystem with writeback data m
ode. Opts: nodelalloc
<6>[ 20.862468] mmc2: Slot status change detected (0 -> 1)
<7>[ 20.915202] mmc2: queuing CIS tuple 0x91 length 3
<6>[ 20.915446] mmc2: new high speed SDIO card at address 0001
Code:
logcat | grep mmc
I've left it running for a few mins but nothings showing up.

Its still not showing anything, but I'm attaching a logcat on stock gb upto the point it restarted.

E:can't mount /sdcard/

Hello! I have the HTC Desire S and it does that problem! I erased the system, data and cache partitions via fastboot but when I boot into recovery to flash the new ROM I face the problem.
I see:
E:can't mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant mount cache/recovery/last_log
When I try to install the ROM from my sdcard it says " E:can't mount/sdcard.
What sould I do now? Tried flashing new recovery, went well but still I get the same error. Even reflashed the hboot via fastboot.
fastboot finds my phone. But I noticed that when I am in HBOOT the device is not scanning for the update files as it normally should do.
I checked the sdcard and the problem doesnt come from it.
What to do now? Thanks inadvance!
Greetings, Simeon.

sssimo96 said:
Hello! I have the HTC Desire S and it does that problem! I erased the system, data and cache partitions via fastboot but when I boot into recovery to flash the new ROM I face the problem.
I see:
E:can't mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant mount cache/recovery/last_log
When I try to install the ROM from my sdcard it says " E:can't mount/sdcard.
What sould I do now? Tried flashing new recovery, went well but still I get the same error. Even reflashed the hboot via fastboot.
fastboot finds my phone. But I noticed that when I am in HBOOT the device is not scanning for the update files as it normally should do.
I checked the sdcard and the problem doesnt come from it.
What to do now? Thanks inadvance!
Greetings, Simeon.
Click to expand...
Click to collapse
The error messages could mean, that the partition cache is corrupted. Which recovery do you use?
You said, flashing of ROM was unsuccessfull? If not, does booting work?
Have you ever flashed a ROM and got it working? Does flashing another ROM work?

Does that not mean a fried emmc chip? Im sure those error mean that. @ op go to development thread and look at the thread by ben_pyett (rom + guides thread) and go down to the bottom n ul see the links bout fried emmc chip.

I have flashed many ROMs. The problem is that the phone cannot locate the sdcard partition. I already fixed the cache partition but the problem with the sdcard is still present. Will try to push the ROM to the cache partition and then flash it with TWRP recovery.
But anyway is there any chances to fix the error mounting sdcard?
Edit: I think its not fried emmc chip. the command
dmesg | grep mmc0
leads to Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Mimi>cd\adb\platform-tools
C:\adb\platform-tools>adb shell
~ # ←[6ndmesg | grep mmc0
dmesg | grep mmc0
<3>[ 5.873718] mmc0: No card detect facilities available
<6>[ 5.874328] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 5.874481] mmc0: Platform slot type: MMC
<6>[ 5.874725] mmc0: 4 bit data mode disabled
<6>[ 5.874847] mmc0: 8 bit data mode enabled
<6>[ 5.875000] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 5.875244] mmc0: Slot eject status = 0
<6>[ 5.875366] mmc0: Power save feature enable = 1
<6>[ 5.875610] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x0c3e4000
<6>[ 5.875732] mmc0: DM cmd busaddr 0x0c3e4000, cmdptr busaddr 0x0c3e4300
<6>[ 6.028350] mmc0: new high speed MMC card at address 0001
<6>[ 6.029418] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ # ←[6n

Well, this could mean your SDcard isn't connected or it is broken. But you said you checked that already.. well if you can get a ROM running you will then could check if you have access to your card.

I start thinking that there is some hardware issue. I just replaced my digitizer so I could have damaged the part that holds the SIM card and the SD. But is it possible the problem to be from the motherboard? If not then I will order new SIM/SD part from ebay and will replace it.

Of course it is but unlikely cause these parts aren't that sensitive. First of all make sure that it is really a hardware issue before you buy anything you don't need.

So I flashed the ICS RUU and the phone works well except for the SD card. So I guess its hardware related. Will buy the SIM/Sd holder but what I am thinking is if it is possible to be something from the motherboard because the SIM works well. Probably the SD slot is broken or the cable is damaged

[Q] I need help with a Samsung Galaxy Tab 2 10.1 GT-P5113

Well I was sent here by jd1639 from xda assist, so I will copy/paste what I said there, and what is my problem.
Hello community, I am new here so I don' t know where to put this.
Well I need some help, I am having problems with my old tab, A Samsung Galaxy Tab 2 10.1 GT-P5113, Flashed with custom ROM CM 10.1.3 for GT-P5110
Worked fine for a year and a Half, the issue that I am having now is that, it constantly restarts, after entering to the OS I can tweak change etc, but after a few secs it just turns of and reboots the system.
The other problem that I am having is that I tried everything that I could think of. I deleted some apps, which came back after the reboot. I booted to safemode, and deleted the last apps that I installed, still came back after the crash reboot.
I went to recovery mode (CWM) and did a Factory reset, delete cache and delete Dalvik Cache. Nothing when reboot everything was like last time.
wen't to and tried to reflash CM 10.1.3 (stable) following every procedure and nothing everything was back.
Last thing I tried is ODIN with stock ROM (which is hard to find for this tab.) but get write error after going to half. I am downloading a second stock ROM (android 4.1.1) to see how it goes.
Hope to find help here, I would be greatly thankful.
EDIT: Flashed now with the new stock ROM, ODIN says success, everything seems fine, but again I got received by the same splash and the same logon screen, and still crashes and reboots...
I hope you guys can help me.

bump.

Isifth said:
bump.
Click to expand...
Click to collapse
I wonder if your EMMC is not writing any more.
@Android-Andi, would you know?

jrc2 said:
I wonder if your EMMC is not writing any more.
@Android-Andi, would you know?
Click to expand...
Click to collapse
How do I check that?

Isifth said:
How do I check that?
Click to expand...
Click to collapse
I do not know. I was just saying that based on the symptoms.

jrc2 said:
I do not know. I was just saying that based on the symptoms.
Click to expand...
Click to collapse
I tryed to fsck but I get:
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p10
That is the /data
Now I check with mount and I have this:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk0p9 on /system type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
EDIT:
Now I tried this command "dmesg | grep mmc0" and got this back:
<6>[ 3.920837] mmc0 LDO enable
<7>[ 4.039184] mmc0 : moviNAND VHX 4.41 DISCARD feature is enabled
<6>[ 4.050109] mmc0: new high speed MMC card at address 0001
<6>[ 4.050476] mmcblk0: mmc0:0001 MAG2GA 14.6 GiB
<6>[ 4.050628] mmcblk0boot0: mmc0:0001 MAG2GA partition 1 2.00 MiB
<6>[ 4.050781] mmcblk0boot1: mmc0:0001 MAG2GA partition 2 2.00 MiB
<6>[ 29.987670] mmc0 LDO Disable
<6>[ 72.762786] mmc0 LDO enable
<6>[ 100.159973] mmc0 LDO Disable
<6>[ 116.042327] mmc0 LDO enable
<6>[ 129.800598] mmc0 LDO Disable
<6>[ 144.014770] mmc0 LDO enable
<6>[ 180.073974] mmc0 LDO Disable
<6>[ 195.574554] mmc0 LDO enable
<6>[ 220.159759] mmc0 LDO Disable
<6>[ 891.409851] mmc0 LDO enable
<6>[ 904.378692] mmc0 LDO Disable
<6>[ 925.569824] mmc0 LDO enable
<6>[ 985.589599] mmc0 LDO Disable
<6>[ 3028.195312] mmc0 LDO enable
<6>[ 3037.534912] mmc0 LDO Disable
I don't know if these can help.

Right now working in my linux desktop, and with my tab connected I noticed something, when the Tab is on (for the short 10 secs before crashing) it is recognize as GT P5110, normal cause that is the firmware version that I putted long ago CM 10.1.3.
Now if it is in recovery mode it is recognize (I think cause of hardware) as a GT P5113, that is the official hardware type.
Now, today, when working on something else in my linux desktop, but my tab still connected just off completely (just the charging icon) I noticed that is recognized as a GT I9100G. Is that normal?
BTW, I can adb shell it and see files and directories from there, I just cannot be SU.

Isifth said:
Right now working in my linux desktop, and with my tab connected I noticed something, when the Tab is on (for the short 10 secs before crashing) it is recognize as GT P5110, normal cause that is the firmware version that I putted long ago CM 10.1.3.
Now if it is in recovery mode it is recognize (I think cause of hardware) as a GT P5113, that is the official hardware type.
Now, today, when working on something else in my linux desktop, but my tab still connected just off completely (just the charging icon) I noticed that is recognized as a GT I9100G. Is that normal?
BTW, I can adb shell it and see files and directories from there, I just cannot be SU.
Click to expand...
Click to collapse
Interesting. The GT I9100G is the Samsung Galaxy S2. Did you maybe flash an S2 ROM???

jrc2 said:
Interesting. The GT I9100G is the Samsung Galaxy S2. Did you maybe flash an S2 ROM???
Click to expand...
Click to collapse
No, if my memories doesn't fail me, no.