CODEWITHSUNDEEP
androidshellpartition
Izzy
Izzy

Reputation: 1454

How can I identify partitions of an Android device from the shell?

I'm trying to find which partition is used for what, e.g. /boot, /recovery, /system, from adb shell. While this is trivial for partitions currently mounted (using the mount or df commands, see e.g. how to identify names of the partitions), this appears to be tricky when it comes to partitions not currently mounted (like /recovery when booted in "user mode").

There's a tutorial at XDA, but it didn't work out for any of the devices I've tried:

So I'm at a loss. I know there are apps like DiskInfo which can show those details, so there must be stored somewhere on the device. However, modifying the device (by installing an app) is not an option in my case.

So basically my question burns down to:

Where on the Android device is this information stored?

If possible, a generic approach is preferred. If not, a "try-and-err" of several approaches (if..elseif..fi) would do as well.

For background: an example use would be "I want to retrieve the /boot partition only" (get an image of it via dd). It wouldn't do to first grab all partitions, and evaluate later – too time consuming, and too much data produced ;) – This already describes the intention: writing a little tool to retrieve a particular disk image.

Upvotes: 23

Views: 65717

Answers (2)

Izzy
Izzy

Reputation: 1454

As there seems to be no "unique way" to achieve that, 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/partitions.lib file. As Adebar is open-source (GPLv2), feel free to copy and use it – or fork the project and improve it.

The full solution is a bit long to post here (as said, you can grab it at Github), but as SE policy is to include at least the general part in the post, here's what it does:

Different sources provide different sets of details, so it tries the "best ones" first – and then recurses down until at least something was found.

  • /proc/dumchar_info gives the most details, so this is tried first. Happy MTK users will get this.
  • /proc/mtd is the second best source.
  • /proc/emmc should have almost as much as the previous candidates, but is a bit tricky to use
  • /dev/block/platform/*/by-name, cross-checked with …
  • /proc/partitions cross-checked with /proc/mounts gives us at least the partitions mounted

So the script I've built basically walks the sources in this order, stopping as soon as it was able to collect details (e.g. if /proc/dumchar_info was found, no need to parse all the others). All of them put into separate functions, returning data using the very same structure, one could even merge results from all of them.

If someone can come up with a better solution, I'm of course always open for the idea :)

Upvotes: 15

Kazuki Sakamoto
Kazuki Sakamoto

Reputation: 13999

You can get the information of mounted-partition on Linux as https://stackoverflow.com/a/15639867/629118 , but I don't think Linux kernel doesn't know about boot and recovery partition if /dev/block/platform/**/by-name doesn't have it.

So you can use the currently mounted information to guess which partition is boot or recovery or something else in /dev/block/* that is not mounted.

In fact, fastboot only sends the name of the partition which you want to flash. It means only the bootloader for fastboot knows the information, I guess.

https://github.com/android/platform_system_core/blob/8163104b3feb575a321b194a70ecb9873a70b29d/fastboot/fastboot_protocol.txt

Upvotes: 1

Related Questions