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.
Related
I am getting an error when trying to sbf my Xoom where it is saying it fails to communicate with the RAM Downloader. I am running Win 7 x64. I have tried putting the files in the rsd folder, root of C, even My documents, nothing is working. I have also set it up to run as administrator to no avail. I have attached the error log if it helps anyone.
19:59:02, April 15, 2011 Line: 1633 ERROR: MA type 0 is not supported. File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp Device ID: 0
20:02:34, April 15, 2011 Line: 1633 ERROR: MA type 0 is not supported. File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp Device ID: 0
20:04:56, April 15, 2011 Line: 612 ERROR: Interface BP: Error checking the RAM Downloader. File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp Device ID: 0
20:04:56, April 15, 2011 Line: 321 ERROR: Interface BP: Error jumping to RAM Downloader File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp Device ID: 0
20:04:56, April 15, 2011 Line: 1190 ERROR: Phone[0000]: Flash failed. File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp Device ID: 0
20:04:56, April 15, 2011 Line: 597 ERROR: Flash failure: Interface BP: Error checking the RAM Downloader. (Error Code: 9f), Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp Device ID: 0
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!
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.
A while ago I received a free Wave S8500 running Bada 1.2. Since this OS was pretty awful I decided to upgrade having done the process before on another phone of the same model. Unfortunately I was stupid and managed to flash the wrong files so my phone ended up in a boot loop. I found the correct set of files and tried to flash them but Multiloader only works up to SHP APP, at this point it fails with a "serial port open error". When I try and boot the phone I reach a blue screen full of the following debugging information:
Page: 1/2 <Pic #>
S/W version: S8500+XP+KJ1
Modem: Q6270B-KPRBL-1.5.45T
SHP: VPP R5 2.1.1
Build Host:s1-AGENT08
BuildAt:2011/10/05 22:44:23
App Debug Level l: 0
ASSERTION_REQUIRE:m_hLib != IN
VALID_HOBJ failed/ (file WinLibDllMgr.cpp, line 40)
Cannot load (shpWindow)
<Callstack information>
PC = 40318BEF OemDumpRegister
LR = 403118 OemDumpRegister
<Running Task(InvalidTask) Call stack>
_SysAssertReport
GWES:WinLib::CDI I Mgr::LoadLibrary
WinLibDllProxyInit
WinLibDispatch
OemBmPrelnitMochaTask
mochaTaskPreInit
Page: 2/2 <* #>
All HW Information:
HW VERSION: S8500_REV07
IMEI VERSION: Not Active
RF CAL DATE: Not Active
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = 2, Current BMPs = 0
Nucleus Task Information:
Running Task name = SHP_PRE SI
ices = 00000000
Wait = 00000000
Signal = 00000000
Priority = 0
To exit
Press 0 for 2sec
After pressing the home key it goes to a screen I've never previously seen with yellow text stating "UPLOAD to pc". Clearly the phone has a problem with the SHP_APP file and the Windows system it's connected to but beyond that I'm completely out of my depth. Can somebody shed some light on what is wrong with my phone and how I might go about fixing it?
Thanks in advance.
Can not backup TA with BackupTA_V2 on Z3 dual with stock ROM. Will someone please help find out what is going wrong? Here are the details:
Code:
$ adb devices -l
List of devices attached
CB5A25TMFR device usb:2-1.1 product:D6633 model:D6633 device:D6633
$ adb shell getprop ro.build.description
D6633-user 5.0.2 23.1.1.E.0.1 937646546 release-keys
$ adb shell cat /proc/version
Linux version 3.4.0-perf-g72984dd ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Feb 27 18:06:32 2015
$ ./backupTA.sh
Running on D6633 on 32-bit platform
Pushing files
127 KB/s (13644 bytes in 0.104s)
109 KB/s (5364 bytes in 0.047s)
185 KB/s (9512 bytes in 0.050s)
98 KB/s (5416 bytes in 0.053s)
109 KB/s (5364 bytes in 0.047s)
23 KB/s (1094 bytes in 0.046s)
Running scripts to dump ta to "TA_D6633_CB5A25TMFR_20171203-1843.img" on device
Overwriting run-as
Attempting to dirtycow
Done dirtycowing
Overwriting secondary payload (screenrecord)
Attempting to dirtycow
Done dirtycowing
Reading dumpta from stdin...
Read dumpta from stdin at 0 bytes
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Attempting exploit with buf of length 0
Error loading source file: No such file or directory
Error dirtycowing, trying again...
Dumped TA as TA_D6633_CB5A25TMFR_20171203-1843.img
File: /data/local/tmp/TA_D6633_CB5A25TMFR_20171203-1843.img with size: 0x0 is not a valid dump!
Sorry trim area dump is corupted and not a safe, please try again!
Pulling image
remote object '/data/local/tmp/TA_D6633_CB5A25TMFR_20171203-1843.img' does not exist
Cleaning up
TA Backup Failed!! Please reboot and try again.
NOTE: If you are running Android Nougat, you need to downgrade to use this tool.
$
The solution was to update to Android 6.0.1
$ adb shell getprop ro.build.description
D6633-user 6.0.1 23.5.A.1.291 2769308465 release-keys
$ adb shell cat /proc/version
Linux version 3.4.0-perf-gc14c2d5 ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Jun 28 11:15:51 2016
Now the backupTA_v2 workes.
Meanwhile I found out that backupTA.sh leaves two files (particularly dumpta and checkta) on the device:
Code:
echo "Cleaning up"
adb shell "rm -f /data/local/tmp/dirtycow /data/local/tmp/run-as /data/local/tmp/exploitta /sdcard/dumpta /data/local/tmp/backupTA.sh"
If you think that this information worth mentioning, please copy it to TA Backup v2 thread, cause I still can not