Database Info

Urgent Linux Help Req'd. Bad ext2 partition...

My phone accidentally became unplugged from xp pc when it was mounted- the phone also dropped on the floor so i am not sure which caused the problem.
Problem is now that i cannot read the ext2 partition on my sd- hence it keeps hanging on boot screen..... when i open it in windows using extfs (or whatever the program is- i am typing this from dual booted linux) it wont even recognise it.
So i booted into ubuntu, which i have not used a hell of a lot, and it recognises the fat32 partition on the sd card but the ext2 it calls it 557.1MB Media. when i click on this a couple of errors come up- "cannot mount volume" and "unable to mount 557.1MB media"
please see attached screenshot.
Is there a way i can fix this ext2 partition?
If it is totally stuffed how do i format it again when gparted and partitin manager dont recognise this partition?
thanks

MontAlbert said:
My phone accidentally became unplugged from xp pc when it was mounted- the phone also dropped on the floor so i am not sure which caused the problem.
Problem is now that i cannot read the ext2 partition on my sd- hence it keeps hanging on boot screen..... when i open it in windows using extfs (or whatever the program is- i am typing this from dual booted linux) it wont even recognise it.
So i booted into ubuntu, which i have not used a hell of a lot, and it recognises the fat32 partition on the sd card but the ext2 it calls it 557.1MB Media. when i click on this a couple of errors come up- "cannot mount volume" and "unable to mount 557.1MB media"
please see attached screenshot.
Is there a way i can fix this ext2 partition?
If it is totally stuffed how do i format it again when gparted and partitin manager dont recognise this partition?
thanks
Click to expand...
Click to collapse
you can try to use fsck -t ext2 on linux to try to fix it, but if it got broken because you dropped I really doubt you'll be able to recovery everything. So you mind as well reformat it using fdisk and mkfs. even that may not help if there is physical damage on the sdcard itself.

knaries2000 said:
you can try to use fsck -t ext2 on linux to try to fix it, but if it got broken because you dropped I really doubt you'll be able to recovery everything. So you mind as well reformat it using fdisk and mkfs. even that may not help if there is physical damage on the sdcard itself.
Click to expand...
Click to collapse
how do i reformat it using fdisk and mkfs?
I can see the partition in file browser but when i go to open it it gives me the unable to mount error....i just want to reformat it and start all over again...... any ideas how to do that?

ok. surely there must be someone here who can help me?
I can't even determine which /dev/sda it is.....
I can see it but not load it in linux..... i just want to format the bugger and start over again!

when i do dmesg tail it gives me:
[ 242.702892] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 242.702918] EXT2-fs: group descriptors corrupted!
[ 1410.052668] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1410.052691] EXT2-fs: group descriptors corrupted!
[ 1530.800896] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1530.800923] EXT2-fs: group descriptors corrupted!
[ 1796.715217] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1796.715243] EXT2-fs: group descriptors corrupted!
[ 2628.601044] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 2628.601071] EXT2-fs: group descriptors corrupted!
[ 2660.632918] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 2660.632941] EXT2-fs: group descriptors corrupted!
now i am stumped- just want to somehow delete the bloody partition and format the whole disk over again....

it should be something like /dev/mmcblk0
just run "fdisk -l /dev/mmcblk0" if that doesn't exist try blk1... anyways if that is the card you should see 2 partition like you mention before..
then do "fdisk /dev/mmcblk0" delete the broken partition (should be 2nd one) and then recreate it. Do man on fdisk if you don't know how should be very simple.
once you have created the partition do "mkfs -t ext2 /dev/<partition that you created>"

MontAlbert said:
when i do dmesg tail it gives me:
[ 242.702892] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 242.702918] EXT2-fs: group descriptors corrupted!
[ 1410.052668] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1410.052691] EXT2-fs: group descriptors corrupted!
[ 1530.800896] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1530.800923] EXT2-fs: group descriptors corrupted!
[ 1796.715217] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1796.715243] EXT2-fs: group descriptors corrupted!
[ 2628.601044] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 2628.601071] EXT2-fs: group descriptors corrupted!
[ 2660.632918] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 2660.632941] EXT2-fs: group descriptors corrupted!
now i am stumped- just want to somehow delete the bloody partition and format the whole disk over again....
Click to expand...
Click to collapse
that means the block bit map of your ext2 partition is corrupted. wouldn't bother with trying to fix that. just recreate it. if you use ubuntu there should be a gui tool that lets you do this easier, but I've never used it... I only used fdisk

MontAlbert said:
ok. surely there must be someone here who can help me?
I can't even determine which /dev/sda it is.....
I can see it but not load it in linux..... i just want to format the bugger and start over again!
Click to expand...
Click to collapse
Patience. It hasn't even been an hour since you last asked. ^_^
Anyhoo, if you want an "easy" way to repartition it, just install Gparted and use that. ^_^
While you're using it, the difference between your hard drive and the sd card is that the SD card is the one with barely any space.

how would i do it with fdisk?
just did a fdisk -l and got:
[email protected]:/dev$ sudo fdisk -l
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8ae08ae0
Device Boot Start End Blocks Id System
/dev/sda1 * 1 23438 188265703+ 7 HPFS/NTFS
/dev/sda2 23439 23504 530145 82 Linux swap / Solaris
/dev/sda3 27638 30401 22201830 f W95 Ext'd (LBA)
/dev/sda4 23505 27637 33198322+ 83 Linux
/dev/sda5 27638 30401 22201798+ b W95 FAT32
Partition table entries are not in disk order
Disk /dev/sdb: 8017 MB, 8017412096 bytes
255 heads, 63 sectors/track, 974 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 907 7281381+ b W95 FAT32
/dev/sdb2 908 975 544026 83 Linux
Partition 2 has different physical/logical endings:
phys=(973, 254, 63) logical=(974, 185, 42)
[email protected]:/dev$

thanks for your help- for some reason when i had card in card reader of PC gparted couldnt see it but when i put it into phone and mounted phone it found it ok. Reformatting now.
damn...... time to buy a back up card i reckon!!!

your memory card is not there in your fsck it should be something like "/dev/mmcblk0" try "fdisk -l /dev/mmcblk0"

knaries2000 said:
your memory card is not there in your fsck it should be something like "/dev/mmcblk0" try "fdisk -l /dev/mmcblk0"
Click to expand...
Click to collapse
thanks mate- just reformatted it- lucky i did a nandroid yesterday and backep up apps the day before.....
i spent about 8hrs trying to fix this- the first 4-5 before i realised it was a stuffed sd card (realised when in bed at 2am)......i was even ringing local pc stores to see if they had cl6 8GB cards....

[Q] No MBR found after flashing image files into a board

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

[Q] How can i unpack/repack this system_1.img+system_2.img+...+system_8.img

I want to modify the Saihon X6 ROM, but the system.img is different from I've ever met, they put the system.img into 8 img, now do not know how to unpack/repack, I need help, need a detailed tutorial. Thank you
ht tp://pan.baidu.com/s/1pJAvLer

How can i unpack/repack like this system.img
ardager said:
I want to modify the Saihon X6 ROM, but the system.img is different from I've ever met, they put the system.img into 8 img, now do not know how to unpack/repack, I need help, need a detailed tutorial. Thank you
ht tp://pan.baidu.com/s/1pJAvLer
Click to expand...
Click to collapse
I used this on ubuntu
Run sudo mount-o loop system_1.img system
displays
Mount: wrong fs type, bad option, bad superblock on / dev/loop0,
Missing codepage or helper program, or Other Error
system log may have some important information,
try using dmesg | tail like a command.
Run dmesg | tail view LOG
display
[74.005499] audit_printk_skb: 18 callbacks suppressed
[74.005518] type = 1400 Audit (1360118240.727:23): AppArmor = "DENIED" operation = "capable" parent = 1 Profile = "/ usr / lib / Telepathy / mission-control-5 "pid = 1553 COMM =" mission-control "Capability = 23 capname =" sys_nice "
[74.415356] type = 1400 Audit (1360118241.135:24): AppArmor = "DENIED" operation = "Open" parent = 1 profile = "/ usr/lib/telepathy/mission-control-5" name = "/ usr / share / gvfs / remote-volume-monitors /" pid = 1553 comm = "mission-control" requested_mask = "r" denied_mask = "r" fsuid = 0 ouid = 0
[365.116251] EXT4-fs (loop0): bad geometry: Block count 97 656 Exceeds Size of device (32767 Blocks)
[579.113993] hrtimer: interrupt took 5,682,946 ns
[630.545278] EXT4-fs ( loop0): bad geometry: Block count ninety-seven thousand six hundred and fifty-six Exceeds Size of device (32767 Blocks)
[644.026965] EXT4-fs (loop0): Unrecognized Mount option "loop1" or Missing value
[670.312507] EXT4-fs (loop0): bad geometry: Block count ninety-seven thousand six hundred fifty-six Exceeds Size of device (32767 Blocks)
[788.599457] EXT4-fs (loop0): bad geometry: 76800 Block count Exceeds Size of device (1657 Blocks)
[1008.514549] EXT4-fs (loop0): bad geometry: Block count 97,656 exceeds size of device (32767 blocks)
file system_1.img
results
system_1.img: Linux rev 1.0 ext4 filesystem data, UUID = 57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)

Anyone made a GT-N8010 or GT-N8013 boot from SD?

I know it's a dead platform pretty much but here goes... I have a mangled GT-N8010. It's been fine for years, I even rooted it and installed nerdyblonde's blissrom image middle of last year. All of a sudden out of nowhere I get bootloop.
It's got TWRP on it and I notice that most of the partitions mount ro even though I have selected for them to be rw. Then I realise that they mount rw to start with then transition to ro due to filesystem errors. From dmesg:
Code:
<6>[ 806.261839] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 806.455283] c0 Atmel MXT1664S 3-004a: P: id[0]
<6>[ 806.519815] c0 Atmel MXT1664S 3-004a: R: id[0] M[0]
<3>[ 806.527889] c2 mmc0: mshci_check_sbc_status cmd response crc error
<3>[ 806.527925] c2 mmc0: it occurs a critical error on eMMC it'll try to recover eMMC to normal state
<6>[ 806.712682] c2 mmc0: recovering eMMC has been done
<3>[ 806.712698] c2 brq->sbc.opcode=23,brq->cmd.opcode=18.
<3>[ 806.712706] c2 brq->sbc.error=-110,brq->cmd.error=0, brq->stop.error=0,brq->data.error=0.
<3>[ 806.712747] c2 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x900
<3>[ 806.712755] c2 mmcblk0: not retrying timeout
<3>[ 806.712813] c2 end_request: I/O error, dev mmcblk0, sector 6008856
<3>[ 806.712908] c2 CMD aborting case in MMC's block layer ret 0.
<3>[ 806.712916] c2 mmcblk0: CMD18, ARG=0x5bb018.
<3>[ 806.712921] c2 packed CMD type = 0.
<3>[ 806.712926] c2 mmc0, request returns 4.
<2>[ 806.713152] c1 EXT4-fs error (device mmcblk0p12): ext4_find_entry:934: inode #2: comm ls: reading directory lblock 0
<3>[ 806.713166] c1 Aborting journal on device mmcblk0p12-8.
<2>[ 806.713176] c1 EXT4-fs (mmcblk0p12): Remounting filesystem read-only
<6>[ 807.261975] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 808.262113] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 809.262253] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 810.262394] c0 binder: 1803:1803 transaction failed 29189, size 0-0
So my internal eMMC is broken. The broken sectors are all over the place too so I don't think I can partition around them with a custom PIT:
Code:
end_request: I/O error, dev mmcblk0, sector 180224
end_request: I/O error, dev mmcblk0, sector 209968
end_request: I/O error, dev mmcblk0, sector 1818496
end_request: I/O error, dev mmcblk0, sector 4685696
end_request: I/O error, dev mmcblk0, sector 5709696
end_request: I/O error, dev mmcblk0, sector 5726210
end_request: I/O error, dev mmcblk0, sector 6008856
end_request: I/O error, dev mmcblk0, sector 30769024
I think I have the latest 4.4.2 Samsung bootloader so what I can do from the bootloader is limited (basically just boot into odin/download mode or into TWRP - no fastboot. Obviously due to failed eMMC I get loads of NAND failures trying to do things with odin.
I would like to make use of the tablet for another 6 months or so, so has anyone ever had any success booting one of these from SD card?

Damn, sorry this should have gone in the Q&A forum. Could someone move it please? Sorry!

Use the report button .

Test custom (zip) ROM on Android Emulator

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