Related
Hey all,
I finally got around to hacking my phone over the weekend. It went quite well (thanks to cyanogen, and all the people that help make this work).
I have firmware 4.0.4 installed (I did a wipe, firmware install, then another wipe), but the Gallery/Album crashes every time I try to start it. I can even take pictures with the camera, but when I try to view them through the gallery button, it crashes back to the camera - the pictures are there, though, I can view them via USB mounting.
I tried to get the debugger to attach to it, but it just waits forever.
I read that the album could be crashing when it tries to create thumbnails, but I completely emptied the fat32 partition, and it still has this problem.
I grabbed the logs, and they just show a segfault. I'm a Unix developer by day, but don't know what to do with an Android stack trace (don't have the dev tools for this set up).
Any help would be greatly appreciated. I tried searching the forums, and found nothing similar.
Code:
09-13 22:56:04.107 I/ActivityManager( 130): Starting activity: Intent { action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com.htc.album/com.htc.album.GalleryPicker} }
09-13 22:56:04.417 I/ActivityManager( 130): Start proc com.htc.album for activity com.htc.album/.GalleryPicker: pid=558 uid=10020 gids={1006, 3003, 2001}
09-13 22:56:04.877 I/ActivityManager( 130): Process android.process.media (pid 546) has died.
09-13 22:56:04.997 I/DEBUG ( 110): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-13 22:56:04.997 I/DEBUG ( 110): Build fingerprint: 'tmobile/kila/dream/trout:1.5/CRC1/150275:user/ota-rel-keys,release-keys'
09-13 22:56:04.997 I/DEBUG ( 110): pid: 558, tid: 558 >>> com.htc.album <<<
09-13 22:56:04.997 I/DEBUG ( 110): signal 11 (SIGSEGV), fault addr 42a1bf38
09-13 22:56:04.997 I/DEBUG ( 110): r0 42a1a730 r1 00000007 r2 434c4b50 r3 00000604
09-13 22:56:04.997 I/DEBUG ( 110): r4 42a1bf38 r5 001805b0 r6 ad079e1c r7 00001810
09-13 22:56:04.997 I/DEBUG ( 110): r8 00003071 r9 0000bc70 10 4104ac48 fp 00000000
09-13 22:56:04.997 I/DEBUG ( 110): ip 00000000 sp bed58538 lr ad05aae9 pc ad05a4d0 cpsr 00000030
09-13 22:56:06.567 W/GTalkService( 210): [DataMsgMgr] parseDataMessageIntent: not including app data -- key is reserved: account, -------
09-13 22:56:06.587 I/DEBUG ( 110): #00 pc 0005a4d0 /system/lib/libdvm.so
09-13 22:56:06.587 I/DEBUG ( 110): #01 pc 0005aae4 /system/lib/libdvm.so
09-13 22:56:06.587 I/DEBUG ( 110): #02 pc 000325ba /system/lib/libdvm.so
09-13 22:56:06.617 I/DEBUG ( 110): #03 pc 0003a110 /system/lib/libdvm.so
09-13 22:56:06.617 I/DEBUG ( 110): #04 pc 0004ea0e /system/lib/libdvm.so
09-13 22:56:06.617 I/DEBUG ( 110): #05 pc 0003aec4 /system/lib/libdvm.so
09-13 22:56:06.617 I/DEBUG ( 110): #06 pc 000131d8 /system/lib/libdvm.so
09-13 22:56:06.627 I/DEBUG ( 110): #07 pc 00017a30 /system/lib/libdvm.so
09-13 22:56:06.627 I/DEBUG ( 110): #08 pc 000174c4 /system/lib/libdvm.so
09-13 22:56:06.627 I/DEBUG ( 110): #09 pc 00049a64 /system/lib/libdvm.so
09-13 22:56:06.627 I/DEBUG ( 110): #10 pc 00050b50 /system/lib/libdvm.so
09-13 22:56:06.637 D/Sync ( 130): Received network tickle for --------
09-13 22:56:06.637 I/DEBUG ( 110): #11 pc 000131d8 /system/lib/libdvm.so
09-13 22:56:06.657 I/DEBUG ( 110): #12 pc 00017a30 /system/lib/libdvm.so
09-13 22:56:06.657 I/DEBUG ( 110): #13 pc 000174c4 /system/lib/libdvm.so
09-13 22:56:06.657 I/DEBUG ( 110): #14 pc 00049c52 /system/lib/libdvm.so
09-13 22:56:06.667 I/DEBUG ( 110): #15 pc 0003844c /system/lib/libdvm.so
09-13 22:56:06.707 I/DEBUG ( 110): #16 pc 00027c9c /system/lib/libandroid_runtime.so
09-13 22:56:06.707 I/DEBUG ( 110): #17 pc 00028796 /system/lib/libandroid_runtime.so
09-13 22:56:06.707 I/DEBUG ( 110): #18 pc 00008c9e /system/bin/app_process
09-13 22:56:06.717 I/DEBUG ( 110): #19 pc 0000be8a /system/lib/libc.so
09-13 22:56:06.737 I/DEBUG ( 110): #20 pc b00015e4 /system/bin/linker
09-13 22:56:06.737 I/DEBUG ( 110): stack:
09-13 22:56:06.737 I/DEBUG ( 110): bed584f8 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed584fc 00000036
09-13 22:56:06.737 I/DEBUG ( 110): bed58500 000081a4 /system/bin/app_process
09-13 22:56:06.737 I/DEBUG ( 110): bed58504 00000001
09-13 22:56:06.737 I/DEBUG ( 110): bed58508 000003e8
09-13 22:56:06.737 I/DEBUG ( 110): bed5850c 00002716
09-13 22:56:06.737 I/DEBUG ( 110): bed58510 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed58514 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed58518 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed5851c 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed58520 afe3bb40
09-13 22:56:06.737 I/DEBUG ( 110): bed58524 afe0ec98 /system/lib/libc.so
09-13 22:56:06.737 I/DEBUG ( 110): bed58528 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed5852c afe0eba8 /system/lib/libc.so
09-13 22:56:06.737 I/DEBUG ( 110): bed58530 df002777
09-13 22:56:06.737 I/DEBUG ( 110): bed58534 e3a070ad
09-13 22:56:06.737 I/DEBUG ( 110): #00 bed58538 001805b0 [heap]
09-13 22:56:06.737 I/DEBUG ( 110): bed5853c c0000000
09-13 22:56:06.737 I/DEBUG ( 110): bed58540 00003071
09-13 22:56:06.757 I/DEBUG ( 110): bed58544 afe0b85b /system/lib/libc.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58548 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed5854c 00000019
09-13 22:56:06.767 I/DEBUG ( 110): bed58550 00000019
09-13 22:56:06.767 I/DEBUG ( 110): bed58554 ad060aec /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58558 42a1a730 /data/dalvik-cache/[email protected]@[email protected]
09-13 22:56:06.767 I/DEBUG ( 110): bed5855c ad071516 /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58560 001805b0 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed58564 ad079e1c /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58568 429c8000 /data/dalvik-cache/[email protected]@[email protected]
09-13 22:56:06.767 I/DEBUG ( 110): bed5856c 001805b0 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed58570 00053000 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed58574 ad05aae9 /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): #01 bed58578 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed5857c 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed58580 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed58584 00053000 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed58588 001805b0 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed5858c 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed58590 00001000
09-13 22:56:06.767 I/DEBUG ( 110): bed58594 ad079e1c /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58598 bed585b0 [stack]
09-13 22:56:06.767 I/DEBUG ( 110): bed5859c 00000019
09-13 22:56:06.767 I/DEBUG ( 110): bed585a0 bed5864c [stack]
09-13 22:56:06.767 I/DEBUG ( 110): bed585a4 ad0325bf /system/lib/libdvm.so
09-13 22:56:06.927 I/ActivityManager( 130): Stopping service: com.android.providers.subscribedfeeds/.SubscribedFeedsIntentService
09-13 22:56:07.577 I/DEBUG ( 110): debuggerd committing suicide to free the zombie!
09-13 22:56:07.587 D/Zygote ( 112): Process 558 terminated by signal (11)
09-13 22:56:07.587 I/ActivityManager( 130): Process com.htc.album (pid 558) has died.
when using any rom, do not wipe after flashing it. if you wipe you must flash another rom. just boot into recovery wipe one more time, then flash the cm 4.0.4 rom. all should be fine.
I did another wipe, and re-applied 4.0.4
The gallery still crashes immediately.
debuggerd committing suicide to free the zombie!
that is hilarious. though back to the problem at hand.
did you check the md5sum to see if your download is correct? if not, then it could provide problems.
Yup, the md5sum of the image on /sdcard is what it should be.
I've heard a couple of people say 4.04 has issues. Try 4.02.
I can manage without the gallery for a while. Really, if this is a firmware issue I'd like to help debug and fix it if I can. What's my next step?
http://code.google.com/p/cyanogenmod/issues/list
thats where cyan's debugging is going on.. see if your issue is there and provide them feedback
I'd looked over there before I'd posted here, but I didn't see anything like my issue. As a developer myself, there are few things more annoying than when a bug is filed against my code when it turns out to be user error - I was just trying to avoid that
Ok, so I got this after reinstalling Cyanogen's 4.1.10.1 after installing a theme on top of it. So far I've tried wiping, restoring a backup, and installing multiple builds, no success.
Heres the logcat:
Code:
W/dalvikvm( 136): JNI_CreateJavaVM failed
E/AndroidRuntime( 136): JNI_CreateJavaVM failed
D/AndroidRuntime( 140):
D/AndroidRuntime( 140): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 140): CheckJNI is OFF
D/dalvikvm( 140): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 140): Stale deps in cache file; removing and retrying
D/dalvikvm( 140): DexOpt: --- BEGIN 'services.jar' (bootstrap=1) ---
I/DEBUG ( 116): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 116): Build fingerprint: 'tmobile/kila/dream/trout:1.5/CRC1/150275:
user/ota-rel-keys,release-keys'
I/DEBUG ( 116): pid: 142, tid: 142 >>> /system/bin/dexopt <<<
I/DEBUG ( 116): signal 11 (SIGSEGV), fault addr 44b60a42
I/DEBUG ( 116): r0 0000ea74 r1 415d0028 r2 41613df0 r3 44b60a42
I/DEBUG ( 116): r4 41051528 r5 00016510 r6 4000c358 r7 bedef9dc
I/DEBUG ( 116): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 116): ip ad07a0d0 sp bedef980 lr ad053349 pc ad052c5c cpsr 000
00030
I/DEBUG ( 116): #00 pc 00052c5c /system/lib/libdvm.so
I/DEBUG ( 116): #01 pc 00053344 /system/lib/libdvm.so
I/DEBUG ( 116): #02 pc 00053506 /system/lib/libdvm.so
I/DEBUG ( 116): #03 pc 00053c2e /system/lib/libdvm.so
I/DEBUG ( 116): #04 pc 00053e3e /system/lib/libdvm.so
I/DEBUG ( 116): #05 pc 00054352 /system/lib/libdvm.so
I/DEBUG ( 116): #06 pc 000471da /system/lib/libdvm.so
I/DEBUG ( 116): #07 pc 000476d4 /system/lib/libdvm.so
I/DEBUG ( 116): #08 pc 000478b4 /system/lib/libdvm.so
I/DEBUG ( 116): #09 pc 00008e20 /system/bin/dexopt
I/DEBUG ( 116): #10 pc 00008ed6 /system/bin/dexopt
I/DEBUG ( 116): #11 pc 0000bf12 /system/lib/libc.so
I/DEBUG ( 116): #12 pc b00016cc /system/bin/linker
I/DEBUG ( 116): stack:
I/DEBUG ( 116): bedef940 00000000
I/DEBUG ( 116): bedef944 afe0ec28 /system/lib/libc.so
I/DEBUG ( 116): bedef948 000119c4 [heap]
I/DEBUG ( 116): bedef94c afe0ed18 /system/lib/libc.so
I/DEBUG ( 116): bedef950 00000000
I/DEBUG ( 116): bedef954 afe0ec28 /system/lib/libc.so
I/DEBUG ( 116): bedef958 000119c0 [heap]
I/DEBUG ( 116): bedef95c ad079e1c /system/lib/libdvm.so
I/DEBUG ( 116): bedef960 000014b4
I/DEBUG ( 116): bedef964 0000216c
I/DEBUG ( 116): bedef968 410514f0 /dev/ashmem/dalvik-LinearAlloc (delet
ed)
I/DEBUG ( 116): bedef96c ad051ba5 /system/lib/libdvm.so
I/DEBUG ( 116): bedef970 410514f0 /dev/ashmem/dalvik-LinearAlloc (delet
ed)
I/DEBUG ( 116): bedef974 00016510 [heap]
I/DEBUG ( 116): bedef978 df002777
I/DEBUG ( 116): bedef97c e3a070ad
I/DEBUG ( 116): #00 bedef980 ad079e1c /system/lib/libdvm.so
I/DEBUG ( 116): bedef984 41051504 /dev/ashmem/dalvik-LinearAlloc (delet
ed)
I/DEBUG ( 116): bedef988 41641118 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef98c 4000c358 /dev/ashmem/mspace/dalvik-heap/0 (del
eted)
I/DEBUG ( 116): bedef990 4191a361 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef994 00016510 [heap]
I/DEBUG ( 116): bedef998 41641118 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef99c ad053349 /system/lib/libdvm.so
I/DEBUG ( 116): #01 bedef9a0 00002bd0
I/DEBUG ( 116): bedef9a4 000000dc
I/DEBUG ( 116): bedef9a8 00000000
I/DEBUG ( 116): bedef9ac afe0afbb /system/lib/libc.so
I/DEBUG ( 116): bedef9b0 42409e54 /data/dalvik-cache/[email protected]@s
[email protected]
I/DEBUG ( 116): bedef9b4 0000003a
I/DEBUG ( 116): bedef9b8 bedef9dc [stack]
I/DEBUG ( 116): bedef9bc 00000abe
I/DEBUG ( 116): bedef9c0 00000460
I/DEBUG ( 116): bedef9c4 00000b05
I/DEBUG ( 116): bedef9c8 00000002
I/DEBUG ( 116): bedef9cc 00000070
I/DEBUG ( 116): bedef9d0 415fdbf0 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef9d4 4000c3f4 /dev/ashmem/mspace/dalvik-heap/0 (del
eted)
I/DEBUG ( 116): bedef9d8 afe3bb8c
I/DEBUG ( 116): bedef9dc 00000abe
I/DEBUG ( 116): bedef9e0 00000000
I/DEBUG ( 116): bedef9e4 000be364
I/DEBUG ( 116): bedef9e8 00000722
I/DEBUG ( 116): bedef9ec ad079e1c /system/lib/libdvm.so
I/DEBUG ( 116): bedef9f0 00016578 [heap]
I/DEBUG ( 116): bedef9f4 41641118 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef9f8 00000000
I/DEBUG ( 116): bedef9fc ad05350b /system/lib/libdvm.so
W/dalvikvm( 140): DexOpt: --- END 'services.jar' --- status=0x000b, process fai
led
E/dalvikvm( 140): Unable to extract+optimize DEX from '/system/framework/servic
es.jar'
D/dalvikvm( 140): Failed on '/system/framework/services.jar' (boot=1)
D/dalvikvm( 140): VM cleaning up
D/dalvikvm( 140): LinearAlloc 0x0 used 4100 of 4194304 (0%)
and repeats over and over... forever!
I've searched through the forums and on google and nothing relevant came up. Please help!
Ok, tried deleting the Dalvik-Cache from recovery console with no success. Formatted my linux parts and bam! fixed.
If your sdcard is partitioned try wiping your ext3, then trying flashing cm 4.0.4, if it still boot loops then you may need to go back to rc-29 and root again
david1171 said:
If your sdcard is partitioned try wiping your ext3, then trying flashing cm 4.0.4, if it still boot loops then you may need to go back to rc-29 and root again
Click to expand...
Click to collapse
Whats up david, glad you could finally join us. Must be nice to sleep in til noon.
nick_karstedt said:
Ok, tried deleting the Dalvik-Cache from recovery console with no success. Formatted my linux parts and bam! fixed.
Click to expand...
Click to collapse
Ive got the same problem along with several other people on this forum but none of us have been able to sort this out.
So pray tell how do you format linux parts?
Ok, I've had this phone rooted and setup with Cyanogen for months. Probably 7 or 8 months. Last night, it started having some issues, so I opened up the Cyanogen updater and told it to get the latest one, given I was running a rather old version. It downloads it, installs, goes to restart, and gets stuck on the boot screen (in my case, the Rogers screen).
Fast forward to today, I have been flashing and installing all sorts of different firmwares, trying to get it working. 0 luck. Started looking at the log, and this is the output of 4.2.7 with adb's logcat. Any help would be greatly appreciated.
Code:
E/AndroidRuntime( 422): JNI_CreateJavaVM failed
D/AndroidRuntime( 423):
D/AndroidRuntime( 423): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 423): CheckJNI is OFF
E/dalvikvm( 423): Unable to find constructor for StackTraceElement
D/dalvikvm( 423): VM cleaning up
D/dalvikvm( 423): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 423): JNI_CreateJavaVM failed
E/AndroidRuntime( 423): JNI_CreateJavaVM failed
E/vold ( 131): Unable to read framework command (Bad file number)
E/vold ( 131): Error processing framework command (Bad file number)
D/AndroidRuntime( 424):
D/AndroidRuntime( 424): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 424): CheckJNI is OFF
E/dalvikvm( 424): Unable to find constructor for StackTraceElement
D/dalvikvm( 424): VM cleaning up
D/dalvikvm( 424): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 424): JNI_CreateJavaVM failed
E/AndroidRuntime( 424): JNI_CreateJavaVM failed
D/AndroidRuntime( 425):
D/AndroidRuntime( 425): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 425): CheckJNI is OFF
E/dalvikvm( 425): Unable to find constructor for StackTraceElement
D/dalvikvm( 425): VM cleaning up
D/dalvikvm( 425): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 425): JNI_CreateJavaVM failed
E/AndroidRuntime( 425): JNI_CreateJavaVM failed
D/AndroidRuntime( 426):
D/AndroidRuntime( 426): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 426): CheckJNI is OFF
E/dalvikvm( 426): Unable to find constructor for StackTraceElement
D/dalvikvm( 426): VM cleaning up
D/dalvikvm( 426): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 426): JNI_CreateJavaVM failed
E/AndroidRuntime( 426): JNI_CreateJavaVM failed
D/AndroidRuntime( 427):
D/AndroidRuntime( 427): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 427): CheckJNI is OFF
E/dalvikvm( 427): Unable to find constructor for StackTraceElement
D/dalvikvm( 427): VM cleaning up
D/dalvikvm( 427): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 427): JNI_CreateJavaVM failed
E/AndroidRuntime( 427): JNI_CreateJavaVM failed
D/AndroidRuntime( 428):
D/AndroidRuntime( 428): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 428): CheckJNI is OFF
E/dalvikvm( 428): Unable to find constructor for StackTraceElement
D/dalvikvm( 428): VM cleaning up
D/dalvikvm( 428): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 428): JNI_CreateJavaVM failed
E/AndroidRuntime( 428): JNI_CreateJavaVM failed
D/AndroidRuntime( 429):
D/AndroidRuntime( 429): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 429): CheckJNI is OFF
E/dalvikvm( 429): Unable to find constructor for StackTraceElement
D/dalvikvm( 429): VM cleaning up
D/dalvikvm( 429): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 429): JNI_CreateJavaVM failed
E/AndroidRuntime( 429): JNI_CreateJavaVM failed
D/AndroidRuntime( 430):
D/AndroidRuntime( 430): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 430): CheckJNI is OFF
E/dalvikvm( 430): Unable to find constructor for StackTraceElement
D/dalvikvm( 430): VM cleaning up
D/dalvikvm( 430): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 430): JNI_CreateJavaVM failed
E/AndroidRuntime( 430): JNI_CreateJavaVM failed
Etc, etc, etc
what cyanogen rom were you on before you downloaded the rom from the updater?
oshizzle1991 said:
what cyanogen rom were you on before you downloaded the rom from the updater?
Click to expand...
Click to collapse
I don't remember an exact version, I want to say it was 4.1.x
You need to flash the htc recovery image the cyanogen ROM. You will probably need to wipe and format your ext partition also.
cloverdale said:
You need to flash the htc recovery image the cyanogen ROM. You will probably need to wipe and format your ext partition also.
Click to expand...
Click to collapse
Already done that with most of the latest flashes. That would be the one from the signed-dream_devphone_userdebug-ota- ***.zip, correct? If so, I have flashed with 14721, and repartitioned several times with sdparted.
I actually have it now at the "Welcome to T-Mobile G1" screen...only problem is that all the applications are dropping like flies.
Force close on com.android.mms, com.android.phone, come.android.process.gapps
Skipping through that and going to the home screen brings..
Force close on com.google.android.apps.uploader, and no home screen at all. Just a black screen and a notification bar.
Log output as such:
Code:
I/ActivityThread( 1531): Publishing provider com.android.launcher.settings: com.android.launcher.LauncherProvider
I/dalvikvm( 1531): Unknown chunk 0x99b00203 (??), size=-268302586 in aux data area
D/dalvikvm( 155): GC freed 9667 objects / 842832 bytes in 397ms
I/CheckinService( 155): Sending checkin request (15493 bytes)...
D/Zygote ( 130): Process 1525 terminated by signal (11)
I/ActivityManager( 155): Process com.google.process.gapps (pid 1525) has died.
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 87783ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 11887ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 21887ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 31886ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 57778ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 89045409464320ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 67776ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 77776ms
I/DEBUG ( 1535): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1535): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,release-keys'
I/DEBUG ( 1535): pid: 1531, tid: 1531 >>> android.process.acore <<<
I/DEBUG ( 1535): signal 11 (SIGSEGV), fault addr 35434798
I/DEBUG ( 1535): r0 0000004d r1 00000007 r2 d1918f9e r3 3c0081c4
I/DEBUG ( 1535): r4 002c90a0 r5 35434798 r6 ad07ff50 r7 f0020710
I/DEBUG ( 1535): r8 ad00f380 r9 0000bc20 10 4104eb9c fp 00000000
I/DEBUG ( 1535): ip afbc30c8 sp be8ae598 lr afbc1055 pc ad05ecc0 cpsr 20000030
I/ActivityManager( 155): Start proc com.google.process.gapps for restart com.google.process.gapps: pid=1539 uid=10020 gids={3003}
I/ActivityThread( 1539): Publishing provider com.google.settings: com.google.android.providers.settings.GoogleSettingsProvider
I/ActivityThread( 1539): Publishing provider gmail-ls: com.google.android.providers.gmail.MailProvider
I/dalvikvm( 1539): Unknown chunk 0x01190119 (), size=18415897 in aux data area
I/DEBUG ( 1535): #00 pc 0005ecc0 /system/lib/libdvm.so
I/DEBUG ( 1535): #01 pc 0005f3b4 /system/lib/libdvm.so
I/DEBUG ( 1535): #02 pc 000341cc /system/lib/libdvm.so
I/DEBUG ( 1535): #03 pc 0003c540 /system/lib/libdvm.so
I/DEBUG ( 1535): #04 pc 000525b4 /system/lib/libdvm.so
I/DEBUG ( 1535): #05 pc 00013f58 /system/lib/libdvm.so
I/DEBUG ( 1535): #06 pc 00019888 /system/lib/libdvm.so
I/DEBUG ( 1535): #07 pc 00018d5c /system/lib/libdvm.so
I/DEBUG ( 1535): #08 pc 0004d468 /system/lib/libdvm.so
I/DEBUG ( 1535): #09 pc 00054f4c /system/lib/libdvm.so
I/DEBUG ( 1535): #10 pc 00013f58 /system/lib/libdvm.so
I/DEBUG ( 1535): #11 pc 00019888 /system/lib/libdvm.so
I/DEBUG ( 1535): #12 pc 00018d5c /system/lib/libdvm.so
I/DEBUG ( 1535): #13 pc 0004d77c /system/lib/libdvm.so
I/DEBUG ( 1535): #14 pc 0003a74c /system/lib/libdvm.so
I/DEBUG ( 1535): #15 pc 00028374 /system/lib/libandroid_runtime.so
I/DEBUG ( 1535): #16 pc 00028e82 /system/lib/libandroid_runtime.so
I/DEBUG ( 1535): #17 pc 00008c9e /system/bin/app_process
I/DEBUG ( 1535): #18 pc 0000c4c2 /system/lib/libc.so
I/DEBUG ( 1535): #19 pc b00018c6 /system/bin/linker
I/DEBUG ( 1535): stack:
I/DEBUG ( 1535): be8ae558 00000000
I/DEBUG ( 1535): be8ae55c 0001f032 [heap]
I/DEBUG ( 1535): be8ae560 000081a4 /system/bin/app_process
I/DEBUG ( 1535): be8ae564 00000001
I/DEBUG ( 1535): be8ae568 000003e8
I/DEBUG ( 1535): be8ae56c 00002718
I/DEBUG ( 1535): be8ae570 00000000
I/DEBUG ( 1535): be8ae574 d1918f9e
I/DEBUG ( 1535): be8ae578 00000000
I/DEBUG ( 1535): be8ae57c 002c90a0 [heap]
I/DEBUG ( 1535): be8ae580 45414088 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae584 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae588 f0020706
I/DEBUG ( 1535): be8ae58c ad05eca7 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae590 df002777
I/DEBUG ( 1535): be8ae594 e3a070ad
I/DEBUG ( 1535): #00 be8ae598 00000099
I/DEBUG ( 1535): be8ae59c 000000b0
I/DEBUG ( 1535): be8ae5a0 00000002
I/DEBUG ( 1535): be8ae5a4 00000003
I/DEBUG ( 1535): be8ae5a8 f0020706
I/DEBUG ( 1535): be8ae5ac 00000028
I/DEBUG ( 1535): be8ae5b0 00000028
I/DEBUG ( 1535): be8ae5b4 ad06587c /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5b8 45414090 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae5bc ad076eb2 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5c0 002c90a0 [heap]
I/DEBUG ( 1535): be8ae5c4 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5c8 453e4000 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae5cc 002c90a0 [heap]
I/DEBUG ( 1535): be8ae5d0 00030090 [heap]
I/DEBUG ( 1535): be8ae5d4 ad05f3b9 /system/lib/libdvm.so
I/DEBUG ( 1535): #01 be8ae5d8 00000000
I/DEBUG ( 1535): be8ae5dc 00000000
I/DEBUG ( 1535): be8ae5e0 00000000
I/DEBUG ( 1535): be8ae5e4 00030090 [heap]
I/DEBUG ( 1535): be8ae5e8 002c90a0 [heap]
I/DEBUG ( 1535): be8ae5ec 00000000
I/DEBUG ( 1535): be8ae5f0 00000400
I/DEBUG ( 1535): be8ae5f4 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5f8 be8ae610 [stack]
I/DEBUG ( 1535): be8ae5fc 00000028
I/DEBUG ( 1535): be8ae600 be8ae6a8 [stack]
I/DEBUG ( 1535): be8ae604 ad0341d1 /system/lib/libdvm.so
I/CheckinService( 155): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
I/ActivityManager( 155): Process android.process.acore (pid 1531) has died.
I/ActivityManager( 155): Start proc android.process.acore for restart android.process.acore: pid=1545 uid=10008 gids={3003, 3002, 3001, 1006, 1015}
D/Zygote ( 130): Process 1531 terminated by signal (11)
I/DEBUG ( 1535): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1535): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,release-keys'
I/DEBUG ( 1535): pid: 1539, tid: 1539 >>> com.google.process.gapps <<<
I/DEBUG ( 1535): signal 11 (SIGSEGV), fault addr 45d67248
I/DEBUG ( 1535): r0 0000004b r1 00000007 r2 d1918f9e r3 0046404a
I/DEBUG ( 1535): r4 0011b998 r5 45d67248 r6 ad07ff50 r7 01190128
I/DEBUG ( 1535): r8 ad00f380 r9 0000bc20 10 4104eb9c fp 00000000
I/DEBUG ( 1535): ip afbc30c8 sp be8ae598 lr afbc1055 pc ad05ecc0 cpsr 00000030
I/ActivityThread( 1545): Publishing provider com.android.globalsearch.stats: com.android.globalsearch.StatsProvider
I/ActivityThread( 1545): Publishing provider contacts;call_log: com.android.providers.contacts.GoogleContactsProvider
I/DEBUG ( 1535): #00 pc 0005ecc0 /system/lib/libdvm.so
I/DEBUG ( 1535): #01 pc 0005f3b4 /system/lib/libdvm.so
I/DEBUG ( 1535): #02 pc 000341cc /system/lib/libdvm.so
I/DEBUG ( 1535): #03 pc 0003c540 /system/lib/libdvm.so
I/DEBUG ( 1535): #04 pc 000525b4 /system/lib/libdvm.so
I/DEBUG ( 1535): #05 pc 00013f58 /system/lib/libdvm.so
I/DEBUG ( 1535): #06 pc 00019888 /system/lib/libdvm.so
I/DEBUG ( 1535): #07 pc 00018d5c /system/lib/libdvm.so
I/DEBUG ( 1535): #08 pc 0004d468 /system/lib/libdvm.so
I/DEBUG ( 1535): #09 pc 00054f4c /system/lib/libdvm.so
I/DEBUG ( 1535): #10 pc 00013f58 /system/lib/libdvm.so
I/DEBUG ( 1535): #11 pc 00019888 /system/lib/libdvm.so
I/DEBUG ( 1535): #12 pc 00018d5c /system/lib/libdvm.so
I/DEBUG ( 1535): #13 pc 0004d77c /system/lib/libdvm.so
I/DEBUG ( 1535): #14 pc 0003a74c /system/lib/libdvm.so
I/ActivityThread( 1545): Publishing provider applications: com.android.providers.applications.ApplicationsProvider
I/DEBUG ( 1535): #15 pc 00028374 /system/lib/libandroid_runtime.so
I/DEBUG ( 1535): #16 pc 00028e82 /system/lib/libandroid_runtime.so
I/DEBUG ( 1535): #17 pc 00008c9e /system/bin/app_process
I/DEBUG ( 1535): #18 pc 0000c4c2 /system/lib/libc.so
I/DEBUG ( 1535): #19 pc b00018c6 /system/bin/linker
I/DEBUG ( 1535): stack:
I/DEBUG ( 1535): be8ae558 00000000
I/DEBUG ( 1535): be8ae55c 0001f04d [heap]
I/DEBUG ( 1535): be8ae560 000081a4 /system/bin/app_process
I/DEBUG ( 1535): be8ae564 00000001
I/DEBUG ( 1535): be8ae568 000003e8
I/DEBUG ( 1535): be8ae56c 00002724
I/DEBUG ( 1535): be8ae570 00000000
I/DEBUG ( 1535): be8ae574 d1918f9e
I/DEBUG ( 1535): be8ae578 00000000
I/DEBUG ( 1535): be8ae57c 0011b998 [heap]
I/DEBUG ( 1535): be8ae580 44bd7120 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae584 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae588 01190119
I/DEBUG ( 1535): be8ae58c ad05eca7 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae590 df002777
I/DEBUG ( 1535): be8ae594 e3a070ad
I/DEBUG ( 1535): #00 be8ae598 00000001
I/DEBUG ( 1535): be8ae59c 00000019
I/DEBUG ( 1535): be8ae5a0 00000001
I/DEBUG ( 1535): be8ae5a4 00000019
I/DEBUG ( 1535): be8ae5a8 01190119
I/DEBUG ( 1535): be8ae5ac 0000001f
I/DEBUG ( 1535): be8ae5b0 0000001f
I/DEBUG ( 1535): be8ae5b4 ad06587c /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5b8 44bd7128 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae5bc ad076eb2 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5c0 0011b998 [heap]
I/DEBUG ( 1535): be8ae5c4 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5c8 44b94000 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae5cc 0011b998 [heap]
I/DEBUG ( 1535): be8ae5d0 00043128 [heap]
I/DEBUG ( 1535): be8ae5d4 ad05f3b9 /system/lib/libdvm.so
I/DEBUG ( 1535): #01 be8ae5d8 00000000
I/DEBUG ( 1535): be8ae5dc 00000000
I/DEBUG ( 1535): be8ae5e0 00000000
I/DEBUG ( 1535): be8ae5e4 00043128 [heap]
I/DEBUG ( 1535): be8ae5e8 0011b998 [heap]
I/DEBUG ( 1535): be8ae5ec 00000000
I/DEBUG ( 1535): be8ae5f0 00000400
I/DEBUG ( 1535): be8ae5f4 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5f8 be8ae610 [stack]
I/DEBUG ( 1535): be8ae5fc 0000001f
I/DEBUG ( 1535): be8ae600 be8ae6a8 [stack]
I/DEBUG ( 1535): be8ae604 ad0341d1 /system/lib/libdvm.so
Try again in this order:
Remove the sdcard (with the phone off) and format with gparted (do a fresh format at least to the ext). Place the sdcard in the phone and boot to recovery. Wipe everything, then flash the htc recovery, then WITHOUT A REBOOT, flash cyanogen.
I had something similar happen to me last week, and I had to repeat the above a few times, but it eventually worked.
cloverdale said:
Try again in this order:
Remove the sdcard (with the phone off) and format with gparted (do a fresh format at least to the ext). Place the sdcard in the phone and boot to recovery. Wipe everything, then flash the htc recovery, then WITHOUT A REBOOT, flash cyanogen.
I had something similar happen to me last week, and I had to repeat the above a few times, but it eventually worked.
Click to expand...
Click to collapse
Is there a huge difference if I mount the sdcard from the phone (via the console and echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) vs directly in the computer (given that the phone is the only way I currently have to access the sdcard.
Regardless, going to give your instructions a few steps right now with my method of loading it up, just to test. Wish me luck.
Result is the same, stuff dies and blank, black, useless home screen. Another interesting tidbit to this story is the fact that even though I am connected to a network, and show as having a full signal and 3G connection....no outgoing data seems to be going on.
Well, another update, but a bit of a sad one, in my opinion.
I got it working. But not with Cyanogen. I used this rom, and it installed and worked fine.
This is strange, it is way beyond me why this would be happening to you. lbcoder is one of the only people I can think of on here that would probably know.
Hello,
since the weekend m G1 (with Cyanogen 4.2.13) is suffering some bad errors.
It happens, that it just freezes.
activating adb logcat it gives me this output (which gets repeated in a two seconds cycle).
D/AndroidRuntime( 1476):
D/AndroidRuntime( 1476): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1476): CheckJNI is OFF
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/core.jar
(/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/core.j
ar'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/ext.jar
(/data/dalvik-cache/[email protected][email protected]@classes.dex)
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/ext.ja
r'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/framewor
k.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/framew
ork.jar'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/android.
policy.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/androi
d.policy.jar'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/services
.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/servic
es.jar'
E/dalvikvm( 1476): ERROR: no valid entries found in bootclasspath '/system/frame
work/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/
framework/android.policy.jar:/system/framework/services.jar'
D/dalvikvm( 1476): VM cleaning up
D/dalvikvm( 1476): LinearAlloc 0x0 used 4100 of 5242880 (0%)
W/dalvikvm( 1476): JNI_CreateJavaVM failed
E/AndroidRuntime( 1476): JNI_CreateJavaVM failed
Click to expand...
Click to collapse
Does anyone have a hint whats failing here?
-Radioactive Man
Just a guess, but probably an I/O error.
opt header write failed: I/O error
Click to expand...
Click to collapse
and what does it mean? broken sdcard? broken internal memory? something else broken?
Now I get another output:
D/AndroidRuntime( 1392):
D/AndroidRuntime( 1392): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1392): CheckJNI is OFF
I/DEBUG ( 1342): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1342): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,re
lease-keys'
I/DEBUG ( 1342): pid: 1392, tid: 1392 >>> zygote <<<
I/DEBUG ( 1342): signal 7 (SIGBUS), fault addr 41a2633b
I/DEBUG ( 1342): r0 00015d80 r1 41a2633b r2 00015d18 r3 00352313
I/DEBUG ( 1342): r4 ad07ff50 r5 00015d80 r6 41746010 r7 00000000
I/DEBUG ( 1342): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 1342): ip ad080214 sp be94b828 lr ad058471 pc ad057bd6 cpsr 20000030
I/DEBUG ( 1342): #00 pc 00057bd6 /system/lib/libdvm.so
I/DEBUG ( 1342): #01 pc 0005846c /system/lib/libdvm.so
I/DEBUG ( 1342): #02 pc 0005867e /system/lib/libdvm.so
I/DEBUG ( 1342): #03 pc 00040690 /system/lib/libdvm.so
I/DEBUG ( 1342): #04 pc 0003681c /system/lib/libdvm.so
I/DEBUG ( 1342): #05 pc 000384b2 /system/lib/libdvm.so
I/DEBUG ( 1342): #06 pc 00028d7e /system/lib/libandroid_runtime.so
I/DEBUG ( 1342): #07 pc 00008c9e /system/bin/app_process
I/DEBUG ( 1342): #08 pc 0000c4c2 /system/lib/libc.so
I/DEBUG ( 1342): #09 pc b00018c6 /system/bin/linker
I/DEBUG ( 1342): stack:
I/DEBUG ( 1342): be94b7e8 000081a4 /system/bin/app_process
I/DEBUG ( 1342): be94b7ec 00000001
I/DEBUG ( 1342): be94b7f0 00000000
I/DEBUG ( 1342): be94b7f4 00000000
I/DEBUG ( 1342): be94b7f8 afe3bc10
I/DEBUG ( 1342): be94b7fc afe0f370 /system/lib/libc.so
I/DEBUG ( 1342): be94b800 00000000
I/DEBUG ( 1342): be94b804 afe0f280 /system/lib/libc.so
I/DEBUG ( 1342): be94b808 41a5f3b0 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1342): be94b80c ad05f32f /system/lib/libdvm.so
I/DEBUG ( 1342): be94b810 00001df2
I/DEBUG ( 1342): be94b814 00001fff
I/DEBUG ( 1342): be94b818 416d4028 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1342): be94b81c ad0735bc /system/lib/libdvm.so
I/DEBUG ( 1342): be94b820 df002777
I/DEBUG ( 1342): be94b824 e3a070ad
I/DEBUG ( 1342): #00 be94b828 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b82c 00015d80 [heap]
I/DEBUG ( 1342): be94b830 ad0735bc /system/lib/libdvm.so
I/DEBUG ( 1342): be94b834 ad056843 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b838 00000002
I/DEBUG ( 1342): be94b83c ad06587c /system/lib/libdvm.so
I/DEBUG ( 1342): be94b840 be94b874 [stack]
I/DEBUG ( 1342): be94b844 ad074a04 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b848 00015a60 [heap]
I/DEBUG ( 1342): be94b84c 00000000
I/DEBUG ( 1342): be94b850 0000bc20 [heap]
I/DEBUG ( 1342): be94b854 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b858 00015d80 [heap]
I/DEBUG ( 1342): be94b85c ad058471 /system/lib/libdvm.so
I/DEBUG ( 1342): #01 be94b860 00015a58 [heap]
I/DEBUG ( 1342): be94b864 00015a60 [heap]
I/DEBUG ( 1342): be94b868 ad0735bc /system/lib/libdvm.so
I/DEBUG ( 1342): be94b86c 00000000
I/DEBUG ( 1342): be94b870 ad06587c /system/lib/libdvm.so
I/DEBUG ( 1342): be94b874 41746010 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1342): be94b878 000111b8 [heap]
I/DEBUG ( 1342): be94b87c ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b880 00000354
I/DEBUG ( 1342): be94b884 0000a9c0 [heap]
I/DEBUG ( 1342): be94b888 fffec080
I/DEBUG ( 1342): be94b88c ad058683 /system/lib/libdvm.so
Click to expand...
Click to collapse
what is happening with my phone?
Have you messed with anything lately, new boot image, removed system apps, went to an eclair ROM and back, metamorphed, themed, etc?
cloverdale said:
Have you messed with anything lately, new boot image, removed system apps, went to an eclair ROM and back, metamorphed, themed, etc?
Click to expand...
Click to collapse
Nothing like that. I only have installed Cyanogen and a few apps from market. Nothing special as I think.
I have had this happen in only three cases:
1.) I tried adding framework that was not compatible with my ROM.
2.) I tried adding a launcher that was not compatible.
3.) I tried coming to a new ROM without a fresh format of my ext partition on my sdcard.
In all cases a fresh wipe of the phone and re-format of the sd ext partition fixed it.
cloverdale said:
I have had this happen in only three cases:
1.) I tried adding framework that was not compatible with my ROM.
2.) I tried adding a launcher that was not compatible.
3.) I tried coming to a new ROM without a fresh format of my ext partition on my sdcard.
In all cases a fresh wipe of the phone and re-format of the sd ext partition fixed it.
Click to expand...
Click to collapse
Might be a theme he's using that's not for the version or a metamorph that's for a older cyan.I remember I had something similar to this.
Ace42 said:
Might be a theme he's using that's not for the version or a metamorph that's for a older cyan.I remember I had something similar to this.
Click to expand...
Click to collapse
Good call. I second this.
Ace42 said:
Might be a theme he's using that's not for the version or a metamorph that's for a older cyan.I remember I had something similar to this.
Click to expand...
Click to collapse
well, I doubt it as I have never installed any theme so far. I will see if it happens again and if so I will try to make a fresh reinstall.
I've experienced a huge problem with my G1. I always liked to play with it, so I rooted it instatly after buying it. Now I have Haykuro, Amon_Ra recovery, .26i radio. I flashed new ROM every week and everything was OK. Until now. Something happened and almost every ROM is getting bootloop! Some hangs on G1 splash, some on their bootscreen. I tried SuperF, SuperD, CM6 RC3, Donut AOSP TheOfficial, Chromatic, SpeedTeam Froyo, SuperE, Dwang, Froyo AOSP and more, but only SuperE and FroyoAOSP booted (but only once - when I turn them off they never boot again). Before every flash I was doing full wipe, sometimes also a fastboot system -w.
Fastboot and recovery working. Tried to reflash radio and recovery, to format SD Card - nothing helped.
I wonder if I should try to unroot and then root again? Did anyone ever encountered this strange situation? Everything was all right and then BANG! everything crashes ;/.
I am always wathing logcat and discovered one interesting thing - few ROMs hang in the same place:
Code:
D/AndroidRuntime( 731):
D/AndroidRuntime( 731): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 731): CheckJNI is OFF
D/AndroidRuntime( 731): --- registering native functions ---
I/Zygote ( 731): Preloading classes...
D/dalvikvm( 731): GC freed 800 objects / 44048 bytes in 6ms
I/DEBUG ( 699): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 699): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 699): pid: 731, tid: 731 >>> zygote <<<
I/DEBUG ( 699): signal 11 (SIGSEGV), fault addr 0000001e
I/DEBUG ( 699): r0 08000000 r1 bea5c5ec r2 bea5c5ec r3 bea5c604
I/DEBUG ( 699): r4 00000200 r5 bea5c604 r6 00000000 r7 00000001
I/DEBUG ( 699): r8 bea5c5ec r9 000904e0 10 bea5c604 fp bea5c5bc
I/DEBUG ( 699): ip ad4abe54 sp bea5c508 lr ad48f551 pc ad47070a cpsr 000
00030
I/DEBUG ( 699): #00 pc 0007070a /system/lib/libicui18n.so
I/DEBUG ( 699): #01 lr ad48f551 /system/lib/libicui18n.so
I/DEBUG ( 699): stack:
I/DEBUG ( 699): bea5c4c8 0007b228 [heap]
I/DEBUG ( 699): bea5c4cc 000001b4
I/DEBUG ( 699): bea5c4d0 000000dc
I/DEBUG ( 699): bea5c4d4 00002bcc
I/DEBUG ( 699): bea5c4d8 00000001
I/DEBUG ( 699): bea5c4dc afe0b70f /system/lib/libc.so
I/DEBUG ( 699): bea5c4e0 afe39dd4 /system/lib/libc.so
I/DEBUG ( 699): bea5c4e4 00000034
I/DEBUG ( 699): bea5c4e8 40031fe0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c4ec 00000004
I/DEBUG ( 699): bea5c4f0 00000001
I/DEBUG ( 699): bea5c4f4 00000001
I/DEBUG ( 699): bea5c4f8 bea5c510 [stack]
I/DEBUG ( 699): bea5c4fc 00000000
I/DEBUG ( 699): bea5c500 df002777
I/DEBUG ( 699): bea5c504 e3a070ad
I/DEBUG ( 699): #00 bea5c508 ad084aa8 /system/lib/libdvm.so
I/DEBUG ( 699): bea5c50c 00000200
I/DEBUG ( 699): bea5c510 ad5c1b50 /system/lib/libicuuc.so
I/DEBUG ( 699): bea5c514 00000001
I/DEBUG ( 699): bea5c518 00000001
I/DEBUG ( 699): bea5c51c 0007b228 [heap]
I/DEBUG ( 699): bea5c520 ad080008 /system/lib/libdvm.so
I/DEBUG ( 699): bea5c524 40031fb0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c528 00000007
I/DEBUG ( 699): bea5c52c 40031fb0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c530 40031fb0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c534 bea5c620 [stack]
I/DEBUG ( 699): bea5c538 4104ee54
I/DEBUG ( 699): bea5c53c 4104ee44
I/DEBUG ( 699): bea5c540 00000000
I/DEBUG ( 699): bea5c544 40031fe0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c548 0000a9c8 [heap]
I/DEBUG ( 699): bea5c54c 00000001
Maybe this is the key? Some hangs in other place, I will try to catch it and post here too. Please, help! I don't want to lose my G1...
If there was someone with same problem, please, post me a link to thread.
OK, I got second place when ROM hangs. Got cyan 5.07 to work and then it hanged after second boot. This is where it was looping:
Code:
D/libEGL ( 255): Setting TLS: 0xafe43b6c to 0xac70a2ec
D/AndroidRuntime( 255):
D/AndroidRuntime( 255): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 255): CheckJNI is OFF
D/AndroidRuntime( 255): --- registering native functions ---
E/JNIHelp ( 255): Native registration unable to find class 'com/android/interna
l/os/RuntimeInit'
E/AndroidRuntime( 255): Unable to register all android natives
I/ServiceManager( 91): service 'media.audio_flinger' died
I/ServiceManager( 91): service 'media.player' died
I/ServiceManager( 91): service 'media.camera' died
I/ServiceManager( 91): service 'media.audio_policy' died
D/libEGL ( 256): Setting TLS: 0xafe43b6c to 0xac70a2ec
I/ ( 256): ServiceManager: 0xad08
I/HTC Acoustic( 256): libhtc_acoustic.so version 1.0.1.2.
E/HTC Acoustic( 256): Fail to open /system/etc/AudioPara_Era.csv -1.
I/HTC Acoustic( 256): open /system/etc/AudioPara4.csv success.
I/HTC Acoustic( 256): acoustic table version: Sapphire_VODAFONE_20090305
I/HTC Acoustic( 256): read_audio_para_from_file success.
I/HTC Acoustic( 256): get_audpp_filter
I/HTC Acoustic( 256): open /system/etc/AudioFilter.csv success.
I/HTC Acoustic( 256): ADRC Filter ADRC FLAG = ffff.
I/HTC Acoustic( 256): ADRC Filter COMP THRESHOLD = 2600.
I/HTC Acoustic( 256): ADRC Filter COMP SLOPE = b333.
I/HTC Acoustic( 256): ADRC Filter COMP RMS TIME = 106.
I/HTC Acoustic( 256): ADRC Filter COMP ATTACK[0] = 7f7d.
I/HTC Acoustic( 256): ADRC Filter COMP ATTACK[1] = 3096.
I/HTC Acoustic( 256): ADRC Filter COMP RELEASE[0] = 7ff7.
I/HTC Acoustic( 256): ADRC Filter COMP RELEASE[1] = 4356.
I/HTC Acoustic( 256): ADRC Filter COMP DELAY = 16.
I/HTC Acoustic( 256): EQ flag = 00.
I/HTC Acoustic( 256): get_audpre_filter
I/HTC Acoustic( 256): open /system/etc/AudioPreProcess.csv success.
D/AudioHardwareMSM72XX( 256): mNumSndEndpoints = 67
D/AudioHardwareMSM72XX( 256): BT MATCH HANDSET
D/AudioHardwareMSM72XX( 256): BT MATCH SPEAKER
D/AudioHardwareMSM72XX( 256): BT MATCH HEADSET
D/AudioHardwareMSM72XX( 256): BT MATCH BT
D/AudioHardwareMSM72XX( 256): BT MATCH CARKIT
D/AudioHardwareMSM72XX( 256): BT MATCH TTY_FULL
D/AudioHardwareMSM72XX( 256): BT MATCH TTY_VCO
D/AudioHardwareMSM72XX( 256): BT MATCH TTY_HCO
D/AudioHardwareMSM72XX( 256): BT MATCH NO_MIC_HEADSET
D/AudioHardwareMSM72XX( 256): BT MATCH FM_HEADSET
D/AudioHardwareMSM72XX( 256): BT MATCH HEADSET_AND_SPEAKER
D/AudioHardwareMSM72XX( 256): BT MATCH FM_SPEAKER
D/AudioHardwareMSM72XX( 256): BT MATCH BT_EC_OFF
D/AudioHardwareMSM72XX( 256): BT MATCH CURRENT
D/AudioHardwareMSM72XX( 256): BT MATCH BT_EC_OFF
D/AudioHardwareInterface( 256): setMode(NORMAL)
I/AudioHardwareMSM72XX( 256): Set master volume to 5.
I/CameraService( 256): CameraService started: pid=256
I/AudioFlinger( 256): AudioFlinger's thread 0xd8a8 ready to run
I/AudioHardwareMSM72XX( 256): Routing audio to Speakerphone
D/HTC Acoustic( 256): msm72xx_enable_audpp: 0x0001
D/AudioHardwareMSM72XX( 256): setVoiceVolume(1.000000)
I/AudioHardwareMSM72XX( 256): Setting in-call volume to 5 (available range is 0
to 5)
No one knows what is going on? No one to help? Please, I'm going nuts because of this, I really don't know what's going on. Almost every ROM hangs in same 2 places, someone has to know what's going on!
WOOPS, double post. Sorry, i thought that it will automatically merge two posts in one.
EDIT: CM6 RC3 boots all right. I can even reboot it. But still, this situation is not normal .
Dont let this piss you off but have you tried a new SDcard?
I have had trouble going from Froyo to Cupcake and vice versa --- they always involve a fresh new SDcard and I really do not know why.
I want to try something... what if I send you some nandroid backups would you want to try fastbooting them in? That may work and I've got only so many gigs of nandroids saved from the past year.
Tried another SD Card, but nope, it's not it. Same results: CM6 RC3 is booting well while everything else is looping. Tried to apply MTD Part Hack (don't know why, I thought that it might help and if it is not working I will have a reason to ask Firerat what's going on ) and loop in SuperD boot changed a little, now it is like this:
Code:
v/0 (deleted)
I/DEBUG ( 132): bedea848 0000bc48 [heap]
I/DEBUG ( 132): bedea84c 0000a9c0 [heap]
I/DEBUG ( 132): bedea850 0000bc48 [heap]
I/DEBUG ( 132): bedea854 0000a9c0 [heap]
I/DEBUG ( 132): bedea858 df002777
I/DEBUG ( 132): bedea85c e3a070ad
I/DEBUG ( 132): #00 bedea860 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bedea864 0000bc48 [heap]
I/DEBUG ( 132): bedea868 0000a9c0 [heap]
I/DEBUG ( 132): bedea86c ad036569 /system/lib/libdvm.so
I/DEBUG ( 132): bedea870 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bedea874 ad080a54 /system/lib/libdvm.so
I/DEBUG ( 132): bedea878 0000a9c0 [heap]
I/DEBUG ( 132): bedea87c ad036923 /system/lib/libdvm.so
I/DEBUG ( 132): bedea880 00000000
I/DEBUG ( 132): bedea884 00000000
I/DEBUG ( 132): bedea888 0000036c
I/DEBUG ( 132): bedea88c ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bedea890 bedea970 [stack]
I/DEBUG ( 132): bedea894 0000a9c0 [heap]
I/DEBUG ( 132): bedea898 0000a978 [heap]
I/DEBUG ( 132): bedea89c ad03854f /system/lib/libdvm.so
I/DEBUG ( 132): bedea8a0 00000003
I/DEBUG ( 132): bedea8a4 ad080c00 /system/lib/libdvm.so
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 179, tid: 179 >>> /system/bin/rild <<<
I/DEBUG ( 132): signal 7 (SIGBUS), fault addr 80004160
I/DEBUG ( 132): r0 80004160 r1 00000000 r2 00000e60 r3 00000000
I/DEBUG ( 132): r4 00000000 r5 00000000 r6 00000000 r7 00000000
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip 00000000 sp befff738 lr 00000000 pc b000268c cpsr 200
00010
I/DEBUG ( 132): #00 pc b000268c /system/bin/linker
I/DEBUG ( 132): #01 pc b00011e2 /system/bin/linker
I/DEBUG ( 132): #02 pc b0001464 /system/bin/linker
I/DEBUG ( 132): #03 pc b0001560 /system/bin/linker
I/DEBUG ( 132): #04 pc b0001cec /system/bin/linker
I/DEBUG ( 132): #05 pc 00008bee /system/bin/rild
I/DEBUG ( 132): #06 pc 0000c572 /system/lib/libc.so
I/DEBUG ( 132): #07 pc b00018c6 /system/bin/linker
I/DEBUG ( 132): stack:
I/DEBUG ( 132): befff6f8 b00107e0 /system/bin/linker
I/DEBUG ( 132): befff6fc 000002ff
I/DEBUG ( 132): befff700 00000000
I/DEBUG ( 132): befff704 00000000
I/DEBUG ( 132): befff708 b000d288 /system/bin/linker
I/DEBUG ( 132): befff70c befff6ac [stack]
I/DEBUG ( 132): befff710 00000000
I/DEBUG ( 132): befff714 00000000
I/DEBUG ( 132): befff718 00000000
I/DEBUG ( 132): befff71c ffffffff
I/DEBUG ( 132): befff720 00000000
I/DEBUG ( 132): befff724 b00041c1 /system/bin/linker
I/DEBUG ( 132): befff728 00000004
I/DEBUG ( 132): befff72c 00000003
I/DEBUG ( 132): befff730 df002777
I/DEBUG ( 132): befff734 e3a070ad
I/DEBUG ( 132): #00 befff738 80004160 /system/lib/libhtc_ril.so
I/DEBUG ( 132): befff73c b0017690
I/DEBUG ( 132): befff740 80004000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): befff744 b0011a3c
I/DEBUG ( 132): befff748 b0010448 /system/bin/linker
I/DEBUG ( 132): befff74c b00011e5 /system/bin/linker
I/DEBUG ( 132): #01 befff750 00000003
I/DEBUG ( 132): befff754 00004000
I/DEBUG ( 132): befff758 b000ca4b /system/bin/linker
I/DEBUG ( 132): befff75c b000c760 /system/bin/linker
I/DEBUG ( 132): befff760 00000000
I/DEBUG ( 132): befff764 00000000
I/DEBUG ( 132): befff768 00000000
I/DEBUG ( 132): befff76c b0011ad0
I/DEBUG ( 132): befff770 00000160
I/DEBUG ( 132): befff774 80004000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): befff778 80000000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): befff77c 00004000
I/DEBUG ( 132): befff780 b001761c
I/DEBUG ( 132): befff784 00000002
I/DEBUG ( 132): befff788 00000003
I/DEBUG ( 132): befff78c b0011b34
I/DEBUG ( 132): befff790 b0011b38
I/DEBUG ( 132): befff794 b0011ad4
I/DEBUG ( 132): befff798 befff99c [stack]
I/DEBUG ( 132): befff79c b0010448 /system/bin/linker
I/DEBUG ( 132): befff7a0 b0011a3c
I/DEBUG ( 132): befff7a4 00000003
I/DEBUG ( 132): befff7a8 b0011ac8
I/DEBUG ( 132): befff7ac b0001469 /system/bin/linker
I/ ( 180): ServiceManager: 0xac38
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 180, tid: 180 >>> /system/bin/mediaserver <<<
I/DEBUG ( 132): signal 7 (SIGBUS), fault addr 80604164
I/DEBUG ( 132): r0 80604164 r1 00000000 r2 00000e80 r3 c0000000
I/DEBUG ( 132): r4 00000000 r5 00000000 r6 00000000 r7 00000000
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip 00000000 sp be822ab8 lr 00000000 pc b0002668 cpsr a00
00010
I/DEBUG ( 132): #00 pc b0002668 /system/bin/linker
I/DEBUG ( 132): #01 pc b00011e2 /system/bin/linker
I/DEBUG ( 132): #02 pc b0001464 /system/bin/linker
I/DEBUG ( 132): #03 pc b0001560 /system/bin/linker
I/DEBUG ( 132): #04 pc b0001cec /system/bin/linker
I/DEBUG ( 132): #05 pc 0000481a /system/lib/libaudio.so
I/DEBUG ( 132): #06 pc 00004a32 /system/lib/libaudio.so
I/DEBUG ( 132): #07 pc 000051a8 /system/lib/libaudio.so
I/DEBUG ( 132): #08 pc 000183ec /system/lib/libaudioflinger.so
I/DEBUG ( 132): #09 pc 00018626 /system/lib/libaudioflinger.so
I/DEBUG ( 132): #10 pc 0000873e /system/bin/mediaserver
I/DEBUG ( 132): #11 pc 0000c572 /system/lib/libc.so
I/DEBUG ( 132): #12 pc b00018c6 /system/bin/linker
I/DEBUG ( 132): stack:
I/DEBUG ( 132): be822a78 b0013e54
I/DEBUG ( 132): be822a7c be822a94 [stack]
I/DEBUG ( 132): be822a80 a7a043c9 /system/lib/libopencore_net_support.s
o
I/DEBUG ( 132): be822a84 b0010ae0 /system/bin/linker
I/DEBUG ( 132): be822a88 be822b04 [stack]
I/DEBUG ( 132): be822a8c 02ff0fa4
I/DEBUG ( 132): be822a90 a600bb68 /system/lib/libopencore_common.so
I/DEBUG ( 132): be822a94 b0000495 /system/bin/linker
I/DEBUG ( 132): be822a98 00000000
I/DEBUG ( 132): be822a9c ffffffff
I/DEBUG ( 132): be822aa0 00000000
I/DEBUG ( 132): be822aa4 b00041c1 /system/bin/linker
I/DEBUG ( 132): be822aa8 00000004
I/DEBUG ( 132): be822aac 00000007
I/DEBUG ( 132): be822ab0 df002777
I/DEBUG ( 132): be822ab4 e3a070ad
I/DEBUG ( 132): #00 be822ab8 80604164 /system/lib/libhtc_acoustic.so
I/DEBUG ( 132): be822abc b0017690
I/DEBUG ( 132): be822ac0 80604000 /system/lib/libhtc_acoustic.so
I/DEBUG ( 132): be822ac4 b0014084
I/DEBUG ( 132): be822ac8 b0010448 /system/bin/linker
I/DEBUG ( 132): be822acc b00011e5 /system/bin/linker
I/DEBUG ( 132): #01 be822ad0 00000007
I/DEBUG ( 132): be822ad4 00004000
I/DEBUG ( 132): be822ad8 be822ae8 [stack]
I/DEBUG ( 132): be822adc b00009ab /system/bin/linker
I/DEBUG ( 132): be822ae0 00000000
I/DEBUG ( 132): be822ae4 00000000
I/DEBUG ( 132): be822ae8 00000000
I/DEBUG ( 132): be822aec b0014118
I/DEBUG ( 132): be822af0 00000164
I/DEBUG ( 132): be822af4 80604000 /system/lib/libhtc_acoustic.so
I/DEBUG ( 132): be822af8 80600000 /system/lib/libhtc_acoustic.so
I/DEBUG ( 132): be822afc 00004000
I/DEBUG ( 132): be822b00 b001761c
I/DEBUG ( 132): be822b04 00000002
I/DEBUG ( 132): be822b08 00000007
I/DEBUG ( 132): be822b0c b001417c
I/DEBUG ( 132): be822b10 b0014180
I/DEBUG ( 132): be822b14 b001411c
I/DEBUG ( 132): be822b18 00000000
I/DEBUG ( 132): be822b1c b0010448 /system/bin/linker
I/DEBUG ( 132): be822b20 b0014084
I/DEBUG ( 132): be822b24 00000007
I/DEBUG ( 132): be822b28 b0014110
I/DEBUG ( 132): be822b2c b0001469 /system/bin/linker
D/AndroidRuntime( 181):
D/AndroidRuntime( 181): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 181): CheckJNI is OFF
D/dalvikvm( 181): Unable to stat classpath element '/system/framework/com.htc.f
ramework.jar'
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 181, tid: 181 >>> zygote <<<
I/DEBUG ( 132): signal 11 (SIGSEGV), fault addr 00000000
I/DEBUG ( 132): r0 00000000 r1 00000000 r2 ffffff08 r3 00000000
I/DEBUG ( 132): r4 000000f8 r5 00000000 r6 00000000 r7 00000007
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip ad080214 sp bed82860 lr ad20cae9 pc ad213d62 cpsr 400
00030
I/DEBUG ( 132): #00 pc 00013d62 /system/lib/libnativehelper.so
I/DEBUG ( 132): #01 lr ad20cae9 /system/lib/libnativehelper.so
I/DEBUG ( 132): stack:
I/DEBUG ( 132): bed82820 ad233ff4 /system/lib/libnativehelper.so
I/DEBUG ( 132): bed82824 0000001d
I/DEBUG ( 132): bed82828 ad233120 /system/lib/libnativehelper.so
I/DEBUG ( 132): bed8282c 00000ed4
I/DEBUG ( 132): bed82830 0000a9c0 [heap]
I/DEBUG ( 132): bed82834 ad233120 /system/lib/libnativehelper.so
I/DEBUG ( 132): bed82838 ad235670 /system/lib/libnativehelper.so
I/DEBUG ( 132): bed8283c ad21543d /system/lib/libnativehelper.so
I/DEBUG ( 132): bed82840 0000a9c0 [heap]
I/DEBUG ( 132): bed82844 4000fd18 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 132): bed82848 0000bc48 [heap]
I/DEBUG ( 132): bed8284c 0000a9c0 [heap]
I/DEBUG ( 132): bed82850 0000bc48 [heap]
I/DEBUG ( 132): bed82854 0000a9c0 [heap]
I/DEBUG ( 132): bed82858 df002777
I/DEBUG ( 132): bed8285c e3a070ad
I/DEBUG ( 132): #00 bed82860 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bed82864 0000bc48 [heap]
I/DEBUG ( 132): bed82868 0000a9c0 [heap]
I/DEBUG ( 132): bed8286c ad036569 /system/lib/libdvm.so
I/DEBUG ( 132): bed82870 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bed82874 ad080a54 /system/lib/libdvm.so
I/DEBUG ( 132): bed82878 0000a9c0 [heap]
I/DEBUG ( 132): bed8287c ad036923 /system/lib/libdvm.so
I/DEBUG ( 132): bed82880 00000000
I/DEBUG ( 132): bed82884 00000000
I/DEBUG ( 132): bed82888 0000036c
I/DEBUG ( 132): bed8288c ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bed82890 bed82970 [stack]
I/DEBUG ( 132): bed82894 0000a9c0 [heap]
I/DEBUG ( 132): bed82898 0000a978 [heap]
I/DEBUG ( 132): bed8289c ad03854f /system/lib/libdvm.so
I/DEBUG ( 132): bed828a0 00000003
I/DEBUG ( 132): bed828a4 ad080c00 /system/lib/libdvm.so
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 182, tid: 182 >>> /system/bin/rild <<<
I/DEBUG ( 132): signal 7 (SIGBUS), fault addr 80004160
I/DEBUG ( 132): r0 80004160 r1 00000000 r2 00000e60 r3 00000000
I/DEBUG ( 132): r4 00000000 r5 00000000 r6 00000000 r7 00000000
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip 00000000 sp bea06738 lr 00000000 pc b000268c cpsr 200
00010
I/DEBUG ( 132): #00 pc b000268c /system/bin/linker
I/DEBUG ( 132): #01 pc b00011e2 /system/bin/linker
I/DEBUG ( 132): #02 pc b0001464 /system/bin/linker
I/DEBUG ( 132): #03 pc b0001560 /system/bin/linker
I/DEBUG ( 132): #04 pc b0001cec /system/bin/linker
I/DEBUG ( 132): #05 pc 00008bee /system/bin/rild
I/DEBUG ( 132): #06 pc 0000c572 /system/lib/libc.so
I/DEBUG ( 132): #07 pc b00018c6 /system/bin/linker
I/DEBUG ( 132): stack:
I/DEBUG ( 132): bea066f8 b00107e0 /system/bin/linker
I/DEBUG ( 132): bea066fc 000002ff
I/DEBUG ( 132): bea06700 00000000
I/DEBUG ( 132): bea06704 00000000
I/DEBUG ( 132): bea06708 b000d288 /system/bin/linker
I/DEBUG ( 132): bea0670c bea066ac [stack]
I/DEBUG ( 132): bea06710 00000000
I/DEBUG ( 132): bea06714 00000000
I/DEBUG ( 132): bea06718 00000000
I/DEBUG ( 132): bea0671c ffffffff
I/DEBUG ( 132): bea06720 00000000
I/DEBUG ( 132): bea06724 b00041c1 /system/bin/linker
I/DEBUG ( 132): bea06728 00000004
I/DEBUG ( 132): bea0672c 00000003
I/DEBUG ( 132): bea06730 df002777
I/DEBUG ( 132): bea06734 e3a070ad
I/DEBUG ( 132): #00 bea06738 80004160 /system/lib/libhtc_ril.so
I/DEBUG ( 132): bea0673c b0017690
I/DEBUG ( 132): bea06740 80004000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): bea06744 b0011a3c
I/DEBUG ( 132): bea06748 b0010448 /system/bin/linker
I/DEBUG ( 132): bea0674c b00011e5 /system/bin/linker
I/DEBUG ( 132): #01 bea06750 00000003
I/DEBUG ( 132): bea06754 00004000
I/DEBUG ( 132): bea06758 b000ca4b /system/bin/linker
I/DEBUG ( 132): bea0675c b000c760 /system/bin/linker
I/DEBUG ( 132): bea06760 00000000
I/DEBUG ( 132): bea06764 00000000
I/DEBUG ( 132): bea06768 00000000
I/DEBUG ( 132): bea0676c b0011ad0
I/DEBUG ( 132): bea06770 00000160
I/DEBUG ( 132): bea06774 80004000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): bea06778 80000000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): bea0677c 00004000
I/DEBUG ( 132): bea06780 b001761c
I/DEBUG ( 132): bea06784 00000002
I/DEBUG ( 132): bea06788 00000003
I/DEBUG ( 132): bea0678c b0011b34
I/DEBUG ( 132): bea06790 b0011b38
I/DEBUG ( 132): bea06794 b0011ad4
I/DEBUG ( 132): bea06798 bea0699c [stack]
I/DEBUG ( 132): bea0679c b0010448 /system/bin/linker
I/DEBUG ( 132): bea067a0 b0011a3c
I/DEBUG ( 132): bea067a4 00000003
I/DEBUG ( 132): bea067a8 b0011ac8
I/DEBUG ( 132): bea067ac b0001469 /system/bin/linker
I/ ( 183): ServiceManager: 0xac38
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 183, tid: 183 >>> /system/bin/mediaserver <<<
I/DEBUG ( 132): signal 7 (SIGBUS), fault addr 80604164
I/DEBUG ( 132): r0 80604164 r1 00000000 r2 00000e80 r3 c0000000
I/DEBUG ( 132): r4 00000000 r5 00000000 r6 00000000 r7 00000000
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip 00000000 sp bef62ab8 lr 00000000 pc b0002668 cpsr a00
00010
And about sending nandroid - of course, I am so glad that someone looked here . What should I do? Flash a ROM that does not work, try to boot it, reboot to recovery, do a nandroid and send to you?
can anyone please tell me how to do fastboot system -w. ?
step by step and treat me as a beginner....
You have to have installed sdk on your computer and installed adb drivers for your phone (you should find out how install drivers on your own). I assume you are using Windows as 90% users of PC, so I will explain how to do it on Windows.
Download SDK HERE
Unzip it to C:\ (or wherever you want, just remember path)
Open windows terminal (command) by typing "cmd" in search bar in start menu (if you are using windows Vista or 7, on XP it's in the All Programs -> Accesories -> Command line (or sth like that))
Power off your phone and boot it with BACK + POWER combination
Plug your phone to PC
In command type (do not type "*" I included for explanations):
Code:
cd android-sdk-windows/tools *
fastboot devices **
fastboot erase system -w
* or any other path where your sdk is placed
**to make sure that your phone is properly connected, it should give you something like -serial number- fastboot
Now you can press MENU to poweroff phone
But honestly, I was expecting some help in my rather bad situation, not more questions about things which you can really google easily -_-.
raven_raven said:
You have to have installed sdk on your computer and installed adb drivers for your phone (you should find out how install drivers on your own). I assume you are using Windows as 90% users of PC, so I will explain how to do it on Windows.
Download SDK HERE
Unzip it to C:\ (or wherever you want, just remember path)
Open windows terminal (command) by typing "cmd" in search bar in start menu (if you are using windows Vista or 7, on XP it's in the All Programs -> Accesories -> Command line (or sth like that))
Power off your phone and boot it with BACK + POWER combination
Plug your phone to PC
In command type (do not type "*" I included for explanations):
Code:
cd android-sdk-windows/tools *
fastboot devices **
fastboot erase system -w
* or any other path where your sdk is placed
**to make sure that your phone is properly connected, it should give you something like -serial number- fastboot
Now you can press MENU to poweroff phone
But honestly, I was expecting some help in my rather bad situation, not more questions about things which you can really google easily -_-.
Click to expand...
Click to collapse
You may want to do
Code:
#df -h
and make sure your system partition is not ridiculously small. If its less than 90 you will have trouble.
Outside of that, maybe reroot but I doubt it will help. You may have corrupt areas in the internal memory.
Can you install and run Dwang? That has always worked for me when nothing else would.
That is all I can think of now I will give it some thought.
Maybe erase every thing then flash it back
fastboot erase system -w
fastboot erase recovery
fastboot erase boot
That will leave you with just fastboot working.
You will need to reflash recovery and every thing. Stay away from nandroids until you have it all working. You may accidentally reinstall whatever is the problem.
Good luck.
Thank you very much for advices, I will try every of them. One question though: I know how to flash recovery, but how to restore boot? Is it flashed with ROM?
And is there a possibility to test an internal memory? It can be it... However EVERY ROM should not work, but FEW are working (but only for one boot) and one (CM6 RC3) is booting flawlessy every time.
Results of
Code:
df -h
are standard to Haykuro:
90M of /system
89.8M of /data
30M of /cache
I will try to flash Dwang and see what results are.
I just rerooted my phone. I used DREAIMG.nbh to back to stock recovery, bootloader, ROM and radio, then gained root, then slowly upgraded everything to previus state (Amon_Ra + Haykuro + .26i radio). Finally I flashed SuperD... again, same bootloop. I am disappointed and I have no idea what is going on . I guess my G1 is saying me "enough of this flashing, I'm tired" and I should stick with stock 1.6...
Did you overclock your last ROM? I am only guessing, but when I restart my phone, SetCPU shows me always some "standard values" (245/576). What will happen if the CPU clock is set too high? I imagine, this may cause a kernel panic and a boot loop. Only guessing ...
Nope, I wasn't using OC since IMO this was only helping to drain battery faster . Even if it was OC, I think that corrupted kernel was wiped many flashes ago when I was unrooting or even further in past, when I was doing thousand wipe and fastboot erase system -w.
I come to conclusion that internal memory of my G1 must've became corrupted. This is only explanation of what's going on.
What will happen if this information is written into some hidden space which is not wiped, like the reboot to recovery flag when flashing radio from recovery?
It may be that some parts of ROM is not wiped even if I did all this unrooting and rooting stuff. The question is: How to find it and how to get rid of it? Man, if some kind of genius like Firerat or Cyanogen looked at this thread .
... or just lbcoder !
Sorry that I cannot help you so much, unfortunatey I am not such an expert as lbcoder or Firerat
Sorry, no offence of course, I really aprecceate your help ! Yep, lbcoder also might know what's going on . Don't know, maybe I'll try to PM one of them, maybe they'll have some time for me.
an old SD card did this to my old G1... not exactly this but something eerily similar. G1 bootoops, depending on rom... very slow on the ROMs that worked, etc..etc.. and the new G1 i have running now is doing the same thing.. time for a new SD. GET YOURSELF A NEW (not "another") get yourself a NEW class 6! micro. Worked for me for a little, then lots of flashing, partitioning, and all that heavy wear... now its getting slow again. These SDs wear down quickly is seems. This phone has a high-speed SDHC card slot for a reason -- why not put it to it's full potential. Another thing that happened to me was that the app "switch pro widget" fried my phones wifi. Makes no sense to you does it? But it happened, and - to me... it didn't seem like coincidence. I went to turn the wifi on via the widget, and the bar turned a shaded green while it turns on, then once connected it went dark green. Well i went to turn it on, and it got the the shaded green and said "updating wifi status" or and it never connected --- and my wifi never worked again. After that i would always get "ERROR" when i turned my wifi on. Flashed tons of new ROMS, new SDs, wiping over and over, new wifi hardware (board and coax cable)... ANYWAYYYY the conclusion is that for some reasons -- these G1's and their external memory (the SD) hold onto info somewhere and i believe theres potential for SOMETHING to become corrupt that we dont even know about, that does not show up on logcat, that stays with the phone....
then there is always potential for a HARDWARE ISSUE that we could be unaware of... at this point, for you and me it seems like kind of a guessing game lol.
are u sure u have death or danger spl and when u wipe do this
1 factory wipe
2 wipe ext partition
3 repair ext partition then flash ur rom and reboot
Yep, I'm 100% sure. I also did fastboot erase system -w, reflashed recovery, radio, tried another SD card and so on, and so on... Even unrooting and rooting again didn't help.
Instead of using the pc try flashing on ur phone from sd and reflaash ur radio and spl from the sd and see wht happens u probably don't have danger spl because its required to flash bigger roms like eclair and etc and post again if it works or not
Sent from my HTC Dream using XDA App on CM 6.00 RC3