[G1 Android Development] R.Giskard_Reventlov:
Ok, I finally was able to connect to my G1 using "adb logcat" while it was trying to bootup CM 4.2.3.1 and it seems that it got stuck on the splash screen since stuff keep crashing behind the scene. I captured maybe 7 seconds worth of logs and there are at least 10 recorded crashes back to back to back as you can see below.

So it started nicely like this:

I//system/xbin/busybox( 48): +++ "This is your world, these are your people. You can live for yourself today, or help build tomorrow for everyone."
I//system/xbin/busybox( 48): +++ Welcome to Android 1.6 / CyanogenMod-4.2.3.1
I//system/xbin/busybox( 48): --- Checking filesystems
I//system/xbin/busybox( 48): e2fsck 1.41.9 (22-Aug-2009)
I//system/xbin/busybox( 48): /dev/block/mmcblk0p2: recovering journal
I//system/xbin/busybox( 48): /dev/block/mmcblk0p2: clean, 147/128520 files, 64261/514080 blocks
I//system/xbin/busybox( 48): cp: cannot stat '/data/dalvik-cache/*': No such file or directory
I//system/xbin/busybox( 48): +++ Apps-to-SD successfully enabled
I/logwrapper( 48): /system/xbin/busybox terminated by exit(0)
I/DEBUG ( 117): debuggerd: Oct 29 2009 22:44:47
E/flash_image( 123): error opening /data/recovery.img: No such file or directory
I/vold ( 116): Android Volume Daemon version 2.0
D/AKMD ( 125): akmd 1.6.6 START
D/AKMD ( 125): library version: 1.2.1.1129
I/vold ( 116): New MMC card '00000' (serial 2095087577) added @ /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:0001
I/vold ( 116): Disk (blkdev 179:0), 7954432 secs (3884 MB) 2 partitions
I/vold ( 116): New blkdev 179.0 on media 00000, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 2
I/vold ( 116): Partition (blkdev 179:1), 6699042 secs (3271 MB) type 0xb
I/vold ( 116): New blkdev 179.1 on media 00000, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 1
I/vold ( 116): Partition (blkdev 179:2), 1028160 secs (502 MB) type 0x83
I/vold ( 116): New blkdev 179.2 on media 00000, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 0
I/vold ( 116): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:0001/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 116): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 116): Volmgr not ready to handle device
D/vold ( 116): Bootstrapping complete

But then, these start coming in:

I/DEBUG ( 128): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 128): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,release-keys'
I/DEBUG ( 128): pid: 152, tid: 152 >>> /system/bin/rild <<<
I/DEBUG ( 128): signal 11 (SIGSEGV), fault addr 00000036
I/DEBUG ( 128): r0 00000006 r1 00000006 r2 00000006 r3 00000006
I/DEBUG ( 128): r4 00000006 r5 00000006 r6 00000006 r7 00000006
I/DEBUG ( 128): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 128): ip afe43198 sp bea5eb40 lr a9d1f5f5 pc a9d2b358 cpsr 00000030
I/DEBUG ( 128): #00 pc 0002b358 /system/lib/libutils.so
I/DEBUG ( 128): #01 pc b00002bc /system/bin/linker
I/DEBUG ( 128): #02 pc b00016c6 /system/bin/linker

The crashing process seems to vary between

>>> /system/bin/app_process <<<

>>> /system/bin/rild <<<

>>> /system/bin/mediaserver <<<

repeating infinitely (pid keep climbing).

Again, so my problem is 4.2.2 boots up fine but 4.2.3.1 (and 4.2.3) got stuck .. Please help?