I believe I have bricked an Alcatel 990 after flashing "cm-7-20121221-UNOFFICIAL-brandy.zip" via CWM.
Here are reasons why I believe it's bricked good and proper ;-P
1/ device boot loops when charging only via usb connection to PC
- 1.1 - device shows android logo - then "Alcatel One Touch Cyanogenmod 7" text/logo
- 1.2 - this loops continuous and never fully boots - output of adb logcat below
2/ when power-up off charge, only "menu", "search" and "back" soft keys illuminate - the screen+backlight stay completely off
- 2.1 - this remains constant until battery pull
- 2.2 - recovery mode via key combos do not work. Period. (no user error - assured!)
3/ when connected via usb during point 2 - there is not feedback from adb logcat - dead as a doorknob ;)
- 3.1 - when boot looping (1.1 above) I get ~2seconds of adb connectivity then device reboots.
- 3.2 - fastboot <options> <commands> does nothing - device stays as "waiting forr device" this is contstant
- 3.3 - adb has better luck - I can invoke adb logcat and this captures log info as below
- 3.4 - adb recovery options fail and device reboots and hangs as on point 2 above
- 3.5 - adb shell shows rooted prompt for 2 seconds when <up/previous command+enter> very quickly repeated keyboard bashing style
- 3.6 - I have invoked "adb shell rm\ -r\ /cache/*" and "adb shell recovery --wipe_data - all to no avail in context of unbricking device
the two lines of output have since not been replicated since I "adb shell rm\ -r\ /cache/*"
D/dalvikvm( 146): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 146): ODEX file is stale or bad; removing and retrying (/cache/dalvik-cache/system@framework@core.jar@classes.dex)
the logcat above outputs at the same time as the adb shell outputs four hash/root prompts (about 2secs then device reboots/loops) at the very last line of output:
I/AudioHardwareMSM72XX( 147): Setting in-call volume to 7 (available range is 0 to 7)
This is replicated on command and is constant. Replicated under slackware/linux and under win7-32bit-ultimate.
Recovery fails to boot so I need some sort of usb 'bridge' to interrupt the boot loop and invoke recovery - or flashall back onto device - but fastboot fails to identify the device/connectivity. - or other solution. any tips or guidance is appreciated.
Hope I've been articulate enough. thanks in advance.
Here are reasons why I believe it's bricked good and proper ;-P
1/ device boot loops when charging only via usb connection to PC
- 1.1 - device shows android logo - then "Alcatel One Touch Cyanogenmod 7" text/logo
- 1.2 - this loops continuous and never fully boots - output of adb logcat below
2/ when power-up off charge, only "menu", "search" and "back" soft keys illuminate - the screen+backlight stay completely off
- 2.1 - this remains constant until battery pull
- 2.2 - recovery mode via key combos do not work. Period. (no user error - assured!)
3/ when connected via usb during point 2 - there is not feedback from adb logcat - dead as a doorknob ;)
- 3.1 - when boot looping (1.1 above) I get ~2seconds of adb connectivity then device reboots.
- 3.2 - fastboot <options> <commands> does nothing - device stays as "waiting forr device" this is contstant
- 3.3 - adb has better luck - I can invoke adb logcat and this captures log info as below
- 3.4 - adb recovery options fail and device reboots and hangs as on point 2 above
- 3.5 - adb shell shows rooted prompt for 2 seconds when <up/previous command+enter> very quickly repeated keyboard bashing style
- 3.6 - I have invoked "adb shell rm\ -r\ /cache/*" and "adb shell recovery --wipe_data - all to no avail in context of unbricking device
Code:
david@1000H:~/Downloads/src/adt-bundle-linux-x86/sdk/platform-tools$ adb logcat
- waiting for device -
--------- beginning of /dev/log/main
I/cm ( 105): Welcome to Android 2.3.7 / CyanogenMod-7-20121221-UNOFFICIAL-brandy
I/cm ( 106): _
I/cm ( 107): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 108): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 109): )) _))
I/cm ( 110):
I/DEBUG ( 144): debuggerd: Dec 21 2012 22:47:32
E/bdaddr ( 154): Can't read btaddr from service.brcm.bt.mac.
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): modem is present in configuration
I/dun_service( 156): The value returned from dun_getusbstate_fromsys is 1
I/dun_service( 156): Post event 1
I/dun_service( 156): received event: DUN_EVENT_USB_UNPLUG
I/dun_service( 156): received event(DUN_EVENT_USB_UNPLUG) in state(DUN_STATE_USB_UNPLUG)
I/dun_service( 156): Ignoring the event DUN_EVENT_USB_UNPLUG in USB_UNPLUG_STATE
I/dun_service( 156): Moved to state(DUN_STATE_USB_UNPLUG)
I/dun_service( 156): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents
--------- beginning of /dev/log/system
I/Vold ( 142): Vold 2.1 (the revenge) firing up
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
D/Vold ( 142): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): got usb offline event
I/dun_service( 156): ustate is DUN_USBSTATE_UNPLUG
I/dun_service( 156): Post event 1
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): got usb online event
I/dun_service( 156): ustate is DUN_USBSTATE_PLUG
I/dun_service( 156): Post event 2
I/dun_service( 156): received event: DUN_EVENT_USB_UNPLUG
I/dun_service( 156): received event(DUN_EVENT_USB_UNPLUG) in state(DUN_STATE_USB_UNPLUG)
I/dun_service( 156): Ignoring the event DUN_EVENT_USB_UNPLUG in USB_UNPLUG_STATE
I/dun_service( 156): Moved to state(DUN_STATE_USB_UNPLUG)
I/dun_service( 156): received event: DUN_EVENT_USB_PLUG
I/dun_service( 156): received event(DUN_EVENT_USB_PLUG) in state(DUN_STATE_USB_UNPLUG)
I/dun_service( 156): Successfully opened SMD port: a, ext port: f
I/dun_service( 156): Configured external host port in RAW mode
I/dun_service( 156): Moved to state(DUN_STATE_IDLE)
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
W/Vold ( 142): Ignoring unknown switch 'MSM72K_UDC'
W/Vold ( 142): Ignoring unknown switch 'MSM72K_UDC'
W/Vold ( 142): Ignoring unknown switch 'usb_configuration'
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
I/dun_service( 156): The value returned from dun_getusbmodemstate_fromsys is 2
D/Vold ( 142): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 142): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/Netd ( 143): Netd 1.0 starting
I/dun_service( 156): modem_bits0, prev_mdm_bits 0, init = 1,
I/dun_service( 156): smdtoextctrl: ext port bits 320, smdoldstatus 0, init = 1
I/dun_service( 156): portbridge: Turning ON external port bits 140
D/AndroidRuntime( 146):
D/AndroidRuntime( 146): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
I/AndroidRuntime( 146): Heap size: -Xmx32m
D/AndroidRuntime( 146): CheckJNI is OFF
D/dalvikvm( 146): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 146): ODEX file is stale or bad; removing and retrying (/cache/dalvik-cache/system@framework@core.jar@classes.dex)
I/ ( 147): ServiceManager: 0xae08
I/AudioHardwareMSM72XX( 147): get_audpp_filter
I/AudioHardwareMSM72XX( 147): open /system/etc/AudioFilter.csv success.
E/AudioHardwareMSM72XX( 147): malformatted pcm control buffer
I/AudioHardwareMSM72XX( 147): failed to set audpp parameters, exiting.
D/AudioHardwareInterface( 147): setMode(NORMAL)
I/AudioHardwareMSM72XX( 147): Set master volume to 7.
I/QualcommCameraHardware( 147): getCameraInfo: IN
I/QualcommCameraHardware( 147): getCameraInfo: loading libqcamera at 0xb000d828
E/mm-camera( 147): mm_camera_get_camera_info: [S]
E/mm-camera( 147): mm_camera_get_camera_info: num 2
E/mm-camera( 147): mm_camera_get_camera_info: 0 [E]
I/QualcommCameraHardware( 147): getCameraInfo: numOfCameras = 2
I/QualcommCameraHardware( 147): Camera sensor 0 info:
I/QualcommCameraHardware( 147): camera_id: 0
I/QualcommCameraHardware( 147): modes_supported: 1
I/QualcommCameraHardware( 147): position: 0
I/QualcommCameraHardware( 147): sensor_mount_angle: 90
I/QualcommCameraHardware( 147): Camera sensor 1 info:
I/QualcommCameraHardware( 147): camera_id: 1
I/QualcommCameraHardware( 147): modes_supported: 1
I/QualcommCameraHardware( 147): position: 1
I/QualcommCameraHardware( 147): sensor_mount_angle: 270
I/QualcommCameraHardware( 147): getCameraInfo: OUT
I/AudioFlinger( 147): AudioFlinger's thread 0xcbb8 ready to run
D/AudioFlinger( 147): setParameters(): io 1, keyvalue routing=2, tid 227, calling tid 147
I/AudioHardwareMSM72XX( 147): Routing audio to Speakerphone
D/AudioHardwareMSM72XX( 147): doAudioRouteOrMute() device 6, mMode 0, mMicMute 1, mBuiltinMicSelected 0, muted
I/AudioHardwareMSM72XX( 147): Routing audio to Speakerphone
D/AudioHardwareMSM72XX( 147): setVoiceVolume(1.000000)
I/AudioHardwareMSM72XX( 147): Setting in-call volume to 7 (available range is 0 to 7)
david@1000H:~/Downloads/src/adt-bundle-linux-x86/sdk/platform-tools$D/dalvikvm( 146): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 146): ODEX file is stale or bad; removing and retrying (/cache/dalvik-cache/system@framework@core.jar@classes.dex)
the logcat above outputs at the same time as the adb shell outputs four hash/root prompts (about 2secs then device reboots/loops) at the very last line of output:
I/AudioHardwareMSM72XX( 147): Setting in-call volume to 7 (available range is 0 to 7)
This is replicated on command and is constant. Replicated under slackware/linux and under win7-32bit-ultimate.
Recovery fails to boot so I need some sort of usb 'bridge' to interrupt the boot loop and invoke recovery - or flashall back onto device - but fastboot fails to identify the device/connectivity. - or other solution. any tips or guidance is appreciated.
Hope I've been articulate enough. thanks in advance.