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
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
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.
Hello, everyone,
I'm using Ubuntu14.0.4 virtualbox virtual machine, the memory size is set as 2G. I set two more virtual disks(/disk_2nd for source code download, /disk_3rd for build output and the directory is android_out).
Java version is openjdk7 as required by android official website.
Git was rebuilt for openssl because of gnutls_handshake error during downloading source code.
I had met the problem caused by small swap so that I already set a new 8G swap partion(not swapfile).
Now I meet two problems during build the android-5.1.1_r2. I searched from web but can't find answer(looks someone met same problem but no answer). If someone can help, it will be very great. Thank you very much.
--------------------------------------------------------------------------------------------------------
1.
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: /disk_3rd/android_out/androidsource/host/linux-x86/obj32/SHARED_LIBRARIES/libjavacore_intermediates/luni/src/main/native/android_system_OsConstants.o: file is empty
libcore/luni/src/main/native/Register.cpp:36: error: undefined reference to 'register_android_system_OsConstants(_JNIEnv*)'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
2.
target Strip: libwebviewchromium (/disk_3rd/android_out/androidsource/target/product/generic/obj/lib/libwebviewchromium.so)
prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/arm-linux-androideabi-strip:/disk_3rd/android_out/androidsource/target/product/generic/symbols/system/lib/libwebviewchromium.so: File format not recognized
make: *** [/disk_3rd/android_out/androidsource/target/product/generic/obj/lib/libwebviewchromium.so] error 1
make: *** Waiting for unfinished work .....( It could be not exact the same words because I translate it from Chinese)
Hi!
I have trouble with rooting my MEDION LIFETAB S10333. This tablet runs Android 4.4.2, so I tried to run psneuter exploit but Android shell returned error: "FATAL: Kernel is too old Aborted".
After this I tried to install Magisk via adb and program returned error: "Failure [INSTALL_FAILED_OLDER_SDK]". Then I tried to root this device via towelroot and kingoroot to no effect.
Do you know other ways to root this tablet?
Kernel version: 3.0.36+
Regards!
AFAIK Magisk only is supported on devices running Android 6.0 ( released 2015 ) - API-level 23 - and higher.
You can try to temporarily root your tablet's Android by means of ADB if you have a su binary what is matching Android 4.4 at your hand.
FYI:
Android 4.4 ( released 2013 ) is API-level 19, today ( 2022 ) Android 12 ( released 2021 ) is API-level 31.
xXx yYy said:
AFAIK Magisk only is supported on devices running Android 6.0 ( released 2015 ) - API-level 23 - and higher.
You can try to temporarily root your tablet's Android by means of ADB if you have a su binary what is matching Android 4.4 at your hand.
FYI:
Android 4.4 ( released 2013 ) is API-level 19, today ( 2022 ) Android 12 ( released 2021 ) is API-level 31.
Click to expand...
Click to collapse
I cloned this github repo: https://github.com/jpacg/su-binary, then I tried to compile it but I got this error:
make[1]: Entering directory '/home/tomek/.bin/su-binary'
Android NDK: WARNING: Building static executable but APP_PLATFORM android-21 is not the latest API level android-31. Build may not succeed.
make[1]: Leaving directory '/home/tomek/.bin/su-binary'
make[1]: Entering directory '/home/tomek/.bin/su-binary'
[armeabi-v7a] Executable : su
ld: error: duplicate symbol: setxattr
>>> defined at common.c:113 (jni/su/common.c:113)
>>> ./obj/local/armeabi-v7a/objs/su/su/common.osetxattr)
>>> defined at syscalls-arm.S:1639 (out/soong/.intermediates/bionic/libc/syscalls-arm.S/gen/syscalls-arm.S:1639)
>>> syscalls-arm.o.text+0xE28) in archive /home/tomek/.bin/android_ndk/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/../sysroot/usr/lib/arm-linux-androideabi/21/libc.a
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [/home/tomek/.bin/android_ndk/android-ndk-r23b/build/core/build-binary.mk:728: obj/local/armeabi-v7a/su] Error 1
make[1]: Leaving directory '/home/tomek/.bin/su-binary'
make: *** [Makefile:5: build] Error 2
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?