Related
First of all my phone is working fine, and I don't see any errors.
However when I do FS check on the data partition - mmcblk0p2
it has so many errors!
Code:
e2fsck -yv /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
DATA 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? yes
Inode 80 was part of the orphaned inode list. FIXED.
Inode 89 was part of the orphaned inode list. FIXED.
Deleted inode 91 has zero dtime. Fix? yes
Inode 105 was part of the orphaned inode list. FIXED.
Inode 5905 has imagic flag set. Clear? yes
Inode 5905 has compression flag set on filesystem without compression support. Clear? yes
Inode 5905 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 5905, i_blocks is 4294967295, should be 0. Fix? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 5905 (...) has invalid mode (0177777).
Clear? yes
Pass 5: Checking group summary information
Inode bitmap differences: -80 -89 -91 -105
Fix? yes
Free inodes count wrong for group #0 (3270, counted=3273).
Fix? yes
Free inodes count wrong (117779, counted=117782).
Fix? yes
DATA: ***** FILE SYSTEM WAS MODIFIED *****
5098 inodes used (4.15%)
385 non-contiguous files (7.6%)
6 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 5026/57
76415 blocks used (15.55%)
0 bad blocks
1 large file
4376 regular files
707 directories
0 character device files
0 block device files
3 fifos
2 links
0 symbolic links (0 fast symbolic links)
3 sockets
--------
5091 files
[check again, it is fine now]
# e2fsck -v /dev/block/mmcblk0p2
e2fsck -v /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
DATA: clean, 5098/122880 files, 76415/491520 blocks
[force check again, ensure all errors are corrected]
# e2fsck -fv /dev/block/mmcblk0p2
e2fsck -fv /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
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
5098 inodes used (4.15%)
385 non-contiguous files (7.6%)
6 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 5026/57
76415 blocks used (15.55%)
0 bad blocks
1 large file
4376 regular files
707 directories
0 character device files
0 block device files
3 fifos
2 links
0 symbolic links (0 fast symbolic links)
3 sockets
--------
5091 files
Now all errors are corrected.
After a few days of normal use, install uninstall apps.... power off and on....
The data partition has errors again during FS check....
I have a Samsung development board. After flash ICS images files into internal storage, at first time it can boot to android animation but failed to go to launcher; when i boot it again, it report 'NO MBR is found at SD/MMC', and can not be flashed. I use MMC command to create the partition and flash it, same error occurs. u-boot log is:
reading kernel device 0 Start 6144, Count 10240
mmc read 0 0x40008000 6144 10240
MMC read: dev # 0, block # 6144, count 10240 ... there are pending interrupts 0x00000008
error during transfer: 0x00008024
mmc read failed
-1 blocks read: ERROR
completed
reading ramdisk device 0 Start 16384, Count 10240
mmc read 0 0x41000000 16384 10240
MMC read: dev # 0, block # 16384, count 10240 ... there are pending interrupts 0x00000008
[ERROR] response timeout error : 00002104 cmd 18
mmc read failed
-19 blocks read: ERROR
completed
Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
any other thoughts on why this issue would occur?
Got another crash last night, again copying a lot of new music onto the phone from computer. Crash call stack is different this time though.
Code:
[ 7523.190689] Buffer I/O error on device mmcblk0p15, logical block 6850041
[ 7523.197373] Buffer I/O error on device mmcblk0p15, logical block 6850042
[ 7523.204241] Buffer I/O error on device mmcblk0p15, logical block 6850043
[ 7523.210711] Buffer I/O error on device mmcblk0p15, logical block 6850044
[ 7523.217395] Buffer I/O error on device mmcblk0p15, logical block 6850045
[ 7523.224140] Buffer I/O error on device mmcblk0p15, logical block 6850046
[ 7523.230732] Buffer I/O error on device mmcblk0p15, logical block 6850047
[ 7523.237721] Aborting journal on device mmcblk0p15-8.
[ 7523.288385] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[ 7523.633754] cypress_touchkey 16-0020: not real interrupt (1).
[ 7524.010986] EXT4-fs error (device mmcblk0p15): ext4_journal_start_sb:328: Detected aborted journal
[ 7524.018982] EXT4-fs (mmcblk0p15): Remounting filesystem read-only
[ 7524.061985] Kernel panic - not syncing: EXT4-fs panic from previous error
[ 7524.062016]
[ 7524.069340] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c07b5180>] (panic+0x88/0x1f8)
[ 7524.077459] [<c07b5180>] (panic+0x88/0x1f8) from [<c01a0714>] (__ext4_abort+0xc0/0xe0)
[ 7524.085394] [<c01a0714>] (__ext4_abort+0xc0/0xe0) from [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8)
[ 7524.094794] [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8) from [<c018b140>] (ext4_dirty_inode+0x14/0x40)
[ 7524.104530] [<c018b140>] (ext4_dirty_inode+0x14/0x40) from [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4)
[ 7524.113839] [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4) from [<c0141c9c>] (file_update_time+0x100/0x120)
[ 7524.123392] [<c0141c9c>] (file_update_time+0x100/0x120) from [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428)
[ 7524.133586] [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428) from [<c00f1760>] (generic_file_aio_write+0x60/0xc8)
[ 7524.144085] [<c00f1760>] (generic_file_aio_write+0x60/0xc8) from [<c01819e4>] (ext4_file_write+0x258/0x2bc)
[ 7524.153821] [<c01819e4>] (ext4_file_write+0x258/0x2bc) from [<c012b108>] (do_sync_write+0x9c/0xd8)
[ 7524.162763] [<c012b108>] (do_sync_write+0x9c/0xd8) from [<c012b1ec>] (vfs_write+0xa8/0x130)
[ 7524.171095] [<c012b1ec>] (vfs_write+0xa8/0x130) from [<c012b414>] (sys_pwrite64+0x50/0x80)
[ 7524.179275] [<c012b414>] (sys_pwrite64+0x50/0x80) from [<c000de80>] (ret_fast_syscall+0x0/0x30)
[ 7524.188004] CPU1: stopping
[ 7524.190659] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c001294c>] (handle_IPI+0x100/0x1cc)
[ 7524.199357] [<c001294c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[ 7524.207964] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000dc3c>] (__irq_usr+0x3c/0x60)
[ 7524.216296] Exception stack(0xc6637fb0 to 0xc6637ff8)
[ 7524.221271] 7fa0: b65f8b76 b6ed66d7 b65f8b77 00000037
[ 7524.229481] 7fc0: 00000000 b6ed66da b65faba4 b65f8b54 b65f8b74 b796f610 b6ed5398 00000000
[ 7524.237630] 7fe0: 50704001 b65f8b3c b6ecb283 b6ebf55c 60030030 ffffffff
[ 7524.344360] Rebooting in 5 seconds..
[ 7529.347686] Going down for restart now
[ 7529.350708] msm_restart : clear reset flag
Wrong forum or the content too technical for people?
BSOD2600 said:
Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
Click to expand...
Click to collapse
Did you ever figure this out?
Was it transferring from SD to External SD? Or just to Internal?
Sent from my SCH-I535 using XDA Free mobile app
Nope, never figured this out and yes it's occurred more than once.
Seem to recall was transferring large file content from PC to Internal. Don't think it's happened with CM11m10 -- yet... but on the other hand I dont do large file transfers daily.
Still an issue with CM11m11 (or more likely the hardware). system reboot when deleting a ~300 MB file from within MX Player.
Code:
[52140.774902] Buffer I/O error on device mmcblk0p15, logical block 4134812
[52140.781556] end_request: I/O error, dev mmcblk0, sector 43663360
[52140.787874] Buffer I/O error on device mmcblk0p15, logical block 5046272
[52140.794405] end_request: I/O error, dev mmcblk0, sector 44711936
[52140.800387] Buffer I/O error on device mmcblk0p15, logical block 5177344
[52140.807254] Buffer I/O error on device mmcblk0p15, logical block 5242880
[52140.813846] Buffer I/O error on device mmcblk0p15, logical block 5275648
[57664.812106] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 158, 2379 clusters in bitmap, 1936 in gd
[57664.822300] Aborting journal on device mmcblk0p15-8.
[57664.833928] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[57664.833928]
[57664.842962] [<c0013928>] (unwind_backtrace+0x0/0xe0) from [<c07abc78>] (panic+0x88/0x1f8)
[57664.851172] [<c07abc78>] (panic+0x88/0x1f8) from [<c01a257c>] (ext4_handle_error+0x8c/0x98)
[57664.859504] [<c01a257c>] (ext4_handle_error+0x8c/0x98) from [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4)
[57664.869393] [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[57664.879892] [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0)
[57664.890055] [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4)
[57664.899852] [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0)
[57664.909436] [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0) from [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94)
[57664.919385] [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94) from [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0)
[57664.929365] [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0) from [<c0188a24>] (ext4_truncate+0xb4/0x174)
[57664.938582] [<c0188a24>] (ext4_truncate+0xb4/0x174) from [<c018d2c0>] (ext4_evict_inode+0x328/0x490)
[57664.947678] [<c018d2c0>] (ext4_evict_inode+0x328/0x490) from [<c0142c84>] (evict+0x94/0x158)
[57664.956101] [<c0142c84>] (evict+0x94/0x158) from [<c0139f50>] (do_unlinkat+0xe8/0x130)
[57664.963975] [<c0139f50>] (do_unlinkat+0xe8/0x130) from [<c000dec0>] (ret_fast_syscall+0x0/0x30)
[57665.072964] Rebooting in 5 seconds..
[57670.076779] Going down for restart now
[57670.079800] msm_restart : clear reset flag
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut
how to unbrick?
botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
how did you check this out?
theonecallednick said:
how did you check this out?
Click to expand...
Click to collapse
I found uart pin on mainboard for debuging .
with serial usb cable pl2303
This is the red light only and unknown hardware found (the unknown hardware is in fact mtk usb vcom driver buth sony version ) if you try sp flash tool for mtk then it comunicates with de phone buth it needs some authentication file.
Help..
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..
botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
.........................
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
Samuel Wankhede said:
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..
Click to expand...
Click to collapse
Try the guide given in thread linked below
http://forum.xda-developers.com/showpost.php?p=57614511&postcount=13
Please share uart pinout
Baudrate should be 115200??
Thanks
uart
please share the uart pinout , thanks
Hi all,
As the title says, the question is how to test a custom rom (the zip file that you should flash on your device) on an Android emulator. I opened this thread because also if this is a common problem with several threads about it (also here on xda), there isn't a real answer, i.e. a working method. I think I'm close to the solution, but it still doesn't work. So, I decided to share here my knowledge with the hope that someone can help me. This method is only for Linux.
Initial setup
Download and open Android Studio. Go to Tools -> Android -> AVD Manager. Create a new device with the same specs of your device. This means that you should choose the same screen size/resolution and the right cpu architecture. Android Studio suggests to install x86 images, because the emulation is faster. Nowadays, the most common architecture on smartphones is armeabi-v7a, so choose this one. I'll use as example a device with Android 4.2 (armeabi-v7a).
Replace system.img
If you go into ~/Android/Sdk/system-images folder, you'll find the folders related to the images that you've installed previously (in the initial setup). In my case I have ~/Android/Sdk/system-images/android-17/google_apis/armeabi-v7a/ which contains system.img. The system.img is the system partition. It's an ext4 filesystem image that you can mount in a folder (i.e. it's a way to "extract" its content):
Code:
$ mkdir system
# mount -o loop system.img system
Now you can edit its content, e.g. replacing some files. When you've done, you can unmount the image with the following command:
Code:
# umount /absolute/path/to/the/system.img
Our goal is to replace the system.img file with the system.img of our custom rom. Unzip the custom rom. If you go into its folder, you'll see the system folder that we need to transform into system.img.
First of all, we should rename the original system.img file (the stock android image):
Code:
$ cd ~/Android/Sdk/system-images/android-17/google_apis/armeabi-v7a
$ mv system.img original_system.img
Now we'll create a new ext4 filesystem (with the same number of blocks) where we'll put the content of the system folder of our custom rom.
Code:
$ dd if=/dev/null of=system.img bs=1M seek=550
$ mkfs.ext4 -F system.img
$ mkdir custom_system
# mount -o loop system.img custom_system
# cp -r /path/to/our/custom/rom/system/* custom_system/
# chmod 755 -R custom_system/
# umount /absolute/path/to/system.img
Note that we are using seek=550, because if the original system.img has 140800 blocks with a total size of 576.7 MB, we need to allocate the same amount of space. In fact, also our (custom) system.img will have a size of 576.7 MB with the same number of blocks. The last command (umount) isn't mandatory, you can proceed keeping mounted the image.
Start the emulator
At this point we should execute the emulator hoping that our system.img is ok.
Run the emulator following this command (I've a 64 bit system):
Code:
$ LD_LIBRARY_PATH=~/Android/Sdk/tools/emulator/lib64 ~/Android/Sdk/tools/emulator/emulator64-arm -show-kernel -avd Name_of_your_avd
I defined LD_LIBRARY_PATH because otherwise it can't find the libraries for the gpu emulation, an alternative solution is to use -gpu off to disable gpu emulation. The -show-kernel parameter is useful to see if there is some problem while the device is booting, instead of -debug-all that is useful to see all the stuff related to the emulator itself and not to the operating system (Android).
-----------------
Small Off-Topic:
Note that on my Linux system to start the emulator for an x86 image I should use:
Code:
LD_PRELOAD="/usr/lib/libstdc++.so.6" ./emulator -avd Avd_Name
--------------
In my case, it seems there is some problem during the boot (black screen all the time). The kernel messages are:
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Initializing cgroup subsys cpu
Linux version 3.4.67-01422-gd3ffcc7-dirty ([email protected]) (gcc version 4.8 (GCC) ) #1 PREEMPT Tue Sep 16 19:34:06 CEST 2014
CPU: ARMv7 Processor [410fc080] revision 0 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Goldfish
Truncating RAM at 00000000-3fffffff to -2f7fffff (vmalloc region overlap).
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 193040
Kernel command line: qemu=1 androidboot.hardware=goldfish console=ttyS0 android.qemud=1 android.checkjni=1 qemu.gles=0
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 760MB = 760MB total
Memory: 748640k/748640k available, 29600k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
.text : 0xc0008000 - 0xc0450618 (4386 kB)
.init : 0xc0451000 - 0xc0476000 ( 148 kB)
.data : 0xc0476000 - 0xc04af9c8 ( 231 kB)
.bss : 0xc04afa08 - 0xc05f9cb0 (1321 kB)
NR_IRQS:256
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
Console: colour dummy device 80x30
Calibrating delay loop... 410.41 BogoMIPS (lpj=2052096)
pid_max: default: 32768 minimum: 301
Security Framework initialized
SELinux: Initializing.
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys cpuacct
Initializing cgroup subsys freezer
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x3628b0 - 0x362908
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
Switching to clocksource goldfish_timer
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP: reno registered
UDP hash table entries: 512 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 176K
goldfish_new_pdev goldfish_interrupt_controller at ff000000 irq -1
goldfish_new_pdev goldfish_device_bus at ff001000 irq 1
goldfish_new_pdev goldfish_timer at ff003000 irq 3
goldfish_new_pdev goldfish_rtc at ff010000 irq 10
goldfish_new_pdev goldfish_tty at ff002000 irq 4
goldfish_new_pdev goldfish_tty at ff011000 irq 11
goldfish_new_pdev smc91x at ff012000 irq 12
goldfish_new_pdev goldfish_fb at ff013000 irq 13
goldfish_new_pdev goldfish_audio at ff004000 irq 14
goldfish_new_pdev goldfish_mmc at ff005000 irq 15
goldfish_new_pdev goldfish-battery at ff014000 irq 16
goldfish_new_pdev goldfish_events at ff015000 irq 17
goldfish_new_pdev goldfish_nand at ff016000 irq -1
goldfish_new_pdev qemu_pipe at ff017000 irq 18
goldfish_pdev_worker registered goldfish_interrupt_controller
goldfish_pdev_worker registered goldfish_device_bus
goldfish_pdev_worker registered goldfish_timer
goldfish_pdev_worker registered goldfish_rtc
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered smc91x
goldfish_pdev_worker registered goldfish_fb
goldfish_pdev_worker registered goldfish_audio
goldfish_pdev_worker registered goldfish_mmc
goldfish_pdev_worker registered goldfish-battery
goldfish_pdev_worker registered goldfish_events
goldfish_pdev_worker registered goldfish_nand
goldfish_pdev_worker registered qemu_pipe
audit: initializing netlink socket (disabled)
type=2000 audit(0.240:1): initialized
Installing knfsd (copyright (C) 1996 [email protected]).
fuse init (API version 7.18)
msgmni has been set to 1462
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
console [ttyS0] enabled
brd: module loaded
loop: module loaded
nbd: registered device at major 43
goldfish_audio_probe
goldfish nand dev0: size 22600000, page 512, extra 0, erase 0
goldfish nand dev1: size 80000000, page 512, extra 0, erase 0
goldfish nand dev2: size 4200000, page 512, extra 0, erase 0
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <[email protected]>
eth0: SMC91C11xFD (rev 1) at fe012000 IRQ 12 [nowait]
eth0: Ethernet addr: 52:54:00:12:34:56
mousedev: PS/2 mouse device common for all mice
*** events probe ***
events_probe() addr=0xfe015000 irq=17
events_probe() keymap=qwerty2
input: qwerty2 as /devices/virtual/input/input0
goldfish_rtc goldfish_rtc: rtc core: registered goldfish_rtc as rtc0
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: [email protected]
ashmem: initialized
logger: created 256K log 'log_main'
logger: created 256K log 'log_events'
logger: created 256K log 'log_radio'
logger: created 256K log 'log_system'
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (11700 buckets, 46800 max)
ctnetlink v0.93: registering with nfnetlink.
NF_TPROXY: Transparent proxy support initialized, version 4.1.0
NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
xt_time: kernel timezone is -0000
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
TCP: cubic registered
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
8021q: 802.1Q VLAN Support v1.8
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 0
mmc0: new SD card at address e118
goldfish_rtc goldfish_rtc: setting system clock to 2017-04-11 07:32:53 UTC (1491895973)
Freeing init memory: 148K
mmcblk0: mmc0:e118 SU02G 100 MiB
mmcblk0:
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot open '/initlogo.rle'
yaffs: dev is 32505856 name is "mtdblock0" rw
yaffs: passed flags ""
yaffs: dev is 32505857 name is "mtdblock1" rw
yaffs: passed flags ""
yaffs: dev is 32505858 name is "mtdblock2" rw
yaffs: passed flags ""
fs_mgr: Warning: unknown flag voldmanaged=sdcard:auto
fs_mgr: Warning: unknown flag noemulatedsd
EXT4-fs (mtdblock0): mounted filesystem with ordered data mode. Opts: barrier=1
EXT4-fs (mtdblock1): recovery complete
EXT4-fs (mtdblock1): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
fs_mgr: Running /system/bin/e2fsck on /dev/block/mtdblock1
fs_mgr: Cannot run fs_mgr binary /system/bin/e2fsck
EXT4-fs (mtdblock1): mounted filesystem with ordered data mode. Opts: barrier=1,nomblk_io_submit
EXT4-fs (mtdblock2): recovery complete
EXT4-fs (mtdblock2): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
fs_mgr: Running /system/bin/e2fsck on /dev/block/mtdblock2
fs_mgr: Cannot run fs_mgr binary /system/bin/e2fsck
EXT4-fs (mtdblock2): mounted filesystem with ordered data mode. Opts: (null)
fs_mgr: Cannot mount filesystem on /devices/platform/goldfish_mmc.0* at auto
init: fs_mgr_mount_all returned an error
fs_mgr: Cannot mount filesystem on /dev/block/mtdblock2 at /cache
init: fs_mgr_mount_all returned an error
fs_mgr: Cannot mount filesystem on /dev/block/mtdblock1 at /data
init: fs_mgr_mount_all returned an error
init: cannot find '/system/bin/qemu-props', disabling 'qemu-props'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
init: cannot find '/system/bin/qemud', disabling 'qemud'
init: cannot execve('/system/etc/init.goldfish.sh'): No such file or directory
init: cannot find '/system/bin/sh', disabling 'console'
init: untracked pid 63 exited
warning: `rild' uses 32-bit capabilities (legacy support in use)
init: untracked pid 56 exited
init: untracked pid 99 exited
init: untracked pid 149 exited
...continue with endless processes termination...
Click to expand...
Click to collapse
I created the system.img from a custom rom for huawei u9508 based on Android 4.2.2. I hope this post could be useful.
Nrin said:
Hi all,
As the title says, the question is how to test a custom rom (the zip file that you should flash on your device) on an Android emulator. I opened this thread because also if this is a common problem with several threads about it (also here on xda), there isn't a real answer, i.e. a working method. I think I'm close to the solution, but it still doesn't work. So, I decided to share here my knowledge with the hope that someone can help me. This method is only for Linux.
Initial setup
Download and open Android Studio. Go to Tools -> Android -> AVD Manager. Create a new device with the same specs of your device. This means that you should choose the same screen size/resolution and the right cpu architecture. Android Studio suggests to install x86 images, because the emulation is faster. Nowadays, the most common architecture on smartphones is armeabi-v7a, so choose this one. I'll use as example a device with Android 4.2 (armeabi-v7a).
Replace system.img
If you go into ~/Android/Sdk/system-images folder, you'll find the folders related to the images that you've installed previously (in the initial setup). In my case I have ~/Android/Sdk/system-images/android-17/google_apis/armeabi-v7a/ which contains system.img. The system.img is the system partition. It's an ext4 filesystem image that you can mount in a folder (i.e. it's a way to "extract" its content):
Now you can edit its content, e.g. replacing some files. When you've done, you can unmount the image with the following command:
Our goal is to replace the system.img file with the system.img of our custom rom. Unzip the custom rom. If you go into its folder, you'll see the system folder that we need to transform into system.img.
First of all, we should rename the original system.img file (the stock android image):
Now we'll create a new ext4 filesystem (with the same number of blocks) where we'll put the content of the system folder of our custom rom.
Note that we are using seek=550, because if the original system.img has 140800 blocks with a total size of 576.7 MB, we need to allocate the same amount of space. In fact, also our (custom) system.img will have a size of 576.7 MB with the same number of blocks. The last command (umount) isn't mandatory, you can proceed keeping mounted the image.
Start the emulator
At this point we should execute the emulator hoping that our system.img is ok.
Run the emulator following this command (I've a 64 bit system):
I defined LD_LIBRARY_PATH because otherwise it can't find the libraries for the gpu emulation, an alternative solution is to use -gpu off to disable gpu emulation. The -show-kernel parameter is useful to see if there is some problem while the device is booting, instead of -debug-all that is useful to see all the stuff related to the emulator itself and not to the operating system (Android).
-----------------
Small Off-Topic:
Note that on my Linux system to start the emulator for an x86 image I should use:
--------------
In my case, it seems there is some problem during the boot (black screen all the time). The kernel messages are:
I created the system.img from a custom rom for huawei u9508 based on Android 4.2.2. I hope this post could be useful.
Click to expand...
Click to collapse
kernel is not work for your system.img