Tag Info

New answers tagged

1

I managed to solve as follows (on Linux): Cause of problem: In the PIT, there is no partition, called "RECOVERY" (duh). Keep in mind, the command is case sensitive. Have a look at the PIT: sudo heimdall print-pit --verbose On my phone the recovery-related partition was called "Kernel2" What worked is: sudo heimdall flash --Kernel2 ...


1

As existing answers already show, there seems to be no "unique way" to achieve that. So I started combining ideas from allover, joining them into a script (or rather a "script library") to have them checked sequentially (until a good hit was made), and integrated that into my "Device Documentation Tool" named Adebar. Those interested can find it in the ...


0

I don't recommend using CWM Recovery for this, but if you're going to this video demonstrates the process -- https://www.youtube.com/watch?v=puLfjeKq_PY See also -- http://wiki.cyanogenmod.org/w/ClockWorkMod_Instructions#Additional_Commands My recommendation is to use Minitool Partition Manager on a Windows machine as it's quite clear what's going on ...


1

First off, don't worry about the first 4 entries. They are most likely mounted to the same partition, which is why they are showing the same exact sizes. If you are rooted, install BusyBox and try command busybox df -h. This should give you a better picture. For example, here's the output on my phone: shell@jgedlte:/ $ su su root@jgedlte:/ # busybox df ...


1

You can see sizes and usage statistics of all mounted partitions by simply using this command: df Note, the typical df -h does not work here and is not needed because the output is already in megabytes. The command works within adb shell and the Android terminal emulator, but not in the Recovery mode terminal because nothing is mounted at that point.



Top 50 recent answers are included