mauiaaron

adb backup -f SomeAndroidApp.ab com.example.SomeAndroidApp
dd if=SomeAndroidApp.ab bs=1 skip=24 | openssl zlib -d > SomeAndroidApp.tar
# TODO : investigate http://sourceforge.net/projects/adbextractor/
# TODO : investigate https://github.com/nelenkov/android-backup-extractor

mauiaaron

//
// Sigh ... adb shell changes LF to CRLF in binary streams ...
//
// http://stackoverflow.com/questions/13578416/read-binary-stdout-data-from-adb-shell
//
// Problem:
//  ( adb shell run-as com.example.someapp dd if=/data/data/com.example.someapp/some_binfile.bin 2\>/dev/null ) > local_binfile.bin
//
//  * Without piping through adb_sanitize you would get a corrupted binary
//

mauiaaron

#ifndef NDEBUG
#include <string.h>
#include <stdio.h>
#include <dirent.h>
#include <fcntl.h>
#include <unistd.h>
#include <errno.h>
#include <sys/resource.h>
int _debug_get_num_fds() {
     int fd_count = 0;

mauiaaron

/*
Yes, 1024 is an internal limit of __android_log_print / __android_log_vprint functions which printf() uses. See https://github.com/android/platform_system_core/blob/master/liblog/logd_write.c

As a workaround I can suggest using custom printf function:
*/

#include <android/log.h>

void uprintf(const char* format, ...) {
    va_list args;

mauiaaron

#include <stdio.h>
#include <mach/mach.h>

natural_t mach_getTotalBytes() {
    static natural_t totalBytes=0;
    if (totalBytes>0) {
        return totalBytes;
    }   

    mach_port_t host_port;