Hi im having trouble updating Mango RTM on my Samsung Focus Any help?
i have followed the whole guide and still getting error Also when in the process of the rebooting stage it would NOT reboot after several minutes.
Error Log: Towards end]
updatewp Information: 0 : 8/17/2011 7:13:20 PM: Device 283e0110 - f929285c - a9df376a - 9ced531a Executing Preparing to install 69%
updatewp Information: 0 : 8/17/2011 7:13:22 PM: Device 283e0110 - f929285c - a9df376a - 9ced531a Executing Preparing to install 72%
updatewp Information: 0 : 8/17/2011 7:13:24 PM: Device 283e0110 - f929285c - a9df376a - 9ced531a Executing Restarting your phone 0%
updatewp Information: 0 : 8/17/2011 7:13:24 PM: Waiting for reboot
updatewp Information: 0 : 8/17/2011 7:14:08 PM: Device Removal: 283e0110 - f929285c - a9df376a - 9ced531a
updatewp Information: 0 : 8/17/2011 7:14:08 PM: Receive Removal Event!
Related
Hello! Every time I try to build my DS homebrew app, this comes up.
1>------ Build started: Project: NintendoDS1, Configuration: Debug Win32 ------
1>Performing Makefile project actions
1>Project : error PRJ0002 : Error result 255 returned from 'C:\Windows\system32\cmd.exe'.
1>Build log was saved at "file://c:\Users\adam\Documents\VisualStudio2008\Projects\HelloWorld\NintendoDS1\Debug\BuildLog.htm"
1>NintendoDS1 - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
How do I fix this? It is becoming annoying. CMD works fine.
Hi,
My Ray sometimes reboots due to what I suspect is an undervolt error situation (cpu/ram).
Is there any log file that I can look into after rebooting, in order to understand what was the cause of the reboot ?
Tks
---------------------------------------------------------------
Xperia Ray
Smart Xperia SX.03.1.B.2.495
VDS Kernel 2.6.32.9 Dec 1 2012
Boost My Xperia 2.0.1 : Multitasking Mode
Sandisk 32GB Class 10 UHS-1
If your kernel support "Ram console" there should be a file named "/proc/last_kmsg" which holds the last kernel log.
Otherwise you can do an "adb logcat" on your PC but that is inconvenient if you can't reproduce manually the problem.
muczy said:
If your kernel support "Ram console" there should be a file named "/proc/last_kmsg" which holds the last kernel log.
Otherwise you can do an "adb logcat" on your PC but that is inconvenient if you can't reproduce manually the problem.
Click to expand...
Click to collapse
Thanks muczy. Will check that.
Will need to investigate further, since these messages seem to be related with a modem module (similar reboot on an Xperia S).
Anyone got similar situation ?
------------- /proc_lastamsslog (snipet) ---------------
ERR crash log report. Version 3.
Error in file mdspasync.c, line 2486
Time of crash (m-d-y h:m:s): 04-16-2013 13:30:04
Uptime (h:m:s): 97:52:24
Build ID: M7630A-ABBQMAZM-2.0.3028DT
REX_TCB ptr: 0x067a1614
tcb.task_name: IST0
Coredump ARCH type is: ERR_ARCH_ARM
Register values from coredump:
ARM_SVC_R0 : 0x00000090
...
Dog Report Information (dog_state_table)
[idx] Task Name Pri Timeout Count Is_Blocked
[ 0] fmrds 0 60 59 0
[ 1] bt_ftm 0 60 59 0
[ 2] time_ipc 0 60 59 0
[ 3] ds_sig 0 60 59 0
[ 4] loc_middlew 0 60 59 0
[ 5] snd 0 4 4 0
[ 6]
------------------------------------------------------------------
----------- /proc/last_kmsg (snipet) ------------------
...
[36005.036865] msmrtc_tod_proc_result: 04/16/2013 13:29:29 (01)
[36005.050659] msmrtc_tod_proc_result: 04/16/2013 13:29:29 (01)
[36005.050781] pm_op(): platform_pm_suspend+0x0/0x54 returns -16
[36005.050842] PM: Device alarm failed to suspend: error -16
[36005.050872] PM: Some devices failed to suspend
[36005.053375] Restarting tasks ... done.
[36005.074340] suspend: exit suspend, ret = -16 (2013-04-16 13:29:29.187896746 UTC)
[36005.074401] active wake lock alarm_rtc, time left 198
[36005.074432] suspend: abort suspend
[36005.887847] suspend: enter suspend
[36005.887878] PM: Syncing filesystems ... done.
[36005.967803] Freezing user space processes ...
[36005.973999] AKM8975 AKECS_GetOpenStatus returned (0)
[36005.982086] (elapsed 0.01 seconds) done.
[36005.982116] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[36005.983398] Suspending console(s) (use no_console_suspend to debug)
------------------------------------------------------------------
Well, this mdspasync.c seems to be hard to find...
Looked in the androidxref dot com for both Android and Kernel sources, but had no luck.
If someone knows what is this for (seems to be related with modem), that would be great.
Hi, I have a problem with my phone, i dont know if is a hw or sw issue. When my phone is charging and i receive a call, rings for 2 or 3 seconds and then reboots. I tried many fw: .14, .17, cm11, and the behaviour is almost the same. (in .14 and .17 the phone suddenly shut down with no reason, in cm11 NOT ) I reach the klog and it seems to me a modem issue :S, please someone can give it a look and tell me, thanks in advance.
============================= KLog Information =============================
magic:FATALM003
prev_reboot_reason:FATALM
kernel_time:[000006EE.358A20E7]
first_rtc:[537A025A.1B89D3DE]
last_rtc:[537A0B5E.27AB99C4]
normal_boot:1
prev_normal_boot:1
klog_userdata_count:5
klog_internal_count:5
klog_external_count:5
system_on_off_state:0x10
sbl_bootup_time:0
aboot_bootup_time:0
android_bootup_time:0
android_shutdown_time:0
sysfs_sync_time:0
kernel_power_off_time:0
suspend_time:2335
resume_time:2870
android_version:4.2.2
modem_version:8930B-BAAAATAZQ-3228109-14-1014
flex_version:FF_SHP_SA77.0.1.1016
rpm_version:3.0.16842938
bootloader_version:1269-1300_S1_Boot_MSM_8X30_R1_25
linux_version:3.4.0-g74b701b-00054-gde56c65-dirty
version_id:15.3.A.1.17
build_version:SA77.0.1.1016
build_date:Wed Mar 26 00:50:55 CST 2014
build_type:user
build_user:cme
build_host:androidbs-desktop
build_key:release-keys
secure_mode:1
debug_mode:0
hw_id:7241
cpuinfo_max_freq:1026000
scaling_max_freq:1026000
sim_state:READY
============================= KLog Start =============================
KLog Category #0:
name:CRASH
size:8192
index:2290
overload:0
<2>[klog]fault_level=0x5, fault_type=-1, fault_msg=modem
<2>[klog]modem crash log:Error Crash Log Report. Version 3.
<2>
<2>Error in file: fws_task.c, line: 245
<2>Time of crash (m-d-y h:m:s): 05-19-2014 13:47:03
<2>Uptime (h:m:s): 0000:38:53
<2>Build ID: M8930B-AAAATAZM-3.2.28109
<2>REX_TCB ptr: 0x8cf18458
<2>tcb.task_name: IST 98
<2>Coredump ARCH type is: ERR_ARCH_QDSP6
<2>R0: 0x00000000
<2>R1: 0x8cee43f8
<2>R2: 0x00000000
<2>R3: 0x8ce28288
<2>R4: 0x000000fe
<2>R5: 0x06c0c5a0
<2>R6: 0x00000000
<2>R7: 0x00000001
<2>R8: 0xe353f7cf
<2>R9: 0x20c49ba5
<2>R10: 0xffdf7b00
<2>R11: 0x00000000
<2>R12: 0xffdf7b00
<2>R13: 0x0004afff
<2>R14: 0x8900cd98
<2>R15: 0x00000002
<2>R16: 0x8ad51378
<2>R17: 0x00000000
<2>R18: 0x00000000
<2>R19: 0x00000000
<2>R20: 0x89a76840
<2>R21: 0x00000000
<2>R22: 0x00000000
<2>R23: 0x00000000
<2>R24: 0x00000000
<2>R25: 0x00000000
<2>R26: 0x00000000
<2>R27: 0x00000000
<2>R28: 0x00000000
<2>SP: 0x8cf18d30
<2>FP: 0x8cf18d38
<2>LR: 0x89d6a88c
<2>PC: 0x895bab98
<2>
<3>modem subsystem failure reason: fws_task.c:245:Firmware generated fatal error..
<2>[klog]fault already exist:5, ignore:5
<2>[klog]klog_magic=FIQHNG###
<2>[klog]preset magic(warn-boot higher):magic=FATALM, state=1, buf=FATALM###
<2>[klog]new klog_magic:klog_magic=FATALM001, buf=FATALM001
<2>[klog]fault already exist:5, ignore:1
<0>Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.
<2>[klog]klog_magic=FATALM001
<2>[klog]preset magic(warn-boot lower):magic=PANICA, state=2, buf=FATALM001
<2>[klog]new klog_magic:klog_magic=FATALM003, buf=FATALM003
<1>[<c0013e54>] (unwind_backtrace+0x0/0x11c) from [<c07fc2cc>] (panic+0x1c8/0x33c)
<1>[<c07fc2cc>] (panic+0x1c8/0x33c) from [<c005fd40>] (subsystem_restart_dev+0x29c/0x398)
<1>[<c005fd40>] (subsystem_restart_dev+0x29c/0x398) from [<c00369ac>] (notify_smsm_cb_clients_worker+0xa4/0x1c0)
<1>[<c00369ac>] (notify_smsm_cb_clients_worker+0xa4/0x1c0) from [<c009f4ec>] (process_one_work+0x280/0x488)
<1>[<c009f4ec>] (process_one_work+0x280/0x488) from [<c009f908>] (worker_thread+0x214/0x3b4)
<1>[<c009f908>] (worker_thread+0x214/0x3b4) from [<c00a3800>] (kthread+0x84/0x90)
<1>[<c00a3800>] (kthread+0x84/0x90) from [<c000eac8>] (kernel_thread_exit+0x0/0x8)
<3>wcnss_8960: crash shutdown : 0
<0>Rebooting in 5 seconds..
============================== KLog End ==============================
============================= KLog Start =============================
KLog Category #1:
name:APPSBL
size:6144
index:0
overload:0
<Empty>
============================== KLog End ==============================
Ok if posted it in older thread may no one read it.
I've got the little Miro day after Christmas from my wife to push system apps manual back in place to earn free space in data partition.
Everything seems OK.... dalvik & cache cleared and reboot... same as every time before.
Phone boot calculated dalvik files... Messages apps Starting show... and spontaneous hotboot with following reboot.
Now it stuck in bootloop.
I get into recovery but I can not del things or add things in partitions. Every time phone say DONE but if I remount the partition I'm working on.... Every thing is like before....
Some logs:
Flashtool
Code:
29/045/2014 00:45:15 - INFO - Selected Bundle for Sony Xperia Miro (ST23i). FW release : 11.0.A.5.8. Customization : Swisscom_CH
29/045/2014 00:45:15 - INFO - Preparing files for flashing
29/045/2014 00:45:15 - DEBUG - Created the prepared folder
29/045/2014 00:45:15 - DEBUG - Saving entry userdata.sin to disk
29/045/2014 00:45:15 - DEBUG - Streaming from jar entry : userdata.sin
29/045/2014 00:45:15 - DEBUG - Writing Entry to .\firmwares\prepared\userdata.sin
29/045/2014 00:45:15 - DEBUG - Saving entry cache.sin to disk
29/045/2014 00:45:15 - DEBUG - Streaming from jar entry : cache.sin
29/045/2014 00:45:15 - DEBUG - Writing Entry to .\firmwares\prepared\cache.sin
29/045/2014 00:45:15 - DEBUG - Saving entry system.sin to disk
29/045/2014 00:45:15 - DEBUG - Streaming from jar entry : system.sin
29/045/2014 00:45:15 - DEBUG - Writing Entry to .\firmwares\prepared\system.sin
29/045/2014 00:45:45 - DEBUG - Saving entry fota0.sin to disk
29/045/2014 00:45:45 - DEBUG - Streaming from jar entry : fota0.sin
29/045/2014 00:45:45 - DEBUG - Writing Entry to .\firmwares\prepared\fota0.sin
29/045/2014 00:45:45 - DEBUG - Saving entry fota1.sin to disk
29/045/2014 00:45:45 - DEBUG - Streaming from jar entry : fota1.sin
29/045/2014 00:45:45 - DEBUG - Writing Entry to .\firmwares\prepared\fota1.sin
29/045/2014 00:45:45 - DEBUG - Saving entry kernel.sin to disk
29/045/2014 00:45:45 - DEBUG - Streaming from jar entry : kernel.sin
29/045/2014 00:45:45 - DEBUG - Writing Entry to .\firmwares\prepared\kernel.sin
29/045/2014 00:45:45 - DEBUG - Saving entry partition-image.sin to disk
29/045/2014 00:45:45 - DEBUG - Streaming from jar entry : partition-image.sin
29/045/2014 00:45:45 - DEBUG - Writing Entry to .\firmwares\prepared\partition-image.sin
29/045/2014 00:45:45 - DEBUG - Saving entry loader.sin to disk
29/045/2014 00:45:45 - DEBUG - Streaming from jar entry : loader.sin
29/045/2014 00:45:45 - DEBUG - Writing Entry to .\firmwares\prepared\loader.sin
29/045/2014 00:45:45 - DEBUG - Saving entry amss.sin to disk
29/045/2014 00:45:45 - DEBUG - Streaming from jar entry : amss.sin
29/045/2014 00:45:45 - DEBUG - Writing Entry to .\firmwares\prepared\amss.sin
29/045/2014 00:45:47 - DEBUG - Saving entry modem_fs1.sin to disk
29/045/2014 00:45:47 - DEBUG - Streaming from jar entry : modem_fs1.sin
29/045/2014 00:45:47 - DEBUG - Writing Entry to .\firmwares\prepared\modem_fs1.sin
29/045/2014 00:45:47 - DEBUG - Saving entry modem_fs2.sin to disk
29/045/2014 00:45:47 - DEBUG - Streaming from jar entry : modem_fs2.sin
29/045/2014 00:45:47 - DEBUG - Writing Entry to .\firmwares\prepared\modem_fs2.sin
29/045/2014 00:45:47 - INFO - Please connect your device into flashmode.
29/045/2014 00:45:48 - INFO - Opening device for R/W
29/045/2014 00:45:48 - INFO - Start Flashing
29/045/2014 00:45:48 - INFO - Processing loader.sin
29/045/2014 00:45:48 - DEBUG - loader.sin : header size : 1020
29/045/2014 00:45:48 - INFO - Checking header
29/045/2014 00:45:48 - DEBUG - Sending part 1 of 1
29/045/2014 00:45:48 - ERROR - Processing of loader.sin finished with errors.
29/045/2014 00:45:48 - INFO - Ending flash session
29/045/2014 00:45:48 - ERROR -
29/045/2014 00:45:48 - ERROR - Error flashing. Aborted
29/045/2014 00:45:49 - INFO - Device connected in flash mode
fastboot.exe
Code:
C:\android>fastboot devices
PSDN:YT91004G4G&ZLP fastboot
C:\android>fastboot erase boot
erasing 'boot'...
(bootloader) Erase of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00002000-0x0000bfff
(bootloader) Erase operation complete, 0 bad blocks encountered
OKAY [ 0.030s]
finished. total time: 0.030s
C:\android>fastboot flash boot C:\android\miro\boot.img
sending 'boot' (20480 KB)...
(bootloader) USB download speed was 26921kB/s
OKAY [ 2.320s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00002000-0x0000bfff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
FAILED (status read failed (Too many links))
finished. total time: 96.080s
C:\android>
adb shell
Code:
C:\android>adb devices
List of devices attached
37714ecd recovery
C:\android>adb shell
~ # ?[6nls
ls
boot external_sd sd-ext
boot.txt fstab.sony sdcard
cache init sys
data init.rc system
datadata logo.rle tmp
default.prop proc ueventd.goldfish.rc
dev res ueventd.rc
emmc root ueventd.sony.rc
etc sbin
~ # ?[6nrm -R /data
rm -R /data
rm: can't remove '/data': Device or resource busy
~ # ?[6ncd /data
cd /data
/data # ?[6nls
ls
/data # ?[6nexit
exit
C:\android>adb remount /data
remount succeeded
C:\android>adb shell
~ # ?[6nls
ls
boot external_sd sd-ext
boot.txt fstab.sony sdcard
cache init sys
data init.rc system
datadata logo.rle tmp
default.prop proc ueventd.goldfish.rc
dev res ueventd.rc
emmc root ueventd.sony.rc
etc sbin
~ # ?[6ncd /data
cd /data
/data # ?[6nls
ls
anr dalvik-cache gg_address radio time
app data local resource-cache tombstones
app-asec dontpanic lost+found shared user
app-private drm misc ssh wiper
backup fota property system wpstiles
/data # ?[6nexit
exit
C:\android>
try to get logcat or something end with
Code:
/sbin/sh: exec: line 1: logcat: not found
dmesg works -> [click]
Linux show me following:
if i try to transfer data with flashtool
Code:
libusb_bulk_transfer (write) : I/O Errors
Error : did not write all data
libusb_bulk_transfer (write) : I/O Errors
Error : did not write all data
libusb_bulk_transfer (read) : I/O Errors
release_interface : Device Not found
attach kernel : Device busy
release_interface : Device Not found
attach kernel : Device busy
Flashtool Log
Code:
04/046/2015 03:46:40 - INFO - (X10flash.java:486) - Start Flashing
04/046/2015 03:46:40 - INFO - (X10flash.java:239) - Processing loader.sin
04/046/2015 03:46:40 - DEBUG - (X10flash.java:240) - loader.sin : header size : 1020
04/046/2015 03:46:40 - INFO - (X10flash.java:218) - Checking header
04/046/2015 03:46:40 - DEBUG - (X10flash.java:222) - Sending part 1 of 1
04/046/2015 03:46:41 - DEBUG - (USBFlashLinux.java:27) - Writing packet to phone
04/046/2015 03:46:41 - DEBUG - (USBFlashLinux.java:32) - OUT : CommandID : 5 / Flags : false,true,false / Data length : 1020 / Data CRC32 : [23, C4, 2F, B5]
04/046/2015 03:46:41 - DEBUG - (USBFlashLinux.java:50) - Reading packet from phone
04/046/2015 03:46:41 - ERROR - (X10flash.java:254) - Processing of loader.sin finished with errors.
04/046/2015 03:46:41 - INFO - (X10flash.java:546) - Ending flash session
The only thing it does is load the battery and nothing more.
Last installed ROM:
FXP cm10 with normal kernel no tweaks.
Oh and yes, i tried all USB Ports reinstalled all drivers used all PC's in house but ... no ... it woudn't be recognized in right mode way
Someone could explain?
I am using Moto G 3(2015)
My phone is rebooting randomly without doing anything. It generally happen 2 - 3 times in a day.
I have taken bug report for last 5 reboot. I found below information in "Last kmsg" from bugreport file :
[ 17.103106,1] msm_cci_release invalid ref count 0 / cci state 1
[ 17.103122,1] msm_sensor_cci_i2c_util line 512 rc = -22
[ 17.103127,1] msm_actuator_close:1439 cci_init failed
[ 17.103423,1] msm_csid_init: CSID_VERSION = 0x30010000
[ 17.103884,1] msm_csid_init: Failed in getting TOP gdscr regulator handle
[ 17.105711,1] msm_csid_init: CSID_VERSION = 0x30010000
[ 17.107891,1] msm_csid_init: Failed in getting TOP gdscr regulator handle
[ 17.112417,0] msm_vfe40_init_qos_parms: NO D/S entries found
[ 17.112433,0] msm_vfe40_init_vbif_parms: NO VBIF entries found
[ 17.129867,0] MSM-CPP cpp_init_hardware:952 CPP HW Version: 0x40000000
[ 17.129883,0] MSM-CPP cpp_init_hardware:973 stream_cnt:0
[ 17.156069,1] MSM-CPP cpp_load_fw:1110 MC Bootloader Version: 0x312e3176
[ 17.161889,1] MSM-CPP cpp_load_fw:1123 CPP FW Version: 0x10040005
[ 17.437125,2] camera_check_event_status : event_data status out of bounds
[ 17.437141,2] camera_check_event_status : Line 71 event_data->status 0X10001
[ 17.437148,2] camera_v4l2_open : checking event status fails Line 592 rc -14
[ 17.438450,3] mdss_fb_release_all: try to close unopened fb 1! from init
[ 17.438474,3] mdss_fb_release_all: try to close unopened fb 0! from init
[ 17.439087,0] Restarting system with command 'post-wdt'.
[ 17.439099,0] Current task:init(1) Parent task:swapper/0(0)
[ 17.439114,0] Going down for restart now
[ 17.440404,0] scm_call failed: func id 0x82000109, arginfo: 0x2, args: 0x1, 0x0, 0x0, 0x0, ret: -2, syscall returns: 0xfffffffc, 0x0, 0x0
[ 17.440417,0] Failed to disable secure wdog debug: -22
Need help to find root cause of issue.
Information of phone:
Build: MPI24.65-25
Build fingerprint: 'motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0/MPI24.65-25/28:user/release-keys'
Bootloader: 0x80CB
Radio: msm
Kernel: Linux version 3.10.49-g88eb8b3 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Tue Dec 8 05:34:29 CST 2015
My moto g is also rebooting randomely :/
mcnico said:
My moto g is also rebooting randomely :/
Click to expand...
Click to collapse
My phone is rebooting in safe mode too, I think it is some hardware bug.
Maybe you can capture bug report for your phone and check if you are getting same error message.
Firstly I am too getting this issue. My phone reboots randomly 2-3 a day. Strangely it reboots even when it is idle for quiet some time.
Secondly did anyone resolve this issue.
Thirdly how do I get the BUG report that you got in the first post?