It sounds like the "/system/bin/app_process" has been modified and so it doesn't match the signature required. There are 2 ways to fix this, either get a copy of the stock file from another phone/rom or flash the factory image for 4.3
Edit: After reading "update 2" it sounds like you want the factory image option detailed below.
In short, if you want to flash KitKat Android 4.4, you'll have to upgrade to a version of CWM greater than v184.108.40.206. Or, use an alternate bootloader. For the Galaxy Tab 2 GT-P5113 or GT-p5110 you can find the instructions here.
It does this in order to break up large .tar files into chunks of 1000000000 bytes (or 1 GB):
-rwxrwx--- root sdcard_r 0 2014-03-19 14:31 data.ext4.tar
-rwxrwx--- root sdcard_r 1000000000 2014-03-19 14:33 data.ext4.tar.a
-rwxrwx--- root sdcard_r 1000000000 2014-03-19 14:36 data.ext4.tar.b
-rwxrwx--- root sdcard_r 1000000000 2014-03-...
Starting with version 6, deduplication support has been built into clockworkmod recovery. The blobs directory folder contains a hashed directory structure that holds the deduplicated files across all backups.
See the developer's Google+ post for more, in short:
ClockworkMod Recovery now deduplicates files between builds. This results in way ...
Clockworkmod stores its backups in /sdcard/clockworkmod/backup (replace /sdcard with the path for your external card if you're looking for backups to external memory). With versions prior to 6.0, you can move off (or delete) the entire directory to clear space. The entire backup is self-contained.
If you're using a 6.0 or greater version of Clockworkmod, ...
Yes, it is possible to install custom kernels on stock roms. The kernel developer will usually say which roms (or types of roms) the kernel supports. If you are not sure you can try reading the kernel thread, and there will always be poeple saying things like "working great on [firmware version here]". This way you can also make sure that it will work ok on ...
Primary reasons for the no swap recommendations are the basic uselessness of swap for most devices, performance reasons, and device longevity.
As Liam mentions, modern devices have no shortage of RAM (Even my old underpowered Wildfire S has as much RAM as my previous desktop.) and that RAM is managed fairly well by the modern Android system, making a swap ...
It was removed because
It's total placebo these days. I wrote it for dealing with the silly things that happen when we used to put apps on SD before Android supported it. Since then, it's been something of a sugar pill that magically fixes all problems without actually doing anything.
(Taken from the commit history, posted by Steve Kondik)
A zip package that contains a firmware update always includes two files in META-INF/com/google/android: updater-script and update-binary. updater-script is a text file containing commands required to install the update. update-binary translates the commands into binary code.
In Android 4.4 KitKat, Google has changed the interface that updater-script uses ...
According to: https://wiki.cyanogenmod.org/w/ClockWorkMod_Instructions#Making_a_backup
ClockworkMod's backup/restore feature will generally only back up the
/system, /data, /cache, /sd-ext, and /dalvik-cache areas. Other
partitions such as /emmc, /sdcard, and /media won't be backed up.
fact, the backed up system will typically be saved to ...
To unpack a YAFFS2 image, you can use the free unyaffs tool, which is available as pre-build ELF-binary (for Linux) from this page at code.google.com. This page also contains hints on how to obtain the source code, so you could build the binary yourself e.g. with gcc (gcc -o unyaffs unyaffs.c).
I use this tool myself, it works fine on Ubuntu 8.04 32bit as ...
I had the same problem. Looking at the source of heimdal revealed that this message is send when no USB device is attached.
And this was in fact the case. lsusb showed that the kernel is not aware of any USB device related to the Galaxy S:
flo@flo-pc ~/data/cm9-sgs $ lsusb
Bus 002 Device 004: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 003 Device 069:...
CWM is the shortform of ClockWorkMod. ROMManager, CWM recovery, Tether etc are their products. CWM Recovery and ROMManager are tools which enables you to backup your current ROM, install custom ROMs etc.
If you are interested in knowing more about CWM, see this page. For rooting you do not need CWM. In fact for installing CWM you need to be rooted.
Wipe data will wipe everything on your /data partition (hence the name). A factory reset will wipe the same (additionally also cache and Dalvik cache), and put your device back to a virgin state. Usually, this doesn't touch the (external) SDCard, and AFAIK should not touch the internal SDCard either.
I don't know on which partition your mentioned folder ...
Assuming your device adheres to some Android standards, you'd want to run fastboot oem device-info.
Often you can also run fastboot reboot-bootloader to get into the bootloader which often says right there on screen whether it's locked or not.
Different devices can display the lock state differently.
fastboot is located in %ANDROID_SDK_DIR%\platform-tools,...
Try doing what it suggests... run e2fsck -b 8193 /dev/block/platform/msm_sdcc.1/by-name/userdata. If that doesn't work, try running mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata.
You can also boot into fastboot mode and run fastboot erase userdata.
If none of these work, please elaborate on this "long story". How did you mess up your data ...
Inside Heimdall zip there is a driver folder.
Run the zadig.exe
click options - List All Devices
Choose your phone from the drop down list (on my pc it was "MSM8960"
I could not get it to work correctly on my PC, onece plugged into laptop "SAMSUNG Mobile USB CDC Composite Device")
Go through the drivers (WinUSB, Libusb0, Libusbk) and clikc Place drive ...
Some stock ROM's may replace the custom recovery with the stock recovery. To solve it you should install the custom recovery with fastboot and reboot to recovery and don't reboot to system. That will prevent the stock ROM from replacing the custom recovery.
To add to other answer, your back up has ALL the information in your back up image as the phone has when you took back up
/system refers to your ROM
/data refers to your data created by apps both that came with phone and user installed apps (/data/data)
/data/cache (the cache) refers to app data stored for quick access
/data/dalvik-cache (the Dalvik cache) ...
Android shuts down your OS before it actually becomes completely flat, in order to ensure it has enough power to do so safely and completely (which is why you can power it back up again, but then it shuts itself off again). Over time, your battery does need to be recalibrated as the system stats on battery usage get wonky and the battery itself won't store ...
Recalibrating your battery won't actually make it last longer. What it might do is ensure that the battery level display is more accurate, so that when it says it's at zero, it's actually at zero.
Personally, I used an app like Battery Calibration (requires root) and it seems to help. To be fair though, I haven't actually tested the actual levels myself, so ...
The general consensus is there's usually different partitions available:
When a guide says to flash "partition" where partition is one of the above, then that implies transferring the contents destined for the partition. The mileage will vary depending on the handset/manufacturer as not all of them actually have implemented ...
If you are talking about a Nandroid backup: Yes, it would. It creates images from the devices file systems -- so all that's stored there gets copied to those image files. You can then even extract single items using e.g. Titanium Backup.
This suggestion assumes familiarity with connecting to the phone via ADB
I had a similar situation on my previous phone. I was able to pull the important stuff over ADB when the phone was in recovery. In my case I had to mount some of the filesystems to access everything I wanted to retrieve.
I'm not sure if it is dependent on the phone whether the ADB ...
In addition to the well-known Titanium Backup app (for which you must purchase the Pro key to unlock the CWM/TWRP nandroid backup support), there is another app now: Nandroid Manager, which according to its description can restore apps from nandroid backups even with the free version (there is a Pro key too, but it is required if you want to restore special ...
Sony Xperia Devices use a recovery-in-boot arrangement. While you can't simply flash a version of TWRP or CWM, you can flash a kernel that includes what you need.
For the Xperia L, you can flash the Phanton Kernel, which includes CWM.
There is no other way to do get CWM or TWRP without flashing a new kernel.
The "device not supported" message means that you probably downloaded the recovery image for a different device (AT&T's LG G2 "d802", or International LG G2 "d800".) You can override this check, but it's not recommended, as the devices might be different enough that you could cause irreparable damage to it (a.k.a. "bricking".)
The most current TWRP ...
A nandroid backup is a full device backup – so you could ask the same question about a full backup of your PC: After restoring the backup, you'd be at exactly the state the device was in when you performed that backup – all changes done between making the backup and restoring it are lost.
Reading between the lines of your question, you're rather asking how ...
/emmc is basically ok and accessible if you can 'mount' it. You already have a working CWM installed which comes with adb enabled. This gives you some options.
Boot to CWM recovery and mount your partition in the 'mounts and storage' section. It's now accessible internally and you can use the adb tool (ADB stands for 'Android debug bridge', it's usually used ...