Related
Hi,
a couple times a week my phone seems to freeze when I push the powerbutton. The hardware buttons light up, but the screen remains black. I always have to pull the battery, after that it works again.
I finally was near a pc when it happened and managed to make a dmesg log. This was taken while the phone wasn't responding. I just plugged it in and used adb to get a log. Here's the interesting part (at least I think it is):
Code:
<6>[ 5433.007232] bravo_ts_power: power 0
<7>[ 5433.007507] __capella_cm3602_power: Turn the capella_cm3602 power off
<6>[ 5433.008026] lcdc_suspend: suspending
<6>[ 5433.008331] [R] early_suspend: sync
<6>[ 5433.033782] active wake lock PowerManagerService
<6>[ 5433.033905] active wake lock SMD_DATA5, time left 21
<6>[ 5433.034149] active wake lock SMD_DS, time left 41
<6>[ 5433.034332] [R] early_suspend end
<3>[ 5438.615905] mmc1: Data CRC error
<3>[ 5438.616729] msmsdcc_data_err: opcode 0x00000019
<3>[ 5438.617156] msmsdcc_data_err: blksz 512, blocks 5
<3>[ 5438.618194] mmcblk0: error -84 transferring data, sector 1668966, nr 5, card status 0xf00
<3>[ 5438.620758] mmc1: Data timeout
<3>[ 5438.621612] end_request: I/O error, dev mmcblk0, sector 1668966
<3>[ 5438.622070] Buffer I/O error on device mmcblk0p1, logical block 1668965
<4>[ 5438.622833] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.623291] end_request: I/O error, dev mmcblk0, sector 1668967
<3>[ 5438.624053] Buffer I/O error on device mmcblk0p1, logical block 1668966
<4>[ 5438.624511] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.625305] end_request: I/O error, dev mmcblk0, sector 1668968
<3>[ 5438.625762] Buffer I/O error on device mmcblk0p1, logical block 1668967
<4>[ 5438.626525] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.626983] end_request: I/O error, dev mmcblk0, sector 1668969
<3>[ 5438.627746] Buffer I/O error on device mmcblk0p1, logical block 1668968
<4>[ 5438.628173] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.628967] end_request: I/O error, dev mmcblk0, sector 1668970
<3>[ 5438.629394] Buffer I/O error on device mmcblk0p1, logical block 1668969
<4>[ 5438.630187] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.042205] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.043090] mmc1: Data timeout
<3>[ 5443.043884] end_request: I/O error, dev mmcblk0, sector 1669055
<3>[ 5443.044311] Buffer I/O error on device mmcblk0p1, logical block 1669054
<4>[ 5443.045104] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.045562] end_request: I/O error, dev mmcblk0, sector 1669056
<3>[ 5443.046325] Buffer I/O error on device mmcblk0p1, logical block 1669055
<4>[ 5443.046752] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.047546] end_request: I/O error, dev mmcblk0, sector 1669057
<3>[ 5443.047973] Buffer I/O error on device mmcblk0p1, logical block 1669056
<4>[ 5443.048736] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.049194] end_request: I/O error, dev mmcblk0, sector 1669058
<3>[ 5443.049987] Buffer I/O error on device mmcblk0p1, logical block 1669057
<4>[ 5443.050415] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.051208] end_request: I/O error, dev mmcblk0, sector 1669059
<3>[ 5443.051635] end_request: I/O error, dev mmcblk0, sector 1669067
<3>[ 5443.052429] end_request: I/O error, dev mmcblk0, sector 1669075
<3>[ 5443.052856] end_request: I/O error, dev mmcblk0, sector 1669083
<3>[ 5443.053649] end_request: I/O error, dev mmcblk0, sector 1669091
<3>[ 5443.054077] end_request: I/O error, dev mmcblk0, sector 1669099
<3>[ 5443.054870] end_request: I/O error, dev mmcblk0, sector 1669107
<3>[ 5443.055664] end_request: I/O error, dev mmcblk0, sector 1669115
<3>[ 5443.056091] end_request: I/O error, dev mmcblk0, sector 1669123
<3>[ 5443.056884] end_request: I/O error, dev mmcblk0, sector 1669131
<3>[ 5443.057312] end_request: I/O error, dev mmcblk0, sector 1669139
<3>[ 5443.058105] end_request: I/O error, dev mmcblk0, sector 1669147
<3>[ 5443.058563] end_request: I/O error, dev mmcblk0, sector 1669155
<3>[ 5443.059326] end_request: I/O error, dev mmcblk0, sector 1669163
<3>[ 5443.059783] end_request: I/O error, dev mmcblk0, sector 1669171
<3>[ 5443.060546] end_request: I/O error, dev mmcblk0, sector 1669179
<3>[ 5443.066314] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.067199] mmc1: Data timeout
<3>[ 5443.067626] end_request: I/O error, dev mmcblk0, sector 2112723
<3>[ 5443.068420] Buffer I/O error on device mmcblk0p1, logical block 2112722
<4>[ 5443.068847] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.074676] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.075653] mmc1: Data timeout
<3>[ 5443.076110] end_request: I/O error, dev mmcblk0, sector 2
<3>[ 5443.081573] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.082427] mmc1: Data timeout
<3>[ 5443.082855] end_request: I/O error, dev mmcblk0, sector 833
<3>[ 5443.088745] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.089599] mmc1: Data timeout
<3>[ 5443.090026] end_request: I/O error, dev mmcblk0, sector 15594
<3>[ 5443.483581] mmc1: Data CRC error
<3>[ 5443.484374] msmsdcc_data_err: opcode 0x00000011
<3>[ 5443.484802] msmsdcc_data_err: blksz 512, blocks 1
<3>[ 5443.485748] mmcblk0: error -84 transferring data, sector 833, nr 1, card status 0xb00
<3>[ 5443.486389] end_request: I/O error, dev mmcblk0, sector 833
<3>[ 5443.487609] FAT: FAT read failed (blocknr 832)
<3>[ 5443.488616] mmc1: DMA channel flushed (0x80000004)
<3>[ 5443.489410] Flush data: 0000c003 3b18e000 00000000 00400040 00050004 00004003
<6>[ 5480.704193] batt: 95%, 4030 mV, -119 mA (-215 avg), 23.6 C, 1275 mAh
<6>[ 5530.876739] batt: 95%, 4030 mV, -69 mA (-82 avg), 23.6 C, 1273 mAh
<6>[ 5563.668518] gpio_keys_scan_keys: key 1-74, 0 (94) changed to 1
<6>[ 5563.673858] request_suspend_state: wakeup (3->0) at 5555550724239 (2010-12-28 12:24:48.362411743 UTC)
<6>[ 5563.674713] [R] late_resume start
<6>[ 5563.675201] lcdc_resume: resuming
<6>[ 5563.675628] samsung_oled_panel_init: +()
<6>[ 5563.676788] samsung_oled_panel_init: -()
<6>[ 5563.677368] msmfb: ready, waiting for full update
<7>[ 5563.678131] __capella_cm3602_power: Turn the capella_cm3602 power on
<6>[ 5563.678955] bravo_ts_power: power 1
<6>[ 5563.680053] lightsensor_ioctl set value = 1
<6>[ 5563.680816] lightsensor_enable
After that I reformatted my SDcard, wiped everything and did a fresh install of CM instead of Oxygen RC4 which I was using before.
Today I was downloading a few apps from the market, when suddenly the downloads disappeared from the notification bar. I used quick system info to look at the logs (again only a small part, i still have the rest if the full log contains more useful information):
Code:
<3> [23578.803039] : mmc1: Data CRC error
<3> [23578.803466] : msmsdcc_data_err: opcode 0x00000019
<3> [23578.804229] : msmsdcc_data_err: blksz 512, blocks 49
<3> [23578.804657] : mmc1: DMA channel flushed (0x80000004)
<3> [23578.805084] : Flush data: 0000c003 3b252030 00000000 00400040 00170015 00008003
<3> [23578.810241] : mmcblk0: error -84 transferring data, sector 2556870, nr 49, card status 0x900
<3> [23578.811096] : mmc1: Data timeout
<3> [23578.811889] : end_request: I/O error, dev mmcblk0, sector 2556870
<3> [23578.812652] : end_request: I/O error, dev mmcblk0, sector 2556878
<3> [23578.813079] : end_request: I/O error, dev mmcblk0, sector 2556886
<3> [23578.813812] : end_request: I/O error, dev mmcblk0, sector 2556894
<3> [23578.814209] : end_request: I/O error, dev mmcblk0, sector 2556902
<3> [23578.814972] : end_request: I/O error, dev mmcblk0, sector 2556910
<3> [23578.815368] : end_request: I/O error, dev mmcblk0, sector 2556918
<3> [23578.821869] : mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3> [23578.823883] : mmc1: Data timeout
<3> [23578.824524] : end_request: I/O error, dev mmcblk0, sector 2556934
<3> [23578.830535] : mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3> [23578.832946] : mmc1: Data timeout
<3> [23578.833801] : end_request: I/O error, dev mmcblk0, sector 2049
<3> [23578.834564] : Buffer I/O error on device mmcblk0p1, logical block 1
<4> [23578.834991] : lost page write due to I/O error on mmcblk0p1
<3> [23578.844360] : mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3> [23578.844635] : mmc1: Data timeout
<3> [23578.844757] : end_request: I/O error, dev mmcblk0, sector 4515
<3> [23578.844879] : Buffer I/O error on device mmcblk0p1, logical block 2467
<4> [23578.845092] : lost page write due to I/O error on mmcblk0p1
<3> [23579.089599] : mmc1: Data CRC error
<3> [23579.090057] : msmsdcc_data_err: opcode 0x00000011
<3> [23579.090454] : msmsdcc_data_err: blksz 512, blocks 1
<3> [23579.091919] : mmcblk0: error -84 transferring data, sector 4515, nr 1, card status 0xb00
<3> [23579.092315] : end_request: I/O error, dev mmcblk0, sector 4515
<3> [23579.093231] : FAT: FAT read failed (blocknr 2467)
<3> [23579.098968] : mmcblk0: error -110 sending read/write command, response 0xb00, card status 0x400b00
<3> [23579.105072] : end_request: I/O error, dev mmcblk0, sector 63598
<3> [23579.105529] : Buffer I/O error on device mmcblk0p1, logical block 61550
<4> [23579.105926] : lost page write due to I/O error on mmcblk0p1
<3> [23579.582916] : FAT: Filesystem error (dev mmcblk0p1)
<3> [23579.583038] : fat_get_cluster: invalid cluster chain (i_pos 984821)
<3> [23579.583465] : FAT: Filesystem has been set read-only
<6> [23585.658355] : wake lock SMD_DATA5, expired
<7> [23585.663910] : save exit: isCheckpointed 1
<6> [23585.666900] : suspend: enter suspend
<6> [23585.667297] : PM: Syncing filesystems ... done.
<4> [23585.670532] : Freezing user space processes ... (elapsed 0.02 seconds) done.
<4> [23585.699371] : Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
<6> [23585.749786] : PM: suspend of devices complete after 28.841 msecs
<6> [23585.750854] : power_suspend_late return 0
<6> [23585.751281] : PM: late suspend of devices complete after 1.036 msecs
<6> [23585.751281] : clocks on: uart_clk
<6> [23585.751281] : [R] suspend end
<6> [23585.751281] : [R] resume start
<6> [23585.751678] : PM: early resume of devices complete after 0.396 msecs
<6> [23585.757965] : wakeup wake lock: SMD_RPCCALL
<6> [23585.764862] : PM: resume of devices complete after 12.439 msecs
<4> [23585.766082] : Restarting tasks ... done.
<6> [23585.783905] : suspend: exit suspend, ret = 0 (2010-12-29 13:37:55.798841765 UTC)
<6> [23585.784912] : active wake lock ds2784-battery
<6> [23585.785339] : suspend: abort suspend
Could the freeze be the result of having apps installed on the SD when the error occurred?
The strange thing is that I got a new SD card for Christmas, and I have had (seemingly) the same freezes before. I never managed to get a log before, since i was never near a computer.
I already tried reformatting the card a few times, but that didn't seem to help.
Does anybody know a solution? Is it SD card related, or can it be caused by something else entirely?
Thanks
Does anyone have know if this is a problem with my SD card?
I find it odd that I also had the lockscreen freezing on my other SD card, I don't have it with me at the moment, so I can't compare the logs.
Is it also possible that the internal memory is corrupt? (Which would be a lot worse i guess )
Are you overclocking? If your min cpu speed is lower that 245mhz sometimes you get issues with the device waking.
Sent from my HTC Desire using Tapatalk
No, I'm not over/underclocking.
The second log was taken after several failed downloads of updates from the market. It showed the exact same error as the one were the lockscreen froze, but the phone functioned normally. Except for the downloads that failed of course.
I think the freezing is the result of an app or essential file on the SD card that can't be reached. Is that possible?
I have the same problem with the screen not waking. Did you find a solution?
Exact same problem..!!
Hey,
I have the exact same problem! I'm running a mildwild rom, with cm7r2 hboot, and 4ext recovery.. everything should be OK, but it's not..
I also think that it's the SD card that's dying.. gonna buy a new one tomorrow, and see if the problem goes away.. I'll post here, as soon as I find something out..!
- H
Is it a class 10 card? Also, maybe the I/O schedule may cause it.
What settings do u have set for it?
SaySayonara said:
Is it a class 10 card? Also, maybe the I/O schedule may cause it.
What settings do u have set for it?
Click to expand...
Click to collapse
Hey,
No I don't think it is.. but I don't think that should matter much, since I just got this phone, and had an old SD-card lying around.. so I rooted it, partitioned it, etc., but these malfunctions appeared almost immediately.. and I'm pretty sure the SD was OK when I put it in.. isn't class 10 usually only recommended for demanding a2sd setup-ups, that run over long periods of time..? I find it extremly suspicious that an SD card, even below class 6, would almost instantaneously die upon being put into use.. ?
However, now I've played around with it some more, and I'm almost certain now that it's the SD card that has gone broken.. because if I clear the data and cache of both google play and google framework services apks, and then boot into recovery and choose "tools" --> "check filesystem" --> sdcard --> repair sdcard (it doesn't work EVERY time, which also makes me suspect the Sd card...!!!!) , and then reboot, the SD card will work -- for a while... Like, I'll install 5-7 apps from google play, and then the same s**t all over again..
Gonna try it out with the same setup, but a brand new class 10 SD tomorrow, and report back..!
- H
I bought Sandisk Extreme 32GB
What partitioning tool did u use? I've seen many ppl saying that 4ext is the best. To be Frank I never had any issues with it.
SaySayonara said:
I bought Sandisk Extreme 32GB
What partitioning tool did u use? I've seen many ppl saying that 4ext is the best. To be Frank I never had any issues with it.
Click to expand...
Click to collapse
Yeah, I also used 4ext.. worked like a charm!
HAhaha, LOL - I was just looking at what card I'm gonna get tomorrow, and it looks like it's gonna be the same as yours..!!
- H
You're in for a treat my friend
I was very surprised by the difference.
All right!
The mystery is solved! Just tested it out with a new SanDisk class 10 16GB SD card.. everything works just fine.. partitioned it in 4ext, installed MildWild AOSP GB rom, installed a s**tload of apps, and everything works just fine.. the a2sd script is working as it should, both the rom install and apps install went smoothly. Besides changing the SD card, I changed nothing; same HBOOT, same 4ext, same everything.. So I guess it was the SD card that was fu***n things up..!
Cheers everybody!
- H
Hey guys. This site has been a huge help to me lately, but I just can't figure out this problem...
To start from the beginning, my R800X is second hand but was never used or activated, so its in perfect condition. It came with 2.3.2 installed on it, and I have not activated it on any service yet (I plan on moving to page plus at some point). I rooted it originally with SuperOneClick and added a 32Gb Sandisk Ultra Mobile UHS-1 Class 10 microSD (which has high read speeds and is made for smartphones and tablets) and Link2SD. Not long after that I decided to have Alejandrissimo unlock my bootloader, which went very smoothly.
The next thing I did was install CWM, and I settled on GBTweaked07 as my first ROM to try out. It seemed nice but was freezing and lagging a lot with Doomkernel, so I tried other CM7 kernels and had the same issues, some times on the first boot. I had thought at one point that it was my SD card so I removed it, formatted it with EasyUS partition master (FAT32, with a second small partition for Link2SD) and the phone just said it was damaged after that... so I formatted it AGAIN in Windows and it worked fine... or so I thought.
I was still having some random lag\freezing and other problems, so I moved on to ICS and installed FXP-142 (with the included kernel) which seemed to work the best, but out of nowhere started giving me the same issues. First I get lag and freezing, then I often times get errors loading apps (not responding or force close errors) and some app icons revery to the android logo and will not load. Rebooting and clearing cache in CWM some times fixes it, but it comes back again later... its really irritating, to say the least. Some times it causes the phone to reboot itself (not completely, CM9.1 just reloads without going back to the FXP screen), other times it makes the phone completely unresponsive with the back-light seemingly stuck off, and I have to pop the battery out to get things working again. Other times, I can play SuperGSNES for hours with no problems at all.
I have used OSMonitor to dig up some error messages, and I've found that these seem to pop up when the phone is going through one of its glitching spells:
Code:
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180500, nr 2, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180500
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180501, nr 1, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180501
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [WARNING] mmcblk0: retrying using single block read
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180494, nr 8, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180494
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180495, nr 7, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180495
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180496, nr 6, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180496
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180497, nr 5, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180497
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180498, nr 4, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180498
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180499, nr 3, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180499
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180500, nr 2, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180500
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180501, nr 1, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180501
10/18/2012 13:58:50 [WARNING] mmc1: Starting deferred resume
10/18/2012 13:58:50 [WARNING] mmc1: Deferred resume completed
I filtered the log to show only mmc errors (related to the memory card from what I can gather) because I get other messages related to "msm_snddev_poweramp" constantly that clutter up the log.
Now, I thought the card was just bad, but I've tested it extensively on my computer and it has no bad clusters or defects of any kind, according to chkdsk or Minitool's diagnostics. I can copy to and read from it over and over with no problems. I've tried formatting it many times, in different programs (Secure Digital SDFormatter, Windows 7, EasyUS PM, Minitool Partition Wizard...) using FAT32 (the phone couldn't read it as EXT4 and I use Windows so that isn't ideal anyway), with and without the second Link2SD partition, and even if it works for a while, the phone will eventually start screwing up and spewing those mmc errors into dmesg.
I never had any of these problems with the stock ROM\kernel and the included 8gb class 2 microSD, and the problems don't seem to occur on the current setup with my spare G.Skill 4Gb Class 4 card.
Is it possible that the phone itself just plain does not work with certain memory cards, specifically UHS-1 class cards? Is it possible that a different Kernel or ROM may fix the problem?
I'm at a loss, and I'm hoping someone can help interpret those mmc messages or point me in a direction to narrow down the cause of this madness.
Thank you!
Well, I've been playing around with a different kernel\ROM setup using my old 4Gb class 4 card, and I'm not having any sdcard errors at all. I'll keep messing with it, but it seems to be stable this way. If it works like this for a while I'll try putting the other card back in to see if it brings on the errors. If so, I'll just have to give up trying to use this card on this phone.
Ice Cream Pureness + LuPuS is fantastic... but I don't seem to have any signal and the baseband is "unknown". It doesn't really matter right now because I have no service, but this is a bit worrying...
ozzuneoj said:
Hey guys. This site has been a huge help to me lately, but I just can't figure out this problem...
To start from the beginning, my R800X is second hand but was never used or activated, so its in perfect condition. It came with 2.3.2 installed on it, and I have not activated it on any service yet (I plan on moving to page plus at some point). I rooted it originally with SuperOneClick and added a 32Gb Sandisk Ultra Mobile UHS-1 Class 10 microSD (which has high read speeds and is made for smartphones and tablets) and Link2SD. Not long after that I decided to have Alejandrissimo unlock my bootloader, which went very smoothly.
The next thing I did was install CWM, and I settled on GBTweaked07 as my first ROM to try out. It seemed nice but was freezing and lagging a lot with Doomkernel, so I tried other CM7 kernels and had the same issues, some times on the first boot. I had thought at one point that it was my SD card so I removed it, formatted it with EasyUS partition master (FAT32, with a second small partition for Link2SD) and the phone just said it was damaged after that... so I formatted it AGAIN in Windows and it worked fine... or so I thought.
I was still having some random lag\freezing and other problems, so I moved on to ICS and installed FXP-142 (with the included kernel) which seemed to work the best, but out of nowhere started giving me the same issues. First I get lag and freezing, then I often times get errors loading apps (not responding or force close errors) and some app icons revery to the android logo and will not load. Rebooting and clearing cache in CWM some times fixes it, but it comes back again later... its really irritating, to say the least. Some times it causes the phone to reboot itself (not completely, CM9.1 just reloads without going back to the FXP screen), other times it makes the phone completely unresponsive with the back-light seemingly stuck off, and I have to pop the battery out to get things working again. Other times, I can play SuperGSNES for hours with no problems at all.
I have used OSMonitor to dig up some error messages, and I've found that these seem to pop up when the phone is going through one of its glitching spells:
Code:
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180500, nr 2, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180500
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180501, nr 1, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180501
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [WARNING] mmcblk0: retrying using single block read
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180494, nr 8, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180494
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180495, nr 7, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180495
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180496, nr 6, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180496
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180497, nr 5, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180497
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180498, nr 4, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180498
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180499, nr 3, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180499
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180500, nr 2, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180500
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180501, nr 1, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180501
10/18/2012 13:58:50 [WARNING] mmc1: Starting deferred resume
10/18/2012 13:58:50 [WARNING] mmc1: Deferred resume completed
I filtered the log to show only mmc errors (related to the memory card from what I can gather) because I get other messages related to "msm_snddev_poweramp" constantly that clutter up the log.
Now, I thought the card was just bad, but I've tested it extensively on my computer and it has no bad clusters or defects of any kind, according to chkdsk or Minitool's diagnostics. I can copy to and read from it over and over with no problems. I've tried formatting it many times, in different programs (Secure Digital SDFormatter, Windows 7, EasyUS PM, Minitool Partition Wizard...) using FAT32 (the phone couldn't read it as EXT4 and I use Windows so that isn't ideal anyway), with and without the second Link2SD partition, and even if it works for a while, the phone will eventually start screwing up and spewing those mmc errors into dmesg.
I never had any of these problems with the stock ROM\kernel and the included 8gb class 2 microSD, and the problems don't seem to occur on the current setup with my spare G.Skill 4Gb Class 4 card.
Is it possible that the phone itself just plain does not work with certain memory cards, specifically UHS-1 class cards? Is it possible that a different Kernel or ROM may fix the problem?
I'm at a loss, and I'm hoping someone can help interpret those mmc messages or point me in a direction to narrow down the cause of this madness.
Thank you!
Click to expand...
Click to collapse
We had confirmed reports class 10 doesnt work on the xperia play. No changing the kernel doesnt make the difference. You need to know the difference between the read and write speeds of the sdcard because class 10 serves a different purpose (digital cameras/video recorder). Otherwise you've been gyped. You need class 6 and below sd cards.
chery2k said:
We had confirmed reports class 10 doesnt work on the xperia play. No changing the kernel doesnt make the difference. You need to know the difference between the read and write speeds of the sdcard because class 10 serves a different purpose (digital cameras/video recorder). Otherwise you've been gyped. You need class 6 and below sd cards.
Click to expand...
Click to collapse
UHS-1 is different than just standard Class 10. It is a new rating for high speed writing AND reading. Speed really should not be an issue with this card. I just ran CrystalDiskMark on the 32Gb Sandisk Ultra and the 4Gb GSkill Class 4 card and these are the results:
Sandisk Ultra 32Gb Class 10 UHS-1
-----------------------------------------------------------------------
CrystalDiskMark 3.0.1 (C) 2007-2010 hiyohiyo
Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]
Sequential Read : 20.047 MB/s
Sequential Write : 13.083 MB/s
Random Read 512KB : 20.483 MB/s
Random Write 512KB : 3.992 MB/s
Random Read 4KB (QD=1) : 3.176 MB/s [ 775.4 IOPS]
Random Write 4KB (QD=1) : 1.392 MB/s [ 339.8 IOPS]
Random Read 4KB (QD=32) : 3.463 MB/s [ 845.4 IOPS]
Random Write 4KB (QD=32) : 1.437 MB/s [ 350.8 IOPS]
Test : 100 MB [K: 1.3% (0.4/28.4 GB)] (x5)
Date : 2012/10/20 13:14:41
OS : Windows 7 SP1 [6.1 Build 7601] (x64)
G.SKill 4Gb Class 4
-----------------------------------------------------------------------
CrystalDiskMark 3.0.1 (C) 2007-2010 hiyohiyo
Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]
Sequential Read : 21.166 MB/s
Sequential Write : 7.057 MB/s
Random Read 512KB : 20.377 MB/s
Random Write 512KB : 0.901 MB/s
Random Read 4KB (QD=1) : 3.770 MB/s [ 920.4 IOPS]
Random Write 4KB (QD=1) : 0.231 MB/s [ 56.3 IOPS]
Random Read 4KB (QD=32) : 3.381 MB/s [ 825.4 IOPS]
Random Write 4KB (QD=32) : 0.220 MB/s [ 53.7 IOPS]
Test : 100 MB [K: 8.5% (321.8/3778.0 MB)] (x5)
Date : 2012/10/20 13:03:34
OS : Windows 7 SP1 [6.1 Build 7601] (x64)
Speed wise the cards are very similar, except that the Class 10 has significantly higher sequential AND random write speeds (random writes are very important for running apps from the card). The Class 4 is a bit faster with the 4kb reads (in MB\s and IOPS) with a queue depth of 1, but I would hope that a 25% difference in read speed in one situation wouldn't completely disable the Android OS and cause data corruption. Its still faster than the random read speed you'll find on many cards.
So, if it isn't a lack of random read\write speed, what is it? The Class 10 designation alone doesn't somehow make a card incompatible... its just a symbol on the package.
Is there any electrical difference between a faster card and a slower one that would make the faster one incompatible with this phone? Maybe its TOO fast, even though the UHS-1 cards are advertised as being made for tablets and smart phones?
Well, after seeing that the LuPuS+Ice Cream Pureness combo was stable with my 4Gb card, I put the 32Gb in and after a while I did get the mmc errors again while copying files. I really feel that I've tried everything at this point, aside from formatting the card with an EXT file system and making it unreadable on my computer.
I still don't understand why a card would be incompatible like this if the read and write speeds are good enough and the card has no physical problems.
Okay, I've made a discovery on another forum:
http://maemo.org/community/maemo-users/n900_microsd_card_i-o_errors_and_corruption/
This is exactly the problem I'm having, and they fixed it on an n900 by editing the DTO (data time-out I think) settings in one of the driver files for the sdcard controller. Basically, some drivers try to tell the memory controller to change this setting dynamically to determine the "optimal" setting for each SD card... where as, any card will apparently work with a standard setting anyway (maybe there is some performance or power benefit to adjusting this). The problem is, changing this setting dynamically is apparently problematic with many high speed cards, resulting in a timing problem and data corruption.
I guess its a fairly common problem with various handheld devices...
http://talk.maemo.org/archive/index.php/t-72789.html
My question is, does anyone have the means and the knowledge to see if the Xperia has a similar setting like this in its drivers? I only have a basic knowledge of programming and zero experience with linux kernel programming... so, if anyone finds a possible solution and attempts to make a fix for it, I'd be willing to test it. In the mean time, if I can find some kernel source files (doomkernel's CDMA source link is broken) I'll try digging around a bit myself. I have no idea how to compile though, even if I do find a similar setting.
Also, it'd be really nice to be able to post this topic in the development forum, but I'm still working my way up to 10 posts...
I can't believe it... I actually found the exact file mentioned in the first thread I linked above:
https://github.com/DooMLoRD/Xperia-...b/master/kernel/drivers/mmc/host/omap_hsmmc.c
The Xperia Play apparently uses the same driver (most likely a different version)... And it has the same exact section above that needs to be edited to remove the problematic DTO checks:
Original:
Code:
static void set_data_timeout(struct omap_hsmmc_host *host,
unsigned int timeout_ns,
unsigned int timeout_clks)
{
unsigned int timeout, cycle_ns;
uint32_t reg, clkd, dto = 0;
reg = OMAP_HSMMC_READ(host->base, SYSCTL);
clkd = (reg & CLKD_MASK) >> CLKD_SHIFT;
if (clkd == 0)
clkd = 1;
cycle_ns = 1000000000 / (clk_get_rate(host->fclk) / clkd);
timeout = timeout_ns / cycle_ns;
timeout += timeout_clks;
if (timeout) {
while ((timeout & 0x80000000) == 0) {
dto += 1;
timeout <<= 1;
}
dto = 31 - dto;
timeout <<= 1;
if (timeout && dto)
dto += 1;
if (dto >= 13)
dto -= 13;
else
dto = 0;
if (dto > 14)
dto = 14;
}
reg &= ~DTO_MASK;
reg |= dto << DTO_SHIFT;
OMAP_HSMMC_WRITE(host->base, SYSCTL, reg);
}
More info here:
http://talk.maemo.org/showthread.php?p=1000707#post1000707
Is it possible to make a module to patch an existing kernel for the xperia play? Specifically the r800x, since I'm willing to make mine a guinea pig. It seems like a very quick edit job... I've done it myself, I just don't have the means or knowledge to compile it into a useful file.
If anyone can do this I'd be very appreciative!
I just wanted to point out that Ive never experienced any lag or problems with my samsung class10 sd card, im using one of these in my r800x and my r800a ... not a single problem ... ever
http://www.samsung.com/ie/consumer/...ards/micro-sd/MB-MSBGA/EU?subsubtype=micro-sd
216Monster said:
I just wanted to point out that Ive never experienced any lag or problems with my samsung class10 sd card, im using one of these in my r800x and my r800a ... not a single problem ... ever
http://www.samsung.com/ie/consumer/...ards/micro-sd/MB-MSBGA/EU?subsubtype=micro-sd
Click to expand...
Click to collapse
Some people have suggested that the problem could arise from problematic metadata on a SD card, since this omap driver is actually trying to query the card to figure out what would be the best setting for it.
You're correct, it doesn't effect all class 10 cards, but it seems to be much more common with class 10 cards vs slower ones... for whatever reason.
Hi. I have Nexus 7 2013 WiFi 32Gb. FLO 04.02 bootloader. Stock 4.4.2 android with root and teamwin.
Recently, I start download file and after that my nexus 7 rebooted. And it stuck on Google boot screen. I try to run teamwin, but it also stuck on Teamwin logo.
In fastboot mode i get:
Code:
> sudo fastboot -u format cache
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 89.945s
> sudo fastboot -w
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.015s
> sudo fastboot flash bootloader bootloader-flo-flo-04.02.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.068s
e2fsck:
Code:
e2fsck /dev/block/mmcblk0
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0
Filesystem mounted or opened exclusively by another program?
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p30
Filesystem mounted or opened exclusively by another program?
mount:
Code:
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
dmesg: pastebin. com/j4hnHkwg
PS. Can't insert links, and can't insert dmesg here, message are too long... =(
Some other logs:
Code:
<4>[ 1013.807952] ------------[ cut here ]------------
<4>[ 1013.807952] WARNING: at drivers/mmc/host/msm_sdcc.c:3538 msmsdcc_disable+0x84/0x10c()
<4>[ 1013.807952] mmc0: msmsdcc_disable: failed with error -22
<4>[ 1013.807983] [<c010cbc8>] (unwind_backtrace+0x0/0x11c) from [<c01730e8>] (warn_slowpath_common+0x48/0x60)
<4>[ 1013.807983] [<c01730e8>] (warn_slowpath_common+0x48/0x60) from [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 1013.807983] [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0659b18>] (msmsdcc_disable+0x84/0x10c)
<4>[ 1013.808013] [<c0659b18>] (msmsdcc_disable+0x84/0x10c) from [<c0646130>] (mmc_release_host+0x4c/0xb0)
<4>[ 1013.808013] [<c0646130>] (mmc_release_host+0x4c/0xb0) from [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0)
<4>[ 1013.808044] [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0) from [<c0657648>] (mmc_queue_thread+0xd4/0x19c)
<4>[ 1013.808044] [<c0657648>] (mmc_queue_thread+0xd4/0x19c) from [<c018f804>] (kthread+0x84/0x90)
<4>[ 1013.808044] [<c018f804>] (kthread+0x84/0x90) from [<c0107228>] (kernel_thread_exit+0x0/0x8)
<4>[ 1013.808074] ---[ end trace c0d52a61d7a24c7c ]---
<6>[ 1013.808074] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1013.808074] mmc0: RPM: runtime_status=0, usage_count=0, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<4>[ 1013.901123] ------------[ cut here ]------------
<4>[ 1013.901245] WARNING: at drivers/mmc/host/msm_sdcc.c:3510 msmsdcc_enable+0x108/0x144()
<4>[ 1013.901306] mmc0: msmsdcc_enable: failed with error -22
<4>[ 1013.901397] [<c010cbc8>] (unwind_backtrace+0x0/0x11c) from [<c01730e8>] (warn_slowpath_common+0x48/0x60)
<4>[ 1013.901519] [<c01730e8>] (warn_slowpath_common+0x48/0x60) from [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 1013.901580] [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c) from [<c065db64>] (msmsdcc_enable+0x108/0x144)
<4>[ 1013.901702] [<c065db64>] (msmsdcc_enable+0x108/0x144) from [<c0646018>] (__mmc_claim_host+0x170/0x180)
<4>[ 1013.901824] [<c0646018>] (__mmc_claim_host+0x170/0x180) from [<c0656d54>] (mmc_blk_issue_rq+0x34/0x4c0)
<4>[ 1013.901916] [<c0656d54>] (mmc_blk_issue_rq+0x34/0x4c0) from [<c0657648>] (mmc_queue_thread+0xd4/0x19c)
<4>[ 1013.902038] [<c0657648>] (mmc_queue_thread+0xd4/0x19c) from [<c018f804>] (kthread+0x84/0x90)
<4>[ 1013.902130] [<c018f804>] (kthread+0x84/0x90) from [<c0107228>] (kernel_thread_exit+0x0/0x8)
<4>[ 1013.902221] ---[ end trace c0d52a61d7a24c7d ]---
<6>[ 1013.902343] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1013.902404] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<6>[ 1013.903350] sps:BAM 0x12402000 enabled: ver:0x5, number of pipes:6
<3>[ 1013.908935] mmcblk0: error -110 sending status command, retrying
<3>[ 1013.914428] mmcblk0: error -110 sending status command, retrying
<3>[ 1013.919891] mmcblk0: error -110 sending status command, aborting
<3>[ 1013.919982] end_request: I/O error, dev mmcblk0, sector 4718594
<3>[ 1013.920104] EXT4-fs (mmcblk0p30): unable to read superblock
<4>[ 1013.920104] ------------[ cut here ]------------
<4>[ 1013.920135] WARNING: at drivers/mmc/host/msm_sdcc.c:3538 msmsdcc_disable+0x84/0x10c()
<4>[ 1013.920135] mmc0: msmsdcc_disable: failed with error -22
<4>[ 1013.920135] [<c010cbc8>] (unwind_backtrace+0x0/0x11c) from [<c01730e8>] (warn_slowpath_common+0x48/0x60)
<4>[ 1013.920166] [<c01730e8>] (warn_slowpath_common+0x48/0x60) from [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 1013.920166] [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0659b18>] (msmsdcc_disable+0x84/0x10c)
<4>[ 1013.920166] [<c0659b18>] (msmsdcc_disable+0x84/0x10c) from [<c0646130>] (mmc_release_host+0x4c/0xb0)
<4>[ 1013.920196] [<c0646130>] (mmc_release_host+0x4c/0xb0) from [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0)
<4>[ 1013.920196] [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0) from [<c0657648>] (mmc_queue_thread+0xd4/0x19c)
<4>[ 1013.920227] [<c0657648>] (mmc_queue_thread+0xd4/0x19c) from [<c018f804>] (kthread+0x84/0x90)
<4>[ 1013.920227] [<c018f804>] (kthread+0x84/0x90) from [<c0107228>] (kernel_thread_exit+0x0/0x8)
<4>[ 1013.920227] ---[ end trace c0d52a61d7a24c7e ]---
<6>[ 1013.920227] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1013.920257] mmc0: RPM: runtime_status=0, usage_count=0, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<3>[ 703.888671] EXT4-fs (mmcblk0p30): unable to read superblock
<3>[ 7.323852] mmcblk0: error -110 sending stop command, original cmd response 0x940, card status 0x2400e40
umount: can't umount /dev/block/mmcblk0: Invalid argument
mmc0: msmsdcc_enable: failed with error -22
<3>[ 757.383453] end_request: I/O error, dev mmcblk0, sector 4718592
<6>[ 1364.750000] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1364.750091] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<6>[ 1364.751068] sps:BAM 0x12402000 enabled: ver:0x5, number of pipes:6
<3>[ 1364.756591] mmcblk0: error -110 sending status command, retrying
<3>[ 1364.762145] mmcblk0: error -110 sending status command, retrying
<3>[ 1364.767608] mmcblk0: error -110 sending status command, aborting
<3>[ 1364.767700] end_request: I/O error, dev mmcblk0, sector 4718592
<3>[ 1364.767791] end_request: I/O error, dev mmcblk0, sector 4718593
<3>[ 1364.767852] end_request: I/O error, dev mmcblk0, sector 4718594
<3>[ 1364.767974] end_request: I/O error, dev mmcblk0, sector 4718595
<3>[ 1364.768035] end_request: I/O error, dev mmcblk0, sector 4718596
<3>[ 1364.768127] end_request: I/O error, dev mmcblk0, sector 4718597
<3>[ 1364.768218] end_request: I/O error, dev mmcblk0, sector 4718598
<3>[ 1364.768310] end_request: I/O error, dev mmcblk0, sector 4718599
I have exactly the same problem. I wasn't doing anything - I just lifted the cover the other morning to find it sitting at the Google logo. Can it really be hosed? Are we SOL for warranty repair?
eecummings said:
I have exactly the same problem. I wasn't doing anything - I just lifted the cover the other morning to find it sitting at the Google logo. Can it really be hosed? Are we SOL for warranty repair?
Click to expand...
Click to collapse
Have you guys test the nexus root tool kit?
it's a wonderful piece of software..
it does helped alot my nexus 4 when it's half bricked...
Try flashing system images and see what happens?
Sent from my XT1032 using XDA Premium 4 mobile app
Hi, I've the exact same problem too.
Did you manage to solve it or did you have to send it back for repair?
Thanks,
Alessandro
I believe this is the same problem I have: Not being able to format my corrupted cache partition.
Since my tablet was not unlocked or rooted I can't seem to flash a ROM either, even stock.
1c3_5n0w said:
Try flashing system images and see what happens?
Click to expand...
Click to collapse
I can't flash or erase or format any partition. I get the same error after some period of timeout.
Hello.
So - I bought this phone about ~8/9 months ago (in april 2014). I installed Cyanogenmod 11 by Maclaw twice, but there were problems with stability, so in August I decided to install AOSP by salvo (slv96).
Since then, everything was okay, until the middle of January (this year), when the phone... just restarted. It did not surprise me, because it restarted couple of times before. Unfortunately, it happend again - twice - so I started looking for possible causes. I noticed that the phone can boot normally, I can even use it for some time, but when I want to change something on it, it restarts, probably getting a kernel panic.
I tried to delete all data, or "triple wipe", but after that phone still had untouched ROM, just like it was before. Nothing was removed. So I downloaded Samsung Kies, because I tried to install an "original ROM", but Kies only shows the message "Connecting" and nothing more happens.
Next time I tried the ADB, I reset the flash counter by command:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732
then I checked "what happens when I write the command dmesg | grep mmc*", which results in something like this:
Code:
[email protected]:/ # dmesg | grep mmc*
dmesg | grep mmc*
<7>[ 0.000000] Normal zone: 1248 pages used for memmap
<7>[ 0.000000] HighMem zone: 286 pages used for memmap
<5>[ 0.000000] Kernel command line: cachepolicy=writealloc mpcore_wdt.mpcore_margin=359 root=/dev/ram0 rw rootwait crash_reboot=yes crash_dump=no init=initconsole='null' [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] vmalloc=264M jig_smd=0 lpm_boot=0 checksum_pass=1 checksum_done=1 sec_debug.enable=0 sec_debug.enable_user=0 androidboot.serialno=473700e240071108 board_id=12 startup_graphics=1 logo. lcdtype=8 sbl_copy=1
<6>[ 0.000000] Console: colour dummy device 80x30
<6>[ 0.322540] print_constraints: dummy:
<6>[ 0.343658] print_constraints: db8500-sva-mmdsp:
<7>[ 0.343688] regulator regulator.9: regulator-db8500-sva-mmdsp-probed
<6>[ 0.343872] print_constraints: db8500-sva-mmdsp-ret:
<7>[ 0.343902] regulator regulator.10: regulator-db8500-sva-mmdsp-ret-probed
<6>[ 0.344329] print_constraints: db8500-sia-mmdsp:
<7>[ 0.344360] regulator regulator.12: regulator-db8500-sia-mmdsp-probed
<6>[ 0.344543] print_constraints: db8500-sia-mmdsp-ret:
<7>[ 0.344604] regulator regulator.13: regulator-db8500-sia-mmdsp-ret-probed
<6>[ 0.772735] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
<6>[ 1.227233] bt404_ts_device 3-0020: send reset command
<6>[ 1.255004] mmci-pl18x sdi2: mmc0: PL180 manf 80 rev4 at 0x80005000 irq 73,-1 (pio)
<6>[ 1.255096] mmci-pl18x sdi2: DMA channels RX dma0chan16, TX dma0chan17
<4>[ 1.298492] mmci-pl18x sdi0: Provided ocr_mask/setpower will not be used (using regulator instead)
<3>[ 1.298645] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<6>[ 1.298950] mmci-pl18x sdi0: mmc1: PL180 manf 80 rev4 at 0x80126000 irq 92,-1 (pio)
<3>[ 1.298980] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<6>[ 1.299072] mmci-pl18x sdi0: DMA channels RX dma0chan18, TX dma0chan19
<3>[ 1.322021] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 8
<3>[ 1.322357] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.322662] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.322967] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.323303] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.323608] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.323913] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.324249] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.324554] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<6>[ 1.368377] mmci-pl18x sdi1: mmc2: PL180 manf 80 rev4 at 0x80118000 irq 82,-1 (pio)
<6>[ 1.368438] mmci-pl18x sdi1: DMA channels RX dma0chan20, TX dma0chan21
<6>[ 1.471282] mmc0: new high speed DDR MMC card at address 0001
<6>[ 1.471771] mmcblk0: mmc0:0001 SEM04G 3.68 GiB
<6>[ 1.471954] mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB
<6>[ 1.472137] mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB
<6>[ 1.477600] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17
<6>[ 1.484130] mmcblk0boot1: unknown partition table
<6>[ 1.487213] mmcblk0boot0: unknown partition table
<3>[ 1.487823] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 1.488159] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 1.511444] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.511779] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.512084] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.512390] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<4>[ 1.548614] [<c0d7bb08>] (dump_stack+0x20/0x24) from [<c073f974>] (warn_slowpath_common+0x64/0x74)
<4>[ 1.548614] [<c073f974>] (warn_slowpath_common+0x64/0x74) from [<c073f9c4>] (warn_slowpath_fmt+0x40/0x48)
<6>[ 1.588836] mmio_probe
<6>[ 1.589508] mmio_camera mmio_camera: MMIO driver initialized with minor=42
<6>[ 1.589538] mmio_camera mmio_camera: system_rev 7, NCP6914 Camera Sub-PMIC
<7>[ 1.595886] mmio_cam_power_pin_control pin : 2 , state 1
<7>[ 1.596466] mmio_cam_power_pin_control pin : 2 , state 0
<4>[ 1.624908] [<c0d7bb08>] (dump_stack+0x20/0x24) from [<c073f974>] (warn_slowpath_common+0x64/0x74)
<4>[ 1.624908] [<c073f974>] (warn_slowpath_common+0x64/0x74) from [<c073f9c4>] (warn_slowpath_fmt+0x40/0x48)
<6>[ 1.636779] asoc: snd-soc-dummy-dai <-> ux500-msp-i2s.0 mapping ok
<4>[ 1.668792] mmc1: host does not support reading read-only switch. assuming write-enable.
<6>[ 1.700103] mmc1: new high speed SDHC card at address 0007
<6>[ 1.700683] mmcblk1: mmc1:0007 SD8GB 7.21 GiB
<6>[ 1.702301] mmcblk1: p1
<6>[ 2.112426] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: errors=panic
<6>[ 2.246673] EXT4-fs (mmcblk0p2): recovery complete
<6>[ 2.247863] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
<6>[ 2.299285] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p2
<6>[ 2.491821] e2fsck: /dev/block/mmcblk0p2: recovering journal
<6>[ 2.491882] e2fsck: /system/bin/e2fsck: unable to set superblock flags on/dev/block/mmcblk0p2
<6>[ 2.581146] EXT4-fs (mmcblk0p2): recovery complete
<6>[ 2.583099] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: journal_async_commit,errors=panic
<6>[ 2.625762] EXT4-fs (mmcblk0p4): recovery complete
<6>[ 2.626617] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
<6>[ 2.669433] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p4
<6>[ 2.741790] e2fsck: /dev/block/mmcblk0p4: recovering journal
<6>[ 2.741851] e2fsck: /system/bin/e2fsck: unable to set superblock flags on/dev/block/mmcblk0p4
<6>[ 2.781799] EXT4-fs (mmcblk0p4): recovery complete
<6>[ 2.782684] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: journal_async_commit,errors=panic
<6>[ 2.803741] EXT4-fs (mmcblk0p7): recovery complete
<6>[ 2.804870] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
<6>[ 2.849517] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p7
<6>[ 2.897705] e2fsck: /dev/block/mmcblk0p7: recovering journal
<6>[ 2.897766] e2fsck: /system/bin/e2fsck: unable to set superblock flags on /dev/block/mmcblk0p7
<6>[ 2.912231] EXT4-fs (mmcblk0p7): recovery complete
<6>[ 2.913024] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: journal_async_commit,errors=panic
<6>[ 2.920623] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: errors=panic
<7>[ 3.355377] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 41301
<7>[ 3.362243] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 40447
<7>[ 3.367767] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 64030
<7>[ 3.367858] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 64025
<7>[ 3.370513] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 56153
<7>[ 3.374267] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 8012
<6>[ 3.374481] EXT4-fs (mmcblk0p5): 6 orphan inodes deleted
<6>[ 3.374511] EXT4-fs (mmcblk0p5): recovery complete
<6>[ 3.398315] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
<6>[ 3.449951] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p5
<6>[ 3.850677] e2fsck: /dev/block/mmcblk0p5: recovering journal
<6>[ 3.850738] e2fsck: /system/bin/e2fsck: unable to set superblock flags on /dev/block/mmcblk0p5
<7>[ 4.324157] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 41301
<7>[ 4.331481] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 40447
<7>[ 4.337310] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 64030
<7>[ 4.337463] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 64025
<7>[ 4.340911] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 56153
<7>[ 4.344512] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 8012
<6>[ 4.344940] EXT4-fs (mmcblk0p5): 6 orphan inodes deleted
<6>[ 4.344970] EXT4-fs (mmcblk0p5): recovery complete
<6>[ 4.365631] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: discard,noauto_da_alloc,journal_async_commit,errors=panic
<3>[ 6.199615] u8500_shrm shrm_bus: common receive with l2 header 210 failed
<4>[ 6.279571] [<c0d7bb08>] (dump_stack+0x20/0x24) from [<c073f974>] (warn_slowpath_common+0x64/0x74)
<4>[ 6.279602] [<c073f974>] (warn_slowpath_common+0x64/0x74) from [<c073fa40>] (warn_slowpath_null+0x2c/0x34)
<3>[ 21.941711] end_request: I/O error, dev mmcblk0, sector 3078528
<3>[ 32.071746] end_request: I/O error, dev mmcblk0, sector 3321888
<3>[ 32.073638] end_request: I/O error, dev mmcblk0, sector 3322784
<3>[ 34.127593] end_request: I/O error, dev mmcblk0, sector 2155520
<3>[ 34.253173] end_request: I/O error, dev mmcblk0, sector 3083136
<3>[ 34.792480] end_request: I/O error, dev mmcblk0, sector 1544704
<3>[ 35.217437] end_request: I/O error, dev mmcblk0, sector 3074040
<3>[ 35.709747] mmc2: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 35.710083] mmc2: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 35.734436] mmc2: [MMC] CMD TIMEOUT STATUS: 4, CMD: 8
<6>[ 35.811065] mmc2: new high speed SDIO card at address 0001
<3>[ 36.042938] end_request: I/O error, dev mmcblk0, sector 3071560
<4>[ 36.340393] sdio_reset_comm():
<4>[ 38.452423] Unknown PRIVATE command WLS_BATCHING GET - ignored
<4>[ 38.453887] Unknown PRIVATE command WLS_BATCHING STOP - ignored
<3>[ 44.364715] end_request: I/O error, dev mmcblk0, sector 3689008
<3>[ 44.548583] end_request: I/O error, dev mmcblk0, sector 3724064
<3>[ 62.210357] end_request: I/O error, dev mmcblk0, sector 3716120
<3>[ 62.472076] end_request: I/O error, dev mmcblk0, sector 3690320
<3>[ 62.775665] end_request: I/O error, dev mmcblk0, sector 3716184
<3>[ 75.980651] end_request: I/O error, dev mmcblk0, sector 3724512
<3>[ 82.332397] end_request: I/O error, dev mmcblk0, sector 2794080
<3>[ 84.947631] end_request: I/O error, dev mmcblk0, sector 3876768
<3>[ 84.949829] end_request: I/O error, dev mmcblk0, sector 3875328
<3>[ 84.959594] end_request: I/O error, dev mmcblk0, sector 3869184
<3>[ 84.960906] end_request: I/O error, dev mmcblk0, sector 3866992
<3>[ 84.962799] end_request: I/O error, dev mmcblk0, sector 3871616
<3>[ 84.965332] end_request: I/O error, dev mmcblk0, sector 3866848
<3>[ 84.967163] end_request: I/O error, dev mmcblk0, sector 3866944
<3>[ 84.969177] end_request: I/O error, dev mmcblk0, sector 3870088
<3>[ 84.971954] end_request: I/O error, dev mmcblk0, sector 3878192
<3>[ 84.973846] end_request: I/O error, dev mmcblk0, sector 3877888
<3>[ 84.991668] end_request: I/O error, dev mmcblk0, sector 3867520
<3>[ 84.993743] end_request: I/O error, dev mmcblk0, sector 3871424
<3>[ 84.998046] end_request: I/O error, dev mmcblk0, sector 3886120
<3>[ 85.004394] end_request: I/O error, dev mmcblk0, sector 3866016
<3>[ 100.235717] end_request: I/O error, dev mmcblk0, sector 3716664
<3>[ 100.686798] end_request: I/O error, dev mmcblk0, sector 3716728
<3>[ 107.611114] end_request: I/O error, dev mmcblk0, sector 3723728
<3>[ 116.956024] end_request: I/O error, dev mmcblk0, sector 3725024
<3>[ 117.235870] end_request: I/O error, dev mmcblk0, sector 3716960
<3>[ 117.372741] end_request: I/O error, dev mmcblk0, sector 3725088
<3>[ 123.722656] end_request: I/O error, dev mmcblk0, sector 3717024
<3>[ 123.910125] end_request: I/O error, dev mmcblk0, sector 3079640
<3>[ 128.908752] end_request: I/O error, dev mmcblk0, sector 3079712
<3>[ 129.095489] end_request: I/O error, dev mmcblk0, sector 3079776
<3>[ 129.182556] end_request: I/O error, dev mmcblk0, sector 3079840
<3>[ 129.626342] end_request: I/O error, dev mmcblk0, sector 1546240
<3>[ 132.953887] end_request: I/O error, dev mmcblk0, sector 3725248
<3>[ 132.995880] end_request: I/O error, dev mmcblk0, sector 3079680
<3>[ 133.043151] end_request: I/O error, dev mmcblk0, sector 3079744
<3>[ 133.115478] end_request: I/O error, dev mmcblk0, sector 3079808
<3>[ 146.493164] end_request: I/O error, dev mmcblk0, sector 3079976
<3>[ 156.772979] end_request: I/O error, dev mmcblk0, sector 3085152
<3>[ 189.913391] end_request: I/O error, dev mmcblk0, sector 2504704
<3>[ 223.977478] end_request: I/O error, dev mmcblk0, sector 2798968
<3>[ 455.043640] end_request: I/O error, dev mmcblk0, sector 3410928
<3>[ 455.045532] end_request: I/O error, dev mmcblk0, sector 3417352
<3>[ 455.047393] end_request: I/O error, dev mmcblk0, sector 3451248
<3>[ 455.049499] end_request: I/O error, dev mmcblk0, sector 3362560
<3>[ 455.051147] end_request: I/O error, dev mmcblk0, sector 3343104
<3>[ 455.053039] end_request: I/O error, dev mmcblk0, sector 3481160
<3>[ 455.055145] end_request: I/O error, dev mmcblk0, sector 3341440
<4>[ 1770.800903] Unknown PRIVATE command WLS_BATCHING GET - ignored
<4>[ 1770.802154] Unknown PRIVATE command WLS_BATCHING STOP - ignored
<3>[ 1806.052703] end_request: I/O error, dev mmcblk0, sector 3716824
[email protected]:/ # dmesg | grep mmc* > wat.txt
dmesg | grep mmc* > wat.txt
sh: can't create wat.txt: Read-only file system
write: Broken pipe
I even tried to clear the internal flash memory from Linux Ubuntu by unmounting internal memory card in CWM Recovery and mounting it as Linux drive, but when I excecuted
Code:
dd if=/dev/zero of/dev/sdb1
and waited for ~2 hours, unmounted drive in Linux and mounted it back in Recovery, nothing happend. It still shows than at sdcard is AOSP.
What I can do with this phone? I have no warranty anymore, because the original system worked very poorly and even if I wanted to - I can't install it, because Samsung Kies does not recognise the phone. Is there any step-by-step tutorial about wiping contents of internal memory card and installing Android on sd card?
Did you try odin?
Yes, I tried ~week ago 4 times. Twice with version 3.10 and twice with Odin 3 v1.85. Installing stock ROM has not helped, I still have AOSP.
But how? There was an error in odin ot what?
Sent from my C1905 using XDA Free mobile app
There was no error, Odin just "stated" that everything was installed correctly, but when I reboot the phone, it still got unchanged AOSP ROM.
Hi All,
Anybody could help me coz got a bit of problem here.
Rom: stock GB 2.3.5 I8150XXKI8
It seems that everything is read-only except the external SD. After reboot, revert back to previous state.
Unable to go to recovery mode.
Done many success flashing in download mode ( flash stock,recovery) though and nothing. it just revert back to the previous state
Reformat usb storage also does not work.
Alot of apps force close.
Long pause at the samsung w logo.
mmcblk0p17 and mmcblk0p27 seems to have an error from below dmesg output.
Needs to confirm with anyone.
Thanks.
<3>[ 3.161895] init: MOUNT NAME /dev/block/mmcblk0p15
<3>[ 3.161925] init: SEC_DEVENC ***[/dev/block/mmcblk0p15][0]
<6>[ 3.181334] EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1
<3>[ 3.181395] init: MOUNT NAME /dev/block/mmcblk0p12
<3>[ 3.181426] init: SEC_DEVENC ***[/dev/block/mmcblk0p12][0]
<6>[ 3.186003] EXT4-fs (mmcblk0p12): barriers disabled
<6>[ 3.202056] EXT4-fs (mmcblk0p12): recovery complete
<6>[ 3.202697] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode. Opts: barrier=0
<3>[ 3.202758] init: MOUNT NAME /dev/block/mmcblk0p16
<3>[ 3.202758] init: SEC_DEVENC ***[/dev/block/mmcblk0p16][0]
<6>[ 3.205413] EXT4-fs (mmcblk0p16): barriers disabled
<3>[ 3.215056] init: [boot time] finish coldboot
<6>[ 3.216735] EXT4-fs (mmcblk0p16): recovery complete
<6>[ 3.217314] EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: barrier=0
<4>[ 3.220519] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.221129] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.238127] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.238738] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.248168] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.249205] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.258544] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.259154] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.271483] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 3.271514] mmc2: new high speed SDHC card at address 1234
<6>[ 3.271605] sdio_al mmc2:1234: Probing..
<6>[ 3.271605] sdio_al mmc2:1234: Not an SDIO card
<6>[ 3.271941] mmcblk1: mmc2:1234 SA16G 14.6 GiB
<6>[ 3.272124] mmcblk1: p1
<4>[ 3.276579] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.277220] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<3>[ 3.278319] init: [disk_config] :::: /dev/block/mmcblk0p27 (ext4)(opt (null)):::::
<3>[ 3.278349] init: internal_storage : ext_identify open
<3>[ 3.278380] init: internal_storage : ext_identify lseek
<3>[ 3.279234] init: internal_storage : ext_identify open
<3>[ 3.279265] init: internal_storage : ext_identify lseek
<3>[ 3.279295] init: MOUNT NAME /dev/block/mmcblk0p27
<3>[ 3.279326] init: SEC_DEVENC ***[/dev/block/mmcblk0p27][0]
<3>[ 3.279357] init: failed that mount s:'/dev/block/mmcblk0p27', t:'/efs', f:ext4 ,op null) (Device or resource busy)
<3>[ 3.279418] init: [disk_config] :::: /dev/block/mmcblk0p17 (ext4)(opt (null)):::::
<3>[ 3.279448] init: internal_storage : ext_identify open
<3>[ 3.279479] init: internal_storage : ext_identify lseek
<3>[ 3.280852] init: internal_storage : ext_identify open
<3>[ 3.280882] init: internal_storage : ext_identify lseek
<3>[ 3.282439] init: [disk_config] :::: fsck -> /dev/block/mmcblk0p17 (ext4):::::
<3>[ 3.282836] init: [disk_config] DEVENC : not mormal [0]
<3>[ 3.282836] init: [disk_config] DEVENC : fs_check with original dev_path
<3>[ 3.644621] mmc1 data status (0x8)
<3>[ 3.644652] mmc1: Data timeout opcode = 0x12
<3>[ 3.644682] mmc1: DMA channel flushed (0x80000004)
<3>[ 3.644682] Flush data: 0000c003 4f713000 00000000 00200040 00290028 00002003
<4>[ 3.645018] mmcblk0: retrying using single block read
<3>[ 4.017912] init: SEC_DEVENC check crypt status
<3>[ 4.017973] init: MOUNT NAME /dev/block/mmcblk0p17
<3>[ 4.017973] init: SEC_DEVENC ***[/dev/block/mmcblk0p17][1]
<3>[ 4.017973] init: SEC_DEVENC checkCrypt main
<3>[ 4.316953] mmc1 data status (0x8)
<3>[ 4.316953] mmc1: Data timeout opcode = 0x12
<3>[ 4.316984] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.316984] Flush data: 0000c003 4f713000 00000000 00200040 05b905b8 00002003
<4>[ 4.317320] mmcblk0: retrying using single block read
<3>[ 4.519804] mmc1 data status (0x8)
<3>[ 4.519834] mmc1: Data timeout opcode = 0x12
<3>[ 4.519865] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.519865] Flush data: 0000c003 4f713000 00000000 00200040 05b905b8 00002003
<4>[ 4.520170] mmcblk0: retrying using single block read
<3>[ 4.727903] mmc1 data status (0x8)
<3>[ 4.727903] mmc1: Data timeout opcode = 0x12
<3>[ 4.727934] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.727934] Flush data: 0000c003 4f713000 00000000 00200040 04690468 00002003
<4>[ 4.728300] mmcblk0: retrying using single block read
<3>[ 5.135984] mmc1 data status (0x8)
<3>[ 5.136015] mmc1: Data timeout opcode = 0x12
<3>[ 5.136045] mmc1: DMA channel flushed (0x80000004)
<3>[ 5.136045] Flush data: 0000c003 4f713000 00000000 00200040 00b900b8 00002003
<4>[ 5.136381] mmcblk0: retrying using single block read
<4>[ 5.233640] EXT4-fs (mmcblk0p17): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 5.234983] EXT4-fs (mmcblk0p17): recovery complete
<6>[ 5.235959] EXT4-fs (mmcblk0p17): mounted filesystem with ordered data mode. Opts: errors=continue
<3>[ 5.236020] init: SEC_DEVENC uncrypted parition mounted
<4>[ 5.237577] param_init !
<3>[ 5.237729] init: [boot time] processing action 0x3b6d8 (post-fs)
<3>[ 5.237760] init: [disk_config] :::: /dev/block/mmcblk0p28 (vfat)(opt (null)):::::
<3>[ 5.240323] init: oem_name (android )
<3>[ 5.244382] init: oem_name (android )
<3>[ 5.244474] init: [disk_config] :::: fsck -> /dev/block/mmcblk0p28 (vfat):::::
<3>[ 5.244901] init: [disk_config] DEVENC : not mormal [0]
<3>[ 5.244932] init: [disk_config] DEVENC : fs_check with original dev_path
<3>[ 5.599302] mmc1 data status (0x8)
<3>[ 5.599302] mmc1: Data timeout opcode = 0x12
<3>[ 5.599332] mmc1: DMA channel flushed (0x80000004)
<3>[ 5.599332] Flush data: 0000c003 4f713000 00000000 00200040 02690268 00002003
<4>[ 5.599698] mmcblk0: retrying using single block read
<3>[ 6.010587] mmc1 data status (0x8)
<3>[ 6.010587] mmc1: Data timeout opcode = 0x12
<3>[ 6.010617] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.010617] Flush data: 0000c003 4f713000 00000000 00200040 02790278 00002003
<4>[ 6.010984] mmcblk0: retrying using single block read
<3>[ 6.435544] mmc1 data status (0x8)
<3>[ 6.435544] mmc1: Data timeout opcode = 0x12
<3>[ 6.435574] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.435574] Flush data: 0000c003 4f713000 00000000 00200040 01b901b8 00002003
<4>[ 6.435910] mmcblk0: retrying using single block read
<3>[ 6.638852] mmc1 data status (0x8)
<3>[ 6.638883] mmc1: Data timeout opcode = 0x12
<3>[ 6.638883] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.638913] Flush data: 0000c003 4f713000 00000000 00200040 00b900b8 00002003
<4>[ 6.639249] mmcblk0: retrying using single block read
my internal memory was damaged. I flashed stock rom, entered it's recovery and formatted the internal memory. then installed cwm and installed custom rom. now everything is perfect.
ozgurakman said:
my internal memory was damaged. I flashed stock rom, entered it's recovery and formatted the internal memory. then installed cwm and installed custom rom. now everything is perfect.
Click to expand...
Click to collapse
Hi,
Thanks for the reply and good for you ozgurakman coz able to go to recovery mode. But I'm unable to go to recovery mode to repair the system though. Press the 3 recovery buttons. and just a screen flicker. It seem that my recovery corrupt also. Even after I reflash the recovery block only, still nada.
It seem that I'm running out options though. Anybody?
Did you tried to install cwm?
ozgurakman said:
Did you tried to install cwm?
Click to expand...
Click to collapse
yup also trying that one. also using the dd command in case the odin not working.
If dd command works, everything is fine. if dd command not working +Odin is not working, flashing via jtag is the only way.
ozgurakman said:
If dd command works, everything is fine. if dd command not working +Odin is not working, flashing via jtag is the only way.
Click to expand...
Click to collapse
the weird is that both dd and odin works. Also when i try to reboot it shutdown instead.
Will try to find shop that can do jtag. thanks
zaffrullah said:
the weird is that both dd and odin works. Also when i try to reboot it shutdown instead.
Will try to find shop that can do jtag. thanks
Click to expand...
Click to collapse
If I helped you, please press to thanks button
Last advise: try to different Odin version, different ops, different Rom.
Select to wipe everything.