I usually use a combination of the following 4 commands and correlate them, since each of these commands gives a piece of the information that might be needed.
Using df lists the filesystem path alias and size info as seen below (total size, used, free and block size)
root@ks01lte:/sdcard # df
Firstly and most important, the credits:
I made this following this great tutorial at XDA-Developers by user metalgearhathaway: http://forum.xda-developers.com/galaxy-s2/development-derivatives/mod-partition-internal-memory-app-t2538947
I used PIT files (I'll explain what they are, don't worry) made from user ElGamal from XDA also, located here (comment ...
First to clarify only root (UID 0) isn't enough to get access to /data at least since Android 5. Discretionary Access Control based on traditional UNIX UIDs/GIDs alone doesn't fulfill the needs of modern complex OSes like Android. DAC is supplemented by Mandatory Access Control (MAC); SELinux in case of Android. So to access /data your process/user must ...
Kudos to @Bruno for a detailed solution and needed files. A much quicker method is listed below, which does not require installing any ROM/Gapps or reboot into the ROM in between steps. You need an external SD card with enough free space to hold all apps+data+photos+etc that are on your internal phone storage.
You can skip steps 1-5 if you already have CWM ...
I found another solution:
Have a look at /data/system/uiderrors.txt. There you will find the apps that are responsible for the trouble. You can delete them (manualy if necessary) to fix the issue. Reinstalling the apps brings the error back, though.
I installed the Disk Info app and in the options, I enabled Expert mode and Unmounted partitions. It doesn't say "swap", but it shows clearly that it's the only other partition on the SD card and it's the right size, so /dev/block/mmcblk1p2 must be the one:
Swapper 2 is configured to use /dev/block/mmcblk0p3 by default, so I'm glad I didn't go with the ...
fdisk -l works if you pass the whole disk device name explicitly (e.g., fdisk -l /dev/block/mmcblk1); what does not work is automatic discovery of block devices (apparently because Android places block device files under the /dev/block directory, but fdisk expects to see those files directly in /dev). Therefore one option is to collect the list of whole disk ...
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 ...
There is nothing abnormal in this case. They is only one device in the first preformatted text, which is /dev/block/mmcblk0 (just like /dev/sda in Linux distros). The rest are the partitions within that device (akin to /dev/sda1, /dev/sda2 and so on).
There is no normal limit, not that I came across, for how many partitions a device can have. It depends ...
This will not change the partition size of /system, but uses another approach: Limit the data placed on that partition. So here's what I did before flashing CM7.2 on my Milestone²:
download the file to flash. This is usually a .zip file (otherwise, the following won't work)
open the .zip with your favorite archive manager (alternatively: unpack to an empty ...
Who or how it was fixed as 190MB?
The manufacturers decided that. They probably expected that that size would be sufficient during the expected time they will continue official support for the phone.
Can the size of partition be increased?
If you're rooted and installed custom boot loader, yes partitions can be resized, although not in a way ...
Titanium Backup users can also go to the batch actions and select manipulate data > remove orphaned files.
As user48823 mentioned, you can also find the apps in /data/system/uiderrors.txt using a root-capable file explorer, but basically Titanium will do this for you, if you select the action I wrote above.
Just fixed it this way on my OnePlus One (...
The CyanogenMod 10 is the first update with the code to detect an invalid IMEI.
You could already have an invalid IMEI and don't know about it.
The issue with an invalid IMEI is that you may have emergency calling problems (inability to do emergency calls).
Does the IMEI reported match the number under your battery?
Dial *#06# and the ...
Even more useful information can be obtained from parted. An example when the block device is /dev/block/mmcblk0:
~ # parted /dev/block/mmcblk0 print
Model: MMC SEM04G (sd/mmc)
Disk /dev/block/mmcblk0: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
10 524kB 1573kB ...
I found it!
The answer was in PIT file, because as it says here:
you will only need to use this if a firmware update needs to change your partition layout (very very unlikely) or if you mess up you partition table (you don’t want to do this)
Which is definitely my case.
So, I tried that GT-I8190N and GT-I8190 should be used with different PIT files (I ...
1) On which physical storage does "Memory" sit
When the specs say "Memory", it's referring to the RAM that the device has. This is not persistent storage, it is "volatile" storage, which loses its information when unpowered (after a brief discharge time). RAM is memory the system and apps use to function, for things like storing the state of an application (...
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 lib/...
Can we explains android terms with its analog with PC[?]
We can try but it will restrict the expansion of our understanding since certain parts would never fit the analogy we're familiar in with desktop computing.
Take a good look at this image:
Image source: Reverse Engineering Android's Aboot - by Jonathan Levin
If you want an analogy, anything before ...
It's even riskier than cybersam says. You shouldn't check/repair a mounted filesystem (i.e. when it is in use), on any operating system, because programs might be using the files while you're checking them and possibly making changes. This could cause the checker to think there are errors where there are really no errors; it might cause unexpected behaviour ...
I had this problem trying to push back a backup of my Samsung Galaxy S2, using ADB with the CWM (clockworkmod) recovery tool. When pushing to a device file, ADB simply deletes the block device file and creates a regular file in its place, and thus no data actually ends up on the mmcblk0 device.
Unfortunately, piping the output of a command into "adb shell" ...
As GiantTree correctly pointed out, That not mounted space might be something the device uses in something like an emergency mode to restore the device. More precisely: it not only might be, but it is. Your df output e.g. doesn't say anything about the /recovery or /boot partitions. And there are even more we are not aware of.
Another argument against re-...
Yes you can boot in TWRP if bootloader is unlocked:
fastboot boot /path/to/twrp.img
Then you can simply dd whole eMMC or individual partitions. You need some extra memory (on external SD card) to backup whole eMMC or /data partition. Smaller partitions (including the biggest one: system) can be backed up to internal memory i.e. data partition.
I found out that all the apps missing have an .asec file in the .android_secure folder on the sd card, however the .android_secure folder itself is there.
On Linux I wrote:
cp sdbackup/* /media/disk -r
It copies all folders, and their content, recursively. Except for the hidden folders in sdbackup, e.g.:
You can use fdisk via busybox on a droid. So, assuming you have the busybox binary on your rom, and it's on your path, the command would simply be:
busybox fdisk [the various fdisk options...]
busybox fdisk -l /dev/block/sda
I tested this, and your concern is valid.
I added a dummy file to /system and then did a nandroid restore. The dummy file survived. Repeated the same test on /data with same result. So I don't know why CWM doesn't wipe those partitions first.
The CWM author probably made an assumption it doesn't matter or there may be a valid reason they don't get wiped....
In my case, I needed a cross-platform solution since I use Linux. Here's what worked for me:
Back everything up. This will wipe everything on the phone, including the internal SD card.
A PIT file you want to flash. I used this one, which resizes /system from 512 MB to 1 GB and /data from 2 GB to 6 GB
Any compatible recovery. I used this one
Looks like this phone does not support flashing partitions via the fastboot utility. According to this guide you will first need to root the phone by following the instructions from here:
Download the latest version of Framaroot and side-load the APK.
Open Framaroot select the action to perform. Select “Install SuperSU”.
In the rooting menu, ...
I stumbled upon this question. I like a challenge...
Tools that I used: BusyBox
I've come up with 3 commands (one you listed) to give some info about the partitions
busybox ls -QAl --color=never /dev/block/platform/*/by-name
lrwxrwxrwx 1 0 0 20 Jan 30 1970 "DDR" -> "/dev/block/mmcblk0p4"
lrwxrwxrwx 1 0 0 ...