why do i need to erase userdata after replace nand flash from x16 to x8??

by Jack stone » Tue, 28 Apr 2009 21:42:30 GMT


Sponsored Links
 i,all:
Replace NAND flash from x16 to x8, Android can run once successfuly!

I have just replaced my NAND flash from x16 to x8.
After change my nand flash driver in uboot and kernel,I use the
android image(ramdisk.gz,
system.img, userdata.img) which run ok on x16 H/W platform to test
my x8 H/W platform,
unfortunately it can run once. After reboot, it can't run
again.Every time it stop here(by logcat &):

# I/DEBUG ( 419): debuggerd: Apr 9 2009 17:00:26
D/mountd ( 418): AddMountPoint device: /dev/block/mmcblk0,
mountPoint: /sdcard driverStorePath: /sys/devices/platform/
usb_mass_storage/lun0/file
E/mountd ( 418): could not read initial mass storage state
D/mountd ( 418): USB offline
D/mountd ( 418): RequestMount /sdcard
E/flash_image( 425): can't find recovery partition
D/AndroidRuntime( 421):
D/AndroidRuntime( 421): >>>>>>>>>>>>>> AndroidRuntime START
<<<<<<<<<<<<<<
D/AndroidRuntime( 421): CheckJNI is ON
I/ ( 422): ServiceManager: 0xabe0
W/AudioHardwareInterface( 422): Using stubbed audio hardware. No
sound will be produced.
I/CameraService( 422): CameraService started: pid=422
I/AudioFlinger( 422): AudioFlinger's main thread ready to run.
D/AndroidRuntime( 421): --- registering native functions ---
I/DEBUG ( 419): *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *** ***
I/DEBUG ( 419): Build fingerprint: 'generic/generic/generic/:1.5/
MAIN/eng.root.20090409.162536:eng/test-keys'
I/DEBUG ( 419): pid: 421, tid: 421 >>> zygote <<<
I/DEBUG ( 419): signal 11 (SIGSEGV), fault addr ecd1608c
I/DEBUG ( 419): r0 ab07a024 r1 00030658 r2 41c9c068 r3 aac1e809
I/DEBUG ( 419): r4 41084ca4 r5 ad34f5c1 r6 bed536e0 r7 00000003
I/DEBUG ( 419): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 419): ip ad08403c sp bed536ac lr ad05d7ad pc
ad0640e2 cpsr 80000030
I/DEBUG ( 419): #00 pc 000640e2 /system/lib/libdvm.so
I/DEBUG ( 419): #01 pc 0005d7a8 /system/lib/libdvm.so
I/DEBUG ( 419): #02 pc 0005d94c /system/lib/libdvm.so
I/DEBUG ( 419): #03 pc 0005d9c4 /system/lib/libdvm.so
I/DEBUG ( 419): #04 pc 0003e968 /system/lib/libdvm.so
I/DEBUG ( 419): #05 pc 0003ea48 /system/lib/libdvm.so
I/DEBUG ( 419): #06 pc 000318bc /system/lib/libdvm.so
I/DEBUG ( 419): #07 pc 0000d39c /system/lib/
libnativehelper.so
I/DEBUG ( 419): #08 pc 00028bb4 /system/lib/
libandroid_runtime.so
I/DEBUG ( 419): #09 pc 0003994a /system/lib/
libandroid_runtime.so
I/DEBUG ( 419): #10 pc 00028cd0 /system/lib/
libandroid_runtime.so
I/DEBUG ( 419): #11 pc 00029236 /system/lib/
libandroid_runtime.so
I/DEBUG ( 419): #12 pc 00008bf2 /system/bin/app_process
I/DEBUG ( 419): #13 pc 0001fd72 /system/lib/libc.so
I/DEBUG ( 419): #14 pc 0000bc12 /system/lib/libc.so
I/DEBUG ( 419): #15 pc b0001424 /system/bin/linker
I/DEBUG ( 419): stack:
I/DEBUG ( 419): bed5366c afe37dd0
I/DEBUG ( 419): bed53670 0000a000 [heap]
I/DEBUG ( 419): bed53674 00000018
I/DEBUG ( 419): bed53678 0005c860 [heap]
I/DEBUG ( 419): bed5367c 00000000
I/DEBUG ( 419): bed53680 00000000
I/DEBUG ( 419):



Other Threads

1. wrong intent getting supplied to OneTimeAlarmReceiver.

> I am using marks' method of alarmreceiver and appservice. I am trying

PendingIntent recycles Intents, in effect. Try specifying
FLAG_UPDATE_CURRENT when you create your PendingIntent.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com
Android App Developer Books: http://commonsware.com/books.html


-- 

2. wrong intent getting supplied to OneTimeAlarmReceiver.

I am using marks' method of alarmreceiver and appservice. I am trying
to pass a record id to the alarmintent through putextra. and receive
it in ontimealarmreceiver in getExtra.

What I observe is, first time record id goes correct (say 11) second
time record id is sent 12, but in receiver i receive record id = 11.
third time too record id -11

whats wrong ?

regards

-- 

3. Build error : Undefined reference to ComponentInit

4. How to change device management objects in android device

5. GK:How to Animate the single image in the Gallery

6. Video display not coming on Android1.6 SDK on OMAP3430 board

7. <WTA> Update rom cyan