[Moto G General] Professor Gibbins:
DISCLAIMER: This thread is unofficial and may contain errors. This information comes from personal knowledge and research from other threads. I am not responsible for what you do with your device.

Context

This thread is intended to provide an explanation of the function and importance of each partition on the Motorola Moto G. Some partitions are very ambiguous, but I will attempt to describe what these partitions store, and whether they are unique/permanent/temporary etc. Again, I am not a developer, but I hope that this will explain the structure of the partitions to new users. Also, feel free to leave more information about these partitions in the comments, and I will try to update the OP with that information.

The following partition layout can be found with root access using various commands such as

ls /dev/block/platform/msm_sdcc.1/by-name

List of partitions

DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
boot -> /dev/block/mmcblk0p31
cache -> /dev/block/mmcblk0p33
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p28
dhob -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p35
logo -> /dev/block/mmcblk0p27
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p30
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p10
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p29
recovery -> /dev/block/mmcblk0p32
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p12
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sdiBackup -> /dev/block/mmcblk0p14
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p34
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p13
userdata -> /dev/block/mmcblk0p36
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15

Partition explanations

Terminology

- Partition: A hard drive, eMMC, or any storage device can be divided into separate section called partitions. Most Windows, OS X or Linux machines have 1 to 3 partitions but android devices tend to have many.

- Unique: This means this partition contains data is specific to only that device, e.g. serial numbers, IMEIs, MAC addresses etc. This data cannot be found on the internet and so one should be careful not to modify or lose it.

- Flashing: Writing data to a disk or partition, replacing what was already there.

- Root ("/"): Not to be confused with "root access", this is the Unix term for the top directory. Similar to C:\, but everything is stored in it, including partition mount points.

Common Partitions

boot: This partition contains the boot image, which includes the kernel, a device tree blob (this describes the hardware to the kernel), and the ramdisk for the root filesystem (not root access - see above). This partition is usually flashed when installing custom or stock ROMs, and can be found within stock firmware. This partition does not contain the bootloader.

system: This partition contains the Android system files (i.e. the ROM). This is what is flashed (alongside 'boot') when installing a ROM, and what is modified to give root access. Before rooting or installing a ROM, one should backup this partition (and boot) to ensure they can restore to stock.

recovery: This partitions hold the files that allow one to enter ‘recovery mode’, which is essentially a second boot partition that allows one to apply OTAs, make/restore backups, and install ROMs or root binaries. This partition will either hold the stock recovery, or a custom recovery. Custom recoveries can be flashed and allow the user to backup, restore, install to and wipe other partitions, among other features. This partition can be safely modified but ensure to always have a stock recovery flashed when applying stock OTAs.

userdata: Also known as the Data partition, this is where every user file, preference and is stored, e.g. photos, settings, app settings, messages, and everything created directly or indirectly by the user. This partition is empty on a new device, and is mounted at /Data. This partition should always be backed up before modifying the phone as it contains essentially everything personal on the phone.

cache: Another common partition; this historically contained temporary data that allows the system and apps to run more efficiently. Now it is mostly used by the recovery. Nothing important is stored here, and so it can, and often should, be wiped when necessary.

Other Partitions

Bootloader Related Partitions

aboot: This partition seems to be the main part of the bootloader. It loads the kernel and is responsible for the bootloader menu and fastboot functionality. This partition is flashed as part of motoboot.img (source below) and so can be restored with stock firmware.

abootBackup: This likely stores a backup of the aboot partition.

tz: This partition also seems to be related to the bootloader, specifically something called 'Trust Zone' . This partition is flashed as part of motoboot.img (source below) and so can be restored with stock firmware.

tzBackup: Again, this likely stores a backup of the 'tz' partition.

rpm: Another bootloader related partition. This partition could possibly be the 'Resource and Power Manager' manager partition. This partition is flashed as part of motoboot.img (source below) and so can be restored with stock firmware.

rpmBackup: hopefully you get the general idea by now...

sdi: I have no idea, but it is flashed as part of motoboot.img, therefore it must be bootloader related. Is included with stock firmware.

sdiBackup: A backup of the above.

sdb1: Bootloader related. Interestingly, after looking around, I found that this appears to contains files relating to a 'Secondary BootLoader'. This partition is flashed as part of motoboot.img (source below) and so can be restored with stock firmware.

Network Related Partitions

modemst1 and modemst2: These partitions appear to contain non-essentials/temporary network related data. Interestingly, they are erased when flashing a stock rom, meaning they are probably not crucial, possibly some kind of ‘baseband cache’?

modem: The modem partition contains modem/baseband related files. These files store store settings that allow the device to communicate with cell towers, such as the frequencies. This partitions is region, not device, specific. This partition is flashed as part of the stock firmware flash procedure, so it also is likely not unique (again ensure to get firmware for the right region).

fsg: This partition also contains files related to the modem firmware/baseband. These files store store settings that allow the device to communicate with cell towers, such as the frequencies. This partitions is region, not device, specific. This partition is flashed as part of the stock firmware flash procedure, so it likely contains non-unique data (but ensure to get firmware for the right region).

Maybe ‘fsg’ and ‘modem’ are related to the modemst1 and modemst2 partitions?

Important/Unique Partitions

pds

: This partition likely contains important device specific data like the IMEI, Serial Number, etc. It is important to backup this partition when you get the chance, as people in other threads attribute the loss of the IMEI to this partition. This is not included in stock firmware, reinforcing the importance of backing up this partition.

persist

: Apparently this partition contains files related to WiFi, Bluetooth, MAC addresses etc. Nevertheless, it is quite important and should be backed up if possible.

hob

and

dhob

: The exact function is not known, but they appear to contain very important information relating to the modem and/or IMEI.

fsc

: Appears to be empty. Although, this partition could sometimes store important IMEI related info. Not included in factory firmware and so best left alone.

Extra

ssd: This partition appears to contains files related to something called the ‘Secure Software Download’ feature. These files are not included in factory firmware so should be left alone.

logo: This partition contains the startup splash screen and bootloader unlock warning. This partition is included with stock firmware.

clogo: After doing some research, it appears this partition might store the boot logo in an image format. Interestingly, this is not included in stock firmware, unlike the 'logo' partition.

cid: This partition appears to contain authentication/digital signature files for the bootloader. This partition is usually never interfered with, and there is no stock firmware for it, so it is best left alone.

sp: Like CID, this partition appears to contain authentication/digital signature files for the bootloader. This partition is usually never interfered with, and there is no stock firmware for it, so it is best left alone.

misc: This partition contains ‘miscellaneous system settings’, more specifically, this partition also helps the bootloader boot to recovery and pass information between boot stages. This partition is best left alone as it is apparently very important, and not included in stock firmware.

padA and padB: Apparently these are empty.

kpan: This partition seems to store kernel panic data.

logs: Possibly stores some form of log files.

utags: These partition seem to contain information used by the barcodes option in the bootloader menu.

utagsBackup: A backup of the above.

Unknown Partitions

DDR <-- Device Description Repository?.. Dance Dance Revolution?..

I could not find any information about the function of the above partitions. Although, none of these partitions are included in factory firmware, so they are likely important and best left alone. Anyone is welcome to share they own knowledge or opinion on what these partitions are for in the comments.

Sources/Interesting information:

Moto G Partition Layout.

http://xdaforums.com/showthread.php?t=2540799

Bootloader Related Partitions (motoboot.img - tz, rpm, sdi, aboot, and sbl1).

http://xdaforums.com/showthread.php?t=2644703&page=2

http://xdaforums.com/moto-g/help/problem-flash-stock-rom-xt1033-t3357718/post66336145#post66336145

Great reading about partitions on Samsung phones, although it appears a lot of this information is relevant to the Moto G. Specifically, this thread gives some hints about the function of motoboot.img, baseband partitions and the 'ssd' partition.

http://xdaforums.com/showthread.php?t=1959445

Possible explanation of modemst1, modemst2 and fsg partitions. (About Samsung partitions but still relevant).

http://xdaforums.com/showthread.php?p=49587431#post49587431

Instructions on flashing factory firmware.

http://xdaforums.com/showthread.php?t=2542219

CID, Trust Zone, and SP partition Information.

http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html

Possible /misc explanation, also some simple explanation of common partitions for new users.

http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/

Some more /misc info

http://linux-sunxi.org/Android/partitions

Thread with some information relating to 'hob' and 'dhob'

http://xdaforums.com/moto-g/help/imp-imei-backup-scripts-moto-g-eall-t3174569

Moto X Boot Logo Change - Appears to show purpose of 'clogo' partition on Moto G

http://www.talkandroid.com/guides/m...on-the-moto-x-splash-screen-no-root-required/

Info on Persist partition

http://xdaforums.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576

https://forums.lenovo.com/t5/MOTO-G...gs-like-hell-after-update/td-p/3231064/page/2

Likely explanation of 'kpan' partition - although 'Kernel PANic' does fit well

https://plus.google.com/+hashcode0f/posts/W84mLxfMomf

Information vaguely referencing 'logs' partition

http://www.ptsmobile.com/tc55/tc55-integrator-guide.pdf

http://techtablets.com/forum/topic/help-windows-fell-by-flash-android/

Info on 'utags'

http://xdaforums.com/moto-g/help/info-moto-g-imei0-t2925970/page26

Finally, thanks to [MENTION=4878287]_that[/MENTION] for extra information and corrections.