Related
Hey everyone,
I am having a strange problem with my sd-ext (ext4) partition for some time now.
The ROM I am using is ICS for Desire by Sandvold (Amarullz and a2sd), but I don't know whether this is strictly ROM related or not.
I have been getting some mass FCs over and over again, across different versions flashed after full wipes.
Today I found out that the problem is that the sd-ext partition is not properly mounted (read-only), but here is the weird part: it is properly mounted (read-write) using the recovery and is also properly mounted before I unlock the sim-card.
When I unlock the sim-card or otherwise change the connectivity (WLAN, mobile data, airplane mode) it remounts sd-ext as read-only.
I have already tried reformatting and repartioning the sd-card.
Any idea why the system is doing that or how I can prevent that from happening?
Thanks
\Update1:
Here is a part of dmesg, showing the error when I unlock the sim-card after a fresh reboot:
Code:
<6>[ 182.512451] active wake lock PowerManagerService
<6>[ 182.512481] active wake lock vbus_present
<6>[ 182.512481] active wake lock SMD_DS, time left 35
<6>[ 182.512481] [R] early_suspend end
<6>[ 190.756866] batt: 74%, 3884 mV, 290 mA (210 avg), 29.8 C, 1008 mAh
<3>[ 191.665740] mmc1: Data CRC error
<3>[ 191.665954] msmsdcc_data_err: opcode 0x00000019
<3>[ 191.666168] msmsdcc_data_err: blksz 512, blocks 16
<3>[ 191.666595] mmc1: DMA channel flushed (0x80000004)
<3>[ 191.666839] Flush data: 0000c003 3b2d8018 00000000 00400040 00370035 00008003
<6>[ 191.667266] mmc1: Controller has been re-initialiazed
<3>[ 191.672515] mmcblk0: error -84 transferring data, sector 6710376, nr 16, card status 0x900
<3>[ 191.672973] mmc1: Data timeout
<6>[ 191.673217] mmc1: Controller has been re-initialiazed
<3>[ 191.673797] end_request: I/O error, dev mmcblk0, sector 6710376
<3>[ 191.674041] end_request: I/O error, dev mmcblk0, sector 6710384
<3>[ 191.679138] Aborting journal on device mmcblk0p2-8.
<0>[ 191.687255] journal commit I/O error
<2>[ 191.726745] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:276: Detected aborted journal
<2>[ 191.727478] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
<3>[ 191.984802] binder: 1268: binder_alloc_buf, no vma
<6>[ 191.985046] binder: 206:339 transaction failed 29201, size 4-0
<6>[ 191.985412] binder: send failed reply for transaction 79996 to 1268:1268
The weird thing is that I have been running the phone without any problem in airplane mode + WLAN for a whole day, until I tried to reactivate mobile connection again and do some tests with it.
It seems that the system only has a problem with the journal when it uses the mobile connection.
\Update2:
Here the dmesg message before I unlock the sim-card. No error message for sd-ext:
Code:
<6>[ 13.084991] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
4EXT is also unable to find any errors with the sd-ext partition (I have used the recovery to format and partition the sd-card).
\Update3:
Ok I just reformatted and repartitioned the sdcard again using gparted and reflashed the ROM with a full wipe.
I am getting the same error again.
Hi all,
I have a Galaxy Nexus with CyanogenMod 10.1 RC2.
Yesterday the battery discharged and the phone turned off.
When at home, I charged and booted it. Short after the phone turned on, it rebooted.
It continues to reboot a few seconds after I turn it on. I wiped everything, and I reinstalled Cyanogenmod, without any effect.
I tried to read the kmesg via ADB. It seems to be a filesysem corruption: pastebin.com/6J2NR4ne
The beginning of the errors is this:
Code:
<6>[ 56.475524] sr_class1p5_calib_work: iva: Calibration complete: Voltage:Nominal=950000,Calib=860920,margin=13000
<4>[ 66.156127] omap_hsi omap_hsi.0: Missed previous CAWAKE falling edge...
<3>[ 66.157775] mmcblk0: timed out sending r/w cmd command, card status 0x900
<3>[ 66.157958] mmcblk0: not retrying timeout
<3>[ 66.158111] end_request: I/O error, dev mmcblk0, sector 2398632
<3>[ 66.158233] end_request: I/O error, dev mmcblk0, sector 2398640
<3>[ 66.158416] end_request: I/O error, dev mmcblk0, sector 2398648
<3>[ 66.158630] end_request: I/O error, dev mmcblk0, sector 2398656
<3>[ 66.158782] Aborting journal on device mmcblk0p12-8.
<0>[ 66.164672] journal commit I/O error
<2>[ 66.170043] EXT4-fs error (device mmcblk0p12): ext4_journal_start_sb:296: Detected aborted journal
<2>[ 66.170715] EXT4-fs (mmcblk0p12): Remounting filesystem read-only
Can anyone help me?
I tried to run e2fsck on /dev/block/mmcblk0p12 while in recovery. It did not solve the problem.
Code:
~ # e2fsck /dev/block/mmcblk0p12
e2fsck 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p12: recovering journal
/dev/block/mmcblk0p12 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p12: 25726/887696 files (4.9% non-contiguous), 1129492/3549691 blocks
SOLVED.
Wiping the /data partition only deleted the files. I flashed userdata.img from the stock image (downloaded from google code), it rewrote /data and it worked
Please report the thread for closing.
Sent from my Nexus
Thread closed per OP's request.
A few days ago, I noticed my phone started displaying the SIM unlock menu in the morning. Later, I saw it reboot all of a sudden, and so I left it to observe for a bit more. The random reboots continued, so I rebackuped everything in TiBu, did a factory reset (wipe /data without /sdcard, /cache and dalvik cache) and updated the ROM I was using.
The reboots were still there, so I copied out all the data, suspecting corruption. My phone rebooted halfway through copying the files so I did it again in recovery. Then, I ran fastboot -w and rebooted into TWRP. It asked for an encryption password, and after doing a factory reset and rebooting it still did. Booting normally and then rebooting into TWRP fixed that.
After that, I went back ingo TWRP and used adb to push the sdcard files back in. Halfway through, adb gave me an error:
Code:
failed to copy './DCIM/Camera/IMG_20130121_174846.jpg' to '/sdcard/DCIM/Camera/IMG_20130121_174846.jpg': Read-only file system
I tried again and the same thing happened. I decided to look in dmesg, and lo and behold:
Code:
......
<3>[ 1232.192260] end_request: I/O error, dev mmcblk0, sector 5539768
<3>[ 1232.192443] end_request: I/O error, dev mmcblk0, sector 5539776
<3>[ 1232.192749] end_request: I/O error, dev mmcblk0, sector 5539784
<3>[ 1232.192932] end_request: I/O error, dev mmcblk0, sector 5539792
<3>[ 1232.193267] end_request: I/O error, dev mmcblk0, sector 5539800
<3>[ 1232.193420] end_request: I/O error, dev mmcblk0, sector 5539808
<3>[ 1232.193756] end_request: I/O error, dev mmcblk0, sector 5539816
<3>[ 1232.193939] end_request: I/O error, dev mmcblk0, sector 5539824
<3>[ 1232.194244] end_request: I/O error, dev mmcblk0, sector 5539832
<3>[ 1232.194580] Buffer I/O error on device mmcblk0p12, logical block 394880
<3>[ 1232.194793] Buffer I/O error on device mmcblk0p12, logical block 394881
<3>[ 1232.195129] Buffer I/O error on device mmcblk0p12, logical block 394882
<3>[ 1232.195312] Buffer I/O error on device mmcblk0p12, logical block 394883
<3>[ 1232.195648] Buffer I/O error on device mmcblk0p12, logical block 394884
<3>[ 1232.195861] Buffer I/O error on device mmcblk0p12, logical block 394885
<3>[ 1232.196197] Buffer I/O error on device mmcblk0p12, logical block 394886
<3>[ 1232.196533] Buffer I/O error on device mmcblk0p12, logical block 394887
<3>[ 1232.196716] Buffer I/O error on device mmcblk0p12, logical block 394888
<3>[ 1232.197052] Buffer I/O error on device mmcblk0p12, logical block 394889
......
<3>[ 1275.397430] Buffer I/O error on device mmcblk0p12, logical block 2600935
<3>[ 1275.397491] Buffer I/O error on device mmcblk0p12, logical block 2600936
<4>[ 1275.397613] EXT4-fs warning (device mmcblk0p12): ext4_end_bio:258: I/O error writing to inode 643562 (offset 1572864 size 524288 starting block 2898409)
<4>[ 1275.479003] JBD2: Detected IO errors while flushing file data on mmcblk0p12-8
......
<3>[ 1529.202911] mmcblk0: timed out sending r/w cmd command, card status 0x900
<3>[ 1529.203247] mmcblk0: not retrying timeout
<3>[ 1529.203430] end_request: I/O error, dev mmcblk0, sector 2425376
<3>[ 1529.203765] end_request: I/O error, dev mmcblk0, sector 2425384
<3>[ 1529.203979] end_request: I/O error, dev mmcblk0, sector 2425392
<3>[ 1529.204284] end_request: I/O error, dev mmcblk0, sector 2425400
<3>[ 1529.204620] end_request: I/O error, dev mmcblk0, sector 2425408
<3>[ 1529.204803] end_request: I/O error, dev mmcblk0, sector 2425416
<3>[ 1529.205139] end_request: I/O error, dev mmcblk0, sector 2425424
<3>[ 1529.205322] end_request: I/O error, dev mmcblk0, sector 2425432
<3>[ 1529.205627] end_request: I/O error, dev mmcblk0, sector 2425440
<3>[ 1529.205993] Aborting journal on device mmcblk0p12-8.
<2>[ 1529.206420] EXT4-fs error (device mmcblk0p12) in ext4_reserve_inode_write:5654: Journal has aborted
<2>[ 1529.216522] EXT4-fs (mmcblk0p12): Remounting filesystem read-only
What should I do now?
Seems to me you're posting in the wrong section; and that your internal emmc has fried. Try to flash stock images, pre-erasing and pre-formatting system, userdata and boot partitions.
a manta wrote this.
Happened to me once... Couldn't revive it whatsoever... Sold it eventually.
Sent from my awesome Xperia Z
Boot into fastboot mode, then try to format the partitions (system, userdata, cache, boot) and see if it helps. Otherwise you've deep fried your NAND.
I had my gnex for a while never used it a lot, cause I got a nexus 4 after that and mine reboots several times a day even not overclocked, and I only ever pick it up to listen to music while my 4 is charging
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
IRX120 said:
I had my gnex for a while never used it a lot, cause I got a nexus 4 after that and mine reboots several times a day even not overclocked, and I only ever pick it up to listen to music while my 4 is charging
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
Click to expand...
Click to collapse
...
Cool story bro; you sure you're not on the wrong thread then?
a maguro wrote this.
beekay201 said:
...
Cool story bro; you sure you're not on the wrong thread then?
a maguro wrote this.
Click to expand...
Click to collapse
I was just trying to explain that my galaxy nexus had a similar issue
IRX120 said:
I was just trying to explain that my galaxy nexus had a similar issue
Click to expand...
Click to collapse
So that would mean all reboots are similar issues? No, whatever may have caused your issue is not necessarily the same issue here.
Sound like brick bug..... If flashing stock doesn't work then your only hope is to send it back to Samsung if you are still under warranty. Else, it looks like there is nothing much you can do as others have mentioned the eemc chip is gone
I was trying to do a backup on my sgh-t989 with clockworkmod and it kept locking up so went into the shell over adb to look at dmesg. This is what turned up:
<4>[ 71.804931] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 71.808410] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 71.808746] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts:
<2>[ 75.416381] EXT4-fs error (device mmcblk0p24): ext4_init_inode_table:1296: comm ext4lazyinit: Something is wrong with group 0
<2>[ 75.416412] Used itable blocks: 479itable unused count: 0
<2>[ 75.416442]
<3>[ 75.848297] Aborting journal on device mmcblk0p24-8.
<2>[ 75.862945] EXT4-fs (mmcblk0p24): Remounting filesystem read-only
<6>[ 157.712677] zcache: destroyed pool id=1, cli_id=65535
<4>[ 200.051544] adbd (152): /proc/152/oom_adj is deprecated, please use /proc/152/oom_score_adj instead.
<3>[ 240.546386] INFO: task jbd2/mmcblk0p24:139 blocked for more than 120 seconds.
<3>[ 240.546844] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 240.547302] jbd2/mmcblk0p24 D c078a2d8 0 139 2 0x00000000
<4>[ 240.548065] [<c078a2d8>] (__schedule+0x600/0x6e4) from [<c02d3780>] (jbd2_journal_commit_transaction+0x24c/0x14b0)
<4>[ 240.548583] [<c02d3780>] (jbd2_journal_commit_transaction+0x24c/0x14b0) from [<c02d8490>] (kjournald2+0xa4/0x204)
<4>[ 240.549102] [<c02d8490>] (kjournald2+0xa4/0x204) from [<c01a75f8>] (kthread+0x7c/0x84)
<4>[ 240.549560] [<c01a75f8>] (kthread+0x7c/0x84) from [<c0105a78>] (kernel_thread_exit+0x0/0x8)
Click to expand...
Click to collapse
So, I proceeded to turn e2fsck on it, but there are many, many, many problems:
~ # e2fsck -n /dev/block/mmcblk0p24
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p24 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 15288 was part of the orphaned inode list. IGNORED.
Inode 15288 is in use, but has dtime set. Fix? no
Inode 15288 has a extra size (3715) which is invalid
Fix? no
Special (device/socket/fifo) inode 15288 has non-zero size. Fix? no
Inode 15289 is in use, but has dtime set. Fix? no
Inode 15289 has imagic flag set. Clear? no
Inode 15289 has a extra size (14485) which is invalid
Fix? no
Inode 15290 is in use, but has dtime set. Fix? no
Inode 15290 has imagic flag set. Clear? no
Inode 15290 has a extra size (15464) which is invalid
Fix? no
Inode 15291 is in use, but has dtime set. Fix? no
Inode 15291 has imagic flag set. Clear? no
Inode 15291 has a extra size (16965) which is invalid
Fix? no
Inode 15292 is in use, but has dtime set. Fix? no
Inode 15292 has a extra size (18435) which is invalid
Fix? no
Inode 15293 is in use, but has dtime set. Fix? no
Inode 15293 has a extra size (19452) which is invalid
Fix? no
Inode 15294 is in use, but has dtime set. Fix? no
Inode 15294 has a extra size (20347) which is invalid
Fix? no
Inode 15295 is in use, but has dtime set. Fix? no
Inode 15295 has a extra size (21139) which is invalid
Fix? no
Inode 15296 is in use, but has dtime set. Fix? no
Inode 15296 has a extra size (23218) which is invalid
Fix? no
Inode 15297 is in use, but has dtime set. Fix? no
Inode 15297 has imagic flag set. Clear? no
Inode 15297 has a extra size (25720) which is invalid
Fix? no
Inode 15298 is in use, but has dtime set. Fix? no
Inode 15298 has imagic flag set. Clear? no
Inode 15298 has a extra size (29073) which is invalid
Fix? no
Inode 15299 is in use, but has dtime set. Fix? no
Inode 15299 has imagic flag set. Clear? no
Inode 15299 has a extra size (33375) which is invalid
Fix? no
Inode 15300 is in use, but has dtime set. Fix? no
Inode 15300 has a extra size (38067) which is invalid
Fix? no
Inode 15301 is in use, but has dtime set. Fix? no
Inode 15301 has a extra size (41538) which is invalid
Fix? no
Inode 15302 is in use, but has dtime set. Fix? no
Inode 15302 has imagic flag set. Clear? no
Inode 15302 has a extra size (43632) which is invalid
Fix? no
Inode 15303 is in use, but has dtime set. Fix? no
Inode 15303 has imagic flag set. Clear? no
Inode 15303 has a extra size (44940) which is invalid
Fix? no
Inode 15304 is in use, but has dtime set. Fix? no
Inode 15304 has imagic flag set. Clear? no
Inode 15304 has a extra size (46293) which is invalid
Fix? no
Inode 15305 is in use, but has dtime set. Fix? no
Inode 15305 has imagic flag set. Clear? no
Inode 15305 has a extra size (47549) which is invalid
Fix? no
Inode 15306 is in use, but has dtime set. Fix? no
Inode 15306 has imagic flag set. Clear? no
Inode 15306 has a extra size (49411) which is invalid
Fix? no
Inode 15307 is in use, but has dtime set. Fix? no
Inode 15307 has a extra size (51383) which is invalid
Fix? no
Special (device/socket/fifo) inode 15307 has non-zero size. Fix? no
Inode 15308 is in use, but has dtime set. Fix? no
Inode 15308 has a extra size (53012) which is invalid
Fix? no
Special (device/socket/fifo) inode 15308 has non-zero size. Fix? no
Inode 15309 is in use, but has dtime set. Fix? no
Inode 15309 has a extra size (53685) which is invalid
Fix? no
Inode 15310 is in use, but has dtime set. Fix? no
Inode 15310 has a extra size (54672) which is invalid
Fix? no
Inode 15288, i_size is 103938212115248, should be 0. Fix? no
Inode 15288, i_blocks is 54520, should be 0. Fix? no
Inode 15289 has compression flag set on filesystem without compression support. Clear? no
Inode 15289 has INDEX_FL flag set but is not a directory.
Clear HTree index? no
Inode 15289 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
HTREE directory inode 15289 has an invalid root node.
Clear HTree index? no
Inode 15289, i_size is 1469282542499554, should be 0. Fix? no
Inode 15289, i_blocks is 341837, should be 0. Fix? no
Inode 15290 has compression flag set on filesystem without compression support. Clear? no
Inode 15290 has INDEX_FL flag set but is not a directory.
Clear HTree index? no
Inode 15290 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
HTREE directory inode 15290 has an invalid root node.
Clear HTree index? no
Inode 15290, i_size is 1473401416137182, should be 0. Fix? no
Inode 15290, i_blocks is 342625, should be 0. Fix? no
Inode 15291 has compression flag set on filesystem without compression support. Clear? no
Inode 15291 has INDEX_FL flag set but is not a directory.
Clear HTree index? no
Inode 15291 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
HTREE directory inode 15291 has an invalid root node.
Clear HTree index? no
Inode 15291, i_size is 1479702133161773, should be 0. Fix? no
Inode 15291, i_blocks is 343944, should be 0. Fix? no
Inode 15292 has illegal block(s). Clear? no
Illegal block #0 (345615) in inode 15292. IGNORED.
Illegal block #1 (345628) in inode 15292. IGNORED.
Illegal block #2 (345728) in inode 15292. IGNORED.
Illegal block #3 (345756) in inode 15292. IGNORED.
Illegal block #4 (345789) in inode 15292. IGNORED.
Illegal block #5 (345808) in inode 15292. IGNORED.
Illegal block #6 (345826) in inode 15292. IGNORED.
Illegal block #7 (345841) in inode 15292. IGNORED.
Illegal block #8 (345857) in inode 15292. IGNORED.
Illegal block #9 (345874) in inode 15292. IGNORED.
Illegal block #10 (345887) in inode 15292. IGNORED.
Too many illegal blocks in inode 15292.
Clear inode? no
Suppress messages? no
Illegal block #11 (345904) in inode 15292. IGNORED.
Illegal indirect block (345923) in inode 15292. IGNORED.
Illegal double indirect block (345932) in inode 15292. IGNORED.
Illegal triple indirect block (345946) in inode 15292. IGNORED.
Error while iterating over blocks in inode 15292: Illegal triply indirect block found
e2fsck: aborted
~ #
Click to expand...
Click to collapse
Not sure if I should allow fsck to fix these. Usually, on Linux, this many errors mean a format of the partition. I don't know for sure what the parition is but it looks like Samsung system (Gingerbread) stuff:
~ # mount /dev/block/mmcblk0p24 /mnt -o ro
~ # ls mnt
CSCFiles.txt build.prop lost+found
CSCVersion.txt csc media
SW_Configuration.xml etc tts
T9DB fonts usr
app framework vsc
bin lib xbin
Click to expand...
Click to collapse
Any thoughts on next steps? If I format the partition I'm pretty much out of an OS. I was not able to flash CM 10.1 nor CM 9.1 as they would boot loop. Suspecting the partition problems, but not sure. It could be a much deeper promlem with underlying media. Is this parition on the removable CF card, or internal to the phone?
Thanks,Sorry so long. Trying to be thorough.
Go grab twrp 2.6.0.4, its 4.3 compatible and won't give u any issues like cwm does, plus its easier to use, if u need help with it pm me
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Go grab twrp 2.6.0.4, its 4.3 compatible and won't give u any issues like cwm does, plus its easier to use, if u need help with it pm me
Click to expand...
Click to collapse
The same thing seems to be happening with TWRP 2.6.0.4. It never finishes backing up. The twirly bar at the bottom just keeps going and going.. dmesg has similar errors as I was getting with CWM:
Code:
<6>[ 338.231903] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 338.237457] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 338.245483] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
<6>[ 338.266418] zcache: destroyed pool id=1, cli_id=65535
<6>[ 338.312561] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 338.318054] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 338.337127] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
<6>[ 338.343261] zcache: destroyed pool id=1, cli_id=65535
<4>[ 338.400177] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 338.413269] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 338.418823] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 338.426849] SELinux: initialized (dev mmcblk0p24, type ext4), uses xattr
<6>[ 338.447357] zcache: destroyed pool id=1, cli_id=65535
<6>[ 338.498107] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 338.503784] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 338.512145] SELinux: initialized (dev mmcblk0p27, type ext4), uses xattr
<6>[ 338.518615] zcache: destroyed pool id=1, cli_id=65535
<6>[ 339.817138] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 339.822662] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 339.847167] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
<4>[ 349.649108] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 349.682159] zcache: created ephemeral tmem pool, id=2, client=65535
<6>[ 349.687835] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 349.695648] SELinux: initialized (dev mmcblk0p24, type ext4), uses xattr
<2>[ 353.107177] EXT4-fs error (device mmcblk0p24): ext4_init_inode_table:1296: comm ext4lazyinit: Something is wrong with group 0
<2>[ 353.107238] Used itable blocks: 479itable unused count: 0
<2>[ 353.107269]
<3>[ 353.655029] Aborting journal on device mmcblk0p24-8.
<2>[ 353.696502] EXT4-fs (mmcblk0p24): Remounting filesystem read-only
<3>[ 362.501586] [TSP] Calibration End!!!!!!
<3>[ 362.504302] [TSP] Clearing unused slots
<3>[ 362.509887] [TSP] Calibration!!!!!!
<3>[ 362.515777] [TSP] Calibration End!!!!!!
<3>[ 362.518707] [TSP] Clearing unused slots
<6>[ 370.498046] max17040_set_property: charger full state!
<6>[ 410.588012] max17040_set_property: charger full state!
<6>[ 450.668121] max17040_set_property: charger full state!
<6>[ 450.672363] max17040_adjust_fullsoc : full_soc = 9641
<6>[ 456.575805] zcache: created ephemeral tmem pool, id=3, client=65535
<6>[ 456.581359] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 456.607147] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
<6>[ 456.613250] zcache: destroyed pool id=3, cli_id=65535
<6>[ 456.689239] zcache: created ephemeral tmem pool, id=3, client=65535
<6>[ 456.694732] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 456.710479] SELinux: initialized (dev mmcblk0p27, type ext4), uses xattr
<6>[ 456.716491] zcache: destroyed pool id=3, cli_id=65535
<6>[ 456.817138] zcache: destroyed pool id=2, cli_id=65535
<3>[ 480.577301] INFO: task jbd2/mmcblk0p24:205 blocked for more than 120 seconds.
<3>[ 480.583831] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 480.607147] jbd2/mmcblk0p24 D c07b1dc8 0 205 2 0x00000000
<4>[ 480.612762] [<c07b1dc8>] (__schedule+0x5cc/0x788) from [<c02d9c10>] (jbd2_journal_commit_transaction+0x1e0/0x1484)
<4>[ 480.637969] [<c02d9c10>] (jbd2_journal_commit_transaction+0x1e0/0x1484) from [<c02de7dc>] (kjournald2+0xa4/0x204)
<4>[ 480.657165] [<c02de7dc>] (kjournald2+0xa4/0x204) from [<c01a8234>] (kthread+0x7c/0x88)
<4>[ 480.664306] [<c01a8234>] (kthread+0x7c/0x88) from [<c0105e80>] (kernel_thread_exit+0x0/0x8)
<6>[ 490.748779] max17040_set_property: charger full state!
<6>[ 530.879364] max17040_set_property: charger full state!
<6>[ 530.883728] max17040_adjust_fullsoc : full_soc = 9630
<6>[ 570.908752] max17040_set_property: charger full state!
Something seems messed up with the filesystem or underlying media on mmcblk0p24. Any other ideas?
UPDATE: Thought I'd make a tar file of the contents of p24 so if I format it, I can untar everything back to the partition. tar failed with an error on file csc/sales_code.dat so I added a --exclude for that file and it seems to work. That's no guarantee the contents of all the files aren't screwed up but it's better than nothing. Question is, how to I format the partition? It mounts as ext4 but there is no mkfs.ext4 utility in the recovery boot. I could format the partition and try to flash CM-10x but not sure if that makes sense.
eris170 said:
The same thing seems to be happening with TWRP 2.6.0.4. It never finishes backing up. The twirly bar at the bottom just keeps going and going.. dmesg has similar errors as I was getting with CWM:
Code:
[ 338.231903] zcache: created ephemeral tmem pool, id=1, client=65535
[ 338.237457] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: (null)
[ 338.245483] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
[ 338.266418] zcache: destroyed pool id=1, cli_id=65535
[ 338.312561] zcache: created ephemeral tmem pool, id=1, client=65535
[ 338.318054] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
[ 338.337127] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
[ 338.343261] zcache: destroyed pool id=1, cli_id=65535
[ 338.400177] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
[ 338.413269] zcache: created ephemeral tmem pool, id=1, client=65535
[ 338.418823] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts: (null)
[ 338.426849] SELinux: initialized (dev mmcblk0p24, type ext4), uses xattr
[ 338.447357] zcache: destroyed pool id=1, cli_id=65535
[ 338.498107] zcache: created ephemeral tmem pool, id=1, client=65535
[ 338.503784] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: (null)
[ 338.512145] SELinux: initialized (dev mmcblk0p27, type ext4), uses xattr
[ 338.518615] zcache: destroyed pool id=1, cli_id=65535
[ 339.817138] zcache: created ephemeral tmem pool, id=1, client=65535
[ 339.822662] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
[ 339.847167] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
[ 349.649108] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
[ 349.682159] zcache: created ephemeral tmem pool, id=2, client=65535
[ 349.687835] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts: (null)
[ 349.695648] SELinux: initialized (dev mmcblk0p24, type ext4), uses xattr
[ 353.107177] EXT4-fs error (device mmcblk0p24): ext4_init_inode_table:1296: comm ext4lazyinit: Something is wrong with group 0
[ 353.107238] Used itable blocks: 479itable unused count: 0
[ 353.107269]
[ 353.655029] Aborting journal on device mmcblk0p24-8.
[ 353.696502] EXT4-fs (mmcblk0p24): Remounting filesystem read-only
[ 362.501586] [TSP] Calibration End!!!!!!
[ 362.504302] [TSP] Clearing unused slots
[ 362.509887] [TSP] Calibration!!!!!!
[ 362.515777] [TSP] Calibration End!!!!!!
[ 362.518707] [TSP] Clearing unused slots
[ 370.498046] max17040_set_property: charger full state!
[ 410.588012] max17040_set_property: charger full state!
[ 450.668121] max17040_set_property: charger full state!
[ 450.672363] max17040_adjust_fullsoc : full_soc = 9641
[ 456.575805] zcache: created ephemeral tmem pool, id=3, client=65535
[ 456.581359] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: (null)
[ 456.607147] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
[ 456.613250] zcache: destroyed pool id=3, cli_id=65535
[ 456.689239] zcache: created ephemeral tmem pool, id=3, client=65535
[ 456.694732] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: (null)
[ 456.710479] SELinux: initialized (dev mmcblk0p27, type ext4), uses xattr
[ 456.716491] zcache: destroyed pool id=3, cli_id=65535
[ 456.817138] zcache: destroyed pool id=2, cli_id=65535
[ 480.577301] INFO: task jbd2/mmcblk0p24:205 blocked for more than 120 seconds.
[ 480.583831] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 480.607147] jbd2/mmcblk0p24 D c07b1dc8 0 205 2 0x00000000
[ 480.612762] [] (__schedule+0x5cc/0x788) from [] (jbd2_journal_commit_transaction+0x1e0/0x1484)
[ 480.637969] [] (jbd2_journal_commit_transaction+0x1e0/0x1484) from [] (kjournald2+0xa4/0x204)
[ 480.657165] [] (kjournald2+0xa4/0x204) from [] (kthread+0x7c/0x88)
[ 480.664306] [] (kthread+0x7c/0x88) from [] (kernel_thread_exit+0x0/0x8)
[ 490.748779] max17040_set_property: charger full state!
[ 530.879364] max17040_set_property: charger full state!
[ 530.883728] max17040_adjust_fullsoc : full_soc = 9630
[ 570.908752] max17040_set_property: charger full state!
Something seems messed up with the filesystem or underlying media on mmcblk0p24. Any other ideas?
UPDATE: Thought I'd make a tar file of the contents of p24 so if I format it, I can untar everything back to the partition. tar failed with an error on file csc/sales_code.dat so I added a --exclude for that file and it seems to work. That's no guarantee the contents of all the files aren't screwed up but it's better than nothing. Question is, how to I format the partition? It mounts as ext4 but there is no mkfs.ext4 utility in the recovery boot. I could format the partition and try to flash CM-10x but not sure if that makes sense.
Click to expand...
Click to collapse
Try using a program like titanium backup ( I use Pro ) and save your apps+ data + system data ( messages / Bookmarks / wifi aps etc ) to an external card. Then, Odin the stock Image which will reformat and repair things. Afterwards, Odin twrp ( not cwm as it likely corrupted partitions to begin with) and reflash your rom. After the rom is good to go, restore all non system apps and data along with the titanium backed up settings / messages. If you have the pro version, it's executed as a batch and restores it all without pushing a single button after selecting what you want to restore. The whole process to restore only takes about 5 minutes. I always clean flash all roms and restore with titanium. It ensures no issues are brought along from the old rom
Sent from my SGH-T889 using xda app-developers app
pyraxiate;45142866 Afterwards said:
Jeezes what happened to CWM? It didn't always suck. ... installing Titanium.. will report back later.
Thanks for the reply.
Click to expand...
Click to collapse
What's the difference between flashing the stock ROM and just using CM-10.x? Also, does it matter which stock ROM should I use? UVLDE, UVLE1, UVLH1 ??? My Baseband version is T989 UVLDH right now (Android 2.3.6)
Ended up tarring up the files on the partition, formatting it with mke2fs and then using tune2fs to get the FS features worked out. Once it was mounting as ext4, I untarred the files back and all good now.
eris170 said:
Ended up tarring up the files on the partition, formatting it with mke2fs and then using tune2fs to get the FS features worked out. Once it was mounting as ext4, I untarred the files back and all good now.
Click to expand...
Click to collapse
Glad to hear you are back up and running ! I used to be an avid cwm user but fit the last 4 devices I've stuck with twrp. Cwm had too many issues restoring backups for me, along with not letting me restore backups I made using earlier versions after upgrading cwm. Twrp hasn't given me any issues at all changing between versions. On my note 2, I'm constantly swapping between 2 different roms depending on whether I need wifi calling at the time or not.
Sent from my SGH-T889 using xda app-developers app
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.