Database Info

[FIRMWARE]ME600GC-N-00.00.34R (chinese backflip)

So, currently the backflip is released in 3 markets:
USA under AT&T as the Backflip MB300
Brazil under Vivo as the Backflip MB300
and
China from motorola as the MB600
MOTOSTORE (chinese)
Currently there is know firmware released for the USA and BRAZIL versions, but it appears I was able to find the firmware for the ME600!!
The file found is ME600GC-N-00.00.34R.zip and contains MotusGC_N_00.00.34R-supermonster-customer.sbf
The original post (chinese) is available at ME600GC-N-00.00.34R - ME600/MB300/Backflip - Android
The direct download for the ZIP containg SBF is http://me600.net/files/ME600GC-N-00.00.34R.zip
I have not had time to do anything with the files, and anybody who uses this file is doing so at their own risk... no complaining to me about ruining your phone.
If you want track my progress at http://twitter.com/moosefist

So i decided to risk (NO brick created) it and tried flashing the file and RSDlite failed with this error:
Code:
23:50:41, March 23, 2010
Line: 563
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0030040 Address: 0xB00000 Command: JUMP
File: X:test_dev_usbflashcodeflashdllRDLOp.cpp
Device ID: 0
23:50:41, March 23, 2010
Line: 318
ERROR: Phone[0000]: Error jumping to RAM Downloader
File: X:test_dev_usbflashcodeflashdllRDLOp.cpp
Device ID: 0
23:50:41, March 23, 2010
Line: 1182
ERROR: Phone[0000]: Flash failed.
File: X:test_dev_usbflashcodeflashdllPST_FP_FlashThread.cpp
Device ID: 0
23:50:41, March 23, 2010
Line: 587
ERROR: Flash failure: Phone[0000]: Error sending JUMP command Device API Error: 0xE0030040 Address: 0xB00000 Command: JUMP (Error Code: e0030040),
Detailed Error Details: Direction of the Error=2000, Command Value=500000, Code Group Number=No Codegroup
File: X:test_dev_usbflashcodeflashdllFlashHdlr.cpp
Device ID: 0

you may need to put it in recovery mode as described here
androidin.net/bbs/thread-71604-1-1 .html

[Q] I bricked my XOOM

I tried to update my XOOM through FASTBOOT to ICS! i think i've done something wrong and i bricked it.
i Tried to flash it through RSD lite 5.0 and i keep getting error.
i copied the error log and it goes as:
"
19:03:03, February 14, 2012
Line: 2203
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
19:03:03, February 14, 2012
Line: 1045
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 2203
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 1045
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 546
ERROR: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
"
HELP PLZ !!!

omarykm said:
I tried to update my XOOM through FASTBOOT to ICS! i think i've done something wrong and i bricked it.
i Tried to flash it through RSD lite 5.0 and i keep getting error.
i copied the error log and it goes as:
"
19:03:03, February 14, 2012
Line: 2203
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
19:03:03, February 14, 2012
Line: 1045
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 2203
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 1045
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 546
ERROR: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
"
HELP PLZ !!!
Click to expand...
Click to collapse
Please use one of the several good rooting guides available right here.
You can try this, but it's not the only one.
http://forum.xda-developers.com/showthread.php?t=1249798
RSD Lite really just doesn't work with the Xoom...we have our own, good tools.
Get familiar with them and use them, please.

okantomi said:
Please use one of the several good rooting guides available right here.
You can try this, but it's not the only one.
http://forum.xda-developers.com/showthread.php?t=1249798
RSD Lite really just doesn't work with the Xoom...we have our own, good tools.
Get familiar with them and use them, please.
Click to expand...
Click to collapse
ok i falshed the recovery img of Tiamat and i cant get the xoom to power on!!
I am new to this, sorry for bothering with silly questions!
now i can boot to recovery android (Tiamat) and fastboot. but i need something i can flash a SBF file to the XOOM ..

Go to Development, look for the EOS ICS Rom for your device, put it and the GApps 10.5 version on your micro sdcard, and flash the rom, and then the GApps file immediately after (follow the instructions in the thread) and enjoy.

NDS Programming, Build Failure.

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.

Z3 dual D6633 BackupTA_V2 failed. Why?

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

[GKI] [android13-5.10] [Bazel] build failed Differences between ksymtab and symbol list detected!

I following this instruction:https://source.android.com/docs/setup/build/building-kernels
I initialized repo and synced
Using Bazel to build (with build/build.sh same error)
Using this command:tools/bazel run --lto=none //common:kernel_aarch64_dist -- --dist_dir=out/android13-5.10/dist
And get this error:
ERROR: /home/aaron/Builds/android-kernel/common/BUILD.bazel:26:22: Checking for kmi_symbol_list_
strict_mode //common:kernel_aarch64 failed: (Exit 1): bash failed: error executing command (from
target //common:kernel_aarch64) /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root f
or debugging
ERROR: Differences between ksymtab and symbol list detected!
Symbols missing from ksymtab:
- __cfi_slowpath
Symbols missing from symbol list:
Target //common:kernel_aarch64_dist failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 3572,647s, Critical Path: 3535,69s
INFO: 7 processes: 3 internal, 4 linux-sandbox.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

Hello, I also encountered this problem, how did you solve it?